1 / 11

SICoP Briefing

SICoP Briefing. August 9, 2007. Architecture Federation Pilot Army Chief Information Officer (CIO/G-6) Architecture Operations, Networks and Space (AONS) Directorate, Army Architecture Integration Center (AAIC). Purpose. portfolio management and investment planning activities

awen
Télécharger la présentation

SICoP Briefing

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. SICoP Briefing August 9, 2007

  2. Architecture Federation Pilot Army Chief Information Officer (CIO/G-6) Architecture Operations, Networks and Space (AONS) Directorate, Army Architecture Integration Center (AAIC)

  3. Purpose • portfolio management and investment planning activities • The DoD EAC COP had previously determined that a complex set of diverse information sources need to be tapped into and merged with the assets represented in architectures in order to support portfolio management

  4. Purpose • Integrate knowledge in support of investment decision making by the following stakeholders • Joint Net-Centric Operations Capability Portfolio Manager (JNO CPM) • Joint Focused Logistics CPM • Joint Command & Control (JC2) CPM IT Portfolio Managers at both DoD and Service levels • the Business Transformation Agency (BTA).

  5. Classification Ontology • Engage a COI to build an ontology that is suitable for classifying the diverse collection of artifacts • common service capabilities and their related definitions • An architectural model of a sub-set of currently deployed Army tactical enterprise services, developed in DODAF constructs • An architectural model of a sub-set of Army tactical enterprise services as planned for future deployment • An architectural model of a sub-set of supporting DoD IT infrastructure • An EXCEL spreadsheet containing a set of Army systems and related attributes

  6. Semantic Wiki • A semantic wiki will be used to develop the classification ontology • A Community of Interest will be formed on the wiki • Stakeholders will collaborate over the definition of the ontology • The ontology will be published to a repository

  7. Repository • The ontology will be imported into a commercial repository • All of the architectural/capability artifacts will be imported into the repository

  8. Semantic Mapping • A semantic mapping tool will be used to match all of the artifacts to the semantically correct nodes in the ontology

  9. Result • Having all of the artifacts related to the ontology will facilitate the answering of the following kinds of questions

  10. What are the capabilities and capability increments of interest?What are the representative echelons of the federation: nodes and ”edges”?For each echelon:What are the minimum and desired capabilities, and when are these needed?What are the points of intersection/interfaces between echelons?Who are the providers (POR or otherwise) and consumers? What are the federation alternatives for each point of interface?For each provider:What increment of a given capability does it offer and what capacity does it have to serve consumers by FY?How much will this service cost to procure by FY?How much will this service cost to sustain by FY ?

  11. What dependencies does this service have on other providers by FY? What is the ’interface’ (e.g. protocol) provided for federation with other providers to implement a given enterprise-wide capability? For each ‘interface’:What is that interface’s dependence on lower-level protocols? What are the QoS/transport/bandwidth dependencies? What are the rules for connecting to it? (e.g. information assurance (IA) credentials?) What is the quality/accuracy/timeliness/consistency specification for that interface (e.g. :”we will provide blue force locations that are no more than 5 minutes old within nearest 1000 meters.”)

More Related