Plan

Use this function to guide and schedule the implementation and execution of a design or a production "change".

You can access this function from the Change Control menu or from the Action panel in a change request.


The key to implementing and executing a successful "change" to a design or a production model is in the planning. An action plan conveys the objectives for the change to the stakeholders and to those actually involved in delivering that change.

This function supports the planning process by bringing all the components that need to be met to successfully deliver a change into a central repository. With quick and easy access to the guiding document for information, and functionality provided to define the rules and controls, this function offers a dual purpose:

  • Used as a planning tool, it facilitates in the consideration and identification of the components needed to deliver a specific change. The project manager subsequently builds these components into an action plan that will deliver those requirements.
    A Change Control action plan actually comprises multiple plans:

    • A single high level Work Breakdown Structure
      This plan outlines the approach to take to deliver the requirements for the change. Essentially it describes the "what", "who", and "when" objectives from the approved scope.
    • Multiple detailed implementation plans
      These plans provide the detail or specifics for delivering the approved requirements. They meet the "how" objectives from the approved scope by providing a breakdown of all work to complete by commitment type or transaction type.
  • Used as a communications tool, it provides the outline and guide for making decisions.
    Stakeholders can use an action plan to consider the components proposed by the project manager and for confirming or developing the scope of the requirements.

By providing this functionality from a single location, the Plan function becomes a critical tool for delivering the business case for change requests. It categorizes the sequencing of activities, and simplifies time estimations to avoid delays and potential cost overruns.

As an additional feature, this function can also safeguard delivery of the approved scope. An action plan directly impacts the progress of a change request through the remaining stages of the processing cycle. A change request, therefore, can only progress to Completed status after all individual tasks or actions on the plans are accomplished. This empowers the change manager to hold a change request at Being implemented status until the requirements are delivered in full and are approved. After the delivered requirements are approved, the change request can then be advanced to the final Closed status.

You do not need to define an action plan.

All plans are automatically deleted if the status of a change request is reverted from In planning status to In review status.

Roles

For an overview of how to use this function in your particular role select the appropriate link in the following list:

Project managers (Planners)

At this stage in the processing cycle of a change request, the change request has been reviewed and progressed to In planning status. As the project manager or planner assigned to that change request the change manager has effectively handed over control of it to you. You'll receive confirmation by email, if the CCMEMAILP–Email planner parameter (TC chapter, CCM group) is set. You're now responsible for planning a successful delivery of those requirements.

Your first task is to build the high level Work Breakdown Structure. This plan needs to outline the approach to take to meet the approved requirements. You'll use it to control or manage the key areas of the design or production change.

To build the Work Breakdown Structure, use the business case or information provided on the change request as your guide. The change request is both the concept proposal and the requirements document. You need to list the main products or transaction types needed for the change with the main tasks or actions to accomplish, and appropriate timeframes. You can adapt the level of detail you provide to the size of the requirements.

A complete Work Breakdown Structure needs to cover the key deliverables, the completion date, and all components needed to deliver the approved scope.

The timeframes, milestones, and dates you define provide an effective control mechanism for successful delivery of the change. You could baseline the change from them. 1 comment field per task is available to you that you could use to communicate with the assigned actioner and the stakeholders. You could use it to state assumptions or list constraints that might limit or affect progress or completion of that task.

Refer to the High level Work Breakdown Structure section.


Your high level Work Breakdown Structure provides the basis for your second task. This is to create detailed implementation plans for the key commitment types or transaction types. It’s these individual plans that deliver the approved scope.

The commitment types that you can define detailed plans for align with the Change control impact analysis functionality. Use the high level Work Breakdown Structure as your guide when building the individual Implementation plans. It helps you determine which key deliverables are needed to deliver the scope and the level of detail necessary to communicate key information. Assign to each key deliverable, the task, or action to accomplish and by whom, with appropriate timeframes.

Refer to the Detailed implementation plans section.


As you complete your high level Work Breakdown Structure and each of the detailed Implementation plans, select the Planning complete checkbox. This sets the status of that plan to Being implemented. This informs the stakeholders that that particular plan is complete. It also indicates to the actioners that they can start actioning the tasks on that plan they're assigned to. They'll receive confirmation of this by email, if the CCMEMAILAC–Email actioner parameter (TC chapter, CCM group) is set.

You've completed the action plan when you've selected the Planning complete checkboxes in the high level and each of the detailed plans. The change manager receives a notification email to confirm this, if the CCMEMAILCM–Email change manager parameter (TC chapter, CCM group) is set. A completed action plan also advances the status of the change request to the next stage in the processing cycle, Being implemented status.

Action plans are not necessary. This function gives you total flexibility over which plans you need and which ones you decide are not needed. You could manage successful delivery of the requirements from simply a high level Work Breakdown Structure. Alternatively you could manage delivery of the requirements from a single detailed implementation plan without a Work Breakdown Structure to support it. There is, however, one rule you need to follow. The status of the change request can only advance to the next stage in the processing cycle, Being implemented status, when the action plan is complete. You therefore need to select the Planning complete checkbox in any plan that displays In planning status to trigger the system to do this.
Actioners can start the tasks they're assigned to before you select the Planning complete checkbox if your company policy permits this. Transactions can then be added to a plan at a later stage. This can be particularly useful where a hierarchy of processes exists within your organization. The system blocks a task from being set to In progress, however it can be set when the plan is ready. Just be aware that the Start date will not then reflect the true start date for the task.

Blocking transactions

A potential consequence of a change can be that processing transaction lines associated with a specific change request needs to be halted or blocked. If this is necessary, you need to manually block the transaction lines affected by the requirements.

Manual blocking is different for the different transaction types. Purchase order lines, for example, can be closed if the supplier has not shipped the goods. Sales order lines can either be closed or the stock deallocated. You need to choose the most suitable blocking method for the type of transaction.

Refer to the impact analysis for more information. The detailed sales orders impact analysis, for example, displays the quantities processed at each stage of an order's preparation and delivery cycle. This information helps if you need to make a blocking decision against a sales order line.

You’re advised not to reactivate a blocked transaction until the approved scope for the change request is delivered in full. This is not until the action plan is implemented and the change request is complete.

Actioners

As an actioner you’re responsible for taking ownership of and delivering a task or action in the action plan by the specified date.

At this point in processing a specific change request, you’re dependent upon the project manager signaling the "go ahead". They'll do this by confirming they've completed the action plan:

  • The high level Work Breakdown Structure defines the approach to take to deliver the requirements for the change.
    It’s complete when the status is Being implemented.
  • The multiple detailed Implementation plans define how the individual commitment types deliver the approved requirements.
    Each is complete when the individual plan is at Being implemented status.

As soon as a high level or detailed plan is complete, you can start actioning the tasks or actions assigned to you. You'll receive confirmation by email, if the CCMEMAILAC–Email actioner parameter (TC chapter, CCM group) is set. The email contains a URL (uniform resource locator) to the completed plan.

All tasks you've been assigned to deliver initially display the Pending status. Set the status of the action when you begin the work and again when you complete it. The Start and End dates are linked to the Status field and populated automatically when you select a value. This not only provides visibility to all stakeholders of your particular progress to date, but also to the progress of the plan overall. Take note of any comments added by the project manager in the Comments fields. They can add a comment per task and could highlight assumptions they've made or constraints they're aware of.

You can start an assigned task before a plan is complete, if your company policy permits this. The system blocks you from setting the task to In progress, however you can set it when the plan is at Being implemented status. Just be aware that the Start date will not then reflect the true start date for the task.
Remember to update the high level Work Breakdown Structure and the detailed Implementation plans. You might have multiple tasks on the detailed plans assigned to you covered by a single task on the high level plan. Keeping the whole action plan up to date provides visibility to all stakeholders of its progress.

The status of your tasks directly affects the status of the whole action plan and ultimately delivery of the requirements. Only when every task on every plan is at Completed status can the change request be advanced through the remaining stages of the processing cycle. It’s imperative, therefore, that you keep your tasks up to date.

Using your personal home page to find your tasks quickly and easily

You can tailor your personal home page to display specific groups of change requests. Some of these provide you with direct access to tasks or actions awaiting your input.

The following gadgets display change requests at the planning or implementation stage of the processing cycle. They're provided for you to add to your home page as Representations (Modules = Change control, Categories = No category):

  • Change requests to plan
    This gadget shows all change requests awaiting, or currently in planning, where your Sage X3 user code matches the assigned planner or project manager.
  • Plan
    This gadget shows all active change requests at the planning or implementation stage of the processing cycle.
  • Plans to action
    This gadget shows all change requests where your user code matches an actioner assigned to an incomplete task or action on an associated plan.

Each gadget displays a spot view of the selected, filtered data at the point you run it. You can use the standard Sage X3 query functionality to manipulate the results in the gadget until it displays the results you need.

You can access the plan associated with the change request directly from the gadget using the standard functionality available on every row.

Stakeholders

As a stakeholder or member of your company's change board or steering committee, you can, at any time, access an action plan. An action plan shows you how the objectives for the design or production change will be met. You can use it as a mechanism for referencing and managing business risk and potentially costs.

While the majority of communication would have taken place during your scheduled meetings, you can obtain specific information when you need it from the plan. Each action plan, the high level Work Breakdown Structure and the detailed implementation plans for the individual commitment types provides visibility of proposed changes. Each action plan also provides visibility of progress against that plan.

From each plan, you can access critical information associated with the specific change request. To access this data, use the standard functionality available with individual fields. From the detailed implementation plans, you can open the details of the individual transactions.

If your actioners update their statuses on a "real-time" basis, the action plan keeps you informed. You can use it when determining the costing estimates, for budgeting and, if needed, for replanning. It’s central to your accountability as a stakeholder.

Prerequisites

Refer to the documentation on Implementation.

Screen management

The High level block is the high level Work Breakdown Structure. This plan defines the approach to take to deliver the requirements for the change request.

The summary grid displays the current status of the individual implementation plans. The entities listed are aligned with the associated impact analysis.

A plan status can be one of the following: In planning, Being implemented, or Completed. Not applicable displays if either of the following conditions apply:

  • The associated impact analysis did not generate any transaction lines.
  • The project manager has confirmed that the plan is not needed.

High level plan

This block is the high level Work Breakdown Structure. This plan defines the approach to take to meet the approved requirements.

For an overview of how to use this function in your particular role select the appropriate link in the following list:

Project managers (Planners)

To build your high level Work Breakdown Structure, append the main transaction types or entities to deliver with the tasks or actions to accomplish. Then assign appropriate timeframes and actioners. A complete Work Breakdown Structure should cover the key deliverables, the completion date, and all components needed to deliver the approved scope.

The actions you can include in your high level Work Breakdown Structure are from a predefined set of values. These are associated for use within your particular organization with specific entities, or types of transactions. For example, if predefined, you could select that the sales order entity is canceled and that the purchase order entity is returned to the supplier.

You assign the key dates and personnel to oversee delivery of each individual "action". You can also add a comment per action to highlight planning assumptions you've made or constraints you’re aware of.

You can broaden the scope of your high level Work Breakdown Structure by including actions for entities associated with your organization. For example, if predefined, you could select a recommendation to consult the customers entity. Another action might be to update your company's product catalog (entity type "Other" with "Product catalog" in the Comment field). You cannot draw up detailed plans for these entities, but by including them in your high level Work Breakdown Structure your action plan will be complete.

Refer to the documentation on Actions.
You need to exercise caution before setting your high level Work Breakdown Structure as Planning complete. As soon as an actioner sets the status of one of their actions to In progress, your high level Work Breakdown Structure will be fixed. You will not be able to append to or delete any of the lines on the plan.

Actioners

Set the status of your assigned action (or task) when you begin the work and again when you complete it. This populates the Start and End dates, and provides visibility to all stakeholders of your progress.

Take note of any comments added by the project manager in the Comments fields. They could highlight assumptions the project manager has made or constraints they're aware of.

For an overview of how to use these fields in your particular role select the appropriate link in the following list:

Status (HIGHLEVEL)

The current stage of the plan.


The following stages are associated with the preparation of a plan and delivery of the requirements:

In planning: When the plan is ready for planning or is currently being prepared (planned).

Being implemented: When the plan is complete.
The individual tasks are defined and the plan is ready for implementing (actioning) or is being actioned.

Completed: When all tasks on the plan are delivered in full.

Not applicable displays if either of the following conditions apply:

  • The project manager has confirmed that the plan is not needed.
  • The associated impact analysis did not generate any transaction lines.

Project managers (Planners)

Planning complete (IMPLEMENT)

Indicates that the plan is complete and ready for implementing.

This indicates to the actioners assigned to specific tasks on the plan that they can now action their tasks. They'll receive confirmation by email, if the CCMEMAILAC–Email actioner parameter (TC chapter, CCM group) is set. If the CCMEMAILCM–Email change manager parameter (TC chapter, CCM group) is set, the change manager receives a notification email when you complete the final plan. The emails have a URL to the plan.

This change request needs to be at In planning status and you need to be logged in as the current planner to have access to this checkbox.
If you've assigned yourself as an actioner, you will not receive a notification email.

The overall status of this change request and the status of the individual plans are directly linked:

  • When the high level Work Breakdown Structure and each of the detailed implementation plans are complete, the change request automatically changes to Being implemented status.
  • Conversely, if the change request is manually changed to Being implemented status, all high level and detailed plans are changed to Being implemented status automatically. The action plan effectively, therefore, is complete.

This particular plan becomes "fixed" when you select this checkbox. To change this plan when its status is Being implemented, all assigned tasks need to be at Pending status. Only then can you clear this checkbox and amend the plan accordingly. Tasks at In progress status can be reverted to Pending status. Completed tasks at Completed status cannot be changed.

To append or amend a task in the plan:

  • The change request needs to be at In planning status.
  • The plan needs to be at In planning status.
  • You need to be logged in as the current planner for the change request.
Entity (TRANTYPE)

The specific entity or type of transaction to action to deliver the design or production change that's needed.

The list of entities is defined in the 2039 local menu.
Action (ACTIONID)

The task or action to perform on the associated entity to successfully deliver the design or production change needed.

For example, you might select the action Disassemble if the associated entity is Work order and the task is a prerequisite for a replacement component.

The list of entities is defined in the 2032 local menu.
Complete by (COMPLETEDATE)

The date to complete the task by.

The date for the final task in your plan should equate to the deadline for delivery. Your final scheduled completion date is essential to delivering a successful change.
Actioner (ACTIONER)

The Sage X3 user that needs to take ownership of the task or action assigned. The user will be responsible for delivering the assigned task in full by the required date.

Select the code of the user responsible for delivering the requirement.

The query displays each user's Role and Department if appropriate values are defined in the CCMROLE–Role (TC chapter, CCM group) and CCMDEPT–Department user parameters (TC chapter, CCM group).

They'll receive confirmation by email after the high level plan is complete, if the folder level CCMEMAILAC–Email actioner parameter (TC chapter, CCM group) is set. The email has a URL to the plan.

If you've assigned yourself as the actioner, you will not receive a notification email.
Comment (COMMENT)

Communicates information to others.

Enter comments pertinent to the task up to a maximum of 50 characters. You could use this field to highlight or warn the actioner responsible for delivering the task of the following:

  • Planning assumptions, or factors that are true, real, or certain that need to be validated for the assigned task.
  • Constraints that might limit or affect progress or completion of the task such as resource availability, a contract reference, or legal rule reference numbers.

Actioners

Status (LINESTATUS)

The current stage of the planned deliverable.


The following stages are associated with actioning a task in the plan:

Pending: When a new action (task) is added to the plan.

Pending is the default status for new tasks.

In progress: When the task in the plan has started or is currently being actioned.

Changing the task from Pending to In progress automatically populates the Start date.

You can revert the task from In progress status to Pending status. If you do this, the system deletes the Start date automatically.

Completed: When the task in the plan is delivered in full and the task is complete.

Changing the task from In progress to Completed populates the End date automatically.

You need to ensure that the scope of the task is delivered in full before you select the Save action. It will not be possible to revert it to In progress after you select Save.

When all tasks are set as complete, the status of the whole plan (Status field) changes to Completed status.

You need to be logged in as the assigned actioner to set a task status.
The change manager, or project manager or planner for the change request is not permitted to add status tracking information on your behalf.

Detailed implementation plans

This grid displays a summary of the status of the individual implementation plans. Each plan provides a breakdown of all the work to complete for the individual transaction types to deliver the approved requirements. Each plan can be accessed by selecting the appropriate action in the Action panel.

For an overview of how to use this function in your particular role select the appropriate link in the following list:

Project managers (Planners)

You create your detailed implementation plans in much the same way as you created your high level Work Breakdown Structure. You select actions to include in your implementation plan from the same predefined set of values associated with the type of transaction such as sales orders, sales quotes, or purchase orders. However, instead of assigning a completion date for the transaction type, you assign individual actions and timeframes to individual transaction lines.

Alternatively you can set a single action, actioner, and timeframe as the default for all displayed transaction lines for the selected transaction type. For example, if predefined, you could select the action "Return to supplier" for a single or all purchase order transactions. Another action could be to "Cancel" all sales order transactions or to "Disassemble" individual work order transactions.

Use the Assign to all lines functionality where a common process or action is carried out on a majority of transactions for a selected transaction type. For the few transaction lines where a different action is needed to deliver the approved scope, you can then change the common or default action. For example, in the event of a product change, the majority of purchase orders transaction type are returned to the supplier. Purchase orders created the previous working day, the minority of orders are canceled. For this scenario, you could apply the default Return to supplier action. You could then use the Quick edit to change each order created the previous working day to the Cancel action.

You assign key dates and personnel to deliver each individual action. You can also add a comment per action. Use this to state assumptions that you've made or constraints you’re aware of that might limit or affect progress or completion of that task.

Refer to the documentation on Actions.
After you set your implementation plan as Planning complete, your plan is validated. All transaction lines with an action defined need a completion date and an actioner responsible for delivering the task assigned.

Actioners

Set the status of your assigned action or task when you begin the work and again when you complete it. This populates the Start and End dates and provides visibility to all stakeholders of your progress.

Take note of any comments added by the project manager in the Comments fields. They could highlight assumptions the project manager has made or constraints they're aware of.

For an overview of how to use these fields in your particular role select the appropriate link in the following list:

Plan status (xxxPLASTA)

The current stage of this particular plan.


The following stages are associated with preparation of the plan and delivery of the requirements:

In planning: When the plan is ready for planning or is currently being prepared or planned.

Being implemented: When the plan is complete.

The individual tasks are defined and the plan is ready for implementing or actioning, or is being actioned.

Completed: When all tasks on the plan are delivered in full.

Not applicable displays if either of the following conditions apply:

  • The project manager has confirmed that the plan is not needed.
  • The associated impact analysis did not generate any transaction lines.

Project managers (Planners)

Planning complete (IMPLEMENT)

Indicates if the plan is complete and ready for implementing.

This indicates to the actioners assigned to specific tasks on the plan that they can now action their tasks. They'll receive confirmation by email, if the CCMEMAILAC–Email actionerparameter (TC chapter, CCM group) is set. If the CCMEMAILCM–Email change manager parameter (TC chapter, CCM group) is set, the change manager receives a notification email when you complete the final plan. The emails have a URL to the plan.

The change request needs to be at In planning status and you need to be logged in as the current planner to have access to this checkbox.
If you've assigned yourself as an actioner, you will not receive a notification email.

The overall status of this change request and the status of the individual plans are directly linked:

  • When the high level Work Breakdown Structure and each of the detailed implementation plans are complete, the change request automatically changes to Being implemented status.
  • Conversely, if the change request is manually changed to Being implemented status, all high level and detailed plans are automatically changed to Being implemented status. The action plan effectively, therefore, is complete.

This particular plan becomes "fixed" when you select this checkbox. To change the plan when its status is Being implemented all assigned tasks need to be at Pending status. Only then can you clear this checkbox and amend the plan accordingly. Tasks at In progress status can be reverted to Pending status. Completed tasks at Completed status cannot be changed.

Assign to all lines

The following fields are present in this block:

To assign a default to all transaction lines in the plan:

  • The change request needs to be at In planning status.
  • The plan needs to be at In planning status.
  • You need to be logged in as the current planner for the change request.
Action ID (DEFACTIONID)

The task or action to perform on all transactions to successfully deliver the design or production change. As the default task your selected action is applied to all lines on this plan.

For example, you might select the action Disassemble if the selected entity is Work order and the task is a prerequisite for a replacement component.

The list of actions is defined in the 2032 local menu.
Actioner (DEFACTIONER)

The Sage X3 user that needs to take ownership of the task or action assigned to all transactions. As the default actioner, your selected user will be assigned to deliver all lines on the plan. They'll be responsible for delivering the assigned task in full by the required date.

Select the code of the user to be responsible for delivering the requirement.

The query displays each user's Role and Department if appropriate values are defined in the CCMROLE–Role and CCMDEPT–Department user parameters (TC chapter, CCM group).

They'll receive confirmation by email after the high level plan is complete, if the folder level CCMEMAILAC–Email actioner parameter (TC chapter, CCM group) is set. The email has a URL to the plan.

If you've assigned yourself as the actioner, you will not receive a notification email.
Complete by (DEFCOMPDATE)

The date to complete all tasks by. As the default completion date, your selected date is applied to all lines on the plan.

The date should equate to the completion date defined in the high level Work Breakdown Structure.

Lines

Action ID (ACTIONID)

The task or action to perform on the associated entity to successfully deliver the design or production change.

For example, you might select the action Disassemble if the associated entity is Work order and the task is a prerequisite for a replacement component.

The list of entities is defined in the 2032 local menu.
Complete by (COMPLETEDATE)

The date to complete the task by.

The date for the final task in your plan should equate to the completion date defined in the high level Work Breakdown Structure.
Actioner (ACTIONER)

The Sage X3 user that needs to take ownership of the task or action assigned. The user will be responsible for delivering the assigned task in full by the required date.

Select the code of the user responsible for delivering the requirement.

The query displays each user's Role and Department if appropriate values are defined in the CCMROLE–Role and CCMDEPT–Department user parameters (TC chapter, CCM group).

They'll receive confirmation by email after the high level plan is complete, if the folder level CCMEMAILAC–Email actioner parameter (TC chapter, CCM group) is set. The email has a URL to the plan.

If you've assigned yourself as the actioner, you will not receive a notification email.
Comment (COMMENT)

Communicates information to others.

Enter comments pertinent to the task up to a maximum of 50 characters. You could use this field to highlight or warn the actioner responsible for delivering the task of the following:

  • Planning assumptions, or factors that are true, real, or certain that need to be validated for the assigned task.
  • Constraints that might limit or affect progress or completion of the task such as resource availability, a contract reference, or legal rule reference numbers.

Actioners

Status (LINESTATUS)

The current stage of the planned deliverable.


The following stages are associated with actioning a task in the plan:

Pending: When a new action (task) is added to the plan.

Pending is the default status for new tasks.

In progress: When the task in the plan has started or is currently being actioned.

Changing the task from Pending to In progress automatically populates the Start date.

You can revert the task from In progress to Pending status. If you do this, the system deletes the Start date automatically.

Completed: When the task in the plan is delivered in full and the task is complete.

Changing the task from In progress to Completed populates the End date automatically.

You need to ensure that the scope of the task is delivered in full before you select the Save action. It will not be possible to revert it to In progress after you select Save.

When all tasks are complete, the status of the whole plan (Status field) changes to Completed status.
You need to be logged in as the assigned actioner to set a task status.
The change manager, or project manager or planner for the change request is not permitted to add status tracking information on your behalf.

Action panel

A change request needs to be at In planning status to create or change a plan.

Edit

Project managers (Planners): Select the Edit action to do the following:

  • Create or add tasks to a high level Work Breakdown Structure.
  • Set your high level Work Breakdown Structure as Planning complete. This informs the "actioners" and stakeholders that the plan is complete and ready to implement.

Actioners: Select the Edit action to update the status of the tasks assigned to you.

The Edit action only displays when the following conditions are met:

  • The change request is at In planning or Being implemented status.
  • You’re logged in either as the current planner for this change request or an actioner assigned to this change request.

Return to request

Select the Return to request action to display the business case for the change request. The full details of the change request itself.

List of change requests

Select the List of change requests action to return to the full list of change requests in the database.

The following actions display the list of commitments for the selected commitment type that have one or more open lines for the following:

  • The product, or the specific major or minor version of the product on the change request.
  • Where the product version is specified, those commitments where the version of the product has not been specified and the major or minor version is blank.
  • An assembly associated with the product, or the specific version or revision of the product on the change request. This includes lines where the product or product version on the change request is a component or subassembly of a bill of material (BOM). All commercial sales, production, and subcontract BOMs are included.

Select the required action to do the following:

  • Project managers (Planners):

    • Create or add tasks to a detailed implementation plan.
    • Set your detailed implementation plan as Planning complete to inform others that the plan is complete and ready for implementing.
  • Actioners: Update the status of the tasks assigned to you.
The individual transaction lines for each commitment type are generated when the impact analysis for the change is run. To repopulate the transaction lines with new snapshot, dynamic data you need to update the impact analysis. To display the updated lines, you need to select the standard browser Refresh (F5).

Where there are variations, this is explained below with the action.

Sales orders


Sales quotes

Purchase orders


Purchase requests


Work orders


Sub contract orders


Demand forecasts

The list displayed does not segregate those forecasts that are for a specific major or minor version of the product.

Stock


BOMs

This action displays a list of assemblies and subassemblies that are associated with the product on the change request. All commercial sales, production, and subcontract BOMs are included.

  • The sales BOMs are those used on sales orders.
  • The production BOMs are those used in cost calculations, work order management, Material Requirements Planning (MRP), and the Master Production Schedule (MPS).
  • The subcontract BOMs are those used on subcontract orders, in cost calculations, MRP, and the MPS.

Routing

This action displays the list of routes as the sequence of operations, materials, and tools needed to produce or process a product that are associated with the following:

  • The product on the change request.
  • An assembly (BOM) associated with the product on the change request. This includes lines where the product on the change request is a component or subassembly put together using a route and the bill of material.
The list displayed does not segregate those routes that are for a specific major or minor version of the product.

The following actions are available from the commitment type selected above.

Edit

Project managers (Planners): Select the Edit action to do the following:

  • Set a single action, actioner, and timeframe as the default for all displayed transaction lines for the selected transaction type.
  • Set your detailed implementation plan as Planning complete. This informs the "actioners" and stakeholders that this plan is complete and ready to implement.
Actioners: You need to select the Quick edit icon on the individual lines to update the status of the tasks assigned to you.

Return to plan

Select the Return to plan action to redisplay the high level Work Breakdown Structure and detailed plan status summary for the change request.

You can access the detailed implementation plan for a different transaction type after you've selected this action.

Return to request

Select the Return to request action to display the business case for the change request. The full details of the change request itself.

Error messages

In addition to the generic error messages, the following messages can appear during the entry:

You do not have permission to add or delete lines

You can only add lines or delete lines from the plan if you’re logged in as the current planner for the change request.

You cannot add or delete lines when the Plan status is 'Implement'

You can only add lines or delete lines from the plan when the plan status is In planning.
To revert this plan to In planning from Being implemented status, you need to clear the Planning complete checkbox.
You can only clear the Planning complete checkbox when all assigned tasks are at Pending status. Tasks at In progress can be reverted to Pending status. Completed tasks at Completed status cannot be changed. If any tasks are completed, you cannot clear the checkbox.
You can only clear the Planning complete checkbox if you’re logged in as the current planner for the change request.

The Entity field must contain a value

You cannot leave the Entity field blank.

The Description field must contain a value

You cannot leave the Description field blank.

Lines with an Action ID must have an Actioner and Complete by date

A complete plan has an action or task, an actioner, and the date the associated task needs to be completed by on each line. You cannot add a partially complete line to this plan.

To select the 'Planning complete' checkbox all lines in plan must have an Action ID, an Actioner and a Complete by date

You can only select the checkbox if the particular plan for the change request is completed in full. A complete plan has an action or task, an actioner, and the date the associated task needs to be completed by on each line.

Some lines do not have actions defined

A complete plan has an action or task, an actioner, and the date the associated task needs to be completed by on each line. You've left some lines in this plan blank.

[User] ( [User name] ) is not authorized for [Entity] for site [Change request Site]

Permission to edit this plan is controlled through your user profile. If your user profile has administrator rights, you have unrestricted visibility and access to the plans, otherwise access is restricted by site. Check the level of access provided for your user profile. It could have site restrictions.

Tables used

Refer to the documentation on Implementation.