AEROSPACE REPORT NO.TOR-2005(8583)-3Systems Engineering15 April 2005Edited byL. W. PENNELLSparta, Inc.F. L. KNIGHTCorporate Chief Architect/EngineerSystems Planning and EngineeringPrepared forSPACE AND MISSILE SYSTEMS CENTERAIR FORCE SPACE COMMAND2430 E. El Segundo BoulevardLos Angeles Air Force Base, CA 90245Contract No. FA8802-04-C-0001Systems Planning and Engineering GroupAPPROVED FOR PUBLIC RELEASE;DISTRIBUTION IS UNLIMITED.AEROSPACE REPORT NO.TOR-2005(8583)-3SYSTEMS ENGINEERINGPrepared byL. W. PENNELLSparta, Inc.F. L. KNIGHTCorporate Chief Architect/EngineerSystems Planning and Engineering15 April 2005Systems Planning and Engineering GroupTHE AEROSPACE CORPORATIONEl Segundo, CA 90245-4691Prepared forSPACE AND MISSILE SYSTEMS CENTERAIR FORCE SPACE COMMAND2430 E. El Segundo BoulevardLos Angeles Air Force Base, CA 90245Contract No. FA8802-04-C-0001APPROVED FOR PUBLIC RELEASE;DISTRIBUTION IS UNLIMITED.NoteThis TOR contains a new draft version of Military Standard 499, Systems Engineering. It incorporates suggested revisions to the MIL-STD-499 and the “B” revision to that document, which was never officially released. It was prepared by and SMC team that included Aerospace, government, SETAs, and independent consultants. This draft has had only limited review by SMC SPOs and industry. This draft is being published at this time to support near-term SMC acquisitions with the intent of using it as a compliance standard.The goal is to reissue this draft standard as an SMC standard. Prior to that, further review by SMC organizations, discussions with industry, and coordination with other agencies such as the NRO and NASA are planned.AcknowledgmentsThe MIL-STD-499C is the result of contributions received from many individuals from a wide spectrum of technical disciplines. The names and organizations of the principal contributors, or those acting as the focal point of contact for their organizations, are listed below.Aerospace:Michael FabriziBusiness and Operations Analysis SubdivisionGerard FisherNational Systems Engineering/ArchitectureAl HohebThe Aerospace InstituteThanh HoangSpace Architecture DepartmentJoe MeltzerOffice of Chief Engineer/ArchitectSusan RuthGround Systems Development and Operations DepartmentExternal:Bill CrabtreeIndependent ConsultantDavid Davis U.S. Air Force - SMC/AXJerry LakeSystems Management InternationalBarry PortnerInnovative Systems Engineering Services, Inc.viiDRAFTNOT MEASUREMENTSENSITIVEMIL-STD-499CRevised 24 March 2005SupersedingMIL-STD-499B6 May 1974MILITARY STANDARDSYSTEMS ENGINEERINGAMSC AREA MISCDISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.MIL-STD-499B 2.70ForewordThis standard is approved for use by all Departments and Agencies of the Department of Defense (DoD) and may be used by other government and commercial organizations. Send comments and pertinent data for improving this standard to HQ SMC/AXEM, 2420 Vela Way, Los Angeles, CA 90245 or email to Dave Davis at david.davislosangeles.af.mil. This standard captures the key aspects of DoD policy to be included in the next revision of the DoD 5000 series as well as the National Security Space Acquisition Policy (NSSAP) 03-01 guidance to apply a robust systems engineering approach that balances total system performance and total ownership costs within the family-of-systems, systems-of-systems context. This standard defines the government requirements for an executable contractor systems engineering process and required systems engineering efforts to assist in defining, performing, managing, and evaluating systems engineering efforts in defense system acquisitions and technology developments. The scope of systems engineering is defined in terms of what should be done, not how to do it. The requirements in this standard, including those for systems engineering management, are defined in terms of the required systems engineering products and the required attributes of the products. This standard provides a reference to the Government for analyzing competing contractor proposals and for evaluating the contractors systems engineering program once on contract. The government will perform initial tailoring of this standard to address appropriate program scope, appropriate program size, and progress within the acquisition life cycle. The standard and tailoring, if any, will be part of the draft and final Requests for Proposal (RFP) along with instructions for contractors to perform further tailoring as part of their proposal submittals.This standard provides the technical foundation for integrating product and process development. This