System Design Review (SDR).

20.1 General.
The SDR shall be conducted to evaluate the optimization, traceability, correlation, completeness, and the risk of the allocated requirements, including the corresponding test requirements in fulfilling the system/subsystem requirements (the functional baseline). The review encompasses the total system requirements, i.e., operations/maintenance/test/training hardware, computer software, facilities, personnel, preliminary logistic support considerations. Also included shall be a summary review of the Systems Engineering Management Activities (e.g., mission and requirements analysis, functional analysis, requirements allocation, manufacturing methods/process selection, program risk analysis, system/cost effectiveness analysis, logistics support analysis, trade studies, intra- and inter-system interface studies, integrated test planning, specialty discipline studies, and Configuration Management) which produced the above system definition products. A technical understanding shall be reached on the validity and the degree of completeness of the following information:

? a. System/Subsystem Specification

? b. The engineering design/cost of the system (see Section 3, Definitions).

? c. Preliminary Operational Concept Description

? d. Preliminary Software Requirements Specification

? e. Preliminary Interface Requirements Specification(s)

? f. As appropriate:

1. (1) Prime Item Development Specification

2. (2) Critical Item Development Specification

20.2 Purpose.
An SDR shall be conducted as the final review prior to the submittal of the Demonstration and Validation Phase products or as the initial Full Scale Development Review for systems not requiring a formal Demonstration and Validation Phase but sufficiently complex to warrant the formal assessment of the allocated requirements (and the basis of these requirements) before proceeding with the preliminary design of HWCIs or the detailed requirements analysis for CSCIs. The SDR is primarily concerned with the overall review of the operational/support requirements (i.e., the mission requirements), updated/completed System/Subsystem Specification requirements, allocated performance requirements, programming and manufacturing methods/processes/planning, and the accomplishment of the Systems Engineering Management activities to insure that the definition effort products are necessary and sufficient. The purposes of the SDR are to:

20.2.1 Insure that the updated/completed System/Subsystem Specification is adequate and cost effective in satisfying validated mission requirements.

20.2.2 Insure that the allocated requirements represent a complete and optimal synthesis of the system requirements.

20.2.3 Insure that the technical program risks are identified, ranked, avoided, and reduced through:

? a. Adequate trade-offs (particularly for sensitive mission requirements versus engineering realism and manufacturing feasibility to satisfy the anticipated production quantities of corresponding performance requirements);

? b. Subsystem/component hardware proofing;

? c. A responsive test program; and

? d. Implementation of comprehensive engineering disciplines (e.g., worst case analysis, failure mode and effects analysis, maintainability analysis, producibility analysis and standardization.)

20.2.4 Identify how the final combination of operations, manufacturing, maintenance, logistics and test and activation requirements have affected overall program concepts; quantities and types of equipment, unit product cost (see Section 3, Definitions, paragraph 3.11), computer software, personnel, and facilities.

20.2.5 Insure that a technical understanding of requirements has been reached and technical direction is provided to the contractor.

20.3 Items to be Reviewed.
The SDR shall include a review of the following items, as appropriate: (as defined in the SEMP)

20.3.1 Systems Engineering Management Activities, e.g.:

? a. Mission and Requirements Analysis

? b. Functional Analysis

? c. Requirements Allocation

? d. System/Cost Effectiveness

? e. Synthesis

? f. Survivability/Vulnerability (including nuclear)

? g. Reliability/Maintainability/Availability (R/M/A)

? h. Electromagnetic Compatibility

? i. Logistic Support Analysis to address, as appropriate, integrated logistics support including maintenance concept, support equipment concept, logistics support concept, maintenance, supply, software support facilities, etc. (MIL-STD-1388-1 and 2)

? j. System Safety (emphasis shall be placed on system hazard analysis and identification of safety test requirements)

? k. Security

? l. Human Factors

? m. Transportability (including Packaging and Handling)

? n. System Mass Properties

? o. Standardization

? p. Electronic Warfare

? q. Value Engineering

? r. System Growth Capability

? s. Program Risk Analysis

? t. Technical Performance Measurement Planning

? u. Producibility Analysis and Manufacturing

? v. Life Cycle Cost/Design to Cost Goals

? w. Quality Assurance Program

? x. Environmental Conditions (Temperature, Vibration, Shock, Humidity, etc).

? y. Training and Training Support

? z. Milestone Schedules

? aa. Software Development Procedures (SDP, STP, and other identified plans, etc.)

20.3.2 Results of significant trade studies, for example:

? a. Sensitivity of selected mission requirements versus realistic performance parameters and cost estimates.

? b. Operations design versus maintenance design, including support equipment impacts.

? c. System centralization versus decentralization

? d. Automated versus manual operation

? e. Reliability/Maintainability/Availability

? f. Commercially available items versus new developments

? g. National Stock Number (NSN) items versus new development

? h. Testability trade studies (Allocation of fault detection/isolation capabilities between elements of built- in test, on board/on-site fault detection/isolation subsystem, separate support equipment, and manual procedures)

? i. Size and weight

? j. Desired propagation characteristics versus reduction interference to other systems (optimum selection frequencies)

? k. Performance/logistics trade studies

? l. Life cycle cost reduction for different computer programming languages

? m. Functional allocation between hardware, software, firmware and personnel/procedures

? n. Life Cycle Cost/system performance trade studies to include sensitivity of performance parameters to cost.

? o. Sensitivity of performance parameters versus cost

? p. Cost versus performance

? q. Design versus manufacturing consideration

? r. Make versus buy

? s. Software development schedule

? t. On-equipment versus off-equipment maintenance tasks, including support equipment impacts

? u. Common versus peculiar support equipment

20.3.3 Updated design requirements for operations/maintenance functions and items.

20.3.4 Updated requirements for manufacturing methods and processes.

20.3.5 Updated operations/maintenance requirements for facilities.

20.3.6 Updated requirements for operations/maintenance personnel and training.

20.3.7 Specific actions to be performed include evaluations of:

? a. System design feasibility and system/cost effectiveness

? b. Capability of the selected configuration to meet requirements of the System/Subsystem Specification

? c. Allocations of system requirements to subsystems/ configuration items

? d. Use of commercially available and standard parts

? e. Allocated inter- and intra- system interface requirements

? f. Size, weight, and configuration of HWCIs to permit economical and effective transportation, packaging, and handling consistent with applicable specifications and standards

? g. Specific design concepts which may require development toward advancing the state-of-the-art

? h. Specific subsystems/components which may require "hardware proofing" and high-risk long-lead time items

? i. The ability of inventory items to meet overall system requirements, and their compatibility with configuration item interfaces

? j. The planned system design in view of providing multi- mode functions, as applicable

? k. Considerations given to:

1. (1) Interference caused by the external environment to the system and the system to the external environment.

2. (2) Allocated performance characteristics of all system transmitters and receivers to identify potential intra- system electromagnetic (EM) incompatibilities.

3. (3) Non-design, spurious and harmonic system performance characteristics and their effect on electromagnetic environments of operational deployments.

? l. Value Engineering studies, preliminary Value Engineering Change Proposals (VECPs) and VECPs (as applicable).

20.3.8 Review the Preliminary Operational Concept Document, and sections 1.0, 2.0, 3.0, 5.0, 6.0, and 10.0 of the System/Subsystem Specification, all available HWCI Development Specifications, preliminary Software Requirements, and Interface Requirements Specifications for format, content, technical adequacy, completeness and traceability/correlation to the validated mission/support requirements. All entries marked "not applicable (N/A)" or "to be determined (TBD)" are identified and explained by the contractor.

20.3.9 Review section 4.0 of the System/Subsystem Specification, all available hardware Development Specifications, and preliminary Software Requirements and Interface Requirements Specifications for format, content, technical adequacy, and completeness. All available test documentation, including HWCI/subsystem and system test plans, shall be reviewed to insure that the proposed test program satisfies the test requirements of section 4.0 of all applicable specifications. All entries labelled "not applicable (N/A)" or "to be determined (TBD)" in section 4.0 of any applicable specification are identified and explained by the contractor.

20.3.10 Review the system, HWCI, and CSCI design for interaction with the natural environment. If any effect or interaction is not completely understood and further study is required, or it is known but not completely compensated for in the design, the proposed method of resolution shall also be reviewed. All proposed environmental tests shall be reviewed for compatibility with the specified natural environmental conditions.

20.3.11 Maintenance functions developed by the contractor to determine that support concepts are valid, technically feasible, and understood. In particular, attention is given to:

? a. R/M/A considerations in the updated System/Subsystem Specification

? b. Maintenance design characteristics of the system

? c. Corrective and preventive maintenance requirements

? d. Special equipment, tools, or material required

? e. Requirements or planning for automated maintenance analysis

? f. Item Maintenance Analysis compatibility with required maintenance program when weapon is deployed

? g. Specific configuration item support requirements

? h. Forms, procedures, and techniques for maintenance analysis

? i. Maintenance related trade-off studies and findings (includes commercially available equipment, software fault diagnostic techniques)

? j. Logistic cost impacts

? k. Support procedures and tools for computer software which facilitate software modification, improvements, corrections and updates

? l. Hardness critical items/processes

? m. Support equipment concept.

20.3.12 System compliance with nuclear, non-nuclear and laser hardening requirements. High risk areas or design concepts requiring possible advances of the state-of-the-art as a result of survivability criteria shall be identified, and prepared approach(es) to the problem reviewed. Prepared test programs shall be reviewed for sufficiency and compatibility with the specified threat environment and existing simulation test facilities.

20.3.13. The optimization, traceability, completeness, and risks associated with the allocation technical requirements, and the adequacy of allocated system requirements as a basis for proceeding with the development of hardware and software configuration items. Include any available preliminary Software Requirements and Interface Requirements Specifications.

20.3.14 Manufacturing (HWCIs only).

20.3.14.1 Production feasibility and risk analyses addressed at the SRR shall be updated and expanded. This effort should review the progress made in reducing production risk and evaluate the risk remaining for consideration in the Full Scale Development Phase. Estimates of cost and schedule impacts shall be updated.

20.3.14.2 Review of the Production Capability Assessment shall include:

20.3.14.2.1 A review of production capability shall be accomplished which will constitute an assessment of the facilities, materials, methods, processes, equipment and skills necessary to perform the full scale development and production efforts. Identification of requirements to upgrade or develop manufacturing capabilities shall be made. Requirements for Manufacturing Technology (MANTECH) programs will also be identified as an element of this production assessment.

20.3.14.3 Present the management controls and the design/ manufacturing engineering approach to assure that the equipment is producible.

20.3.14.4 Present a review of trade-off studies for design requirements against the requirement for producibility, facilities, tooling, production test equipment, inspection, and capital equipment for intended production rates and volume.

20.3.14.5 The analysis, assessments and trade-off studies should recommend any additional special studies or development efforts as needed.

20.3.15 Engineering Data.
Evaluate the contractor's drawing system, reviewing the drafting room manual, the preparation and review procedures, change control procedures, flowdown of requirements to subcontractors and vendors, and other aspects fundamental to the acceptability of Level 3 drawings. If available, review completed drawings from other programs or the normal company product line to determine compliance with the company procedures.

1. Post Review Action.
After completing the SDR, the contractor shall publish and distribute copies of Review Minutes. The contracting agency officially acknowledges completion of the SDR as indicated in paragraph 4.2.4.

APPENDIX C

Date: 2016-06-13; view: 8