Architecture Tool Vendor’s Day Tool Characterization Template OPS DAS SE CPM JCIDS PPBE Architecture Tool Vendor’s Day Tool Characterization Template 14 March 2011

Tool Characterization Template (see subsequent slides for legends)

Primary Functionality Model Development A model is a simplified representation of a system at some particular point in time or space intended to promote understanding of the real system. Repository / Integration A logical partitioning of data where multiple databases that apply to specific applications or sets of applications reside. Data integration involves combining data residing in different sources and providing users with a unified view of these data. Analysis / M&S A simulation is the manipulation of a model in such a way that it operates on time or space to compress it, thus enabling one to perceive the interactions that would not otherwise be apparent because of their separation in time or space. The use of models, including emulators, prototypes, simulators, and stimulators, either statically or over time, to develop data as a basis for making managerial or technical decisions.

An M&S Taxonomy Modeling& Simulation Concept Exploration Cost EVMS Schedule KPPs Performance Concept/ Technology Development Component Advanced Development Tech Requirements/ Capabilities Definition System-level Architecture Process Risk Funding Parts Planning, Programming & Budgeting Cost Analysis Business Element Modeling& Simulation Acquisition System Development & Demonstration Analysis Requirements Design CDRL Contracts Integration Demonstration Military Production Deployment Production Readiness/LRIP CTR Personnel Suppliers Rate Production/ Deployment Training Operational Evaluation IOT&E Logistics Sustainment LFT&E Test & Evaluation FOT&E Military Utility Assessment

Principal Discipline Architectures (see Architecture Types slides for DoD definitions) System Engineering Systems Engineering is an interdisciplinary approach and means to enable the realization of successful systems. It focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, then proceeding with design synthesis and system validation while considering the complete problem: Operations Cost & Schedule Performance Training & Support Test Disposal Manufacturing Systems Engineering integrates all the disciplines and specialty groups into a team effort forming a structured development process that proceeds from concept to production to operation. Systems Engineering considers both the business and the technical needs of all customers with the goal of providing a quality product that meets the user needs. Core Process (see Core Process slide)

DoD’s 6 Core Processes Operations (OPS) Combatant Command CONOPS Standing communications and operations plans (COMPLAN, O-PLANs) These describe networks, systems, organization, activities, equipment allocation, etc., Joint Capability Integration Development System (JCIDS) Focal point for DoD service chiefs to prioritize needs, shortfalls, and gaps Tightly coupled with DAS and PPBE processes Defense Acquisition System (DAS) Approval process for all acquisitions Milestones reviews Four acquisition categories ~ $ value Architecture data assists go/no-go/contingent decisions Systems Engineering (SE) Technical execution of an acquisitions All programs in the acquisition process must have a Systems Engineering Plan The developed system engineering documents and specifications should flow from and be consistent with the architecture Capability Portfolio Management (CPM) Process for managing $’s by required capabilities Architecture models link investments to the desired effects, tasks, and conditions of capabilities Programming Planning and Budget Execution (PPBE) Annual 5-year budget proposal to Congress Each DoD component develops one and then consolidated by White House to go to Congress Architecture models are used to determine interconnected impacts and to justify the $ request Related to Capital Planning and Investment Control (CPIC) OPS DAS SE CPM JCIDS PPBE

DoD Architecture Types Enterprise Architecture The explicit description and documentation of the current and desired relationships among business and management processes and information technology. (OMB Circular A-130) DoD Enterprise Architecture A federation of descriptions that provides context and rules for accomplishing the mission of the Department of Defense. These descriptions are developed and maintained at the DoD, capability area, and Component levels and collectively define the people, processes, and technology required in the "current" and "target" environments; and the roadmap for transition to the target environment. (Draft DoDD 8210.bb) Reference Model An abstract framework for understanding significant relationships among the entities of some environment. (Reference Model for Service Oriented Architecture 1.0, Organization for the Advancement of Structured Information Standards (OASIS)) Reference Architecture An authoritative source of architecture information (within a domain) that guides and constrains the instantiations of solution architectures by providing rules, principles and holistic models and patterns of the abstract architectural elements together with a common vocabulary, and sets of technical standards/specifications (Derived from OASIS, OMB, and Joint Pub 1-02 References) Component = a. The Office of the Secretary of Defense b. The Military Departments c. The Office of the Chairman of the Joint Chiefs of Staff d. The Combatant Commands e. The Office of the DoD IG f. The Defense Agencies g. The DoD Field Activities h. Such other offices, agencies, activities, and commands established or designated by law, the President, or the Secretary of Defense.

DoD Architecture Types Capability Architecture A set of descriptions that portrays the context and rules required to achieve a desired effect through a combination of doctrine, organization, training, materiel, leadership and education, personnel, and facilities. (Draft DoDD 8210.bb) Segment Architecture Detailed results-oriented (baseline and target) and a transition strategy for a portion or segment of the enterprise. (FEA Practice Guidance, December 2006) Solution Architecture A set of descriptions that portray the fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution. (Draft DoDD 8210.bb) Component* Architecture A framework or structure that portrays relationships among all elements of an organizational grouping within the Department of Defense responsible for safeguarding the national security of the United States. (Draft DoDD 8210.bb) Component = a. The Office of the Secretary of Defense b. The Military Departments c. The Office of the Chairman of the Joint Chiefs of Staff d. The Combatant Commands e. The Office of the DoD IG f. The Defense Agencies g. The DoD Field Activities h. Such other offices, agencies, activities, and commands established or designated by law, the President, or the Secretary of Defense. *e.g., Air Force, Navy & Marine Corps, Army, Defense Logistics Agency, Defense Information Systems Agency, National Geospatial Agency, Business Transformation Agency, National Security Agency, Defense Threat Reduction Agency, Defense Intelligence Agency, Defense Technical Information Center.

DoD’s Nine Business Areas -- Joint Capability Areas (JCA) -- Force Support The ability to establish, develop, maintain and manage a mission ready Total Force. Battlespace Awareness The ability to understand dispositions and intentions as well as the characteristics and conditions of the operational environment that bear on national and military decision-making. Force Application The ability to integrate the use of maneuver and engagement in all environments to create the effects necessary to achieve mission objectives. Logistics The ability to project and sustain a logistically ready joint force through the deliberate sharing of national and multi-national resources to effectively support operations, extend operational reach and provide the joint force commander the Command and Control The ability to exercise authority and direction by a properly designated commander or decision maker over assigned and attached forces and resources in the accomplishment of the mission. Net-Centric The ability to provide a framework for full human and technical connectivity and interoperability that allows all DoD users and mission partners to share the information they need, when they need it, in a form they can understand and act o Protection The ability to prevent/mitigate adverse effects of attacks on personnel (combatant/non-combatant) and physical assets of the United States, allies and friends. Building Partnerships The ability to set the conditions for interaction with partner, competitor or adversary leaders, military forces, or relevant populations by developing and presenting information and conducting activities to affect their percept Corporate Management and Support The ability to provide strategic senior level, enterprise-wide leadership, direction, coordination, and oversight through a chief management officer function.

Analytics Supported Measures of Performance (MOP) A criterion used to assess friendly actions that are tied to measuring task accomplishment. Measures of Effectiveness (MOE) A criterion used to assess changes in system behavior, capability, or operational environment that is tied to measuring the attainment of an end state, achievement of an objective, or creation of an effect. Verification A Quality control process that is used to evaluate whether or not a product, service, or system complies with regulations, specifications, or conditions imposed at the start of a development phase. Verification can be in development, scale-up, or production. Validation A Quality assurance process of establishing evidence that provides a high degree of assurance that a product, service, or system accomplishes its intended requirements. This often involves acceptance of fitness for purpose with end users and other product stakeholders. It is sometimes said that validation can be expressed by the query "Are you building the right thing?" and verification by "Are you building it right?"

DoDAF-DM2 Conformance Level 1 -- Conceptually conformant Uses DoDAF terms and aliases (from DM2 CDM) to categorize its concepts DoDAF views (AV-1 thru DIV-3) have correct information according to “monster matrix”).  For example, An OV-2 with radios would be non-conformant An OV-4 with Tank parts would be non-conformant Fit-For-Purpose (FFP) would have to be conformant with whatever the FFP model specifier said, e.g., a “FFP-1" view for which the originator specified the model as Services mapping to Capabilities should have Services and Capabilities and the relationship but shouldn't have unrelated info Level 2 -- Logically conformant Level 1 + adheres to terms and relationships from DM2 LDM and aliases Level 3 -- Physically conformant Level 2 + expressed as DoDAF – DM2 PES that can be consumed by others Level 4 -- Semantically conformant Level 3 + IDEAS semantics are correct 11

Tool [xyz]