0055 Basic data - Revision management

Use this tab to configure how revisions will be managed within your company. Revisions can be managed by reference date or by revision number.

Note: Set this field before you start working with Revision Management, and do not change it afterwards. Changing it would have major implications for your accounting records. If you want to change the field setting anyway, please contact Isah first.

Part revision management by reference date

Use revision management by reference date if you want to be able to maintain different calculations for a part. If you are using revision management by reference date, you will register the validity period of calculation lines. This is done in the Parts module on the Calculation/production tab, using the Parts, Operations, Equipment, External operations, and Surcharges buttons. All of these calculation components have a Revision tab on which the validity of the lines can be set. When using this method, the validity of the calculation is based on a reference date.

Part revision management by reference date is often used to phase out a calculation component by entering a validity end date, and then adding a new part line that will be valid as of that date.

The characteristics of revision management by reference date are:

• Part revisions are released immediately after they have been created.
• The validity of the calculation lines is entered on the Revision tab of the relevant calculation line. By default, part calculation lines are valid from the entry date of the line, whereas operation, equipment, external operation, and surcharge lines are valid from January 01, 1900 to December 31, 9999.
• Part calculations are copied to production files based on the reference date. By default, this is the system date. If a BOM contains more than one level, this reference date will be used throughout the structure.

Part revision management by revision number

Use the 'Part revision management by revision number' option if you want to formally maintain different calculations for your parts based on revision numbers. As with revision management by reference date, you can register part revisions, as well as the validity of the calculation lines. Revision management by revision number is basically an extended version of revision management by reference date.

Before you start working with this method, specify when a new part revision must be created in the Fields resulting in part line copy when changed pane. You can do so by filling in the fields that control your revision management. If the values entered here are changed on a part calculation line in the Parts module, a new revision number will be created for the parent part. The new revision number is created automatically.

Tip: You are recommended to include the Part number field as a revision-linked field. This field may be relevant if a part is included in the calculation of another part. For example, if a component is taken off the market, and you will use a new part as the component instead, the parent part will automatically be assigned a new revision number.

The characteristics of part revision management by revision number are:

• Releasing a revision is a separate step.
• The validity of the part calculation lines is determined by Isah, and is based on your actions (entering, changing, deleting). The validity of the part calculation lines always corresponds with one or more revisions, and cannot be changed manually.
• The validity of the other calculation lines (operations, equipment, external operations, and surcharges) works in the same way as for revision management by reference date.
• Only calculation lines of non-released revisions can be entered and deleted. Released revisions may be changed, but only if the fields are marked as revision-linked (General Settings module, Basic data, Settings, Revision management tab, Fields resulting in part line copy when changed pane).
• Part calculations are copied to production files based on the part revision number of the production file. This is also true for the underlying calculations of multi-level BOMs.