11 Service Oriented Architecture (SOA) - Where is the Federal Government Now? John J. Shea Dir, Information Policy & Integration Office of the DoD CIO 28 April 2009

22 Maritime Domain Awareness (MDA)− Real example of the challenges we face Scaling SOA to the Enterprise

33 SMS/ JPSC2 Google Earth MASTER CAS Seaport AIS Data Tripwire E-MIO FASTC2AP CMA LINX TAANDEM Current SECNAV MDA Spiral 1 Architecture Systems to systems approach with point to point data transfer across multiple security domains

44 Federated Core Enterprise Services providing authorized consumers the ability to discover, access and understand shared data, products and services Publish Subscribe SMS/ JPSC2 Google Earth MASTER CAS Seaport AIS Data Tripwire E-MIO FASTC2AP CMA LINX TAANDEM SMS/ JPSC2 Google Earth MASTER CAS Seaport AIS Data Tripwire E-MIO FASTC2AP CMA LINX TAANDEM Transition to net-centric, services-based information sharing architecture….. Future MDA Architecture….

55 …and it needs to scale to support national MDA requirements Federated Core Enterprise Services providing authorized consumers the ability to discover, access and understand shared data, products and services Publish Subscribe Vessel Data People Data Infrastructure Data Cargo Data DHS Systems & Services DOT System & Services DOD Systems & Services DNI System & Services DOJ System & Services International Systems & Services Lots of Sources, Lots of Consumers….

66 MASS SD MSSIS GMMS USCG NAIS SCC-J SMS DRDC Halifax GHMD MASS C5FMASS C2FMASS C3FMASS CPF NORTHCOMMIDAS DOJ’s SeaHawk Charleston, SC GCCS-I3 NAVAIR PandaC4I Suite DISA’s Net-Centric Enterprise Services SecurityService DiscoveryMessaging (Pub/Sub)Content Discovery Enterprise Service ManagementMediationIdentity Management USCG NAIS ONI AMRS SILOANOA DHS iCAV Publishing data in a community defined schema via NCES Subscribing to data via NCES MASTERRMACCMA Current “MDA DS COI” Architecture Begins to address DOD’s needs, but not a national MDA solution In Progress AIS Data Vessel of Interest Data People Data Value-Added Services Hosted at a DECC GMMS DASHAS ADS DECC (Exploited AIS data--Only part of the Vessel Data picture)

77 NCES People Data Infrst. Data Cargo Data Vessel Data People Systems Infrst. Systems Cargo Systems Vessel Systems International ES People Data Infrst. Data Cargo Data Vessel Data People Systems Infrst. Systems Cargo Systems Vessel Systems ICES People Data Infrst. Data Cargo Data Vessel Data People Systems Infrst. Systems Cargo Systems Vessel Systems DHS ES People Data Infrst. Data Cargo Data Vessel Data People Systems Infrst. Systems Cargo Systems Vessel Systems Federal ES People Data Infrst. Data Cargo Data Vessel Data People Systems Infrst. Systems Cargo Systems Vessel Systems National MDA Architecture needs to support all types of data across the U.S Government as well as our partners (foreign and commercial industry) NCES by itself will not scale to meet the national MDA requirements. Other enterprises (ES) must be involved as well. What will “bind” them?

88 NCES People Data Infrst. Data Cargo Data Vessel Data International CES People Data Infrst. Data Cargo Data Vessel Data ICES People Data Infrst. Data Cargo Data Vessel Data DHS ES People Data Infrst. Data Cargo Data Vessel Data Federal ES People Data Infrst. Data Cargo Data Vessel Data National MDA Architecture needs to be based upon common standards, specifications, services to ensure interoperability across multiple enterprises. Common standards, specifications, services are needed but they have to be adopted, implemented to federate the enterprise Global MDA Data Consumers DOT ES DOJ ES State & Local ES Industry ES Common, Industry-Based Standards, Specifications, Services

99 NCES People Data Infrst. Data Cargo Data Vessel Data International CES People Data Infrst. Data Cargo Data Vessel Data ICES People Data Infrst. Data Cargo Data Vessel Data DHS CES People Data Infrst. Data Cargo Data Vessel Data Federal CES People Data Infrst. Data Cargo Data Vessel Data National MDA Architecture needs to be based upon common standards, specifications, services to ensure interoperability across multiple enterprises Global MDA Data Consumers DOT CES DOJ CES State & Local CES Industry CES Common, Industry-Based Standards and Specifications Multiply this example of one domain with a few agencies to the broader challenge of creating a federal enterprise! Things we learned we need: Identity management Access control privileges Standard syntax and semantics for some content (e.g., UCore) Strong governance

10 How do we federate? What is the minimum set of controlling standards, specifications, services needed to “federate” across all the entities in the enterprise(s)? How do we choose common standards, specifications, and services? Who governs the federation? How? Who enforces compliance within the federation? Who provides the “top level” infrastructure? But wait……..

11 But wait…….. Can we really expect the federal government to agree to and adopt a massively scale federation plan? IF we define/execute a COA to support federal federation how long will it take to implement? Will we still be having this conversation in five years? Ten years? Is this even achievable???

12 The Cloud Buzz…….. Tipping point…. –Cloud Computing is real 2-10 Technology –Rob Carter, EVP CIO FedEx –Two years of Hyper-Buzz –Ten years of adoption The next big thing….

13 The Cloud Buzz…….. Obvious benefits… not so obvious implementation Fact: Cloud Computing has the attention of the new Administration –Public –Secure –Federal, State, Local, Tribal - Law Enforcement Federal CIO moving fast….

14 Our Strategy… Continue to evolve the Services Construct to achieve an “Information Advantage for our people and mission partners….” through the establishment of the Service-Oriented Enterprise –Enterprise Guidance Board (EGB) –Establishment of Key Services Identity Management Access Control Access Management

Our Strategy… 15 Services Construct –Update our Department of Defense Net- Centric Services Strategy memorandum to align with EGB activities Strategy for a Net-Centric, Service Oriented DoD Enterprise, March 2007 –Prepare a new Enterprise Services Implementation Guidance document Like we did with DODD g for Data Strategy

16 Our Strategy… Looking towards the future of Cloud Computing – near term: –Keep pace with Federal plans –DISA RACE project –DISA Forge.MIL –Establish DoD CIO outreach Industry, FFRDCs, etc

17 Our Strategy… Establish DoD CIO Cloud Computing Pilots –DoD CIO “Storefront” Lightweight User Composeable Framework Enterprise / Community Portlets – App Store –Enterprise: SSO, Search, Publish, etc –Community: User submitted / Forge.MIL –Publishing into the Cloud will reshape our understanding of Content Management

18 Our Strategy… IaaS / PaaS / SaaS - Commodities Focus on transition –How to move Apps into the Cloud? –What are the pre-cursors / requirements? –Invest in highly reusable tools to migrate current legacy Apps into the DoD Cloud Minimize the risk of transition Easy for PoR to transition

19 We need your help… We need to rethink HOW we are going to achieve the Information Advantage We don’t have the answers… We need your help!!!

20 Thank you for your time and attention