Attach_1_PWS.pdf

Attachment 1 Performance Work Statement

PERFORMANCE WORK STATEMENT (PWS) FOR

AIRCRAFT DELIVERY INFORMATION SYSTEM (ADIS)

AND CORONET AIR REFUELING PLANNER (CARP)

SUSTAINMENT, OPERATIONS, AND MAINTENANCE

SUPPORT

FOR THE

AIR COMBAT COMMAND

AIR OPERATIONS SQUADRON

JOINT BASE LANLEY-EUSTIS, VA

Software Sustainment, Operations, and Maintenance Support

Name: Aircraft Delivery Information System (ADIS) and Coronet Air Refueling

Planner (CARP)

Organization: Air Combat Command Air Operations Squadron (ACC AOS)

Address: 22 Rickenbacker Rd. (Bldg 10), Suite A-108 Langley AFB, VA 23665

Executive Summary. This Performance Work Statement (PWS) identifies the requirements to support the Aircraft Delivery Information System (ADIS) and Coronet Air Refueling Planner (CARP) software applications managed by the Air Combat Command Air Operations Squadron (ACC AOS) Contracting Officer Representative (COR). The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items (including non-personal services) necessary to perform services as defined in this PWS except for those items specified as government furnished property and services. The Contractor shall perform to the standards described in this PWS.

1. PURPOSE. The purpose of this PWS is to provide sustainment, operations, and maintenance support for the Aircraft Delivery Information System (ADIS) and Coronet Air Refueling Planner (CARP) software applications managed by the Air Combat Command Air Operations Squadron (ACC AOS) Contracting Officer Representative (COR). The contractor will provide Information Technology support to the ACC AOS to perform software sustainment, operations, maintenance, and client support administrator (tier 1) support of ADIS/CARP.

2. SCOPE. ADIS and CARP are Command and Control (C2) programs that provide seamless planning, scheduling, execution, delivery, and analysis of combat aircraft deliveries during peacetime, crisis, contingency, and wartime operations. ADIS and CARP are powerful planning tools that present an integrated view of planning and scheduling transoceanic flight and delivery of combat aircraft. These unique systems provide capability to the DoD’s single, executive agent for the delivery of combat aircraft.

ADIS provides users real time status monitoring and updating capability for C2 of multiple transoceanic CORONET fighter ferry missions--it is also a repository of historical information of these missions. ADIS data elements include specific information of each aircraft delivery such as:

itineraries; number of, type of, and tail number of aircraft; unit and aircrew data; air-to-air refueling requirements; and other pertinent information. ADIS produces Air Tasking Orders, schedules, suspenses, and reports used by unit planning and financial staff as well as the ACC AOS commander and ACC staff. ADIS creates the CORNET request "Excel" files for import into AMC's Air Refueling Management System (ARMS) via the Consolidated Air Mobility Planning System (CAMPS) portal for the analysis and scheduling of tanker resources to provide aerial refueling support for the CORNET missions.

CARP uses/modifies/extends/enhances the Joint Mission Planning System (JMPS) framework, a Government Off-The-Shelf (GOTS) program, to provide unique planning capabilities to the ACC AOS in support of the organization's operational mission to plan, execute, and control the safe, transoceanic delivery of combat aircraft, worldwide, for the DoD and partner nations. CARP is a flight planning tool which provides capabilities to model the flight performance of a cell of multiple receiver aircraft (up to 8 per cell) with multiple aircraft configurations, refine multiple receiver air refueling requirements based on multiple Missed Refueling Base (MRB) and avoidance routing constraints, analyze the feasibility of routes based on varying wind conditions, and produce a variety of products (e.g., flight profiles) by merging mission data with configurable report templates.

ADIS and CARP enhance usability and minimize training requirements for users and systems personnel, using several industry standard Commercial Off The Shelf (COTS) products, and a consistent Graphical User Interface (GUI) “look and feel” across all user functions. ADIS and CARP application support may require stakeholders to interact with several different government and contract entities. The Contractor shall interact with these entities. ADIS and CARP software is complex and delivery of new functionality requires the contractor to mitigate system performance risk not only with regard to the new capability, but also with the legacy code and the possible unintended legacy code problems. The Contractor must ensure quality software is delivered. Risk mitigation plans and actions must be in place to address how end user, program management, and Government ADIS and CARP testers will be involved in development processes to insure the highest quality of software is delivered. In the absence of specific guidance, application interface design should follow industry and Air Force best practices when applicable. ADIS and CARP are hosted at Langley AFB, VA. An optional backup site will be determined and will be maintain under this contract as directed by the government.

3. REQUIREMENTS/DESCRIPTION OF SERVICES. The Contractor shall provide the ACC AOS with software maintenance, software performance improvements, software operation support, software configuration, software documentation, and software testing for ADIS/CARP components.

The Contractor shall follow the Software Change Requests (SCR) process, used by the Government.

3.1 Software Sustainment Support. The Contractor shall provide support for sustaining the current ADIS/CARP application capabilities. Application sustainment includes activities such as modifications of the software to support software deficiencies, fact-of-life changes, upgrades for obsolete GOTS/COTS software, and security vulnerabilities. The Contractor shall provide generalized software maintenance and support to including:

Integrate and troubleshoot software components, Assess and support remote access connections and deployed software, Monitor software performance during normal duty hours to prevent potential backlogs and to correct problems associated with installed software, Maintain and fine tune the integrity of necessary databases, and Isolate and diagnose degraded performance issues.

3.2 Software Performance Improvements/Modernization Support. The Contractor shall monitor, analyze, and evaluate software performance of application or systems to make recommendations for improved stability, accuracy, and throughput capability. As appropriate, the Contractor shall assist government personnel to prototype and/or test potential improvements and subsequently modify software components to implement those modifications approved by the government. The Contractor shall analyze existing squadron software code to identify and remove obsolete code that unnecessarily complicates or degrades processing efficiency.

Developed scripts or code shall be documented.

3.3 Software Operation Support. The Contractor shall provide technical expertise and assistance with issues related to operation of ADIS/CARP.

3.4 Software Configuration Management Support. The Contractor shall be tasked by the Government with SCRs that contain a description of required software modifications along with a priority level for accomplishment. Final implementation dates for SCRs will be coordinated between the COR and the PM.

The Contractor shall perform all software modifications in accordance with established government configuration control standards and procedures. The Contractor shall test the software developed product prior to operational implementation. The Contractor shall gain approval from the COR prior to implementing any new software in the operational environment.

3.5 Software/Hardware Reliability/Testing Support. The Contractor shall thoroughly test and assess impacts of software modifications on stability, performance, and accuracy.

3.5.1 The Contractor shall provide a Software Test Plan for Government approval for each SCR. Progress on each SCR and Software Test Plan shall be documented in the Monthly Status

Report. This test plan shall describe the types of testing for each major type of software component, such as analytical modules, user interfaces, or database interfaces.

3.5.2 The Contractor shall prepare and deliver, to the COR, a Software Test Report for each SCR that is completed and ready to be implemented. The Software Test Report will document results for each test identified in the Software Test Plan for that SCR. These test reports will be used by the COR and SME to ensure the modifications or enhancements fulfill the technical requirement for the change and the reliability of the software change. Upon Government approval the Contractor shall complete implementation of the SCR.

3.5.3 The Contractor shall update the existing Programmer’s Guide as required to maintain currency and accuracy. The Contractor shall update all documentation to accurately depict current algorithms and process flow, to include flow charts as required.

3.5.4 The Contractor shall conduct Information Assurance (IA) testing on GOTS software using Government approved, and furnished, testing software. The Contractor shall fix IA vulnerabilities during code scans and run the government approved IA testing software to verify IA compliance of the code. The Contractor shall assist Government personnel in securing certificate-to-field or authority to operate for GOTS software. Testing will ensure code availability, integrity, authentication, confidentiality, and non-repudiation.

3.6 Monthly Status Reports and Backup/Recovery Plans. The contractor shall prepare and deliver Monthly Status Reports (MSR). The Contractor shall also establish backup and recovery plans. The MSR shall include accomplishments during the monthly reporting periods to include information assurance testing of GOTS/COTS products, projected task schedules, and problems encountered during the reporting month.

4 CONTRACTUAL REQUIREMENTS

4.1 Period of Performance. The period of performance shall be for one (1) Base Year of 12 months and four (4) 12-month option years.

4.2 Place of Performance. The work shall be performed at HQ ACC AOS sites located on Langley

AFB, VA.

4.3 On-site Personnel. The Contractor shall provide three, on-site contract employees to accomplish the requirements of this PWS and ensure adequate availability of expertise.

4.4 Normal Hours of Operation. Contract employees shall be available during core government business hours (Mon – Fri, 0730-1630), excluding U.S. Federal holidays.

A Functional Help Desk will operate during normal duty hours, unless the COR directs a change to accommodate events such as installation support. Additionally, the contractor shall provide on-call functional support 24/7--technical support availability shall be 24/7 for high priority trouble tickets (historically about 24 times per year). For other COR-authorized situations, the Contractor may be required to work extended work weeks (EWW) over 40 hours may be required or provide surge support. Surge is used for supporting emergency mission critical software sustainment changes.

4.5 Security

4.5.1 Personnel Security. Contract employees shall be United States citizens and have an active Secret clearance at the time of contract proposal, in accordance with DD Form 254, “Contract Classification Specification”. Prior to personnel performing Cybersecurity activities, the Contractor shall obtain, and remain current with, technical and/or management certifications to ensure compliance with AFMAN 33-285 Cybersecurity Workforce Improvement Program, section 2.20 and DoD 8570.01-

M, Information Assurance Workforce Improvement Program (with all current changes), and as stipulated in the basic contract, Section H, Clause. All work will be conducted at the network level or below.

4.5.2 Information Security and Force Protection. The Contractor shall comply with DoD Manual 5200.1-R, DoD Information Security Program Regulation; DoD Directive 8570.1, Information Assurance Workforce Improvement Program; DoD Instruction 8500.2, Information Assurance Implementation; and DoD Directive 5400.11, DoD Privacy Program. The Contractor shall provide Information Security and Force Protection training specified in AFI 31-401, Information Security Program Management; AFI 10-245, Air Force Antiterrorism Standards, and applicable AFHSIO and local supplements. The Contractor shall participate in the sustained Information Security and Force Protection/Anti-terrorism training or include this training as part of their on-going security program. The Security Manager will evaluate the training posture of Air Force contract activities and operations.

4.5.3 Protection of System Data. Unless otherwise stated in the contract, the Contractor shall protect system design-related documents and operational data whether in written form or in electronic form 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 Intelligence Community approved External Certification Authority (ECA) and shall make use of at least 128-bit encryption.

The Contractor shall not install nor connect non-Government-owned computing systems or devices to Government networks without obtaining proper authorization from the appropriate IA Office and COR coordination. Non-Government-owned computing systems or devices include, but not limited to personal or Contractor-owned thumb drives (i.e. memory sticks, flash drives, universal serial bus (USB) drives, jump drives, pen drives), removable or external hard drives, personal digital assistants (PDA), personal computer memory card international association (PCMCIA) media, MP3 players, cellular phones, digital media, floppy disks, compact discs, digital video disk DVD burners, optical recordings, photo flash cards, laptops or any other devices that can store data.

Cyber Risk Management. The Contractor shall obtain, and remain current with, technical and/or management certifications to ensure compliance with AFMAN 33-285 Cybersecurity Workforce Improvement Program, section 2.20 and DoD 8570.01-M, Information Assurance Workforce Improvement Program. The majority of Contractor personnel shall be considered privileged users of DoD information systems for the purpose of Cybersecurity certification. The Contractor shall support C3MS compliance efforts with Risk Management Framework (RMF).

Tasks include:

In coordination with the COR, create or maintain artifacts required for the certification and accreditation of the system to comply with the Risk Management Framework process via the Enterprise Mission Assurance Support Service (eMASS). Support the portfolio management process by providing information necessary for the Program Office to update Enterprise Information Technology Database Repository (EITDR) IAW Federal Information Security Management Act (FISMA).

Ensure systems are in compliance with Security Technical Implementation Guides (STIGs).

Provide expert knowledge of policies and processes related to RMF and Computer Network

Defense (CND) implementations.

Provide engineering artifacts for A&A efforts as required and assist with A&A package updates or generation.

Ensure all information systems/major applications being modified receive their

DIACAP/RMF and are device agnostic. Ensure compliance with the DoD Mobile Development Strategy V2.0 dated May 2012.

Work in conjunction with the host base and assigned Information System Security Manager (ISSM) to identify and mitigate OS and software security vulnerabilities. Implement and ensure security preventive measures are fully functioning.

4.5.4 Information System/Application Cybersecurity Assessment. For those solutions that will not inherit existing network security controls, and thus integrate an entirely new application system consisting of a combination of hardware, firmware and software, system security assurance is required at all layers of the TCP/IP DoD Model. The Contractor shall ensure that all system/application deliverables comply with Public Law 111-383, DoD and AF Cybersecurity policy, specifically DoDI 8500.01, and AFI 33-200. To ensure that Cybersecurity policy is implemented correctly on systems, Contractors shall ensure compliance with DoD and AF A&A policy, specifically DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), and AFI 33-200 . The Contractor shall also support activities and meet the requirements of DoDI 8520.02, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, in order to achieve standardized, PKI-supported capabilities for biometrics, digital signatures, encryption, identification and authentication.

The Contractor shall ensure that all application deliverables comply with the Defense Information Systems Agency (DISA) Application Security & Development Security Technical Implementation Guide (STIG), which includes the need for source code scanning and analysis, the DISA Database STIG, and a Web Penetration Test to mitigate vulnerabilities associated with SQL injections, cross-site scripting, and buffer overflows. For those solutions that will be installed within the ACC AOS, and similar environments, and thus inherit existing network security controls, application security assurance is required at the Application layer of the transport control protocol (TCP)/ Internet Protocol (IP) DoD Model. The Contractor shall also support activities and meet the requirements of DoDI 8520.02 in order to achieve standardized, PKI-supported capabilities for biometrics, digital signatures, encryption, identification and authentication.

The Air Force Network Operations Center (AFNOC), established by AFR 205-16, issues advisories to identify known vulnerabilities in computers and computer networks. These advisories include but are not limited to Information Assurance Vulnerability Alerts, Virus notification, Advisory Compliance Messages (ACMs), Bulletins and Follow-Up Messages as in defined in CJCSM 6510.01B.

The Contractor shall report suspected vulnerabilities and security incidents IAW AFSSI 5021. The Contractor shall implement, after COR approval, the countermeasures identified by the advisory within the timeframe specified by the advisory or as specified by the COR. If the countermeasures cannot be implemented, the contractor shall document the inability and must receive approval from the Designated Approving Authority (see AFI 33-202) and the COR for either an alternative corrective action or to continue operations without the countermeasures. If alternative corrective action is approved, the contractor shall implement this action within the timeframe specified by the COR.

4.5.5 Mission Assurance. The Contractor shall provide security and information assurance support, protecting information and information systems, and ensuring confidentiality, integrity, authentication, availability and non- repudiation. The Contractor shall provide application services support for Certification and Accreditation (C&A) processes, DIACAP processes, SISSU processes, Enterprise Information Technology Data Repository (EITDR) certification or ICD 503.

4.5.6 Testing. The Contractor shall conduct rapid testing and deployment of Core Data Services and Aggregation and Presentation Layer Services using distributed testing environments. The Contractor shall develop dynamic testing environments to support C&A and functional testing. For mission systems and Secret networks, the contractor shall perform testing IAW standards, policies and guidelines identified in the contract/PWS.

4.5.7 Test Lab. When requested and specified in the PWS, the Contractor shall establish and maintain a system integrated test lab that is capable of supporting a full range of integration test activities for both the currently fielded system as well as maintenance/modernization releases.

The currently fielded system includes the most current version and up to three previous versions for products that have not yet been declared ‘end of life.’ The contractor shall support test activities in areas which include, but are not limited to, product testing (regression testing and new capability testing), operational scenarios (real world simulation testing considering system topology and concept of operation, disaster recovery, clustering, and load balancing), stress and longevity (throughput, speed of service, and duration), interoperability, security (VPN, Firewall, security configuration of products and operating systems, and CAC Middleware testing), usability, transition (upgrade paths), and packaging/installation.

4.5.8 System and Network Authorization Access Requests. 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.

4.5.9 Access to Government Facilities with Controlled or Restricted Areas. Contractor must comply with security regulations imposed by the installation commander and/or the agency responsible for the project location. Due to specific mission requirements inherent in the nature of controlled or restricted areas on Air Force Installations, the Government may direct Contractor to leave the controlled or restricted areas at any given time.

4.5.10 Intellectual Property Protection. At the completion of the contract or when turning-in Government IT equipment to the Government, the Contractor shall not remove, change, or manipulate data, files, computer code, operating systems, and other information residing on any Government owned/provided storage media, without the expressed written authorization by the Contract Officer (CO) or the COR. This requirement is invoked whether the data, files, etc. are placed there by the Contractor employees in course of Contractor performance or otherwise provided by the Government or the Contractor. Also, in no case shall the Contractor u s e any method to destroy or remove data on a Government-owned storage media to a point that it is not easily recoverable using operating system data recovery tools, without expressed written permission from the Government.

4.5.11 Safeguarding Classified and Unclassified Information. The Contractor shall comply with the DD Form 254, DoD Contract Security Classification Specification, which includes meeting Air Force standards for storing, processing, and handling classified information and systems.

Additionally, all resources (e.g., maps, publication/instructions, photos) provided by the Government to assist the Contractor in the performance of the contract shall be surrendered to the COR or other government employee designated by the COR, upon termination of employment or the end of the contract performance period.

4.5.12 Classification Security. Individuals performing work under this PWS shall comply with applicable program security requirements as stated in the contract. A Secret Security clearance is required for any individuals supporting the contract. .\Contractors shall be able to obtain adequate security clearances prior to performing services under the contract. The Contract Security Classification Specification (DD Form 254) will be included in the contract and will encompass all security requirements. All contractors located on military installations shall also comply with Operations Security (OPSEC) requirements as set forth in DoD Directive 5205.02, Operations Security Program and AFI 10-701, Operations Security. 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).

4.5.13 Transmission of Classified Material. The contractor shall transmit and deliver classified material/reports IAW the National Industrial Security Program Operating Manual (DoD 5220.22- M). These requirements shall be accomplished as specified in the contract.

4.5.14 Non-Disclosure Requirements. The Contractor shall execute non-disclosure agreements before the Contractor obtains or is provided Government “For Official Use Only” and/or classified information and/or when the Contractor obtains or is provided information from other Contractors, firms not having Government contracts, academic institutions, and other not-for-profit organizations. The Contractor agrees to enter into company-to-company agreements (1) to protect another company’s information from unauthorized use or disclosure for as long as it is considered proprietary by the other company, and (2) to refrain from using the information for any purpose other than that for which it was furnished. For informational purposes, the Contractor shall furnish copies of these agreements to the COR. These agreements are not intended to protect information available to the Government or to the Contractor from other sources and are furnished voluntarily without restriction. This restriction shall be included in all subcontracts, teaming arrangements, and other agreements calling for performance of work.

4.6 Training. Contractor personnel are required to possess the skills needed 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 to this contract.

4.6.1 Government-Provided Training. Contractor employees may participate in other Government provided training, under the following circumstances:

The Contractor employees’ participation is on a space-available basis, The Contractor employees’ participation does not negatively impact performance, The Government incurs no additional cost in providing the training as a result of the Contractor employees’ participation, and Man-hours spent as a result of the Contractor employees’ participation in such training are not invoiced to contract.

4.6 Software Support and Data Rights. 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 Government obtains “unlimited rights” to all computer software, software source code, computer software documentation, enhancements, and technical data developed under this PWS. “Unlimited rights” means rights to use, modify, reproduce, release, perform, display or disclose in whole or in part, in any manner and for any purpose whatsoever, and to have the ability to authorize others to do so.

The data rights ownership/licensing guidance are specified in applicable DFARS references.

4.7 Section 508 of the Rehabilitation Act. 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, and (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.8 Organizational Conflicts of Interest. The Contractor personnel performing work under this contract may perform evaluation services which may create an Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer (CO) immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the CO to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the CO and in the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the CO may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

4.9 Program Management/Project Management. The Contractor shall identify a contract Program Manager or a Project Manager ( P M ) who shall be the primary representative responsible for all work awarded under this contract. The PM shall participate in Program/Project Management Reviews and ensure compliance with all standards referenced herein.

4.10 Contract Management. The Contractor shall establish and provide a qualified workforce capable of performing the required tasks. 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 efforts with an emphasis on cost-efficiency, schedule, performance, responsiveness, and consistently high-quality delivery.

4.11 Records, Files, and Documents. All physical records, files, documents, and work papers, provided and/or generated by the Government and/or generated for the Government in performance of this PWS, maintained by the Contractor which are to be transferred or released to the Government or successor Contractor, shall become and remain Government property and shall be maintained and disposed of IAW AFMAN 33-363, Management of Records; AFI 33-364, Records Disposition – Procedures and Responsibilities; the Federal Acquisition Regulation, and/or the Defense Federal Acquisition Regulation Supplement, as applicable. Nothing in this section alters the rights of the Government or the Contractor with respect to patents, data rights, copyrights, or any other intellectual property or proprietary information as set forth in any other part of this PWS or the contract of which this PWS is a part (including all clauses that are or shall be included or incorporated by reference into that contract). The Contractor shall manage all data created for Government use or legally controlled by the Government, in support of the functional activity or required by AF publication, IAW with the AF Records Management procedures in AFI 33-322, AF Manual 33-363, and AFI 33-364 (or subsequent replacements).

4.12 Safety. The Contractor shall comply with the latest applicable Federal, State, Air Force, Air Mobility Command, and Installation, regulations, instructions, policies, management plans, and requirements regarding personnel health, occupational and operational safety. The COR shall provide copies of p u b l i c a t i o n s not available on the web and updates as they become available.

4.13 Staffing. The Contractor shal l provide quali f ied personnel at contract start that meet or exceed the stated quali f ications . The Contractor shall ensure the continuation of services during prolonged personnel absences due to sickness, leave, and voluntary or involuntary termination from employment such that impact to the Government is minimal. Once a Contractor has knowledge that an employee will be unable to perform IAW with this PWS, either temporarily or permanently, the Contractor shall provide written notification to the CO and COR within three (3) business days. Notification shall include the date position will be vacant, anticipated replacement date, and what Contractor management corrective action will be taken to ensure task continue performance IAW this PWS.

4.13.1 Vacancies. Vacancies shall not exceed fourteen (14) calendar days unless directed or approved, in writing, by the CO. Failure to fill employee vacancies beyond a two week period will result in a price reduction. The price reduction shall be calculated by the Contractor and reflected in subsequent monthly invoices until the position is filled. If it should become necessary to substitute or replace personnel for those originally assigned, the Contractor shall provide the names, experience, and qualifications of personnel selected to perform under this contract to the COR.

4.14 Certifications/Qualifications. The Contractor shall provide labor personnel with experience in software development, software maintenance, web application development, web application maintenance, and configuration management. Contractor personnel shall:

Be familiar with the USAF’s CSA program and be able to obtain the necessary permissions to perform these functions as required.

Have knowledge of Microsoft’s Windows operating systems.

Be familiar with new operating systems offerings as they are released from the vendor.

Possess the ability to troubleshoot and replace components for desktop systems, laptops, and uninterruptable power supplies.

Have experience in Java, JavaScript, C, C++, Microsoft .Net/C#, Windows scripting, JQuery, SQL, PL/SQL, and JMPS architecture framework. Familiarity with Distributed Interactive Simulation (DIS) and High Level Architecture (HLA) protocols is desirable.

Have a minimum of one (1) year experience with ADIS or CARP in the last five (5) years.

5. PERFORMANCE SUMMARY

The Contractor’s performance will be assessed by measuring success towards achieving defined performance objectives. The Services Delivery Summary (SDS) will be in accordance with AFI 63- 101, Acquisition and Sustainment Life Cycle Management, AFI 10-601, Capabilities-Based Requirements Development and FAR Subpart 37.6, Performance-Based Acquisition. The SDS and the Contractor’s Quality Control Plan (QCP) provide information on contract requirements, the level of Contractor performance, and the expected method of government validation and confirmation of services provided.

Services Delivery Summary

Performance Objective

PWS

Reference Performance Threshold

1 Modify software or interfaces of operational applications or systems.

3.1 Implemented no later than (NLT)

coordinated completion date

2 Complete all assigned SCRs within the established completion date.

3, 3.4 100% compliance

3 Isolate, diagnose, and fix causes of degraded performance of critical software components.

3.1 NTE 2 failed attempts

4 Test and assess impacts of software modifications on stability, performance, and accuracy in accordance to test plan.

Implement software fixes/enhancements that are accurate, complete and tested according to the test plan.

3.5, 4.5.6 100% compliance

8 Administer security measures, patches & procedures to enable authorized customers access to data

4.5.2, 4.5.3, 4.5.4, 4.5.5

100% compliance

9 Design and validate information backups and recovery procedures to prevent data loss

3.6 100% compliance

10 Provide qualified people at contract start

4.13 Performance is acceptable when

qualified personnel are on the job at contract start, unless previously negotiated by the CO

11 Effectively replace/substitute personnel 4.13.1 Vacancies are filled with qualified personnel within 14 calendar days of vacancy, unless approved in writing or otherwise directed in advance by the CO and there is no mission impact due to position vacancies or unqualified personnel

5.1 COR Designation. The CO will provide the Contractor with a COR Designation Memorandum to inform them a COR has been designated to the contract.

5.2 Performance Evaluation. Contractor performance is subject to Government COR surveillance to ensure PWS compliance. The Contractor shall comply with the following:

The Contractor shall permit the CO or authorized representative access to all work areas, records, and data used in the performance of the contracted services. The Contractor shall provide support, and not interfere with the CO, CORs, state, federal, and other designated personnel in the performance of their official duties. Access shall be provided as soon as possible, but not to exceed one (1) workday after the request.

Identify and control non-conformances through root cause analysis, corrective actions, and preventive actions. Focus on eliminating the cause to prevent reoccurrence.

Maintain records of non-conformities and actions taken. Correct and provide response to all Government-identified non-conformances IAW time frames specified by the CO. This contract identifies two types of non-conformances: Minor and Major.

o A minor non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. It normally does not increase risk to the Government.

Minor non-conformances are typically low risk and are communicated through notices; first notices are issued for any identified non-conformance, second notices are issued for repeat non-conformances or failing to correct issues within a reasonable amount of time. Upon receipt of a non-conformance notification (first or second notice), the Contractor shall complete applicable sections and return it to the CO within time constraints directed by the CO in the notice. A formal corrective action plan is not required for notices.

o A major non-conformance is a non-conformance that adversely impacts (or has the potential to impact) mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. This type of nonconformance increases risk to the Government and therefore has a risk assessment rating of moderate or high. An example of increasing risk would be a significant number of recurring non-conformances, which is an indication of inadequate preventive measures/actions and lowers the Government’s confidence that the Contractor can provide quality services on time and within costs. The CO will communicate major non-conformances on a Corrective Action Request (CAR) form with a suspense date for the Contractor’s corrective action plan. As a minimum, the Contractor’s corrective action plan will address: action taken to fix the immediate problem, root cause analysis of the problem to determine cause, corrective action on the cause of the problem, and actions taken to prevent recurrence.

5.2 Multifunctional Team Meetings. The COR, Contractor (or representative), Contract Specialist/Manager (CS/CM), and CO will meet as necessary to discuss contract performance, resolve issues, discuss customer complaints, and provide positive interaction and feedback to all parties. Any party may request a meeting when necessary. Written minutes of any such meetings shall be recorded by the Contractor and sent to the CO, COR, and CS/CM within five (5) workdays following the meeting.

If a party does not concur with any portion of the minutes, such nonoccurrence shall be provided in writing to the CO within ten (10) calendar days following receipt of the minutes.

6. Property Incidental to the Place of Performance/Services.

The Government will provide or make available at the worksite a furnished work space for each contract employee including:

Workstation with desk and chair Desktop computer w/ dual monitors and necessary software for daily operations Desktop and monitor for software/system development/testing Telephone Color printer

No alterations to the work space shall be made without the specific written permission from the COR and the CO as coordinated and approved via the Civil Engineer work order. In case of alterations necessary for compliance with OSHA, such permission shall not be reasonably withheld. The Contractor shall return the office space to the government in the same condition as received, except for fair wear and tear and approved modifications.

6.1 Physical Property Protection. Property protection for facilities where the Contractors’ primary work center is located will be the responsibility of the local facility manager and local Government Security Manager, or their duly authorized representative IAW AFI 31-101, Integrated Defense, and command/local directives. The Contractor shall safeguard all Government-owned equipment and materials in his/her possession or use.

6.2.1 The Contractor shall establish and implement methods to ensure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. Keys issued to the Contractor by the Government shall NOT be duplicated. The Contractor shall immediately report any occurrences of lost or duplicate keys to the COR.

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

7. DELIVERABLE(S) SUMMARY.

The Contractor shall provide contract deliverables in a format mutually agreed upon by the Government and the Contractor. All deliverables will be reviewed for timeliness, accuracy and format. If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last work day prior to the due date. Unless otherwise specified, documents will be delivered in electronic format using the Microsoft Office Suite of applications.

PWS

Reference

Data Item Description Frequency

3.5 Software Test Plan Five (5) work days after SCR is assigned.

3.5 Software Test Report Five (5) work days after the conclusion of each test.

3.6 Monthly Status Report Six (6) calendar days after the month being reported.

5 Quality Control Plan Ten (10) calendar days after contract award

5.2 Meeting Minutes Five (5) work days after meeting.

8. TRANSITION PLAN: The purpose of this transition plan is to prevent mission degradation due to the transition from the previous contract. To mitigate transition risk, new hires must be identified as early as possible but NLT 15 January 2017.

8.1 Transition In. If required due to a change in personnel, the transition period will be 60 calendar days for Contractor personnel. This allows time for Contractor key personnel to process and obtain required ID/CAC cards, computer system access requests, and receive workplace and task orientation to ensure the entire team is in place for period of performance start, in order to fulfill this TO. Any remaining days of the transition period can be spent receiving briefings on specific duties and responsibilities Contractor personnel will be expected to accomplish to fulfill this TO. The Contractor shall provide a Hiring Status Report (HSR) until all positions are filled.

8.2 Transition Out. Prior to the end of the TO period of performance, the incumbent Contractor shall support a 60 calendar day transition period with incoming personnel. During this period, all programs, information, data, etc. will be passed from the incumbent Contractor to the incoming Contractor so that there is no break in mission support.

9.0 Contractor Manpower Reporting. In accordance with Section 8108 of Public Law 112-10 of the Department of Defense and Full-Year Continuing Appropriations Action, 2011.

9.1 The Contractor shall report ALL labor hours required for performance of services provided under this contract via the secure Contractor Manpower Reporting Application (CMRA) data collection site. The Contractor is required to completely fill in all required data fields at:

http://www.ecmra.mil (Department of Air Force CMRA Portal). Reporting inputs shall be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported anytime during the FY, all data shall be reported not later than 31 October of each calendar year. The Contractor may direct questions to the CMRA help desk. The prime Contractor is responsible to ensure all subcontractor data is reported.

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

9.3 User Manual. Data for the AF services requirements must be input at the AF CMRA link.

However, user manuals for Government personnel and Contractors are available at the U.S. Army CMRA link at http://www.ecmra.mil.

9.4 Subcontractor Input in CMRA. Prime Contractors are responsible to ensure all subcontractor data is reported. Subcontractors will not be able to enter any data into CMRA, but will enter their information into a Bulk Loader spread sheet available from the AF CMRA helpdesk. Subcontractor shall fill in columns A-C then return it to the AF CMRA helpdesk after it's completed and a technician team will enter the information into CMRA.