Systems Engineering Division
Major Current Tasks and Activities
DoD Reliability Analysis, Planning, Tracking and Reporting Directive Released:
The Directive-Type Memorandum (DTM) 11-003, Reliability Analysis, Planning, Tracking, and Reporting (March 21, 2011) is now available on the DoD Issuances Web site: http://www.dtic.mil/whs/directives/corres/pdf/DTM-11-003.pdf
This policy is the result of the Reliability Senior Steering Group chartered by Dr. Ashton Carter, Under Secretary of Defense for Acquisition, Technology and Logistics last year to make recommendations to strengthen system reliability policy. This DTM places early and continuous emphasis on reliability growth management that is fully integrated across systems engineering, life cycle sustainment, and test and evaluation activities. Andy Monje, the OSD Reliability and Maintainability Engineering lead is available to help programs implement this new policy. He can be reached at 703-692-0841 or firstname.lastname@example.org with questions.
Computational Research and Engineering Acquisition Tools and Environments (CREATE)
CREATE Briefings Announcement
Posted January 3, 2011
CREATE Executive Briefings Proceedings
Posted March 8, 2011
The DoD Computational Research and Engineering Acquisition Tools and Environments (CREATE) Program
Multi-Disciplinary, Physics-Based Simulation Software Products of the CREATE-AV Project
Plans and Status of the CREATE-SHIPS Project: Enabling Required Naval Warship Performance Throughout the Acquisition Lifecycle
CAPSTONE: Providing Geometry, Meshing and Attribution for Physics-based Analysis and Design
Physics-based Performance Prediction at Goodyear
CREATE Transition Challenges
Development Planning and Working Group
Development Planning and Working Group Announcement
Posted April 26, 2010
Review of Draft MIL-STD-882D
MIL-STD-882D Comment Sheet
Posted April 22, 2010
Capability Maturity Model Integration (CMMI)
Capability Maturity Models (CMMs) are the current commonly accepted methodology for assuring complete, efficient, and comprehensive Continuous Process Improvement within companies and organizations. The benchmark CMM is the Software capability Maturity Model (SW-CMM) issued in June 1991 and managed by the Software Engineering Institute. A Systems Engineering CMM was written by INCOSE, updated by the EIA and released as EIA/IS 731 in early 1999. In late 1997 the Department of Defense initiated an integration activity to integrate these two stand-alone models, add the discipline of Integrated Product and Process Development, into an expandable product suite called Capability Maturity Model Integration (CMMI). The DoD sought an industry co-sponsor and asked the NDIA SED to fulfil that role.
The CMMI project is a major undertaking involving numerous companies, DoD organizations, the SEI, and other individuals. Two drafts have been released as of the end of 1999, and the current response is that the integrated model is in fact comprehensive and reflects a much more efficient implementation of the maturity model concept. The final release version will be available in the summer of 2000. Almost all major aerospace companies, and many thousands of commercial companies, are users of CMMs and are anticipate to gravitate to CMMI over the next 2 years, when the current "stovepipe" models will be "sunset". To participate or for further information, contact Bob Rassa (email@example.com). You can also obtain additional information from the CMMI Website at http://www.sei.cmu.edu and click on "CMMI" in the main menu.
The Effective Use of CMMI position paper
Supportability Documentation Task
OSD and the Services are well along in the Acquisition Reform-related process of deleting MIL-STDs and telling their suppliers "how" to design and build the equipment they wish to procure. They are now only specifying the "what" and allowing suppliers to use their documented and proven internal processes and specifications to work the "how" portion (thus the great emphasis on CMMI as described previously). DoD is also no longer procuring full detailed documentation of the systems and equipment they buy, and is starting to allow vendors to maintain this supporting documentation. They are also, on select systems, allowing the supplier to fully maintain the equipment and manage the overall configuration control portion.
However, this can cause a downstream problem should the vendor default for any number of reasons, such as being purchased, getting out of that aspect of the business, or simply going out of business entirely. DoD needs to determine what is the optimum methodology of specifying data capture and retention performance elements in such contracts, and the SED has been asked to undertake this task. For further information on this task, contact Bill Chen (firstname.lastname@example.org) at United Defense LP.
Supportability Factors Identification Task
The SED was initially formed to help improve weapon systems supportability and improve total ownership costs, and it was clearly understood by the visionaries at the outset that the only way to effect this was in the very front end of design, during the systems engineering process, and we know that many of these dramatically affect downstream supportability. This task seeks to identify all those "front-end" factors that affect downstream supportability, and establish at least a qualitative measure of their impact. The concept is to provide a guideline and checklist of the things that absolutely must be considered during front-end design, and why. This is a very important effort that will affect the overall systems engineering and design activities, and the way that they are contracted.
This task is being handled by our newest SubCommittee, Automated Test. To participate, contact Les Orlidge at email@example.com.