Microsoft Motion business architecture methodology What is Microsoft Motion? What is a Motion project? Why Do We Need It?

Enterprise Integration Hub Infrastructure services Business needs Enterprise Integration Hub Web Svcs Infrastructure services Outputs Security Process Mgt Workflow Diary Mgr Business Rules Ops Mgmt Common presentation logic Devices Voice Wireless Mail Email Business services Segmentation Customer Admin Agent Admin Campaign Mgt Commission Sales Mgt Contact Mgt Adviser tools Document Mgt. Content Mgt External web services B2B

What Does the Business Want IT to Do? Understand the business better But org charts and process maps don’t cut it Respond a little faster But IT rarely gets funding for resilient, flexible solutions Cost a little less … or create more value Help make a difference Invoke IT as an enabler for effective business change Identify powerful leverage points for the application of IT

Describing the Business

Defining the Business 1. Business capabilities are stable 2. Capabilities that don’t add value can be eliminated 3. IT is a powerful agent for transformational change Web services SOA Motion

What is Microsoft Motion?

Microsoft Motion Business Architecture Modelling Customers Business partners Customer-facing channel partners IT providers Financial service providers 1. Develop product or service 2. Generate demand 5. Collaborate 3. Fulfil demand 4. Plan and manage

The Basic Module Map Customers Business partners Customer-facing channel partners IT providers Financial service providers 1. Develop product or service 2. Generate demand 5. Collaborate 3. Fulfil demand 4. Plan and manage the business

Module Map – Business Capabilities Financial service providers Customer-facing channel partners Customers Business partners IT providers 1. Develop product or service 2. Generate demand 5. Collaboration 3. Fulfil Demand 4. Plan and manage the enterprise 3.1 Provide Service 3.2 Advanced Planning 3.3 Procure resources 3.4 Produce Product 3.5 Logistics 3.3.1 Sourcing and Supplier Contract Management 3.3.2 Purchasing Create purchase requisitions Request Resources

The module map

Anatomy of a Capability Platform Process People

Encapsulating a Capability

What Use is a Business Architecture Model? Value proposition Operating model Customers Business partners Customer-facing channel partners IT providers Financial service providers 1. Develop product or service 2. Generate demand 5. Collaborate 3. Fulfil demand 4. Plan and manage Capabilities Metrics Outsourcing Partnerships Offshoring Self-service IT project portfolio IT projects SOA

How do you use Microsoft Motion?

Why Start a Motion Project? Customers Business partners Customer-facing channel partners IT providers Financial service providers 1. Develop product or service 2. Generate demand 5. Collaborate 3. Fulfil demand 4. Plan and manage Motion project Module map Acquisition Core vs. non-core Consolidation Sourcing Business architecture Automation SOA Problem-solving Incremental change Governance and compliance

Motion Project – Phase 1 Phase 1 Establish Project Context Go/no-go? Phase 1 Establish Project Context Generate Level 2+ capability map Document project context & objectives Assess capability performance Gate 1 – Go, or no-go?

Motion Project – Phase 2 Phase 2 Capture Business Architecture Go/no-go? Check completeness of operational, environmental and financial framing Phase 2 Capture Business Architecture Gather existing business and financial documentation 'Go In' – Map relevant Level 2+ capabilities 'Go Up' – Connect capability Levels 1 and 2 'Go Out' – Connect environmental capabilities Gate 2: Check completeness Off-Ramp

Motion Project – Phase 3 Phase 3 Go/no-go? Check completeness of operational, environmental and financial framing Understand 'as-is' business architecture Phase 3 Complete 'as-is' Business Architecture 'Go Down' – Cross-reference capabilities to teams, business objectives and financials Identify capability connectors Identify service level expectations Identify people, process and platform views Workshop: Gate 3 – Understand Business Architecture Off-Ramp

Motion Project – Phase 4 Phase 4 Recommend Next Steps Go/no-go? Check completeness of operational, environmental and financial framing Understand 'as-is' business architecture Deliver final project recommendations Phase 4 Recommend Next Steps Identify leverage points and impediments Select appropriate improvement model Develop next step recommendation Identify project opportunities and risks Deliver final project recommendation

Case Study Situation Project Result Fortune 500 logistics company Comprises five independently-minded business units IT wanted to move to SOA, business saw little benefit Project Senior executive wanted to expose commonalities across LoB Eight week Motion project sponsored Result Business thought there was ~15% overlap between LoB; actually ~60% Businesses now communicating with a common language 20% sustainable reduction in CIO’s CapEx Management has a clear path to adopt SOA Motion rolled out to all departments as operating model & strategy

Microsoft Motion business architecture methodology Next steps … Workshop – this afternoon, 1pm Panel discussion – tomorrow, 3pm