PWS-BAM-AHAS 03-20-25 Draft.pdf

AIR FORCE SAFETY CENTER BAM/AHAS

PERFORMANCE WORK STATEMENT (PWS)

20 March 2025

1. Title. Air Force Safety Center Bird Avoidance Model/ Avian Hazard Advisory System (BAM/AHAS) Support

2. Background. The United States Air Force (USAF) experiences thousands of bird strikes each year during flight operations in low-altitude environments. The average costs associated with those strikes exceeded $35 million annually prior to 2001. The USAF Bird/wildlife Aircraft Strike Hazard (BASH) Team developed a Bird Avoidance Model (BAM) to assist in reducing the potential of a damaging bird strike. The BAM has undergone several revisions in an effort to more adequately identify hazardous bird concentrations, but continues to be limited by biases in historical data which provides the baseline data for distribution.

In the late 1980’s, the USAF BASH Team funded research to determine the potential capability of integrating the Next Generation Weather Radar (NEXRAD) network as a source for near real-time hazard advisories. Work conducted by Dr. Ron Larkin, University of Illinois, concluded NEXRAD Doppler radar could identify bird targets and that data could be processed to identify hazardous conditions. This initial investigation was conducted from 1985 through 1991, and a final report was presented in 1995. In the intervening years, several developments changed the potential options for identification and dissemination of bird hazard advisories. First, NEXRAD data was made available to commercial vendors for processing to sell to various industries, (e.g., mostly television markets). The National Information Distribution System (NIDS) allows for easy access to information from the NEXRAD model WSR-88D facilities nationwide at a single location by means of satellite data links. Second, advances in PC platforms allow for relatively inexpensive hardware to further process the data for the development of a bird hazard advisory system. Finally, improvements in communications capabilities by the internet allow for distribution of hazard advisories to multiple locations in relatively short periods of time.

Draft

The weather has long been understood to play a significant role in the movement of birds.

Integrating NEXRAD observations with weather data provides added insight into movement patterns of birds in the vicinity of routes, ranges, and Military Operational Areas (MOAs).

The USAF has funded several projects that integrate NEXRAD data into a comprehensive system to provide bird hazardous conditions. In 1998, the USAF funded a project to assess the technical capabilities of the WSR-88D and identify potentially hazardous bird concentrations moving in a region from Cape Fear, North Carolina, north to the Canadian border, and from the Atlantic Ocean coastline west to the Appalachian Mountains. Avian Hazard Advisory System (AHAS) advisories and forecasts are developed by processing radar data from the network of WSR-88D radars across the nation and from Model Output Statistics (MOS) weather data and vertical wind profiles. Data from the BAM is also incorporated into AHAS as a baseline model. Advisories and data processed through AHAS are archived for future integration into the BAM. Data collected from the AHAS system provides a higher resolution for the development of future updates to the BAM. Increased accuracy and update of data allows for the BAM to be a more integral part of the advisory system.

In 2005, independent contractors researched and developed a real-time bird monitoring radar using existing radar technologies to identify local bird hazards at airfields. This new system is Bird Detection Radar (BDR). Since its inception, BDR technologies have advanced to accurately depict bird concentrations in three-dimensional tracks within five Nautical Miles of airfields. Currently, BDR units are maintained at eight USAF locations world-wide. Ongoing procurement for additional BDR units is being sought by USAF Major Commands (MAJCOMs) and installation Wing units. The integration of BDR data must be included into the evolution of the USAF Bird Hazard Warning System through the BAM/AHAS contract, managed by Headquarters, Air Force Safety Center (AFSEC).

3. Objectives. This Performance Work Statement (PWS) describes the requirements, deliverables, and schedule to be executed by the contractor in support of the AFSEC BAM/AHAS contract. The objectives of this effort are to enhance the current USAF Bird Hazard Warning system by leveraging technological advances and available data (e.g., integration of the BDR and formal wildlife survey data) to boost the long-range safety benefits of the BASH program.

4. Scope. The contractor shall act as an integrating BAM/AHAS authority for USAF BASH programs, providing support services for the operation of the BAM/AHAS system as delineated in paragraphs 5.1, 6.1., and 6.4. of this document. This system support includes archiving of BAM/AHAS data, sustainment of the BAM/AHAS website, and development of avian risk models for low-level routes, visual routes, and MOAs/ranges. The contractor shall assist the USAF in: 1.) the development, implementation, operational deployment, assessment, sustainment, and enhancement of the USAF BAM/AHAS System; 2.)

knowledge sharing of technological and operational findings, benefits, and advances for integration with BAM/AHAS; 3.) collaboration with BASH Contracting Officer Representatives (CORs); 4.) regular communication with USAF/DoD personnel, and 5.)

maintenance and dissemination of educational/training materials for the operation of the BAM/AHAS system.

5. Performance Requirements.

5.1. Contract Manager. The contractor shall designate a Contract Manager that will oversee administration and execution of the BAM/AHAS project, including BAM/AHAS tasks completed by all contract personnel. The Contract Manger is responsible for overall operations and functional area management of the BAM/AHAS project, including:

performance monitoring, quality control, schedule development, and tracking/review of contract deliverables. The Contract Manager shall implement quality assurance through:

program evaluation, technical review support, configuration management, system sustainment, and risk management. The Contract Manager shall coordinate with AFSEC/SEFW CORs to apply continual development and maintenance of the BAM/AHAS system by identifying technological advancements in bird hazard detection through:

participation in various Working Groups, Technical Reviews, and Task Forces. The Contract Manager shall conduct educational outreach activities through remote, web-based presentations on the BAM/AHAS to various military and civilian groups, as noted in paragraphs 6.3.1. A Contract Manager and alternate must be designated at least 10 calendar days after contract award. The COR must be notified of a Contract Manager change 15 calendar days before a position change.

5.1.1. Personnel Qualifications. BAM/AHAS is a unique, mission-essential safety system, with required use that demands an uninterrupted operational status. The contractor shall provide and maintain personnel with expertise consistent with supporting the BAM/AHAS system. Personnel will include functional specialists in the following disciplines with the corresponding minimum qualifications:

• Radar Ornithology and Wildlife Science o Minimum of a Bachelor's degree in biology with an emphasis in wildlife behavior, specializing in bird movement and migration o Minimum of 5 years’ experience in bird movement and migration

• Data Geographic Information Systems (GIS) o Official certification or degree in GIS applications o 5 years’ experience in GIS applications

• IT systems management/programming o 5 years’ experience with a focus on government compliant information systems o All system administrators must obtain any one of three IAT certifications, according to their respective IAT level responsibilities. System administrators will maintain their IAT certification through annual recurring training. Available certifications for each IAT level along with requirements for recurring training may be referenced in DoD 8570.01-Manual paragraph C3.2.3.3. and extension Table AP3.T2.

(http://iase.disa.mil/eta/iawip/content pages/iabaseline.html), and satisfy requirements for IA control PRTN-1. Certification documentation will be promptly submitted to the AFSEC IA Workforce Improvement Manager (currently, also the

1AM).

• IAT Level II: The primary system administrator must maintain one of the following at a minimum: GSEC, Security+CE, or SSCP. (DoD 8570.01-M paragraph C3.4)

• IAT Level I: The alternate system administrator must maintain one of the following at a minimum: A+-CE, Network+CE, or SSCP. (DoD 8570.01- M paragraph C3.3)

NOTE: Experience must be current to within the past five (5) years.

Project management and functional specialists shall be in place within 15 calendar days and all other personnel will be in place within 30 calendar days of the contract start date. The contractor shall ensure personnel fulfilling this contract are eligible to hold a DoD Common Access Card (CAC). All personnel changes shall include nameless resumes to validate qualifications as stated above and provided to the COR for review. The contractor shall have personnel replacements in place within 15 calendar days from notice of expected or unexpected position vacancy. The contractor shall notify the COR or alternate COR within one day of the contractor’s discovery of an intended vacancy.

5.1.2. COR Approval. The contractor shall communicate BAM/AHAS system decisions, plans, processes, procedures, and recommended technology upgrades to the COR or alternate COR for review and approval prior to implementation within the BAM/AHAS system. COR approval is not needed for normal system upgrades, modifications, and sophistication of the BAM/AHAS system to ensure the most accurate generation of BAM/AHAS risk models. BAM/AHAS system updates and improvements will be consistent with requirements under paragraph 6.4.1.

5.1.3. Required Documentation. The contractor shall coordinate the project kick-off meeting at a government approved location within 10 calendar days of the contract award.

The kick-off meeting may be conducted remotely based on mutual agreement from the http://iase.disa.mil/eta/iawip/contentpages/iabaseline.html) contractor and COR. The kick-off meeting will include review of the BAM/AHAS Operational Control Plan and review of the Monthly Status Report format.

5.1.3.1. Operational Control Plan (OCP). The OCP will serve as operational guide for the execution of the BAM/AHAS system, to include:

• Provide a narrative summary detailing how task elements will be executed by the contractor, including all subparagraphs under paragraph 6, Engineering and Technical Support Tasks.

• Describe how the contractor will recognize system deficiencies through active self-inspection, particularly integration of radar and weather data.

• Identify the extent and cause of any non-conformance with mission support tasks and technological evaluations, and plans to accomplish corrective actions.

• Address how the contractor will prevent and correct lapses in analytical services (paragraph 6.1.1.). The OCP will describe conditions under which transfer from the primary BAM/AHAS Internet Protocol (IP) address to the backup IP address will be performed.

• Define system transition testing protocol and frequency. Transition testing is required to be completed at least quarterly. The contractor shall create an appropriate beta database for testing capability and applications.

• Define procedures for conducting utility system backup testing and contingencies for corrective action. Ensure that backup systems for sustaining BAM/AHAS are sufficient for providing user access and risk model generation for users.

The OCP will be submitted to the Contracting Officer (CO) and COR electronically by the kick-off meeting for review. If sections of the OCP are rejected by the CO, they will be changed and resubmitted within 10 calendar days of notification of non-acceptance. The OCP will ensure all written deliverables according to timelines identified in paragraph 14, Delivery Schedule.

5.1.3.2. Monthly Status Reports (MSR). MSRs shall describe contractor activities completed in the past month and anticipated activities for the next month, including any travel and corrective actions. The MSR must incorporate work accomplished during the reporting period and the status of long-term initiatives, to include:

• System validation execution and results (paragraph 6.1.4.).

• USAF analytical service support (paragraph 6.1.1.-6.1.7.).

• Analysis and implementation of system upgrades (paragraphs 6.2.2, 6.2.3., and 6.4.2.2.).

• Education and training activities (paragraph 6.3.).

• BDR data integration status (paragraph 6.4.1.3.).

• System maintenance and sustainment (paragraphs 6.4.1.1., 6.4.1.2., 6.4.3.1., 6.4.3.2. and 6.4.4.).

• TDY summaries in support of BAM/AHAS contract (paragraphs 8.2.).

• Results from the transition testing operations, to include dates of transition testing execution, outcome, and corrective actions.

• Results from backup testing operations, to include dates of backup testing execution, outcome, and corrective actions.

The contractor shall add any additional information and/or project issues deemed necessary for USAF awareness. MSRs must be included with each monthly invoice submitted by the contractor.

The Contract Manager shall ensure that all deliverables are technically correct, logically organized, free from clerical errors, and meet all requirements before they are submitted to the Government. The contractor will document all quality control efforts and make this documentation available to the COR and CO for review.

5.1.4. Certification and Accreditation (C&A). C&A ensures Information Assurance (IA) is properly implemented for all USAF procured Information Systems and Guest systems. The DoD-required process for accomplishing C&A is the Risk Management Framework (RMF).

Within the USAF this is now accomplished via the Enterprise Mission Assurance Support Service (eMASS). The contractor for BAM/AHAS must obtain certification and accreditation utilizing eMASS to achieve an Authority to Operation (ATO) from USAF Information Management Office (SAF/AAI). The contractor must sign an annual penetration testing letter allowing and providing the government permission to run annual Retina scans of and conduct annual penetration testing on the AHAS network in order to be compliant with the Federal Information Security Management Act of 2002 (FISMA) Title III IA requirements for Federal IT systems and satisfy requirements for IA Control ECMT- 1, Conformance Monitoring and Testing. This shall take place without any disruption in service, software corruption, or other unexpected results of the penetration testing.

Full Operating Capability (FOC) shall be defined as: 1.) the point in time at which all deliverables have passed User Acceptance Testing (UAT), 2.) received a valid ATO, and 3.)

when all USAF Safety offices have the ability to use the system in an operational sense (i.e., the system can be used by USAF personnel worldwide). Any schedule deviations that may impact the status of the FOC must be reported immediately to the COR. For C&A requirements to be achieved, the contractor secure FOC status through coordination with USAF within 90 calendar days of the contract award start date.

In the event physical data storage for the BAM/AHAS system migrates to a USAF-owned, Amazon Web Service (AWS) cloud-based data storage system, the contractor will ensure all

DoD and USAF security and information technology requirements are fulfilled for operational integrity.

5.1.5. Contractor Furnished Equipment. The contractor will furnish all equipment for the BAM/AHAS system. The contractor will ensure sustainment of adequate hardware, software, maintenance plans, and licenses required to maintain, support, and back up for BAM/AHAS. For each applicable task, the contractor shall ensure that all software has been thoroughly tested at the unit, component, and functional level, including regression testing.

6. Engineering and Technical Support Tasks.

The overall focus of this requirement area involves analyses, review, and presentation of bird hazards in the flight environment; development of technical strategy recommendations;

review and assessment of program/project technical direction/strategy; and technical consulting to programs and services. In particular it involves the following areas:

6.1. Mission Support Task.

6.1.1. Analytical Services. The contractor shall derive information using the existing bird hazard analysis tool set (consisting but not limited to the BAM/AHAS Program, Thermal Index Calculator, Forecast Loader, Weather Reader, AHAS Export Program, local BDR data, AF installation formal wildlife surveys, and Microsoft Internet Information Service) and communicate that information a minimum of every ten minutes to the USAF on a web-based platform.

To ensure the most accurate risk model possible, the contractor shall routinely review and evolve BAM/AHAS system techniques and visualizations. The contractor may provide feedback and recommendations to AFSEC on new avian radar detection technologies.

Implementation of new technology must be approved by the COR in advance. Installation-based BDR data and formal wildlife survey data will be continuously incorporated into BAM, as available. The contractor shall provide bird hazard analysis for all USAF training routes/areas to include Instrument Routes (IRs), Visual Routes (VRs), Slow Routes (SRs), Military Operations Areas (MOAs), Ranges, Military Airfields, and Civilian Airports (as requested).

6.1.2. Radar and Weather Data. The contractor shall acquire radar and weather data to identify near-real-time bird movements for developing hazard advisories. The contractor shall provide the necessary support to establish vendor service for NIDS and weather data, monitor NEXRAD sites in each geographic region to ensure validity and continual processing of data, archive NIDS files for future analysis, and integrate this data into the AHAS system.

6.1.3. Maintain and Operate the BAM and AHAS system. The contractor shall provide the necessary support to BAM and AHAS for management and production of bird hazard advisories, ensuring the advisories are available to aircrews within a minimum of 10 minutes. Bird Hazard Advisories shall include specific low-level airspace, MOA's, ranges, and airfields in the geographic region; disseminate historical hazards data through BAM, near-real-time bird hazard advisories through AHAS, monitor the system from 4:00am to 10:00pm Central Time Monday-Thursday and 4:00am to 6:00pm Central Time Fridays, and maintain off-site backup files for all issues and advisories

6.1.4. Validate Radar Risk Prediction. The contractor shall review and validate data collected from WSR-88D sites, utilizing available technology including but not limited to: electronic imagery, BDR data, thermal imagery, and/or visual observations. Annually, two on-site validations and a minimum of ten remote validations will be performed for locations covered by the AHAS system. At a minimum, one AHAS system validation will be executed each month.

On-site validation will include travel to an installation within the continental United States covered by AHAS. Or another desirable location that allows for ground proofing the system, and approved by the COR. Validation results shall be noted within the MSRs. Validation information collected and reported in the MSR will include: dates of validation, routes evaluated, data source used for verification, and outcome if validation is unconfirmed.

6.1.5. Maintain System Documentation. The contractor shall maintain BAM/AHAS user and system documentation, including: maintaining and updating instructions (annually) to enable military users access to the advisories on the web site and in a printable format (as requested). The contractor shall review BAM/AHAS user and system documentation within the first six months of the contract, updating and validating each document for effective use.

Cite the date of revision/review on all instruction documentation. User instructions shall be available by hard copy (upon request) and through online tutorials in the BAM/AHAS website. Additional revisions will be implemented based on need (e.g. if the user interface to BAM/AHAS is changed) or at the request of the COR.

6.1.6. Back up and Archive Data. The contractor shall archive NIDS data and AHAS bird hazard advisories each month, ensuring a record of historical data. Maintain this data indefinitely, or until approved by the COR or alternate COR. Backup and achieved data will be available to the USAF upon request by the COR.

6.1.7. Technical Assistance. The contractor shall provide technical assistance to the USAF on issues involving BAM/AHAS, including but not limited to: queries from USAF and Government officials for data on the system and performance; analysis of system design;

project planning; effects and recommendations for resolving issues resulting from changes in the USAF mission, policy, or directives; effects and recommendations for enhancements to the AHAS/BAM system based on the new technologies and software.

6.2. Technology Evaluation Task.

6.2.1. System Maturation. The contractor shall investigate and evaluate various options for technological improvements, including: coordinating system demonstration/evaluations, developing technology evaluation criteria, recommending the best solution to the USAF, taking into consideration system capabilities and functionality, AHAS system security, integration with USAF networks, user configurability, hardware requirements, technical support, training, user aids, and purchase, licensing, and sustainment costs.

6.2.2. Enhance and Upgrade AHAS. The contractor shall evaluate and maintain the effectiveness of AHAS site format by: recommending format improvements, making COR-approved modifications to the AHAS advisory format and/or distribution system, expand the current system to incorporate new parameters (e.g., new training routes and airfields as identified by USAF users and approved by the COR), and review current AHAS software.

The contractor will enhance AHAS software through development of new algorithms for weather suppression and distribution methodologies, retraining AHAS networks with processed data specific to each particular region. The contractor will evaluate new sources of weather data, modifying the AHAS model to enhance the quality of risk analysis, while reducing the need for physical data storage servers, migrating data storage into the USAF AWS system.

6.2.3. Enhance and Upgrade BAM. The contractor shall evaluate and maintain the effectiveness of the BAM site format by: recommending appropriate changes; make COR-approved modifications to the BAM advisory format and/or distribution system; expand current system to incorporate new parameters (e.g., new training routes and airfields as identified by USAF users and approved by the COR), and review current BAM software. The contractor will enhance BAM software to include: research and development of new components and capabilities for the BAM database to support new GIS Application capabilities, evaluate updated GIS databases and base data, incorporation of BDR and formal wildlife survey data (as available), recommend improvements (implemented as approved by the Government), and evaluation of new tools and methodologies that could be used to enhance the modeling techniques for BAM modules. The contractor will evaluate application of cloud data storage systems for the operation of BAM. The contractor will utilize USAF AWS cloud data storage systems, as appropriate and available without impacting the operational integrity of BAM. The BAM enhancements and upgrades shall be included in the MSR.

6.3. Education and Training Materials Task.

6.3.1. Training Materials and Presentations. The contractor shall maintain high quality, effective visual communication materials for education and training program courseware.

Educational outreach will include: interactive video conferencing (e.g., Microsoft Teams), internet-based training, and magazine articles. Annually, these materials shall be reviewed, updated, and verified for validity, consistent with paragraph 6.1.5. of this contract and in accordance with approvals by the COR. The contractor will ensure video teleconference capability with USAF units for instruction on use of BAM/AHAS, when requested and approved by the COR or alternate COR.

6.3.2. Bird Strike Committee USA Outreach. The contractor shall be prepared to travel to the Bird Strike Committee professional conference to present major changes to the bird hazard tool, training for BAM/AHAS, and capabilities of the system. Presentations shall cover software analysis advances and product changes to BAM/AHAS and the BDR technologies.

6.3.3. Topical Currency. The contractor shall communicate with AFSEC as needed to keep abreast of current areas of interest, especially safety. The contractor will modify the analysis focus, as necessary, to address these areas of interest with approval from the COR or alternate COR. The contractor should also maintain currency in areas that focus on but are not limited to: software upgrades and configuration, system/network development, capabilities, and functionality, system security integration, GIS applications, and modeling methodologies.

6.4. Development Tasks. The overall focus of this requirement area involves improving data collection and analysis development of automatic upgrades, website maintenance/sustainment, and system security. In particular, it involves the following areas:

6.4.1. System Improvements/Upgrades Task.

6.4.1.1. Data Collection and Analysis. Use of existing open-source legacy software, Commercial-Off-The-Shelf (COTS) products, and or a combination thereof shall be considered to the maximum extent practical in fulfilling the following requirements: add new/improved data sets into the analysis tool; remove outdated/inaccurate data; improve data download techniques and processing capability; and work on the development and configuration of customized data analysis solutions. The contractor will implement BAM/AHAS improvements to ensure the most accurate risk model development possible, including integration of BDR data into BAM (as available).

6.4.1.2. Develop Automated BAM/AHAS Updates. When requested by the government and authorized by the COR, develop automated updates of actual strike data reported within the Air

Force Safety Automated System (AFSAS). Updates must be compatible with BAM and AHAS interactions. Security requirements and assurance controls, as directed by the AFSEC ISSM and documented in EMASS, must be met when interfacing with AFSAS.

6.4.1.3. BDR Data Integration. The contractor shall integrate historical BDR data collected at USAF installations (as available), into the BAM/AHAS wildlife modeling database. The contractor is responsible for coordination with the COR to identify the data delivery method (i.e., submission over DoD SAFE, compact disc, other) and any formatting requirements for BDR data integration from each host BDR organization.

6.4.2. Website Task.

6.4.2.1. Accessibility and Sustainment. The contractor shall provide the software, methodology, and manpower necessary to operate and maintain the BAM/AHAS website. The site shall be publicly accessible and will include (at a minimum): general pages, unit-specific pages (as requested /approved by the COR or alternate COR), menus, and system tutorials/user guides. The contractor is responsible for obtaining and maintaining an ATO from the USAF to operate BAM/AHAS as a publicly accessible website.

The contractor shall provide user access to bird hazard data/information and host the required system. Provide the Uniform Resource Locator (URL) link to the Government to ensure compliance with EITDR Requirement CF03. At a minimum, the contractor will conduct quarterly transition testing from the primary BAM/AHAS Internet Protocol (IP) address to the backup IP address. An exception will be issued for complex technical issues when mutually agreed upon by the contractor and COR, if notified within 10 calendar days of the quarterly deadline.

6.4.2.2. Enhance and Upgrade BAM/AHAS Website. The contractor shall ensure a continual stream of data input into the AHAS system advisories no less than a minimum of 10 minutes. The contractor may recommend and implement enhancements to the website and provide online instruction to USAF units concerning use of the website with approval by the COR or alternate COR.

BAM/AHAS website availability shall be 24 hours a day, seven days a week. Scheduled maintenance on the web site or associated hardware/software will be performed during off-peak hours only after posting advanced online notice of the work to users. Website availability to users shall be not less than 97 percent each month, less scheduled maintenance, or other exemptions defined in the Summary Schedule of this PWS. Any scheduled maintenance shall be communicated to the COR at a minimum of 7 calendar days in advance.

An exception for complex technical issues can be issued when mutually agreed approval is established in writing with the Contract Manager and COR within 30 days from the date of the contractor request. Severe weather conditions, such as hurricane evacuations or other unforeseen emergency responses beyond the contractor’s control are exempt from technical deficiencies of the primary operating system, assuming backup system testing has been properly executed and functional. Document all system unavailability (planned and unplanned) in the MSR, along with corrective action for enhanced availability.

6.4.2.3. Hyperlink. The contractor shall include the DoD required website links on the BAM/AHAS website as instructed by the COR or alternate COR.

6.4.3. Software System Support Task

6.4.3.1. System Maintenance. The contractor shall provide system maintenance and support, including, but not limited to: application, file/database management, storage, AHAS system security, and communications. The contractor shall incorporate the necessary technical support and product upgrades for BAM/AHAS technology, ensuring availability and the most accurate risk models possible. BAM/AHAS system upgrades, including installation, testing, and debugging of software shall be included in the MSR.

The contractor is responsible for performing configuration management and operating on/off-site system backup systems. The contractor shall install all available software upgrades and patches on a monthly basis and include installation records in the MSR. At a minimum, backup integrity testing of off-site systems shall be accomplished at least once a month to ensure uninterrupted data output on the BAM/AHAS website. Monitoring off-site systems will be accomplished daily.

Off-site backup testing will be documented in the MSR, including: date of the test, duration, capability evaluation, and corrective action for backup system failures. The contractor shall maintain a protective anti-virus and firewall on the BAM/AHAS system to deter unauthorized entry into the programming code, approved by the COR and consistent with USAF requirements. External penetrations of the BAM/AHAS shall be investigated and resolved immediately. Report any system breach to the COR, and the AFSEC ISSM within 24 hours and then document on the MSR.

6.4.3.2. IT Support. The contractor shall evaluate hardware components, recommend improvements, and implement as approved by the COR; evaluate software packages used in processing and developing hazard advisories, recommend improvement and implement as approved by the COR; test, acquire, install, and configure hardware/software at the contractor site to ensure that all hardware components meet satellite data link requirements and data storage capabilities. The contractor shall answer technical questions about the BAM and AHAS systems; help customers troubleshoot errors, and monitor the system from 4:00am to 10:00pm

Central Time Monday-Thursday and 4:00am to 6:00pm Central Time Fridays, and maintain backup files for all issued advisories.

6.4.4. Sustainment Task. The contractor shall sustain and maintain all products delivered and deployed under this contract. Sustainment begins when the product achieves Full Operational Capability (FOC) and includes both software maintenance and sustainment. Maintenance is defined as the process of modifying a software system or component after delivery to correct faults, improve performance or other attributes, or adapt to a changed environment.

Sustainment is defined as the processes, procedures, people, materiel, and information required to support operation of the BAM/AHAS system. The contractor shall sustain and maintain the BAM/AHAS system and website under this contract to include all trouble-shooting, debugging, recoding, testing of repairs, complete installation of maintenance upgrades to fix discrepancies, development and deployment of all engineering change requests issued by the government, sustainment of security controls, maintaining configuration control of all software releases, maintaining and answering help desk emails, and updating all documentation as changes occur. Sustainment shall include incorporating Engineering Change Proposals (ECPs) initiated through feedback and/or requested enhancements.

7. Place of Performance. Work shall be performed at contractor facilities. Tasks performed at a Government facility will only occur during TDY projects. During fulfillment of TDYs, the Government will provide workspace for the contractor as needed and approved by the COR. Location of work at Government facilities will be identified by the COR as necessary. The COR or alternate COR will be notified of contractor work at a Government facility in advance. The contractor will utilize video teleconferencing whenever possible and practical, and in coordination with the COR or alternate COR.

8.1 Administrative Dismissal for Safety Reasons. The contractor will provide alternate work sites for personnel when local government organizations institute emergency declarations that would restrict normal workplace attendance. The contractor may authorize situational telework and other arrangements, consistent with the organizations policies. The contractor will notify the COR within 24 hours of emergency situations that would interrupt normal workplace attendance and impacts to the BAM/AHAS system. Preemptive utilization of backup BAM/AHAS sustainment systems will be utilized upon contractor recommendation and COR approval. Local emergency conditions include inclement weather (i.e., snow, tornados, earthquakes, hurricanes, etc.).

8.2. Travel and Per Diem. Travel and per diem shall be in accordance with the Federal Travel Regulation for the locations visited. U.S. Per Diem rates for the continental U.S. are located at the following website: http://www.defensetravel.dod.mil/site/perdiem.cfm.

a. Federal Travel Regulations prescribed by the General Services Administration for travel in the contiguous 48 United States.

b. Joint Travel Regulations Volume 2, DoD Civilian Personnel, Appendix A, prescribed by the Department of Defense for travel in Alaska, Hawaii, the Commonwealth of Puerto Rico, and the territories and possessions of the United States; Standardized Regulations, (Government Civilians, Foreign Areas), Section 925, "Maximum Travel Per Diem Allowances in Foreign Areas" prescribed by the Department of State, for travel in areas not covered in (a) and (b) above. The contractor shall retain supporting documentation, which shall be submitted with the applicable invoice, which includes travel expenses.

The contractor shall conduct necessary travel commensurate with the requirements of the mission and in accordance with good traffic management principles. When it is necessary to use air or rail travel, the contractor shall use coach, tourist class, or similar accommodations to the extent consistent with the successful and economical accomplishment of the mission for which the travel is being performed.

The contractor shall obtain approval from the COR or alternate COR prior to conducting travel under this contract. Travel may encompass, but is not limited to, activities such as:

• Attendance at the annual Bird Strike Committee USA Conference, hosted either in the United States or Canada each year.

• Validation trips annually. The location of each validation trip will occur at an installation within the United States. Or other desirable location that allow for ground proofing the system, and approved by the COR.

8. Safety Information Security. Contractors shall abide by the guidance in AFI 51-307, Aerospace and Ground Accident Investigations, Paragraph 1.15. (Safety Investigations) and AFI 91-204, Safety Investigations and Reports regarding the handling and protection of privileged safety information and shall sign nondisclosure agreements to be kept on file with the COR. The contractor will comply with any supplements or amendments to DoD and USAF Instructions within 30 days after notification by the COR, as applicable. DoD Instructions and AFIs are available online.

9. Records/Data/Hardware/Software and Documentation. All data, data rights, hardware, courseware, documentation, and systems associated with this effort shall be the property of the AFSEC and the U.S. Government. The contractor shall provide the government with unlimited data rights to all software and information developed under this http://www.defensetravel.dod.mil/site/perdiem.cfm contract and form and function data in accordance with contract data rights clause(s), Data Rights in General.

10. Quality Assurance and Performance Evaluation. The Government will continuously monitor and evaluate the contractor’s performance through intermittent inspections of the contractor’s quality control program, contract surveillance, and receipt of validated complaints from contract customers. Quality assurance for this contract follows the Quality Assurance Surveillance Plan (QASP). The QASP sets forth the procedures and guidance that the COR will use in evaluating the technical performance of the contractor in accordance with the terms and conditions of the contract. The QASP will be used as a Government document to enforce the inspection and acceptance of all PWS Deliverables.

The QASP describes the mechanism for documenting noteworthy accomplishments or discrepancies for work performed by the contractor.

11. Section 508 Accessibility Standards. The contractor will incorporate all applicable USAF Section 508 requirements over the entire period of performance. Section 508 requirements required by federal law but not observed in AF requirements will also be administered. The contractor will coordinate Section 508 changes with the COR.

12. Privacy and Privilege. Contractor employees may be exposed to data that is subject to the Privacy Act of 1974, Arms Export Control Act or the Export Administration Act of 1979, and Safety Privileged data. All contractor employees assigned to this contract shall be required to take appropriate action to prevent disclosure of this information. Contractor employees shall abide by the guidance in DoDI 6055.07, AFI 91-202, AFI 91-204, and AFI 33-332. Completion of non-disclosure statements will be required by on-site contractor employees to ensure information that is considered sensitive, proprietary, or privileged is not compromised.

• Required Training. No training is required currently. We reserve the right to require future training if necessary.

13. Services Summary.

Task PWS Paragraph Number

Performance Objective Performance Threshold

SS-1

Qualifications and Labor

Paragraph 5.1., 5.1.1., and 7.0

Maintain qualified personnel and labor reporting requirements for implementation of

BAM/AHAS

Performance is acceptable when:

- The contractor’s service delivery is fully staffed with qualified personnel consistent with PWS requirements.

- All contractor labor hours are annually reported in sam.gov, NLT 31 October of the subsequent FY.

Performance is unacceptable when:

- Contractor staffing shortfall is detected according to vacancy requirements of the PWS.

- All contractor labor hours are not reported in sam.gov by 31 October of the subsequent FY.

SS-2

Certification and Accreditation

(C&A)

5.1.4. Fulfillment of all

USAF C&A

requirements

Performance is acceptable when

- FOC status is attained within 90 calendar days of contract award start date and maintained uninterrupted.

Performance is unacceptable when:

- FOC status is not complete within first 90 calendar days of contract award start date, or,

- For a lapse in BAM/AHAS implementation due to unsecured ATO validation or other SAF/AAI requirements.

SS-4

Mission

Support Task and Technology

Evaluation

6.1.1., 6.1.4., 6.4.2.2., 6.4.3.1.

Fulfillment of all BAM/AHAS Mission Support requirements

Performance is acceptable when:

- Continual stream of data for hazard advisories NLT every 10 minutes.

- Website availability NLT 97 percent each month outside of scheduled maintenance.

- Off-site backup test is performed monthly with corrective action completed, as necessary.

- One AHAS system validation is performed each month.

- Two on-site validations are completed annually.

- Perform transition testing once every three months with corrective action completed, as necessary.

- Scheduled maintenance will be communicated to the COR at a minimum of 7 calendar days in advance.

Task PWS Paragraph Number

Performance Objective Performance Threshold

Performance is unacceptable when:

- Continual stream of data for hazard advisories exceeds 10 minutes.

- Website availability exceeds 97 percent each month outside of scheduled maintenance.

- An off-site backup test is not performed in a reporting month or necessary corrective action is incomplete.

- One AHAS system validation is not performed each month.

- Two on-site validations are not completed annually.

- Transition testing is not complete every three months, or corrective action is incomplete.

- Scheduled maintenance is not communicated to the COR within 7 calendar days in advance.

SS-6

System

Sustainment, Improvements, and Support

Tasks

6.1.5., 6.2.1., 6.2.2., 6.2.3., 6.3.1., 6.4.2.1., 6.4.4.

Fulfillment of requirements in identified paragraphs and other applicable PWS subparagraphs

Performance is acceptable when:

- Instruction and materials are maintained annually, and updated/validated within the first six months from the contract award start date.

- All COR-approved improvements and upgrades are documented in the MSR.

- Negative effects from changes to the BAM/AHAS system were not identified or corrected within 14 calendar days.

- Support actions for this task occur within 30 days from the date the COR request is made.

Performance is unacceptable when:

- Instruction and materials are not provided without 30 days prior notice to cancel or reschedule.

- Improvements and upgrades are not documented in the MSR, and,

- Changes that negatively affect the BAM/AHAS system were identified and not corrected within 14 days.

- Support actions exceed 30 days of the request date without prior COR approval

14. Delivery Schedule.

PWS

Task # Deliverable Title Format Number Delivery Date

5.1.3.1. Operational

Control Plan

(OCP)

Contractor Format

Single Electronic Copy to COR

Draft provided electronically by the kick-off meeting; non-compliance resubmission within 10 calendar days after return following the kick-off meeting.

5.1.3.2. Monthly Status

Report (MSR)

COR-

approved Format

Single Electronic Copy to COR

Monthly, submitted in conjunction with the invoice in Procurement Integrated Enterprise Environment, Wide Area Workflow.

5.1.4. Certification and

Accreditation

(C&A) Compliance eMASS

Annual

Inspection

In progress by award start date, reviewed bi-annually for fulfillment of new USAF requirements.

All documents shall be delivered in electronic media format. The format shall be a Microsoft Office software program or other replacement format, approved by the COR prior to delivery. All other products shall be delivered to industry standards reviewed and approved by the COR or through designated information systems. Inspection and acceptance of deliverables shall conform to industry standards unless otherwise specified.

For standard distribution of all deliverables, provide one copy of a transmittal letter without the deliverable to the CO and one copy of the transmittal letter with the deliverable to the Primary COR. An electronic message (i.e., email) is an acceptable form of transmittal letter.