Navigation:  Configuration > Product Master >

Change Control

Training Manuals Alphabetical Function List Back Print this Topic Previous topicOne level upNext topic
Show/Hide Hidden Text

This tab is applied to specify the level of control to be exercised in certain areas that define the configuration of an item.

These areas include the Product structure (bill of material) where the item and it's components/material are defined with related engineering, manufacturing and maintenance data. It also includes the Part operations (routing) that defines the way the item is manufactured/assembled, as well as repair and maintenance tasks if the part is a maintenance significant item. The other area includes revisions to items drawings.

 

For each of these areas, and for the life cycle that a part may be in at a given point in time, the level of control may be varied.

 

The control must be specified by either the assigned Product manager or Product administrator.

They  can specify stricter levels of control for a product than those specified on System Configuration for these areas, but never any value that implies less change control than the minimum required as a Company policy.

 

Change control thus implies that unless "No control" is the specified option, any additions, changes or deletes of records in the product structure, part operations and/or revisions will only be allowed if the user can reference an approved Engineering change proposal. See Change proposal (ECP) for more detail.

 

If the predefining of key fields are required, the ECP has to specify the exact key to be changed or deleted. (e.g. parent and component part for a product structure change and routing part, operation number and type for a part operation).

The selected ECP thus need to reference the exact key being changed or deleted.

 

If the option is "Record changes", the parent part or routing part must be referenced but it is not required to identify the exact component or operation to be changed or deleted. During implementation of the ECP, the exact keys that were added, changed or deleted will be record in the ECP detail.

 

On this tab the following fields can be viewed:

 

hmtoggle_plus1Apply

The "Apply" button is enabled when the signed on user is the Product Manager or Product Administrator of the selected product code.

 

When the "Apply" button is clicked, the Product Master table is updated with any new level(s) of ECP control, should these levels at least adhere to the minimum levels of control as specified on System configuration.

hmtoggle_plus1Ecp Control For Planning Bills

The purpose of the change control setting on the Change Control tab is to indicate whether the existing change control rules as specified on the change control tab do apply or not, to forecasting or planning bills of material.

 

Since product structures created for the purpose of forecasting or planning purposes can consistently change, you may not want to enforce ECP control on changes to these bills of material. Forecast/planning bills may be for long lead-time items or product options and the assigned percentages for the options may be adjusted frequently as and when market trends vary.

 

You thus have the option to either exclude these bills from the strict levels of control or you can decide that change control applies anyway. The change control setting is used in conjunction with Forecast Planning Bill setting on the Part Master function. The current change control rules shall apply if the linked product code's change control setting is checked.

hmtoggle_plus1Grid

The grid is used to setup and/or maintain the levels of Change (ECP) control in conjunction with the settings, ECP Control Part Operations , ECP Control Part Revisions , and ECP Control Product Structure on System Configuration.  The Product manager can specify stricter levels of control than those specified on System Configuration, but never any value that implies less change control than the minimum required as a Company policy.

 

Change control thus implies that unless "No control" is the specified option, any additions, changes or deletes of records in the product structure, part operations and/or revisions will only be allowed if the user can reference an approved Engineering change proposal.

 

If the predefining of key fields are required, the ECP has to specify the exact key to be changed or deleted. (e.g. parent and component part for a product structure change and routing part, operation number and type for a part operation).

The selected ECP thus need to reference the exact key being changed or deleted.

 

If the option is "Record changes", the parent part or routing part must be referenced but it is not required to identify the exact component or operation to be changed or deleted. During implementation of the ECP, the exact keys that were added, changed or deleted will be record in the ECP detail.

 

The cells display the Change Proposal (ECP) Level of Control. It is populated with the column value and column description from the Column Values table where the column name is equal to "ECP Level of Control" and the column values matches the value entered or

selected by the user. The number of characters to be entered before the list is shown is governed by the value of  "populate length" (mandatory).

 

Only the Product Manager or Product Administrator may change the level(s) of control.

 

After adding a new product code, the grid defaults to the values of the settings ECP Control Part Operations , ECP Control Part Revisions , and ECP Control Product Structure  from System Configuration.

 

When inquiring on an existing product code, the grid displays the levels of Change (ECP) control and the life cycle stages of the Part Operation, Part Revision and Product Structure tables from the Product Master table.

 

The settings for ECP control can be either "No Control N", ECP Control Applies "Changes are Recorded R", or ECP Control Applies "Key fields to be Predefined P".  The minimum scenario allowed as per the System Configuration settings are as follows:

 

1.If the setting is "ECP Control Not Forced", no control is forced on any life cycle stage. If a new product code is added, all the ECP life cycle settings will default to "No Control".  The Product Administrator or Product Manager may change the ECP level of control to "Record Changes" or "Predefined key fields" for stricter control.

 

2.If the setting is from "Experimental Development XDM", control is forced from "Experimental Development XDM" through all the life cycles to Obsolete "OBS". The Product Administrator or Product Manager may only change the ECP level of control between "Record Changes" or "Predefined key fields".

 

3.If the setting is from "Advanced Development Model ADM", "Experimental Development XDM" is optional but the rest of the life cycle from Advanced Development Model "ADM" is forced.

 

4.If the setting is from "Engineering Development Model EDM", "Experimental Development XDM" to "Advanced Development Model ADM" is optional and "Engineering Development Model EDM" to "Obsolete OBS" is forced.

 

5.If the setting is from "Pre Production Model PPM", "Experimental Development XDM" to "Engineering Development Model EDM" is optional and "Pre Production Model PPM" to "Obsolete OBS" is forced.

 

6.If the setting is from "Production Model PM", "Experimental Development XDM" to "Pre Production Model PPM" is optional and "Production Model PM" to "Obsolete OBS" is forced.

 

7.If the setting is from "Production Model", Excluding "Obsolete Phase PMO", "Experimental Development XDM" to "Pre Production Model PPM" and "Obsolete" Phase is optional and "Product Model PM", and "Post Production Model PP" is forced.

 

8.If the setting is from "Production Model", Including "Obsolete Phase PMO", "Experimental Development XDM" to "Pre Production Model PPM" is optional and "From Product Model", Including "Obsolete Phase PM", and "Post Production Model PP" is forced.

 

Only the Product Administrator or Product Manager may change the ECP level of control. For any one of the table's, life cycles which is optional, any control setting may be selected.

 

For any one the table's life cycles that is enforced, the ECP level of control may only be switched between "Record Changes" or "Predefined" key fields.