DI-SESS-81223A
Schematic Block Diagrams
Schematic Block Diagrams are used as the basis for displaying functional and technical requirements and interfaces, supporting design synthesis, integration, and interface compatibility functions.
Approval DateOctober 9, 2019
AMSC Number10112
Preparing ActivityMI
Project NumberSESS-2019-049
DTIC ApplicableNo
GIDEP ApplicableNo
Use & Relationship
Schematic Block Diagrams (SBDs) are used as the basis for displaying functional and technical requirements and interfaces. As such, they support the design synthesis, integration, and interface compatibility functions.
a. This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.
b. SBDs are used when a multi-contractor relationship exists, and there is a need for commonality or exchange of this data among the contractors. SBDs can also be used when there is a special requirement for this data to support technical reviews and audits.
c. This DID supersedes DI-GDRQ-81223.
Requirements
1Reference Documents.None.
2Format.The SBDs format shall be in accordance with section 3 below.
3Content.The SBDs shall show the functional interfaces and apportionment or requirements between major systems; within the system between the elements of the system (e.g., equipment, personnel, facilities); and between end items, end-to-end, and closed-loop relationships. The SBDs shall also show the maintenance or check out aspects of the proposed design. Sufficient details shall illustrate how the design requirements are to be met. The SBDs shall delineate with symbols (e.g., schematic, architectural, electronic, mathematical, structural, mechanical, etc.) the features and relationships of end items, subsystems, and subsystems components and parts. The SBDs shall identify:
3.aIntersystem relationships.(e.g., a command and control system, interface with a strategic weapon system, etc.)
3.bIntrasystem relationships.including the relationship between constituent elements of a subsystem (e.g., in a communication subsystem interfaces between closed-circuit television, work station intercom, remote site communication, spacecraft communication, etc.)
3.cSubordinate detailed schematics.as required, to augment 3.a. and 3.b. above.
3.1Characteristics.The SBDs and significant elements within the diagrams shall be uniquely identified to provide the basis for:
3.1.aGenerating a family of lower-level-of-detail diagrams.traceable from the top down or from the bottom up.
3.1.bCollecting and apportioning effective Requirements Allocation Sheets.requirements or trade study requirements against applicable system or subsystem equipment.
3.1.cIdentifying major intersystem and intrasystem requirements.and interrelationships.
3.2Developing SBDs.The basic technique for developing SBDs is illustrated in Figure 1.
3.2.aThe first-level SBDs.shall be complete for the subsystem or subsystems being developed. The schematic shall depict a "closed-loop," including a block depiction of intersystem interfaces.
3.2.bThe second-level detail SBDs.shall be technical expansions of the first-level SBDs, and shall relate contract end items within the subsystem. Input and output expansion shall be related to the interfaces expressed in the first-level SBDs.
3.2.cThe third-level detail SBDs.shall be organized functionally to define significant end-to-end system logic across all hardware and facility interfaces involved (e.g., power subsystem, launch control, flight sequence, malfunction detection and control, etc.).
Schema v2.0Community-maintained · Verify against ASSIST 