PrelimSOW.doc
DOC document 44 KB Posted
- Attached to
- Space Threat Assessment Testbed (STAT) Program Federal contract opportunity
- Solicitation number
- FA9101-08-R-0002
About this file
Preliminary Statement of Work
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| SF30_Amendment 09.pdf | ||
| SF30.pdf | ||
| SF30.pdf | ||
| Q A_Amendment 07.pdf | ||
| SF30.pdf | ||
| Q A_Amendment06.pdf | ||
| Atch 19 Section M.pdf | ||
| Atch 18 Section L.pdf | ||
| Cover_Ltr.pdf | ||
| Atch 17 PSOW.pdf | ||
| SF30.pdf | ||
| Questions and Answers.pdf | ||
| SF30_04.pdf | ||
| 3_SF30.pdf | ||
| 2_SF30.pdf | ||
| MapofUTSI.pdf | ||
| MaptoUTSI.pdf | ||
| SF30_QA_CDRL.pdf | ||
| FinalRFP.zip | ZIP file | |
| ConsolidatedQ A-answered_Final.doc | DOC document | |
| 1_SF30.pdf | ||
| ConsolidatedQA-answered_Rev1.doc | DOC document | |
| SectionH_Rev1.doc | DOC document | |
| SF30.pdf | ||
| Synopsis.doc | DOC document | |
| 2_sf30.pdf | ||
| DD254_Atchs.pdf | ||
| AirForcePortalSelf-registrationProcess.doc | DOC document | |
| 1_sf30.pdf | ||
| sf30.pdf | ||
| STATCostTemplate-2007Dec12.xls | XLS spreadsheet | |
| Cover_Ltr_Signed.pdf | ||
| ExecutiveSummaryforDraftRFP.doc | DOC document | |
| DraftRFP_FBO_9Nov07.zip | ZIP file |
Show all 34
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
17 December 2007
Preliminary Statement of Work
1. Statement of Work (SOW) Tasks: The following are minimum program tasks that shall be accomplished for the STAT program. Offerors are expected to propose in their SOW an optimum combination of best military and commercial practices to meet the STAT program objectives.
A. Space Chamber: Design, develop, instrument, test, and transition the STAT system to meet all STAT System Specification requirements
B. Systems Engineering/Program Management
1) Systems Engineering
a) Develop, implement and maintain a program Systems Engineering Plan (SEP), including AEDC support contract and Government tasks. Correlate key systems engineering activities to events in the Integrated Master Schedule (IMS).
b) Support the Government (i.e., participate in planning and technical meetings, engineering analysis, testing, etc.) in completing required reviews.
c) Develop, implement and maintain a STAT Software Development Plan, a Software Requirements Specification, a Software Design Description, and a System/Subsystem Design Description.
d) Establish and maintain a list of critical technologies (per DoDD 5200.39).
e) Establish Interface Control Working Groups and develop Interface Control Documents (ICDs) as necessary to develop the program. Coordinate and maintain configuration of the ICDs.
f) Develop and maintain a list of critical safety items to transition the STAT system to AEDC.
g) Address hazards of electromagnetic radiation to ordnance per MIL-HDBK-240 as part of the Safety Assessment Report.
h) Develop, implement, and maintain an Environmental, Safety and Occupational Health (ESOH) Plan to integrate ESOH into the systems engineering and program management processes. Use the systems safety methodologies in MIL-STD-882D, Standard Practice for System Safety, and MIL-STD 882C, Task 207, Health Hazard Assessment, to manage ESOH risks with the goal to prevent or eliminate ESOH hazards when possible and manage ESOH risks where hazards cannot be avoided. The plan will:
(A) Include analysis of hazards associated with normal operation and system failures for environmental and occupational health risk assessment, tracking, and elimination/minimization.
(B) Require identification and quantification of hazardous materials (HAZMATs) used and hazardous waste generated during normal operations and maintenance (O&M) and emergency situations.
(C) Establish an unrestricted hazard data tracking system that will be easily accessible by testers, operators, and maintainers and will be transferable to the sustainer when the STAT is fielded.
i) Establish and maintain a configuration and data management process (hardware and software) for the duration of the program, using MIL-HDBK-61A as a guide. Develop, implement, and maintain the STAT Configuration Management/Data Management Plan that addresses the entire life cycle. Establish and maintain an electronic data management system that facilitates Government access.
j) Develop and maintain the approved System Specification. The Government will control the STAT functional baseline as reflected in the System Specification, and the contractor shall control their allocated and product baseline (software and hardware) throughout development.
k) Prepare a specification tree that follows the contractor work breakdown structure (CWBS). Provide requirements traceability from the System Specification to the lowest level specifications in the tree and from the lowest level back up to the System Specification.
l) Develop, implement, and maintain an open systems approach to: 1) facilitate development of a modular architecture and allow for affordable interoperability and support, 2) ensure that the system design is sufficiently flexible and robust to accommodate changing technology and requirements, 3) facilitate integration and use of products from multiple sources, including Government and commercial off the shelf, both in the initial design and in future enhancements, and 4) enable technology insertion as currently available products mature and new products become available, and 5) manage the impact of data rights restrictions for proprietary technologies on the foregoing factors.
m) Provide complete technical data and computer software deliverables and appropriate license rights for the entire STAT system. For any unmodified commercial-off-the-shelf (COTS) systems, this includes at least the deliverables and licenses rights as are typically provided to the customer or end user, and at least the minimum rights for technical data as required by DFARS 252.227-7015. For all other systems (e.g., noncommercial, military peculiar, or developmental - including any modifications to commercial systems that are funded in whole or in part by the Government), this includes (ie.) the complete technical data package providing all production-level details; (ii) all computer software as defined at DFARS 252.227-7014, including object/executable code, source code, and design information; and (iii) the associated license rights consistent with the applicable DFARS data rights clauses (including/allowing specially negotiated license rights when appropriate).
2) Program Management
a) Implement an integrated product development (IPD) approach, including participation by the Government and the AEDC operating contractor, to manage the program. Use integrated digital environment (IDE) tools as appropriate. Implement and maintain the contract Integrated Master Plan (IMP). Develop, implement, and maintain an IMS for execution of the IMP.
b) Develop, document, implement and maintain a STAT risk management process that systematically identifies and mitigates program cost, schedule, and technical risks. Co-chair, with the Government, integrated risk assessments. Incorporate identified risk handling strategies into program level plans and schedules.
c) Maintain an Earned Value Management System (EVMS) with requirements flowed down through CWBS level 3. Provide the Government the ability to review EVMS status at the level 3 CWBS. Develop and maintain a CWBS and dictionary that meets the requirements of MIL-HDBK-881A and correlates to the EVMS.
d) Prepare and provide Contractor Performance Reports (CPR) in accordance with correlating Contract Data Requirements List (CDRL). Support all program management meetings and special interest activities such as program management reviews, technical interchange meetings (TIMs), integrated baseline reviews, periodic or scheduled integrated logistics support management meetings, integrated risk assessments, what-if analyses, audits, independent review teams, test and evaluation safety review boards, and using command requirement and planning councils. Provide agendas and minutes for all STAT contractor-Government meetings, conferences, and audits.
e) Assist the Government in the development and/or update of security-related documents. Protect against compromising security in accordance with information security, emissions security, communication security, operations security, computer security, and physical security. Identify, implement, test, and support the certification and accreditation of appropriate baseline Information Assurance (IA) controls in accordance with DoDI 8500.2.
f) Perform special studies as requested by the Government (e.g., design trade studies, cost benefit analyses, and software maintenance/upgrade plans).
g) Implement a comprehensive major/critical subcontractor management process that ensures appropriate flow down of contract requirements and provides effective management of subcontractor performance.
h) Implement procedures to ensure early identification of all asserted restrictions on all technical data and computer software (both commercial and noncommercial) including restrictions asserted by subcontractors and suppliers, and to manage the use of proprietary technologies.
i) Develop, maintain, and provide a Life Cycle Cost (LCC) estimate for the STAT program.
C. Test and Evaluation
1) Develop, implement, and maintain a STAT Integrated System Test and Evaluation Plan and procedures for development test and evaluation and contractor testing.
2) Lead the Integrated Test Team. Support integrated test working group meetings.
3) Provide support for integrated test planning and execution (e.g., spares, initial operators and maintenance training, technical manual validation and verification).
4) Plan and conduct a test program, incorporating testing techniques and procedures which permit integrated verification through contractor testing, developmental testing, and full integrated testing.
5) Provide required test reports.
6) Train operators and maintenance team to support technical manual development.
D. Logistics
1) Develop, implement and maintain an Integrated Lifecyle Support Plan (ILCSP)
a) Include integrated product support and sustainment planning and implementation processes, tasks, reviews, and key events in the IMP and IMS.
b) Include specific plans to meet the System Requirements Document (SRD) requirements.
2) Support AEDC’s maintenance concept, using the current AEDC maintenance and logistics support structure.
a) During the transition from contractor to operational capability, provide over-the-shoulder support to AEDC maintainers through full operational capability (FOC).
b) Identify the data/processes and provide the licensing to those data/processes sufficient for an AEDC maintenance and repair capability over the life cycle. Provide access to and reproduction of engineering data, including processes called out on drawings, for the commercial baseline system and non-developmental items in support of AEDC operations, maintenance, installation, and training.
3) Adequate spares levels shall be in place to support test and evaluation.
4) Identify initial spares (commercial, peculiar, mission specific and support/test equipment), and support equipment for the STAT base level requirements, to include production lead-times.
5) Develop STAT training to include human factors in maintenance, general familiarization, and operational engineering, maximizing the use of existing AEDC training programs and available vendor training.
6) The Government intends to establish and achieve full organic maintenance capability for the STAT. Successful establishment and achievement of this capability requires the contractor and subcontractors to compile, control, maintain and deliver various engineering design disclosure data including computer software in varying media forms and methods.
Attachment 19
File details come from the government source that posted it. Updated .