Spencer Technologies - Monday, January 31, 2011 8:16 PM:
We are in the very early stages of looking into options for an electronic system to handle document control, records management, etc... As I see it, much of the functionality provided by this tool will be part of the quality system and should thus be controlled. How are implementers controlling changes to the tool itself? How do you sandbox the changes for review and approval? How do you migrate the changes into the live system in a controlled manner? How do you capture the change - is it the full set of xml files that define the particular itemtype/form/workflow?
Brian - Tuesday, February 1, 2011 6:15 AM:
How do you sandbox the changes for review and approval:
Typically you will want three or four environments. Dev (sandbox) for devloping new functionality, Quality/Test for thorough testing and Production. You may also have a Test/Training environment for showing new users how to do something without giving them access to the Quality/Test system.
How do you migrate changes:
Transfer of functionality from Environment to Environment are done via "Packages" and are export from one database and imported to the next database using the "Solution Updgrade Tools" that can be found on the Community Projects Site. The tool includes a document providing instructions on use. You can run separate instances of Innovator allowing you to have different code trees between the Dev and Production environments if you are making changes to the code tree rather than making changes inside a given database.
How do you capture the change:
Import of a package into the system will write a log which contains information on what was added/changed in the import. The Package exported from one database and imported into the other contains all of the "new" changes to the system and could be stored/archived as progressive development points. These packages contain the xml that defines the Items etc that make up the solution.
Cheers,
Brian.
authentic - Monday, August 15, 2011 3:42 AM:
jkTiger1: Nike Shoes advertisements can be found almost anywhere. In all corners of the world, you can find big banners with the words NIKE on them. The Nike Free Run is one of the shoes that Nike is really proud of, making them the highlight of their advertisements and commercials. At the same time, Nike advertisements are also found in all top sports meet, sponsoring the professional athletes on the embark for glory and outbreak. On our Nike Shoes Australia, you will find the many shoes you have seen on the ads and TV commercials. Our Nike Shoes Online will not disappoint you with our huge veriety of Nike footwear.
My dear friends, so happy that you can see our store various and good performance Nike Shoes. As we all know that, as the no pressure wear feel spread over the world. We all persue the easy breath and lightweight shoes to realease our feet. Nike Shoes made it. Nike Free Shoes is come here to safe you. The barefoot design can let you enjoy amazing feel. Apart of that Nike Free Run 2 also can be yoru choice. If you wanan find a pair of awsome look shoes with various colors, Nike Air Max in good condition for your reference. Nike Air Max 2011 Australia with Nike Air Max unit resilient to absorb the impact gurantee your support. Nike Zoom Kobe VI in low cut design gurantee your free motion on court and improve your workout hot sale online now. What are you waiting? The chance to order the cheap and good performance Nike Shoes on your eye sight now. Just catch it! Fast and free shipping worldwide!
Spencer Technologies - Tuesday, February 1, 2011 12:41 PM:
Hi Brian,
Thanks for the response. Based on your comments, I'm envisioning the release of a change as the following sequence:
- Develop the solution in a separate environment using a replication of the production database. Informal development testing is done here. Export to a package.
- Import the package into the Quality/Test environment, also using a replication of the production database (maybe the same database as is used for development?). Perform verification and validation here. Provide access for reviewers to review and try out the change. Export to a package.
- Bundle the exported package along with the design description and the V&V evidence in an ECR on the production system.
- ECR approvers review and approve the package in the production system and then document control works with the developers / IT to import the package into the production system.
- Document control / developers / IT verify that the import log matches the import log from the Quality/Test environment (where relevant) and verify that the solution is installed.
Steps #4 and #5 feel a little sloppy but probably not unreasonable. Any comments on this workflow? Are there any implementers out there that can describe how they control changes to the system?
Thanks again for the feedback.
Brian - Tuesday, February 1, 2011 4:36 PM:
Hi,
Your Test/Quality database should be as close to the production instance as possible so that you don't have to extensively re-test in the production environment, you can just import and go.
The ECR that you are describing in step 3 is really only a written description as there are no "Items" to change inside the database as you are changing the structure of the database itself. Nothing to stop you from doing it but the system isn't designed to keep that sort of track of itself.
The closer you make the Quality/Test system to the Production system the more confidence you will have that the changes will work correctly in the Production System.
A note regarding importing changes. Adding and editing individual elements/properties of the items in the system will be handled by the Import tool. Deleting say an activity or path from a workflow or a lifecycle or a property from an Item Type will not be handled by the Import tool. ALL deletions must be handled manually so it is very important that designers keep track of ANY and ALL deleted elements/items etc within the system since you must manually update these in all systems along the way.
I think the real trick to a process like this is to have the requirements and the test scenarios determined before you start the development that way everyone knows that if you have met all the requirements by passing all the tests then you are in good shape to import into the production system.
Cheers,
Brian.
Spencer Technologies - Tuesday, February 1, 2011 5:25 PM:
Thanks for the continued input on this question. Regarding the importance of the Quality/Test system closely mirroring the production system, is it feasible to accomplish this by starting fresh on each test cycle by replicating the entire production system to create a new test system? What all would be involved in that replication? Thanks.
Brian - Tuesday, February 1, 2011 5:45 PM:
Hi,
Yes it is feasible to do that replication.
Bear in mind that the production system will (should) only change when you want it to so if your tests in the Quality/Test system are OK and you successfully import the changes to the new system then they will be the same anyway. Obviously if you import other packages into the Test system that don't make it to production then you will have a divergence and want to overwrite with the production system at some stage.
Essentially you will back up your production database and copy it over your Quality/Test database. In order to do this you will need Microsoft SQL Server Management Studio which comes with SQL Server.
Check on the community projects for the "Demo Database" project. There is a document there that describes copying a backed up database into a new instance.
FYI: I am a consultant on PLM systems working for Matrix (an Aras Partner www.matrix.co.nz) and would be happy to assist you on a more formal basis through any part of your analysis and/or implementation. I can be reached directly by email at [email protected].
Regards,
Brian.
Spencer Technologies - Tuesday, February 1, 2011 5:56 PM:
Thanks Brian, I appreciate your assistance. This solution certainly appears to be one of the more promising options we've surveyed, largely due to the extensive flexibility and relative simplicity when it comes to customization. Thanks again for all your answers.
