html5-img
1 / 36

Using Enterprise Architecture to Avoid Errors and Ensure Success: A Marine Corps Case Study

Using Enterprise Architecture to Avoid Errors and Ensure Success: A Marine Corps Case Study. Dr. Geoffrey P Malafsky President, TECHi2 Ms. Elizabeth Sedlacek Director Information Systems & Infrastructure Marine Corps Systems Command. Architecture.

leda
Download Presentation

Using Enterprise Architecture to Avoid Errors and Ensure Success: A Marine Corps Case Study

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using Enterprise Architecture to Avoid Errors and Ensure Success: A Marine Corps Case Study Dr. Geoffrey P Malafsky President, TECHi2 Ms. Elizabeth Sedlacek Director Information Systems & Infrastructure Marine Corps Systems Command

  2. Architecture • The art & science of designing and erecting buildings. • A style and method of design and construction • Orderly arrangement of parts; structure: the architecture of the federal bureaucracy; the architecture of a novel. • Computer Science: The overall design or structure of a computer system, including the hardware and the software required to run it, especially the internal structure of the microprocessor. TECHi2, MCSC

  3. When We Think of Architecture.. TECHi2, MCSC

  4. Form Materials Structure Aesthetics Use patterns Maintenance Construction Safety Architecture Includes … An architecture is “the structure of components, their relationships, and the principles and guidelines governing their design and evolution over time.” (IEEE Std 610.12) TECHi2, MCSC

  5. Architecture for IT • Network diagrams • Software models • Communication protocols • Hardware connections TECHi2, MCSC

  6. Yes, But Also… • How, who, when, why, where, what of design, funding, decision-making, development, operation and maintenance • Why all of these “soft” issues • Lessons Learned from many years of large scale IT programs • Organizational issues can dominate systems engineering • Real success depends on single system blending people, process, technology TECHi2, MCSC

  7. Architecture Frameworks • Federal Enterprise Architecture Framework (FEAF) • Zachman framework • The Open Group Architecture Framework (TOGAF) • Object Management Group (OMG) Model Driven Architecture (MDA) • Department of Defense Architecture Framework (DODAF) TECHi2, MCSC

  8. Zachman Framework TECHi2, MCSC

  9. DODAF • Defines 3 primary views • There is no single view of an architecture (business process, network, hardware, data management, etc.) that describes all critical components, data, and users • Use standardized products, terms, and definitions • Operational View: tasks and activities of concern and the information exchanges required • Technical View: profile of a minimal set of time-phased standards and rules governing the implementation, arrangement, interaction, and interdependence of system elements. • System View: systems of concern and the connections among those systems in context with the operational architecture view. TECHi2, MCSC

  10. DODAF: Example Key Products • ALL Views • AV-1: Overview and Summary Information • AV-2: Integrated Dictionary • Operation Views • OV-1: High-level Operational Concept Graphic • OV-2: Operational Node Connectivity Description • OV-3: Operational Information Exchange Matrix • System View • SV-1: System Interface Description • Technical View • TV-1: Technical Architecture Profile TECHi2, MCSC

  11. System Design & Development: Known Hurdles • Acquisition is structured to purchase tools based on lists of functions • Users need support of business processes • No single organizational group makes all necessary decisions and controls all types of funds • Success or failure of the system and program hinges on the intangibles of usefulness, usability, relevance TECHi2, MCSC

  12. Errors to Avoid • “Wrong” group doing: • Requirements • Technical specifications • Program management • Systems engineering • Debating the above issues across organizational roles and responsibilities • Relying on vendor or analyst literature for technical design • Focusing most effort on networks, hardware, software instead of business process, operational capabilities TECHi2, MCSC

  13. Success Factors to Promote • Clear roles and responsibilities • Maximize use of industry and government standards • Business focused Measures of Effectiveness • Constantly restate role of technology as supporting not driving design of capabilities TECHi2, MCSC

  14. How does EA Help? • Keeps people aware of need for synergy among people-process-technology • Highlights operational capabilities as source of design and development not by-products • Forces explicit definition of information needs, by whom, when, …. • Requires explicit statement of organizational roles and responsibilities TECHi2, MCSC

  15. Example: Who Defines Requirements • Operational Views show the goals and major information requirements • System Views show the layout and connections of network, hardware, software • Which view states requirements? • Who defines the requirements? • Answer: Different roles for different requirements TECHi2, MCSC

  16. DODAF Views Requirements group, e.g. CIO Systems engineering group: e.g. MCSC Standards group, e.g. Acquisition, policy, industry TECHi2, MCSC

  17. DODAF OVs From Software Productivity Consortium TECHi2, MCSC

  18. DODAF SVs From Software Productivity Consortium TECHi2, MCSC

  19. As an example, a portal was designed for the Commandant of the Marine Corps (CMC). As this OV-1 shows, the intent of the portal is not to deploy just a portal but to provide the Marine Corps senior leadership with one secure tool bringing together applications, databases, and metadata to provide key information and data. TECHi2, MCSC

  20. The OV-2 for the Commandant’s portal shows the major stakeholders and how they are connected in terms of informationneeds. A separate product (i.e. SV) will show how the system components are connected for each stakeholder. TECHi2, MCSC

  21. CMC Portal OV-3: Information Exchange Requirement TECHi2, MCSC

  22. The SV-1 for the Commandant’s portal shows the major system components and how they are connected in terms of hardwareneeds. TECHi2, MCSC

  23. United States Marine Corps Enterprise Architecture Ms. Elizabeth Sedlacek Director Information Systems and Infrastructure Marine Corps Systems Command

  24. What is an Enterprise Architecture? TECHi2, MCSC

  25. What is an Enterprise Architecture? • Enterprise Architecture – • Is a discipline for assessing and recommending candidate Information Technology solutions in an integrated context with business and mission operations • Translates to – • Significant increase in the Warfighting Capability Takes the…Baseline Architecture Utilizes… an Integration Plan To develop…a Target Architecture TECHi2, MCSC

  26. How do we use the Enterprise Architecture? - Operational Requirements • Provides the basis from which we define operational capabilities • Describes the linkages among systems, which turn separate systems into Warfighting Capabilities. EA is the disciplined approach to achieve a Network Centric Warfare Capability TECHi2, MCSC

  27. How do we use the Enterprise Architecture? – Systems Engineering • It provides a tool for systems engineers to communicate so that the separate system designs become integrated to produce required Operational Capabilities. TECHi2, MCSC

  28. How do we use the Enterprise Architecture? – Modeling and Testing • It provides a tool for test engineers to develop scripts which are operationally relevant and doctrinally sound that goes beyond architecture modeling. Agency-Level View (OV-2) Architecture Cube Roles & Chores (Composite View) TECHi2, MCSC

  29. How do we use the Enterprise Architecture? – Analyses • It provides a common framework to evaluate, analyze and report linkages and sensitivities among the DOTMLPF factors. Map Roles & Chores to Systems Map Chores toSystem-Operator Steps Assess Consistency of Doctrine, Organization, Training, and Materiel TECHi2, MCSC

  30. Roles and Responsibilities MOA HQMC, C4 CIO - Define and issue IT standards and policies - Participate in the collaborative environment - Develop the Roadmap for enhancing the EITA - Address architectures in AIS/IT requirements MCCDC - Develop and maintain the operational architectures and concepts - Participate in the collaborative environment - Address architectures in AIS/IT requirements MCSC - Develop and maintain systems and technical architectures - Create a collaborative environment to develop and maintain the EITA - Ensure all IT programs are compliant with the EITA - Lead the resolution of conflicts between operational, systems, and technical views TECHi2, MCSC

  31. Marine Corps Enterprise IT Services (MCEITS)A look at the Marine Corps EA in action…….. TECHi2, MCSC

  32. What is MCEITS • MCEITS is envisioned to become the Marine Corps solution for: • Infrastructure (brick and mortar) • IT Centers – Physical location of hardware, software and computer applications • Services • Data Management – Access to data needed to make decisions • Application Management – 24/7 availability of computer applications • Governance • Policy and Engineering Management – Standards and Systems Engineering • Acquisition Support Governance Services Infrastructure TECHi2, MCSC

  33. Beginning of Marine Corps Net-CentricEnterpriseServices Implementation MCEITS and NCES • Infrastructure • The IT Centers will comprise a disciplined and standardized hardware, software, and firmware baseline which will furnish the MC with proven, reliable, resilient, and survivable production, testing, and development environments. • Services • This baseline will host multiple database systems and application in an N-tier architecture and will also provide the requisite administrative and management Services to fully support the hosted systems. • Governance • The capabilities of the IT Centers and Services will be harnessed and augmented by a consistent and disciplined Governance process. TECHi2, MCSC

  34. Overall Benefits • Harmonizes ITS/NSS Assets - Cost, readiness, interoperability • Enables Marine Corps to respond to DoD IT business process improvement and transformation initiatives • Facilitates Marine Corps participation in DoD Net-Centric programs • Creates conditions for enterprise IT demands (scalability) • Augments current initiatives (NMCI, COOP, PORs) • Provides common user / application services • Forcing function for creating system interoperability, integration and training TECHi2, MCSC

  35. So what about the Enterprise Architecture? • Forcing function for creating system interoperability, integration and training • System identification and interfaces • NCES/NII/OSD requirements • Organizational processes • Program alignment and interoperability TECHi2, MCSC

  36. Summary & Questions Brief is available at: www.techi2.com www.e-gov.com/events/2004/ea2/downloads/

More Related