eSpline

Governance to the Change Process...

eSpline's Managing VC:Team Edition adds governance to the VC & IPC change process that improves quality and productivity with a combination of software tools and partner software running on an eSpline hosted server or on a server behind your firewall.

It is a long process and you go through many of these manually.  Governance can begin here:

1.  Avenue Managing VC provides multiple ways to Extract a product model to an SaaS application

2. You want to check the model for possible errors or issues with compatibility, so you run the Health Check

3.  You review the Health Check report and make changes to a copied VC or IPC product model 

4.  You direct Managing VC to Extract the changed VC product model or IPC or SSC Kb 

5.  Now, there are two [2] versions of a product model [original and changed] 

6.  View the model characteristics, pre-conditions, materials, dependency nets, long text, etc. in an  easy to read HTML from or create a PDF with active links for easy navigation of the model 

7.  Compare the two selected models and see the differences highlighted in color, in seconds 

8.  Managing VC recognizes changes, creates a test case and sends the test case to ConfigScan (Automated VC Testing solution) 

9. Collaborate with your VC Team click on an icon next to the change and to make a comment / request and send a message to your VC Teams members or tester 

10.  Managing VC sends an email with the message/comment for review and answer with a comment 

11.  You may create additional, reusable test cases to automatically test your changes 

12.  Then, you automatically test the changed model to make sure there are no conflicts resulting  

13.  Repeat until the model behavior is stable and results are correct and documented 

14.  ConfigScan informs Managing VC with a notification message and a green icon appears that the test cases passed

15.   You review the changes and formally approve the changes with a click of the mouse 

16. You, direct an automatic move or upload of the changed model to a target SAP instance  

17. Create a Engineering Change Notice for the changes approved  

18. Then, you have Managing VC document and archive the model by including the Model View PDF generated report, the generated test cases, the new VC model, original VC model, the Managing VC log files and your original specifications.

Avenue Managing VC has led you through a consistent process where you have:

Your model quality is assured

improved governance for SAP Product models

Now there is a history of the changes and tests.  You now have a repository of the changes with the original and new VC models and you have done it in nearly half the time as the manual process.  This is improved productivity. With the ability to track all transactions made while in the eSpline Managing VC Portal, reqports can be created from the log files. Now you have Governance.

Except for making the model changes, the change process has been improved and automated.   Your model is thoroughly tested and the Project Manager has seen the test results, the changes have been approved and now are ready for moving to QA or Production.