Checklist: Creating a Change
Are you ready to create a new Change?
Start the workflow in one of three ways:
- Click New Change in the Changes world
- Select Items from a list and click Include in Change
- Build a Promoted Request into a Change, carrying Items from the Request to the Change.
What type of Change is this?
Pick a Category. The Change Number and Effectivity fields may be prefilled with default values if your workspace is already configured.
Who needs to approve this Change?
Routings are the group of users who will review and vote on the Change. You may be able to select a routing, depending on how your workspace is configured. If you do not see the option to choose a routing, a Change Administrator or BOMControl will route it for you.
What is the approval deadline for your Change?
It is a good idea to set a specific date when you think the Change should be approved. BOMControl will send reminders as the deadline approaches. If you choose to enforce the deadline, however, the Change will be rejected if all necessary votes are not cast by the deadline. Setting an approval deadline and enforcing it are both optional.
When will this Change become effective?
The Change can take effect immediately, or on a future date. Use the calendar icon to choose a date. Note that temporary effectivity is for Deviations only.
What Items are affected by this Change?
You can add Items as part of the New Change workflow or return to an Open and Unlocked Change later and click Add Items. The fastest way to add Items to an Open Change is to search for Items and build a list using the Keep or Show Only commands.
What is going to be different about the Items when this Change becomes effective?
For each Item you add, you’ll select the action to be performed as part of the Change. Examples of actions are:
- Release an Item to the Design or Production stage
- Move an Item to a different phase (such as Obsolete or Abandoned)
- Make modifications to the Item’s working revision effective, creating a new effective revision and superseding the old revision
Which Item views are modified?
For Items where you are making working modifications effective, you’ll select the Item views that should be included in the Change. Views that have been modified are shown in bold. Views you select here will be locked as soon as the Change is submitted. Enter notes about each view, describing what modifications have been made.
What will the new revision numbers be?
In the same step, you’ll set the next revision number for each Item. If your workspace is configured to use revision sequences, you can just click Use Next at the top of the page to use the suggested revision number for all included Items.
Add More Information. After creating the Change, make sure reviewers have all the information they need to vote.
Do you need to attach Files?
Generally, Files associated with a Change provide information about modifications being made to included Items. You can also add a markup: a file containing instructions for modification. Create markups in the Files world. In the Files view of the Change, search for Files and associate them with the Change—or upload and associate new Files in one workflow.
What will you do with existing inventory?
What should be done with existing stock of Items affected by this Change? What about products in the field, or Items on order? In the Items view, click the Inventory Disposition subview and click Edit for each Item. Choose a date when the new revision should be considered effective, and enter instructions for how to treat existing inventory of Items affected by the Change.
Should any Requests be associated with the Change?
In the Requests view, select existing Requests that are relevant to the Change. In the Addressed Requests subview, you can select any Request; in the Related Requests subview, you can select Requests that contain Items included in the Change.
Do Suppliers need access to this Change?
In the Supplier Access view, you can grant Supplier users three levels of access:
- Read access allows Supplier users to view the Change after it is approved.
- Approval access allows Supplier users to vote on the Change at the stage you choose.
- Implementation access allows Supplier users to participate in the process of implementing an approved Change by adding files, notes, and setting a status.
Remember that Supplier users must be granted access to included Items in order to view those Items.
Assess Impact. Use built-in tools to see how a Change will affect your product record.
Do you need to include assemblies?
In the Items view, click the Affected Assemblies subview and review the list of assemblies containing Items included in the Change. Use the checkboxes to select assemblies and click Include in Change.
Does the Change have errors or notices?
Click the Alerts view to see if there are any problems with the Change. Errors are caused by lifecycle rule violations, such as releasing an assembly to Production when its BOM contains Items in earlier lifecycle stages. You can usually resolve errors by removing the affected Items or including other Items. A Change cannot be submitted with errors. Notices are potential problems with the Change, such as an Item with a repeated revision number, but will not stop a Change from being submitted.
Submit Change. When you’re ready, submit the Change for approval or for routing, depending on the routing method used in your workspace. Included Item views are locked and cannot be edited.