Disciplined authoring using MCN

You can use an active Manufacturing Change Notice (MCN) to track all changes related to a given activity. One of the benefits of tracking the changes in the MCN is that when the changes are ready for release, all changes are processed.

Note:

Although the name implies change, it is recommended that you use an MCN when you initially create process elements and operations. This makes it easier to take advantage of the benefit of using the MCN, ensuring all changes are tracked and released together.

You have the option of setting the preference NGPDisableAuthoringWithoutMCN to True, which suppresses the commands listed below. This preference is set to False by default.

When you set the preference NGPDisableAuthoringWithoutMCN to True, you cannot make changes to an activity without an active MCN. To enable the tracking of subsequent changes, you can create an MCN from the activity page by selecting the icon without navigating to other pages.

  • Create a process element, regardless of the method used

  • Revise a process element

  • Clone a process element with or without traceability

  • Delete a process element

  • Update a cloned process element

  • Update a cloned activity

Note:

Cloning an activity or a build element is not impacted by this preference and does not require an active MCN.

If the preference NGPDisableAuthoringWithoutMCN is set to True, and there is not an active MCN that includes the affected activity, you will receive an error message if you attempt any of the commands listed above.

For more information about change management and MCNs, see Request and release changes.