MarcL: PLM solutions at a minimum should provide Version tracking for the most recent released revision and previous revs with date/time stamps. A new version should be based on an update of the PLM database which should occur whenever an item is checked into the PLM solution, and also should occur when the user initiates an update, but typically does not need to coincide with the user saving changes on their local disk.
Peter Schroer:
Aras internally used the terms Major_Rev, Minor_Rev and Generation.
The “Version” and “Revision” are just labels that do not impact the underlying web services behaviors. In our experience, everyone calls it something different; it’s the defined behaviors that are important.
CMII revision behaviors are supported by the standard out-of-the-box Aras configuration.
All edits, whether work-in-process or formal releases are tracked in Aras Innovator (these are the Generations), and your company decides which of the increments are exposed to which users.
Once a File is checked-out, a Generation is reserved, and that user can make multiple edits which are saved to disk without bumping the Generation.
This Generation behavior is configurable and for security intensive scenarios can be set-up to log every save, but the default settings allow local saves that are not recognized by the PLM system.
For more info on this see posts like ‘Version & Revision Release Levels in Aras’ and ‘Data Relationships and Fixed / Float Rules in Aras’
Or check out the Posts Tagged ‘Revision & Version’.
Tags: configuration management, customize, document management, File Vaulting, Files, framework, Items, ItemType, Objects, platform, Revision & Version, Rules, Vault
what's your take?