1 / 17

System of Systems Enterprise Architecture

System of Systems Enterprise Architecture. October 6, 2009 Gustavo Limon, OCIO Harry Tabak, OCIO. Enterprise as a system. Enterprise Architecture models and analyzes an enterprise as a system -- or System of Systems.

addison
Download Presentation

System of Systems Enterprise Architecture

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. System of SystemsEnterprise Architecture October 6, 2009 Gustavo Limon, OCIO Harry Tabak, OCIO

  2. Enterprise as a system • Enterprise Architecture models and analyzes an enterprise as a system -- or System of Systems. • Doing so, facilitates the community planning necessary of members of the enterprise to work and play together. • Without it we get the Winchester House

  3. Winchester Mystery House San Jose, CA

  4. Winchester Mystery House - San Jose, CA • Some of the bizarre phenomena that gave the mansion its name: • A window built into the floor • Staircases leading to nowhere • A chimney that rises four floors • Doors that open onto blank walls • Upside down posts • Sarah Winchester kept the carpenters' hammers pounding 24 hours a day for 38 years • Blueprints available: None! Mrs. Winchester never had a master set of blueprints, but did sketch out individual rooms on paper and even tablecloths!

  5. Winchester Mystery House - San Jose, CA • Number of rooms: 160 • Cost: $5,500,000 • Date of Construction: 1884 - September 5, 1922 (38 continuous years!) • Number of stories: Prior to 1906 Earthquake - 7; presently 4 • Number of basements: 2 • Heating: Steam, forced air, fireplaces • Number of windows: Frames 1,257; panes approx. 10,000 • Number of doors: Doorways 467, doors approx. 950 not including cabinet doors. • Number of fireplaces: 47 (gas, wood, or coal burning) • Number of chimneys: Presently 17 with evidence of 2 others • Number of bedrooms: Approx. 40 • Number of kitchens: 5 or 6 • Number of staircases: 40, total of stair steps - 367 • Number of skylights: Approx. 52 • Number of ballrooms: 2 (one nearly complete, and one under construction)

  6. Models assist planning and analysis • Models help people to communicate. • A model describes the situation in a particular way, for a particular audience, so that other people can understand. • Models explain and make predictions. • A model relates primitive system components to one another and to complex components, providing explanation and predictions about the behavior of the system. • Models mediate among multiple viewpoints. • Two people frequently won’t agree with what they want to know about a component; models represent their commonalities while allowing the differences to be explored.

  7. Getting There From Here • Future model to meet corporate strategic plans. • This is the ‘target’ state as it must evolve to reflect its strategic plan and business drivers in order to close performance gaps and take advantage of opportunities. • Baseline model to understand where we are. • Capture just enough detail to model the target state and transition plans. • Transition stages as a roadmap to the future. • A transition plan to model evolution stages through which the enterprise must evolve.

  8. EA is different than system architecture

  9. Community Planning • EA provides “community planning” for system of systems while component systems evolve autonomously. Provides standards, design patterns, and best practices for community common requirements. Areas of common interest include: • Hardware – standardization reduces training, maintenance and acquisition costs. • Virtualization foster sharing of physical facilities -- normal operations and COOP. • Networking • Data Standards – ensure that data sets can be shared, and linked • Geospatial master data management – virtually unified, but geographically dispersed • Common data schema. • Communications protocols • Authentication, authorization, and access control allows the right people to get the right information, at the right time. But keep the wrong people away. • Ontology describes services and conditions offered by enterprise systems. • Registry for providers to advertise, and consumers to find services. • EA modeling standards -- Federal Enterprise Architecture framework plus DoDAF enable sharing with FAA and DOD partners.

  10. Backup Slides

  11. DOC/OMB Registered Segments

  12. FEA Reference Models

  13. NOAA CIO Conceptual EA • Latest Version • Subject to change

  14. Current NOAA Architectural Layers NOAA Business Operations Manual (BOM) (see www.ppi.noaa.gov/PPI_Capabilities/Documents/BOM.pdf) NOAA Strategic Plan, Annual Guidance Memorandum (AGM), CIO Priority Initiatives, etc. OMB FEA Rqmts FTF & LOBs, etc. GPRA, OMB PART, exhibit 300 PRM Mappings NOAA Functional Model (FuMo) Exhibit 300 DRM mappings, FIS IA, IOOS, etc. NOAA Conceptual SOA GEO-IDE, Exhibit 300 SRM mappings Technical Reference Model (TRM) Security Architecture & Rqmts

  15. NOAA ConceptualTarget Architecture 15

  16. Conceptual Data Architecture Example Artifacts Standardization Areas • Logical Data Model • Physical Data Schema • Semi & unstructured data types • XML schemas • Product catalog Data Description Data & Data Assets • Discovery level metadata • Taxonomies • Ontologies • Mappings to: • - processes • - service components Data Context Taxonomies • Web services specs • Access protocols • Content search services • Subscription services Data Sharing Query points & exchange Conceptual Data Architecture (From FEA Data Reference Model)

  17. Conceptual Infrastructure Services Layer (Draft) Draft 17

More Related