Global MSD - Supply Chain Initiatives

1. Global MSD - Supply Chain Initiatives SCITe Communication to ‘Functional Teams’ 17/08/2001

2. SCITe - Progress between end of functional team workshops and beginning of August • 1. Each functional team produced a summary of the work done to date in each workstream (June 18). This contained (to varying degrees of breadth and depth), the following information: • A list and description of the business scenarios that would need to be taken into consideration by a potential supply chain planning and scheduling solution • Business requirements that an Advanced Planning and Scheduling (APS) system would need to deliver to support the identified business scenarios, • Benefits allocated by cpb across each of the supply chain categories identified in the Macro Assessment Study (MAS), and split between better data and information, improved processes, changes in people and organisation, and application capability • Issues surrounding the capability of MSD to implement a supply chain planning solution due to concerns about application capability, data capability, process change, organisation and people changes, timescale, past history etc • Functional and data requirements. Not all teams produced this due to time. • 2. The functional team workbooks have been consolidated into one document - the ‘Consolidated • Project Document’. This is a working document which will be used as the prime source of information in constructing the 502. It contains the following sections : • Consolidated ‘Business Planning Scenarios’ and ‘Opportunistic Events’ - the original business scenarios have been edited and categorised to provide a more comprehensive and easily understood set of scenarios and events, • Business requirements represented in the ‘Business Attribute Model’ - this contains all the business requirements to support an APS solution in MSD, and has been cross checked to the business scenarios

3. SCITe - Progress between end of functional team workshops and beginning of August • Initial interpretation of the information provided by the functional teams. The information from the functional teams has been analysed (1st cut) to try to build up a picture of each of the envelopes by supply chain function so that each envelope only builds the supply chain solution it requires, which acknowledges one of the underlying key messages that there will be different supply chain solutions for different envelopes/groups of envelopes, • Benefits consolidated by volume by envelope across the MAS categories and linked to SEOP cpb (established in the MAS) for SEOP envelopes and SOPE cpb (validated after the MAS) to SOPE envelopes, and • Risks consolidated from the issues logs, and split between risks to be considered as part of the 502, and issues which will need to be dealt with as part of the design and implementation phases of the project. • 3. The data management group has taken the Business Planning Scenarios, Business Attributes Model, Functional and Data Requirements produced by the Functional Teams as input in developing a Business Entity Model which specifies the ‘data cubes ’ie groups of data, which will be required to support improvements to the supply chain (either with or without the use of an APS tool). The group has also begun work on producing ‘dashboards’ for key supply chain functions, the technical architecture and support organisation, and the cost model required to support the new supply chain solution. • 4. A joint SEOP and SOPE MSD workshop has been held to validate, update and comment on work • done between the end of functional team phase and consolidation; and to challenge and make • suggestions about the way forward. These have been incorporated into a detailed action plan.

4. SCITe - Work to be completed from mid August to mid October • 1. Communication Activities(Now and Ongoing) • Regular monthly communications to go out to two stakeholder groups in MSD - OPE and Functional Teams • 2.SEOP Workshop (end August) • SEOP workshop to be held at end of August to : • Discuss and understand the business imperative/s for going ahead with the SCITe project, • Validate, update and sign off work done to date around business scenarios, requirements, benefits, and risks, • Gain buy-in to perform the envelope analysis to determine the type of supply chain solution required in each envelope • 3. Vision and Scope (end August through September) • Aim to have MSD aligned in the SCITe project by end of August. September will see much more involvement of the rest of the organisation. • 4. Business Scenarios & Business Requirements (end Aug to 21 Sep) • In order to be able to use the business scenarios and business requirements as input by an APS vendor when considering the software requirements to support the supply chain planning solution, to create test cases for the final solution, and as a base for developing prototypes and process design, the business scenarios need to be : • Validated by the business for completeness and checked to the Business Attributes Model to ensure all the business requirements from the business scenarios are reflected in the model

5. SCITe - Work to be completed from mid August to mid October • 5. Envelope Work (Beginning September to 21 September) • Build on existing envelope information to establish a supply chain planning solution across each supply chain function for each envelope and associate the benefits to be applied to each envelope. The solutions will be different for each envelope depending on which supply chain functions that envelope will need to support • Establish the process and organisation areas that will be impacted by the appropriate supply chain solution • 6. Benefits (Mid September to end September) • Carry out benefit assessment by envelope using the results from the envelopes • Split benefits by data, application, process and organisation by envelope • Link benefits realisation to time-phased implementation • 7. Risks (End September to mid October) • Assess the risks by envelope for size and probability of occurrence, and link to time-phased implementation • 8. Data Management (Kevin to complete) • 9. Construction of 502 (beginning October to mid October)