20160420_GBS_Engineering_Services_PWS_3213.docx

309 SMXG Global Broadcasting System (GBS) Engineering Services Task Order Performance-based Work Statement

Hill Air Force Base, UT 84056

Executive Summary

The 309th Software Maintenance Group (309 SMXG) is a world-class software sustainment organization. 309 SMXG has a reputation for excellent performance, war-fighter support and delivery of high-quality products and is Software Engineering Institute (SEI) certified Capability Maturity Model Integration (CMMI) Level 5 organization. The Group’s Vision Statement encompasses an emphasis on process improvement: “We are the team of choice providing exceptional weapons systems software and related hardware solutions and technology adoption expertise to enhance our nation’s defense. Our continually improving processes, skills and business practices ensure a stable, productive, and technically challenging environment that results in high customer satisfaction.” The current workloads of the 309th Software Maintenance Group are numerous and imperative to the continued mission of Hill AFB and the war-fighter. 309 SMXG has a history of providing improved weapon system capabilities, quality products, fiscal performance, and on-time delivery.

309 SMXG is a world-leader in “cradle-to-grave” systems support, performing software sustainment, including;

· corrective maintenance of faults discovered in the operation of the software

· preventive maintenance of faults

· perfective maintenance to incorporate changes to users’ requirements or changes in operational needs

· adaptive maintenance to respond to changes in hardware or other environmental conditions or interface requirements for interoperability

Software engineering development and maintenance is transforming the modern battlefield. Advancements in hardware architecture are most efficiently used when they are combined with software technology. Older, less efficient hardware can be made to operate more efficiently and capably through software enhancement. Software can be easily changed to adapt or modernize capabilities in mission areas and assigned tasks. Software algorithms are often times classified at the secret or top secret level. Facilities shall be able to support the physical requirements of the Joint Air Force Army Navy (JAFAN) 6/9 security policy.

Products developed and sustained include operational flight programs, operating programs, Command & Control, Communications, Computers and Intelligence (C4I) communications systems, flight-line support equipment, Automatic Test Equipment Test Program Sets, database applications, Web based applications, and many others, along with supporting documentation. Skills include system software design and development for various systems, hardware design and development, electronic circuit analysis, design and development of test platforms, simulation & modeling, and many others.

309 SMXG employs a wide variety of software engineering technologies to develop system and subsystem designs which include software (operational, supporting, and utility), test procedures (Manual and Automated), Configuration Management, data archiving, and product delivery. Operating systems in active use are Windows, Video Management Software (VMS), Linux, Solaris, Real Time Operating System (RTOS), UNIX and others. Programming languages including Ada, C, Visual C/C++/C#, C++, .Net Technology, Java, Fortran, Assembly, Jovial, Visual Basic and scripting languages such as Extensible Markup Language (XML), Hypertext Markup Language (HTML), Java Script, Active Server Pages (ASP), Perl are utilized.

The 309 SMXG employs numerous engineering support and cutting edge technologies to respond to the rapidly changing Software engineering environment. Mission requirements of development and maintenance and validation of weapon system software, Test Program Set (TPS) and associated Integration Test Adapter (ITA), C4I and situational awareness functionality drive stringent processes, peer reviews, Configuration Management and documentation of the system as it is built.

The 309 SMXG is and shall remain highly proficient at software development, real-time operating system development, software languages and development suites, automated test scripting languages, hardware and communication component development and integration, and integration of Commercial off the Shelf (COTS) components.

309 SMXG GBS Engineering Services Support

1. PURPOSE

The purpose of this contract is to transfer knowledge from the contractor to the Government by providing temporary interim support in assisting the 309th Software Maintenance Group (309 SMXG) with the sustainment of the Global Broadcast Service (GBS) that is being transitioned to 100% organic support at Hill Air Force Base, Utah under Depot Source of Repair (DSOR).

2. SCOPE

The contractor shall be certified as a Level 3 Capability Maturity Model Integration (CMMI) company. Under the direction of DSOR #10-146, the Defense Enterprise Computing Centers (DECC) Global Broadcast Service (GBS) Satellite Broadcast Manager (SBM) and Receive Broadcast Manager (RBM), will be sustained by the 309th SMXG, Hill Air Force Base, UT. 309th SMXG engineers do not have the domain expertise to sustain this service at this time and requires subject matter experts (SMEs) experienced in the development / design of the system to transfer this knowledge to organic personnel.

3. REQUIREMENT(S)/DESCRIPTION OF SERVICE(S)

3.1 Tier II Operations Support Requirements (Includes On Call Support)

The Contractor shall use disciplined systems engineering processes including, but not limited to; requirements development, technical management and control, system/software design and architecture, Integrated Risk Management, Configuration Management, Data Management, test, evaluation, verification and validation practices throughout the period of performance of task orders in accordance with AFI 63-101/20-101 Integrated Life Cycle Management.

The Contractor shall provide Tier II SBM Operations Support to include 24/7 on-call support to the GBS Operations Center (GBSOC) with two (2) hour(s) response time. The Contractor shall provide operational technical support and troubleshoot operational issues. The Contractor shall provide on-call support for technical assistance, support of multiple software versions, training, testing and maintenance, 24-hours a day, 7-days a week, 365 days a year. The Contractor shall maintain and conduct an annual SBM Operator Training course for the GBSOC operations staff and other Government personnel.

The Contractor shall provide Tier II RBM Operations Support to the GBSOC and directly to the Services as the RBM GRS release(s) is fielded by the DoD Services. This includes supporting the transition of the Legacy RBMs to RBMs running GRS.

The Contractor shall report GBS documentation deficiencies found to appropriate organization. The Contractor shall act as a GBS liaison to DISA DECC and DISA Consolidated Communications Center (CCC). The Contractor shall assist with troubleshooting source integration issues and provide Continuity of Operations (COOP) and reconstitution support to the GBSOC.

The Contractor shall support planning, preparation and execution of test events, technology transitions and satellite constellation changes as directed by the Government. The Contractor shall assist the Government in installation and verification of changes made to the SBM Mission Unique Equipment (MUE), shared DECC Infrastructure, Primary Injection Point (PIP) and Teleport networks as directed by the Government.

The Contractor shall informally train and perform systematic GBS domain knowledge transfer to the 309 SMXG of the Tier II Operations activities.

3.2 DECC GBS Domain Subject Matter Expert (SME) Reach back Sustainment Support

The Contractor shall analytically and systematically evaluate problems of work flows and network usage, organization, planning and develop appropriate corrective action. The Contractor shall design architecture to include the software, hardware and communications to support the total requirements as well as provide for present and future cross-functional requirements and interfaces.

The Contractor shall provide support, analysis and research into complex problems and processes relating to the subject matter. The Contractor shall serve as a technical expert on executive-level project teams providing technical direction, interpretation and alternatives.

The Contractor shall work under consultative direction toward predetermined long-range goals and objectives. The Contractor may be required to self-initiate assignments. The Contractor shall determine and pursue courses of action necessary to obtain desired results.

The Contractor shall provide SBM and RBM sustainment reach-back support to 309 SMXG and MCL to include:

· Investigating System Problem Reports (SPRs) as requested

· Evaluate and verify proposed changes to the GBS DECC infrastructure

· Providing SBM release installation and verification support

· Providing GRS release development support and regression testing support

· Supporting the MCL Deficiency Review Board (DRB) and Engineering Review Board (ERB)

· New capability source integration (i.e. Split-IP v2.0)

· Maintaining the existing sustainment procedures (B014)

· Other development activities as directed by the Government

The Contractor shall develop engineering change studies, engineering change requests (CRs) and engineering change proposals (ECPs) for recommended changes in the GBS DECC architecture and the associated test and support environment software/hardware. For activities that are not within scope of the Performance-based Work Statement (PWS), engineering change packages (ECPs) shall be prepared IAW Contract Data Requirements List (CDRL) Axxx to include updated source data for Time Compliance Technical Orders (TCTOs), Technical Orders/Technical Manuals and the GBS System Requirements Document (SRD). The Contractor shall assist the 309 SMXG to produce prototype designs and oversee development and testing for proposed changes.

The Contractor shall engineer solutions as required and prioritized by the Government to include assigned SPRs, Cyber Security (formerly IA) compliance requirements, requests for product improvements, and COTS Obsolescence Resolution tasks written against GBS system products.

The Contractor shall informally train and perform systematic GBS domain knowledge transfer to the 309 SMXG of the SBM and RBM to include the design, development, and operational troubleshooting of the GBS.

3.3 Cyber Security Support of the SBM and RBM

The contractor shall perform information assurance activities including the documentation and testing required to maintain all appropriate Authority to Operate (ATO) certifications for the SBM and RBM. The contractor shall evaluate Information Assurance Vulnerability Alerts (IAVAs) as they are released by CYBERCOM for applicability and creating the appropriate SPRs. The contractor shall evaluate Security Technical Implementation Guide (STIG) updates as they are released by CYBERCOM for applicability and creating the appropriate PRs. The contractor shall provide regular Plans of Actions & Milestones (POA&M) updates as required to maintain the SBM, and RBM accreditation.

The contractor shall evaluate the Cyber Security impacts of the proposed solutions for all SBM and RBM PRs. The contractor shall perform a Risk Assessment of all SBM and RBM releases prior to their installation and fielding at the operational sites. The contractor shall support the transition from DIACAP to the Risk Management Framework (RMF) per NIST SP 800-53 Version 4 for the SBM and the RBM packages.

The Contractor shall informally train and perform systematic GBS domain knowledge transfer to the 309 SMXG of the information assurance activities.

3.4 Sigonella Primary Injection Point (PIP) Site Support (Option CLIN)

3.4.1 Sigonella PIP SME Reach back Support

The Contractor shall provide Sigonella PIP DECC Enclave sustainment reach-back support to 309 SMXG and MCL to include assisting in designing, implementing, and testing changes to the Sigonella PIP DECC Enclave baseline.

3.5.2 Cyber Security Support of the Sigonella PIP Site Support

The contractor shall perform information assurance activities including the documentation and testing required to maintain all appropriate Authority to Operate (ATO) certifications for the Sigonella PIP. The contractor shall evaluate Information Assurance Vulnerability Alerts (IAVAs) as they are released by CYBERCOM for applicability and creating the appropriate SPRs. The contractor shall evaluate Security Technical Implementation Guide (STIG) updates as they are released by CYBERCOM for applicability and creating the appropriate PRs. The contractor shall provide regular Plans of Actions & Milestones (POA&M) updates as required to maintain the Sigonella PIP accreditation.

The contractor shall evaluate the Cyber Security impacts of the proposed solutions for Sigonella PIP PRs. The contractor shall perform a Risk Assessment of the Sigonella PIP updates prior to their installation.

3.6 Travel

The Contractor shall travel as needed for project purposes including, but not limited to program support and software maintenance activities. The Contractor shall coordinate specific travel arrangements with the Government to obtain advance, written approval for the travel that may be conducted. The Contractor’s request for travel shall be in writing and contain the dates, locations and estimated costs of the travel in accordance with the basic contract clause H047. Costs associated with contract travel shall be in accordance with FAR Part 31.205-46 Travel Costs.

If any travel arrangements cause additional costs to the task order that exceed those previously negotiated, written approval by the Contracting Officer is required, prior to undertaking such travel. The Contractor shall travel using the lower cost mode transportation commensurate within the mission requirements. When necessary to use air travel, the Contractor shall use economy class or similar accommodations to the extent when they are available and commensurate with the mission requirements. Travel will be reimbursed on a cost reimbursable basis; no profit or fee will be paid.

The Government estimates travel will be performed at a minimum, quarterly, to support release and major technical interchange meetings to the following locations: Oklahoma City, OK; Shriever AFB, CO; Peterson AFB, CO, Mechanicsburg, PA; Hill AFB, UT; Sigonella, Italy (specific to section 3.5). The Contractor shall travel to other locations as directed by Government.

4.0 CONTRACTUAL REQUIREMENTS

4.1 Place of Performance

The Place of Performance will be primarily at the contractor facility. Contractor personnel shall augment 309 SMXG with on-site contractor support to work with civilian personnel on an as needed basis in a team environment on depot software maintenance activities. Locations for support may include but are not limited to Hill Air Force Base, UT; Oklahoma City, OK; Peterson AFB, CO; Shriever AFB, CO; Mechanicsburg, PA; and Sigonella, Italy (specific to section 3.4). The Government will provide no permanent working space in any of the above mentioned facilities.

4.2 Government Furnished Property

The Contractor shall be responsible for safeguarding all Government property provided for Contractor use. At the close of each work period, Government facilities, property, and materials shall be secured.

4.3 Facilities and Equipment and Personnel for Off-Site Support

The contractor shall have the capability to establish or have access to the facilities, equipment, and qualified personnel necessary to meet the requirements of the PWS. The contractor shall have the ability to obtain and effectively utilize these facilities, equipment, and qualified personnel. The Government is not obligated to provide these facilities/equipment.

The following listing of property is provided in support of this PWS. All property provided to the contractor shall remain the property of the Government. The contractor shall conduct a joint inventory with the Government and turn in this equipment to the Contracting Officer Representative upon request or completion of the Task order. If the contractor proposes alternative tools, models, equipment etc., in supporting the requirements of the PWS, the verification, validation, and accreditation of those items shall be included in the proposal.

4.4 Non-Personal Services

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the contractor feels that any actions constitute, or are perceived to constitute personal services, it shall be the contractor’s responsibility to notify the Contracting Officer immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions relative to programs supported by the contractor shall be the sole responsibility of the Government.

4.5 Contractor Identification

All contractor/subcontractor personnel shall be required to wear AF-approved or provided picture identification badges so as to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, contractor/subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors/subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractor/subcontractors occupying collocated space with their Government program customer should identify their work space area with their name and company affiliation. Refer to Clause H063 of the overarching ID/IQ contract.

4.6 Task Order Management

The Contractor shall establish and provide a qualified workforce capable of performing the required tasks. The workforce may include a project/task order manager who will oversee all aspects of the task order. The Contractor shall use key performance parameters to monitor work performance, measure results, ensure delivery of contracted product deliverables and solutions, support management and decision-making and facilitate communications. The Contractor shall identify risks, resolve problems and verify effectiveness of corrective actions. The Contractor shall institute and maintain a process that ensures problems and action items discussed with the Government are tracked through resolution and shall provide timely status reporting. Results of contractor actions taken to improve performance shall be tracked, and lessons learned incorporated into applicable processes. The Contractor shall establish and maintain a documented set of disciplined, mature, and continuously improving processes for administering all contract and Task Order efforts with an emphasis on cost-efficiency, schedule, performance, responsiveness, and consistently high-quality delivery. The Contractor shall provide transition plans as required.

The Contractor shall provide the Government, via email, a Contractor’s Progress Report, in Contractor format, which will provide program cost information and the tasks accomplished each month by the Contractor. The Contractor shall obtain Government approval of the report format and content prior to the first submittal. The Contractor shall submit the report as outlined in the associated CDRL. (A057) Information contained shall match the Contractors monthly invoice. The Contractor shall provide, via email, interim financial status information as requested by the Government. The financial report shall contain sufficient information both in breath and detail to provide the Government a means to track all expenditures related to this contract.

4.7 Quality Control

The Contractor shall have in place a Human Resource Management Program to ensure qualified candidates are identified, screened, placed, monitored, and trained/retained to fulfill service requirements. The Contractor shall accomplish requirements by employing and utilizing qualified personnel with appropriate combinations of education, experience, knowledge, training, abilities and skills, as well as physical capabilities. The Contractor shall maintain clear organizational authority and responsibility to effectively manage and control personnel. This shall be accomplished without requiring Government employees to engage in the contractor’s operational or human resource management processes. The Contractor shall have an internal process in place to ensure that work or labor hours reported by employees are accurately reflected on billing invoices and monthly reports.

The Contractor shall establish and provide all reasonable means to ensure that performance of this contract in a Government facility is fully complementary with, and does not run counter to, any written local operating procedure or policies that may be provided by the Government. This is consistent with the contractor’s exclusive right and authority to supervise and control its employees.

The Contractor’s Quality Control Program is the means by which he assures himself that his work complies with the requirement of the contract. This plan shall be provided as part of the task order proposal but shall not be evaluated for award. The Contractor shall make appropriate corrections and modifications to the plan and obtain acceptance of the plan by the contracting officer before the start of the first operational performance period. Updates shall be provided whenever there is a change. (A083)

The plan shall reflect the contractor’s overall approach, internal management controls, processes, and procedures for reporting to the Government on identified aspects of quality issues. The plan shall identify the means by which the contractor will ensure quality effectiveness and demonstrate comprehensive management and review of data. The plan shall describe what is measured, how often it is tracked and provided, who reviews and assures that appropriate action is initiated when trends are unfavorable, who the Government will contact for contractor quality issues, what method and process is used to track and resolve issues, where reports are sent and maintained, and how often quality issues are reviewed and reported. The plan shall identify how the contractor identifies and resolves deficiencies, identifies potential improvements, and maintains and makes available to the Government, documentation reflecting quality control inspections and any corrective actions taken. The Contractor shall provide copies of all discrepancies to the COR.

4.8 Safety Requirements

In performing work under this task order, the Contractor shall conform to the safety requirements contained in this Performance-based Work Statement and the Safety, Fire Protection and Health Specification Industrial Safety Requirements (attached) for all activities related to the accomplishment of the work. Take such additional immediate precautions as the contracting officer may reasonably require for safety and mishap prevention purposes. Implement a safety program in accordance with the applicable contract clauses and their accepted Safety and Health Program Plan. (A099)

Contractors shall comply with Occupational Safety and Health Act (OSHA) (Public Law 91-596) and OSHA Standard 29 CFR 1910 for the protection of their employees. It is the Contractor’s sole responsibility to make certain that all safety requirements are net. Additionally, the Contractor is responsible for the safety and health of all subcontractor employees. The 309 SMXG and Hill AFB are pursuing recognition under OSHA’s Voluntary Protection Programs (VPP). To achieve and maintain this level of recognition, all contractors working on the installation shall receive the same level of safety and health protection as Government employees. All contractors are required to familiarize themselves with the requirements of VPP. Information on the VPP can be accessed at http://www.osha.gov/dcsp/vpp/index.html.

The Contractor shall provide to the Government, on an annual basis, injury and illness rates for employees working onsite at a government facility during the previous calendar year under this contract; specifically the Total Case Incidence Rate (TCIR) and Days Away, Restricted, or Transferred (DART) rates consistent with OSHA’s recordkeeping requirements. These rates shall be provided by 01 Feb of each year for comparison with corresponding injury and illness rates provided by the Bureau of Labor Statistics (BLS) based on the appropriate North American Industrial Classification System (NAICS) code and shall be included in any subsequent OSHA VPP Application or Annual Self Evaluation as required. For more information on TCIR/DART calculations and related VPP documentation, refer to OSHA Publication CSP 03-01-003, Voluntary Protection Program (VPP): Policies and Procedures Manual, Appendix A. http://www.osha.gov/OshDoc/Directive_pdf/CSP_03-01-003.pdf (A055)

4.9 Security

4.9.1 Protection of System Data

The Contractor shall not release or remove system documentation, data, or reports generated by or through use of Government systems. The Contractor shall not divulge any information regarding files, data, processing activities/functions, user IDs, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. All requests for information shall be forwarded to the appropriate 309 SMXG security manager. A signed Non-Disclosure Agreement is required for each employee.

The Contractor shall protect system design-related documents and operational data whether in written form or in electronic form via a network in accordance with all applicable policies and procedures for such data, including DoD Regulation 5400.7-R and DoD Manual 5200.01(v1-v4) to include latest changes, and applicable service/agency/ combatant command policies and procedures. The Contractor shall protect system design related documents and operational data at least to the level provided by Secure Sockets Layer (SSL)/Transport Security Layer (TSL)-protected web site connections with certificate and or user ID/password-based access controls. In either case, the certificates used by the Contractor for these protections shall be DoD or IC approved Public Key Infrastructure (PKI) certificates issued by a DoD or IC approved External Certification Authority (ECA) and shall make use of at least 128-bit encryption.

4.9.2 Transmission and Marking of Classified Material

The Contractor shall transmit and deliver classified material/reports IAW the National Industrial Security Program Operating Manual (NISPOM) DoD 5220.22-M. These requirements shall be accomplished as specified in this task order. The Contractor shall mark all classified products, regardless of media (i.e., paper documents, e-mails, slide presentations, web pages, etc.) IAW DoDM 5200.01-V2. The ISOO Marking Classified National Security Information Booklet may be used for training and/or reference material. In the event of any conflicts between this publication, the ISOO Marking Classified National Security Information Booklet, and DoDM 5200.01-V2, follow the DoD Manual. In addition to marking classified material, unclassified material kept in a security container, secure room, or vault storing classified material shall be marked to reflect its unclassified status. The Contractor shall be compliant with Air Force Instruction (AFI) 31-401 Information Security Program Manager Air Force Guidance Memorandum 3013-03 dated 18 September 2013 as prescribed in Air Force Instruction 31-601, Industrial Security Program.

4.9.3 Personnel Security

Contractors shall have, at a minimum, a SECRET clearance prior to performing services under this task order. Any clearance requirements other than SECRET will be communicated to the contractor by the Contracting Officer post-award and time to meet any additional clearance requirements will be coordinated through the Contracting Officer. The Contract Security Classification Specification (DD Form 254) is at the task order level and encompasses all security requirements required specific to this task order.

In accordance with DoD 5200.2-R, Personnel Security Program (Jan 87), DoD military, civilian, consultants, and contractor personnel using unclassified automated information systems, including e-mail, shall have, at a minimum, a completed favorable National Agency Check plus Written Inquiries (NACI). The contractor shall familiarize all new employees and conduct refresher sessions as needed in the areas of Operations Security as referenced on the current DD Form 254 (DoD Contract Security Classification Specification) addendum. Operations Security (AFI 10-701 OPSEC Security as supplemented, and AFI 31-401 Information Security Program, Standards for Storage and Handling Classified Material as supplemented).

The types of Personnel Security Investigations (PSI) required for the contractor vary in scope of investigative effort depending upon requirements of the Government and/or conditions. The Contractor shall diligently pursue obtaining the appropriate PSI for its employees prior to assigning them to work. Acquisition planning shall consider Anti-Terrorism (AT) measures when the effort to be contracted could affect the security of operating forces (particularly in- transit forces), information systems and communications systems IAW DoD Instruction 2006.16 Anti-Terrorism Standards.

4.9.4 Contractor Identification Badges

Badge/Common Access Card (CAC) Information/Unescorted Entry Authorization, IAW Hill AFB Instruction 36-812. The Contractor shall meet the same security requirements as Government employees for access to the site Air Force Base’s (AFB) network or Automated Information Systems (AIS).

For a CAC to be issued to the Contractor, the process as outlined in HAFB OI 36-812 will be followed. The Contractor shall complete and submit a Contractor’s CAC application form (AFMC Form 496) for each of the contractor’s employees who shall have access to a Government computer to begin this process. A Defense Biometric Identification System (DBIDS) card may be issued if necessary during this process after a Local Files Check has been accomplished by the Security Manager. The forms shall be submitted to the Complex/Group security manager(s) for approval. A DBIDS card may be issued if necessary during this process after a Local Files Check has been accomplished by the Security Manager. The Contractor shall coordinate with the Complex/Group Security Manager(s) to ensure new contractor employee’s packets are complete and submitted.

The Contractor’s 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 Security Forces (site location Visitor Center). The AF Form 2586 shall be returned to the Government security manager for accountability.

As required, the contractor employee shall also obtain a Building ID and access card from the appropriate Building Security Manager.

When the Period of Performance (PoP) has ended or the task is considered complete, contractors shall have five (5) working days to terminate all their network user accounts and to return all access cards and base identification badges.

During performance of the contract and at the completion or termination of the contract, the Contractor shall be responsible for prompt return of credentials to the appropriate security manager for any employee who no longer requires access to the work site, and for obtaining required identification of newly assigned personnel. Lost badges shall be reported to the Maintenance Group Security Officer within one (1) working day of loss.

Should a security violation occur, the Contractor shall: immediately report to the site location Group Security Manager all available facts related to each instance; take such precautions as the Security Manager may reasonably require for security purposes; take reasonable and prudent action to establish control of the scene, prevent further violation, and to preserve evidence until released by proper authority; and cooperate fully and assist Government personnel as the Government conducts an investigation of the violation. Participation shall last until the investigation is completed.

The Contractor shall create an Incident/Mishap report when a contract employee loses a CAC or Restricted/Controlled Area Badge Line badge.

4.9.5 System and Network Authorization Access Requests

All communications with DoD organizations are subject to Communications Security (COMSEC) review. The DoD authorizes the military departments to conduct COMSEC monitoring and recording of telephone calls originating from, or terminating at DoD organizations. The Government advises the contractor that at any time they place a call to, or receive a call from a DoD organization, they are subject to COMSEC procedures. The Contractor assumes the responsibility for ensuring wide and frequent dissemination of the above information to all employees dealing with official DoD information. For Contractor personnel who require access to DoD, DISA, or Air Force computing equipment or networks, the Contractor shall have the employee, prime or subcontracted, sign and submit a System Authorization Access Report (SAAR), DD Form 2875 and complete Government provided Information Assurance Awareness Program (IAAP) training prior to accessing Government computer networks.

4.9.6 Key/Key Card 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, misplaced, or used by unauthorized persons. The Contractor shall not duplicate any keys/key cards issued by the Government. Immediately report to the Government Program Manager or Contracting Officer any occurrences of lost or duplicated keys/key cards. The Contractor shall be required, in the event contractor controlled keys/key cards are lost or duplicated, to re-key or replace the affected lock or locks without cost to the Government.

4.10 Data Rights and Non-Commercial Computer Software

In order to implement the provisions at DFARS 252.227-7013(b) and (e) and DFARS 252.227- 7014(b) and (e) and DFARS 252.227-7017, the Contractor shall disclose to the ordering Contracting Officer and ordering office in any proposal for a task order, or after award of a task order if not previously disclosed in the proposal, any technical data or non-commercial computer software and computer software/source code documentation developed exclusively at Government expense in performance of the task order. This disclosure shall be made whether or not an express requirement for the disclosure is included or not included in the PWS or solicitation for the order. The disclosure shall indicate the rights asserted in the technical data and non-commercial computer software by the Contractor and rights that would be acquired by the Government if the data or non-commercial software was required to be delivered under the task order and its CDRL requirements and any cost/price associated with delivery. This disclosure requirement also applies to segregatable routines of non-commercial software that may be developed exclusively at Government expense to integrate Commercial Software components or applications provided under a commercial software license or developed to enable Commercial Software to meet requirements of this Task Order. Performance of this disclosure requirement shall be considered a material performance requirement of any task order under which such technical data or non-commercial computer software is developed exclusively at Government expense.

4.11 Software Support and Data Rights

Unless specified otherwise in the Task Order, the Contractor shall fully support all unique software developed to support integrated solutions on this contract. The Contractor shall be able to support all software revisions deployed or resident on the system, and sub-systems.

The data rights ownership/licensing guidance are specified in Section I, Clause 252.227-7013 and 252.227-7015.

4.12 Training

Contractor personnel are required to possess the skills necessary to support their company’s minimum requirements of the labor category under which they are performing. Training necessary to meet minimum requirements will not be paid for by the Government or charged by contractors.

Ogden Air Logistics Complex (ALC) required training will be provided by the Government in accordance with Ogden ALC training requirements consisting of approximately 16 hours initial new hire training and will be required prior to performance of the basic requirements with an additional 14-16 hours refresher training annually. Any training beyond an estimated 20 hours within each 12 month period of performance shall be specifically authorized by the Contracting Officer and will require a signed memorandum that such contemplated labor, travel, and costs to be reimbursed by the Government are mission essential and in direct support of unique or special requirements to support the billing of such costs.

4.12.1 Mission-Unique Training

In the event during the execution of this task it is determined to require a unique level of support because of program/mission-unique needs, then the contractor may directly charge on a cost reimbursable basis. Unique training required for successful support shall be specifically authorized by the Contracting Officer. Labor expenses and travel related expenses may be allowed to be billed on a cost reimbursement basis. Tuition/Registration/Book fees (costs) may also be recoverable on a cost reimbursable basis if specifically authorized by the Contracting Officer. The agency requiring the unique support shall document the file with a signed memorandum that such contemplated labor, travel, and costs to be reimbursed by the Government are mission essential and in direct support of unique or special requirements to support the billing of such costs against this effort.

4.12.2 Other Government-Provided Training

The Contractor’s employees may participate in other Government provided training, on a non-discriminatory basis as among contractors, under the following circumstances:

(1) The contractor employees’ participation is on a space-available basis

(2) The contractor employees’ participation does not negatively impact performance of this task order

(3) The Government incurs no additional cost in providing the training due to the contractor employees’ participation

(4) Man-hours spent due to the contractor employees’ participation in such training are not invoiced to the task order

4.13 Section 508 of the Rehabilitation Act

The Contractor shall meet the requirements of the Access Board’s regulations at 36 CFR Part 1194, particularly 1194.22, which implements Section 508 of the Rehabilitation Act of 1973, as amended. Section 508 (as amended) of the Rehabilitation Act of 1973 (20 U.S.C. 794d) established comprehensive requirements to ensure: (1) Federal employees with disabilities are able to use information technology to do their jobs. (2) Members of the public with disabilities who are seeking information from Federal sources will be able to use information technology to access the information on an equal footing with people who do not have disabilities.

4.14 Continuation of Essential Contractor Services during Crisis Declared by the President of the United States, the Secretary of Defense, or Overseas Combatant Commander

The performance of these services may be considered mission-essential functions during time of crisis. Should a crisis be declared by the Secretary of Defense, the CO or representative will verbally advise the Contractor of the revised requirements, followed by written direction. When a crisis is declared, all services identified in this PWS are considered mission-essential functions during a crisis. The Contractor shall continue providing service to the requesting organization 24 hours a day until the crisis is over. The Contractor shall ensure enough skilled personnel are available during a crisis for any operational emergency. A crisis management plan shall be submitted IAW A-TE-3, A04, which states that the Contractor shall “Submit an essential personnel list within 10 days after the contract start date. The list shall contain the employee’s name, address, home phone number, beeper number (or cell phone number), social security number, security clearance, and duty title. This list shall be updated annually or as changes occur. It must include the language spelled out in DFARS 237.76 – Continuation of Essential Contractor Services to identify services determined mission-essential functions during a crisis situation IAW DODI 3020.37. Note: It is the responsibility of the Combatant Commander to determine mission-essential functions and to establish procedures to ensure that these standard support requirements and any additional requirements are met.

5.0 SERVICES DELIVERY SUMMARY

6.0 DATA DELIVERABLES

The Government requires all deliverables that include Scientific and Technical Information (STINFO), as determined by the Government, be properly marked IAW DoD Directive 5230.24 and AFI 61-204 prior to initial coordination or final delivery. Failure to mark deliverables as instructed by the Government will result in non-compliance and non-acceptance of the deliverable. The Contractor shall include the proper markings on any deliverable deemed STINFO regardless of media type, stage of completeness, or method of distribution. Therefore, even draft documents containing STINFO and STINFO sent via e-mail require correct markings. Additionally, the contractor shall formally deliver as a CDRL all intellectual property, software, licensing, physical records, files, documents, working papers, and other data for which the Government shall treat as deliverable.

Detailed Contract Data Requirements List is provided below IAW DFAR 204.7105 on DD Form 1423-1, FEB 2001.

A055 – DI-MGMT-80227 OSHA 300 Information Total Case Incident Rate/Days Away Restricted or Transferred (TCIR/DART) rate A057 – DI-MGMT-80555A Program Progress Report A067 – DI-MGMT-81834 Contractor’s Personnel Roster A083 – DI-QCIC-81794 Quality Assurance Program Plan A099 – DI-SAFT-81563 Safety Plan/Accident/Incident Report engineering change packages (ECPs) shall be prepared IAW CDRL Axxx (para 3.3)

7.0 APPLICABLE STANDARDS AND REFERENCES

Related Documentation:

· 309 SMXG Policy 309 SMXG Policy for Engineering Development and Support Project Management, 25 January 2011

· AS9100-2009 Rev. C Quality Management Systems – Requirements for Aviation, Space and Defense Organizations

· AS9115 Quality Management Systems – Requirements for Aviation, Space and Defense Organizations – Deliverable Software (Supplement to 9100)

· CMMI-Dev, V1.3 CMMI for Development, Version 1.3, November 2010, Carnegie Mellon University, Software Engineering Institute, Third Edition

· IEEE Std 828-2005 IEEE Standard for Software Configuration Management Plans

· EIA STD-649 EIA Standard, National Consensus Standard for Configuration Management

· ISO 10007 International Standard, Quality Management Systems – Guidelines for Configuration Management

· T.O. 00-5-16 Software Managers Manual USAF Automated Computer Program Identification Numbering System (ACPINS), 1 January 2009

· T.O. 00-5-17 User’s Manual USAF Computer Program Identification Number (CPIN) 15 May 2003 Global Broadcast Service Security Classification/Declassification Guide (SCG) Revision A , signed 23 May 2013

OGDEN AIR LOGISTICS COMPLEX

UNITED STATES AIR FORCE

HILL AIR FORCE BASE, UTAH 84056

APPENDIX C

SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION

INDUSTRIAL SAFETY REQUIREMENTS

PREPARED BY:

Roger Hoffmann, OO-ALC/SE, DSN 777-3972

SECTION I – GENERAL REQUIREMENTS

A. Safety Program Requirements.

In context with AFMC Acquisition Reform initiatives, contract language will now focus on ensuring safety objectives are met through contractor risk management rather than the traditional method of providing specific Government guidance for risk elimination. With this “nonperformance-based” language, the Government will provide the Contractor with Government identified workplace hazards at the task order level for Government employees as informational to the Contractor. The Contractor will be required to survey and identify workplace hazards and meet safety requirements to include providing Personal Protective Equipment for Contractor employees. The Contractor will implement a safety program plan 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. A Safety Plan and corresponding site specific checklist that addresses, as a minimum, the subjects listed in Section II –Specific Requirements, and will be used during the performance of the work described in the contract. The Safety Plan and checklist will be approved by OO-ALC/SE (Safety Office) prior to commencement of any work described in this contract.

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

4. Competent personnel to provide surveillance of the Safety Plan.

5. All Contractor personnel shall be trained and qualified to perform their duties safely.

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

B. Mishap Notification

1. For operations outside of Hill AFB, Contractor shall comply with local mishap reporting procedures as well as those listed below.

2. The Contractor shall notify OO-ALC Safety (Phone (801) 777-3972) who in turn will notify 75 ABW/SEG ((801) 777-3333) or OO-ALC Operations Center ( (801) 777-3238), or the Hill AFB Command Post (801-777-3007) after normal duty hours, and the designated Government Representative (GR), i.e., the ACO, PCO, PM or COR, 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 Safety. 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 COR.

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

3. IAW AFI 91-204, paragraph 2.4.6:

· The Contractor will support and comply with the safety investigation and report requirements of AFI 91-204

· The Contractor shall be aware that:

· A record of all mishaps involving Air Force resources will be entered into the Air Force reporting system

· A record of mishaps involving other DoD resources will be forwarded to the involved agencies

· The Air Force is responsible for the investigation of mishaps involving aerospace vehicles. The Air Force is authorized to investigate mishaps involving non-accepted Air Force aerospace vehicles (Non-delivered vehicles for which the Government has accepted responsibility; DD Form 250. Material Inspection and Receiving Report, HAS NOT been executed).

4. If requested by authorized Government personnel (ACO, PCO, QAE, safety representative, Fire Department, and Security Forces), the Contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by safety investigators.

C. General Safety Requirements:

If the safety plan is modified, the contractor shall submit the proposed modification, in writing, IAW CDRL A099.