PWS_Technical_ReachBack_Contract_20_Dec_16.docx

PERFORMANCE-BASED WORK

STATEMENT FOR

Battle Control System – Fixed (BCS-F) Weapon System Software Development and Training

309th SOFTWARE MAINTENANCE GROUP HILL AFB, UTAH

(520 SMXS)

December 20th, 2016

TABLE OF CONTENTS

1. Description of services

This Performance-Based Work Statement (PWS) outlines the tasks and duties required of the contractor in support of 309th Software Maintenance Group’s (SMXG) Battle Control System-Fixed (BCS-F) Weapon System program within 309 SMXS. The BCS-F weapon system will provide NORAD and PACOM Commanders with surveillance and control of NORAD’s Area of Operations (AOO) warning and assessment of aerospace attacks and response against air attack. The mission requires a 24 hours a day, 365 days a year operation. The BCS-F weapon system processes, integrates, displays, and distributes data from sensors, data links, and other Command and Control (C2) agencies to maintain situational awareness and support air interdiction operations. The role of the BCS-F will be extended to place greater emphasis on the monitoring of domestic air traffic as a result of the terrorist attacks of 11 September 2001.

2. Scope

The contractor shall support BCS-F Weapon System Software Sustainment team in: Systems Engineering, Software Engineering, Test Engineering, Hardware Engineering, System Administration, and Information Assurance solutions to enhance and sustain the BCS-F weapon systems. The contractor shall support sustainment and development solutions, and root cause analysis.

3. Basic Service requirements

3.1. Sustainment and Maintenance of contractor-located BCS-F Systems

3.1.1. Software Development Environment (SDE). Software Development Environment (SDE) at the contractor facility consists of equipment and software used in the development and test of software code contained in the BCS-F system. The contractor shall:

3.1.1.1. Complete system administration and maintenance tasks required to maintain operational status of software and hardware used to support the government software development activities including code analysis and review.

3.1.1.2. Maintain virus and malware protections on all contractor-located BCS-F systems.

3.1.1.3. Provide secure source repositories for all baseline sources to facilitate technical design and code evaluation, peer reviews, and technical mentoring for BCS-F technologies.

3.1.1.4. Install and configure software components required for government development purposes.

3.1.1.5. Shall report all hardware defect or failure issues to the BCS-F Weapon Systems Help Desk program for resolution.

3.1.2. Integrated Test Facility (ITF). Integrated Test Facility consists of equipment and software used in the testing of BCS-F weapons system software. The contractor shall perform systems administration and system maintenance tasks required to maintain an operational status for all software and hardware contractor-located BCS-F systems. The contractor shall:

3.1.2.1. Complete system administration and maintenance tasks required to maintain operational status of software and hardware used to support government software testing, integration, and debugging analysis.

3.1.2.2. Maintain virus and malware protection on all contractor-located BCS-F systems.

3.1.2.3. Install and configure software components required for government development purposes.

3.1.2.4. Shall report all hardware defects or failure issues to the BCS-F Weapon Systems Help Desk program for resolution.

3.2. BCS-F Operations SME and System Administrator. The contractor shall provide BCS-F Weapons Systems Subject Matter Expert (SME) level support for system administration and technical support of the Organic Integrated Test Facility (OITF) at Hill AFB and development activities. The contractor provided shall:

3.2.1. Be local to Hill AFB to provide on-site support.

3.2.2. Possess System Administration and Security Certifications at Security Plus or higher level.

3.2.3. Have experience in reading and interpreting operational data logs recorded by the BCS-F Weapons System to assist in root cause analysis of system failure modes.

3.2.4. Have operational experience in all facets of the BCS-F Weapons System including, but not limited to:

3.2.4.1. Performing incremental system and logs backup weekly and full backup monthly, or when system has changed.

3.2.4.2. Maintaining BCS-F Weapon System classified and unclassified networks and update as needed.

3.2.4.3. Configure routers, servers, workstations (Linux, Microsoft, Solaris, Unix, & VMS) and switches.

3.2.4.4. Perform system recovery of classified and unclassified networks upon notification to restore system to normal.

3.2.4.5. Perform modifications or repairs to the network.

3.2.4.6. Troubleshoot OITF systems and components.

3.2.4.7. Provide BCS-F Weapons System operational guidance to government engineers.

3.2.4.8. Provide assistance to developers as requested by the government for operations and root cause analysis of defects at locations to include all Sectors and lab sites including, but not limited to:

· CADS -Canadian Air Defense Sector, North Bay, Ontario Canada]

· EADS - Eastern Air Defense Sector, Griffiths Technology Park, Rome, NY,

· WADS - Western Air Defense Sector, Joint Base Lewis-McChord, WA

· AKROAC - AKA Alaska Air Defense Sector (AADS), Joint Base Elmendorf-Richardson, Anchorage, AK

· HIRAOC - Hawaii Region Air Operations Center, Wheeler Army Airfield, Oahu, HI

· OITF - Organic Integrated Test Facility, Hill AFB, UT

· SSF - Software Support Center, Tyndall AFB, FL.

3.3. BCS-F Weapons System Testing Support. The contractor shall provide BCS-F Weapons System SME level support in the area of systems and software testing. The contractor shall:

3.3.1. Provide informed guidance for BCS-F Weapon System product testing in order to assist the government in validation and verification of product releases.

3.3.2. Review and provide technical assessment of Test Procedure Documents.

3.3.3. Provide test document examples to assist in learning opportunities for the government sustainer.

3.3.4. Provide technical training (see Section 3.7 Training) in the testing of software components subcomponents of the BCS-F Weapon System to fulfill technical requirements.

3.3.5. Provide assistance to government engineers in developing and executing test plans for operational qualifications and root cause analysis of defects at locations to include all Sectors and lab sites (CADS, EADS, WADS, AFROAC, HIROAC, OITF, and SSF (refer to section 3.2.4.8) as requested by the government.

3.4. Systems Engineering Support. The contractor shall provide SME level responses to government requests for guidance and technical reach back on BCS-F Weapons Systems components, interfaces, data architecture, protocols, SSS level requirements documents and others. The contractor shall:

3.4.1. Contribute systems architecture and operational knowledge in peer reviews, code reviews, and other technical reviews as requested by the Government Representative (GR) for the purposes of verifying and validating technical solutions.

3.4.2. Provide SME level consulting in response to technical questions posed by the government in order to clarify or obtain technical understanding of the BCS-F Weapons Systems.

3.4.3. Provide guidance in engineering requirements breakdown.

3.4.4. Provide technical training (see Section 3.6 Training) in the architecture of components and subcomponents of the BCS-F Weapon System.

3.4.5. Provide technical expertise using a knowledge-based approach to assist the government in accelerating the determination of root cause for software defects, anomalies and deficiencies.

3.5. Software Development Code Support. The contractor shall provide technical assistance and mentoring to the government to facilitate the transition of the BCS-F source baselines to government sustainment and to assist in the development of government expertise with respect to the BCS-F Weapon System code. In the accomplishment of this task the contractor shall:

3.5.1. Participate in code and other engineering reviews of solutions developed by the government and provide technical evaluations for acceptability with regards to both design and code implementation within the BCS-F Weapon System.

3.5.2. Participate in direct engineer-to-engineer technology discussions with government engineers to assist in the understanding and experience with the BCS-F source base.

3.5.3. Assist the government in defining approaches to testing coded solutions (unit level test).

3.5.4. Assist the government in determining root cause analysis of system defect and deficiency reporting including expert level review of system log files.

3.5.5. Develop a mechanism to ingest 520th code baseline and executables into the contractor SDE and ITF to enable debugging assistance as needed by the government to facilitate all Section 3.6 and 3.2 requirements.

3.5.6. Provide suggestions of ‘best practice’ approaches for software development.

3.5.7. Provide training (See Section 3.6 Training) to transfer the technology and architecture knowledge base for the BCS-F Weapons System.

3.5.8. Provide training per section 3.6 in the areas of software development and problem diagnostics to assist in root cause analysis of failure modes and understanding of sub system interfaces.

3.6. BCS-F Weapons System Technical Product Training. The contractor shall provide training in the technologies and design approaches incorporated into the BCS-F Weapons Systems software to the government in order to facilitate the full transition of software sustainment to the organic government organization within the term of this contract. The contractor shall:

3.6.1. Provide “On the Job Training” (OJT) for software and hardware components of the BCS-F Weapon Systems.

3.6.2. Present semi-formalized training either at the contractor location or the government location (Hill AFB, UT), as requested by the GR to facilitate efficient execution and cost containment (See Section 3.16 – Travel).

3.6.3. Not exceed 84 calendar days, including travel days, each contract year.

3.6.4. Expend no more than 40 hours per training instance in preparation time.

3.6.5. Provide up to 40 hours of follow-on support subsequent to each training instance wherein the trainer will be available on short notice to respond to questions from the government engineering staff.

3.6.6. Provide technical documentation to facilitate training and technical exchanges and provide necessary training materials in engineering notebook format and/or Power Point slide decks two (2) weeks in advance of training for preparation and content review by the government. (CDRL A001)

3.6.7. Training topics shall include (but are not limited to) the following areas:

3.6.7.1. BSC-F systems and subsystems architecture details and coding or design considerations to include: Sentry, ProCon, OpenView, RTAP-RWS, TIGER Simulator, Firewall, Switch Components, and Communications Protocols (Link 11, Link 16, etc.).

3.6.7.2. Description of the sensors within the BCS-F Weapon System communications, the message formats used in communications interfaces, and a functional breakdown of SENTRY component message or data interchanges.

3.6.7.3. ProCon customized ASTERIX interface details.

3.6.7.4. ProCon message handing (Mode 4 Interrogation Requests) to compatible sensors.

3.6.7.5. Message architecture and transfer mechanisms between Radiant Mercury Guard (RMG) including logs and their use as a diagnostic tool.

3.6.7.6. Concept of Operations (ConOps) details and information for system use including an overview of system modes and how the various types of operators interact with the system.

3.6.7.7. Datalink technology overview and use cases within BCS-F Weapon System.

3.6.7.8. Mapping of known problems to code and functional areas within the BCS-F Weapons Systems.

3.6.7.9. Tracing the interfaces and data flow within functional areas of the software baseline.

3.6.7.10. Software problem diagnostics to assist in root cause analysis of failure modes.

3.7. Return or destruction of Licensed products and Materials. No GFP is expected to be included in this contract; however, may be included in the future. This allows for the contractor to return any relevant materials that may be provided.

3.7.1. Prior to the contract expiration, the contractor shall return all equipment and operational materials provided, or shall destroyed equipment and materials at the direction of the providing government organization.

3.7.2. The contractor shall remove all software products provided for the performance of this contract from contractor and/or GFE and return all licensing, installation, and documentation materials to the providing organization.

3.7.3. The contractor shall provide evidence of either destruction or removal and return of all government provided equipment, licensed materials, and software materials no later than seven (7) working days of contract expiration. (CDRL A002)

3.8. Reporting.

3.8.1. Contractor Monthly Status Reporting. The contractor shall provide to the GR a detailed Monthly Status Report for the reporting period ending on their financial month-end. This is typically between the 20th and 28th of the month. (CDRL A003) The contractor shall:

3.8.1.1. Provide report within the first seven (7) business days of the subsequent month.

3.8.1.2. Include in all reports the following:

· Planning and engineering consulting or mentoring activities including training and other engineering activities.

· GFE sustainment activities – both SDF and ITF, including systems administration and maintenance actions performed.

· Status of submitted help desk items pertaining to labs

· Lab configuration changes performed including BCS-F software installed on each system

· Staffing

· Deliverables

· Financial Metrics

· Spend down plan and monthly budget report by man month including budget, actual performance, contract performance accumulative data for each and %deviation from plan (both monthly and accumulative).

· All travel accomplished on behalf of the Government to include travel dates, destinations, Point of Contacts, and working dates for all miscellaneous and training travel.

· Invoices amounts for past 30 days including invoice number, CLIN, and function.

3.8.2. Program Management Review (PMR). The contractor shall prepare and present a program management review to the GR and delegates (Program Directors (PDs) and Contracting Officer Representative (COR)), quarterly. This review is for the purpose of improving project operations and increasing project effectiveness. (CDRL A004) The contractor shall supply such information as:

· Risk and Issues relevant to contract execution

· Summary of accomplishments

· Lessons learned

· Guidance to program improvement

· Financial review

· Contract and program coordination

3.8.3. Project Activity Status Report. In order to fulfill the requirements of CMMI level 3 and higher certifications, 309 SMXS requires metric data to be collected and reported on all software sustainment activities. This does not constitute a need for full Earned Value Metric implementations but does require specified data be collected and reported to the government. The contractor shall provide, as requested by the GR, a bi-weekly status report in government format, to address task status. (CDRL A005)

3.8.3.1. The government operates within a scheduled, iterative development environment which utilized 2 week task cycles. Progress data for all tasks is needed for planning and tracking of work, Status reports shall include the following performance data:

· the contractor’s performance in comparison to the planned delivery schedule (% complete)

· estimate of effort (hours to complete)

· estimate of schedule (anticipated completion data)

· hours expended in execution of tasks

· Status of issues/concerns and associated recommendations to include any risks that would cause a change in schedule.

· Associated recommendations to mitigate the issue.

3.8.3.2. The contractor shall provide an explanation and plan for correction to accompany any item that is or will likely be more than 15% behind schedule within each two week period.

SERVICES SUMMARY

Training materials and notebooks

3.6.6 Training notebooks and presentation material to be submitted to the GR no later than two (2) weeks prior to the training event(s). (CDRL A001)

Evidence of Disposition of Government Property Report

3.7.3 Report to be submitted to the GR and COR no later than seven (7) working days prior to contract expiration. (CDRL A002)

Monthly Status Report

3.8.1 Report to be submitted to GR and COR by the seventh (7th) business day of the subsequent month containing all items specified. (CDRL A003)

Program Management Review Read Ahead

3.8.2 Review to be submitted to GR and COR, quarterly. (CDRL A004)

Weekly/Bi-Weekly Status Report

3.8.3 Report to be submitted to GR and COR as requested by GR. (CDRL A005)

4. GOVERNMENT FURNISHED PROPERTY (GFP)

The contractor may be provided GFP to government-owned equipment to include: engineering work stations, test stations, Organic ITF, and 520 SMXS BCS-F weapon system Configuration Management (CM) library.

5. GENERAL INFORMATION

5.1. Security Requirements

5.1.1. The contractor shall be required to obtain security clearances for all of their employees. In addition, the contractor shall be required to obtain a security clearance of SECRET. A DD Form 254 will be required for all personnel.

5.1.2. The contractor shall be required to maintain DD2358 to comply with export policies.

5.1.3. The GR or 309 SMXG security manager will assist contractor in processing the necessary DoD forms to obtain base or area badges for access to Government facilities.

5.1.4. The contractor shall comply with all clearance and access requirements throughout the period of performance.

5.1.5. Contractors that provide on-site support for the Hill AFB, UT facilities will be required to comply with all requirements for classified operations similar to requirements at the NORAD Air Defense Sectors.

5.2. OPSEC Requirements

5.2.1. The contractor shall familiarize all new employees and conduct refresher sessions in the areas of Operations Security (DOD Contract Security Classification Specification) addendum. Operations Security (AFI 10-701 Operations Security as supplemented, and AFI 31-1404, Information Security Program, Standards for Storage and Handling Classified Material as supplemented).

5.3. Hill Network Access

5.3.1. Access to the Hill AFB computer network for onsite (Hill AFB) support may be required to accomplish the requirements of this PWS. The following shall be completed prior to receiving that access.

5.3.1.1. For those contractor employees who require government computer access only, a National Agency Check with written Inquiries (NACI) must be submitted. For those contractor employees who require a higher level of investigation for a security clearance and government computer access, a National Agency Check with Local Agency Checks and Credit Check (NACLC), Secret or a Single Scope Background Investigation (SSBI), Top Secret, must be submitted. (AFI 31-501, Personnel Security Management Program, AFSSI 8522, Access to Information Systems).

5.3.1.2. Contractors will complete all required training via TSS. This training is currently available at: https://ooafmctss.hill.af.mil/TSSPortal/HDHome.aspx?sGuid=D9148323-B368- 499C-933F-277127F4BA93

5.3.1.3. If a government provided e-mail account is required the contractor will take Information Assurance Awareness Training prior to receiving access to that account, and annually thereafter.

5.3.1.4. Contractors are required to report in a timely manner (3 days AFI 33- 202_AFMCS1) to the appropriate security manager & Functional System Administrator, personnel who no longer need network or AIS access.

5.3.1.5. The contract administrator shall complete a "Request for Identification Credential (AFMC Form 496)" for each employee of the contractor requiring access to Hill AFB. The requests shall be submitted to Pass and Registration (South or West Gate Visitors Center).

5.4. Badge/Common Access Card (CAC) Information/Unescorted Entry Authorization

5.4.1. The group security manager shall complete an “Unescorted Entry Authorization Certificate” (AF Form 2586) for each employee requiring entry into controlled areas. The request shall be submitted to Pass and Registration.

5.4.2. If needed, the contractor employee shall also obtain a Building ID and access card from the appropriate Building Security Manager.

5.4.3. When the period of performance is complete and/or contractor leaves work on this project they shall have 5 working days to terminate all their network user account and to return all access cards and base identification badges.

5.5. Quality Control

5.5.1. The contractor shall establish Quality Control Plan to ensure the requirements of this contract are provided as specified. The contractor's quality management program shall comply with the minimum quality management systems elements specified in the American National Standards Institute (ANSI), American Standards Organization (ASO), and International Standard Organization (ISO) family of standards. (CDRL A006)

5.6. Quality Assurance

5.6.1. The Contracting Officer Representative (COR) is the authorized government representative(s) who will perform assessments of the contractor’s performance. Subsequent to contract award, the identity of the COR(s), with a letter defining duties and authority will be promptly furnished to the contractor.

5.6.2. The COR(s) or alternate(s) will inform the task manager when discrepancies occur and will request corrective action. The COR(s) or alternate(s) will make a notation of the discrepancy on the assessment checklist with the date and time the discrepancy was noted and will request the task manager (or authorized representative) to initial the entry on the checklist.

5.6.3. Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the Contract Officer (CO), not to the COR(s).

5.6.4. The services to be performed by the contractor during the period of this contract are at all times and places subject to review by the CO or authorized representative(s).

5.6.5. The Government will periodically evaluate the contractor’s performance by appointing a representative(s) to monitor performance to ensure services are received. The Government representative will evaluate the contractor’s performance through inspections and receipt of complaints from base personnel.

5.6.6. The government may inspect each task as completed or increase the number of quality control inspections if deemed appropriate because of repeated failures discovered during quality control inspections or because of repeated customer complaints.

5.7. Government Observation

5.7.1. Government, other than CO and COR(s), may from time to time, with CO coordination, observe contractor operations. However, these may not interfere with contractor performance or make any changes to the contract.

5.8. Data Rights

5.8.1. The government, BCS-F Program Office, asserts ownership all use rights to the BCS-F Weapons System code baseline.

5.8.2. The Government will have all the rights and access necessary to BCS-F data required to maintain the BCS-F system as currently established with the BCS-F Program Office (the acquiring and owning government agency). This contract does not establish or modify the BCS-F Program Office’s rights or claims to BCS-F data as presently understood or lawfully established. The Government will not release restricted source code outside of the BCS-F software sustainment effort. Refer to The Contractor restricted data rights clarification letter. However, it should be understood that the Government reserves the right to challenge any restrictions to technical data relating to the BCS-F Program. The Government shall have unlimited rights to all software developed (new) or government purpose rights for software modified (delta) during the performance of this contract.

5.8.3. The Government asserts the right to use such items for any other purpose as stated in the Defense Federal Acquisition Regulation Supplement (DFARS) definitions of “government purpose rights” or “unlimited rights”.

5.8.4. In addition, all materials, if supplied to the contractor are the sole property of the Government and may not be used for any other purpose except its intended use.

5.9. Hours of Operation

5.9.1. The contractor shall perform the services required under this contract during the following hours when on site at Hill Air Force Base (HAFB): Typical Workdays will be 8 to 9 hours long a within the security schedule of the HAFB facility (Typically 06:00 – 05:30 hrs. M-F). In the contractor is available to work outside of the normal facility hours, coordination and approval of the government is required. Contractors are not authorized compensation for attendance at base functions unless directly related to project assignments as authorized by the Project Director.

5.9.2. Under no circumstances is a contractor allowed on site without the presence of a responsible government employee.

5.10. Observance of Legal Holidays and Excused Absence

5.10.1. Government personnel observe the following holidays and contractor access will be limited or unavailable:

· New Year's Day

· Martin Luther King's Birthday

· President's Day

· Memorial Day

· Independence Day

· Labor Day

· Columbus Day

· Veteran's Day

· Thanksgiving Day

· Christmas Day

5.10.2. In addition to these days designated as holidays, the Government observes the following days:

· Any day designated by federal statute

· Any day designated by executive order

· Any day designated by a President of the United States proclamation

5.11. Records

5.11.1. The contractor shall be responsible for creating, maintaining, and disposing of only those government required records that are specifically cited in this PWS. If requested by the government, the contractor shall provide the original record or a reproducible copy of any such record within five working days of receipt of the request.

5.12. Installation-Specific Safety and Health Standards

5.12.1. Voluntary Protection Program (VPP)

5.12.1.1. Hill AFB, along with the entire Air Force, has adopted the VPP as recognized by Occupation Safety Health Association (OSHA). Consequently, VPP impacts all “applicable contractors” operating on Air Force Installations. It is the contractor’s responsibility to ensure its onsite employees and managers have a comprehensive understanding of VPP as well as full compliance with OSHA requirements. Onsite contractor personnel will participate in the safety activities provided for The Government employees. Detailed information on VPP is available on the OSHA website (http://www.osha.gov/dcsp/vpp/index.html). Contractors, whether regularly involved in routine site operations or engaged in temporary projects such as construction or repair, must follow the safety and health rules of the installation or VPP site.

5.12.1.2. VPP requirements apply to contractors whose employees work more than 1,000 hours per quarter. The contractor shall flow down these requirements to all subcontractors who qualify as applicable contractors under this contract.

5.12.1.3. Contractors are required to provide from their OSHA 300 information the Total Case Incident Rate/Days Away Restricted or Transferred (TCIR/DART) rates. Submit to the CO as part of the installation’s annual OSHA VPP self-evaluation report. (CDRL A007)

5.12.2. Safety Program

5.12.2.1. The contractor shall maintain its safety program at the contractor location that ensures protection of Government personnel and property. Additionally, the contractor shall follow the rules and guidelines of the customer location for contractor personnel working on-site. (See Appendix C)

5.12.2.2. In the event of an accident/mishap, the contractor shall take reasonable and prudent action to establish control of the accident/mishap scene, prevent further damage to persons or property, and preserve evidence. A written or email copy of the mishap/incident notification shall be sent within three calendar days to the Government Representative, who will forward it to 309 SMXG safety. (CDRL A008)

5.13. Scope Change

5.13.1. Any matter concerning a change to the scope, prices, terms or conditions of this contract will be referred to the CO and not to the COR.

5.14. Communication

5.14.1. The contractor shall inform government management of problems and risks that could impact the mission or organization during weekly status meetings. Cooperates and coordinates with others within the assigned organization, and functions well as a member of a project or government product team. (Services Summary)

5.15. Travel

5.15.1. In the event travel is required, the contractor shall obtain approval from the GR fourteen (14) calendar days in advance of traveling unless otherwise directed. Any travel required shall be performed IAW the Federal Travel Regulations and FAR 31.205-46, Travel Costs. The contractor shall be responsible for making all necessary arrangements for their personnel, including air travel, car rental, lodging and subsistence.

5.15.2. As part of the Monthly Status Report (Section 3.6.1), upon completion of any travel, the contractor representative may be required to submit a trip report. Airfare for travel and per- diem shall be billed IAW Federal Travel Regulations (FTR). (CDRL A003)

5.15.3. The contract shall travel no more than 84 days based on training requirements.

5.15.4. The contractor shall travel for site evaluation and problem duplication of system defects.

5.16. Manpower Reporting Requirement

5.16.1. The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the BCS-F via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

5.16.2. Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the CMRA help desk.

5.16.3. Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

APPENDIX A

ACRONYMS AND BREVIATIONS

SDF

APPENDIX B

Summary of Deliverables

Appendix C

DI-SAFT-81563

APPENDIX C

SAFETY, FIRE PROTECTION AND HEALTH

SPECIFICATION

INDUSTRIAL SAFETY REQUIREMENTS

OGDEN AIR LOGISTICS COMPLEX

UNITED STATES AIR FORCE

HILL AIR FORCE BASE, UTAH 84056

Battle Control System – Fixed (BCS-F) Software Development and Training

14 Nov 2016 Prepared by:

Tim Helms

OO-ALC/SE

801-586-6038

Control Number: TH161109

SECTION I - GENERAL REQUIRMENTS

A. Safety Program Requirements.

The contractor will implement a safety program that ensures protection of Government personnel and property. The program will consist of, as a minimum:

1. Mishap reporting, as defined in paragraph B1 below.

2. Routine and recurring surveillance to ensure the safety requirements of this contract are enforced.

3. Identification of segregated work site locations for operations that cannot be co-mingled with general industrial operations and the process for ACO approval of operations and changes at these specific sites.

4. All contractor personnel shall be trained and qualified to perform their duties safely.

5. The contractor shall include a clause in all subcontracts requiring the subcontractors to comply with the safety provisions of this contract, as applicable.

6. Per AFPAM 91-210, para 6.4, due to non-hazardous nature of work, a Safety Plan and corresponding site specific checklist is not required.

B. Mishap Notification

1. The contractor shall notify OO-ALC/SE (801-586-6038) or the Hill AFB Command Post (801-777-3007) after normal duty hours, and the designated Government Representative (GR), i.e., the ACO, PCO, or DCMA COR (Contracting Officer's Representative) within one (1) hour of all mishaps or incidents at or exceeding $2,000 (material + labor) in damage to DOD property entrusted by this contract, even if the government is wholly or partially reimbursed. This notification requirement shall also include physiological mishaps/incidents. A written or email copy of the mishap/incident notification shall be sent within three calendar days to the GR, who will forward it to OO-ALC/SE. For information not available at the time of initial notification, the contractor shall provide the remaining information no later than 20 calendar days after the mishap, unless extended by the ACO.

Mishap notifications shall contain, as a minimum, the following information:

(a) Contract, Contract Number, Name and Title of Person(s) Reporting

(b) Date, Time and exact location of accident/incident

(c) Brief Narrative of accident/incident (Events leading to accident/incident)

(d) Cause of accident/incident, if known

(e) Estimated cost of accident/incident (material and labor to repair/replace)

(f) Nomenclature of equipment and personnel involved in accident/incident

(g) Corrective actions (taken or proposed)

(h) Other pertinent information

2. The contractor shall cooperate with any and all government mishap investigations. Additionally if requested by government personnel or designated government representative (GR), i.e., the ACO, PCO, or DCMA COR (Contract Officers Representative), the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by safety investigators.

3. The contractor shall provide copies of contractor data related to mishaps, such as contractor analyses, test reports, summaries of investigations, etc. as necessary to support the government investigation.

4. The contractor shall support and comply with the safety investigation and reporting requirements of AFI 91-204, Chapters 1 – 5.

C. General Safety Requirements:

Contractor personnel must receive Explosive Safety Awareness Training if their duties require entry into the Explosive Clear Zone. This training will be provided by the OO-ALC Safety Office. Contact Eric Covington at 586-0168.

A Risk Assessment will be required prior to any work being accomplished, if munitions will remain in the facility.

Compliance with OSHA and other applicable laws and regulations for the protection of contractor employees is exclusively the obligation of the contractor. Note: The government shall assume no liability or responsibility for the contractor's compliance or non-compliance with such requirements. The contractor shall furnish to each of his/her employees a place of employment, which is free from recognized hazards. The contractor shall brief his/her employees on the safety requirements of this contract and on hazards associated with prescribed tasks. The contractor is responsible for compliance with OSHA Public Law and the resultant standards identified within. In addition, the contractor is required to flow down the safety requirements/specification to all subcontractors. This applies to Federal Acquisition Regulation (FAR) 12 commercial acquisitions as well. This contract shall in no way require persons to work in surroundings or under working conditions which are unsafe or dangerous to their health. The contractor must coordinate and perform work so as not to impact the safety of government employees or cause damage to government property. This requires providing personnel with protective equipment and associated safety equipment as may be necessary. The contractor must also protect personnel from hazards generated by the work. If the contractor employs BILINGUAL speaking employees, they must post bilingual signs and have written procedures for specific tasks in applicable languages.

SECTION II – SPECIFIC REQUIREMENTS

PEDESTRIAN CROSSWALKS: All contractor personnel are required to use the closest crosswalk, or traffic controlled intersection when crossing the road. Pedestrians must look both ways to ensure the coast is clear before stepping out into the crosswalk. Pedestrians DO NOT have the right of way unless they are already in the crosswalk. Contractor vehicle operators have the same responsibilities as pedestrians, to share the road and mutually observe and yield to pedestrians.

MOTOR VEHICLES: Contractor shall comply with the standards in: DoD Directive 5525.4, Enforcement of State Traffic Laws on DoD Installations", Nov 2, 1981, Para 3-4; DODI 6055.4, DoD Traffic Safety Program, 20 Jul 99; AFI 91-207, USAF Traffic Safety Program, 22 May 07; and AFI 91-207 AFMC SUP1, The US Air Force Traffic Safety Program, 1 Oct 07. Each applies to all persons at any time on an Air Force Installation and includes all leased, owned, or privatized property including housing areas. In addition: AFI 13-213, Airfield Management, 29 Jan 08, Paragraphs 1.3.6 and 4.4.2.1 applies to all contractors, sub-contractors, vendors, commercial delivery companies, and all other private business vehicles who operate anywhere on Hill Air Force Base, including the airfield (to include the industrial areas and any buildings or hangars located upon the airfield) in support of their mission.

HOUSEKEEPING: Housekeeping shall be conducted according to the requirements in OSHA Standard 29 CFR 1910.141. CLEAN AS YOU GO will be enforced.

The authorized Government Representative (OO-ALC Safety Office) shall approve the contractor’s procedures within the Health and Safety Plan as meeting the intent of the below referenced standards, with the exception of Mishap Notification / Reporting Procedures, which are outlined in Section I, paragraph B of this Appendix C.

Element/Requirement Referenced Benchmark

Contract Safety AFPAM 91-210 Para. 6

NFPA 409/410

AFI 91-203 Chapters 6, 22

Handling, Storage and use of Flammable/ NFPA 30, 33

Hazardous Material Management AFI 32-7086 HAFBSUP 1

Storage and Materials Handling DoDI 4140.62 DoDI 4145.19-R-1 image1.jpeg