1 / 10

Overarching Architecture v2.5 Architecture Workshop 1 June 2006

Overarching Architecture v2.5 Architecture Workshop 1 June 2006. Olaf Kruidhof NC3A Senior Systems Architect Project manager OA v2.5. Lead-points supporting Transformation. Services as the unifying paradigm Information as the central subject

holst
Download Presentation

Overarching Architecture v2.5 Architecture Workshop 1 June 2006

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. Overarching Architecture v2.5Architecture Workshop 1 June 2006 Olaf Kruidhof NC3A Senior Systems Architect Project manager OA v2.5 NATO / EAPC Unclassified

  2. Lead-points supporting Transformation • Services as the unifying paradigm • Information as the central subject • Objectives as the common foundation for OA and CBP • Comprehensive and coherent set of architectures supported by • Systematic and logical causal reasoning • Flexible tool environment NATO / EAPC Unclassified

  3. Resource & Capability Planners Related to Defence Planning Fellow Architects REQUIREMENTS C3CAPABILITY TO MATCH NATO NEEDS C3OVERARCHINGARCHITECTURE BaselineArchitecture RESOURCE PLANNING - SRB (NATO FUNDED PROGRAMMES) TargetArchitectures ReferenceArchitectures ARMAMENTS PLANNING - CNAD (MULTINATIONAL PROGRAMMES) National parties FORCE PLANNING – ACT/MC (NATIONS’ CAPABILITIES) Systems Developers Operational Users NATO / EAPC Unclassified

  4. What people need to accomplish & how they collaborate What systems need to do & under which conditions What information need be available & how to distribute Approach NATO Architecture Framework = User’s View Doctrine Operational Concept Mission types System characteristics on physical nodes Architecture Engineering Methodology = Builder’s View NATO / EAPC Unclassified

  5. Mission Space Information Application Technical Infrastructure Aspect Areas Abstraction levels Direction and impact from the environment Why are we doing it? The concepts and functionality What do we want? Logical solutions How do we ideally want it to work? Feasible solutions With what can it actually work? Migration path When can we do what? Architecture viewpoint Security and Governance Architecture Engineering Methodology: Supporting transformation to NNEC Why? Contextuallevel What? Functioanlitylevel How? Construction level With what? Implemenatio level When? Transformationlevel NATO / EAPC Unclassified

  6. Execution Responsibility of Interoperability Sub-Committee(AC/322-SC/2) Policy Responsibility of NC3 Board Target Architectures Reference Architectures Operational View Systems View Technical View Nato’s architectures NAF Design Implementation OverarchingArchitecture NC3TA – Volume 4 NCSP & 5 NCOE NC3TA – Volume 2 Products – NATO Interoperability Environment Responsibility of Information Systems Sub-Committee(AC/322-SC/5) NATO C3 Interoperability Framework NATO / EAPC Unclassified

  7. Key features OA v2.5 • Top-down description of the requirements for the NATO enterprise-wide To-Be situation • Incorporating the NNEC paradigm • Based on a rigorous line of reasoning behind the diagrams • Mapped against As-Is systems and Reference Architectures • Allows for assessment of conformity of current situation to the envisioned situation • Allows for provision of guidance to future developments (NATO & nations) • Provide textual descriptions and graphical presentation of: • Which systems do we need: Envisioned functionality of CIS at strategic, tactical and operational nodes • How do they interface: Envisioned interfaces between system services as captured in CIS/Reference Architectures • What do they exchange: Unambiguous semantic definitions of the information elements exchanged • How well do they need to operate: Quality requirements for system services, e.g. security, availability and performance • NID and NAF v2.0 compliant views • Stored in an open (XML-based) repository that allows for: • Re-use of earlier results • Accumulation and inter-relation of architecture deliverables • Creation of tailored views and reports NATO / EAPC Unclassified

  8. Example Application of OA -Operational Planning Mission Space Information InformationSystems Technical Infrastructure Aspect Areas Abstraction levels Why: Context Starting point Operational Planning Planning situation (COP, SDP) Real situation (OPLAN) What: Functionality Desired effects Requires Operational Services Information Services User Services TI Services 1 1 1 How: Construction Force Structure 2 2 With what: Implementation Forces Procedures Information systems Technical Infra Equipment Derived from 1 NATO / EAPC Unclassified Analysis current systems 2

  9. Summary and Next steps • The Service paradigm is an integral and unifying paradigm in the OA  Brief Item 3 • Information is the key subject • The OA can be queried and analysed to support NATO’s planning processes: • Capability development  Briefs Items 5 & 7 • NNEC CMM  Brief Item 8 • The OA is NAF compliant but more information is available and needed for NNEC  Brief Item 4 • The OA provides a enterprise-wide starting-point with material to be reused an refined at Reference Architecture level  Brief Item 6 • The OA provides the pointers to identification of new technologies and standards  Brief Item 9 NATO / EAPC Unclassified

  10. Questions? Olaf.kruidhof@nc3a.nato.int NATO / EAPC Unclassified

More Related