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 must 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 dual purpose:
- Used as a planning tool it facilitates in the consideration and identification of the components required to deliver a specific "change". The project manager subsequently builds these components into an action plan that will deliver those requirements.
A Sage X3 Change Control action plan actually comprises multiple plans: - A single high level Work Breakdown Structure
This plan outlines the approach to be taken 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 be completed 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 in the delivery of 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 the 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 once all individual tasks (actions) on the plans have been accomplished. This empowers the change manager to hold a change request at Implement status until the requirements have been delivered in full and have been approved. Once the delivered requirements have been approved the change request can then be advanced to the final status of Closed.
It is not mandatory 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.
For an overview of how to use this function in your particular role click on the appropriate link in the following list:
- Project manager (Planner)
- Actioner
- Stakeholder
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 will receive confirmation of this by email, if the CCMEMAILP - Email planner parameter (TC chapter, CCM group) is set. You are now responsible for planning a successful delivery of those requirements.
Your first task is to build the high level Work Breakdown Structure. This plan should outline the approach to be taken to meet the approved requirements. You will 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 should list the main products or transaction types required for the "change" with the main tasks or actions to be accomplished, and appropriate timeframes. You can adapt the level of detail you provide to the size of the requirements.
A complete Work Breakdown Structure should cover the key deliverables, the completion date and all components required to deliver the approved scope.
The timeframes, milestones and dates you define will provide you with an effective control mechanism in the successful delivery of the "change". You could baseline the change from them. One comment field per task is available to you which you could use to communicate with the assigned actioner and the stakeholders. You could use it, for example, to state assumptions or list constraints that might limit or affect progress or completion of that task.
High level Work Breakdown Structure
Your high level Work Breakdown Structure will provide the basis for your second task. This is to create detailed implementation plans for the key commitment types (or transaction types). It is these individual plans that will deliver the approved scope.
The commitment types for which you can define detailed plans 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 will help you determine which key deliverables are required to deliver the required scope and the level of detail necessary to communicate key information. You should assign to each key deliverable the task or action to be accomplished and by whom, with appropriate timeframes.
As you complete your high level Work Breakdown Structure and each of the detailed Implementation plans, select the Planning complete check box. 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 to which they have been assigned. They will receive confirmation of this by email, if the CCMEMAILAC - Email actioner parameter (TC chapter, CCM group) is set.
You have completed the Action plan when you have selected the Planning complete check boxes in the high level and each of the detailed plans. The change manager will receive 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 mplemented status.
Action plans are not mandatory. This function gives you total flexibility over which plans you need and which ones you decide are not required. For example, you could manage a successful delivery of the requirements from simply a high level Work Breakdown Structure. Alternatively you could manage the delivery of the requirements from a single detailed implementation plan without a Work Breakdown Structure to support it. There is, however, one rule you must 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 must, therefore, select the Planning complete check box in any plan that displays In planning status to trigger the system to do this.
Actioners can start the tasks to which they have been assigned before you select the Planning complete check box 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 exist within your organization. The system will block 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 the processing of transaction lines associated with a specific change request must be halted, or blocked. Should this be necessary you must 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 dealloacted. You must choose the most suitable blocking method for the type of transaction.
Refer to the impact analysis for 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 will help if you have to make a blocking decision against a sales order line.
You are advised not to reactivate a blocked transaction until the approved scope for this change request has been delivered in full. This will not be until the action plan has been implemented and the change request is complete.
Actioners
As an actioner you are responsible for taking ownership of and delivering a task or action in the action plan by the specified date.
At this point in the processing of a specific change request, however, you are dependent upon the project manager signaling the "go ahead". They will do this by confirming they have completed the action plan:
- The high level Work Breakdown Structure defines the approach to be taken to deliver the requirements for the "change".
It is complete when the status is Being implemented. - The multiple detailed Implementation plans define how the individual commitment types will deliver the approved requirements.
Each is complete when the individual plan status is Being mplemented.
As soon as a plan, high level or detailed, is complete you can start actioning the tasks (actions) to which you have been assigned. You will receive confirmation of this by email, if the CCMEMAILAC - Email actioner parameter (TC chapter, CCM group) is set. The email will contain a uniform resource locator (URL) to the completed plan.
All tasks you have been assigned to deliver will initially display 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 have made or constraints they are aware of.
You can start an assigned task before a plan is complete, if your company policy permits this. The system will block you from setting the task to In progress however you can set it when the plan status is Being implemented. 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 Complete status can the change request be advanced through the remaining stages of the processing cycle. It is imperative, therefore, that you keep your tasks up to date.
Using your Landing page to locate your tasks quickly and easily
You can tailor your personal Landing page to display specific groups of change requests. Some of these will provide you with direct access to tasks (actions) awaiting your input.
The following gadgets display change requests at the planning or implementation stage of the processing cycle. They are provided for you to add to your landing 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 (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 Sage X3 user code matches an actioner assigned to an incomplete task (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 require.
You can access the plan associated with the change request directly from the gadget using the standard Sage X3 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.
Whilst 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 Sage X3 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 necessary, for replanning. It is central to your accountability as a stakeholder.
Screen management
The High level block is the high level Work Breakdown Structure. This plan defines the approach to be taken 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 is displayed 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 required.
High level
Presentation
This block is the high level Work Breakdown Structure. This plan defines the approach to be taken to meet the approved requirements.
Project managers (Planners)
To build your high level Work Breakdown Structure append the main transaction types (entities) to be delivered with the tasks or actions to be accomplished. Then assign appropriate timeframes and actioners. A complete Work Breakdown Structure should cover the key deliverables, the completion date and all components required 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 have been associated for use within your particular organization with specific entities, or types of transactions. For example, if predefined, you could select that sales orders (entity) are cancelled (action) and that purchase orders (entity) are returned to the supplier (action).
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 have made or constraints you are 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 that customers (entity) must be consulted (action). Another action might be that your company's product catalogue (entity type "Other" with "Product catalogue" in the Comment field) must be updated (action). 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.
You must 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 will populate the Start and End dates and provide 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 are aware of.
Close
Fields
The following fields are present in this block :
|
This field indicates the current stage of this particular plan.
In planning Being implemented Completed Not applicable is displayed if either of the following conditions apply:
|
Project managers (Planners)
|
|
Select this check box if this particular 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 will receive confirmation of this 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 will receive a notification email when you complete the final plan. The emails will contain a uniform resource locator (URL) to this plan.
|
|
|
|
Use this field to identify a specific entity or type of transaction that must be actioned to deliver the required design or production "change". The list of entities is defined in local menu 2039. |
|
|
Use this field to define the task or action that must be performed on the associated entity to successfully deliver the required design or production "change". For example, you might select the action "Disassemble" if the associated entity is "Work orders" and this task is a prerequisite for a replacement component. The list of entities is defined in local menu 2032. |
|
|
Use this field to define the date by which this task must be completed.
|
|
|
Use this field to identify the Sage X3 user who must take ownership of the task or action assigned. This user will be responsible for delivering the assigned task in full by the required date. Type in or select from the Users table (AUTILIS) the code of the Sage X3 user who will be responsible for delivering the requirement. The query displays each user's Role and Department if appropriate values have been defined in the user parameters CCMROLE - Role (TC chapter, CCM group) and CCMDEPT - Department (TC chapter, CCM group). They will receive confirmation of this by email once the high level plan is complete, if the folder level parameter CCMEMAILAC - Email actioner (TC chapter, CCM group) is set. The email will contain a uniform resource locator (URL) to this plan.
|
|
|
Use this field to communicate information to others. Type in comments pertinent to the task (maximum 50 characters). For example, you could use this field to highlight or warn the actioner responsible for delivering the task of the following:
|
Actioners
|
|
Use this field to indicate the current stage of this planned deliverable.
Pending In progress Completed |
Close
Detailed Implementation Plans
Presentation
This grid displays a summary of the status of the individual implementation plans. Each plan provides a breakdown of all the work to be completed for the individual transaction types to deliver the approved requirements. Each plan can be accessed by simply clicking the appropriate action in the Action panel.
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 be included in your implementation plan from the same predefined set of values associated with the type of transaction (Sales orders, Sales quotes, purchase orders etc). 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.
Tip: Use the Assign to all lines functionality where a common process (action) is carried out on a majority of transactions for a selected transaction type. For the few transaction lines where a different action is required to deliver the approved scope you can then change the common (default) action. For example, in the event of a product change the majority of purchase orders (transaction type) are returned to the supplier (action). Purchase orders raised the previous working day, the minority of orders are, however, cancelled (action). For this scenario you could apply the default "Return to supplier" action. You could then use the Quick edit to change each order raised 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 you have made, or constraints you are aware of that might limit or affect progress or completion of that task.
Once you set your implementation plan as Planning complete your plan is validated. All transaction lines for which an action has been defined must have been assigned a completion date and an actioner responsible for delivering the task.
Actioners
Set the status of your assigned action (or task) when you begin the work and again when you complete it. This will populate the Start and End dates and provide 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 are aware of.
Close
Fields
The following fields are present on this screen :
|
|
This field indicates the current stage of this particular plan.
In planning Being implemented Completed Not applicable is displayed if either of the following conditions apply:
|
Project managers (Planners)
|
|
Select this check box if this particular 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 will receive confirmation of this 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 will receive a notification email when you complete the final plan. The emails will contain a uniform resource locator (URL) to this plan.
|
Assign to all lines
The following fields are present in this block :
To assign a default to all transaction lines in this plan:
This change request must be at In planning status. This plan must be at In planning status. You must be logged in as the current planner for this change request.
|
|
Use this field to define the task or action that must be performed on all transactions to successfully deliver the required design or production "change". As the default task your selected action will be applied to all lines on this plan. For example, you might select the action "Disassemble" if the selected entity is "Work orders" and this task is a prerequisite for a replacement component. The list of actions is defined in Local menu 2032. |
|
|
Use this field to identify the Sage X3 user who must take ownership of the task or action to be assigned to all transactions. As the default actioner your selected user will be assigned to deliver all lines on this plan. They will be responsible for delivering the assigned task in full by the required date. Type in or select from the Users table (AUTILIS) the code of the Sage X3 user who will be responsible for delivering the requirement. The query displays each user's Role and Department if appropriate values have been defined in the CCMROLE - Role and CCMDEPT - Department user parameters (TC chapter, CCM group). They will receive confirmation of this by email once the high level plan is complete, if the folder level CCMEMAILAC - Email actioner parameter (TC chapter, CCM group) is set. The email will contain a uniform resource locator (URL) to this plan.
|
|
|
Use this field to define the date by which all tasks must be completed. As the default completion date your selected date will be applied to all lines on this plan.
|
Lines
|
|
Use this field to define the task or action that must be performed on the associated entity to successfully deliver the required design or production "change". For example, you might select the action "Disassemble" if the associated entity is "Work orders" and this task is a prerequisite for a replacement component. The list of entities is defined in local menu 2032. |
|
|
Use this field to define the date by which this task must be completed.
|
|
|
Use this field to identify the Sage X3 user who must take ownership of the task or action assigned. This user will be responsible for delivering the assigned task in full by the required date. Type in or select from the Users table (AUTILIS) the code of the Sage X3 user who will be responsible for delivering the requirement. The query displays each user's Role and Department if appropriate values have been defined in the CCMROLE - Role and CCMDEPT - Department user parameters (TC chapter, CCM group). They will receive confirmation of this by email once the high level plan is complete, if the folder level CCMEMAILAC - Email actioner parameter (TC chapter, CCM group) is set. The email will contain a uniform resource locator (URL) to this plan.
|
|
|
Use this field to communicate information to others. Type in comments pertinent to the task (maximum 50 characters). For example, you could use this field to highlight or warn the actioner responsible for delivering the task of the following:
|
Actioners
|
|
Use this field to indicate the current stage of this planned deliverable.
Pending In progress Complete |
Close
Action panel
A change request must be at In planning status to create or change a plan.
|
Project managers (Planners) - Click the Edit action to do the following:
Actioners - Click the Edit action to update the status of the tasks to which you have been assigned.
|
|
Click the Return to request action to display the business case for this change request, that is, the full details of the change request itself. |
|
Click 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 version (that is, the major or the minor version) of the product on this change request.
- Where the product version has been specified, those commitments where the version of the product has not been specified, that is, the major/minor version is blank.
- An assembly associated with the product, or the specific version or revision of the product on this change request. This includes lines where the product or product version on this change request is a component or subassembly of a bill of materials (BOM). All commercial (sales), production (manufacturing) and subcontract BOMs are included.
Click 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 to which you have been assigned.
The individual transaction lines for each commitment type are generated when the impact analysis for this change is run. To repopulate the transaction lines with new snapshot, dynamic data you must update the impact analysis. To display the updated lines you must click the standard browser Refresh (F5).
Where there are variations, this is explained below with the action.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.
The following actions are available from the commitment type selected above.
|
Project managers (Planners) - Click the Edit action to do the following:
|
|
Click the Return to plan action to redisplay the high level Work Breakdown Structure and detailed plan status summary for this change request. You can access the detailed implementation plan for a different transaction type after you have selected this action. |
|
Click the Return to request action to display the business case for this change request, that is, 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 this plan if you are logged in as the current planner for this change request.
You cannot add or delete lines when the Plan status is 'Implement'
You can only add lines or delete lines from this plan when the plan status is In planning.
To revert this plan to In planning status from Being implemented status you must clear the Planning complete check box.
You can only clear the Planning complete check box when all assigned tasks are at Pending status. Tasks at In progress status can be reverted to Pending status; completed tasks, that is a task at Complete status, cannot be changed. If any tasks have been completed you cannot clear this check box.
You can only clear the Planning complete check box if you are logged in as the current planner for this 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 by which the associated task must be completed on each line. You cannot add a partially complete line to this plan.
To select the 'Planning complete' check box all lines in plan must have an Action ID, an Actioner and a Complete by date
You can only select this check box if this particular plan for this change request has been completed in full. A complete plan has an action or task, an actioner and the date by which the associated task must be completed on each line.
Some lines do not have actions defined
A complete plan has an action or task, an actioner and the date by which the associated task must be completed on each line. You have 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 will have unrestricted visibility and access to the plans otherwise access will be restricted by site. Check the level of access provided for your user profile as it could have site restrictions against it.