Case Studies

Custom Solution for Change Management System

Situation:
A Major Chemical Company Needed a global application to manage the tracking, reviewing and implementing Enterprise-Wide changes.

• The Current Change Management application has a Single Web form (ASP) for all communities with a SQL Database as the back end. Adding new communities of users requires developer work to add data and customize the web form. The other issues with the Change Management application are,
• The Single Web form has very complicated code behind it.
• Change Management Submission meant an e-mail was sent to a generic e-mail box. The email was manually forwarded to the next person in the process chain. Information was also retyped into other applications.
• Browse or Search (could only look up using the ID number).

The process for submitting and managing the approval/disapproval of temporary and permanent change requests was inefficient. Change requests are submitted to a variety of communities based upon the nature of the change request with regards to specific processes and procedures for each community. It is the responsibility of the individual communities to manage the actual change request processing directed to that community. In conjunction with the Initiator (person who originally created the request), the key community member roles (Administrator, Approver, Coordinator, Reviewer, and Owner) are associated with processing of a change request.

Solution:
The new change management application eliminates these issues. The technologies chosen for this solution are.

• Microsoft InfoPath 2003 SP1.
• Windows SharePoint Services.
• C# for Application Logic Modules.
• BizTalk 2004 (with APCI enhancements).
• Web Services
• InfoPath to application logic modules.
• Application logic modules to/from BizTalk.