|
BLK16-REMARKS:
|
BLK04:
Modify DID as follows:
10.2.1.i - Add: The following EIA-632 requirements shall be used as guidance
on how the requirements allocation is developed, maintained, and used
throughout the life of the program:
- Requirement 16; System Technical Requirements
- Requirement 17; Logical Solution Representations
- Requirement 18; Physical Solution Representations
- Requirement 19; Specified Requirements
10.2.2 - Add: The following EIA-632 requirements shall be used as guidance in
development of Technical Program Planning and Control:
- Requirement 25; Requirements Statement Validation
- Requirement 28; System Technical Requirements Validation
- Requirement 29; Logical Solution Representations Validation
- Requirement 30: Design Solution Verification
10.2.2.a - Risk Assessment and Management: This section shall include the
project aspects of risk identification (sources and causes), risk
characterization (effects, probabilities, choices, time frame, and coupling),
risk prioritization (greatest harm, greatest effect, and time urgency), and
risk aversion (mitigation, avoidance, transfer, and acceptance). The
assessment shall identify critical areas and further investigate the need for
additional prototyping, testing, or back up development to minimize risk. The
assessment shall also identify test requirements, technical performance
measures, parameters, and critical milestones for those areas identified. The
risk management functions to be performed by assigned teams and by supporting
analysts and specialists as well as the acceptable levels of risk for a particular
enterprise-based life-cycle phase, or group of phases, shall be included.
10.2.2.e – This section shall describe the manner in which the contractor’s
program reviews (EVMS Integrated Baseline Reviews (IBR)) shall assess,
reoptimize, and redirect the technical program effort during the course of
the contractual effort.
10.2.2.f – Change the title of the section to Detailed Design Review.
10.2.2.h - Change the title of the section to Technical Information
Management and Control.
10.2.2.j – Add: Tradeoff studies shall consider at a minimum the intra- and
inter-relationships among the following:
- Life Cycle Cost
- Construction
- Operating
- Logistics
- Maintenance
- Reliability and Maintenance
- Manpower
- Training
- Supply Support
- Engineering Support
- Operational Availability
- Mission Performance
- Risk
- System Safety
- Human Systems Integration
10.2.2.k – Testing Trials and Verification. This section shall describe the
plan for technical performance tracking and reporting iaw Testing, Trials,
and Verification (SOW Section 092) and
include the following:
10.2.2.k (2) – Delete
10.2.2.k (7) (f) - Delete
10.2.3 Part III – Engineering Integration. This part of the SEMP shall
describe the methods by which the contractor proposes to integrate the
engineering efforts. It shall include a summary of each specialty program and
cross reference the individual plans covering specialty programs such as, but
limited to, the Integrated Support Plan (CDRL
080-001), Human Systems Integration Plan (CDRL
088-001), Weight Control Plan (CDRL 096-001),
and Quality Plan (CDRL 090-001). Engineering
specialty integration shall be discussed as well as the relationship of the
engineering with the overall logistic efforts.
10.2.3.a. System Safety Plan. IAW SOW
Section 077-1, this section shall describe the contractor’s activities to
identify the hazards of the RB-M and its subsystems and impose design
requirements and management controls to prevent mishaps.
10.2.3 b. Provisioning Program Plan. IAW SOW
Section 083-1.2., this section shall describe the contractor’s efforts to
integrate the provisioning effort with the system design and engineering,
supportability analysis, and material selection processes to optimize
logistics support for system and equipment.
BLK10: Two times, with revisions. The first deliverable need only consist of
an outline and executive summary for each section. The second deliverable
shall contain all information required by the DID and be updated with
revisions as necessary to reflect changes in the Contractors organization or
plan.
BLK 12: The initial submission of the first deliverable is due 40 DBIBR.
Allow 20 days for Government review.
The second deliverable is due in conjunction with the initial submission of
the first phase of the detailed design review required by SOW Section 068-3.2. Allow 30 days for
government review.
Revisions are due 30 days after the organizational or planning change
requiring the revision. Allow 30 days for government review.
BLK 13: The subsequent submission of the first deliverable is due at IBR.
Allow 20 days for Government review.
Subsequent submissions of the second deliverable, including revisions, are
due 15 DARC. Allow 15 days for Government review.
|