PWS_17_Oct_16.pdf

Current as of 17 October 2016

PERFORMANCE WORK STATEMENT (PWS)

SAFETY HAZARD ANALYSIS AND RISK PROCESSING (SHARP) SYSTEM

45th Space Wing Safety

Part 1

General Information

1. GENERAL: This is a technical services contract to provide SHARP technical support. The Government shall not exercise any supervision or control over the contract providers performing the services herein. Such contract service providers shall be accountable solely to the contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and for technical services necessary to perform SHARP technical support as defined in this Performance Work Statement (PWS) except for those items specified as Government Furnished Services. The contractor shall perform to the standards in this PWS. (CDRL A100)

1.2 Background: All launch safety analysis computer systems require sustainment. The SHARP system performs very complex flight and risk analyses using over 2 million lines of executable software code what was previously processed in part by a deteriorating CYBER mainframe computer system replaced with the more modern, flexible SHARP system. SHARP is required to function in a very dynamic environment where new mission requirements (e.g., new launch vehicles, modifications to existing launch vehicles, new flight profiles over populated areas) require modeling software changes. SHARP is required to comply with over 100 DoD Information Assurance Certification and Accreditation Process (DIACAP) controls and the stringent configuration management controls that are imposed by 45th Space Wing Instruction (45 SWI) 10-602, 45th Space Wing Eastern Range Acceptance Process and 45 SWI 91-701, 45th Space Wing Launch Safety Software Management.

1.3 Objectives: The contractor shall provide for both flight and risk analysis technical support as described herein. Contractor resources shall provide adequate support of scheduled and contingency activities.

1.4 Scope: This work statement identifies the technical support required to augment and operationally implement the comprehensive safety program of the 45th Space Wing (45 SW) as it pertains to the SHARP system. SHARP is the designation for the hardware, software and procedures used to perform flight analysis and risk analysis by 45 SW/SEL analysts in support of space launch missions at the Eastern Range.

The contractor shall provide resources necessary to support the launch safety functions described herein for flight analysis software models used by 45 SW/SELF analysts to produce operational products for flight control and risk analysis software models used by 45 SW/SELR analysts to determine risks associated with launch hazards (e.g., debris impact, toxic effluent exposure and distant focusing overpressure effects).

These models are either deterministic or probabilistic. The deterministic models run on laptops or PCs;

whereas, the probabilistic models typically run on a Beowulf CPU cluster. The contractor shall attend and participate in Sustainment safety-related meetings or events as deemed necessary by 45 SW Range Safety as it may pertain to SHARP. Additional meetings may be required to meet the needs identified in work related taskings issued under Launch Safety Analysis CLIN as defined in Schedule B. The contractor shall perform studies, develop prototypes and set up proof of concept demonstrations for future range safety systems as funding becomes available and when determined necessary by 45 SW/SE. The contractor shall provide a work breakdown structure (WBS) that adequately addresses the work tasks associated with the PWS. Software models maintained under this contract will be used to support launches of NASA's Space Launch System and other manned launches. Thus, the prime contractor must have achieved a Capability Maturity Model Integration (CMMI) maturity level of at least III (CMMI Level-III).

1.5 Period of Performance: The period of performance shall be for one (1) Base Year of 12 months and two (2) 12-month option years. The period of performance reads as follows:

Phase-in 1 Mar 17 – 31 Mar 17 Base Year 1 Apr 17 – 31 Mar 18 Option Year I 1 Apr 18 – 31 Mar 19 Option Year II 1 Apr 19 – 31 Mar 20

1.6 General Information

1.6.1 Quality Control: The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with (IAW) this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is the means by which he assures himself that his work complies with the requirement of the contract. Within 30 days after contract award, three copies of a comprehensive Quality Control Plan shall be submitted to the Program Office and within 5 working days when changes are made thereafter. After acceptance of the quality control plan the contractor shall receive the contracting officer’s (CO’s) acceptance in writing of any proposed change to his QC system. (CDRL A108)

1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the government must do to ensure that the contractor has performed IAW the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3 Recognized Holidays:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day

1.6.4 Hours of Operation: The contractor is responsible for conducting business between the hours of 7:30 am to 4:30 pm, Monday thru Friday except Federal holidays or when the government facility is closed due to local or national emergencies, administrative closings, or similar government directed facility closings.

For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. The contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the government facility is not closed for the above reasons. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the workforce are essential. Contractor personnel shall be able to work overtime when no satisfactory alternative exists while complying with the work time limitation requirements of AFSPCMAN 91-710, Volume 6, para 5.1.4 (EWR 127-1, Chapter 6, para 6.5.1.4) if applicable.

1.6.5 Place of Performance: The work to be performed under this contract will be performed at contractor facilities or Patrick Air Force Base, FL in Bldg 423.

1.6.6 Type of Contract: The government will award a firm fixed priced Indefinite Delivery – Indefinite Quantity (IDIQ) contract.

1.6.7 Security Requirements: Contractor personnel performing work under this contract must have a SECRET clearance at time of the proposal submission, and must maintain the level of security required for the life of the contract. The security requirements are IAW the DD Form 254, DoD Contract Security Classification Specification listed in section “J” of the contract. The unit security monitor is responsible for initiating this form. The contractor shall ensure that its personnel have the necessary security clearances to perform their duties. A SECRET clearance will be required of all personnel handling up to SECRET information or requiring access to the local area network. The contractor shall be responsible for safeguarding all government property provided for the contractor’s use. At the close of each work period, all government facilities, equipment and materials shall be secured.

1.6.7.1 Physical Security: The contractor shall be responsible for safeguarding all government equipment, information, and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

1.6.7.2 Key Control: The contractor shall establish and implement methods of making sure all keys/key cards issued to the contractor by the government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the contractor by the government shall be duplicated. The contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the CO.

1.6.7.2.1. In the event keys, other than master keys, are lost or duplicated, the contractor shall, upon direction of the CO, re-key or replace the affected lock or locks; however, the government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the government and the total cost deducted from the monthly payment due the contractor.

1.6.7.2.2. The contractor shall prohibit the use of government issued keys/key cards by any persons other than the contractor’s employees. The contractor shall prohibit the opening of locked areas by contractor employees to permit entrance of persons other than contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the CO.

1.6.7.3 Lock Combinations/Cypher Lock: The contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons if locked access is determined to be necessary. The contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the contractor’s Quality Control Plan.

1.6.8 Special Qualifications: The contractor is responsible for ensuring that employees who require access to the Patrick Local Area Network possess and maintain current Information Assurance Technician (IAT) Level I professional certification during the execution of this contract.

1.6.9 Post Award Conference/Periodic Progress Meetings: The contractor agrees to attend any post award conference convened by the contracting activity or contract administration office IAW Federal Acquisition Regulation Subpart 42.5. The CO, Contracting Officer’s Representative (COR), and other government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance.

At these meetings the CO will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the government of problems, if any, being experienced.

Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.10 Contracting Officer’s Representative (COR): The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions; assure that the contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance;

maintain written and oral communications with the contractor concerning technical aspects of the contract;

issue written interpretations of technical requirements, including government drawings, designs, specifications; monitor contractor's performance and notify both the CO and contractor of any deficiencies;

coordinate availability of GFP, and provide site entry of contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the contract.

1.6.11 Key Personnel: The contractor shall provide a point of contact (POC) and alternate who shall be responsible for the performance of the work. The name of this person and/or the alternate shall be designated in writing to the CO. The POC or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The POC or alternate shall be available during normal duty hours (7:30 am to 4:30 pm) Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons. Qualifications for all key personnel are listed below:

1.6.11.1 Contract POC and Alternate: The POC and Alternate must have must have experience and familiarity in mathematical, engineering, and/or quantitative analysis. Additionally, the POC shall be familiar with the contract scope of work, terms and conditions, and related administrative functions.

1.6.11.2 SHARP Systems Administrator: The SHARP Systems Administrator must be able to set up and maintain a work group network and subversion server/client data repositories. Additionally, the systems administrator shall be familiar with the contract scope of work and related administrative functions.

1.6.12 Identification of Contractor Employees: All contractor personnel attending meetings, answering government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. The contractor shall ensure each employee obtains necessary pass and identification items as applicable for contract personnel. Contractor personnel shall maintain identification cards in their possession at all time while on base or while performing their official duties.

1.6.13 Contractor Travel: In support of Launch Safety Analysis task orders, the contractor may be required to travel CONUS during the performance of the task order to install and configure software models, attend meetings, and training. Contractor will be authorized travel expenses consistent with the provisions of the Joint Travel Regulation (JTR). All travel will be negotiated within the task order and reported in accordance with CDRL A107.

1.6.14 Failed Hardware: Should critical system hardware fail (e.g., hard drive, network switch, uninterruptible power supply) the government will purchase and provide necessary replacement(s) to ensure sustainment.

1.6.15 Data Rights: The government has Government Purpose Rights to all technical documents/material and noncommercial software and noncommercial software documentation produced under this contract. All technical documents/ materials and noncommercial software and noncommercial software documentation shall be made available in accordance with applicable Defense Acquisition Regulation DFARs clauses, policy and guidance thereto as referenced and/or incorporated in the resultant contract. These rights does not abrogate any other government rights.

1.6.16 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interest (OCI) as defined in FAR Subpart 9.5. The contractor shall notify the CO immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the CO to avoid or mitigate any such OCI. The contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the CO and in the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the CO may affect other remedies as he or she deems necessary, including prohibiting the contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.17 Phase-In/Phase-Out Period: To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the contractor shall have personnel on board, during the 30-day phase in/phase out periods. During the phase in period, the contractor shall become familiar with performance requirements in order to commence full performance of services on the contract start date.

1.6.17.1 Phase-In: During the phase-in for this contract, the successor shall inspect the network, and become familiar with the SHARP system setup and authority to operate (ATO) requirements. Contractor shall accomplish any required computer based training to acquire access to the Patrick AFB local area network (LAN). The successor contractor shall sign any custody records and obtain office key. Phase-in assistance as defined above is considered within the scope of this contract and no adjustment in estimated costs, fees, price, or other provision by reason of such effort will be warranted. In no event shall presence of the incumbent contractor relieve the successor contractor of contractual responsibilities under this contract.

1.6.17.2 Phase-Out: In addition to the clause “Continuity of Services” (FAR 52.237-3) in Section I, the contractor agrees to give support to and cooperate with any successor that may be designated prior to the expiration of this contract. Phase-in assistance to a successor contractor may be required during the final 30 days of this contract.

1.6.17.2.1 Re-employment: In the event that the contractor is to be replaced by a successor contractor in the performance of all or part of the work contemplated by this contract, it is mutually understood and agreed that the best interests of the government will be served through re-employment by the successor contractor of qualified contractor employees. Therefore, the contractor shall cooperate in good faith with any successor contractor to provide reasonable access to employees and employee records for recruitment efforts. With respect to any such employees who are offered positions by the successor contractor, the incumbent contractor further agrees to release, without penalty, any employee who chooses to accept employment by a successor contractor. This obligation shall not require the contractor to release an employee prior to the completion date of its performance under this contract if such early release would materially affect the contractor’s ability to perform its obligations under the remainder of the contract.

Furthermore, this clause shall not be deemed to preclude the contractor from making bona fide offers of alternate employment to its employees involved in the performance of this contract.

1.6.17.2.2 Documentation: The contractor shall make available to the successor copies of all written and electronic operating instructions, maintenance instructions, documentation, vendor points of contact, hardware or software utilities and all other procedures developed in the performance of this contract. Make available to the successor electronic copies of all historic data, including but not limited to, tests, reports, procedures, schematics, drawings and diagrams developed and documented in the performance of this contract. This documentation shall be transferred to the successor contractor by the start date of the follow-on contract.

1.6.17.2.3 On-going Operations: On-going operations shall be coordinated with management and administrative personnel of the successor to ensure uninterrupted mission requirements are met. The contractor shall provide a monthly activity report detailing work described herein. This report will include detail as described in CDRL A101.

1.6.17.2.4 Staffing: In the event the incumbent contractor is to be replaced by a successor contractor, the incumbent contractor shall retain a minimum level of staffing to assist the CO with contract close out, not to exceed 30 days.

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. CONTRACTOR: A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

2.1.2. CONTRACTING OFFICER (CO): A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the Government.

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR): An employee of the U.S. Government appointed by the CO to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. DEFECTIVE SERVICE: A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5. DELIVERABLE: Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.6. FUNCTIONAL COMMANDER/FUNCTIONAL DIRECTOR (FC/FD): The Government person having the overall responsibility for ensuring that the services are provided by the contractor. Responsible for nominating to the commander qualified QA Personnel. The FC does not direct the contractor, but works through the CO.

2.1.7. KEY PERSONNEL: Contractor personnel that are required to be used in the performance of the contract. Description of the Key Personnel is listed in the PWS.

2.1.8. LAUNCH VEHICLE: Launch vehicles are conveyances used to transport and/or deliver a payload to a desired location. This term includes, but is not limited to, aircraft, all types of space launch vehicles, crewed launch vehicles, missiles, rockets and their stages, probes, aerostats and balloons, drones, unmanned aircraft, projectiles, torpedoes, and air-dropped bodies.

2.1.9. PHYSICAL SECURITY: Actions that prevent the loss or damage of government property.

2.1.10. QUALITY ASSURANCE (QA): The government procedures to verify that services being performed by the contractor are performed according to acceptable standards.

2.1.11. QUALITY ASSURANCE Surveillance Plan (QASP): An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.12. QUALITY CONTROL (QC): All necessary measures taken by the contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.14. PERFORMANCE REQUIREMENT SUMMARY: Identifies the key service outputs of the contract that will be evaluated by the Government to assure contract performance standards are met by the contractor.

2.1.15. SUBCONTRACTOR: One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.16. WORKDAY: The number of hours per day that the contractor provides services IAW the contract.

“Workday” means a normal duty day, Monday through Friday (except Federal holidays) from 7:30 am through 4:30 pm.

2.1.17. WORK WEEK. Monday through Friday, unless specified otherwise.

2.2. ACRONYMS:

45 SW 45th Space Wing AF Air Force AFB Air Force Base AFI Air Force Instruction AFPD Air Force Policy Directive AFM Air Force Manual AFSPCMAN Air Force Space Command Manual AFWay AF Way (Web-Based Computer Purchasing System) CDRL Contract Data Requirements List CO Contracting Officer COMPUSEC Computer Security COMSEC Communications Security CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer’s Representative COTS Commercial-Off-the-Shelf DD250 Department of Defense Form 250 (Receiving Report) DD254 Department of Defense Contract Security Requirement List DIACAP DoD Information Assurance Certification and Accreditation Process DOD Department of Defense DRMO Defense Reutilization and Marketing Office DSN Defense Switching Network EMSEC Emission Security ENTNET Enterprise Network [Base LAN] EWR Eastern and Western Range FAR Federal Acquisition Regulation FC Functional Commander FD Functional Director FOUO For Official Use Only IA Information Assurance IAW In Accordance With IT Information Technology ITCC Information Technology Commodity Council ITE IT Equipment LAN Local Area Network NISPOM National Industrial Security Program Operating Manual NLT Not Later Than OCI Organizational Conflict of Interest OMC Official Mail Center OPSEC Operations Security PA Privacy Act PAFB Patrick Air Force Base PIPO Phase In/Phase Out PM Program Manager POC Point of Contact PRS Performance Requirements Summary

PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Program SEL 45 SW Launch Safety Branch (Flight & Risk Analysis) SHARP Safety Hazard Analysis and Risk Processing SSVB Safety Software Validation Board SWI Space Wing Instruction TE Technical Exhibit WAWF Wide Area Work Flow WBS Work Breakdown Structure

PART 3

GOVERNMENT SERVICES

3. GOVERNMENT FURNISHED SERVICES:

3.1. Services: The Government will provide the following Services.

3.1.1 Network Account and Access: The government will provide For Official Use Only (FOUO) intranet and internet access for accomplishment of work in support of this PWS. The contractor shall comply with AF regulations and 45 SWI 33-108, 45th Space Wing Enterprise Network (ENTNET) Policy, for network accounts and access to the 45 SW ENTNET.

3.1.1.1 45 SW Computer Hardware, Software and other Information Technology Equipment (ITE): The government monitors, approves and disapproves information technology (IT) installations and changes that affect 45 SW network architecture. The contractor shall use the government approved requirements process to request access (new or changes) to the network or facilitate changes to hardware, software, LAN, data, voice, and video configurations. The contractor shall notify the CO by letter not later than 30 days after contract award; the name and appropriate contact information of the primary and alternate point of contact (POC) for all computer hardware, software and other ITE related issues.

3.1.1.2. Software Management: The contractor shall manage software inventory IAW AFI 33-114, Software Management. The contractor shall maintain a listing of all Commercial-Off-The-Shelf (COTS) computer software in use and a central repository of original delivered copies of all COTS computer software, and authorized upgrades for the duration of the contract. Only approved software is authorized for use on systems that process DoD/Air Force information. If the desired software is not on the list, the contractor shall request approval utilizing the most current DoD/AF software approval process, which is currently the Air Force Network Integration Center (AFNIC) software approval process.

3.2 Facility: The government will provide at PAFB: approximately 200 square feet of net office space in Building 423 (100 sq ft per person for up to 2 personnel). Government reserves the right to provide same size accommodations at another location at government’s discretion. Space allocation will be determined IAW AFH 32-1084, Table 12.5. The contractor shall maintain all facilities in a neat and orderly condition and shall be responsible for repairs beyond fair wear and tear for contractor-caused damage. Facilities maintenance, refurbishment, repair, alteration, plan engineering services, minor construction, refurbishment of post-launch damage, and facilities corrosion prevention/control will be provided on government furnished facilities. Furnishings will not be provided other than those already established at the office location.

3.3 Equipment: The contractor shall provide all management, administration, training, supervision, labor, materials and supplies necessary to perform all tasks related to the launch safety functions as described within this work statement and report system status.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General: The contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3, Government Furnished Service, of this

PWS.

4.2 Secret Facility Clearance: The contractor shall possess and maintain a SECRET facility clearance from the Defense Security Service. The contractor’s employees, performing work in support of this contract shall have been granted a SECRET security clearance from the Defense Industrial Security Clearance Office. The contractor shall comply with DD Form 254 (Attachment 1), Department of Defense Contract Security Classification Specification requirements. The contractor shall report personnel's Information Assurance (IA) certification status and compliance with DoD 8570.01-M, Information Assurance Workforce Improvement Program Manual.

4.3. Visitor Security Agreement: The contractor shall sign a Visitor Security Agreement stipulating the security requirements of this contract as provided in DoD 5200.22-R/AFI 31-601, Paragraph 1-108e. All provisions of DoD 5220.22-M, DoD National Industrial Security Program Operating Manual (NISPOM), shall apply to this contract.

4.4. Employee Listing (Applicable to sustainment only): The contractor shall maintain a current listing of employees by name and security clearance level. This list shall be provided to the CO, COR, and/or security police organization at contract start date with changes updated upon occurrence. Contractor format is acceptable.

4.5. Classified Handling: Classified materials shall be handled IAW Industrial Security Manual (ISM).

AF Form 310 will be used for receipt/return of classified working papers, graphics, and photoproducts, etc.

4.6. SF702: Standard Form 702, Security Container Check Sheet, shall be used as required.

4.7. Information Assurance (IA): If the contractor desires to have its own automated information system interfaced to a DoD network, the contractor shall protect all information IAW a contractor-developed IA program to include communications security (COMSEC), computer security (COMPUSEC), IA Assurance Awareness Program, and emissions security (EMSEC). The contractor will follow the processes in Department of Defense Instruction 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), to obtain IA certification and accreditation. Security training requirements shall be considered within scope of the contract, including correct formatting on Staff Summary Sheets and/or Letters of Assurance for the Certification and any necessary Accreditation Process Point Papers that are required to be submitted during the certification process. The contractor must perform a semi-annual self-assessment of its automated information system that is interfaced to a DoD network using AF Form 4160, Information Assurance Assessment and Assistance Program Criteria, self-assessment checklist.

4.8. Materials and Equipment: Should the government direct the contractor to modify the SHARP network in building 423 at Patrick AFB, the government will provide computers, network switches, LAN cables, uninterruptable power supplies, cooling fans and other supplies as required.

4.8.1. The contractor shall furnish for their use the required number of portable hard drives necessary to perform the required maintenance and/or support for the SHARP network. Portable hard drives shall be labeled “Unclassified” and include the contract number, company name and Systems Administrator name/phone number.

PART 5

SPECIFIC TASKS

5. Specific Tasks: The contractor shall provide technical support in two distinguishable areas pertaining to the SHARP system - continuous sustainment of the standalone SHARP network and computers at Patrick AFB and specific tasks involving systems upgrade and development of SHARP flight and risk analysis models (e.g., algorithms and code). SHARP Sustainment entails maintaining SHARP LAN access, Safety Software Validation Board (SSVB) support, SHARP network system administration and authority to operate (ATO) requirements, information assurance controls, and upgrades of existing SHARP models/tools (e.g., new modules or versions) located at Patrick AFB. (CDRL A103 & A104). Specific tasks can involve implementation of system upgrades or model development activities (e.g., software creation or adaptation from software requirements definition through algorithm and code writing, testing, approval, and implementation.)

5.1. SHARP Sustainment includes technical support of both the Flight Analysis LAN and computers as well as the separate Risk Analysis standalone laptops, PCs, and Beowulf clusters.

5.1.1. Launch Safety Flight Support: The contractor shall provide services supporting launch safety flight analysis sustainment as described in this subsection. Contractor resources shall provide adequate support of scheduled and contingency activities. Contractor support for the flight analysis systems and software under SHARP includes:

5.1.1.1. Resolution of operational problems encountered by 45 SW/SELF analysts associated with the use of SHARP tools that reside on the Joint Advanced Range Safety System (JARSS) Mission Planning (MP) tool bench.

5.1.1.2. Maintenance of an automated software problem reporting database for the SHARP tools in JARSS MP. The contractor shall provide technical support that ensures government technical leads complete availability and access to the SHARP problem report database. No more than two incidents of non-access with 24 hour period during performance month

5.1.1.3. Providing cost estimates for resolving software problems reported in the automated database as requested by the government for sustainment of SHARP tools in JARSS MP.

5.1.1.4. Resolution of JARSS MP software problem reports that have been authorized by the government for sustainment of SHARP tools on the JARSS MP tool bench. The contractor shall provide technical support that ensures government technical leads complete availability and access to the SHARP problem report database. No more than two incidents of non-access with 24 hour period during performance month

5.1.2. Launch Safety Risk Support: The contractor shall provide services supporting launch safety risk analysis sustainment as described in this subsection. Contractor resources shall provide adequate support of scheduled and contingency activities. Contractor support for the risk analysis systems and software under SHARP includes:

5.1.2.1. Resolution of operational problems encountered by 45 SW/SELR analysts that are associated with the use of risk models under SHARP.

5.1.2.2. Maintenance of an automated software problem reporting database for the risk software models under SHARP.

5.1.2.3. Providing cost estimates for resolving software problems reported in the automated database as requested by the government for sustainment of the risk software models under SHARP.

5.1.2.4. Resolution of software problem reports that have been authorized for resolution by the government for sustainment of the risk software models under SHARP.

5.1.2.5. Additional requirements may be worked as available funding and mission requirements mandate.

As an example, this may include the contractor providing the capability to perform theoretical and or statistical analysis of various launch vehicle systems and components to determine reliability, resultant failure rates and failure mode scenarios as required.

5.1.3. SHARP Network Sustainment and Administrative Support including:

5.1.3.1. Maintaining availability of the SHARP network and standalone computers as described by the SHARP Security & Administrative Guide (SAAG). SHARP network downtime shall not exceed 4 hours (continuous) in any business day.

5.1.3.2. Performing SHARP system administration duties as described in the SAAG.

5.1.3.3. Updating the SAAG as required.

5.1.3.4. Recovering data from the SHARP host PC as required. Lost data from the SHARP host PC shall be recovered from backup data within 4 hours of the contractor being notified that a data loss has occurred.

5.1.3.5. Maintaining Authority to Operate (ATO) approval and requirements for the SHARP (unclassified) and SHARP-C (classified) systems by performing the following activities: (CDRL A105)

5.1.3.5.1. Preparing ATO renewal packages using the Air Force Enterprise Mission Support Services (eMASS) web-based workflow system. SHARP ATO renewal shall be processed not later than 30 business days prior to expiration.

5.1.3.5.2. Assisting 45 SW/SE execute configuration control activities IAW 45 SWI 91-701, 45th SW Launch Safety Software Management.

5.1.3.5.3. Performing SSVB member duties of the delegated Information Assurance Manager as described in 45 SWI 91-701.

5.1.3.5.4. Coordinating annual Catastrophic Incident Response Plan exercises and drafting associated reports.

5.1.3.5.5. Performing annual Information Assurance controls testing and drafting associated Federal Information Security Management Act (FISMA) reports.

5.1.3.5.6. Maintaining SHARP and SHARP-C records in the Enterprise Information Technology Database Repository (EITDR).

5.2. Special Task Launch Safety Analysis Work Requests: The contractor shall provide Launch Safety Analysis consisting of Flight and Risk Analyses. Qualified and experienced personnel to perform SHARP launch safety analysis consisting of Flight and Risk task support as requested by the CO. Work under this special task support shall begin only after the government issues a fully executed work request defining scope, resources, and schedule of the task. This support is specific and may include the following efforts

(CDRL A104):

5.2.1. Installation of software to new or upgraded computer systems (e.g., purchase of new Beowulf cluster requires installation of Monte Carlo risk evaluation software). This includes testing to ensure proper software installation.

5.2.2. Performing theoretical and or statistical analysis of various launch vehicle systems and components to determine reliability, resultant failure rates and failure mode scenarios as required.

5.2.3. Creation or adaptation of existing software models (flight or risk) to accommodate a new vehicle or scenario (e.g., change hard data input to variable input(s), create selectable variables or ranges, incorporate new module to evaluate new vehicle flight or risk mode, implement a new algorithm/methodology that increases efficiency/accuracy). This includes software requirements definition through algorithm and code writing, testing, approval, and implementation.

5.2.4. Independent Verification and Validation (IV&V) of software (new or adapted) to evaluate efficiency and accuracy of software and discovery any adverse effects from changes or transfer of output to other models.

5.2.5. Evaluation of uncertainty in modeling. Development/refinement of risk drivers that carry large uncertainties affecting output. This may include test plans to understand risk scenarios to minimize uncertainty and incorporation of test/accident data into existing/new models/modules.

5.2.6. Research and coordination with subject matter experts on issues driving risk (e.g., human vulnerability to debris impact, overpressure, aircraft vulnerability, new materials hazards, explosive modeling, radioisotope hazards, propellant chemistry).

5.3. Invoicing: Contractor shall invoice for services in a timely manner. Invoicing for Sustainment shall occur NLT 30 calendar days after completion of monthly performance. Invoicing for Launch Safety Analysis work requests task orders shall occur NLT 60 days after completion and acceptance of task(s).

(CDRL A106).

5.4. Status of work performed will be provided in a monthly activities report, contractor format acceptable.

(CDRL A101)

PART 6

APPLICABLE PUBLICATIONS

6. APPLICABLE PUBLICATIONS (CURRENT EDITIONS): The contractor must abide by all applicable regulations, publications, manuals, and local policies and procedures. The contractor shall support and carry out launch vehicle operations and launch safety requirements of AFSPCMAN 91-710 or EWR 127-1 as outlined in the PWS. If no specific version is specified for a particular facility, operation, or program, the latest revision will be used (as tailored and approved by 45 SW Range Safety for that particular use or program). NOTE: The contractor will be responsible for the most current version of the regulations. If there is a cost impact due to a regulatory change, the contractor will be required to notify the CO immediately of any need for an equitable adjustment. Contractor is responsible and must comply with all applicable federal, state, and local requirements.

Number Title Applicable Paragraphs

Department of Defense Directives

DoD Regulation 5400.7 Air Force Supplement, DoD Freedom of Information Act Program 9/11/2008 All

DoD Directive 5200.28 DoD Trusted Computer System Evaluation Criteria 3/21/1988 All

Department of Defense Manuals

DoD 5220.22-M National Industrial Security Program Operating Manual (NISPOM) 2/28/2006 M: Chapters 1-11, Supp 1 A: Remainder

DoDM 4525.8/AF Supp 1 Official Mail Manual 3/20/2006 All

Air Force Directives

AFPD 33-2 Information Protection 4/19/2007 All

AF ITCC Policy Memo 04-01

Information Technology Commodity Council Policy Memorandum, Mandatory Desktop/Laptop Strategy 9/15/2004

All

Air Force Handbooks

AFH 32-1084 Facility Requirements 9/01/1996 Table 12.5

MIL-HDBK-881 Work Breakdown Structure

Air Force Manuals/Instructions

AFM 33-153 Information Technology (IT) Asset Management 03/19/14 All

AFI 33-332 Air Force Privacy Act Program 1/29/2004 All

AFI 33-360 Air Force Content Management Program 5/18/2006 All

AFI 91-204 Safety Investigations and Reports 9/24/2008 All

Air Force Special Security Instructions

DoDM 5200.01 DoD Information Security Program, Volumes 1 - 4 02/24/12 All

45th Space Wing Instructions and Operating Plans

45 SWI 91-204 Launch Vehicle Toxic Plume/Distance Focusing Overpressure Instruction for On-Base Personnel 08/28/14 All

45 SWI 91-701 45th Space Wing Launch Safety Software Management 11/05/14 All

45 SWI 32-9001 Building/Facility Care - Real Property Management 06/20/1994 All

AFMAN 33-153 45SWSUP 1 Information Technology (IT) Asset Management (ITAM) 08/05/15 All

45 SWI 33-108 45th Space Wing Enterprise Network Policy 6/01/2005 All

PART 7

TECHNICAL EXHIBIT LISTING

7. Technical Exhibit List:

7.1. Technical Exhibit 1 – Performance Requirements Summary

7.2. Technical Exhibit 2 – DD Form 1423, Contract Data Requirements List (CDRL) Deliverable Schedule

7.3. Technical Exhibit 3 – Estimated Workload Data (Projected)

TECHNICAL EXHIBIT 1

Performance Requirements Summary (PRS) The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

PRS #

PWS Objective

PWS

Reference

Performance Threshold

PRS # 1

The contractor shall provide technical support that ensures government technical leads complete availability and access to the SHARP problem report database.

PWS paragraphs

5.1 thru 5.1.1.4

Access to Report Data Base: 100% within 24 hour period Maximum Allowable Defect: 2 one hour incidents No more than two incidents of non-access within 24 hour period during performance month

PRS #2

The contractor shall ensure the SHARP network downtime shall not exceed 4 hours in any business day

PWS para 5.1.3.1 System Availability 97.5% of time Maximum Allowable Defect: 2.5% Downtime of the SHARP network shall not to exceed a maximum of 4 hours (Continuous) in any normal business day.

PRS # 3

The contractor shall ensure that lost data from the SHARP host PC shall be recovered from backup data within 4 hours (or sooner) of the contractor being notified that a data loss has occurred.

PWS para 5.1.3.4 Data Storage Recovery 100% Maximum Allowable Defect: 0 Data lost from the SHARP host PC must be recovered from backup data within 4 hours of the contractor being notified that a data loss has occurred

PRS # 4

The contractor shall complete the SHARP ATO renewal packages and then submit in eMASS 30 business day’s prior to when the current ATO expires.

PWS para.5.1.3.5 ATO Renewal: 100% Maximum Allowable Defect: 0 SHARP ATO renewal packages are completed and submitted in eMASS 30 business days prior to when the current ATO expires.

PRS # 5

Timely Invoicing:

Sustainment (CLIN X001) shall occur not later than 30 calendar days after last day of monthly performance.

Launch Safety Analysis task orders (CLIN X002) shall occur not later than 60 calendar days after completion of task.

PWS para 5.3 Timely Invoicing: 100% Maximum Allowable Defect: 0 Sustainment: not later than 30 calendar days Launch Safety Analysis: not later than 60 calendar days.

TECHNICAL EXHIBIT 2

DD FORM 1423, CONTRACT DATA REQUIREMENTS LIST (CDRL)

Number DID Subtitle

A100 N/A CONTRACT WORK BREAKDOWN STRUCTURE

A101 N/A ACTIVITY REPORT

A102 N/A RESERVED

A103 N/A REPORTS FOR SHARP SYSTEMS STATUS

A104 N/A TECHNICAL DELIVERABLES

A105 N/A SHARP INFORMATION ASSURANCE (IA) REVIEW

A106 N/A INVOICES

A107 N/A TRIP REPORTS

A108 N/A QUALITY ASSURANCE PROGRAM PLAN

CONTRACT DATA REQUIREMENTS LIST

Form Approved CMB No. 0704-0188

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 222202-2302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract. PR No. listed in Block E.

A. Contract Line Item No.

B. Exhibit A

C. Category

D. System/Item

SAFETY SUPPORT SERVICES

E. Contract/PR NO.

F. Contractor

1. Data Item No.

A100

2. Title of Data Item:

RANGE SAFETY STANDARDS & OPERATING PROCEDURES

3. Subtitle:

CONTRACT WORK

BREAKDOWN STRUCTURE

4. Authority (Data Acquisition Document No.)

N/A

5. Contract Reference

PWS 1.1

6. Requiring Office

45 SW/SE

7. DD 250 Req

LT

9. Dist Statement Required

10. Frequency

ONCE

12. Date of First Submission

SEE BLOCK 16

14. Distribution

8. APP Code

11. As of Date

13. Date of Subsequent Submission

a. Addressee b. Copies

A AS REQUIRED Final

Dra ft

Reg Repro

16. REMARKS

BLOCK 12 and 13: Draft submission will be due with contractor’s proposal.

Final submission will be due NLT 60 days after contract start.

CONTENT: The contractor shall provide a work breakdown structure that adequately addresses the work tasks associated with the PWS. This breakdown structure should adequately address each paragraph, down to the subparagraph, of the PWS and include any Subcontractor involvement.

Reference MIL-HDBK-881, Work Breakdown Structure.

Contractor format is acceptable.

NOTE: If electronic media is utilized and government/range user access is readily available, hard-copy submittals may not be required.

45 SW/SE 1 1

45 CONS/LGCZ 1

15. TOTAL 1 2

G. PREPARED BY

H. DATE

I. APPROVED BY

J. DATE

DD Form 1423-1, JUN 90 Previous editions are obsolete Page of Pages

CONTRACT DATA REQUIREMENTS LIST Form Approved CMB No. 0704-0188

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 222202-2302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract. PR No. listed in Block E.

A101

2. Title of Data Item:

RANGE SAFETY STANDARDS & OPERATING PROCEDURES

3. Subtitle:

ACTIVITY REPORT

4. Authority (Data Acquisition Document No.)

N/A

5. Contract Reference

PWS 1.6.17.2.3

6. Requiring Office

45 SW/SE

7. DD 250 Req

MONTHLY

12. Date of First Submission

AN END OF QUARTER SEE BLOCK 16 Final

Draft Reg Repro

BLOCK 12: First due NLT 10 January for Oct-Dec

BLOCK 13: Within 10 days after each quarter throughout the contract.

CONTENT: The…