1  

A Business Driven Enterprise Architecture

Approach to Transformation

2  

Chuck Blucher Information Technology Architect

3  

About Bell Helicopter •  Subsidiary of Textron (NYSE: TXT) •  Industry-leading producer of commercial and military vertical lift aircraft •  13,000+ helicopters in service in over 140 countries •  Globally recognized for world-class customer service, innovation and

superior quality •  Major facilities: Fort Worth, Amarillo & Corpus Christi TX, Ozark AL,

Bristol TN, Mirabel QC •  2012 Revenues $4.27B, 10,500+ employees

4  

What is Enterprise Architecture? •  There are many definitions of Enterprise

Architecture (EA) and depending on your perspective one may be more important.

•  EA is used to guide decision making toward the evolution of the future state architecture.

•  EA aligns the business’ needs with the capabilities needed to reach them.

5  

What is Enterprise Architecture? •  EA is a discipline for leading enterprise

responses to disruptive forces toward a desired business vision and outcomes.

•  EA is the process of translating business vision and strategy into effective enterprise change.

•  EA is the process that hold the Business and IT together and ensure alignment.

6  

EA Relationships and Synergies

Developers  

Opera,ons  Team  

Business  

PMO  

Solu,on  Architecture  

IT  

Enterprise  Architecture  

Governance  

7  

Solution vs Enterprise Focus

BREADTH  

SOLUTION  OUTCOMES  

BUSINESS  OUTCOMES  

8  

The Focus of EA is Changing •  Traditionally EA focused on Strategies, Roadmaps,

Building Blocks, Standards, Architecture and Design Patterns, Best Practices, etc

•  Leading EA teams are now focusing on transforming and integrating business initiatives by: §  Aligning Business and IT Strategies §  Delivering Strategic Business (and IT) Value §  Enabling Business Agility and Transformation

9  

The Focus of EA is Changing •  Business and IT Leaders are looking to for ways

to execute their business strategy and deliver desired business outcomes.

•  Developing a meaningful and collaborative relationship with the business is critical § Otherwise, Technology and Solution focused.

•  Focusing on business outcomes drives business value and impacts the bottom line.

10  

What does the business care about? •  The Business cares about:

§  World Class Products and Services §  Customer Satisfaction §  Agility to seize New Opportunities and Change §  Time to Market §  Business Efficiency §  Increasing Revenue & Reducing Costs §  Business Process and Integration §  Capabilities

RESULTS  AND  POSITIVE  BUSINESS  OUTCOMES  

11  

What does the business care about? •  The Business…

§  Understands that technology is a thread in the fabric of everything they do

§  Expects that technology work seamlessly & securely §  Technology is a means to an end…, not the end itself

•  Cloud & Consumerization is a game changer •  Every IT person needs to think like a business

person contributing to business outcomes •  Partnership with IT as a Trusted Advisor

DO  YOU  WANT  TO  TRANSFORM  BUSINESS  OR  RUN  IT?  

12  

Why do Technology Driven Approaches to RFID Fail?

•  Focusing on things that are not most important to the business

•  Focusing on Technology and losing sight of: §  Enterprise View §  Overall Auto ID Strategy §  Desired Business Outcomes §  Impact on Business Processes §  Importance of Enterprise Application Integration §  The value that an RFID Integrator can provide

13  

Focus on Growing Business Value

§ Calibra2on  /Maintenance  Status  § VMI,  Right-­‐of-­‐Use  

§ Data  Mapping  Status  § Program  Status  § Order  Status  § Working  Capital  Alloca2on  

§ How  can  we  do  it  beLer  next  2me?  

§ Con2nuous  Improvement  Metrics  

What  is  the  Asset  

Producing?  

Where  is  the  Asset?  

What  is  the  Asset  Doing?  

What  Could  the  Asset  Be  Doing?  

§ Cri2cal  Service  Due  § Imminent  Auditor  Visit  § Leasing/Paperwork  Changes  

14  

A Survey of Bell Helicopter’s Journey •  Silos with similar and dissimilar needs •  Benchmarking: Industry & Internal •  Customer Interviews & Requirements Affinities •  Created an RFID Community with an Enterprise

Vision – RFID Council •  Developed an Enterprise Strategy, Business

Case with Iterative Phased Implementations •  Took a standards based approach for RFID •  Solution Evaluation & Selection •  Pilots versus Phases – Words are important!

15  

Requirement Affinities Example

16  

Strategy Discovery Summary Example

17  

Multi-Layered Road Mapping Example

18  

Key Realizations

•  View RFID as a disruptive technology •  Focus on what the business does and what it will

need to do differently in response to strategic challenges and opportunities

•  Engage the business to holistically understand business process impacts and desired business outcomes from the beginning

•  Use desired business capabilities modeling & Use Cases to represent the business’s future state in order to define actionable deliverables

19  

Key Realizations

•  Need a business champion(s) with Enterprise Vision

•  Encourage the business to Own and Lead •  Understanding the physics and technology of

RFID was important but not enough •  Needed the help of an Integrator until we

could became more self sufficient

20  

Key Realizations •  Needed an iterative Use Case driven approach

•  Use Case implementations are not equal

•  RFID without business integration limits possible business outcomes and value

•  Start small, Get Quick Wins, Focus on Value

•  Business Case should focus on hard $$

•  Communication is critical to success

21  

Summary • Use an EA driven approach to guide decision making • Use a business driven approach to improve adoption

and meet business case value

•  Focus on how to deliver better business outcomes

• Remember what the business cares about most. Technology driven approaches will fail.

• Change the way you think about IT – become a trusted advisor with business savvy

22  

Summary • Develop a Business Case and Strategy that is

focused on outcomes • Define Business & IT Governance Policies • Establish RFID Community of Stakeholders with a

common sense of purpose • Start with low hanging fruit to get ‘Quick Wins’ • Auto ID technologies can be disruptive… • Create a company standard and framework for

future RFID projects

23  

Summary •  Deploy a solution based upon proven technology

and best practices; Capture Lessons Learned •  Take a Use Case Driven Approach •  Use enterprise application integration to achieve

better business outcomes •  Leverage industry expertise; use an integrator to

get started and develop expertise

Focus  on  Business  Outcomes    Without  it,  nothing  else  maKers  very  much  

24  

25