Scope, Prioritize, Budget, and Staff an SAP BW Implementation Project

Session Title

6Developer training should start early for all project team membersSAP R/3 skills are not easily transferable to BW; hands-on experience is needed (it is very hard to learn while being productive)Quality is much more important than the number of team membersA skilled BW developer can accomplish in one day what three novice developers can do in a week Timelines and Staffing Plan: Lessons Learned

7Project and cost estimates should be based on experience levelsPlan on formal knowledge-transfer from external resources from day one. Link inexperienced with the experienced members.Have identified go-to resources available in all areas (make a list)

Timelines and Staffing Plan: Lessons Learned (cont.)Don't underestimate the benefits of having strong developer skills on your team R/3 experience does not substitute for hands-on BW skills

3What Well Cover The project preparation phaseOrganizing your teamSetting and managing project scopeBudgeting and prioritizing effortsCustomization vs. standard contentIdeas for quick-hit implementationsThe drivers for your project and legacy systemsThe strategic planWrap-up

4

IntroductionPlanning an SAP BW project can be quite intimidating It is hard to decide where to start and how to scope, size, staff, and budget the projectYou also have to put processes in place that minimize the risks and leverage the standard content as much as possibleThis session will give you some ideas on how to approach the tasks of getting your BW project organized and create a strategic plan for your enterprise data warehouse

We will keep a rapid pace and give you real examples to illustrate the topics.5What Well Cover The project preparation phaseOrganizing your teamSetting and managing project scopeBudgeting and prioritizing effortsCustomization vs. standard contentIdeas for quick-hit implementationsThe drivers for your project and legacy systemsThe strategic planWrap-up

8Example: Small BW Project for Single Subject Area (e.g., Billing, Inventory, or Accounts Payable)4-5 team members and normally 3-6 months duration, depending on scopeBasis and functional R/3 supportThese are roles, not positions; (sometimes one team member can fill more than one role).Detailed role descriptions are included with this presentation on the take-home Conference CD

9Example: Mid-sized BW Project for Single Complex Subject Area (e.g., Cost and Profitability, Internal Billing)Basis and functional R/3 support

8-10 team members and normally 2-4 months duration depending on scopeThese are roles, not positions; (sometimes one team member can fill more than one role)10Example: Large BW Project for Multiple Subject Areas (e.g., Sales, Finance, and Material Management)Basis and functional R/3 support

15-25 team members and normally 6-18 months duration depending on scopePortal developer(s)BW ArchitectBusiness analyst/(sub-team lead)BW developerPresentation developer(s)ETL developerSales TeamBusiness analyst/(sub-team lead)BW developerPresentation developer(s)ETL developerFinance TeamBusiness analyst/(sub-team lead)BW developerPresentation developer(s)ETL developerMaterial Mgmt. TeamProject ManagerProject sponsor/Steering CommitteeThese are roles, not positions; (sometimes one team member can fill more than one role)11On-Boarding and TrainingIdeal Years Experience (minimum)Training days (if new in the role )In-house training daysBW Developer 2+153-5ETL Developer 3+15-203-5Presentation Developer 1+5-103-5Project Manager 5+10-153-5Business Analysts 5+5-103-5Dont underestimate the value of in-house, hands-on training in addition to formal SAP training classes


13

Why Use Change Control?Enforce consistency between business/process and development project plans (i.e., dates, case names)Ensure that previously approved scope is re-planned appropriatelyShows responsiveness and provides a forum for new requests

Accurate Resource PlanningReduces impact on other planned workStrategic staffing vs. reactive staffingMake best use of resources13Effectively manage requested changes to completed work by ensuring good decision making and strong follow through on action plans.

14Defining the Scope For the first Go-Live, keep the scope as simple as possible, in an area with solid standard BW content (i.e., Accounts Payable, Accounts Receivable, G/L, or COPA)You have only three dimensions to work with:If one of these dimensions changes, you have to adjust at least one of the others or the quality of your BW system will suffer

Caution14Basic documents on the source system side AP, Invoice, Order, Delivery are great places to start.R3 Finance content in BW is strong and fits most companies processes. Great place to startWho doesnt want to visibility to money earned/profitability and money spent/expensed. 15The Scope AgreementFirst, determine what the business drivers are and make sure you meet these objectives. Define the scope in terms of what is included, as well as what is not included. Make sure you obtain approval of the scope before you progress any further. All your work from now on will be driven based on what is agreed to at this stage.

Source: PMI15Base to build from is very important if you are building in phases.Help the business understand the growth potential.A dump into a warehouse does not give you visibility to much of anything. 16The Scope Agreement (cont.)As part of the written scope agreement, make sure you implement a formal change request process. This typically includes a cost-benefit estimate for each change request and a formal approval process.Change management is done to manage scope, timelines, and competing business requirements16Base to build from is very important if you are building in phases.Help the business understand the growth potential.A dump into a warehouse does not give you visibility to much of anything. 17Managing Scope The Change ControlDefine change (what is a change?)Establish procedures and when to use change processDocumentation Must be able to link to a requirement Description Timing and dependencies Test case and data availabilityEstablish procedures and when to use change processWork effort to complete developmentDate when available for testResource availabilityImpact to schedule Impact to existing development

BW is an integrated environment. Late changes in one area can have large impacts across the system17A proposed change to some aspect of the project (i.e.. requirements, rules, IDEFs, process flows, etc.) previously agreed upon and/or signed-off.Scope Change Material change to the project scope or integration business case that requires Executive or Board approval. (e.g. acquisition, divestiture, etc.)Design Change Any material change to an approved EDGE deliverable. (e.g. Approved to Not a fit, Proposed to Not a fit)New Requirement Request for new functionality.Program Milestone Change Request to change a committed milestone date.

Effectively manage requested changes to completed work by ensuring good decision making and strong follow through on action plans.

18Change Control Process Example

Change control processes should be formal, with escalation rules that can be used if disputes occur.This example is from a large SAP project that included R/3 and BW and needed strong scope control.

18After the cc meeting:Business/Process TracksAdd Functional Specification, Technical Specification, Code & Unit Test, and Acceptance Test tasks to project plan with Case NameUpdate Functional Specification with actual dateCoordinate with development tracks.Development tracksAdd Functional Specification, Technical Specification, Code & Unit Test, and Acceptance Test tasks to project plan with Case NameDetermine actual dates for Technical Specification and Code & Unit TestCoordinate with Business/Process tracks The date that technical specification and coding & unit test will be completedThe previously approved work that needs to be re-planned if anyAgree on final Acceptance Test dates and update project planBusiness/Process TracksUpdate Technical Specification, Code & Unit Test, and Acceptance Test tasks with actual datesCreate change control documents for work that needs to be re-planned if any

19Determining Scope Through a Release Plan

Plan multiple implementations and write a long-term outline that may change (using a formal change request process).

20Determining Scope Through a Release Plan (cont.)

21 Post this plan on the walls in the hallways. Don't hide it in the PM's office!

Keep it under 30 items!

Writing the Milestone PlanUse a milestone plan to illustrate dependencies and high-level tasks:

22Example: Infrastructure to Meet the Milestone Dates

In a complex project with multiple development environments and releases, it is important to have a well-communicated and detailed chart to make sure everyone is in-sync at all times


24Budgeting Process StepsWe will now take a look at how each of these steps can be done in practiceCreate the milestone plan and the scope statement first before attacking the budgeting process!Start the budgeting process by estimating the workload in terms of the development effortBudgeting Process Steps:Size the BW effort based on the scope Prioritize the effortMap the effort to the delivery schedulePlan for number of resources needed based on the scope, delivery schedule. and the effort

251. Size the BW Effort Based on the Scope (Real Example)

Remember that your sizing also has to be based on the teams experience and skill level

262. Prioritize the Effort

The next step is to prioritize and outline the effort on a strategic timelineMake sure your sponsor and the business community agree with your delivery schedule

273. Use Project Estimates and Timeline to Create Project Load PlanThere are 480 available work hours per project member per quarter. Knowing this, we can plan the number of team members we need.

284. Result: Good Input for the Staffing Costs and Planning Many companies plan a 60%-40% mix of internal and external resources for a first Go-Live. Also, most use $50-$90 per/hr for internal budgeting and $90-$170 per/hr for external resources.

Use this information to plan for training, on-boarding, and staffing:

This spike in resource needs is due to an overlap in the delivery schedule

Now might be a good time to review that decision 29What Well Cover The project preparation phaseOrganizing your teamSetting and managing project scopeBudgeting and prioritizing effortsCustomization vs. standard contentIdeas for quick-hit implementationsThe drivers for your project and legacy systemsThe strategic planWrap-up

30

* Rapidly improving contentStandard Content vs. CustomizationAll functional areas are not equally supported by strong standard BW business content. Some areas have so much you can leverage, others will require more enhancements depending on your requirements. The differences are often due to customization on the R/3 side by companies and/or industry solutions31Standard Content vs. Customization (cont.)Start gathering your requirements and break those down to data requirementsMap the data functional requirements against standard content (InfoCubes)Take the standard model of that InfoCube (provided by BW admin workbench), and add your additional data fields into the modelMap the new data fields to the source and hand the logical model to the BW developer

Do not remove fields from the standard cube, and do not rename objects (you will not be able to take advantage of current and future delivered queries and cockpits)32What Well Cover The project preparation phaseOrganizing your teamSetting and managing project scopeBudgeting and prioritizing effortsCustomization vs. standard contentIdeas for quick-hit implementationsThe drivers for your project and legacy systemsThe strategic planWrap-up

33Ideas for Quick-Hit BW ImplementationsLimit the first Go-Live to one source system (easier to source)Think about quick visibility to enterprise consolidated dataSome easy InfoCubes to implement (document level)Sales OrdersDeliveriesBillingAccounts receiveablesAccounts payablesGeneral ledgerPurchase ordersFor a quick-hit Go-Live, limit yourself to as much standard content as possible in areas that have high-impact

34Ideas for Quick-Hit BW Implementations (cont.)Keep the scope focused and use a simple approach: No functional or technical specs are used in this approach. The user acceptance session is used to refine requirements.Activate standard contentReview data quality issuesCreate 2-3 sample queriesLoad infocubeUser acceptance sessionRequest for modificationsIn-scope?RejectionIn-futurescope?Make enhancementsTestDeployYesNoNo


36Your Company's StrategyWhat are the drivers for the project?Why do you need visibility increase revenue, decrease expenses, increase competitive advantage (how? and how do you measure this?)Who are the companys customers what do they have in common? Who are their vendors (your competitors)? How can the companys customers be segmented? What changes are occurring in the customer base? Where is the company heading?The enterprise data warehouse should sets the stage for effective analysis of information to make strategic decisions and identify competitive advantages (proactive and not retroactive!)

37Your Company's Strategy (cont.)Typically the current state of Data Warehousing (DW) is a combination of centralized and decentralized resulting in inefficiencies Moving to a centralized DW should enable future projects to reduce costs by leveraging common hardware, standardizing on software, and leveraging a pool of technical resource (is your project a cost-saving project?)How can you provide information not data for decision making (KPIs?)38Your Company's Strategy (cont.)Is your company a low-cost provider, a research leader, a premium provider? The answer will drive what you should report on ...Is your company divesting or growing the business through mergers and acquisitions?The answer will drive how you prioritize the development The need for integrated, historical, and accessible data across the enterprise is key to a competitive advantage

39Your Company's Strategy (cont.)For example, project X provides an end-to-end BW solution that empowers decision making to help provide better customer service and deliveries to increase profitability How?Increased accuracy of reportsTimely information in an interactive, easy to use mannerStandardized reporting method and shared toolsAccess to enterprise-wide informationContinuous monitoring of KPIs; profitability and margin analysis The goal is to give users the information when they need it and in a format they understand so they can execute day-to-day decisions and be more productive40Why Build BW and R/3 at the Same Time?Leverage Resources The basis and the business knowledge is available at lower additional costsAvoid rework Avoid rework of standard content when the R/3 module is implemented. Many smaller configurations can be accommodated without impact to the project team. Consequently, if extensions are made without regards to the BW implementation, rework may be required.Building BW and R/3 at the same time is a challenge, but there are also benefits

40Know your usersWhat they haveversusWhat they wantversusWhat they need

You must minimize this impact with a proper training program, a sound development approach and with the business community having critical roles during every phase of the project.Know what BI tools you have, how to use them and what are there limitations prior to deployment.A wise person once remarked that: a paper airplane can be constructed with little fore thought...............but a jet airplane cannot.

Similarly, a small stovepipe application with only a handful of users can get by without a set of carefully planned and executed activities, but a BI application certainly cannot.

41Why Build BW and R/3 at the Same Time? (cont.)Cost avoidance Avoid creating ABAP and custom reports that is available in BW Project successWhile R/3 is optimized for transaction processing, BW is maximized for analysis and user access to the data. The available reports and features improve the the quality of user experience thereby increasing the projects likelihood of success.




42Why Build BW and R/3 at the Same Time? (cont.)Things to watch Usually the BW implementation starts by lagging 4-6 weeks behind the R/3 team in the Prep, Blueprint, and Realization phase. However, during the implementation phase, the BW and the R/3 team are both in-sync for the same Go-Live date. This lag allows the BW team to leverage the other teams work without having to sit idle for the first few weeks of the project. It also allows the R/3 team to focus on the processes instead of the data in the beginning of each phase.




43Retiring Legacy Reporting SystemsBuilding interim solutions while an implementation takes place is hard Interim reporting is expensive and the business need must be fully accessed and understood. However, if you must do this, be very careful. Duplicate reports leads to confusion and slow adoption.

Politics retool the legacy organization as soon as possible and develop advocates for the new tool set and process. You must involve legacy reporting groups to be successful.

Have a "sunset" plan for legacy reporting systems "burn the boats"43Significant work needed to keep legacy data and BW data in synch. Some data required by the Enterprise Reporting BW data model may not exist in the legacy source systems therefore preventing the affected business from being able to migrate to BW or at least realizing the entire value of a centralize/enterprise warehouse in BW.

Leverage the investment made through Enterprise Reporting in SAP BW, and long term reduce cost by retiring sector legacy data warehousing solutions.

Consolidation of data across the enterprise.

Standardization of the decision support toolset for the enterprise

Duplication of data, extract programs, . Cost of software, hardware, storage and communications.


45Writing the Strategic Plan for Your Enterprise Data WarehousesTable of ContentExecutive SummaryBackgroundStrategyMotivator of change (why?)As-is state of systems and reportingTo-be state of enterprise data warehouseBenefits of the enterprise data warehouseProposed scopeProposed architectureProposed rollout planProposed project organizationProposed support organizationResourcesInternal resource assessmentExternal resource assessmentTraining needsRecruitmentThe strategic plan should contain these sections:Vendor overview and /or selectionHardwareSoftwarePartnersBudgets Detailed budgetProposed funding approvalLimitations, Assumptions, and RisksReferences

46The Pitfalls of ManyFailure to break from as-is environmentTreating legacy systems as requirementsComparing and replicating old reports and system functionalityUnderestimating development effort of complex requirementsR/3 is different than most legacy systems, as is reportingFailing to understand sources of information. (i.e., sales reporting) can come from sales orders, deliveries, billings, A/R, G/L, or COPASingle SponsorLack of corporate ownership and executive buy-inNo succession plan and the Enterprise Data Warehouse often becomes an orphan

47The Pitfalls of Many (cont.)Failure to quickly disable legacy reporting systemsCreates competing systems, politics, and no real cost savingsRemoves urgency and creates slow user adaptationOverly complex architecture and lack of enforcing of standards

Technology is seldom the reason why EDWs fail; organization and strong leadership is paramount48The Living Strategy How to Make It Work A strategy is a living document that is subject to changeIt is not a one-time effort that is ignored after the first change (many create a strategy only to file it in a drawer)The strategy should be clearly communicated to all team members and the business communityChange control approvals are needed to make the strategic planning process work in reality

A periodic review should be scheduled (e.g., quarterly) to monitor how well the implementations follow the strategy49What Well Cover The project preparation phaseOrganizing your teamSetting and managing project scopeBudgeting and prioritizing effortsCustomization vs. standard contentIdeas for quick-hit implementationsThe drivers for your project and legacy systemsThe strategic planWrap-up

50Resources

SAP Planning Best Practices in Implementations, by George W. Anderson

The Complete Project management Office Handbook, by Gerard M. Hill

Waltzing With Bears: Managing Risk on Software Projects, by Tom Demarco & Timothy Lister

Mastering the SAP Business Information Warehouse, by Kevin McDonald, Andreas Wilmsmeier, David C. Dixon

51

7 Key Points to Take HomeWrite the business case around the areas of greatest benefit to your users. Do not use a shot-gun approach, but keep it focused.Define your scope in terms of what is included and state what is not includedEstablish a formal change control process that is well communicatedPlan your project based on the hours required for the effort and the project teams skill level

52

7 Key Points to Take Home (cont.)Establish milestone dates and map the work hours required to these datesMake sure you have a plan for retiring legacy reporting systemsEvaluate staffing and training models periodically53Your Turn!How to contact us:Joyce RedmonDr. Bjarne [email protected] [email protected]

Questions? dSAPersonnelStep 3Step 2Step 1PolicyQuality Assurance!Board of DirectorsPackagingGroup of unique namesPublicationsMail RoomCertificate TemplateReceivingOrganizational personRequirements Gathering(Scope Planning)Scope Change ControlProject Scope Statement(Scope Definition)Project Committment(Scope Verification)Project InitiationScope Management Processes! dSAPersonnelStep 3Step 2Step 1PolicyQuality Assurance!Board of DirectorsPackagingGroup of unique namesPublicationsMail RoomCertificate TemplateReceivingOrganizational personScope Change ControlRiskAssessmentAction ItemsRisk Management ProcessesBusiness Teams

Change Control DB

Make/review decision.

Identify change, evaluate need, and submit, if valid.

Tracks

PMC / ESCPMOEDGE Integration TeamTeam LeadTracks

Yes

Escalation Levels1. Team Lead2. Project Integration Team3. Project Management Org4. Project Management Council

Assign to responsible Track.

Operating Model Integration Team

PMC / PMOProject Integration TeamTeam LeadTracks

Change Control DB

Analyze request and estimate impacts.

Change Control DB

Tracks

Escalate request to next level in organization for decision/review.

Change Control DB

Execute action plans and close change request.

Change Control DB

Change Control DB

Identify change, evaluate need and assign to responsible Track.

Current scope of work?

Update to relevant release and notify Business. No further action at this time.

Change Control DB

No

Yes



Based onimpact, can a decision be made at this level?

No

Yes

Communicate resolution to Business.

Team LeadTracks

WouldBusiness like further review?

Change Control DB

Tracks

No

WBSWBSDLVAudit TrackData Mgmt TrackDevelopment TracksInfrastructure TrackOMD (Karl Plan)Prep TrackProcess TracksRelease MgmtTesting TrackTraining TrackVersion TeamsCommentsCritial Path Guidelines01 PrepX10 Proj InfrX05 Assess Proj InfrX15 Team ReadinessX05 Project Team TrainingX05 Define StrategyX10 Define Curriculum BlueprintX20 Stakehold MgmtX05 ID Exec SponsorsX10 Dev Exec Sponsor Engage PlanX15 Initiate Exec Sponsor Engage PlanX25 Bene RealizationX05 Create Bene Real PlanX40 Data Mgmt ScopeX05 Id Data Conv ScopeX10 Id Data Stnds ScopeX15 Id Master Data Mgmt ScopeX90 Phase ReviewX05 Review Proj Prep PhaseX02 Blueprint.05 Blueprint Phase PrepX05 Team ReadinessX10 Infrastr Design.X05 Define Landscape Topology DLVDXtbd06 Define Landscape Topology DetailX10 Define Sys Security Strategy DLVDXtbd11 Define Sys Security Strategy DetailX15 Define HW Reqmts DLVDXtbd16 Define HW Reqmts DetailX20 Define SW Reqmts DLVDXtbd21 Define SW Reqmts DetailX25 Define Archiving Strategy DLVDXtbd26 Define Archiving Strategy DetailX30 Define Sizing Reqmts DLVDXtbd31 Define Sizing Reqmts DetailX15 Biz Process Design.X05 Review Id Refine ReqmtsX10 Document Int Scenarios DLVDXEOB - 55 days11 Document Int Scenarios DetailX15 Dev Design Doc.X05 Approve Scope and Design TeamX10 Dev Design Approach DLVDX05 Scope and Reqmts 1-3aXEOB - 50 days10 Recommendation 1-3bXEOB - 55 days15 Conduct Prelim ReviewX20 Refine Design Approach 1-3X25 Approve Design Approach 1-3XEOB - 50 days15 Deep Dive Workshop.XEOB - 45 days05 Prep for Deep DiveX10 Conduct Deep DiveX20 Design Doc Fit Gap.X05 Assess Business FitX10 Propose Solution or GapX15 Estimate PRICEFsX30 Complete Design Doc DLVDX10 Document Sections 4 6-9XEOB - 40 days15 Document Section 5XEOB - 35 days20 Signoff Sections 4 - 9XEOB - 30 days20 Scenario Design.X05 Update Reqmts DLVDXEOB - 40 days06 Update Reqmts DetailX10 Scenario Fit Gap DLVDXEOB - 35 days05 Assess Business FitX10 Propose Solution or GapX15 Estimate PRICEFsX15 Scenario Docs.X05 Update IDEF and Flows DLVDXEOB - 30 days06 Update IDEF and Flows DetailX10 Update Audit Controls DLVDXEOB - 30 days11 Update Audit Controls DetailX15 Update Biz Rules DLVDXEOB - 30 days16 Update Biz Rules DetailX20 Update Org Impacts DLVDXEOB - 30 days21 Update Org Impacts DetailX25 Update KPI Defn DLVDXEOB - 30 days26Update KPI Defn DetailX30 Update SAP Org Hierarchy DLVDXEOB - 30 days31 Update SAP Org Hierarchy DetailX35 Define Data Design Impact DLVDXEOB - 30 days36 Define Data Design Impact DetailX40 Define Security Roles DLVDXEOB - 30 days41 Define Security Roles DetailX45 Define Data Conv Impacts DLVDXEOB - 30 days46 Define Data Conv Impacts DetailX50 Define MDM Process Impact DLVDXEOB - 30 days51 Define MDM Process Impact DetailX25 Master Data Design.X05 Consol Data ImpactsX10 Data Fit GapX15 Cross Functional ReviewX20 Define Baseline Master Data Design DLVDXEOB - 25 days21 Define Baseline Master Data Design detailX25 Define Baseline Data Stnds DLVDXEOB - 25 days26 Define Baseline Data Stnds DetailX30 Integrate Designs.X05 Integrate Design Documents.X05 Create Design Doc Summary DLVDXEOB - 25 days06 Create Design Doc Summary DetailX10 Signoff Int Design Docs DLVDXEOB - 20 days11 Signoff Int Design Docs DetailX10 Document Cases Cond DLVDXEOB - 15 days11 Document Cases Cond DetailX15 Document Proto Data Reqmts DLVDXEOB - 15 days16 Document Proto Data Reqmts DetailX35 Prioritize PRICEFs DLVDXEOB - 15 days05 Consolidate PRICEFsX10 Propose Initial Dev ScopeX20 Data Conversion Design.X05 Update Conv StrategyX10 Draft Conv Approach DLVDXEOB - 15 days11 Draft Conv Approach DetailX15 Draft Collection PlanX25 Org Design.X10 Design To Be Org Structure DLVDXtbd11 Design To Be Org Structure DetailX15 Design Roles and Resp DLVDXtbd16 Design Roles and Resp DetailX20 Design Perform Measures DLVDXtbd21 Design Perform Measures DetailX25 Design Work Groups DLVDXtbd26 Design Work Groups DetailX30 Design Integrating Mechanisms DLVDXtbd31 Design Integrating Mechanisms DetailX35 Validate To Be Org Design DLVDXtbd36 Validate To Be Org Design DetailX40 Develop Org Transition Plan DLVDXtbd41 Develop Org Transition Plan DetailX30 Stakeholder Mgmt.X05 Execute Exec Sponsor Engage PlanX10 Develop Impl Network Engage Plan DLVDXtbd11 Develop Impl Network Engage Plan DetailX15 Execute Impl Network Engage PlanX20 Develop Power User Plan DLVDXtbd21 Develop Power User Plan DetailX25 Checkpoint Exec Sponsor Engagement DLVDXtbd26 Checkpoint Exec Sponsor Engagement DetailX35 Change Management.X05 Execute Awareness CommunicationsX10 Conduct HR Site Coordinator Meeting DLVDXtbd11 Conduct HR Site Coordinator Meeting DetailX15 Conduct Roadshows Facility Visits DLVDXtbd16 Conduct Roadshows Facility Visits DetailX20 Conduct Readiness Assessment DLVDXtbd21 Conduct Readiness Assessment DetailX40 End User Training.X05 Design Curriculum DLVDXEOB - 30 days06 Design Curriculum DetailX10 Develop Course Outlines DLVDXEOB - 5 days11 Develop Course Outlines DetailX45 Bene Realization.X05 Assess Benefits PlanX10 Update Benefits PlanX55 Business Design Validation DLVDXEOB - 10 days05 Prepare for ValidationX10 Conduct Validation WorkshopX60 Build Realization Infrastructure.X05 Construct Sandbox Syst DLVDXEOB - 10 days06 Construct Sandbox Syst DetailX10 Construct Dev Syst DLVDXEOB - 5 days11 Construct Dev Syst DetailX60 Test Strat DesignX05 Define Test StratX70 Develop Realization Plan DLVDXEOB - 5 days05 Refine Version CharterX10 Develop Realization Work PlanXXXXX15 Refine Business Resource EstimatesXX90 QA and Integration Reviews.X05 Conduct Mid Blueprint Integration Rev DLVDXdepends on timing of phase07 Conduct Mid Blueprint Integration Rev detailX10 Conduct End Blueprint Integration Rev DLVDXend of blueprint (EOB)12 Conduct End Blueprint Integration Rev detailX15 Conduct Phase End Review DLVDXend of blueprint (EOB)17 Conduct Phase End Review detailX03 Realization.05 Realization PrepXX05 Project Team TrainingXX10 IT Construction.X05 Conduct Facility Site SurveyDX10 Id New SAP Users by NameDX15 Refine Facility Scope of WorkDX20 Ensure Connectivity of Addl AppsDX25 Incorp New Apps into Change MgmtDX30 Id Batch Jobs and ScheduleDX35 Build Test EnvironmentsDX40 Build Training EnvironmentsDX45 Id HA DA RequirementsDX50 ID App Monitoring ReqmtsDX55 Order Facility EquipmentDX60 Obtain Updated SLA ReqmtsDX71 Define SLAsDX72 Establ Sys Admin FunctionsDX73 Impl Security StratDX74 Construct Prod SystDX15 Dev Case Solution XLV.XXXData track for MDM, Versions for interim processes05 Prototype Cycle 1.XXX10 Prep Case DLVDXXXPrototype cycle 1 end date - 10 days05 Prep Case DetailXXX15 Execute Proto Case DLVDXXXPrototype cycle 1 end date - 5 days10 Config ESBXXX15 Config EDVXXX20 Prototype Config DetailXXX20 Update Design Docs DLVDXXXPrototype cycle 1 end date05 Task FlowsXXX10 Config DocsXXX15 ASAPXXX20 Audit ControlsXXX25 OtherXXX25 Update Data Design DLVDXXXPrototype cycle 1 end date05 Master Data DesignXXX10 Data StandardsXXX30 Functional Specs.05 Portals DLVDXPrototype cycle 1 end date07 Portal DetailXXXX10 Reports DLVDXPrototype cycle 1 end date12 Report DetailXXXX15 Interfaces DLVDXPrototype cycle 1 end date17 Interface DetailXXXX25 Enhancements DLVDXPrototype cycle 1 end date27 Enhancement DetailXXXX30 Forms DLVDXPrototype cycle 1 end date32 Form DetailXXXX35 Cube DLVDXPrototype cycle 1 end date37 Cube DetailXXXX40 Query DLVDXPrototype cycle 1 end date42 Query DetailXXXX10 Prototype Cycle 2.XXX10 Prep Case DLVDXXXPrototype cycle 2 end date - 10 days05 Prep Case DetailXXX15 Execute Proto Case DLVDXXXPrototype cycle 2 end date - 5 days10 Config ESBXXX15 Config EDVXXX20 Prototype Config DetailXXX20 Update Design Docs DLVDXXXPrototype cycle 2 end date05 Task FlowsXXX10 Config DocsXXX15 ASAPXXX20 Audit ControlsXXX25 OtherXXX25 Update Data Design DLVDXXXPrototype cycle 2 end date05 Master Data DesignXXX10 Data StandardsXXX30 Functional Specs.05 Portals DLVDXPrototype cycle 2 end date07 Portal DetailXXX10 Reports DLVDXPrototype cycle 2 end date12 Report DetailXXX15 Interfaces DLVDXPrototype cycle 2 end date17 Interface DetailXXX25 Enhancements DLVDXPrototype cycle 2 end date27 Enhancement DetailXXX30 Forms DLVDXPrototype cycle 2 end date32 Form DetailXXX35 Cube DLVDXPrototype cycle 2 end date37 Cube DetailXXX40 Query DLVDXPrototype cycle 2 end date42 Query DetailXXX15 Prototype Cycle 3.10 Prep Case DLVDXXXPrototype cycle 3 end date - 10 days05 Prep Case DetailXXX15 Execute Proto Case DLVDXXXPrototype cycle 3 end date - 5 days10 Config ESBXXX15 Config EDVXXX20 Prototype Config DetailXXX20 Update Design Docs DLVDXXXPrototype cycle 3 end date05 Task FlowsXXX10 Config DocsXXX15 ASAPXXX20 Audit ControlsXXX25 OtherXXX25 Update Data Design DLVDXXXPrototype cycle 3 end date05 Master Data DesignXXX10 Data StandardsXXX30 Functional Specs.05 Portals DLVDXPrototype cycle 3 end date07 Portal DetailXXX10 Reports DLVDXPrototype cycle 3 end date12 Report DetailXXX15 Interfaces DLVDXPrototype cycle 3 end date17 Interface DetailXXX25 Enhancements DLVDXPrototype cycle 3 end date27 Enhancement DetailXXX30 Forms DLVDXPrototype cycle 3 end date32 Form DetailXXX35 Cube DLVDXPrototype cycle 3 end date37 Cube DetailXXX40 Query DLVDXPrototype cycle 3 end date42 Query DetailXXX20 Technology Development.07 Tech Specs.05 Portals DLVDXObject type Code/Unit date - 5 days07 Portal DetailX10 Reports DLVDXObject type Code/Unit date - 5 days12 Report DetailX15 Interfaces DLVDXObject type Code/Unit date - 5 days17 Interface DetailX25 Enhancements DLVDXObject type Code/Unit date - 5 days27 Enhancement DetailX30 Forms DLVDXObject type Code/Unit date - 5 days32 Form DetailX35 Cube DLVDXObject type Code/Unit date - 5 days37 Cube DetailX40 Query DLVDXObject type Code/Unit date - 5 days42 Query DetailX10 Code and Unit Test.X05 Portals DLVDXObject type Accept Test date - 5 days07 Portal DetailX10 Reports DLVDXObject type Accept Test date - 5 days12 Report DetailX15 Interfaces DLVDXObject type Accept Test date - 5 days17 Interface DetailX25 Enhancements DLVDXObject type Accept Test date - 5 days27 Enhancement DetailX30 Forms DLVDXObject type Accept Test date - 5 days32 Form DetailX35 Cube DLVDXObject type Accept Test date - 5 days37 Cube DetailX40 Query DLVDXObject type Accept Test date - 5 days42 Query DetailX20 Accept Test and Migrate.05 Portals DLVDXXXIUT start date - 5 days07 Portal DetailX10 Reports DLVDXXXSys Test Cycle 1 start date - 5 days12 Report DetailX15 Interfaces DLVDXXXIUT start date - 5 days17 Interface DetailX25 Enhancements DLVDXXXIUT start date - 5 days27 Enhancement DetailX30 Forms DLVDXXXIUT start date - 5 days32 Form DetailX35 Cube DLVDXXXIUT start date - 5 days37 Cube DetailX40 Query DLVDXXXSys Test Cycle 1 start date - 5 days42 Query DetailX25 End User Doc Development.XXX05 Work Instruction DLVDXXXCase Accept Test - 5 days07 Work Instruction DetailXXX10 User Procs DLVDXXXCase Accept Test - 5 days12 User Procs DetailXXX15 Compliance Assess DLVDXXXCase Accept Test - 5 days17 Compiance Assess DetailXXX20 Biz Continuity Procs DLVDXXXCase Accept Test - 5 days22 Biz Continuity Procs DetailXXX30 Case Acceptance Test.XXX05 Case Accept Test DLVDXXXSys Test Cycle 1 start date - 5 days07 Case Accept Test DetailXXX20 Manage Prototyping.05 Cycle 1.05 Prep Proto Cycle 1XXX05 Build Cycle 1 CasesXXX10 Define Proto Master Data Reqd DLVDXXXProto cycle 1 start date + 5 days12 Define Proto Master Data Reqd detailXXX15 Collect Prot Master Data DLVDXProto cycle 1 start date + 10 days17 Collect Prot Master Data detailX20 Load Proto Master Data DLVDXProto cycle 1 start date + 15 days22 Load Proto Master Data detailX10 Walkthrough Cycle 1X05 Define Walkthru Master Data ReqdXX10 Collect Walkthru Master DataXX15 Load Walkthru Master DataX25 Prep WalkthroughXX30 Exec WalkthroughXX35 Review ResultsXX10 Cycle 2.XXX05 Prep Proto Cycle 2.XXX05 Build Cycle 1 CasesXXX10 Define Proto Master Data Reqd DLVDXXXProto cycle 2 start date + 5 days12 Define Proto Master Data Reqd detailXXX15 Load Proto Master Data DLVDXProto cycle 2 start date + 10 days17 Load Proto Master Data detailX10 Walkthrough Cycle 2XX05 Define Walkthru Master Data ReqdXX10 Collect Walkthru Master DataXX15 Load Walkthru Master DataX25 Prep WalkthroughXX30 Exec WalkthroughXX35 Review ResultsXX15 Cycle 3.XXX05 Prep Proto Cycle 3.XXX05 Build Cycle 1 CasesXXX10 Define Proto Master Data Reqd DLVDXXXProto cycle 3 start date + 5 days12 Define Proto Master Data Reqd detailXXX15 Load Proto Master Data DLVDXProto cycle 3 start date + 10 days17 Load Proto Master Data detailX10 Walkthrough Cycle 3XX05 Define Walkthru Master Data ReqdXX10 Collect Walkthru Master DataXX15 Load Walkthru Master DataX25 Prep WalkthroughXX30 Exec WalkthroughXX35 Review ResultsXX20 Maintain Master DataX91 Maintain Proto Master Data - Cycle 1X92 Maintain Proto Master DataX93 Maintain Proto Master DataX94 Maintain Walkthru Master DataX95 Maintain Walkthru Master Data - 2X96 Maintain Walkthru Master DataX25 Integrated Unit Test.05 Plan IUT DLVDXXIUT start date - 10 days07 Plan IUT detailXX10 Define IUT Data Reqmts DLVDXXIUT start date - 5 days12 Define IUT Data Reqmts detailXX15 Load IUT Data DLVDXIUT start date17 Load IUT Data detailX20 Execute IUT CasesXX25 Support IUT ExecutionXX30 End User Security.XX05 Design Activity Roles DLVDXXSys Test cycle 1 start date - 10 days10 Design Activity Roles DetailXX15 Unit Test Activity Roles DLVDXXSys Test cycle 1 start date - 5 days20 Unit Test Activity Roles DetailXX35 Data Conversion.X05 Data Conv Plan.X05 Final Conv Approach DLVDX07 Final Conv Approach DetailX10 Final Data Collection Plan DLVDX12 Final Data Collection Plan DetailX15 Develop Conv Execution Plan DLVDX17 Develop Conv Execution Plan DetailX10 Data Conv Quality.X05 Collect Data IterativeX10 Assess Data QualityX15 Plan Data ImprovementsX25 Perform Data ImproveX30 Dev DQ Verification Rules DLVDX35 Dev DQ Verifiation Rules DetailX40 Define Validation Procs Tech DLVDX45 Define Validation Procs Tech DetailX50 Define Validation Procs Content DLVDX55 Define Validation Procs Content DetailX20 Data Conv Dev.X05 Funct Specs DLVDXSys Test cycle 1 mock conversion - 20 days10 Funct Specs DetailX15 Tech Specs DLVDXSys Test cycle 1 mock conversion - 15 days20 Tech Specs DetailX25 Code Unit Test DLVDXSys Test cycle 1 mock conversion - 10 days30 Code Unit Test DetailX35 Accept Test DLVDXSys Test cycle 1 mock conversion - 5 days40 Accept Test DetailX40 Data StndsX05 Final Master Data DesignX15 Final Data StndsX45 System Test.05 System Test Cycle 1.05 Plan Sys Test DLVDXXXSystem test cycle 1 start date07 Plan Sys Test DetailXXX10 Conduct Mock Conv DLVDXXSystem test cycle 1 start date12 Conduct Mock Conv detailXX15 Execute Syst Test CasesXXX20 Support Sys Test ExecutionXXX10 System Test Cycle 2.05 Plan Sys Test DLVDXXXSystem test cycle 2 start date07 Plan Sys Test DetailXXX10 Conduct Mock Conv DLVDXXSystem test cycle 2 start date12 Conduct Mock Conv detailXX15 Execute Syst TestXXX20 Support Sys Test ExecutionXXX50 Change Mgmt.X05 Conduct End User Readiness AssessmentX10 Conduct Learning Map WorkshopsX15 Conduct Facility Funct Group RoadshowsX20 Conduct Role Discussion Managers' MeetingX25 Conduct Weekly LT Conf CallsX30 Develop Customer Facing Change PlanX35 Develop Facility Change PlanX40 Develop Responses to 6 Critical QuestionsX45 Develop Sector/Business Change PlanX50 Develop Support Group Change PlanX55 Devleop Role Discussion GuideX60 Document New Roles & ResponsibilitesX65 Map Stakeholders to Training CurriculumX70 Review Roles & Responsibilities with StakeholdersX75 Transition from Change to TrainingX99 Change Understand Accept ActivitiesX99 Conduct Readiness Assessment SurveyX99 Dev Change ModelX99 Dev Sector Change PlanX99 Monitor Change Plan ExecutionX99 Rollout Change PlansX55 Training Dev.X05 Dev Training Matls.X05 Draft A DLVDX07 Draft A DetailX10 Draft B DLVDX12 Draft B DetailX15 Draft C DLVDX17 Draft C DetailX10 Prepare Training Environment.X05 Define Training Master Data Required DLVDX07 Define Training Master Data Required detailX10 Load Training Master Data DLVDX12 Load Training Master Data detailX15 Test TrainingX05 Conduct Dry RunsX10 Train the TrainerX15 Conduct Pilot CoursesX20 Maintain Training EnvironmentX05 Maintain Training Master DataX10 Maintain Training Environment ConfigX60 Post Impl Supp Design.X05 Setup HelpdeskX10 Define Sustain StrategyX15 Refine Prod Support RolesX65 Cutover Planning.X05 Plan CutoverX70 Bene Realization.X05 Review Benefits Realization PlanX10 Update Benefits PlanX75 Stakehold Mgmt.X05 Execute Exec Sponsor Engage PlanX10 Checkpoint Sponsor Engagement DLVDXmanually determined15 Execute Impl Network Engage PlanX20 Checkpoint Implementation Network DLVDXmanually determined80 Power User Mgmt.X05 Execute Power User PlanX10 Id Power Users DLVDX12 Id Power Users detailX15 Communicate Power User Resource Needs DLVDX17 Communicate Power User Resource Needs detailsX20 Conduct Conf Call with Power User Mgrs DLVDX22 Conduct Conf Call with Power User Mgrs detailX90 QA and Integration Rev.XXXXXX05 Mid Point Review DLVDXXXXXXmanually determined07 Mid Point Review detailXXXXXX10 End of Phase Integration Review DLVDXXXXXXend of realization12 End of Phase Integration Review detailXXXXXX15 Phase Compl Review DLVDXXXXXXend of realization17 Phase Compl Review detailXXXXXX04 Final Prep.X05 Phase PrepX10 Technical Infrastructure.X05 Install Facility EquipmentDX15 Burn In Period for FacilityDX20 Communicate Help Desk ProcessX25 Finalize Revised SLAX15 Integration Test.X05 Int Test Cycle 1.X05 Plan Integration Test DLVDX07 Plan Integration Test DetailX10 Conduct Mock Conversion DLVDXX12 Conduct Mock Conversion detailXX15 Execute Integration Test CasesX20 Support Integration Test ExecutionXXX10 Int Test Cycle 2.X05 Plan Integration Test DLVDX07 Plan Integration Test DetailX10 Conduct Mock Conversion DLVDXX12 Conduct Mock Conversion detailXX15 Execute Integration Test CasesX20 Support Integration Test ExecutionXXX20 End User Training.X05 Deliver End User TrainingX10 Evaluate Training EffectivenessX15 Maintain Training EnvironmentXX05 Maintain Training Master DataX10 Maintain Training Environment ConfigurationX25 Change Management.X05 Execute Change PlanX10 Checkpoint Change Plan Execution DLVDXmanually determined15 Conduct User Readiness Assessment DLVDX17 Conduct User Readiness Assessment detailX30 Finalize Post Impl Support.X05 Setup HelpdeskX10 Define Sustain StratX15 Refine Prod Support RolesX35 Data Conversion.XX05 Transition Conv Plan to CutoverXX10 Final Data CollectionXX15 Execute Dual MaintenanceXX40 Bene Realization.X05 Establish BaselineX10 Assess BeneX15 Update Bene PlanX20 Present Bene FindingsX45 Stakeholder Mgmt.X05 Execute Exec Sponsor Engage PlanX10 Execute Impl Network Engage PlanX15 Xfer Ownership to Impl NetworkX20 Develp Plan for Go LiveX50 Cutover.X05 Refine Cutover Plans and ProcX10 Refine Go Live PlanX15 Load Go Live Data DLVDX17 Load Go Live Data detailX20 Cutover to Prod EnvironX25 Approve Go LiveX90 QA and Integration Reviews.XXX05 Mid Phase Integration Review DLVDXXXmanually determined07 Mid Phase Integration Review detailXXX10 End Phase Integration Review DLVDXXXend of final prep phase12 End Phase Integration Review detailXXX15 Final Prep Completion Review DLVDXXXend of final prep phase17 Final Prep Completion Review detailXXX05 Go Live and SupportX10 End User TrainingXX05 Deliver Post Go Live End User TrainXX15 Monitor Change PlansX20 Exec Stakeholder Mgmt ProgramX25 Org TransitionX05 Support Org Go Live ActivitiesX30 Implement Post Impl SupportX05 Provide Go Live SupportX35 Go Live Transition and Knowledge TransferX05 Finalize People Proc TransitionX10 Finalize Biz Proc TransitionX15 Finalize Info Tech TransitionX20 Perform Bene Accountability Transition to Biz OwnersX40 Go Live Review Sign Off and HandoverX05 Go Live Review Sign Off and HandoverX90 Go Live and Support ReviewX05 Review Go Live and Support DLVX07 Review Go Live and Support detailX09 Project MgmtXXXXXXX05 Track Project StatusXXXXXXX10 Manage Project Issues and ProblemsXXXXXXX15 Manage Risk PlanXXXXXXX20 Manage Project CharterXXXXXXX91 AdministrationXXXXXXX05 Non EDGE ActivitiesXXXXXXX10 Time OffXXXXXXX

&C&"Arial,Bold"EDGEWBS Work Plan Usage&CPage &P of &N&R&D&T

Critical Path - SummaryMilestonesV1 Wave 2V1 Wave 3V1 Wave 4V2 Wave 1V3 Wave 1V4 Wave 1Fiber SupplyBlueprintEnd of Blueprint11/1/0411/1/042/4/052/25/052/25/056/10/051/30/05RealizationStart of Prototype Cycle 110/18/0410/18/0412/27/043/21/05End of Prototype Cycle 111/12/0411/12/042/11/055/20/05Start of Prototype Cycle 210/18/0411/15/042/14/055/23/05End of Prototype Cycle 211/12/041/28/054/8/057/22/05Start of Integrated Unit Test11/15/041/31/054/11/057/25/05End of Integrated Unit Test12/10/043/4/055/13/058/26/05Start of System Test Cycle 112/13/043/7/056/13/0510/3/05End of System Test Cycle 11/28/044/29/057/29/0511/18/05Final PrepStart of Integration Test Cycle 11/31/055/2/058/1/0511/28/05End of Integration Test Cycle 13/11/056/3/059/2/051/6/06Start of Integration Test Cycle 26/6/059/5/051/9/06End of Integration Test Cycle 27/8/059/30/052/3/06Go Live4/1/058/1/0510/31/053/1/06

&C&"Arial,Bold"EDGEImplementation Summary Milestones&CPage &P of &N&R&D&T

Critical Path - DLVWBSDLVEstimating ApproachV1 Wave 2V1 Wave 3V1 Wave 4V2 Wave 1V3 Wave 1V4 Wave 1Fiber Supply02 Blueprint.10 Infrastr Design.05 Define Landscape Topology DLVDtbd10 Define Sys Security Strategy DLVDtbd15 Define HW Reqmts DLVDtbd20 Define SW Reqmts DLVDtbd25 Define Archiving Strategy DLVDtbd30 Define Sizing Reqmts DLVDtbd15 Biz Process Design.10 Document Int Scenarios DLVDEOB - 55 days8/16/048/16/0411/19/0412/10/0412/10/043/25/0511/14/0415 Dev Design Doc.10 Dev Design Approach DLVDEOB - 50 days8/23/048/23/0411/26/0412/17/0412/17/044/1/0511/21/0415 Deep Dive Workshop.20 Design Doc Fit Gap.30 Complete Design Doc DLVDEOB - 35 days9/13/049/13/0412/17/041/7/051/7/054/22/0512/12/0420 Scenario Design.05 Update Reqmts DLVDEOB - 45 days8/30/048/30/0412/3/0412/24/0412/24/044/8/0511/28/0410 Scenario Fit Gap DLVDEOB - 40 days9/6/049/6/0412/10/0412/31/0412/31/044/15/0512/5/0415 Scenario Docs.05 Update IDEF and Flows DLVDEOB - 35 days9/13/049/13/0412/17/041/7/051/7/054/22/0512/12/0410 Update Audit Controls DLVDEOB - 35 days9/13/049/13/0412/17/041/7/051/7/054/22/0512/12/0415 Update Biz Rules DLVDEOB - 35 days9/13/049/13/0412/17/041/7/051/7/054/22/0512/12/0420 Update Org Impacts DLVDEOB - 35 days9/13/049/13/0412/17/041/7/051/7/054/22/0512/12/0425 Update KPI Defn DLVDEOB - 35 days9/13/049/13/0412/17/041/7/051/7/054/22/0512/12/0430 Update SAP Org Hierarchy DLVDEOB - 35 days9/13/049/13/0412/17/041/7/051/7/054/22/0512/12/0435 Define Data Design Impact DLVDEOB - 35 days9/13/049/13/0412/17/041/7/051/7/054/22/0512/12/0440 Define Security Roles DLVDEOB - 35 days9/13/049/13/0412/17/041/7/051/7/054/22/0512/12/0445 Define Data Conv Impacts DLVDEOB - 35 days9/13/049/13/0412/17/041/7/051/7/054/22/0512/12/0450 Define MDM Process Impact DLVDEOB - 35 days9/13/049/13/0412/17/041/7/051/7/054/22/0512/12/0425 Master Data Design.20 Define Baseline Master Data Design DLVDEOB - 20 days10/4/0410/4/041/7/051/28/051/28/055/13/051/2/0525 Define Baseline Data Stnds DLVDEOB - 5 days10/25/0410/25/041/28/052/18/052/18/056/3/051/23/0530 Integrate Designs.05 Integrate Design Documents.05 Create Design Doc Summary DLVDEOB - 25 days9/27/049/27/0412/31/041/21/051/21/055/6/0512/26/0410 Signoff Int Design Docs DLVDEOB - 20 days10/4/0410/4/041/7/051/28/051/28/055/13/051/2/0510 Document Cases Cond DLVDEOB - 15 days10/11/0410/11/041/14/052/4/052/4/055/20/051/9/0515 Document Proto Data Reqmts DLVDEOB - 15 days10/11/0410/11/041/14/052/4/052/4/055/20/051/9/0535 Prioritize PRICEFs DLVDEOB - 15 days10/11/0410/11/041/14/052/4/052/4/055/20/051/9/0520 Data Conversion Design.10 Draft Conv Approach DLVDEOB - 20 days10/4/0410/4/041/7/051/28/051/28/055/13/051/2/0525 Org Design.10 Design To Be Org Structure DLVDtbd15 Design Roles and Resp DLVDtbd20 Design Perform Measures DLVDtbd25 Design Work Groups DLVDtbd30 Design Integrating Mechanisms DLVDtbd35 Validate To Be Org Design DLVDtbd40 Develop Org Transition Plan DLVDtbd30 Stakeholder Mgmt.10 Develop Impl Network Engage Plan DLVDtbd20 Develop Power User Plan DLVDtbd25 Checkpoint Exec Sponsor Engagement DLVDtbd35 Change Management.10 Conduct HR Site Coordinator Meeting DLVDtbd15 Conduct Roadshows Facility Visits DLVDtbd20 Conduct Readiness Assessment DLVDtbd40 End User Training.05 Design Curriculum DLVDEOB - 30 days9/20/049/20/0412/24/041/14/051/14/054/29/0512/19/0410 Develop Course Outlines DLVDEOB - 5 days10/25/0410/25/041/28/052/18/052/18/056/3/051/23/0545 Bene Realization.55 Business Design Validation DLVDEOB - 10 days10/18/0410/18/041/21/052/11/052/11/055/27/051/16/0560 Build Realization Infrastructure.05 Construct Sandbox Syst DLVDEOB - 10 days10/18/0410/18/041/21/052/11/052/11/055/27/051/16/0510 Construct Dev Syst DLVDEOB - 5 days10/25/0410/25/041/28/052/18/052/18/056/3/051/23/0570 Develop Realization Plan DLVDEOB - 5 days10/25/0410/25/041/28/052/18/052/18/056/3/051/23/0590 QA and Integration Reviews.05 Conduct Mid Blueprint Integration Rev DLVDdepends on timing of phase10 Conduct End Blueprint Integration Rev DLVDend of blueprint (EOB)11/1/0411/1/042/4/052/25/052/25/056/10/051/30/0515 Conduct Phase End Review DLVDend of blueprint (EOB)11/1/0411/1/042/4/052/25/052/25/056/10/051/30/0503 Realization.10 IT Construction.05 Conduct Facility Site SurveyDtbd10 Id New SAP Users by NameDtbd15 Refine Facility Scope of WorkDtbd20 Ensure Connectivity of Addl AppsDtbd25 Incorp New Apps into Change MgmtDtbd30 Id Batch Jobs and ScheduleDtbd35 Build Test EnvironmentsDtbd40 Build Training EnvironmentsDtbd45 Id HA DA RequirementsDtbd50 ID App Monitoring ReqmtsDtbd55 Order Facility EquipmentDtbd60 Obtain Updated SLA ReqmtsDtbd71 Define SLAsDtbd72 Establ Sys Admin FunctionsDtbd73 Impl Security StratDtbd74 Construct Prod SystDtbd15 Dev Case Solution XLV.05 Prototype Cycle 1.10 Prep Case DLVDPrototype cycle 1 end date - 10 days10/29/0410/29/041/28/055/6/0515 Execute Proto Case DLVDPrototype cycle 1 end date - 5 days11/5/0411/5/042/4/055/13/0520 Update Design Docs DLVDPrototype cycle 1 end date11/12/0411/12/042/11/055/20/0525 Update Data Design DLVDPrototype cycle 1 end date11/12/0411/12/042/11/055/20/0530 Functional Specs.05 Portals DLVDPrototype cycle 1 end date11/12/0411/12/042/11/055/20/0510 Reports DLVDPrototype cycle 1 end date11/12/0411/12/042/11/055/20/0515 Interfaces DLVDPrototype cycle 1 end date11/12/0411/12/042/11/055/20/0525 Enhancements DLVDPrototype cycle 1 end date11/12/0411/12/042/11/055/20/0530 Forms DLVDPrototype cycle 1 end date11/12/0411/12/042/11/055/20/0535 Cube DLVDPrototype cycle 1 end date11/12/0411/12/042/11/055/20/0540 Query DLVDPrototype cycle 1 end date11/12/0411/12/042/11/055/20/0510 Prototype Cycle 2.10 Prep Case DLVDPrototype cycle 2 end date - 10 days10/29/041/14/053/25/057/8/0515 Execute Proto Case DLVDPrototype cycle 2 end date - 5 days11/5/041/21/054/1/057/15/0520 Update Design Docs DLVDPrototype cycle 2 end date11/12/041/28/054/8/057/22/0525 Update Data Design DLVDPrototype cycle 2 end date11/12/041/28/054/8/057/22/0530 Functional Specs.05 Portals DLVDObject type Tech Spec date - 5 days10/18/041/3/053/14/056/27/0510 Reports DLVDObject type Tech Spec date - 5 days11/15/042/7/055/16/059/5/0515 Interfaces DLVDObject type Tech Spec date - 5 days10/18/041/3/053/14/056/27/0525 Enhancements DLVDObject type Tech Spec date - 5 days10/18/041/3/053/14/056/27/0530 Forms DLVDObject type Tech Spec date - 5 days10/18/041/3/053/14/056/27/0535 Cube DLVDObject type Tech Spec date - 5 days10/18/041/3/053/14/056/27/0540 Query DLVDObject type Tech Spec date - 5 days11/15/042/7/055/16/059/5/0520 Technology Development.07 Tech Specs.05 Portals DLVDObject type Code/Unit date - 5 days10/25/041/10/053/21/057/4/0510 Reports DLVDObject type Code/Unit date - 5 days11/22/042/14/055/23/059/12/0515 Interfaces DLVDObject type Code/Unit date - 5 days10/25/041/10/053/21/057/4/0525 Enhancements DLVDObject type Code/Unit date - 5 days10/25/041/10/053/21/057/4/0530 Forms DLVDObject type Code/Unit date - 5 days10/25/041/10/053/21/057/4/0535 Cube DLVDObject type Code/Unit date - 5 days10/25/041/10/053/21/057/4/0540 Query DLVDObject type Code/Unit date - 5 days11/22/042/14/055/23/059/12/0510 Code and Unit Test.05 Portals DLVDObject type Accept Test date - 5 days11/1/041/17/053/28/057/11/0510 Reports DLVDObject type Accept Test date - 5 days11/29/042/21/055/30/059/19/0515 Interfaces DLVDObject type Accept Test date - 5 days11/1/041/17/053/28/057/11/0525 Enhancements DLVDObject type Accept Test date - 5 days11/1/041/17/053/28/057/11/0530 Forms DLVDObject type Accept Test date - 5 days11/1/041/17/053/28/057/11/0535 Cube DLVDObject type Accept Test date - 5 days11/1/041/17/053/28/057/11/0540 Query DLVDObject type Accept Test date - 5 days11/29/042/21/055/30/059/19/0520 Accept Test and Migrate.05 Portals DLVDIUT start date - 5 days11/8/041/24/054/4/057/18/0510 Reports DLVDSys Test Cycle 1 start date - 5 days12/6/042/28/056/6/059/26/0515 Interfaces DLVDIUT start date - 5 days11/8/041/24/054/4/057/18/0525 Enhancements DLVDIUT start date - 5 days11/8/041/24/054/4/057/18/0530 Forms DLVDIUT start date - 5 days11/8/041/24/054/4/057/18/0535 Cube DLVDIUT start date - 5 days11/8/041/24/054/4/057/18/0540 Query DLVDSys Test Cycle 1 start date - 5 days12/6/042/28/056/6/059/26/0525 End User Doc Development.05 Work Instruction DLVDCase Accept Test - 5 days11/29/042/21/055/30/059/19/0510 User Procs DLVDCase Accept Test - 5 days11/29/042/21/055/30/059/19/0515 Compliance Assess DLVDCase Accept Test - 5 days11/29/042/21/055/30/059/19/0520 Biz Continuity Procs DLVDCase Accept Test - 5 days11/29/042/21/055/30/059/19/0530 Case Acceptance Test.05 Case Accept Test DLVDSys Test Cycle 1 start date - 5 days12/6/042/28/056/6/059/26/0520 Manage Prototyping.05 Cycle 1.15 Collect Prot Master Data DLVDBlueprint end date11/1/0411/1/042/4/051/30/0520 Load Proto Master Data DLVDPrototype cycle 1 start date +1511/8/0411/8/041/17/054/11/0510 Cycle 2.05 Prep Proto Cycle 2.10 Define Proto Master Data Reqd DLVDProto cycle 2 start date -15 days9/27/0410/25/041/24/055/2/0515 Collect Prot Master Data DLVNEW: Prot cycle 2 sart date - 5 days10/11/0411/8/042/7/055/16/0515 Load Proto Master Data DLVDProto cycle 2 start date + 5 days10/25/0411/22/042/21/055/30/0525 Integrated Unit Test.05 Plan IUT DLVDIUT start date - 30 days10/4/0412/20/042/28/056/13/0510 Define IUT Data Reqmts DLVDIUT start date - 25 days10/11/0412/27/043/7/056/20/05Collect IUT DataNEW: IUT start date - 20 days10/18/041/3/053/14/056/27/0515 Load IUT Data DLVDIUT start date11/15/041/31/054/11/057/25/0530 End User Security.05 Design Activity Roles DLVDSys Test cycle 1 start date - 10 days11/29/042/21/055/30/059/19/0515 Unit Test Activity Roles DLVDSys Test cycle 1 start date - 5 days12/6/042/28/056/6/059/26/0535 Data Conversion.05 Data Conv Plan.05 Final Conv Approach DLVDSys Test cycle 1 start - 65 days9/13/0412/6/043/14/057/4/0510 Final Data Collection Plan DLVDSys Test cycle 1 start - 55 days9/27/0412/20/043/28/057/18/0515 Develop Conv Execution Plan DLVDSys Test cycle 1 start - 40 days10/18/041/10/054/18/058/8/0510 Data Conv Quality.15 Plan Data ImprovementsNew DLV Sys Test cycle 1 start - 45 days10/11/041/3/054/11/058/1/0530 Dev DQ Verification Rules DLVDSys Test cycle 1 start - 25 days11/8/041/31/055/9/058/29/0540 Define Validation Procs Tech DLVDSys Test cycle 1 start - 25 days11/8/041/31/055/9/058/29/0550 Define Validation Procs Content DLVDSys Test cycle 1 start - 25 days11/8/041/31/055/9/058/29/0520 Data Conv Dev.05 Funct Specs DLVDSys Test cycle 1 start - 55 days9/27/0412/20/043/28/057/18/0515 Tech Specs DLVDSys Test cycle 1 start - 50 days10/4/0412/27/044/4/057/25/0525 Code Unit Test DLVDSys Test cycle 1 start - 35 days10/25/041/17/054/25/058/15/0535 Accept Test DLVDSys Test cycle 1 start - 25 days11/8/041/31/055/9/058/29/0545 System Test.05 System Test Cycle 1.05 Plan Sys Test DLVDSystem test cycle 1 start date12/13/043/7/056/13/0510/3/0510 Conduct Mock Conv DLVDSystem test cycle 1 start date12/13/043/7/056/13/0510/3/0510 System Test Cycle 2.05 Plan Sys Test DLVDSystem test cycle 2 start daten/an/an/an/a10 Conduct Mock Conv DLVDSystem test cycle 2 start daten/an/an/an/a50 Change Mgmt.55 Training Dev.05 Dev Training Matls.05 Draft A DLVDtbd10 Draft B DLVDtbd15 Draft C DLVDtbd10 Prepare Training Environment.05 Define Training Master Data Required DLVDtbdCollect Training Master DataNEW10 Load Training Master Data DLVDtbd60 Post Impl Supp Design.65 Cutover Planning.70 Bene Realization.75 Stakehold Mgmt.10 Checkpoint Sponsor Engagement DLVDmanually determined20 Checkpoint Implementation Network DLVDmanually determined80 Power User Mgmt.10 Id Power Users DLVDtbd15 Communicate Power User Resource Needs DLVDtbd20 Conduct Conf Call with Power User Mgrs DLVDtbd90 QA and Integration Rev.05 Mid Point Review DLVDmanually determined10 End of Phase Integration Review DLVDend of realization15 Phase Compl Review DLVDend of realization04 Final Prep.10 Technical Infrastructure.05 Install Facility EquipmentDtbd15 Burn In Period for FacilityDtbd15 Integration Test.05 Int Test Cycle 1.05 Plan Integration Test DLVDIntegration test cycle 1 start date1/31/055/2/058/1/0512/31/9912/31/9912/31/9911/28/0510 Conduct Mock Conversion DLVDIntegration test cycle 1 start date1/31/055/2/058/1/0512/31/9912/31/9912/31/9911/28/0510 Int Test Cycle 2.05 Plan Integration Test DLVDIntegration test cycle 2 start daten/an/an/an/an/an/an/a10 Conduct Mock Conversion DLVDIntegration test cycle 2 start daten/an/an/an/an/an/an/a20 End User Training.25 Change Management.10 Checkpoint Change Plan Execution DLVDmanually determined15 Conduct User Readiness Assessment DLVDmanually determined30 Finalize Post Impl Support.35 Data Conversion.40 Bene Realization.45 Stakeholder Mgmt.50 Cutover.15 Load Go Live Data DLVDgo live4/1/058/1/0510/31/0512/31/9912/31/9912/31/993/1/0690 QA and Integration Reviews.05 Mid Phase Integration Review DLVDmanually determined10 End Phase Integration Review DLVDend of final prep phase15 Final Prep Completion Review DLVDend of final prep phase

&C&"Arial,Bold"EDGECritical Path Deliverable Exception Dates&CPage &P of &N&R&D&T

Calendar20062007Week starting7/258/18/88/158/228/299/59/129/199/2610/310/1010/1710/2410/3111/711/1411/2111/2812/512/1212/1912/261/21/91/161/231/302/62/132/202/273/63/133/203/274/34/104/174/245/15/85/155/225/296/56/126/196/267/37/107/177/247/318/78/148/218/289/49/119/189/2510/210/910/1610/2310/3011/611/1311/2011/2712/412/1112/1812/251/11/81/151/221/292/52/122/192/263/53/123/193/264/24/94/164/234/305/75/145/215/286/46/116/186/257/27/97/167/237/308/68/138/208/279/39/109/179/2410/110/810/1510/2210/2911/511/1211/1911/2612/312/1012/1712/2412/311/71/141/211/282/42/112/182/253/33/103/173/243/314/74/144/214/285/55/125/195/266/26/96/166/236/307/77/147/217/288/48/118/188/259/19/89/159/229/2910/610/1310/2010/2711/311/1011/1711/2412/112/812/1512/2212/291/51/121/191/262/22/92/162/233/23/93/163/233/304/64/134/204/275/45/115/185/25Nov. 2005 / R04V1W4BW 3.5 UpgradeP x0V/x0Q Mig& Rgrs.x0Q Conv.System TestMth.Endx0V Conv.x0V MockConv.MockIntegration Test 1Month EndI/G x0V/x0Q Mig & Rgrs.Conv.MockIntegration Test 2Month. EndProd. ConvEarly OrdersCut OverR04V1W4BW 3.5 UpgradeBreak-Fix WindowMarch 2006 / R05Project W1Project X (1)Proto 1 Support Pk Apply/TstProto 2 Support PkTPR Fix Support PkIntegrated Unit TestMth Endx0Q Conv.Data/MigConversionsMockSystem Test 1Month.Endx0V Conv.x0V MockRegression Prior WavesConversionsMockIntegration Test 1P x0V/x0Q Mig& Rgrs.I/G x0V/x0Q Mig & Rgrs.Regression Prior WavesConversionsMockIntegration Test 2Mth EndTraining Conv.Training Data StagingProd. ConvErly OrdrCut OverR05Fiber W1X-Plant Trim(1)Break-Fix WindowJuly 2006 / R06Project W2V2 Wave 1Prototype Cycle 1WalkthruPrototype Cycle 2Integrated Unit Testx0V Conv.x0V MockData/MigData LoadData/MigConversionsMockSystem Test 1P x0V/x0Q Mig& Rgrs.x0Q Conv.ConversionsMockIntegration Test 1I/G x0V/x0Q Mig & Rgrs.ConversionsMockIntegration Test 2Prod. ConvErly OrdCut OverR06Fiber W2X-Plant Trim(2)Break-Fix WindowNov 2006 / R07Fiber W3V2 Wave 2BaselinePrototype Cycle 1Prototype Cycle 2Integrated Unit Testx0Q Conv.Data LoadsData/MigData LoadData/MigConversionsMockSystem Test 1x0V Conv.x0V MockConversionsMockIntegration Test 1P x0V/x0Q Mig& Rgrs.I/G x0V/x0Q Mig & Rgrs.ConversionsMockIntegration Test 2Prod. ConvEarly OrdersCut OverR07Fiber W3Break-Fix WindowMarch 2007V2 Wave 3,4,5BaselinePrototype Cycle 1Prototype Cycle 2Integrated Unit Testx0Q Conv.Data LoadsData/MigData LoadData/MigConversionsMockSystem Test 1x0V Conv.x0V MockConversionsMockIntegration Test 1P x0V/x0Q Mig& Rgrs.I/G x0V/x0Q Mig & Rgrs.ConversionsMockIntegration Test 2Prod. ConvErly OrdCut OverR08Break-Fix WindowDevelopment - Prototype 1Resources unavailable to execute activity due to deploymentDevelopment - Prototype 2Month end testing occuring in environment after the formal end of testingTPR Fix (EDV suite)System Test boxes (ET0 suite), client 75 connectionsIntegration Test boxes (ETS suite), client 75 connectionsIntegration Test boxes (ETS suite), client 85 connectionsTraining suitesProductionSystem Refresh

&L&16DRAFT&C&16EDGE Release Calendar Version 14&R&16DRAFT&L&16DRAFT&C&16&D &TVersion 14Last Modified: 7/26/2005&R&16DRAFTPI/GPEDE Avail. 2/17PIPPGConversions start 5/24PIPIPPIPIPPI/GII/GPIGPIGII/GPI/GPGGGGGGNote: Support pack schedules have only been planned to date for the March 2006 release. On 10/17 support packs for this release go to system test and on 10/18 to the integration test environments. Thereafter, they will move with the "P" transport group.5/266/136/30Note: Versions which have not yet exited blueprint have been removed from the release calendar. Initial implementations of versions will be slotted into releases and published on the calendar when the version finishes blueprinting and has developed a detailed realization plan.Release Calendar 14 Key Changes:

* Added walkthrus for July 2006 release and beyond* Added March 2006 support pack schedule5/65/146/77/28-7/29R04I xTSRelease Calendar 14 Key Changes:

* Added March 2006 support pack timing* Completed detailed transport dates for Nov. 2005 release through go-live* Training conversion/staging times for March 2006 added* Added a week to ITC2 conversions for Nov. 2005 release (start earlier)* Added a week to ITC2 conversions for Mar. 2006 release (start earlier)* Removed X-Plant trim phase 2 testing until MTS study finalized9/7-9/8 R04P x0V9/17-9/18R04P x0110/15-10/16R04I x0110/5-10/6 R04I x0V9/14-9/15 R04P x0Q10/12-10/13 R04I x0V10/49/5R05P xT09/22-9/23R05I xT010/18-10/20R05P+spt pk xTS10/17 spt. Pk xT011/10-11/11R05I xT012/15-12/16R05I ITC2 Mock Prep

MBD01533EE1.vsdxSB

Support &Release N &Release N+1

Instance Copy afterCycle 1 Conversions

xDE

Support &Release N

InstanceCopy atBeginningof Classes

xDV

xT0

xTS

x0V

x0Q

x01

xRB

xR1

xRP

Test

TPR Fix

Proto C2 & IUT

SystemTest

Dvlp Support

Prod

Test Support

TrainClass

TrainPractice

ProtoC1

Integration

TrainBuild