ea implementation - 1 enterprise architecture implementation mba731 enterprise architecture...

EA Implementation - 1

Enterprise Architecture Implementation

MBA731

Enterprise Architecture

ImplementationCase Study:

US Navy Marine Corps Intranet

(NMCI)

Seth Riggins

22 October ‘07


EA Recap

Basic Principles

• Enterprise Architecture: – is the description of the current and/or future

structure and behavior of an organization's processes, information systems, personnel and organizational sub-units, aligned with the organization's core goals and strategic direction.

– relates more broadly to the practice of business optimization in that it addresses business architecture, performance management, organizational structure and process architecture as well.


EA Recap

• EA Methodology– The Practice of Enterprise Architecture involves

developing an architecture framework to describe a series of "current", "intermediate" and "target" reference architectures and applying them to align change within the enterprise. Another set of terms for these are "as-is", "to-be" and the "migration plan".

– The primary purpose of creating an enterprise architecture is to ensure that business strategy and IT investments are aligned.


EA Recap

• EA Frameworks– These frameworks detail all relevant structure

within the organization including business, applications, technology and data.

– They will provide a rigorous taxonomy and ontology that clearly identifies what processes a business performs and detailed information about how those processes are executed.

• Products/Results– The end product is a set of artifacts that describe in

varying degrees of detail exactly what and how a business operates and what resources are required. These artifacts are often graphical.


EA Recap

• Why do we have to care?– As investments in IT systems become a larger

relative portion of organizations’ operating costs, more consideration must be given to the structure and nature of those systems and the business processes they support.

• When should someone use it? – Whenever there is redundancy or inefficiency in any

internal process, the solutions proposed must encompass their relationships to the organization as a whole.

– The Enterprise approach is simply a standardized, ‘big picture’ view that considers all parts of the organization and evaluates each function in context of the aggregated processes.


EA Recap

• How should one go about implementing it? – Solutions will vary with the nature of the problems

presented, however, general success factors in EA implementation are similar to those in BPR and software design success factors:» Comprehensive Needs Assessment

» Requirements Definition and Control – “Roadmap”

» Balancing Innovation with Functionality

» Exception Management

» Transition Management

» Top Leadership Involvement


NMCI History and Evolution

Implementation Case Study - NMCI



• What is NMCI?– The largest government IT contract in the world,

with contract minimums valued at a potential $8 Billion throughout the life of the contract.

– The four-year, firm-fixed-price contract was awarded to an EDS-led team of industry partners on Oct. 6, 2000, with an option for 3 more years.

– In October 2004, this option was exercised, and the original contract was extended to October 2007. The October 2007 contract extension included another option for an additional three years.

– On March 24, 2006, the Navy and EDS agreed to exercise this additional three-year option to extend the contract to/through September 2010.



• Why was NMCI created?– Dept of the Navy (DoN) is inherently geographically

diverse and requires global IT support

– Numerous common functions and processes are performed at each location, with only minor deviations in focused mission areas. Most could be met with COTS solutions and products.

– Requirement for classified and unclassified service at the same locations and operational flexibility drove need for network infrastructure independent from commercial providers

– Compelling need to control costs prompted DoN to standardize and streamline many enabling capabilities, and IT was/is a major focus area



• What does NMCI do?– NMCI provides the Department of the Navy (DoN)

with a full range of network-based information services - secure, universal access to integrated voice, video and data communications - on a single, enterprise-wide intranet.

– The common environment improves security across the enterprise, periodically integrates the most up-to-date commercial technologies, and centralizes information technology budgeting and expenditures for the department.



• Quick Facts– Eventually, the massive network will link more than

400,000 workstations and laptops for 500,000 Navy and Marine Corps users at over 300 locations across the continental United States, Hawaii, Cuba, Guam, Japan and Puerto Rico.

– More than 328,000 seats are under EDS management – a single seat, such as a workstation or laptop, can support more than one user.

– EDS has completed Assumption of Responsibility (AOR) at more than 1,000 networked sites.

– So far, 5,381 seats have been deployed in support of Operation Iraqi Freedom and the war on terrorism.



• Quick Facts– NMCI and EDS operate:

» Four network operations centers

» Three enterprise help desks

» Sixteen (of 19 planned) classified server farms

» Thirty-one (of 31 planned) unclassified server farms

» Three thousand enterprise-wide servers

» Connectivity for approxmiately 11,000 Blackberry wireless devices and 2,086 air cards, 24 hours a day, seven days a week



• Quick Facts– NMCI is the only network to have completely

implemented and enforced the Department of Defense’s Cryptographic Log On (CLO) mandate, providing additional defense in depth.

– NMCI blocks approximately 9 million spam messages per month.

– NMCI also detects more than 5.2 million monthly unauthorized intrusion attempts to penetrate the NMCI external boundaries.



• Real-world Responsiveness– Integrated operation of NMCI network operations

centers, help desks and server farms enables off-site storage, rapid service and data restoration, and rapid response to service delivery requirements in the event of a real or potential disaster.

– NMCI has helped the Department of Navy to sustain mission capability through real-world challenges: » 9/11 Pentagon reconstruction

» Hurricanes Isabel, Katrina and Rita

» California wild fires

» Singapore Tsunami



• The ‘Business’ of NMCI– NMCI is a key component of FORCEnet, the DoN's

strategy for implementing network-centric warfare, and it supports the DoD’s goals for information technology superiority.

– In addition to moving the DoN to an e-business model, with common corporate applications and databases, NMCI supports new processes and technologies, such as knowledge management, distance learning and telemedicine to improve the quality of life for Sailors, Marines and the DoN’s civilian employees and support personnel.



• NMCI Critical Objectives:

– Enhancing network security

– Ensuring interoperability across commands and with other services

– Facilitating knowledge-sharing around the globe

– Increasing productivity

– Improving systems reliability and quality of services

– Reducing the cost of voice, video and data services


EA Applicability to NMCI

• As a DoD IT system, NMCI is subject to the Federal Enterprise Architecture (FEA):

– Modeling EA is becoming a common practice within the U.S. Federal Government to inform the Capital Planning and Investment Control (CPIC) process. The FEA reference models serve as a framework to guide Federal Agencies in the development of their architectures.

– The primary purpose of creating an enterprise architecture is to ensure that business strategy and IT investments are aligned. As such, enterprise architecture allows traceability from the business strategy down to the underlying technology.



• Some characteristics of FEA:

– The Federal Enterprise Architecture (FEA) is an initiative of the US Office of Management and Budget that aims to comply with the Clinger-Cohen Act and provide a common methodology for information technology (IT) acquisition in the United States federal government.

– It is designed to ease sharing of information and resources across federal agencies, reduce costs, and improve citizen services.



• The FEA is currently a collection of reference models that develop a common taxonomy and ontology for describing IT resources. These include the following:



• Each FEA Model Layer has its own focus:– PRM: a standardized framework to measure the performance

of major IT investments and their contribution to program performance

– BRM: a function-driven framework for describing the business operations of the Federal Government independent of the agencies that perform them

– SRM: a business and performance-driven, functional framework that classifies Service Components with respect to how they support business and/or performance objectives

– DRM: describes, at an aggregate level, the data and information that support government program and business line operations

– TRM: a component-driven, technical framework used to categorize the standards, specifications, and technologies that support and enable the delivery of service components and capabilities



• The detail reflected at each level of the FEA reference models is described below:


NMCI Implementation

• So, what did they do?– After synthesizing the customer needs into the

above framework, NMCI began the task of delivery.

– Initial rollouts were small-scale by individual command or organization; fewer than 1,000 seats at a time.

– Early feedback refined their migration process into defined service areas, and they began to standardize and streamline the ‘assimilation’ of new activities.

– Most of these activities are now managed by the ‘Infrastructure Solutions’ service area.


NMCI Implementation

• What is that?– Infrastructure Solutions provides resources,

technology and integration to transform a client's enterprise into a more efficient, agile and cost-effective operation. These services enable lower IT costs, optimization of IT operations, and reduced security risks.

– Services include: » Managed Hosting

» Applications Rationalization

» File Share and Storage Solutions

» Network Solutions

» Wall Plugs and Ports


NMCI Implementation

• Applications Rationalization – The Applications Rationalization offering is a set of

capabilities, methods and tools that simplify your application portfolio.

– It focuses on identifying inefficient, redundant or obsolete applications so that you can consolidate applications, functionality and support services.

– By minimizing the number of operating systems and improving the quality of functional and technical applications, you can drive toward modernization.

– This framework for application lifecycle management represents a long-term strategy, and ongoing governance and monitoring of the application portfolio using an established framework and tools.


NMCI Implementation

• How it works– A phased transformation framework is initiated to

assess, modernize, and manage your application portfolio.

– An Applications Portfolio Assessment is conducted to collect data, identify modernization opportunities, assess gaps, and develop a high-level transition strategy.

– Programs and data structures are analyzed and an end-state abstract is developed to drive the areas of modernization.

– Applications are moved into a managed environment that sustains modernization by supporting production and development environments, licensing, security and privacy services, and application deployment.


NMCI Implementation

• This effectively amounts to a local assessment of each new activity and a ‘cherry-picking’ of available services, while noting which ones cannot be supported by NMCI infrastructure, and must then be managed as exceptions.

• This results in two things: 1) tailored requirements generated locally by users

2) another list of applications that must have a refined roadmap to transition them created and managed


NMCI Implementation

• So, how well did it work?– The jury is still out. The process is still ongoing,

with new activities being assimilated, while other are on their second tech refresh cycle.

– The rollout process is greatly improved, and lessons learned are incorporated on an ongoing basis.

– Many functions have been centralized and standardized, are faster and cheaper, but some localized IT support staff were dismissed in favor of centralized support centers.

– OMB oversight continues, and regular reports are made on its status, but most of its progress can only be measured by user satisfaction, so surveys are now constantly requested.


Implementation Difficulties

• Accommodating Exceptions– Legacy systems are still in use for unique functions

» Defense Messaging System (DMS)

» Personnel Time and Effort Tracking systems

• Accuracy in Package Loadout and Changing it– Palm Pilot software compatibility/testing rqmts

– Pro/full versions of standard Office programs

• Cutover Management– Flash cutover by site is inconsistent

• Tech Refresh Issues– Underestimated hardware update costs

– Contractual articulation of hardware requirements


Conclusions

• EA is, in reality, iterative – no one gets it right the first time, and requirements (missions, environments, external factors) change. With better EA defining your processes, though, it is easier to adapt to change.

• EA Roadmaps are only as effective as the quality of the Implementation execution.

• Any process that relies primarily on the user to define the tools needed to do their job is bound to neglect some critical functionality.


Conclusions

• Small changes in Enterprise Architecture Roadmaps can have huge impacts downstream.

• The only magical efficiencies gained in any transition to EA are those that exploit the ‘low-hanging fruit’ first and provide the greatest benefits to users. The rest is life cycle management.


Fin

Questions?


References

• Enterprise_Architecture

• Zachman_framework

• Bailey, I.D. (2006). "A Simple Guide to Enterprise Architecture"

• Federal_Enterprise_Architecture

• “NMCI Fact Sheet” from the NMCI Public Affairs Office

• NMCI homepage (DoN restricted access): https://www.homeport.navy.mil/

• May 2007 NMCI Enterprise Conference presentations

ea implementation - 1 enterprise architecture implementation mba731 enterprise architecture...

Documents