NCOIC Deliverables by Scott Simkin

Network Centric Operations Industry Consortium

The Role of NCOIC Deliverables October 2007

Approved for Public Release Distribution Unlimited DRAFT V2.1-2007-10-09

The purpose of this document is to describe the NCOIC deliverables, their fundamental use from a customer perspective, and how the deliverables work with each other to form an integrated suite of systems engineering and design tools. The NOTES pages are intended for use as speakerâ&#x20AC;&#x2122;s notes when briefing the slides, and also intended to provide additional insight to readers seeking additional insight into the role and value of the NCOIC technical deliverables.

NCOIC Assists Customers

in obtaining interoperable solutions: The Role of NCOIC Deliverables CUSTOMER GOALS

MISSIONS TO ACHIEVE GOALS

MISSION NEEDS

NCO Initiatives Database SCOPE Model NCOIC Interoperability Framework (NIF™)

The NCOIC deliverables work together to assist in achieving interoperable systems, services, and capabilities

SOLUTIONS TO NEEDS (EXISTING AND FUTURE)

Typical Process Steps to Solutions:

1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation 4. Design Synthesis

N I F

B B

N C A T

5. Design Verification 6. Deployment 7. Support 8. Upgrade or Disposal

RESULTING CAPABILITIES & SERVICES Supports End-to-End Quality of Service

Network Centric Analysis Tool

(NCAT™)

Building Blocks (BB)

Modeling & Simulation and Demonstrations of missions, needs, & solutions Test & Evaluation of solutions & results

The NCOIC assists our customers, both government and civil, in obtaining interoperable systems, services, and capabilities. As depicted in grey across the top of this slide, our customers have various goals. They’ve identified various missions to achieve those goals. Each mission has needs. The solutions to these needs—systems (hardware, software) services, facilities, personnel, and materiel—are usually developed according to Systems Engineering process steps #1 - #8, which you see outlined under “Solutions to Needs.” The typical focus of industry is on these solutions to needs, which is but a means to the true goal of most customers: the resulting services and capabilities provided by interoperable solutions to needs. The NCOIC has developed a set of deliverables (shown in blue text) that assists in obtaining interoperable solutions. The NCO Initiatives Database tracks major customer initiatives for Network Centric Operations (NCO), Network Centric Warfare (NCW), Net-Enabled Capability (NEC), Internet readiness, or compatibility with customer-owned or shared networks ranging from local area networks up to global wide area networks. NCOIC recognizes that regardless of the name used, the capability desired is interoperability The SCOPE Model helps to characterize systems & organizations along interoperability dimensions in order to understand details of gaps to be overcome and strengths to be leveraged. The NCOIC Interoperability Framework (NIF™) provides patterns & guidance for potential solutions in the form of recommended standards, with implementation guidance and key success metrics for Communications Infrastructures, Information Infrastructures, Service-Oriented Architectures, Semantic Interoperability, Information Assurance, etc. The Building Blocks (BB) provides a catalog of NIF-Compliant Off-The-Shelf products. The Network-Centric Analysis Tool (NCAT™) provides an assessment of reaching interoperability goals. End-to-End Quality of Service evaluates the resulting quality of operations in missions, plus the quality of information and quality of networks required to obtain the resulting services and capabilities. Modeling & Simulation and Demonstrations allow Test & Evaluation of missions, needs, solutions, and results on terms of measures of performance and the resulting impact on measures of effectiveness. 2

NCOIC Assists Customers

in obtaining interoperable solutions: Process Steps to Solutions CUSTOMER GOALS

MISSIONS TO ACHIEVE GOALS

MISSION NEEDS

SOLUTIONS TO NEEDS (EXISTING AND FUTURE)

RESULTING CAPABILITIES & SERVICES

Typical Process Steps to Solutions:

Choosing the Right Solutions: • Analysis of alternatives – – – – –

Acquisition & support costs Schedule needs Risk mitigation Technology limits Operational & cultural impact

• Deriving requirements for the chosen approach – – – –

Performance Cost Schedule Risk

• Validating that those are the “right” requirements

1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation

Iterate as appropriate

4. Design Synthesis 5. Design Verification 6. Deployment 7. Support 8. Upgrade or Disposal 3

The solutions to mission needs are usually developed according to systems engineering process steps. The solutions to needs may be accomplished with new systems and new services, but are often achieved by enhancing existing systems and services with new capabilities, with the “proper mix” established via an analysis of alternative solutions. Process step #1 is typically conducted by the customer with inputs from industry that considers such factors as acquisition and support costs (both near-term and life cycle), schedule needs, risk mitigation, technology limits, and other operational doctrine and cultural factors of importance to a customer (such as DOTMLPF for the US DoD: Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel and Facilities). The typical remaining process steps to develop the selected solutions are detailed below. The process steps are often iterative—lessons learned from trying to accomplish any particular step may show the need to go back and re-evaluate the results from prior process steps. Likewise, a change in goals, missions, or mission needs may require iteration and re-visitation of prior steps in the process of developing solutions. For each selected solution resulting from the analysis of alternatives, system requirements are derived from mission needs (process step #2: “Requirements Derivation”). The term “requirements” in this step includes performance, cost, schedule, and risk requirements. Lower-level requirements for component portions of each system are then derived from the higher-level system requirements. The next process step is to validate that the requirements are correct (process step #3: “Requirements Validation”) in the sense that all mission needs will be satisfied if all requirements are met for all associated systems and services. Then for each system/service solution, lower-level requirements are validated to assure that the system-level requirements are met if all lower-level requirements are met, and so on for each level of requirements.

NCOIC Assists Customers

in obtaining interoperable solutions: Process Steps to Solutions CUSTOMER GOALS

MISSIONS TO ACHIEVE GOALS

MISSION NEEDS

SOLUTIONS TO NEEDS (EXISTING AND FUTURE)

RESULTING CAPABILITIES & SERVICES

Typical Process Steps to Solutions:

Building the Selected Solutions: • Design of new or upgraded systems and services – Trade studies – Standards selection – Implementation guidance for consistency & interoperability

• Verifying that the design meets requirements Applying the Solutions: • Deployment • Support • Upgrade • Disposal

1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation

Iterate as appropriate

4. Design Synthesis 5. Design Verification 6. Deployment

Iterate as appropriate

7. Support 8. Upgrade or Disposal 4

A significant process step is to design the new or upgraded systems and services (process step #4: “Design Synthesis”). The relative importance of (or weighting factors for) performance, cost, schedule, and risk requirements are established, as well as metrics or evaluation criteria for measuring the satisfaction of those requirements. Alternative means of achieving the performance, cost, schedule and risk requirements may be considered, and the “best” choice—balanced across the relative evaluated weight of all of the requirements—is selected as the preferred option in a trade study. The next process step is to verify that the resulting design meets requirements (process step #5: “Design Verification”). This may involve analysis or inspection of the design, and testing of prototypes or models as necessary to “prove” with reasonable confidence that allocated requirements are met by the design. The next process steps are to deploy and support the systems (hardware, software) and services (process step #6: “Deployment” and process step #7: “Support”). This includes not only systems (hardware, software) and services but also implementation of resulting changes to operational doctrine and cultural factors including administrative and logistics processes. Although the bottom step appears to be last (process step #8: “Upgrade or Disposal”) it is often the beginning of another new iteration of most, if not all, of the above process steps. Changes in customer goals, missions, and needs may initiate a need for upgrade or disposal of solutions, simple passage of time may dictate this step via such factors as technology obsolescence, increasing cost of ownership, legal implications, competitiveness, and personnel or facility changes.

NCOIC Assists Customers

in obtaining interoperable solutions: The NCO Initiatives Database CUSTOMER GOALS

MISSIONS TO ACHIEVE GOALS

MISSION NEEDS

NCO Initiatives Database SCOPE Model NCOIC Interoperability Framework (NIF™)

The NCO Initiatives Database tracks major customer initiatives and programs: – Interoperability initiatives for Net-Centric Operations (NCO), Network Centric Warfare (NCW), Net-Enabled Capability (NEC), Internet readiness, or compatibility with customer-owned or shared networks

SOLUTIONS TO NEEDS (EXISTING AND FUTURE)

Typical Process Steps to Solutions:

1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation 4. Design Synthesis

N I F

B B

5. Design Verification 6. Deployment 7. Support 8. Upgrade or Disposal

N C A T

RESULTING CAPABILITIES & SERVICES Supports End-to-End Quality of Service Network Centric Analysis Tool (NCAT™) Building Blocks (BB)

Modeling & Simulation and Demonstrations of missions, needs, & solutions Test & Evaluation of solutions & results

Now that we have defined all the terms on the chart, let’s determine how NCOIC deliverables help achieve customer goals: The NCO Initiatives Database (shown in blue text) tracks major customer initiatives and programs (commercial, government and military) that address some customer NCO goals and missions, needs for those missions, and policy regarding the kinds of solutions to those needs. Solutions to mission needs—systems (hardware, software) services, facilities, personnel, and materiel—are usually developed according to Systems Engineering process steps #1 - #8. The customer initiatives and programs in the NCO Initiatives Database may address all of these steps, but usually detail very specific guidance or policy regarding conduct of analysis of alternatives (#1), requirements derivation (#2) and validation (#3), and especially design synthesis (#4) processes. Note that the major customer initiatives and programs may involve existing or legacy components, new components, or the evolution from existing (“as-is”) conditions to future (“to-be”) conditions. The NCO Initiatives Database includes interoperability initiatives for Network Centric Operations or Net-Centric Operations (NCO), Network Centric Warfare (NCW), Net-Enabled Capability (NEC), Internet readiness, or compatibility with customer-owned or shared networks ranging from local area networks up to global wide area networks (for example: DoD NR-KPP, U.S. GIG, NATO NEC, Internet2, IPv4/IPv6, etc.) The NCOIC is composed of more than 100 global leaders of industry, government, and academia, thus providing a unique repository for a wide range of initiatives (commercial, government and military).

NCOIC Assists Customers

in obtaining interoperable solutions: The SCOPE Model CUSTOMER GOALS

MISSIONS TO ACHIEVE GOALS

MISSION NEEDS

NCO Initiatives Database

Systems, Capabilities, Operations, Programs & Enterprises (SCOPE) Model NCOIC Interoperability Framework (NIF™)

The SCOPE Model: – An analytical tool that characterizes systems and organizations along interoperability dimensions – Helps to understand gaps to be overcome and strengths to be leveraged – Interoperability across various nodes (similar or dissimilar) can be assessed, especially for Legacy systems

SOLUTIONS TO NEEDS (EXISTING AND FUTURE)

Typical Process Steps to Solutions:

1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation 4. Design Synthesis

N I F

B B

5. Design Verification 6. Deployment 7. Support 8. Upgrade or Disposal

N C A T

RESULTING CAPABILITIES & SERVICES Supports End-to-End Quality of Service Network Centric Analysis Tool (NCAT™) Building Blocks (BB)

Modeling & Simulation and Demonstrations of missions, needs, & solutions Test & Evaluation of solutions & results

The Systems, Capabilities, Operations, Programs, and Enterprises (SCOPE) Model is an analytical tool that can be used to characterize systems & organizations along interoperability dimensions in order to understand specific details of gaps to be overcome and strengths to be leveraged. Through SCOPE Model analysis, the aspects of interoperability across various nodes (similar or dissimilar) can be assessed, especially for legacy systems. More specifically, the SCOPE tool that allows customers and companies to characterize customer goals, missions, and mission needs and capabilities in interoperability-relevant aspects or capability of a system in terms of a set of dimensions. Solutions to mission needs—systems (hardware, software) services, facilities, personnel, and materiel—are usually developed according to Systems Engineering process steps #1 - #8. The SCOPE model may provide useful information for all of these steps, but especially in the conduct of analysis of alternatives (#1), requirements derivation (#2) and validation (#3), and design synthesis (#4) processes. The four top-level dimensions are Net-Readiness (ability to deliver capability in a network context), Capability/Domain-Independent Scope (range of scope or context supported), Capability/Domain-Dependent Scope (the nature, quantity, quality, speed, etc., of capability provided to meet operational needs), and Technical/Economic Feasibility (the feasibility or risk associated with providing capability). The Capability/Domain-Independent and Capability/Domain-Dependent Scope dimensions define the “What”, “Why”, and “Where” of a capability (i.e., what specific capability is needed, in what context, and for what purpose). The Net-Readiness dimensions define the “How” of a capability (i.e., how can that capability be implemented technically and delivered over a network). The Technical/Economic Feasibility dimensions define the “How Much” of a capability (i.e., given technical and economic tradeoffs, how much of the ideal technical solution is feasible and affordable). The dimensions are organized hierarchically so that each dimension may contain sub-dimensions, which may in turn contain even lower level dimensions, and so on. 6

NCOIC Assists Customers

in obtaining interoperable solutions:

NCOIC Interoperability Framework (NIF™) CUSTOMER GOALS

MISSIONS TO ACHIEVE GOALS

MISSION NEEDS

NCO Initiatives Database SCOPE Model

NCOIC Interoperability Framework (NIF™)

The NIF™ provides enabling guidance for net-ready solutions – Principles, frameworks and patterns for NCO solutions – Recommended standards & implementation guidance for communications & information infrastructures, service-oriented architectures (SOA), semantic interoperability, information assurance (IA), etc.

SOLUTIONS TO NEEDS (EXISTING AND FUTURE)

Typical Process Steps to Solutions:

1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation 4. DESIGN SYNTHESIS

N I F

B B

N C A T

5. Design Verification 6. Deployment 7. Support 8. Upgrade or Disposal

RESULTING CAPABILITIES & SERVICES Supports End-to-End Quality of Service Network Centric Analysis Tool (NCAT™) Building Blocks (BB)

Modeling & Simulation and Demonstrations of missions, needs, & solutions Test & Evaluation of solutions & results

The NCOIC Interoperability Framework (NIF™) provides enabling guidance via principles, frameworks and patterns for NCO solutions in the form of recommended standards with implementation guidance and key success metrics for Communications Infrastructures, Information Infrastructures, Service-Oriented Architectures, Semantic Interoperability, Information Assurance, etc. Solutions to mission needs—systems (hardware, software) services, facilities, personnel, and materiel—are usually developed according to Systems Engineering process steps #1 - #8. The NIF may provide useful information for all of these steps, but especially in the design synthesis (#4) process. The information provided by the NIF is intended to complement the reference architectures being developed via various government entities (departments, ministries, and services - defense and civil) and the systems engineering processes and tools already resident in engineering firms. Thus, NIF affords interoperability implementation guidance to allow different firms to develop system elements/nodes interoperable with systems/nodes being developed by others. The NIF is implemented as a development framework that helps system architects and system engineers to embed interoperability starting from requirements using resources such as artifacts, patterns, technology or methodology. Whenever possible, those resources are based upon standards. Recognizing that a single framework cannot address all the needs of the many disciplines involved by systems interoperability, the NIF “framework of frameworks” supports the creation and integration of specialized subframeworks for communications, information, security, etc. Having identified the Service concept as a key concept for interoperability, NIF enforces the use of service orientation and fosters the SOA approach as preferred for information systems. At lower levels, Services are provided as references for key infrastructure (e.g. web-services). At upper level, Services support capabilities for key mission areas (e.g. Sense and Respond Logistics, Mobile Emergency Communications Interoperability, etc.). Having identified the protocol concept as a another key interoperability concept, NIF provides specific guidance for protocols through the use of Protocol Functional Collections (PFCs) patterns. The PFCs provide references for specific “open standards” and implementation guidance for their use. 7

NCOIC Assists Customers

in obtaining interoperable solutions: Building Blocks Verification & Catalog CUSTOMER GOALS

MISSIONS TO ACHIEVE GOALS

MISSION NEEDS

NCO Initiatives Database SCOPE Model NCOIC Interoperability Framework (NIF™)

The Building Blocks (BB) initiative addresses NIF-Compliant Off-The-Shelf products, including: – Self-Verification Criteria for candidate re-usable off-the-shelf products – BB Catalog on a public web-site, providing a database of certified BB entries available for inquiry by member and public entities

SOLUTIONS TO NEEDS (EXISTING AND FUTURE)

Typical Process Steps to Solutions:

1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation 4. DESIGN SYNTHESIS

N I F

B B

N C A T

5. DESIGN VERIFICATION 6. Deployment 7. Support 8. Upgrade or Disposal

RESULTING CAPABILITIES & SERVICES Supports End-to-End Quality of Service Network Centric Analysis Tool (NCAT™)

Building Blocks (BB)

Modeling & Simulation and Demonstrations of missions, needs, & solutions Test & Evaluation of solutions & results

Solutions to mission needs—systems (hardware, software) services, facilities, personnel, and materiel—are usually developed according to Systems Engineering process steps #1 - #8. The Building Blocks (BB) initiative (shown in blue text) assists in the design synthesis (#4) and design verification (#5) processes with the goal of obtaining interoperable solutions through use of NIF-compliant off-the-shelf (OTS) products. As a complement to the NIF, the NCOIC has developed certification criteria regarding NIF-identified characteristics of interoperable capability for OTS products (e.g. commercially available products, public domain offerings, and/or government developed items). These certification criteria may be used by entities (members and non-member companies and agencies) that wish to identify and certify re-usable OTS products that may serve as candidate Building Blocks for specific design solutions. Those wishing to check the availability of interoperable elements may use this database for research or validation. The NCOIC Building Blocks initiative is based on a Self-Verification program. In general, the company (or agency) choosing to have their product offering(s) certified registers their intent to pursue certification via the Certification Criteria. The company or agency then executes the certification protocols, assembles the evidence of certification, and submits their completed application for self-verification in an audit review. Once verified, the submitting organization is granted an NCOIC trademark license acknowledging their offering as an “NCOIC Certified Interoperability Building Block” subject to license restrictions. The NCOIC has developed a Building Block catalog that is available via the NCOIC public web-site. This site provides a database of certified Building Block entries available for inquiry by member and public entities. This catalog will provide cross reference to specific NCOIC NIF patterns, certification criteria, self-verification status as well as certification from other entities, and links to web-sites for the “off the shelf” products. The BB Catalog may contain candidate entries that have not (yet) been subjected to the certification process. The NCOIC provides a supplier/vendor neutral forum for Building Block references, and does not favor any given market offering over another. The goal is to identify a wide number of interoperable building blocks that help enable interoperability for the benefit of our members, government agencies, other industry representatives, and academic communities.

NCOIC Assists Customers

in obtaining interoperable solutions:

Network Centric Analysis Tool (NCAT™) CUSTOMER GOALS

MISSIONS TO ACHIEVE GOALS

MISSION NEEDS

NCO Initiatives Database SCOPE Model NCOIC Interoperability Framework (NIF™)

The Network Centric Analysis Tool (NCAT™) provides an assessment of reaching interoperability goals – Provides feedback in development and iterative improvements to assist design, implementation, and acquisition efforts – A positive NCAT assessment provides ample confidence that the system can operate in a network centric environment

SOLUTIONS TO NEEDS (EXISTING AND FUTURE)

Typical Process Steps to Solutions:

1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation 4. Design Synthesis

N I F

B B

N C A T

5. DESIGN VERIFICATION 6. Deployment 7. Support 8. Upgrade or Disposal

RESULTING CAPABILITIES & SERVICES Supports End-to-End Quality of Service

Network Centric Analysis Tool

(NCAT™) Building Blocks (BB)

Modeling & Simulation and Demonstrations of missions, needs, & solutions Test & Evaluation of solutions & results

The Net Centric Analysis Tool (NCAT™) provides an assessment of reaching interoperability goals in customer missions, mission needs, and solutions to needs. The NCAT helps to measure the net-centric interoperability of the resulting systems. Not only does NCAT provide a snapshot of the progress in development of a system, it provides feedback and “closes the loop” for iterative improvements. A positive NCAT assessment can provide ample confidence that the system can operate in a network centric environment. Solutions to mission needs—systems (hardware, software) services, facilities, personnel, and materiel—are usually developed according to Systems Engineering process steps #1 - #8. The NCAT may provide useful evaluations in any of these steps, but especially in conduct of the design verification (#5) process. The NCAT analyzes architectures, frameworks, and reference models against a common set of user-specified evaluation criteria. NCAT supports selection of appropriate architectures, comparison to each other, and assessing compliance with specific architecture guidelines and reference models via a web based tool that is capable of handling multiple sets of criteria, users, programs, and time slices. This tool also provides for extensive reporting, and assists design and implementation communities as well as the acquisition community. NCAT adopts a questionnaire/survey based method and works to remove any subjectivity in scoring by providing criteria points on either a fixed scale or else a weighted variable scale. Each user has the option to customize the questions to suit their desired outcome. NCAT allows a tree-structured questionnaire drawing from a multiplicity of questionnaires and configurations, and program specific customizations of a content database. The initial NCAT content was based on the US DoD OSD/NII’s net-centric checklist, but is being expanded to include questionnaires based on the NCOIC’s SCOPE Model, the US DoD Net-Ready Key Performance Parameters (NR-KPPs), the NATO Capability Maturity Model (CMM), other key customer interoperability initiatives in the NCO Initiatives Database, and userspecified criteria.

NCOIC Assists Customers

in obtaining interoperable solutions:

Modeling & Simulation, Test & Evaluation CUSTOMER GOALS

MISSIONS TO ACHIEVE GOALS

MISSION NEEDS

NCO Initiatives Database SCOPE Model NCOIC Interoperability Framework (NIF™)

The NCOIC uses modeling, simulation, and demonstration techniques and laboratories – To test and evaluate increased levels of interoperability from use of NCOIC deliverables – To recommend Modeling & Simulation standards – To verify the NCOIC deliverables

SOLUTIONS TO NEEDS (EXISTING AND FUTURE)

Typical Process Steps to Solutions:

1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation 4. Design Synthesis

N I F

B B

5. Design Verification 6. Deployment 7. Support 8. Upgrade or Disposal

N C A T

RESULTING CAPABILITIES & SERVICES Supports End-to-End Quality of Service Network Centric Analysis Tool (NCAT™) Building Blocks (BB)

Modeling & Simulation and Demonstrations of missions, needs, & solutions Test & Evaluation of solutions & results

The NCOIC uses modeling, simulation, and demonstration techniques and laboratories in order to test, validate and/or demonstrate increased levels of interoperability resulting from use of NCOIC deliverables. Key goals are to quantitatively demonstrate effectiveness of NCOIC concepts and deliverables (especially under simulated “Real-World” or field conditions), and to foster interoperability of NCOIC member, academic, commercial and government labs. The NCOIC will also identify and recommend modeling/simulation standards for use in demonstrations of interoperability. These will be Open (non-proprietary) standards that are internationally-recognized. Candidate Standards Include: HLA (High-Level Architecture, IEEE 1516), DIS (Distributed Interactive Simulation, IEEE 1278.1a), Extensible Modeling & Simulation Framework (XMSF), and the Standard Simulation Architecture (SSA). The NCOIC will also survey potential for interconnection of Consortium members’ simulation / demo labs, and survey potential for connection of Consortium members’ simulation / demo labs with government(s) customers’ labs.

NCOIC Assists Customers

in obtaining interoperable solutions: The NCOIC Lexicon CUSTOMER GOALS

MISSIONS TO ACHIEVE GOALS

MISSION NEEDS

NCO Initiatives Database SCOPE Model NCOIC Interoperability Framework (NIF™)

The NCOIC Lexicon defines terms and expressions that have specific meaning in NCOIC – Provides an online Wiki for collection of new NCOIC-specific terms and update or review of items by all NCOIC technical members – Provides links to external and public definitive sources for general terms and definitions

SOLUTIONS TO NEEDS (EXISTING AND FUTURE)

Typical Process Steps to Solutions:

1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation 4. Design Synthesis

N I F

B B

5. Design Verification 6. Deployment 7. Support 8. Upgrade or Disposal

N C A T

RESULTING CAPABILITIES & SERVICES Supports End-to-End Quality of Service Network Centric Analysis Tool (NCAT™) Building Blocks (BB)

Modeling & Simulation and Demonstrations of missions, needs, & solutions Test & Evaluation of solutions & results

The NCOIC Lexicon defines terms and expressions that have NCOIC-specific meaning in texts published by the NCOIC and that, if left undefined by the Lexicon, may cause costly misinterpretation. This is accomplished via an online Lexicon Wiki. The NCOIC Lexicon Wiki is a dynamic collection tool used by NCOIC members for collection of new items and the update & review of exiting items. External users of the Wiki (i.e. customer organizations and companies that are not members of the NCOIC) can recommend new terms or text modifications via e-mail to the NCOIC Lexicon Custodian Working Group, as the Wiki is publicly available on a read-only basis. Note that common terms, and terminology defined by other organizations are not detailed in the NCOIC Lexicon Wiki– instead, the wiki provides an online link to the definitive source(s).

NCOIC Assists Customers

in obtaining interoperable solutions: End-to-End Quality of Service Organizational Quality Drivers

Aligned Operations

People & Process

Aligned Procedures Knowledge/Awareness of Actions Semantic/Information Interoperability

Information Services

Data/Object Model Interoperability Connectivity & Network Interop. Physical Interoperability

ENDTOEND

NEEDS

Harmonized Strategy/Doctrines

Network Transport

CONSTRAINTS

Layers of Interoperability

Political or Business Objectives

QUALITY OF SERVICE

Technical Quality Drivers 12

â&#x20AC;&#x153;Interoperabilityâ&#x20AC;? is a key topic with multiple levels. In any organization, the people and processes must work in an acceptable level of harmony. This requires interoperable information services in the various systems supporting those people and processes. The network infrastructure must, in turn, provide the requisite communication services (voice, data, video) to efficiently support the people, processes, and systems. Using the analogy of a plumbing system, the network transport layers are like the pipes, the information service layers are like the contents of the pipes, and the people and processes are the like consumers of the plumbing system. Quality factors are important at each level. Of key importance for customer goals and missions are Quality of Operations needs for political or business objectives, harmonized strategy or doctrines, aligned operations, aligned procedures, and knowledge/awareness of actions by people and processes. The Quality of Information Service must support the required Quality of Operations. Of key importance to solutions are knowledge/awareness or discoverability of information, information transport interoperability, and format or data/object model interoperability. The Quality of Networks must support the required Quality of Information. Of key importance to solutions are connectivity (either fixed or mobile users of a fixed or mobile network infrastructure), network interoperability, and physical interoperability. The NCOIC uses the term End-to-End Quality of Service (E2E QoS) to represent a coordinated capability including Quality of Operations, Quality of Information, and Quality of Networks in the resulting capabilities and services. In theory, E2E QoS is driven by a top-down approach in order to satisfy political or business objectives. But real-world constraints of resulting cost impact, schedule impact, technology limitations, and risk provide a bottom-up practical adjustment to the theoretical needs. The resulting balance of need vs. cost/schedule/technology/risk sets the optimal level of E2E QoS.

NCOIC Assists Customers

in obtaining interoperable solutions: End-to-End Quality of Service CUSTOMER GOALS

MISSIONS TO ACHIEVE GOALS

MISSION NEEDS

Key Needs: • Political or business objectives • Harmonized strategy or doctrines • Aligned operations • Aligned procedures • Knowledge/awareness of actions by people and processes Key Attributes: • Urgency (timeliness) • Priority (degree of cooperation) • Information Assurance (IA) fluidity of response, clarity of understanding, ubiquity or extent of influence, accuracy

(EXISTING AND FUTURE)

RESULTING CAPABILITIES & SERVICES

Typical Industry Focus

Typical Customer Focus

Quality of Operations

SOLUTIONS TO NEEDS

Quality of Information Service Quality of Network Service

End-to-End = Quality of Service

Key Needs: Key Needs: • Discoverability • Connectivity (fixed, mobile) • Semantic interoperability • Network interoperability • Format interoperability • Physical interoperability • Transport interoperability Key Attributes: Key Attributes: • Urgency (transport lag or delay, • Urgency (data/topic latency, jitter, packet loss, packet errors) service response time, • Priority (class of service, application timeliness) differentiated service, • Priority (precedence of user precedence, preemption, requests, data, and services) guaranteed service) • Information Assurance (IA) • Information Assurance (IA) –Data Trust: integrity & availability –Data Trust: (fault tolerance) (fault tolerance, accessibility) –Security: (encryption, –Security: (data confidentiality, authentication, authorization, authentication, access control, intrusion detection, access 13 non-repudiation) control)

As depicted with the black boxes, our customers have various goals. They’ve identified various missions to achieve those goals. And of course, each customer has both unique missions and missions which require coordination with similar missions performed by other customers. Each customer mission has needs—some needs that are unique to that mission, and other needs that are common across missions. The solutions to these needs are usually in the form of systems (hardware, software), services, facilities, personnel, and materiel. The typical focus of industry is on the solutions to needs, which is but a means to the true goal of most customers: the resulting services and capabilities provided by the solutions to needs. Of key importance for customer goals and missions are Quality of Operations (QoOps) needs for political or business objectives, harmonized strategy or doctrines, aligned operations, aligned procedures, and knowledge/awareness of actions by people and processes. These are usually expressed in terms of urgency (timeliness), priority (degree of cooperation), and Information Assurance (IA: accuracy, clarity of understanding, fluidity of response, and ubiquity or extent of influence). The Quality of Information Service (QoInfo) must support the required Quality of Operations. Of key importance to solutions are knowledge/awareness or discoverability of information, semantic interoperability, format or data/object model interoperability, and information transport interoperability. These are usually expressed in terms of urgency (data/topic latency, service response time, and application timeliness requirements), priority or precedence (of user requests, data, and services), and Information Assurance (IA). Typical IA elements are Data Trust: integrity & availability (fault tolerance, accessibility) and Security: (data confidentiality, requester & sender authentication & non-repudiation). The Quality of Networks (QoNet) must support the required Quality of Information. Of key importance to solutions are connectivity (either fixed or mobile users of a fixed or mobile network infrastructure), network interoperability, and physical interoperability. These are usually expressed in terms of urgency (transport lag or delay, jitter, packet loss, packet errors), priority (class of service, differentiated service, precedence, preemption, guaranteed service), and Information Assurance (IA) Typical elements are Data Trust: fault tolerance and Security: encryption, intrusion detection, authentication, authorization, and access control. The NCOIC uses the term End-to-End Quality of Service (E2E QoS) for coordinated Quality of Operations, Quality of Information, and Quality of Networks in the resulting capabilities and services. 13

NCOIC Goal Net-Enabled Future

Stovepiped Systems, Point-to-Point Networks

This slide is intended for use as a closing or “get off the stage” speech. As depicted in the upper right corner, the goal of the future is a net-enabled environment where all information systems plug into a network, and where all users can work together to obtain and use that information. As depicted in the lower left corner, today’s systems are usually optimized for a specific objective, and are not fully net-enabled. The goal of the NCOIC is to accelerate the adaptation of today’s systems to participate in a more netcentric approach, and to accelerate the adoption of net-centric approaches in the development of future systems.