July 17, 2008

System Design Specification Guidebook Appendix D – Land Systems

System Design Specification Appendix D – Land Systems

Background: “The Marine Corps task-organizes for operations consistent with its statutory tasking to ‘…provide forces of combined arms, including aviation…’ by forming Marine Air Ground Task Force (MAGTF). The MAGTF is a balanced, air-ground combined arms task organization of Marine Corps forces under a single commander, structured to accomplish a specific mission. It is the Marine Corps’ principle organization for all missions across the range of military operations. It is designed to fight, while having the ability to prevent conflicts and control crises. All MAGTFs are task-organized and vary in size and capability according to the assigned mission, threat, and battlespace environment… They are specifically tailored for rapid deployment by air or sea and ideally suited for a forward presence role…All MAGTFs are expeditionary by design and composed of four core elements: a command element, ground combat element, aviation combat element, and a combat service support element.”

The systems which support the Marine warfighter must enable the task organization (from a systems perspective) that is required routinely of our operational forces. Therefore, the interfaces, interoperability, and operability of United States Marine Corps (USMC) systems are critical to effectual support for the warfighter.

Intent: The intent of the System Design Specification(SDS) Guidebook and Appendix D – Land Systems for the Marine Corps is to define the system under consideration for development and acquisition in sufficient detail to inform senior leadership of any significant risks and provide industry with more system design definition earlier in the acquisition process. Critical to meeting this intent is the definition of system interfaces (internal and external) and preferred solutions (i.e. weapons mount for crew served weapon on a wheeled vehicle).

Marine Corps Process: The process that the Marine Corps will follow is depicted below in Figure 1.Figure 2 depicts a general Marine Corps Systemsspecification tree.

Figure 1: Marine Corps System Engineering Timeline

Figure 2: Marine Corps System Specification Tree

Applicability: The SDS Guidebook and Appendix D – Land Systemsshall be used for all Marine CorpsAcquisition Category (ACAT) I and II systems in developmentof SDS requirements in order to provide clarity of purpose through design and engineering detail to senior leadership and industry.

ACAT I and II programs within the Marine Corps typically are categorized into one of the following:

  • Vehicles (excludes aircraft or air vehicles)
  • Weapons System
  • Command and Control(Command, Control, Communications, Computer, Intelligence, Surveillance and Reconnaissance)(C4ISR)
  • Business
  • Sensors
  • Intelligence

The Marine Corps acquires aircraft through Naval Air Systems Command and will therefore follow theSDS Guidebook Appendix B - NAVAIRSYSCOM guidance for Marine Corps Aircraft.

Land Systems:

1. Scope

1.1.Introduction

  1. Operational Requirements
  2. Missions
  3. Threat
  4. Environment
  5. Requirements
  6. Performance Requirements
  7. Derivation of Performance Requirements from Concept of Operations (CONOPS) and Capabilities Development Document (CDD)
  8. KPPs
  9. KSAs
  10. Additional / Derived Attributes
  11. Capabilities
  12. Derivation of Functional Requirements from Concept of Operations (CONOPS) and Capabilities Development Document (CDD)
  13. KPPs
  14. KSAs
  15. Additional / Derived Attributes
  1. Reference Documents – provide an itemized list of specifications developed during the Systems Engineering process. A specification tree is included above.

3.1.1.1.System Specification Document - The Functional Baseline is documented in the System/Subsystem Spec. The System/Subsystem Specification specifies the requirements for a system or subsystem and the methods to be used to ensure that each requirement has been met. Requirements pertaining to the system or subsystem's external interfaces may be presented in the SSS or in one or more Interface Requirements Specifications (IRSs) All functional requirements shall be traceable to higher-level capabilities and shall be verifiable by a specific test method. All elements of the SSS will be reviewed at the SRR and the follow-on SFR. A template for the SSS can be found in the DI-IPSC-81431A.

3.1.1.2.System/Subsystem Design Document - The SSDDs (DI-IPSC-81432) can be used as a guide toSSDD development. Requirements pertaining to the system orsubsystem's external interfaces may be presented in the SSDD orin one or more IRSs referenced from the SSDD. The SSDD, possiblysupplemented by IRS and IDD is used as the basis for design andqualification testing of a system or subsystem.

3.1.1.3.Item Detail Specifications(Product Specification, Process Specification, Material Specification) – Uses the same System/Subsystem Specification (DI-IPSC-81431A) as 3.1.1.1 but provides a lower level of requirements detail.

3.1.1.4.Interface Requirements Document - The IRD (DI-IPSC-81434) specifies the requirements imposed on one or more systems, subsystems, HWCIs, CSCIs, manual operations, or other system components to achieve one or more interfaces among these entities. An IRD can cover any number of interfaces. The IRD can be used to supplement the SSDD and SRS as the basis for design and qualification testing of systems and CSCI’s.

3.1.1.5.Interface Control Document(DI-CMAN-81248A) - A document that establishes and defines the detailed interface definition between the interface owners of two or more end products of two or more systems, or end products within the same system. The ICD is a tool used to control the defined interface. The ICD canbe used to supplement the SSDD and SRS as the basis for designand qualification testing of systems and CSCI’s.

3.1.1.6.Interface Design Document - The IDD (DI-IPSC-81436) describes the interface characteristics of one or more systems, subsystems, HWCIs, CSCIs, manual operations, or other system components. An IDD may also describe any number of interfaces. The IDD can be used to supplement the System/Subsystem Design Description (SSDD)(DI-IPSC-81432) or Software Design Description (SDD) (DI-IPSC-81435). The IDD and its companion IRS serve to communicate and control interface design decisions.

3.1.1.7.Software Requirements Specifications – The SRS (DI-IPSC-81433) specifies the requirements for a Computer Software CSCI and the methods to be used to ensure that each requirement has been met. Requirements pertaining to the CSCI external interfaces may be presented in the SRS or in one or more Interface IRS referenced from the SRS. The SRS, possibly supplemented by the IRS, is used as the basis for design and qualification testing of a CSCI.

  1. Design Criteria
  2. Standards and Practices – describe the applicability of each of the following directives/ instructions/ practices etc on your program. It is not expected that every program will have a component that addresses each standard and practice – the list should be tailored to those standards that are applicable to the system being described. If you have tailored a particular standard or specification, annotate why that was done and the expected result.
  3. MIL SPEC / MIL STDs
  4. Operational Instructions
  5. SYSCOM Instructions
  6. Design Standards
  7. Commercial Standards
  8. Information Assurance
  9. Transportability
  10. Total Force Structure Considerations
  11. Naval Integration
  12. NavalEnterprise Architecture Standards
  13. Open System Architecture Standards (all SDS systems are required to perform an open architecture self-assessment [tool provided at and document the results, further OA guidance is contained in Appendices C & E)
  14. System Software Safety Technical Review Panel (SSTRP) Guidance
  15. Weapon Systems Explosive Safety Review Board (WSESRB) Guidance
  16. Wartime Reserve Mode Requirements
  17. NSS Supportability – Bandwidth / Quality of Service Requirements

4.2.Statutory and Regulatory Requirements – This paragraph should describe the statutory and regulatory requirements that apply to the program and the plan for achieving these requirements including the applicable approving authority. Additional information is specified in DoDI 5000.2,Enclosure 3.

  1. Requirements - This section shall be divided into the following paragraphs to specify thesystem requirements, that is, those characteristics of the system that are conditions for itsacceptance. Each requirement shall be assigned a project-unique identifier to support testingand traceability and shall be stated in such a way that an objective test can be defined for it. Each requirement shall be annotated with associated qualification method(s) (see Section 7) and,for subsystems, traceability to system requirements (see Section 6.7), if not provided in thosesections. The degree of detail to be provided shall be guided by the following rule: Include thosecharacteristics of the system that are conditions for system acceptance; defer to designdescriptions those characteristics that the acquirer is willing to leave up to the developer. If thereare no requirements in a given paragraph, the paragraph shall so state. If a given requirementfits into more than one paragraph, it may be stated once and referenced from the otherparagraphs.

5.1.Required states and modes - If the system is required to operate in more than one stateor mode having requirements distinct from other states or modes, this paragraph shall identify anddefine each state and mode. Examples of states and modes include: idle, ready, active, post-useanalysis, training, degraded, emergency, back-up, wartime, peacetime. The distinctionbetween states and modes is arbitrary. A system may be described in terms of states only,modes only, states within modes, modes within states, or any other scheme that is useful. If nostates or modes are required, this paragraph shall so state, without the need to create artificialdistinctions. If states and/or modes are required, each requirement or group of requirements inthis specification shall be correlated to the states and modes. The correlation may be indicatedby a table or other method in this paragraph, in an appendix referenced from this paragraph, orby annotation of the requirements in the paragraphs where they appear.

5.2.System capability requirements - This paragraph shall be divided into subparagraphs toitemize the requirements associated with each capability of the system. A "capability" is definedas a group of related requirements. The word "capability" may be replaced with "function,""subject," "object," or other term useful for presenting the requirements.

5.2.1.Logistics – This section should include performance requirements to support logistical operations throughout the MAGTF. The requirements should include planning and execution of the six functions of Marine Corps logistics (supply, maintenance, transport, health services, general engineering and other services).

5.2.2.Fires - This section should include hard-kill and soft-kill performance requirements against targets in various environmental and jamming conditions. The requirements should include planning, sensing, control and engagement capabilities. The performance requirements should cover detection ranges, number and types of tracks, reaction time, coverage, firepower, simultaneous engagements, probability of kill, system availability etc.

5.2.3.Maneuver - This section should include mobility and performance considerations in various terrain and environmental conditions. The requirements should include speed, maneuverability, payload capacity and armament (if any).

5.2.4.MAGTF Command and Control - This section should include the systems performance regarding planning, command and control and communications for commanders at all levels of the MAGTF (Force, MEF, MEB, MEU) and/or supporting establishment (reach back/reach forward).

5.2.5.Intelligence - This section should include requirements that enable intelligence operations in various environmental and jamming conditions. The requirements should include planning, sensing and analysis capabilities. The performance requirements should cover detection ranges, number and types of tracks, reaction time, coverage, system availability etc.

5.2.6.Force Protection - This section should include active and passive measures employed to protect the Force in various environmental and jamming conditions. The requirements should include planning, sensing, control and engagement capabilities. The performance requirements should cover detection ranges, number and types of tracks, reaction time, coverage, survivability, firepower, simultaneous engagements, probability of kill, system availability etc.

5.3.System external interface requirements - This paragraph shall be divided into subparagraphsto specify the requirements, if any, for the system’s external interfaces. This paragraphmay reference one or more Interface Requirements Specifications (IRSs) or other documentscontaining these requirements.

5.3.1.Interface identification and diagrams. This paragraph shall identify the required externalinterfaces of the system. The identification of each interface shall include a project-uniqueidentifier and shall designate the interfacing entities (systems, configuration items, users, etc.) byname, number, version, and documentation references, as applicable. The identification shallstate which entities have fixed interface characteristics (and therefore impose interfacerequirements on interfacing entities) and which are being developed or modified (thus havinginterface requirements imposed on them). One or more interface diagrams shall be provided todepict the interfaces.

5.3.2.(Project-unique identifier of interface). This paragraph (beginning with 5.3.2) shall identifya system external interface by project-unique identifier, shall briefly identify the interfacing entities,and shall be divided into subparagraphs as needed to state the requirements imposed on thesystem to achieve the interface. Interface characteristics of the other entities involved in theinterface shall be stated as assumptions or as "When [the entity not covered] does this, thesystem shall...," not as requirements on the other entities. This paragraph may reference otherdocuments (such as data dictionaries, standards for communication protocols, and standards foruser interfaces) in place of stating the information here. The requirements shall include thefollowing, as applicable, presented in any order suited to the requirements, and shall note anydifferences in these characteristics from the point of view of the interfacing entities (such asdifferent expectations about the size, frequency, or other characteristics of data elements).

5.4.System internal interface requirements. This paragraph shall specify the requirements,if any, imposed on interfaces internal to the system. If all internal interfaces are left to the designor to requirement specifications for system components, this fact shall be so stated. If suchrequirements are to be imposed, paragraph 5.3provides a list of topics to beconsidered.

5.5.System internal data requirements. This paragraph shall specify the requirements, if any,imposed on data internal to the system. Included shall be requirements, if any, on databases anddata files to be included in the system.

5.6.Adaptation requirements. This paragraph shall specify the requirements, if any,concerning installation-dependent data that the system is required to provide (such as sitedependentlatitude and longitude or site-dependent state tax codes) and operational parametersthat the system is required to use that may vary according to operational needs (such asparameters indicating operation-dependent targeting constants or data recording).

5.7.Safety requirements. This paragraph shall specify the system requirements, if any,concerned with preventing or minimizing unintended hazards to personnel, property, and thephysical environment. Examples include restricting the use of dangerous materials; classifyingexplosives for purposes of shipping, handling, and storing; abort/escape provisions fromenclosures; gas detection and warning devices; grounding of electrical systems; decontamination;and explosion proofing. This paragraph shall include the system requirements, if any, for nuclearcomponents, including, as applicable, requirements for component design, prevention ofinadvertent detonation, and compliance with nuclear safety rules.

5.8.Security and privacy requirements. This paragraph shall specify the system requirements,if any, concerned with maintaining security and privacy. The requirements shall include, asapplicable, the security/privacy environment in which the system must operate, the type anddegree of security or privacy to be provided, the security/privacy risks the system mustwithstand,required safeguards to reduce those risks, the security/privacy policy that must be met, thesecurity/privacy accountability the system must provide, and the criteria that must be met forsecurity/privacy certification/accreditation.

5.9.System environment requirements. This paragraph shall specify the requirements, if any,regarding the environment in which the system must operate. Examples for a software systemare the computer hardware and operating system on which the software must run. (Additionalrequirements concerning computer resources are given in the next paragraph). Examples for ahardware-software system include the environmental conditions that the system must withstandduring transportation, storage, and operation, such as conditions in the natural environment (wind,rain, temperature, geographic location), the induced environment (motion, shock, noise,electromagnetic radiation), and environments due to enemy action (explosions, radiation).

5.10.Computer resource requirements. This paragraph shall be divided into the followingsubparagraphs. Depending upon the nature of the system, the computer resources covered inthese subparagraphs may constitute the environment of the system (as for a software system)or components of the system (as for a hardware-software system).

5.10.1.Computer hardware requirements. This paragraph shall specify the requirements, if any,regarding computer hardware that must be used by, or incorporated into, the system. Therequirements shall include, as applicable, number of each type of equipment, type, size, capacity,and other required characteristics of processors, memory, input/output devices, auxiliary storage,communications/network equipment, and other required equipment.

5.10.2.Computer hardware resource utilization requirements. This paragraph shall specify therequirements, if any, on the system’s computer hardware resource utilization, such as maximumallowable use of processor capacity, memory capacity, input/output device capacity, auxiliarystorage device capacity, and communications/network equipment capacity. The requirements(stated, for example, as percentages of the capacity of each computer hardware resource) shallinclude the conditions, if any, under which the resource utilization is to be measured.

5.10.3.Computer software requirements. This paragraph shall specify the requirements, if any,regarding computer software that must be used by, or incorporated into, the system. Examplesinclude operating systems, database management systems, communications/network software,utility software, input and equipment simulators, test software, and manufacturing software. Thecorrect nomenclature, version, and documentation references of each such software item shallbe provided.