1. Architecture Tool Vendor’s Day
OPS
DAS SE
CPM
JCIDS
PPBE
Architecture Tool Vendor’s Day
14 March 2011

2. Objectives of this Vendor’s Day
DoD CIO’s Vision of Tool Vendor – Government cooperation
Tool vendors briefly characterize their tool(s) in terms of type, core process supported, type(s) of architecture applicable to, and analytics provided (template follows)
Users discuss their current and emerging requirements for architecture tools 2

3. DoD Architectures are Required to Support 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

4. For everything DoD does – the 9 Joint Capability Areas (JCA)

5. For all 8 types of Architectures in DoD
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.

6. And the Architectural Description must be Conformant with DoDAF-DM2
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 6

7. Tool Characterization Template

8. Tool [xyz]

9. User Feedback and Requirements Open Discussion