Team 4 – Exercise 5

1. Team 4 – Exercise 5 Jeff, Brij, Marty, Doug

2. Critical Business Problems • High cost structure • Dominance of the incumbent • Incumbent prices are lower • Increase in oil price • Pacific Rim Logistics is losing money • HCC barely breaking even • UPE Merger is not yet complete • UPE is losing market share • Old IT systems –PL1, NT4

3. Proposed Business Solution • Reduce costs by eliminating duplication of IT systems and Business processes. • Improve customer service (system simplification, GPS Tracking functionality) • Strategic Partnerships (Bonsai) • Use the ZExpress brand • Leverage the ZExpress marketing capability

4. Constraints • Time • CEO has promised cost reduction within 2 years • PRL can only continue with current P&L for 18 months • Budgetary constraints • Current costs are too high • EA must reduce cost not increase it! • Keep operations going • Architectural change must occur without disrupting current business operations • Availability of business resources • Business input is vital • But they have their day jobs! • Global nature of business • Different time zones means challenges to arranging collaboration • Architecture must respect local variations

5. Scope of the Enterprise Architecture Project • Breadth of Enterprise • Include all 3 original Enterprises • Exclude Partners and Suppliers • Architecture Domains • All domains considered: Business; IS; Technology • Level of Detail • Only enough and no more • Time Horizon • Minimise Transitional Architectures

6. Architecture Partitions 1 • Architecture partitioned by major business process areas • Why? • Time constraints mean that architecting the entire enterprise is not an option • Allows us to focus initial effort on segments where the most business value can be extracted

7. Architecture Partitions 2 • Two basic approaches: • A. Segment architecture and work through ADM in parallel • B. Segment and cycle through ADM in series • Option B was chosen: • Quickest way to deliver business value was to concentrate EA efforts on one segment and deliver that segment architecture to build • Some risk of missing dependencies between segments • Mitigation of risk provided by working on entire enterprise architecture in Preliminary and Architecture Vision phases thus gaining a high level overview of all segments

8. Architecture Partitions 3 • Package Tracking • Billing, Accounting, HR • Route Management • Transportation Management • Sort Management • Office Productivity

9. ADM We will iterate through all phases of the ADM The Preliminary phase will only be conducted in the first iteration unless significant change management issues lead to the need of a new kick start As the Preliminary and Architecture Vision phases in the initial iteration will be conducted on an enterprise wide scope, these phases are expected to take a lesser amount of time in subsequent iterations We estimate 2 months for the Preliminary and Architecture Vision phases and 2 weeks for the rest of the phases in the first iteration Subsequent iterations through the phases will take less or more time depending on the complexity of the problem area we target in the particular iteration

10. Preliminary Phase • Key Activities • Confirm Governance and Support Frameworks • Define and Establish Enterprise Architecture Team • Identify and Establish Architecture Principles • Select and Tailor Architecture Framework(s) • Key Deliverables • Organization Model for EA • Tailored EA Framework including Architecture Principles • Governance Framework

11. Architecture Vision • Key Activities • Identify Stakeholders, Concerns, and Business Requirements • Evaluate Business Capabilities • Define Scope • Develop Architecture Vision • Develop high level baseline and target architectures for each domain • Identify the Business Transformation Risks and Mitigation Activities • Key Deliverables • Approved Statement of Architecture Work • Capability Assessment • Refined Business Principles, Goals and Drivers • Architecture Vision • Communication Plan

12. Business Architecture • KeyActivities • Select Reference Models, Viewpoints, and Tools • Develop Baseline and Target Business Architecture Description • Perform Gap Analysis • Define Roadmap Components • Resolve Impacts Across the Architecture Landscape • Conduct Formal Stakeholder Review • Finalize the Business Architecture • Create Architecture Definition Document • Key Deliverables • Refined and Updated Architecture Vision Phase Outputs • Draft Architecture Definition Document containing V 1.0 of Baseline and Target Business Architecture • Draft Architecture Requirements Documents (Business Requirements)

13. Information Systems Architecture(Data, Applications & Technology) • Key Activities • Select Reference Models, Viewpoints, and Tools • Develop Baseline and Target Data/Application /Technology Architecture Description • Perform Gap Analysis • Define Roadmap Components • Resolve Impacts Across the Architecture Landscape • Conduct Formal Stakeholder Review • Finalize the Data/Application/Technology Architecture • Create Architecture Definition Document • Key Deliverables • Updated Statement of Architecture Work • Draft Architecture Definition Document containing V 1.0 Data, Application and Technology Architecture • Draft Architecture Requirements Documents (Data, Application and Technology Requirements)

14. Opportunities and Solutions • Key Activities • Determine/Confirm Key Corporate Change Attributes • Review and Consolidate Gap Analysis Results from Phases B to D • Refine and Validate Dependencies • Confirm Readiness and Risk for Business Transformation • Formulate High-Level Implementation and Migration Strategy • Identify and Group Major Work Packages • Identify Transition Architectures • Create Portfolio and Project Charters and Update the Architectures • Key Deliverables • Statement of Architecture Work • Comprehensive Architecture Vision Document • Consolidated and Validated Architecture Roadmap • Capability assessment • Transition Architecture (s) • Implementation and Migration Strategy

15. Implementation Governance • Key Activities • Confirm Scope and Priorities for Deployment with Development Management • Identify Deployment Resources and Skills • Guide Development of Solutions Deployment • Perform Enterprise Architecture Compliance Reviews • Implement Business and IT Operations • Perform Post-Implementation Review and Close the Implementation • Key Deliverables • Architecture Contract • Compliance Assessments • Change Requests • Architecture-compliant solution(s)

16. Implementation Governance • Key Activities • Establish Value Realization Process • Deploy Monitoring Tools • Manage Risks • Provide Analysis for Architecture Change Management • Develop Change Requirements to Meet Performance Targets • Manage Governance Process • Activate the Process to Implement Change • Key Deliverables • Architecture updates • Changes to architecture framework and principles • New Request for Architecture Work, to move to another cycle (for major changes) • Statement of Architecture Work, updated if necessary • Architecture Contract, updated if necessary • Compliance Assessments, updated if necessary

17. Architecture Requirements Management • Key Activities • Baseline Requirements • Monitor and Update Requirements as we go through the phases • Key Deliverables • Requirements Impact Assessment • Architecture Requirements Specification (Updated through the phases if necessary)

18. Project Structure

19. Governance Approach • Implement in the preliminary phase • Identify processes, artefacts, controls, environment • Establish cross-org architecture board • Establish responsibilities and structure • Develop compliance strategy • Establish policies, procedures, roles… • Process and tools to manage EA operations • Define set of criteria by which aspects of the EA will be assessed • Establish Principles to guide EA