Dataset versioning creates a library of historical planning data on which new versions can be based. This system has a number of advantages:
At least one Planning version must always be retained. |
||
|
Care must be taken when deleting Dataset versions. |
|
|
Master versions should not be deleted. They should be moved into Archive and a new Master version created from the appropriate Planning version. |
|
Planning |
Planning versions are available for modification. |
|
|
There can be multiple Planning versions at any time. |
|
Master |
Master versions will have read-only access and will be locked. |
|
|
Only one Master version can exist at any time. |
|
|
Deletion of Master versions is prohibited. |
|
|
Master versions will contain only those projects with a status as defined with Application Settings. |
|
Archive |
Archive versions will have read-only access. |
|
|
Multiple Archive versions may exist. |
|
|
Archive versions can be copied from Master versions only. |
|
Locked |
Once planning versions have been locked, user modification is prevented. |
Year |
Scenario |
Historical |
Type |
|
A Planning dataset is created |
Year 1 |
Planning |
|
A Master Dataset is created from the original Year 1 planning Dataset. |
Year 1 |
Master |
|
A new Dataset is created, based on the Year 1 Master Dataset |
Year 2 |
Planning |
|
Year 1 Dataset is now Archived. |
Year 1 |
Archive |
|
Year 2 Dataset is now the Master copy. |
Year 2 |
Master |
|
A new Dataset is created based on the Year 2 Master data |
Year 3 |
Planning |