Difference between revisions of "Joint Capabilities Integration and Development System (JCIDS)"
m |
m |
||
| Line 14: | Line 14: | ||
* <u>[http://acqnotes.com/ AcqNotes:]</u> ... [http://acqnotes.com/search Search/TopicList] ... [http://acqnotes.com/dictionary Dictionary] | * <u>[http://acqnotes.com/ AcqNotes:]</u> ... [http://acqnotes.com/search Search/TopicList] ... [http://acqnotes.com/dictionary Dictionary] | ||
** [http://acqnotes.com/references Main References] | ** [http://acqnotes.com/references Main References] | ||
| − | *** Main Acquisition References: [http://www.dau.edu/tools/dag Website: Defense Acquisition Guidebook (DAG)], [http://acqnotes.com/wp-content/uploads/2014/09/DoD-Directive-704514-PPBE-Process-29-Aug-2017.pdf | + | *** Main Acquisition References: [http://www.dau.edu/tools/dag Website: Defense Acquisition Guidebook (DAG)], [http://acqnotes.com/wp-content/uploads/2014/09/DoD-Directive-704514-PPBE-Process-29-Aug-2017.pdf DOD Directive 7045.14: Program Planning Budget & Execution (PPBE) Process (pdf)], and [http://www.acqnotes.com/Attachments/DAU%20Program%20Managers%20Toolkit.pdf DAU Program Managers Toolkit (pdf)] ... |
| − | **** [http://acqnotes.com/acqnote/acquisitions/dodd-5000 | + | **** [http://acqnotes.com/acqnote/acquisitions/dodd-5000 DOD Directive 5000.01: The Defense Acquisition System] |
| − | ***** [http://acqnotes.com/wp-content/uploads/2014/09/DoD-Directive-5000.01-Defense-Acquisition-System-31-Aug-2018.pdf | + | ***** [http://acqnotes.com/wp-content/uploads/2014/09/DoD-Directive-5000.01-Defense-Acquisition-System-31-Aug-2018.pdf DOD Directive 5000.01: The Defense Acquisition System (pdf)] |
***** [http://www.jcs.mil/Portals/36/Documents/Library/Instructions/CJCSI%205123.01H.pdf?ver=2018-10-26-163922-137 CJCS Instruction 3170.01H Charter of The Joint Requirements Oversight Council (JROC) and Implementation of The Joint Capabilities Integration and Development System (JCIDS) (pdf) | Joint Staff] ...This instruction establishes the JCIDS as the process used by the Joint Requirements Oversight Council (JROC) to fulfill its advisory responsibilities to the Chairman of the Joint Chiefs of Staff in identifying, assessing, validating, and prioritizing joint military capability requirements | ***** [http://www.jcs.mil/Portals/36/Documents/Library/Instructions/CJCSI%205123.01H.pdf?ver=2018-10-26-163922-137 CJCS Instruction 3170.01H Charter of The Joint Requirements Oversight Council (JROC) and Implementation of The Joint Capabilities Integration and Development System (JCIDS) (pdf) | Joint Staff] ...This instruction establishes the JCIDS as the process used by the Joint Requirements Oversight Council (JROC) to fulfill its advisory responsibilities to the Chairman of the Joint Chiefs of Staff in identifying, assessing, validating, and prioritizing joint military capability requirements | ||
****** [http://acqnotes.com/acqnote/acquisitions/joint-requirements-oversight-council Joint Requirements Oversight Council (JROC)] | ****** [http://acqnotes.com/acqnote/acquisitions/joint-requirements-oversight-council Joint Requirements Oversight Council (JROC)] | ||
******* [http://www.acqnotes.com/Attachments/CJCSI%203180.01%20JROC.pdf CJCSI 3180.01 Joint Requirements Oversight Council (pdf) – 31 Oct 01] | ******* [http://www.acqnotes.com/Attachments/CJCSI%203180.01%20JROC.pdf CJCSI 3180.01 Joint Requirements Oversight Council (pdf) – 31 Oct 01] | ||
***** [http://intellipedia.intelink.gov/ Website: JCIDS Intellipedia (CAC Required)] | ***** [http://intellipedia.intelink.gov/ Website: JCIDS Intellipedia (CAC Required)] | ||
| − | **** [http://acqnotes.com/acqnote/acquisitions/dodi-5000 | + | **** [http://acqnotes.com/acqnote/acquisitions/dodi-5000 DOD Instruction 5000.02 - Acquisition Process] |
| − | ***** [[Joint Capabilities Integration and Development System (JCIDS)#Adaptive Acquisition Framework (AAF)| | + | ***** [[Joint Capabilities Integration and Development System (JCIDS)#Adaptive Acquisition Framework (AAF)|DOD Instruction 5000.02 Operation of The Adaptive Acquisition Framework January 2020 - <i>reference AAF section below</i>]] |
| − | ***** [http://acqnotes.com/wp-content/uploads/2014/09/DoD-Instruction-5000.02-The-Defense-Acquisition-System-10-Aug-17-Change-3.pdf | + | ***** [http://acqnotes.com/wp-content/uploads/2014/09/DoD-Instruction-5000.02-The-Defense-Acquisition-System-10-Aug-17-Change-3.pdf DOD Instruction 5000.02T Operation of the Defense Acquisition System (pdf) – 10 Aug 17 (Change 3)] |
| − | *** Key Guides and Handbooks: [http://www.acqnotes.com/Attachments/DoD%20Integrated%20Master%20Plan%20and%20Integrated%20Master%20Schedule%20Preparation%20and%20User%20Guide.pdf Integrated Master Plan and Integrated Master Schedule Preparation and User Guide (pdf)], [http://acqnotes.com/wp-content/uploads/2017/07/DAU-Systems-Engineering-Fundamentals.pdf DAU Systems Engineering Fundamentals (pdf)], [http://www.acqnotes.com/Attachments/Test%20and%20Evaluation%20Management%20Guide.pdf Test and Evaluation Management Guide (pdf)], [http://www.acqnotes.com/Attachments/GAO%20Cost%20Estimating%20Guide%2009.pdf GAO Cost Estimating Guide (pdf)], [http://www.acqnotes.com/Attachments/Naval%20Aviation%20Systems%20Team%20Acquisition%20Logistics%20Support%20Plan%20Guide.doc Draft Naval Aviation Systems Team Acquisition Logistics Support Plan Guide], and [http://www.acqnotes.com/Attachments/NAVY%20DoD%20Information%20Assurance%20Certification%20and%20Accreditation%20Process%20Handbook.pdf Navy | + | *** Key Guides and Handbooks: [http://www.acqnotes.com/Attachments/DoD%20Integrated%20Master%20Plan%20and%20Integrated%20Master%20Schedule%20Preparation%20and%20User%20Guide.pdf Integrated Master Plan and Integrated Master Schedule Preparation and User Guide (pdf)], [http://acqnotes.com/wp-content/uploads/2017/07/DAU-Systems-Engineering-Fundamentals.pdf DAU Systems Engineering Fundamentals (pdf)], [http://www.acqnotes.com/Attachments/Test%20and%20Evaluation%20Management%20Guide.pdf Test and Evaluation Management Guide (pdf)], [http://www.acqnotes.com/Attachments/GAO%20Cost%20Estimating%20Guide%2009.pdf GAO Cost Estimating Guide (pdf)], [http://www.acqnotes.com/Attachments/Naval%20Aviation%20Systems%20Team%20Acquisition%20Logistics%20Support%20Plan%20Guide.doc Draft Naval Aviation Systems Team Acquisition Logistics Support Plan Guide], and [http://www.acqnotes.com/Attachments/NAVY%20DoD%20Information%20Assurance%20Certification%20and%20Accreditation%20Process%20Handbook.pdf Navy DOD Information Assurance Certification and Accreditation Process Handbook (pdf)] |
**** [http://acqnotes.com/acqnote/acquisitions/capabilities-based-assessment-cba JCIDS Process - Capabilities Based Assessment (CBA)] | **** [http://acqnotes.com/acqnote/acquisitions/capabilities-based-assessment-cba JCIDS Process - Capabilities Based Assessment (CBA)] | ||
***** [http://acqnotes.com/wp-content/uploads/2014/09/Capabilities-Based-Assessment-CBA-Users-Guide-version-3.pdf Capabilities-Based Assessment (CBA) User’s Guide version 3 (pdf) March 2009] | ***** [http://acqnotes.com/wp-content/uploads/2014/09/Capabilities-Based-Assessment-CBA-Users-Guide-version-3.pdf Capabilities-Based Assessment (CBA) User’s Guide version 3 (pdf) March 2009] | ||
| Line 35: | Line 35: | ||
***** [http://acqnotes.com/acqnote/acquisitions/capability-development-document-cdd JCIDS Process - Capability Development Document (CDD)] | ***** [http://acqnotes.com/acqnote/acquisitions/capability-development-document-cdd JCIDS Process - Capability Development Document (CDD)] | ||
****** [http://www.acqnotes.com/Attachments/CDD%20Writers%20Guide.pdf Capability Development Document (CDD) Writer’s Guide (pdf) June 2009 | TRADOC] | ****** [http://www.acqnotes.com/Attachments/CDD%20Writers%20Guide.pdf Capability Development Document (CDD) Writer’s Guide (pdf) June 2009 | TRADOC] | ||
| − | *** | + | *** [[Defense|DOD]] Document Databases: [http://www.esd.whs.mil/Directives/issuances/dodd/ DOD Directives], [http://www.esd.whs.mil/Directives/issuances/dodi/ DoD Instructions], [http://www.esd.whs.mil/directives/issuances/dodm/ DOD Manuals], [http://quicksearch.dla.mil/qsSearch.aspx Website: ASSIST] for[http://acqnotes.com/acqnote/careerfields/defense-standardization-program Defense Standardization Program (DSP)], and [http://everyspec.com/ EverySpec.com]]...Specifications, Standards, Handbooks and Mil-Spec documents |
| − | ** [http://acqnotes.com/dod-guides-handbooks | + | ** [http://acqnotes.com/dod-guides-handbooks DOD Guides and Handbooks] |
*** [http://www.dau.edu/library DAU – Publications and Catalogs] | *** [http://www.dau.edu/library DAU – Publications and Catalogs] | ||
*** [http://www.secnav.navy.mil/rda/OneSource/Pages/Program%20Assistance%20and%20Tools/HandbooksGuidesReports.aspx Navy Handbooks, Guides & Reports] | *** [http://www.secnav.navy.mil/rda/OneSource/Pages/Program%20Assistance%20and%20Tools/HandbooksGuidesReports.aspx Navy Handbooks, Guides & Reports] | ||
| Line 47: | Line 47: | ||
= <span id="Adaptive Acquisition Framework (AAF)"></span>Adaptive Acquisition Framework (AAF) = | = <span id="Adaptive Acquisition Framework (AAF)"></span>Adaptive Acquisition Framework (AAF) = | ||
| − | * [http://acqnotes.com/acqnote/acquisitions/dodi-5000 Acquisition Process - | + | * [http://acqnotes.com/acqnote/acquisitions/dodi-5000 Acquisition Process - DOD Instruction 5000.02] |
| − | ** [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500002p.pdf?ver=2019-05-01-151755-110 | + | ** [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500002p.pdf?ver=2019-05-01-151755-110 DOD Instruction 5000.02 Operation of The Adaptive Acquisition Framework (pdf) January 2020 | Office of the Under Secretary of Defense for Acquisition and Sustainment] |
* [http://aaf.dau.edu/ Adaptive Acquisition Framework | DAU] | * [http://aaf.dau.edu/ Adaptive Acquisition Framework | DAU] | ||
* [http://www.dau.edu/library/defense-atl/DATLFiles/July_Aug2020/Cummings_Woolsey.pdf The Adaptive Acquisition Framework - Better, Faster, More Tailored (pdf)] .. An interview with Stacy Cummings, Principal Deputy for Acquisition Enablers in the Office of the Under Secretary of Defense for Acquisition and Sustainment (A&S) | * [http://www.dau.edu/library/defense-atl/DATLFiles/July_Aug2020/Cummings_Woolsey.pdf The Adaptive Acquisition Framework - Better, Faster, More Tailored (pdf)] .. An interview with Stacy Cummings, Principal Deputy for Acquisition Enablers in the Office of the Under Secretary of Defense for Acquisition and Sustainment (A&S) | ||
* [http://www.youtube.com/redirect?redir_token=QUFFLUhqa2IxYlJLR2lxVUt2OFVwaEZVZGRQQjNxUGpUQXxBQ3Jtc0tuMEFMM3VkVDlxdFZVZ0hkajZwbGo0OW5BeDNNRDlBdjZpak8yZHVWVHhnWENYZGR5T2RqYTRjSmk2SF9naVYxVDZxT05MbThXRGJQSU9XcWlaUy1xV0hPTXRpaC1GU3ZOM0pwTWlXYk1famk0UXp3UQ%3D%3D&q=https%3A%2F%2Fwww.dau.edu%2Fabout%2FDocuments%2F20200220%2520-DAU%2520Hunstville%2520-Cummings.pptx&v=vJRjYfZMO-I&event=video_description Overview of the Adaptive Acquisition Framework | Stacy Cummings, Principal Deputy Assistant Secretary of Defense for Acquisition] | * [http://www.youtube.com/redirect?redir_token=QUFFLUhqa2IxYlJLR2lxVUt2OFVwaEZVZGRQQjNxUGpUQXxBQ3Jtc0tuMEFMM3VkVDlxdFZVZ0hkajZwbGo0OW5BeDNNRDlBdjZpak8yZHVWVHhnWENYZGR5T2RqYTRjSmk2SF9naVYxVDZxT05MbThXRGJQSU9XcWlaUy1xV0hPTXRpaC1GU3ZOM0pwTWlXYk1famk0UXp3UQ%3D%3D&q=https%3A%2F%2Fwww.dau.edu%2Fabout%2FDocuments%2F20200220%2520-DAU%2520Hunstville%2520-Cummings.pptx&v=vJRjYfZMO-I&event=video_description Overview of the Adaptive Acquisition Framework | Stacy Cummings, Principal Deputy Assistant Secretary of Defense for Acquisition] | ||
| − | * [http://resources.sei.cmu.edu/asset_files/Presentation/2019_017_001_634747.pdf Modernizing | + | * [http://resources.sei.cmu.edu/asset_files/Presentation/2019_017_001_634747.pdf Modernizing DOD Software Production (pdf) | Jeff Boleng, OUSD(A&S), Special Assistant for Software Acquisition] |
| − | * [http://www.dau.edu/mdid/Pages/Default.aspx Milestone Document Identification tool (MDID)] ...helps acquisition personnel identify statutory and regulatory program information requirements, as referenced in | + | * [http://www.dau.edu/mdid/Pages/Default.aspx Milestone Document Identification tool (MDID)] ...helps acquisition personnel identify statutory and regulatory program information requirements, as referenced in DODI 5000.85 and DODI 5000.81 |
The AAF is a major advancement for modern defense acquisition. It is more than a policy update. It is policy re-envisioned and restructured in a framework that encourages critical thinking by program managers in selecting and tailoring the best suited approach or pathway for a particular acquisition. It facilitates more rapid delivery to the point of need. The AAF acquisition pathways provide opportunities for MDAs/DAs and PMs to develop acquisition strategies and employ acquisition processes that match the characteristics of the capability being acquired. | The AAF is a major advancement for modern defense acquisition. It is more than a policy update. It is policy re-envisioned and restructured in a framework that encourages critical thinking by program managers in selecting and tailoring the best suited approach or pathway for a particular acquisition. It facilitates more rapid delivery to the point of need. The AAF acquisition pathways provide opportunities for MDAs/DAs and PMs to develop acquisition strategies and employ acquisition processes that match the characteristics of the capability being acquired. | ||
| Line 75: | Line 75: | ||
* There are three (3) types of of Urgent Needs: 1. Joint Urgent Operational Needs (JUON), 2. Joint Emergent Operational Need (JEON), and 3. Urgent Operational Need (UON) | * There are three (3) types of of Urgent Needs: 1. Joint Urgent Operational Needs (JUON), 2. Joint Emergent Operational Need (JEON), and 3. Urgent Operational Need (UON) | ||
* [http://acqnotes.com/acqnote/acquisitions/joint-urgent-operational-need-juon JCIDS Process - Urgent Capability Acquisition] | [http://acqnotes.com/ AcqNotes] | * [http://acqnotes.com/acqnote/acquisitions/joint-urgent-operational-need-juon JCIDS Process - Urgent Capability Acquisition] | [http://acqnotes.com/ AcqNotes] | ||
| − | ** [http://acqnotes.com/wp-content/uploads/2014/09/DoD-Instruction-5000.81-Urgent-Capability-Acquisition-31-Dec-19.pdf | + | ** [http://acqnotes.com/wp-content/uploads/2014/09/DoD-Instruction-5000.81-Urgent-Capability-Acquisition-31-Dec-19.pdf DODI 5000.81 Urgent Capability Acquisition | Office of the Under Secretary of Defense for Acquisition and Sustainment (A&S)] |
** [http://acqnotes.com/wp-content/uploads/2014/09/DAU-Urgent-Operational-Needs-7-Jul-2016.pdf Urgent and Emergent Operational Needs and Their Fulfillment (pdf)] | ** [http://acqnotes.com/wp-content/uploads/2014/09/DAU-Urgent-Operational-Needs-7-Jul-2016.pdf Urgent and Emergent Operational Needs and Their Fulfillment (pdf)] | ||
| Line 81: | Line 81: | ||
Programs that are intended to be completed in a period of 2-5 years via two acquisition pathways. | Programs that are intended to be completed in a period of 2-5 years via two acquisition pathways. | ||
* [http://acqnotes.com/acqnote/acquisitions/middle-tier-acquisitions Acquisition Process Middle Tier Acquisition (Section 804)] | [http://acqnotes.com/ AcqNotes] | * [http://acqnotes.com/acqnote/acquisitions/middle-tier-acquisitions Acquisition Process Middle Tier Acquisition (Section 804)] | [http://acqnotes.com/ AcqNotes] | ||
| − | ** [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500080p.PDF?ver=2019-12-30-095246-043 | + | ** [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500080p.PDF?ver=2019-12-30-095246-043 DODI 5000.80 Operation of the Middle Tier of Acquisition (MTA) (pdf) | Office of the Under Secretary of Defense for Acquisition and Sustainment (A&S)] |
* Section 804 “Middle Tier of acquisition paths to acquire critical national security capabilities” | * Section 804 “Middle Tier of acquisition paths to acquire critical national security capabilities” | ||
* Section 806 “Developing, Prototyping, Developing of Weapons System Components or Technology” | * Section 806 “Developing, Prototyping, Developing of Weapons System Components or Technology” | ||
| Line 89: | Line 89: | ||
* Tailorable | * Tailorable | ||
* [http://aaf.dau.edu/aaf/mca-interim/ Major Capability Acquisition | DAU] | * [http://aaf.dau.edu/aaf/mca-interim/ Major Capability Acquisition | DAU] | ||
| − | * [http://acqnotes.com/acqnote/acquisitions/dod-instruction-5000-85-major-capability-acquisition Acquisition Process | + | * [http://acqnotes.com/acqnote/acquisitions/dod-instruction-5000-85-major-capability-acquisition Acquisition Process DOD Instruction 5000.85 Major Capability Acquisition] ...establishes policy and procedures that guide the acquisition of major capability acquisition programs including: [http://acqnotes.com/acqnote/acquisitions/major-defense-acquisition-program Major Defense Acquisition Programs (MDAPs)]; Other programs categorized as Acquisition Category (ACAT); Major systems, usually categorized as [http://acqnotes.com/acqnote/acquisitions/acquisition-category ACAT II]; Automated information systems (AIS) (not managed by other acquisition pathways); and Other capabilities developed via the major capability acquisition pathway. |
| − | ** [http://acqnotes.com/wp-content/uploads/2020/08/DoD-Instruction-5000.85-Major-Capability-Acquisition-6-Aug-2020.pdf | + | ** [http://acqnotes.com/wp-content/uploads/2020/08/DoD-Instruction-5000.85-Major-Capability-Acquisition-6-Aug-2020.pdf DOD Instruction 5000.85 Major Capability Acquisition (pdf)] |
=== Software Acquisition === | === Software Acquisition === | ||
| Line 98: | Line 98: | ||
* Capability Needs Statements | * Capability Needs Statements | ||
* [http://www.acq.osd.mil/ae/assets/docs/USA002825-19%20Signed%20Memo%20(Software).pdf The Software Acquisition Pathway (pdf) 3 Jan 20] - <i>Interim Policy</i> | * [http://www.acq.osd.mil/ae/assets/docs/USA002825-19%20Signed%20Memo%20(Software).pdf The Software Acquisition Pathway (pdf) 3 Jan 20] - <i>Interim Policy</i> | ||
| − | * [http://apps.dtic.mil/sti/pdfs/AD1089247.pdf | + | * [http://apps.dtic.mil/sti/pdfs/AD1089247.pdf DOD Software Acquisition: Can DOD Build Weapon Systems Software Better and Faster (pdf) 11 Apr 19 | Carmela B. Rice - Defense Acquisition University] |
* [[Digital Twin#AEGIS|Example: AEGIS Virtual Twin system]] | * [[Digital Twin#AEGIS|Example: AEGIS Virtual Twin system]] | ||
=== Defense Business Systems (DBS) 5000.75 === | === Defense Business Systems (DBS) 5000.75 === | ||
| − | Business systems are information systems that are operated by, for, or on behalf of the | + | Business systems are information systems that are operated by, for, or on behalf of the DOD. |
* [http://acqnotes.com/acqnote/careerfields/defense-business-system-dbs Information Technology - Defense Business Systems (DBS) |][http://acqnotes.com/ AcqNotes] | * [http://acqnotes.com/acqnote/careerfields/defense-business-system-dbs Information Technology - Defense Business Systems (DBS) |][http://acqnotes.com/ AcqNotes] | ||
** [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500075p.PDF?ver=2020-01-24-132012-177 DOD Instruction 5000.75 Business Systems Requirements and Acquisition (pdf)] | ** [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500075p.PDF?ver=2020-01-24-132012-177 DOD Instruction 5000.75 Business Systems Requirements and Acquisition (pdf)] | ||
=== Acquisition of Services 5000.74 === | === Acquisition of Services 5000.74 === | ||
| − | Acquisition of contracted services from private sector entities by or for the | + | Acquisition of contracted services from private sector entities by or for the [[Defense|DOD]]. |
* [http://acqnotes.com/acqnote/acquisitions/acquisition-of-services Acquisition Process - Acquisition of Services] | [http://acqnotes.com/ AcqNotes] | * [http://acqnotes.com/acqnote/acquisitions/acquisition-of-services Acquisition Process - Acquisition of Services] | [http://acqnotes.com/ AcqNotes] | ||
| − | ** [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500074p.pdf?ver=2020-02-12-144922-503 | + | ** [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500074p.pdf?ver=2020-02-12-144922-503 DOD Instruction 5000.74 Acquisition of Services (pdf) | Office of the Under Secretary of Defense for Acquisition and Sustainment] |
| − | ** [http://acqnotes.com/wp-content/uploads/2018/07/Director-DPAP-DoDI-5000.74-Defense-Acquisition-of-Services.pdf | + | ** [http://acqnotes.com/wp-content/uploads/2018/07/Director-DPAP-DoDI-5000.74-Defense-Acquisition-of-Services.pdf DODI 5000.74 Presentation | Defense Procurement and Acquisition Policy (pdf)] |
* [http://www.dau.edu/tools/Documents/SAM/home.html DAU's virtual Service Acquisition Mall (SAM)] ...create your performance-based service acquisition requirements | * [http://www.dau.edu/tools/Documents/SAM/home.html DAU's virtual Service Acquisition Mall (SAM)] ...create your performance-based service acquisition requirements | ||
| Line 117: | Line 117: | ||
==== Early Prototyping 3201.01 ==== | ==== Early Prototyping 3201.01 ==== | ||
Technology or capability that is being matured by the research laboratories. | Technology or capability that is being matured by the research laboratories. | ||
| − | * [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/320101p.pdf?ver=2019-05-07-085149-300 | + | * [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/320101p.pdf?ver=2019-05-07-085149-300 DOD Instruction 3201.01 DOD Research and Development (R&D) Laboratories (pdf)] |
==== 10 USC 2373: Procurement for Experimental Purposes: Rapid acquisition tool for fielding and testing new capabilities ==== | ==== 10 USC 2373: Procurement for Experimental Purposes: Rapid acquisition tool for fielding and testing new capabilities ==== | ||
| Line 128: | Line 128: | ||
<youtube>vJRjYfZMO-I</youtube> | <youtube>vJRjYfZMO-I</youtube> | ||
<b>Overview of the Adaptive Acquisition Framework with Stacy Cummings | <b>Overview of the Adaptive Acquisition Framework with Stacy Cummings | ||
| − | </b><br>Feb. 20, 2020, Stacy Cummings, Principal Deputy Assistant Secretary of Defense for Acquisition Enablers, delivers an overview of the | + | </b><br>Feb. 20, 2020, Stacy Cummings, Principal Deputy Assistant Secretary of Defense for Acquisition Enablers, delivers an overview of the [[Defense|DOD]]'s new Adaptive Acquisition Framework as part of the annual Acquisition Update held at the DAU campus in Huntsville, Ala. During the hour-long presentation, Cummings addressed some of the monumental changes that the framework brings to [[Defense|DOD]] acquisition policy. The session also provided a look at the six new acquisition pathways programs can use to add flexibility and speed to their strategies. |
|} | |} | ||
|<!-- M --> | |<!-- M --> | ||
| Line 136: | Line 136: | ||
<youtube>ujJx2Qx-ziw</youtube> | <youtube>ujJx2Qx-ziw</youtube> | ||
<b>Adaptive Acquisition Framework: Software Pathway | <b>Adaptive Acquisition Framework: Software Pathway | ||
| − | </b><br>In this round table discussion, senior | + | </b><br>In this round table discussion, senior [[Defense|DOD]] leaders and experts from the field discuss the interim software policy that is part of the new Adaptive Acquisition Framework. Based largely on the SWAP Report Line of Effort A1, released by the Defense Innovation Board, the policy establishes a new acquisition pathway for software that prioritize continuous integration and delivery of working software in a secure manner, with continuous oversight from automated analytics. Moderator: Dr. Jeff Boleng, Special Assistant for Software Acquisition. Panel members: a. Stacy Cummings, Principal Deputy Assistant Secretary of Defense/ Acquisition Enablers, OUSD A-S b. Carmela Rice, OUSD A-S c. Robert Borka, Director, Navy Acquisition Policy, DASN APB d. Maj Zachary McCarty, Program Manager, F-22 Pipeline Operations. |
|} | |} | ||
|}<!-- B --> | |}<!-- B --> | ||
| Line 219: | Line 219: | ||
<youtube>uB1vrpSN2YQ</youtube> | <youtube>uB1vrpSN2YQ</youtube> | ||
<b>Defense Acquisition Categories | <b>Defense Acquisition Categories | ||
| − | </b><br>Defense Acquisition U professor Matt Ambrose provides a top-level description of Acquisition Categories (ACATs) used in the U.S. Department of Defense and the role such categories play in the management of acquisition programs. Ambrose also discusses the differences between weapon system and automated information system categories and provides an explanation of what makes a system a Major Defense Acquisition Program (MDAP) or a Major Automated Information System (MAIS). The | + | </b><br>Defense Acquisition U professor Matt Ambrose provides a top-level description of Acquisition Categories (ACATs) used in the U.S. Department of Defense and the role such categories play in the management of acquisition programs. Ambrose also discusses the differences between weapon system and automated information system categories and provides an explanation of what makes a system a Major Defense Acquisition Program (MDAP) or a Major Automated Information System (MAIS). The DODI 5000.02 and Milestone Documentation Identification tool (MDID) are referred to for further exploration of the topic and practical application. |
|} | |} | ||
|}<!-- B --> | |}<!-- B --> | ||
| Line 229: | Line 229: | ||
|| | || | ||
<youtube>rlZxMPS2oT0</youtube> | <youtube>rlZxMPS2oT0</youtube> | ||
| − | <b> | + | <b>[[Defense|DOD]] Acquisition Process |
</b><br>AcqNotes The Defense Acquisition Process July 16, 2017 | </b><br>AcqNotes The Defense Acquisition Process July 16, 2017 | ||
|} | |} | ||
| Line 237: | Line 237: | ||
|| | || | ||
<youtube>GfSCqy-riTQ</youtube> | <youtube>GfSCqy-riTQ</youtube> | ||
| − | <b> | + | <b>[[Defense|DOD]] JCIDS Process Overview |
</b><br>AcqNotes Nov 4, 2012 | </b><br>AcqNotes Nov 4, 2012 | ||
|} | |} | ||
| Line 309: | Line 309: | ||
<img src="https://www.csiac.org/wp-content/uploads/2018/12/policy_chart-e1544125489744.jpg" width="200"> | <img src="https://www.csiac.org/wp-content/uploads/2018/12/policy_chart-e1544125489744.jpg" width="200"> | ||
| − | [http://dodiac.dtic.mil/wp-content/uploads/2019/01/ia-policychart-7-Jan-19-DoDIN.pdf | + | [http://dodiac.dtic.mil/wp-content/uploads/2019/01/ia-policychart-7-Jan-19-DoDIN.pdf DOD Cybersecurity Policy Chart | Cyber Security & Information Systems Information Analysis Center] |
| − | * [http://acqnotes.com/wp-content/uploads/2014/09/DoD-Instruction-5000.02-The-Defense-Acquisition-System-10-Aug-17-Change-3.pdf | + | * [http://acqnotes.com/wp-content/uploads/2014/09/DoD-Instruction-5000.02-The-Defense-Acquisition-System-10-Aug-17-Change-3.pdf DODI 5000.02T - Operation of the Defense Acquisition System, Enclosure 14; Cybersecurity in the Defense Acquisition System] |
* [http://acqnotes.com/acqnote/careerfields/information-assurance Information Technology - Cybersecurity] | [http://acqnotes.com AcqNotes] | * [http://acqnotes.com/acqnote/careerfields/information-assurance Information Technology - Cybersecurity] | [http://acqnotes.com AcqNotes] | ||
** [http://www.acqnotes.com/wp-content/uploads/2014/09/PM-Guidebook-for-Integrating-Cybersecurity-RMF-into-System-Acquisition-Lifecycle-Sep-2015.pdf Guidance on Cybersecurity Implementation in Acquisition Programs (pdf)] | ** [http://www.acqnotes.com/wp-content/uploads/2014/09/PM-Guidebook-for-Integrating-Cybersecurity-RMF-into-System-Acquisition-Lifecycle-Sep-2015.pdf Guidance on Cybersecurity Implementation in Acquisition Programs (pdf)] | ||
| − | ** [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001p.pdf?ver=2019-02-26-101520-300 | + | ** [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001p.pdf?ver=2019-02-26-101520-300 DODI 8510.01 - Risk Management Framework (RMF) for DOD Information Technology (IT) (pdf)] |
** [http://www.acqnotes.com/wp-content/uploads/2014/09/PM-Guidebook-for-Integrating-Cybersecurity-RMF-into-System-Acquisition-Lifecycle-Sep-2015.pdf PM Guidebook for Integrating Cybersecurity RMF into System Acquisition Lifecycle (pdf) – Sep 2015] | ** [http://www.acqnotes.com/wp-content/uploads/2014/09/PM-Guidebook-for-Integrating-Cybersecurity-RMF-into-System-Acquisition-Lifecycle-Sep-2015.pdf PM Guidebook for Integrating Cybersecurity RMF into System Acquisition Lifecycle (pdf) – Sep 2015] | ||
* [http://www.dau.edu/cop/test/DAU%20Sponsored%20Documents/Cybersecurity-Test-and-Evaluation-Guidebook-Version2-change-1.pdf Cybersecurity Test and Evaluation Guidebook (pdf)] | * [http://www.dau.edu/cop/test/DAU%20Sponsored%20Documents/Cybersecurity-Test-and-Evaluation-Guidebook-Version2-change-1.pdf Cybersecurity Test and Evaluation Guidebook (pdf)] | ||
| Line 323: | Line 323: | ||
** [http://www.acqnotes.com/Attachments/Program%20Protection%20Plan%20Outline%20and%20Guidance.doc Outline (doc)] | ** [http://www.acqnotes.com/Attachments/Program%20Protection%20Plan%20Outline%20and%20Guidance.doc Outline (doc)] | ||
** [http://acqnotes.com/wp-content/uploads/2014/09/Program-Protection-Plan-PPP-Template-v3.2-Jul-11.docx Template (doc)] | ** [http://acqnotes.com/wp-content/uploads/2014/09/Program-Protection-Plan-PPP-Template-v3.2-Jul-11.docx Template (doc)] | ||
| − | ** [http://www.dau.edu/guidebooks/_layouts/15/WopiFrame.aspx?sourcedoc=/guidebooks/Shared%20Documents/Chapter%209%20Program%20Protection.pdf&action=default Defense Acquisition Guidebook (DAG) Chapter 9 (pdf)] ...provides guidance for the system security engineering (SSE) discipline and Department of Defense ( | + | ** [http://www.dau.edu/guidebooks/_layouts/15/WopiFrame.aspx?sourcedoc=/guidebooks/Shared%20Documents/Chapter%209%20Program%20Protection.pdf&action=default Defense Acquisition Guidebook (DAG) Chapter 9 (pdf)] ...provides guidance for the system security engineering (SSE) discipline and [[Defense|Department of Defense (DOD)]] program protection for defense acquisition programs. The program manager (PM) and the systems engineer (SE) should use DAG |
* [http://acqnotes.com/acqnote/careerfields/system-security-engineering Intelligence & Security - System Security Engineering (SSE)] | [http://acqnotes.com AcqNotes] ...Systems Security Engineering (SSE) is an element of Systems Engineering (SE) that applies scientific and engineering principles in a standardized, repeatable, and efficient manner to identify security vulnerabilities, requirements, and methods of verifications that minimize risks. SSE delivers systems that satisfy stakeholder security needs for weapon system operation in today’s cyber-contested environments. | * [http://acqnotes.com/acqnote/careerfields/system-security-engineering Intelligence & Security - System Security Engineering (SSE)] | [http://acqnotes.com AcqNotes] ...Systems Security Engineering (SSE) is an element of Systems Engineering (SE) that applies scientific and engineering principles in a standardized, repeatable, and efficient manner to identify security vulnerabilities, requirements, and methods of verifications that minimize risks. SSE delivers systems that satisfy stakeholder security needs for weapon system operation in today’s cyber-contested environments. | ||
** [http://acqnotes.com/wp-content/uploads/2020/08/USAF-Weapon-System-PP-and-SSE-Guidebook-v2.0.pdf Program Protection/Systems Security Engineering Guidebook (pdf) 12 Mar 20] | ** [http://acqnotes.com/wp-content/uploads/2020/08/USAF-Weapon-System-PP-and-SSE-Guidebook-v2.0.pdf Program Protection/Systems Security Engineering Guidebook (pdf) 12 Mar 20] | ||
| Line 329: | Line 329: | ||
* Cyber Threat Analysis | * Cyber Threat Analysis | ||
** [http://acqnotes.com/acqnote/careerfields/validated-online-lifecycle-threat-volt Intelligence & Security - Validated Online Lifecycle Threat (VOLT)] ...The VOLT Reports involve the application of threat modules, and are to be written to articulate the relevance of each module to a specific acquisition program or planned capability. Note: The STAR was replaced by the VOLT | ** [http://acqnotes.com/acqnote/careerfields/validated-online-lifecycle-threat-volt Intelligence & Security - Validated Online Lifecycle Threat (VOLT)] ...The VOLT Reports involve the application of threat modules, and are to be written to articulate the relevance of each module to a specific acquisition program or planned capability. Note: The STAR was replaced by the VOLT | ||
| − | * [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520039p.pdf | + | * [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520039p.pdf DODI 5200.39, Critical Program Information (CPI) Identification and Protection Within Research, Development, Test and Evaluation (RDT&E) (pdf)] |
| − | * [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520044p.pdf | + | * [http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520044p.pdf DODI 5200.44, Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN) (pdf)] |
{|<!-- T --> | {|<!-- T --> | ||
| Line 367: | Line 367: | ||
<youtube>HkslgE-UzVw</youtube> | <youtube>HkslgE-UzVw</youtube> | ||
<b>SERC TALKS: ’Mission Engineering’: Systems of Systems Engineering in Context | <b>SERC TALKS: ’Mission Engineering’: Systems of Systems Engineering in Context | ||
| − | </b><br>Today most organizational or societal capabilities rely on a mix of material and non-material ‘systems’ working together to achieve desired outcomes – to achieve their ‘mission’. Organizations typically define mission statements about why they exist – their “reason for being” -- and they use these mission statements as the basis for planning actions and investments. Government or religious organizations often form ‘mission’ teams to achieve a set of goals to share ideas or conduct negotiations. Space and defense organizations commonly refer to planned actions to achieve objectives as their ‘missions’ - e.g. US NASA Apollo mission to the moon. In most cases these include a set of objectives and a plan of actions to achieve these objectives. Recently US Defense has started to apply systems engineering concepts and practices to missions in what is being termed ‘Mission Engineering” - the deliberate planning, analyzing, organizing, and integrating of current and emerging operational and system capabilities to achieve desired mission effects. In this presentation Dr. Dahmann will discuss the motivation for employing systems approaches to mission capabilities as an extension and a broader context for application of systems of systems engineering. BIO: Dr. Judith Dahmann is a Technical Fellow at the MITRE Corporation Center and the capability lead for Systems of Systems (SoS). Dr. Dahmann is the MITRE project leader for SE Technical Support to OUSD R&E supporting mission engineering (ME) activities and the application of digital engineering to ME. She was the technical lead for development of the | + | </b><br>Today most organizational or societal capabilities rely on a mix of material and non-material ‘systems’ working together to achieve desired outcomes – to achieve their ‘mission’. Organizations typically define mission statements about why they exist – their “reason for being” -- and they use these mission statements as the basis for planning actions and investments. Government or religious organizations often form ‘mission’ teams to achieve a set of goals to share ideas or conduct negotiations. Space and defense organizations commonly refer to planned actions to achieve objectives as their ‘missions’ - e.g. US NASA Apollo mission to the moon. In most cases these include a set of objectives and a plan of actions to achieve these objectives. Recently US Defense has started to apply systems engineering concepts and practices to missions in what is being termed ‘Mission Engineering” - the deliberate planning, analyzing, organizing, and integrating of current and emerging operational and system capabilities to achieve desired mission effects. In this presentation Dr. Dahmann will discuss the motivation for employing systems approaches to mission capabilities as an extension and a broader context for application of systems of systems engineering. BIO: Dr. Judith Dahmann is a Technical Fellow at the MITRE Corporation Center and the capability lead for Systems of Systems (SoS). Dr. Dahmann is the MITRE project leader for SE Technical Support to OUSD R&E supporting mission engineering (ME) activities and the application of digital engineering to ME. She was the technical lead for development of the [[Defense|DOD]] guide for systems engineering of systems of systems (SoS) and the project lead for ISO 21839, a international standard on ‘SoS Considerations Throughout the System Life Cycle’. Dr. Dahmann is also the task lead for a set of Defense Advanced Research Projects Agency (DARPA) SoS programs investigating advanced technology approaches to complex SoS challenges. Dr. Dahmann is an INCOSE Fellow and the co-chair of the INCOSE Systems of Systems Working Group and the co-chair of the NDIA SE Division SoS Committee. She teaches Enterprise SE as an adjunct faculty member of the Johns Hopkins University in the Systems Engineering Program for Engineering Professionals. Presented on August 5, 2020 |
|} | |} | ||
|}<!-- B --> | |}<!-- B --> | ||
| Line 376: | Line 376: | ||
<youtube>4I7kT1dEZFA</youtube> | <youtube>4I7kT1dEZFA</youtube> | ||
<b>Graphs in Government: Achieving Total Cost Visibility for the U.S. Army | <b>Graphs in Government: Achieving Total Cost Visibility for the U.S. Army | ||
| − | </b><br>Maximizing cost visibility is a common goal for large organizations, including the United States Department of Defense. The United States Army is required to track operating and support costs for weapon systems including weapons definition, force structure, inventory, requisitions, maintenance, ammunition and more. That equates to a vast amount of data and growing data management complexities. To address these challenges and achieve total cost visibility, the Army adopted the Neo4j graph database to create, manage, and analyze data relationships across the logistics community. In this webinar, Jason Zagalsky, Federal Account Manager at Neo4j, will provide a brief overview of Neo4j and Graphs In Government, followed by Preston Hendrickson, Principal Systems Analyst at CALIBRE Systems, describing how modernizing its cost tracking system gave the Army the cost visibility needed to meet | + | </b><br>Maximizing cost visibility is a common goal for large organizations, including the United States Department of Defense. The United States Army is required to track operating and support costs for weapon systems including weapons definition, force structure, inventory, requisitions, maintenance, ammunition and more. That equates to a vast amount of data and growing data management complexities. To address these challenges and achieve total cost visibility, the Army adopted the Neo4j graph database to create, manage, and analyze data relationships across the logistics community. In this webinar, Jason Zagalsky, Federal Account Manager at Neo4j, will provide a brief overview of Neo4j and Graphs In Government, followed by Preston Hendrickson, Principal Systems Analyst at CALIBRE Systems, describing how modernizing its cost tracking system gave the Army the cost visibility needed to meet [[Defense|DOD]] objectives |
|} | |} | ||
|<!-- M --> | |<!-- M --> | ||
| Line 392: | Line 392: | ||
|| | || | ||
<youtube>Ik4aZyyhyDU</youtube> | <youtube>Ik4aZyyhyDU</youtube> | ||
| − | <b>Changing Software Acquisition in | + | <b>Changing Software Acquisition in [[Defense|DOD]] - Roundtable with the Defense Innovation Board |
| − | </b><br>Defense Acquisition University (Changing | + | </b><br>Defense Acquisition University (Changing [[Defense|DOD]]'s Software Acquisition Strategy, Workforce, Culture, and Metrics- A roundtable discussion with members of the Defense Innovation Board hosted by Dr. Jeff Boleng, Office of the Secretary of Defense.) |
|} | |} | ||
|<!-- M --> | |<!-- M --> | ||
| Line 401: | Line 401: | ||
<youtube>9FXlwmrXFqw</youtube> | <youtube>9FXlwmrXFqw</youtube> | ||
<b>Accelerating the Delivery of Weapon and Embedded System Software | <b>Accelerating the Delivery of Weapon and Embedded System Software | ||
| − | </b><br>Defense Acquisition University Dr. Jeff Boleng, Special Advisor for Software Acquisition, to the Under Secretary of Defense for Acquisition and Sustainment, held a roundtable with the Defense Innovation Board (DIB) to discuss how | + | </b><br>Defense Acquisition University Dr. Jeff Boleng, Special Advisor for Software Acquisition, to the Under Secretary of Defense for Acquisition and Sustainment, held a roundtable with the Defense Innovation Board (DIB) to discuss how [[Defense|DOD]] can “shift left” and optimize the long tail of weapons software certification (e.g., weapons safety, flight safety, nuclear surety, cyber security, etc.) and testing (e.g., Developmental, Operational, Live Fire). On a modern battlefield and in a future war, [[Defense|DOD]] may need to change complex software every day as a necessary factor for winning. “Shift left” and adopting private-sector, modern software development practices, will be key to accelerating software-based capabilities to weapon systems and the Warfighter. |
|} | |} | ||
|}<!-- B --> | |}<!-- B --> | ||
Revision as of 12:11, 7 October 2020
Youtube search... ...Google search
- Framing Context
- Enterprise Architecture (EA) ... What is a Capability?
- Evaluation
- Defense
- AcqNotes: ... Search/TopicList ... Dictionary
- Main References
- Main Acquisition References: Website: Defense Acquisition Guidebook (DAG), DOD Directive 7045.14: Program Planning Budget & Execution (PPBE) Process (pdf), and DAU Program Managers Toolkit (pdf) ...
- DOD Directive 5000.01: The Defense Acquisition System
- DOD Directive 5000.01: The Defense Acquisition System (pdf)
- CJCS Instruction 3170.01H Charter of The Joint Requirements Oversight Council (JROC) and Implementation of The Joint Capabilities Integration and Development System (JCIDS) (pdf) | Joint Staff ...This instruction establishes the JCIDS as the process used by the Joint Requirements Oversight Council (JROC) to fulfill its advisory responsibilities to the Chairman of the Joint Chiefs of Staff in identifying, assessing, validating, and prioritizing joint military capability requirements
- Website: JCIDS Intellipedia (CAC Required)
- DOD Instruction 5000.02 - Acquisition Process
- DOD Directive 5000.01: The Defense Acquisition System
- Key Guides and Handbooks: Integrated Master Plan and Integrated Master Schedule Preparation and User Guide (pdf), DAU Systems Engineering Fundamentals (pdf), Test and Evaluation Management Guide (pdf), GAO Cost Estimating Guide (pdf), Draft Naval Aviation Systems Team Acquisition Logistics Support Plan Guide, and Navy DOD Information Assurance Certification and Accreditation Process Handbook (pdf)
- JCIDS Process - Capabilities Based Assessment (CBA)
- Systems Engineering Initial Capabilities Document (ICD)
- Program Management - Business Case Analysis (BCA)
- Acquisition Process Materiel Development Decision (MDD) ...where the Joint Capabilities Integration and Development System (JCIDS) analysis has identified a capability gap/need and a MDD Review has determined a materiel solution is needed. The MDD is the formal point that initiates the ...
- DOD Document Databases: DOD Directives, DoD Instructions, DOD Manuals, Website: ASSIST forDefense Standardization Program (DSP), and EverySpec.com]...Specifications, Standards, Handbooks and Mil-Spec documents
- Main Acquisition References: Website: Defense Acquisition Guidebook (DAG), DOD Directive 7045.14: Program Planning Budget & Execution (PPBE) Process (pdf), and DAU Program Managers Toolkit (pdf) ...
- DOD Guides and Handbooks
- Milestone Requirements Matrix ..tab ACAT I, ACAT II, and ACAT III & Below
- Templates ...main templates that are used in defense acquisitions; need to check with requesting organization
- Main References
Integrated Product Support Implementation Roadmap ...List ... Timeline
Contents
- 1 Adaptive Acquisition Framework (AAF)
- 1.1 Adaptive Acquisition Framework Methods (Pathways)
- 2 Overview
- 3 Cybersecurity & Acquisition Lifecycle Integration
- 4 Insights
Adaptive Acquisition Framework (AAF)
- Acquisition Process - DOD Instruction 5000.02
- Adaptive Acquisition Framework | DAU
- The Adaptive Acquisition Framework - Better, Faster, More Tailored (pdf) .. An interview with Stacy Cummings, Principal Deputy for Acquisition Enablers in the Office of the Under Secretary of Defense for Acquisition and Sustainment (A&S)
- Overview of the Adaptive Acquisition Framework | Stacy Cummings, Principal Deputy Assistant Secretary of Defense for Acquisition
- Modernizing DOD Software Production (pdf) | Jeff Boleng, OUSD(A&S), Special Assistant for Software Acquisition
- Milestone Document Identification tool (MDID) ...helps acquisition personnel identify statutory and regulatory program information requirements, as referenced in DODI 5000.85 and DODI 5000.81
The AAF is a major advancement for modern defense acquisition. It is more than a policy update. It is policy re-envisioned and restructured in a framework that encourages critical thinking by program managers in selecting and tailoring the best suited approach or pathway for a particular acquisition. It facilitates more rapid delivery to the point of need. The AAF acquisition pathways provide opportunities for MDAs/DAs and PMs to develop acquisition strategies and employ acquisition processes that match the characteristics of the capability being acquired.
5000.02 Hybrid Program Model A (Hardware Dominant) ...
- Interactive Adaptive Acquisition Framework Tool (ppt)
- Interactive Defense Acquisition Life Cycle Wall Chart (ppt)
- Defense Acquisition Life Cycle Wall Chart; Compliance Baseline (Pre-Tailoring) (pdf)
- Defense Acquisition Life Cycle Wall Chart; Objectives & Contributions with Tailoring, and Compliance with Tailoring (pdf)
Adaptive Acquisition Framework Methods (Pathways)
Urgent Capability Acquisition (UCA) 5000.81
Need identified by Commanders involved in an ongoing contingency operation or emergent need.
- Fielded less than 2 years
- There are three (3) types of of Urgent Needs: 1. Joint Urgent Operational Needs (JUON), 2. Joint Emergent Operational Need (JEON), and 3. Urgent Operational Need (UON)
- JCIDS Process - Urgent Capability Acquisition | AcqNotes
Middle-Tier Acquisition (MTA) 5000.84
Programs that are intended to be completed in a period of 2-5 years via two acquisition pathways.
- Acquisition Process Middle Tier Acquisition (Section 804) | AcqNotes
- Section 804 “Middle Tier of acquisition paths to acquire critical national security capabilities”
- Section 806 “Developing, Prototyping, Developing of Weapons System Components or Technology”
Major Capability Acquisition (MCA) 5000.85
Execute to the standard defense acquisition model with modifications.
- Tailorable
- Major Capability Acquisition | DAU
- Acquisition Process DOD Instruction 5000.85 Major Capability Acquisition ...establishes policy and procedures that guide the acquisition of major capability acquisition programs including: Major Defense Acquisition Programs (MDAPs); Other programs categorized as Acquisition Category (ACAT); Major systems, usually categorized as ACAT II; Automated information systems (AIS) (not managed by other acquisition pathways); and Other capabilities developed via the major capability acquisition pathway.
Software Acquisition
To facilitate rapid and iterative delivery of software capability to the user.
- 6 to 12 months; enable continuous integration and delivery
- Software Acquisition Pathway as the preferred path for acquisition and development of software-intensive systems
- Capability Needs Statements
- The Software Acquisition Pathway (pdf) 3 Jan 20 - Interim Policy
- DOD Software Acquisition: Can DOD Build Weapon Systems Software Better and Faster (pdf) 11 Apr 19 | Carmela B. Rice - Defense Acquisition University
- Example: AEGIS Virtual Twin system
Defense Business Systems (DBS) 5000.75
Business systems are information systems that are operated by, for, or on behalf of the DOD.
Acquisition of Services 5000.74
Acquisition of contracted services from private sector entities by or for the DOD.
- Acquisition Process - Acquisition of Services | AcqNotes
- DAU's virtual Service Acquisition Mall (SAM) ...create your performance-based service acquisition requirements
Prototyping & Experiments
Early Prototyping 3201.01
Technology or capability that is being matured by the research laboratories.
10 USC 2373: Procurement for Experimental Purposes: Rapid acquisition tool for fielding and testing new capabilities
|
|
|
|
Overview
Click: JCIDS Process Flow Chart (pdf)
Defense Acquisition University (DAU)
|
|
|
|
|
|
AcqNotes Videos
|
|
|
|
U.S. Army Command and General Staff College (CGSC)
|
|
|
|
Cybersecurity & Acquisition Lifecycle Integration
- DevSecOps in Government
- Cybersecurity
- Cybersecurity - Visualization
- Cybersecurity and Acquisition Lifecycle Integration Tool (CALIT) | DAU
- The Cybersecurity and Acquisition Life-Cycle Integration Tool | Steve Mills and Tim Denman ...(pdf) - AcqNotes
Understanding what these processes are and how they interact will lead to better acquisition outcomes. The Cybersecurity & Acquisition Lifecycle Integration Tool (CALIT) provides the user the insight into these supporting processes and the ability to visualize how these processes work together to promote cyber resilient weapon systems.
DOD Cybersecurity Policy Chart | Cyber Security & Information Systems Information Analysis Center
- DODI 5000.02T - Operation of the Defense Acquisition System, Enclosure 14; Cybersecurity in the Defense Acquisition System
- Information Technology - Cybersecurity | AcqNotes
- Cybersecurity Test and Evaluation Guidebook (pdf)
- Intelligence & Security - Cybersecurity Strategy ...The strategy is created and maintained by the Program Office and appended to the Program Protection Plan (PPP). It’s required for all ACAT level programs.
- Intelligence & Security - Program Protection Plan (PPP) | AcqNotes
- Outline (doc)
- Template (doc)
- Defense Acquisition Guidebook (DAG) Chapter 9 (pdf) ...provides guidance for the system security engineering (SSE) discipline and Department of Defense (DOD) program protection for defense acquisition programs. The program manager (PM) and the systems engineer (SE) should use DAG
- Intelligence & Security - System Security Engineering (SSE) | AcqNotes ...Systems Security Engineering (SSE) is an element of Systems Engineering (SE) that applies scientific and engineering principles in a standardized, repeatable, and efficient manner to identify security vulnerabilities, requirements, and methods of verifications that minimize risks. SSE delivers systems that satisfy stakeholder security needs for weapon system operation in today’s cyber-contested environments.
- Cyber Threat Analysis
- Intelligence & Security - Validated Online Lifecycle Threat (VOLT) ...The VOLT Reports involve the application of threat modules, and are to be written to articulate the relevance of each module to a specific acquisition program or planned capability. Note: The STAR was replaced by the VOLT
- DODI 5200.39, Critical Program Information (CPI) Identification and Protection Within Research, Development, Test and Evaluation (RDT&E) (pdf)
- DODI 5200.44, Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN) (pdf)
|
|
Insights
|
|
|
|
|
|
Center for Strategic & International Studies
|
|