DI-SESS-81785B

Systems Engineering Management Plan (SEMP)

Describes the contractor's technical approach and proposed plan for the conduct, management, and control of the integrated systems engineering effort, reflecting the program's scope, purpose, and life-cycle phases.

Approval DateJanuary 8, 2025

AMSC Number10515

Preparing ActivitySE

Project NumberSESS-2024-043

OPR—

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

DI-SESS-81785A

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The SEMP describes the contractor's technical approach and proposed plan for the conduct, management, and control of the integrated systems engineering (SE) effort. It reflects the scope, purpose, and life-cycle phase(s) of the program.

This Data Item Description (DID) contains the content and intended use information for the data deliverable resulting from the work task described in paragraph 6.3.1.4 of IEEE 24748-7:2019, or by the specific and discrete task requirements as delineated in the contract.

This DID supersedes DI-SESS-81785A

Preparation Instructions

1Reference documents

aOffice of the Secretary of Defense (OSD) Systems Engineering Plan (SEP) Outline

bIEEE 24748-7:2019, IEEE Standard for Application of Systems Engineering on Defense Programs

cIEEE 24748-8:2019, IEEE Standard for Technical Reviews and Audits on Defense Programs

2FormatThe SEMP format shall be selected by the contractor.

3ContentThe SEMP shall be consistent with and address all topics in the government SEP, if available. In the absence of a government SEP, the SEMP shall address the topics in the OSD SEP Outline active at the time of the Request for Proposal (RFP). Minimally, the SEMP shall:

3.1Describe the contractor's planned engineering approachto meeting the program's contract, objectives, and overall technical and management approach.

3.2Describe the contractor's detailed operational planfor executing systems engineering, including integration of the specialty engineering disciplines.

3.3Contain an annotated mapping between contractorand government SE processes. Identify any technical or technical management processes not mapped, including rationale for why they are not needed.

3.4Show alignment of SE processesof the contractor and subcontractors providing engineering effort.

3.5Describe planned technical solution activities

aDevelopment, documentation, maintenance, and communicationof the system architecture, including both internal and external interfaces.

bFormal technical reviews and auditsas defined in IEEE 24748-8 or by the specific and discrete task requirements delineated in the contract, including the entry and exit criteria for each review/audit.

cTrade studies for system requirements definitionarchitecture definition, design definition, integration, and verification/validation decisions.

dIntegration, verification, and validation down tothe appropriate system element level.

3.6Describe related planning associated with applicationof the contractor's systems engineering processes as tailored to meet the needs of the program and at a level of detail necessary for the contractor to manage and execute the technical effort. Details of process integration and communication with suppliers (i.e., subcontractors of engineered system elements and COTS vendors) shall be provided.

3.7Include referenced lower-level and subcontractor technical plans(e.g., risk management plan, requirements management plan, data management plan, and configuration management plan) as determined necessary by the contractor to plan and execute a total systems engineering effort.

3.8Provide detail related to other areas deemednecessary to execute systems engineering to meet the program's contract, objectives, and overall technical and management approach.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer