PWS dated March 05 2009 - Master File .pdf

Launch and Range Systems Wing (LRSW)

Systems Engineering & Integration (SE&I) Contract

DDRRAAFFTT PPeerrffoorrmmaannccee--bbaasseedd WWoorrkk SSttaatteemmeenntt ((PPWWSS))

Contract FA8811-10-C-XXXX

Attachment 1

March 5, 2009

Launch & Range Systems Wing Space & Missile Systems Center

483 North Aviation Boulevard Los Angeles AFB, California 90245-2808

Phone: (310) 653-3656

BLANK

i

Table of Contents

1.0 Description of Service

1.1 SE&I

1.2 LAAFB PWS

1.3 CCAFS PWS

1.4 VAFB PWS

2.0 Services Summary

2.1 General

2.2 Performance Evaluation

3.0 Government Furnished Property and Services

3.1 Facilities

3.2 Government-Furnished Services

3.3 Government-Furnished Property

3.4 Forms and Publications

4.0 General Information

4.1 Contractor Personnel

4.2 Security / Controlled Areas

4.3 Hours of Operation

4.4 Performance Evaluation Meetings

4.5 Quality Assurance

4.6 Scope Changes

4.7 Administrative Records

4.8 Safety

APPENDICES

Appendix A - Government Furnished Property/Services/Equipment Appendix B - Acronyms, Abbreviations and Definitions Appendix C - Applicable Publications and Forms (DRAFT)

1.0 Description of Service

The contractor shall furnish all personnel, equipment, labor, tools, materials, supervision, transportation and other items and services necessary to perform System Engineering and Integration (SE&I) services for the Launch and Range Systems Wing (LRSW) located at the Space and Missile Systems Center at Los Angeles Air Force Base, California (LAAFB) and two satellite locations: Cape Canaveral Air Force Station, Florida (CCAFS); and Vandenberg Air Force Base, California (VAFB). Services provided under this contract support LRSW’s space launch operations for current and future LRSW launch systems. Deliverables provided under this contract are in accordance with Exhibit A, Contract Data Requirements Lists (CDRLs). This is accomplished through the following mechanisms, in accordance with (IAW) Space & Missile Systems Center Program Integration (SMC/PI) description of SE&I functions (not all the SE&I functions are performed at each location under this Performance-based Work Statement (PWS)):

• Systems Engineering and Integration

• Mission Integration Management

• Systems Safety Engineering

• Systems Environmental Engineering

• Systems Security & Information Assurance

• Product Assurance

• Launch Schedule Management

• Launch Risk Management

CDRLs A001, A002, A003 (applies to 1.0 and subparagraphs)

1.1 SE&I

The current SE&I effort consists primarily of systems engineering and integration tasks in support of the Evolved Expendable Launch Vehicle (EELV) program. The SE&I also includes overarching integration of launch and range programs which will require interfacing with both the EELV and future LRSW launch systems and the Launch and Test Range System (LTRS).

The SE&I PWS contains work for four separate entities at three locations. There is work performed for LRSW by personnel located at LAAFB, VAFB, and CCAFS. This effort will support LRSW, 4th Space Launch Squadron (4 SLS), and 5th Space Launch Squadron (5 SLS). The PWS also contains work for the 30th Launch Group (30 LCG) to be performed by personnel located at VAFB.

1.2 LAAFB PWS

1.2.1 SE&I IN SUPPORT OF LRSW LAUNCH SERVICES

1.2.1.1 Systems Engineering & Integration

1.2.1.1.1 SYSTEMS ENGINEERING AND INTEGRATION ACTIVITIES

1.2.1.1.1.1 The contractor shall generate draft revisions to the EELV System

Performance Requirements Document (SPRD), EELV Standard Interface Specification (SIS), Engineering Launch Support System (ELSS) System Requirements Document (SRD), and Derived Communications Requirements Document (DCRD); incorporating agreed upon-changes and preparing the documents, IAW MIL- STD-961E, for Configuration Control Board (CCB) approval.

1.2.1.1.1.2 The contractor shall update the LRSW Mission Assurance Plan (MAP) annually; submitting it to LRSW/EN.

1.2.1.1.1.3 The contractor shall update the EELV Systems Engineering Plan (SEP) IAW Air Force Instruction (AFI) 63-1201 (Life Cycle Systems Engineering).

1.2.1.1.2 ENGINEERING LAUNCH SUPPORT SYSTEM (ELSS)

1.2.1.1.2.1 The contractor shall analyze ELSS user-requested changes and recommend implementation options to LRSW. The contractor shall analyze the requested changes in the context of the ELSS requirements, develop system designs, implement system updates, and document changes to ELSS Launch Vehicle (LV) Launch Support Center (LSC), High Speed Network (HSN), and interface) requirements. The contractor shall revise ELSS Concept of Operations (ConOps) to reflect requirements changes.

The contractor shall perform ELSS systems integration and activation for ELSS system revisions to support LRSW launch vehicle systems operations. (Excludes National Reconnaissance Office (NRO) Operations Squadron (NOPS) and Spacelift Telemetry Acquisition and Reporting System (STARS))

1.2.1.1.2.2 The contractor shall analyze proposed changes to ELSS interfaces with other systems as specified in the DCRD, e.g.

NOPS and STARS. The contractor shall provide written recommendations to LRSW on optimum implementation. The contractor shall verify ELSS compliance with interface requirements. The contractor shall accomplish the final verification by supporting system-of-systems end-to-end testing.

1.2.1.1.2.3 The contractor shall develop a recapitalization plan for ELSS/LV_LSC and EELV acquired equipment.

1.2.1.1.3 RD-180 ENGINEERING

1.2.1.1.3.1 The contractor shall provide engineering expertise on the Atlas V RD-180 booster engine to support the launch vehicle contractor technical team and the LRSW program team for RD-180 engine production, operations, and post-flight data review.

1.2.1.1.3.2 The contractor shall assure that the RD-180 engine is properly designed, developed, and manufactured to meet system requirements. The contractor shall monitor RD-180 co-production development to assure that the propulsion system meets launch vehicle system performance requirements.

1.2.1.1.3.3 The contractor shall provide expertise in the foreign design, development, test, and manufacturing process and how they differ from U.S. processes.

1.2.1.1.3.4 The contractor shall validate and track technical performance of the launch vehicle propulsion system to include specific focus on RD-180 development and acceptance testing. The contractor shall coordinate with government personnel and launch service contractors to obtain and maintain program information to provide program status. The contractor shall maintain close insight into RD-180 anomaly resolution and operations. The contractor shall participate in any failure review and recovery board.

1.2.1.1.3.5 The contractor shall serve as the Wing focal point for Former Soviet Union (FSU) policy requirements, technical assistance agreements, and State Department requirements.

1.2.1.2 MISSION INTEGRATION MANAGEMENT

1.2.1.2.1 The contractor shall perform planning and development of launch program contract requirements (e.g. statements of work).

1.2.1.2.2 The contractor shall analyze programmatic issues related to the contract (e.g. cost, schedule and performance). The contractor shall conduct weekly launch vehicle contract status reviews with the United Launch Alliance (ULA) and LRSW. The contractor shall coordinate and track launch program Comprehensive Cost and Requirement (CCaR) System, unfunded requirements list and obligation plan. The contractor shall provide written status reports to the government at conclusion of weekly status meeting.

1.2.1.2.3 The contractor shall identify mission management programmatic issues associated with cost, schedule and performance. The contractor shall provide written impact statements and identify possible alternative recommendations.

1.2.1.2.4 The following tasks shall require a 25% increased level of support for two FTEs for approximately three to four weeks prior to a LRSW supported launch. While the number of launches is subject to change year to year, on average LRSW supports four ER and two WR launches per year.

Additionally, on average, this increased level of support may have to be repeated for at least two launch periods per year due unknown pre-launch delays.

1.2.1.2.4.1 The contractor shall assemble program data (e.g. schedule and performance) and provide technical programmatic planning and development of readiness reviews. (e.g. Hardware Acceptance Review, Mission Readiness Review, Independent Readiness Review, NRO Mission Assurance Review, Flight Readiness Review, Executive Mission Readiness, Launch Readiness Review, and Post-Flight Review).

1.2.1.2.4.2 As a member of the Rehearsal Anomaly Team (RAT), the contractor shall plan, develop and de-conflict activities, evaluate goals and objectives for launch campaign operations readiness reviews, exercises, and rehearsals (e.g. tabletop exercises, stand-alone, and integrated crew exercises and rehearsals) IAW the Baseline Government EELV Rehearsal Plan. The contractor shall define evaluation criteria, design and develop anomaly scenarios (e.g. design script inputs and drop inputs to members on console), and evaluate mission launch teams on operations execution performance. The contractor shall report findings to the integrated launch team. The contractor shall identify lessons learned and integrate them into existing operations for continuous launch program improvement, and update the Baseline Government EELV Rehearsal Plan. The RAT is composed of technical representatives from the LV and Space Vehicle (SV) program offices, Launch Vehicle Contractors (LVCs) and Space Vehicle Contractors (SVCs), NRO, and the launch site wings. The RAT plans, develops, and evaluates goals and objectives for mission campaign exercises and rehearsals.

1.2.1.2.5 The contactor shall provide continuity of mission management activities and knowledge transfer to government mission team members.

1.2.1.3 SYSTEMS SAFETY ENGINEERING

1.2.1.3.1 The contractor shall provide systems safety engineering for activities at LAAFB. The contractor shall maintain the System Safety documentation (e.g. System Safety Management Plan (SSMP) and Programmatic Environmental Safety and Health Evaluations (PESHE)) IAW National Security Space (NSS) 03-01, and AFI 91-202 AFSPCSUP1, to ensure compliance with applicable Department of Defense (DoD) and Air Force (AF) requirements.

1.2.1.3.2 The contractor shall review and verify LVC documentation and activities are in compliance with applicable system safety requirements (e.g.

EWR 127-1, AFSPCMAN 91-710, MIL-STD-882, and AFI 91-202 AFSPCSUP1) and provide the government with written documentation of discrepancies.

1.2.1.3.3 The contractor shall identify and track open launch and range safety items, and provide the government with written recommendations for disposition of the open items.

1.2.1.3.4 The contractor shall provide systems safety assessments of payload integration, ground testing, and flight safety activities to ensure mission readiness. The contractor shall report noted deficiencies to the government within 1 work day of the assessments.

1.2.1.3.5 The contractor shall analyze the design and testing of launch vehicle flight termination systems and other critical safety components to provide the government with written recommendations for risk mitigation.

1.2.1.3.6 The contractor shall assess the LVC’s hazard analyses to verify all hazards are properly identified and mitigated; findings shall be reported in written form to the government.

1.2.1.3.7 The contractor shall evaluate mission unique EWR 127-1 requirements and provide the government with written documentation of discrepancies and potential cost impacts.

1.2.1.3.8 The contractor shall provide system safety engineering analysis for the deactivation and disposition of LRSW launch systems. This will include providing system safety and environmental safety analysis reports related to disposition alternatives and closeout activities.

1.2.1.3.9 The contractor shall activate the LRSW Mishap Control Center (MCC) for each launch and provide communication between LRSW and the Mission Director, in case of a mishap. MCC activities will be conducted IAW LRSW Operating Instruction (OI) 91-201.

1.2.1.3.10 The contractor shall develop and maintain mishap investigation policies and processes.

1.2.1.3.11 The contractor shall participate as required in internal mishap investigations including system safety and environmental safety analyses related to disposition alternatives and closeout activities.

1.2.1.4 SYSTEMS ENVIRONMENTAL ENGINEERING

1.2.1.4.1 The contractor shall evaluate the LVC’s (need to change this with LVC throughout document) designs, operations, and procedures for launch vehicles, and ground support systems to verify compliance with all environmental requirements.

1.2.1.4.1.1 The contractor will evaluate the LVC’s environmental compliance through all programmatic phases, from concept development through program closeout and disposal.

1.2.1.4.1.2 The contractor shall provide written strategies needed to achieve and maintain compliance with federal, state, and local environmental laws, regulations, requirements, and standards.

1.2.1.4.1.3 The contractor shall review launch Engineering Change Proposals (ECPs), and provide written mitigation options to decrease or limit potential environmental liabilities and costs.

1.2.1.4.2 The contractor shall survey LVC pollution prevention progress to ascertain compliance with the provisions of applicable federal, state, and local laws, regulations, requirements, and standards; providing written documentation of compliance status.

1.2.1.4.3 The contractor shall construct Requests for Environmental Impact Analysis (AF Form 813) to initiate the National Environmental Policy Act (NEPA) process for launch activities.

1.2.1.4.4 The contractor shall review launch operations NEPA

documentation to verify that the documentation complies with all applicable requirements.

1.2.1.4.5 The contractor shall perform research and analyses of environmental impacts associated with launch operations IAW EELV Environmental Mitigation Plans (EMP). This includes special studies required by local and federal governments.

1.2.1.4.6 The contractor shall assess proposed federal, state and local environmental requirements, regulations, laws, and standards to determine potential impacts to launch operations; providing written documentation of impact analyses.

1.2.1.4.7 The contractor shall attend program reviews, working groups, Technical Interchange Meetings (TIMs), and Technical Exchange Meetings TEMs) to ensure compliance with federal, state, local environmental laws, regulations, requirements, and standards. The contractor shall report compliance status, in writing.

1.2.1.4.8 The contractor shall maintain and update the PESHE and EMP.

1.2.1.5 SYSTEMS SECURITY & INFORMATION ASSURANCE

1.2.1.5.1 The contractor shall plan, develop, and implement system security, program protection planning and information assurance policies, products, and procedures in accordance with National Security Space (NSS) Acquisition Policy 03-01, DoDD 5000.1 DoDD 5200.1, DoDD 5200.39, DoDD 5200.1-M, AFI 63-17, AFPAM 63-1701, and SMC AFPEO/SP Policy 63-17.

1.2.1.5.2 The contractor shall safeguard critical program data (e.g.

classified and unclassified controlled information) IAW AFI 31-401. The contractor shall conduct semi-annual LRSW self-inspections using the most current Air Force Space Command (AFSPC) checklists (e.g., Acquisition Intelligence Inspection Checklist, AFSPCCL 63-17, APSPCCL 31-13, APSPCCL 31-14, and AFSPCCL 31-15). The contractor shall document and provide a written report of results and any subsequent actions, and participate in periodic Integrated Program Reviews (IPRs).

1.2.1.5.3 The contractor shall update and maintain currency of the Enterprise Information Technology Data Repository (EITDR) database as required to ensure mandatory compliance with Federal Information Security Management Act (FISMA) reporting.

1.2.1.5.4 PROGRAM PROTECTION PLANNING

1.2.1.5.4.1 The contractor shall conduct a program protection scheme to support program protection planning for LRSW, specifically:

• Update Program Protection Plans with annual reviews as required

• Develop Integrated Threat Assessments with 18 month updates and as required

• Develop System Threat and Analysis Reports with 18 month updates and as required

• Update Security Classification Guides as required

• Develop Technology Assessment and Control Plans as required

• Host and record system security working group meetings quarterly or as required

1.2.1.5.4.2 The contractor shall participate with National Security Administration (NSA), US Strategic Command (USSTRATCOM), Air Force Space Command (AFSPC), SMC, user and operator representative, LRSW and industry, in the evaluation and review of evolving security and protection concepts and policies. The contractor shall review and/or analyze the LVC’s program protection implementation plans for the protection of Critical Program Information and Critical System Resources (CPI/CSR).

1.2.1.5.4.3 The contractor shall implement and integrate the Systems Security Engineering (SSE) process into LRSW systems engineering, configuration management and specialty engineering efforts. The SSE process will support Program Protection Planning as identified in reference material.

1.2.1.5.4.4 The contractor shall review, analyze and provide SSE assessments (cost benefit/value analysis) to program and segment level documents to include but not limited to:

• Operational Requirements Documents (ORD)

• Mission Need Statement(s) (MNS)

• Concept of Operation (ConOps)

• Single Acquisition and Management Plan(s) (SAMP)

• Test and Evaluation Master Plan (TEMP)

• Risk Analyses/Trade Studies

• System Engineering Management Plans (SEMP)

• Program Management Directive(s) (PMD)

1.2.1.5.4.5 The contractor shall support the LRSW Change Board processes and recommend concurrence, or non-concurrence changes, as security/protection impacts are identified. The contractor shall provide recommendations along with cost benefits analyses.

1.2.1.5.4.6 The contractor shall process public and foreign release requests and associated documentation Designated Disclosure Letter (DDL) and Foreign Disclosure Officer (FDO) documentation by conducting initial review, determining coordination routing, correlating evaluation comments/recommendations, and preparing approval/disapproval final documentation for LRSW and the FDO.

1.2.1.5.5 MISSION SYSTEMS CERTIFICATION AND ACCREDITATION

1.2.1.5.5.1 The contractor shall conduct a mission systems Certification and

Accreditation (C&A) program for LRSW mission systems in accordance with the DoD Information Assurance (IA) C&A Program (DIACAP). The contractor shall also:

• Develop, maintain, and publish DIACAP schedule for each LRSW mission system

• Plan, develop and publish requests for approvals to operate with updates as required

• Plan, develop and publish requests for interim approvals to operate

• Plan, develop and publish request for interim approvals to test/connect

• Maintain a tracking system for DIACAP Artifacts

• Develop C&A process for LRSW space mission systems and associated test/maintenance labs

• Integrate DIACAP into mission systems overall information management system or like system

• Initiate, publish and maintain mission systems DIACAP ScoreCard

• Initiate, publish and maintain mission systems DIACAP Plan of Action & Milestone (POA&M)

• Conduct and maintain records for mission system Certification Readiness Reviews

• Conduct, analyze and recommend System Certification Risk IAW the DIACAP

• Ensure DIACAP products and artifacts are accomplished on-time through the entire life-cycle

• Conduct information assurance annual analysis on security postures against published standards

• Report compliance and a consistent method to meet the Federal Information Security Management Act (FISMA) and DIACAP requirements

1.2.1.5.5.2 The contractor shall develop LRSW mission systems certification policies, programs, procedures and reports for new and evolving IA system requirements.

1.2.1.5.5.3 The contractor shall establish and maintain a liaison with the program office, system user, operator, certifier, NSA and designated approval authority through the security working groups, such as Integrated Product Teams (IPTs) and other forums.

1.2.1.6 PRODUCT ASSURANCE

1.2.1.6.1 The contractor shall provide reviews, as assigned, of manufacturing, production, and quality processes as a member of the pedigree team for pedigreed parts IAW pedigree guidance documentation (e.g., EELV Atlas V Pedigree Review Guidelines, Delta Hardware Pedigree Handbook, internal documentation). The contractor shall have a working knowledge of flight hardware associated with the EELV and heritage family of launch vehicles (e.g. structural, mechanical, propulsion, guidance and control systems, ordnance, pressurization, and feed line components).

1.2.1.6.2 The contractor shall evaluate production operations and quality hardware history. The contractor shall identify and document hardware pedigree issues IAW internal pedigree guidance.

1.2.1.6.3 The contractor shall examine LV production operations to include identification of key process parameters, associated monitoring metrics, variability, determination of “statistical control”, capability and capacity (e.g. fusion and friction stir welding, metal forming, electronics assembly, printed wiring board production, wire harness assembly, X-Ray inspection and other nondestructive inspection techniques, electrical testing, final assembly, and transportation methods). The contractor shall document conditions adverse to quality production. The contractor shall provide documentation (e.g. written reports, email documentation, or presentation).

1.2.1.6.4 The contractor shall investigate production issues and quality escapes, anomalies, and failures. The contractor shall provide analysis of LVC root-cause determination and verify corrective action implementation and objectively monitor process health.

1.2.1.6.5 The contractor shall provide technical readiness assessments to the government. The contractor shall provide documentation (e.g. written reports, email documentation, or presentation).

1.2.1.6.6 Contractor Quality Engineers (QEs) shall work with prime contractors and suppliers in reviewing production and quality systems.

Contractor QEs will assess effectiveness of these systems and, where directed, participate in implementation of modern quality methods such as statistical process control, sampling methods, statistical analysis, and design of experiments (DOE).

1.2.1.6.7 The contractor shall assess and develop metrics to examine prime contractor and supplier production and quality performance, such as cost of quality, first time quality, and metrics associated with reject and rework rates and escapes. The contractor shall possess the expertise to perform statistical analysis to identify focus areas adverse to quality or manufacturing operations.

1.2.1.6.8 The contractor shall assess production related issues to determine impacts to the overall mission assurance, and suggest mitigation methods.

1.2.1.6.9 The contractor shall assess impact and risk associated with component and process anomalies, Government Industry Data Exchange Program (GIDEP) alerts and notifications, and other component and process issues associated with the Parts Material and Process Control Board (PMPCB). The contractor will also develop associated corrective action plan recommendations.

1.2.1.6.10 The contractor shall assess LVC product assurance projects and indicate methods to enhance effectiveness and efficiencies of such projects as: non-conformance reduction; lean manufacturing initiatives foreign & domestic object damage and quality escape elimination.

1.2.1.6.11 The contractor shall attend audits, Program Management Reviews, Corrective Action Boards and provide written assessment.

1.2.1.7 LAUNCH SCHEDULE MANAGEMENT

1.2.1.7.1 The contractor shall analyze the launch activity scheduling process and provide an integrated approach for the development of an integrated Wing Master Schedule (WMS). The contractor shall ensure the WMS tool is compatible with the LVC-provided schedules.

1.2.1.7.2 The contractor shall develop and maintain an integrated WMS, which includes launch impacting activities of Launch Group (LCG), LVC, ELSS/LV_LSC, SMC reviews, and Range Group acquisition and sustainment.

The contractor shall analyze the WMS and provide the government with options to mitigate conflicts and milestone slippages.

1.2.1.7.3 The contractor shall update the Space Launch Manifest resident on the Launch Information Support Network (LISN), or equivalent (includes LRSW and Office of Space Launch (OSL) missions). The contractor shall evaluate the Space Launch Manifest identifying potential scheduling conflicts (launch dates, facilities, rehearsals, etc) and provide an assessment to LRSW, on available options. The contractor shall assemble an LRSW Launch Manifest using the LISN. The contractor shall post the manifest on LRSW’s Integrated Data Environment (IDE) and distribute via email to government provided distribution list.

1.2.1.7.4 The contractor shall develop and maintain the LRSW Launch Manifest Operating Instruction.

1.2.1.8 LAUNCH RISK MANAGEMENT

1.2.1.8.1 The contractor shall evaluate current EELV risk management processes for compliance with the standards set in the Risk Management Guide for DoD Acquisition. The contractor shall bring deficiencies, and recommended changes, to LRSW Chief Engineer’s attention. The contractor shall document the EELV risk management process, update the EELV Risk Management Plan, and submit the plan for Government approval. The contractor shall review the EELV Risk Management Plan annually, and provide LRSW with recommended changes. TOR-2005(8583)-4018, TOR- 2005(8583)-4019, and ANSI/PMI 99-001-2004 will be used as references.

1.2.1.8.2 The contractor shall develop a weekly consolidated Atlas, Delta, and Launch and Test Range System risk status report for the LRSW Chief Engineer. The contractor shall conduct a monthly LRSW Risk Management Board (RMB), chaired by the Chief Engineer. The contractor shall present the status of all current and potential risks at the RMB. The contractor shall continue to status all risks identified for tracking by the Chief Engineer.

1.3 CCAFS PWS

1.3.1 SE&I IN SUPPORT OF LRSW LAUNCH SERVICES

1.3.1.1 LAUNCH SITE SYSTEMS ENGINEERING AND INTEGRATION

ACTIVITIES

1.3.1.1.1 The contractor shall actively monitor the launch flow process and synthesize lessons learned. The contractor shall input all identified lessons learned into the Launch Verification Database (LVDB) within three work days of identification.

1.3.1.1.2 The contractor shall provide launch site activity mission assurance related recommendations to the 45th Launch Group Commander (45 LCG/CC), 45th Launch Group Technical Director (45 LCG/TD), and the 5th Space Launch Squadron Commander (5 SLS/CC) on heritage and EELV launch site activities.

1.3.1.1.3 The contractor shall maintain and update the 45th Launch Group (45 LCG) strategic plan, 45 LCG operating instructions, and 45 LCG ConOps.

The contractor shall review draft Launch and Range related AF and AFSPC-level instructions for technical validity and recommend revisions within three work days of receipt of documents.

1.3.1.1.4 The contractor shall maintain and update the 45 LCG technical risk management program documentation. The contractor shall identify risks and recommend mitigation approaches.

1.3.1.1.5 The contractor shall participate in system TIMs/TEMs and reviews, providing technical expertise and inputs.

1.3.1.1.6 The contractor shall manage and act as the primary point of contact for the LVDB structure and use.

1.3.1.1.6.1 Conduct training for the LVDB;

1.3.1.1.6.2 Track and manage status of Launch Verification Matrix (LVM) loading into LVDB;

1.3.1.1.6.3 Ensure consistent use of LVDB; and

1.3.1.1.6.4 Coordinate with 5 SLS and LVDB developers regarding database enhancements.

1.3.1.1.7 The contractor shall provide system integration for launch flow processing, including range and range systems for heritage and EELV programs. The contractor shall comply with and complete required tasks identified in the Master Mission Checklist (MMC) for each mission.

1.3.1.1.8 The contractor will be an active participant and contributor in all Operational Status Review Meetings, and be responsible for briefing the status of the MMC.

1.3.1.1.9 The contractor shall maintain and update squadron operating instructions, and ConOps. The contractor shall review draft squadron booster and launch flow processing instructions for technical validity, recommend revisions, and implement approved changes as required.

1.3.1.1.10 The contractor shall provide technical guidance and technical training for range-unique LV_LSC console operations. The contractor will be an active contributor/member/participant in the RAT by identifying and scheduling necessary resources for exercises.

1.3.1.1.11 The contractor shall develop and execute anomaly scenarios;

(e.g., develop script inputs and drop inputs to members on console).

1.3.1.1.12 The contractor shall establish evaluation criteria, evaluate 45 LCG personnel on consoles and report findings to senior leadership; as well as, identify and input all lessons learned into the LVDB within two work days of End of Exercise (EndEx).

1.3.1.1.13 The contractor shall assimilate and provide technical evaluation of schedules from multiple launch campaigns and produce an integrated launch flow processing (create standard definition for glossary-what it entails) master schedule.

1.3.1.1.14 The contractor shall provide a scheduled assessment of launch vehicle readiness, technical schedule risks and mitigation recommendations.

1.3.1.1.15 The contractor shall provide written status to Launch Mission Managers.

1.3.1.2 LAUNCH VEHICLE LAUNCH SUPPORT CENTER (LV_LSC)

1.3.1.2.1 The contractor shall perform ELSS integration in support of launch vehicle systems operations to include but not limited to the following tasks:

1.3.1.2.1.1 The contractor shall maintain configuration management of current LV_LSC architecture and support processes in accordance with source requirements documents to include: SRD, ConOps and DCRD.

1.3.1.2.1.2 The contractor shall develop and maintain an integrated schedule of the LV_LSC events and provide de-confliction recommendations of EELV processing and launch rehearsals to Launch Mission Manager and implement approved schedule.

1.3.1.2.1.3 The contractor shall develop maintenance plans for all equipment in the LV_LSC as well as EELV acquired equipment and monitor compliance with these plans.

1.3.1.2.1.4 The contractor shall act as the technical point of contact for mission communications kick-off meetings. The contractor shall analyze requirements and configure LV_LSC for each launch campaign.

1.3.1.3 LAUNCH SITE SOFTWARE DEVELOPMENT AND SUSTAINMENT

1.3.1.3.1 The contractor shall maintain and manage mission assurance and launch verification software applications (e.g. the LVDB, Critical Data Management Applications (CDMAs), Change Problem Request (CPR) databases, and launch checklists).

1.3.1.3.2 The contractor shall develop and maintain all software documentation (e.g. commenting in the code, user’s manuals, training guides, explanation of the software coding, and audit/change logs) and make these documents available for government use.

1.3.1.3.3 The contractor shall provide end user clarification for proper use of software and program features and functionality changes.

1.3.1.3.4 The contractor shall host and maintain a fully integrated data environment for mission assurance and launch verification software applications on a government provided server. The server shall be accessible to all authorized users, to include remote users. The contractor shall verify configuration requirements of all computers supporting the above listed mission assurance and launch verification software.

1.3.1.3.5 The contractor shall perform Structured Query Language (SQL) server database administration, database programming, backup, disaster recovery and security to prepare for launch operations, satellite and booster processing, and contingency/anomaly resolution.

1.3.1.3.6 The contractor shall provide system-level management of mission assurance and launch verification software to include oversight of:

structure and use, training development, and system maintenance and upgrades.

1.3.2 MISSION INTEGRATION MANAGEMENT

1.3.2.1 The contactor shall provide continuity of mission management activities and knowledge transfer to government mission team members.

1.3.3 SYSTEMS SAFETY ENGINEERING

1.3.3.1 The contractor shall provide systems safety engineering for activities at CCAFS. The contractor shall review the System Safety documentation (e.g. SSMP and PESHE) IAW NSS 03-01, and AFI 91-202 AFSPCSUP1, to ensure compliance with applicable DoD and Air Force requirements.

1.3.3.2 The contractor shall review and verify LVC documentation and activities are in compliance with applicable system safety requirements (e.g. EWR 127-1, AFSPCMAN 91-710, MIL-STD-882, and AFI 91-202 AFSPCSUP1) and provide the government with written documentation of discrepancies.

1.3.3.3 The contractor shall identify and track open launch and range safety items, and provide the government with written recommendations for disposition of the open items.

1.3.3.4 The contractor shall provide systems safety assessments of payload integration, ground testing, and flight safety activities to ensure mission readiness.

The contractor shall report noted deficiencies to the government within 24 hours of the assessments.

1.3.3.5 The contractor shall analyze the design and testing of launch vehicle flight termination systems and other critical safety components to provide the government with written recommendations for risk mitigation.

1.3.3.6 The contractor shall assess the LVC’s hazard analyses to verify all hazards are properly identified and mitigated; findings shall be reported in written form to the government.

1.3.3.7 The contractor shall evaluate mission unique EWR 127-1 requirements and provide the government with written documentation of discrepancies and potential cost impacts.

1.3.3.8 The contractor shall provide system safety engineering analysis for the deactivation and disposition of LRSW systems. This will include providing system safety and environmental safety analysis reports related to disposition alternatives and closeout activities.

1.3.4 SYSTEMS ENVIRONMENTAL ENGINEERING

1.3.4.1 The contractor shall evaluate the LVC’s designs, operations, and procedures for launch vehicles, and ground support systems to verify compliance with all environmental requirements.

1.3.4.1.1 The contractor will evaluate the LVC’s environmental compliance through all programmatic phases, from concept development through program closeout and disposal.

1.3.4.1.2 The contractor shall provide written strategies needed to achieve and maintain compliance with federal, state, and local environmental laws, regulations, requirements, and standards.

1.3.4.1.3 The contractor shall review launch ECPs, and provide written mitigation options to decrease or limit potential environmental liabilities and costs.

1.3.4.2 The contractor shall survey LVC environmental compliance and pollution prevention progress to ascertain compliance with the provisions of applicable federal, state, and local laws, regulations, requirements, and standards; providing written documentation of compliance status.

1.3.4.3 The contractor shall construct Requests for Environmental Impact Analysis (AF Form 813) to initiate the NEPA process for launch activities.

1.3.4.4 The contractor shall review launch operations NEPA documentation to verify that the documentation complies with all applicable requirements.

1.3.4.5 The contractor shall perform research and analysis of environmental impacts associated with launch operations IAW EELV EMP. This includes special studies required by local and federal governments.

1.3.4.6 The contractor shall assess proposed federal, state and local environmental requirements, regulations, laws, and standards to determine potential impacts to launch operations; providing written documentation of impact analyses.

1.3.4.7 The contractor shall attend program reviews, working groups, TIMs, audits (e.g. Occupational Health Compliance Assessment and Management Program (ESOHCAMP)), evaluations, and assessments to ensure compliance with federal, state, local environmental laws, regulations, requirements, and standards.

The contractor shall report on compliance status, in writing.

1.3.4.8 The contractor shall review and provide updates to the PESHE and EMP.

1.3.4.9 Participate in ESOHCAMP compliance process as follows:

1.3.4.9.1 Prepare for ESOHCAMP audits by attending TIMs and

assessing compliance with applicable laws, regulations, and standards

1.3.4.9.2 Participate in ESOHCAMP audit as required

1.3.4.9.3 Review the audit report and develop a mitigation plan for resolution of environmental impacts and issues

1.3.4.9.4 Validate that government approved mitigation plan is implemented and completed.

1.3.4.10 The contractor shall monitor all activities for Hazardous Material (HAZMAT) management, environmental and bioenvironmental compliance and pollution prevention to ensure compliance with applicable laws, standards, regulations, and codes.

1.3.5 SYSTEMS SECURITY & INFORMATION ASSURANCE

1.3.5.1 The contractor shall manage, and implement system security, program protection planning and information assurance policies, products, and procedures in accordance with NSS Acquisition Policy 03-01, DoDD 5000.1 DoDD 5200.1, DoDD 5200.39, DoDD 5200.1-M, AFI 63-17, AFPAM 63-1701, and SMC AFPEO/SP Policy 63-17.

1.3.5.2 The contractor shall safeguard critical program data (e.g. classified and unclassified controlled information) IAW AFI 31-401. The contractor shall document and provide a written report of results and any subsequent actions, and participate in periodic IPR’s.

1.3.5.3 The contractor shall update and maintain currency of the EITDR database as required to ensure mandatory compliance with FISMA reporting.

1.3.6 PRODUCT ASSURANCE (N/A)

1.3.7 LAUNCH SCHEDULE MANAGEMENT

1.3.7.1 The contractor shall develop and maintain an integrated LCG Master Schedule that includes key 45 LCG activities and existing schedules (e.g. individual mission schedules (LVC provided)). The contractor shall analyze the 45 LCG Master Schedule and provide the government with options to mitigate conflicts and milestone slippages. The contractor shall, at a minimum, provide a scheduled assessment of LV and SV readiness, technical schedule risks and mitigation recommendations. The contractor shall provide written status to Launch and Spacecraft Mission Managers.

1.3.7.2 The contractor shall identify, analyze, and recommend mitigations on integrated launch process flow issues including technical review and recommendations to LCG technical correspondence and taskers. The contractor shall update mission schedule documentation, including, but not limited to: weekly Vehicle Activity Review slides, weekly LCG mission assurance and readiness slides, and weekly senior leader meeting documents and slides.

1.3.7.3 The contractor shall compile inputs from LVC, SVC, SV program office and 45th Space Wing (45 SW) agencies to provide strategic logistics planning to create a detailed schedule de-conflicting infrastructure requirements, anomaly reviews, and daily vehicle processing activities.

1.3.7.4 The contractor shall develop an integrated schedule identifying the critical path and provide written detailed status of 45 LCG launch flow process activities (e.g. MDA, EELV, and DMSP) and 45 SW launch support activities (e.g. planned power & water outages, road maintenance, and controlled burns) to the Group Control Center (GCC). The GCC serves as a single point command and control (C2) node for 45 LCG during all processing, launch, and contingency operations.

The contractor shall participate in daily LCG Ops meeting.

1.3.8 LAUNCH RISK MANAGEMENT (N/A)

1.4 VAFB PWS

1.4.1 SE&I IN SUPPORT OF LRSW LAUNCH SERVICES

1.4.1.1 LAUNCH SITE SYSTEMS ENGINEERING AND INTEGRATION

ACTIVITIES

1.4.1.1.1 The contractor shall actively monitor the launch flow process and synthesize lessons learned. The contractor shall input all identified lessons learned into the LVDB within three work days of identification.

1.4.1.1.2 The contractor shall provide launch site activity mission assurance related recommendations to the 4th Space Launch Squadron Commander (4 SLS/CC) and 4th Space Launch Squadron Technical Director (4 SLS/TD) on heritage and EELV launch site activities.

1.4.1.1.3 The contractor shall maintain and update 4 SLS operating instructions, and Concept of Operations (ConOps). The contractor shall review draft Launch and Range related AF and AFSPC-level instructions for technical validity and recommend revisions.

1.4.1.1.4 The contractor shall maintain and update the 4 SLS technical risk management program documentation. The contractor shall identify risks and recommend mitigation approaches.

1.4.1.1.5 The contractor shall participate in system TIMs/TEMs and reviews, providing technical expertise and inputs.

1.4.1.1.6 The contractor shall manage and act as the primary point of contact for the LVDB structure and use.

1.4.1.1.6.1 Conduct training for the LVDB;

1.4.1.1.6.2 Track and manage status of LVM loading into LVDB;

1.4.1.1.6.3 Ensure consistent use of LVDB; and

1.4.1.1.6.4 Coordinate with 4 SLS and LVDB developers regarding database enhancements.

1.4.1.1.7 The contractor shall provide system integration for launch flow processing, including range and range systems for heritage and EELV programs.

1.4.1.1.8 The contractor shall maintain and update squadron operating instructions, and ConOps. The contractor shall review draft squadron booster and launch flow processing instructions for technical validity, recommend revisions, and implement approved changes as required.

1.4.1.1.9 The contractor shall provide technical guidance for range-unique LV_LSC console operations. The contractor will be an active contributor/member/participant in the RAT by identifying and scheduling necessary resources for exercises.

1.4.1.1.9.1 The contractor shall develop and execute anomaly scenarios;

(e.g., develop script inputs and drop inputs to members on console).

1.4.1.1.9.2 The contractor shall establish evaluation criteria, evaluate personnel on consoles and report findings to senior leadership; as well as identify and input all lessons learned into the LVDB within two work days of EndEx.

1.4.1.1.10 The contractor shall assimilate and provide technical evaluation of schedules from multiple launch campaigns and produce an integrated launch flow processing (create standard definition for glossary-what it entails) master schedule.

1.4.1.1.10.1 The contractor shall provide a scheduled assessment of launch vehicle readiness, technical schedule risks and mitigation recommendations.

1.4.1.1.10.2 The contractor shall provide written status to Launch Mission Managers.

1.4.1.1.11 The contractor shall participate at launch campaign planning meetings, readiness reviews, exercises, tests, and rehearsals (e.g. Working Groups, Wet Dress Rehearsals, Launch Readiness Reviews, and Flight Readiness Reviews). The contractor shall provide a written summation, within five working days of event conclusion.

1.4.1.1.12 The contractor shall provide payload processing and related activities technical risk assessments for LV Mission Assurance. The contractor shall document risk assessment, comments, and engineering analyses using a Mission Assurance Verification Matrix (MAVM) task database, (e.g. LVDB and Stargate) to inform LV Mission Managers.

1.4.1.1.13 The contractor shall monitor and provide oral and written status of the LVC processing activities and anomaly resolution to the LV Mission Managers, Flight Technical Leads, and Flight Commanders.

1.4.1.1.14 The contractor shall review flight/spacecraft hardware processing and testing to ensure compliance with approved LVC procedures and verify all discrepancies are satisfactorily addressed, closed out, and approved by government.

1.4.1.2 EELV LAUNCH VEHICLE LAUNCH SUPPORT CENTER (LV_LSC)

1.4.1.2.1 The contractor shall plan for extended support of requirements during the last 48 hours of launch campaigns, anticipate an average of two launches per year. Tasks include but are not limited to the following:

1.4.1.2.1.1 The contractor shall maintain configuration management of current LV_LSC architecture and support processes in accordance with source requirements documents to include: SRD, ConOps and DCRD.

1.4.1.2.1.2 The contractor shall develop and maintain an integrated schedule of the LV_LSC events and provide de-confliction recommendations of EELV processing and launch rehearsals to Launch Mission Manager and implement approved schedule.

1.4.1.2.1.3 The contractor shall develop maintenance plans for all equipment in the LV_LSC as well as EELV acquired equipment and monitor compliance with these plans.

1.4.1.2.1.4 The contractor shall act as the technical point of contact for mission communications kick-off meetings. The contractor shall analyze requirements and configure LV_LSC for each launch campaign.

1.4.1.3 EELV LAUNCH SITE SOFTWARE DEVELOPMENT AND

SUSTAINMENT (this task will be phased in ~ April 2010)

1.4.1.3.1 The contractor shall maintain and manage mission assurance data in the Launch Verification Matrix database.

1.4.1.3.2 The contractor shall develop and maintain all software documentation (e.g. commenting in the code, user’s manuals, training guides, explanation of the software coding, and audit/change logs) and make available for government use.

1.4.1.3.3 The contractor shall provide end user clarification for proper use of software and program features and functionality changes.

1.4.1.3.4 The contractor shall host and maintain a fully integrated data environment for mission assurance and launch verification software applications on a government provided server. The server shall be accessible to all authorized users, to include remote users located at CCAFS and LAAFB. The contractor shall maintain all administrative computers supporting the above listed mission assurance and launch verification software.

1.4.1.3.5 The contractor shall perform SQL server database

administration, database programming, backup, disaster recovery and security to prepare for launch operations, satellite and booster processing, and contingency/anomaly resolution. Contractor performance/scheduling of this effort shall allow for flexibility to address off-hour server maintenance in support of launch operations and/or server backup/disaster recovery.

1.4.1.3.6 The contractor shall provide system-level management of mission assurance and launch verification software to include oversight of:

upgrades.

1.4.1.4 EELV AND HERITAGE SYSTEMS SAFETY ENGINEERING

1.4.1.4.1 The contractor shall provide systems safety engineering for activities at VAFB. The contractor shall review the System Safety documentation (e.g. SSMP and PESHE) IAW NSS 03-01, and AFI 91-202 AFSPCSUP1, to ensure compliance with applicable DoD and Air Force requirements.

1.4.1.4.2 The contractor shall review and verify LVC documentation and activities are in compliance with applicable system safety requirements (e.g.

EWR 127-1, AFSPCMAN 91-710, MIL-STD-882, and AFI 91-202 AFSPCSUP1) and provide the government with written documentation of discrepancies.

1.4.1.4.3 The contractor shall identify and track open launch and range safety items, and provide the government with written recommendations for disposition of the open items.

1.4.1.5 EELV AND HERITAGE SYSTEMS ENVIRONMENTAL ENGINEERING

1.4.1.5.1 The contractor shall evaluate the LVC’s designs, operations, and procedures for launch vehicles, and ground support systems to verify compliance with all environmental requirements.

1.4.1.5.1.1 The contractor will evaluate the LVC’s environmental compliance through all programmatic phases, from concept development through program closeout and disposal.

1.4.1.5.1.2 The contractor shall provide written strategies needed to achieve and maintain compliance with federal, state, and local environmental laws, regulations, requirements, and standards.

1.4.1.5.1.3 The contractor shall review launch ECPs, and provide written mitigation options to decrease or limit potential environmental liabilities and costs.

1.4.1.5.2 The contractor shall survey LVC environmental compliance and pollution prevention progress to ascertain compliance with the provisions of applicable federal, state, and local laws, regulations, requirements, and standards; providing written documentation of compliance status.

1.4.1.5.3 The contractor shall construct Requests for Environmental Impact Analysis (AF Form 813) to initiate the NEPA process for launch activities.

1.4.1.5.4 The contractor shall review launch operations NEPA

documentation to verify that the documentation complies with all applicable requirements.

1.4.1.5.5 The contractor shall perform research and analysis of environmental impacts associated with launch operations IAW EELV EMP.

This includes special studies required by local and federal governments.

1.4.1.5.6 The contractor shall assess proposed federal, state and local environmental requirements, regulations, laws, and standards to determine potential impacts to launch operations; providing written documentation of impact analyses.

1.4.1.5.7 The contractor shall attend program reviews, working groups, TIMs, audits (e.g. ESOHCAMP), evaluations, and assessments to ensure compliance with federal, state, local environmental laws, regulations, requirements, and standards. The contractor shall report on compliance status, in writing.

1.4.1.5.8 The contractor shall review and provide updates to the PESHE and EMP.

1.4.1.5.9 Participate in ESOHCAMP compliance process as follows:

1.4.1.5.9.1 Prepare for ESOHCAMP audits by attending technical interchange meetings (TIMs) and assessing…