RFP_Atch_1_PWS.pdf

i

PERFORMANCE WORK STATEMENT (PWS)

ADVANCED COMPUTER FLIGHT PLAN (ACFP)

APPLICATION SUPPORT

28 Aug 2013

Table of Contents

1. Description of Services

1.1. Background

1.2. Scope of Work

1.3. Specific Support Services

1.4. Deliverables

2. Services Summary

3. Government-Furnished Property and Services

3.1. Government-Furnished Property

3.2. Government-Furnished Services

3.3. Property Protection

4. General Information

4.1. Place of Performance

4.2. Retention of Contractor Personnel

4.3. Quality Control Plan

4.4. Government Quality Assurance

4.5. Access to Government Automated Information Systems

4.6. Security Management

4.7. Program Management Assistance

4.8. Handling and Safeguarding Classified Information

4.9. Contractor Access

4.10. Highest Security Clearance

4.11. Network and Computer Security

4.12. Information in the Contractor Possession

4.13. For Official Use Only Information

4.14. Privacy Act

4.15. Contractor Consent to Background Checks

4.16. Proper Employee Credentials

4.17. Information Assurance

4.18. Antiterrorism Level I Training

4.19. Safety Requirements

4.20. Contractor Personnel Training

4.21. Travel Expense and Other Direct Costs Reimbursement

4.22. Non-Disclosure Agreements

4.23. Identification of Non-Disclosure Requirements

4.24. Protecting Government Intellectual Property

4.25. Data Rights

4.26. Organizational Conflict of Interest

4.27. Contractor Manpower Reporting

ii

4.28. Transition Period

Appendices Appendix 1. Government Furnished Equipment

Appendix 2. ACFP Hardware

Appendix 2. ACFP v4.5 Baseline Software

Appendix 3. Non-Disclosure Agreement

1.0 DESCRIPTION OF SERVICES

1.1 BACKGROUND.

The Headquarters Air Mobility Command, Directorate of Communications and Information, Mobility

Systems Division (HQ AMC/A6I) has responsibility for program management of AMC Command and

Control (C2) programs. HQ AMC/A6I acquires, deploys, and maintains the hardware, systems software, and applications software for AMC C2 applications. On October 1, 1995, AMC was designated as the lead command and assumed program management responsibility for the acquisition and development of the Advanced Computer Flight Plan (ACFP) system.

ACFP is AMC‟s primary automated aircraft flight planning system, used worldwide by AMC and other

United States Air Force major commands during peacetime, crisis, contingency, and wartime operations.

The system provides fuel and time optimized computer flight plans using an online system of track libraries, international navigational aids library, remote terminal request and dissemination procedures, and current weather forecasts.

ACFP V4.x consists of Oracle/Sun server hardware with Solaris as the operating system, an Oracle

Relational Database Management System (RDBMS), and Intel based Windows 2003 servers. The application source code is written in C++ and C#. ACFP Client Software (Request Input Manager - RIM, and Request Segment Builder - RSB) runs on Windows Vista and Windows 7.

1.2 SCOPE OF WORK.

This PWS describes the efforts and tasks that shall be performed by the contractor for HQ AMC.

AMC/A6I has embarked upon a division-wide process improvement initiative using the Software

Engineering Institute (SEI), Capability Maturity Model Integration for Acquisition (CMMI-ACQ) as the model baseline in its efforts to improve overall program management of software releases and program support/integration. In accordance with (IAW) tasks delineated in this PWS, the contractor shall provide

ACFP Application Support. The following areas apply to this PWS:

Requirements Analysis

Custom Application Development

Test and Evaluation

Security Engineering Supporting Certification and Accreditation

Web Services

Operations Support

Software

Managed Services

1.3 SPECIFIC SUPPORT SERVICES.

Throughout the duration of this contract, the contractor shall perform the following tasks:

1.3.1 TASK 1 - PROGRAM MANAGEMENT.

The contractor shall plan, direct, coordinate, and control the project as necessary to effectively and efficiently accomplish all requirements contained in this PWS. This effort shall be consistent with this

PWS, referenced documents, and government-approved plans, schedules, and milestones. The contractor shall ensure any joint contractor, subcontractor, or vendor products and services satisfy the requirements of this PWS and are properly integrated in compliance with all aspects of the contract. The contractor shall provide the technical and functional activities at the contract level needed for the program management of this PWS.

The contractor shall meet stated government requirements and milestones and must advise the

Contracting Officer‟s Representative (COR) as soon as possible whenever requirements and milestones cannot be met. Actual or projected failures to meet contract or PWS requirements, milestones, and systems requirements shall be orally reported to the COR as soon as the contractor becomes aware of the information/potential problems and shall document the issues in the appropriate periodic reports, test reports, and review minutes. Contractor proposals for corrective action shall also be provided for all reported actual or projected system failures. The Program Management effort shall continue for the entire term of the contract.

1.3.1.1 Subtask 1-1 – Monthly Contractor Progress, Status/Management Report, Project Schedule, Trip

Report, Task Management Review (TMR) Agendas, Minutes, and Action Items.

The contractor shall provide to the COR and the Contracting Officer (CO), a monthly Contractor Progress

Status/Management Report {Contract Data Requirements List (CDRL) A001}. The report shall be submitted via email and is due by the 5th workday of each month. The report shall contain the following information:

Contract number, contractor name, period covered by report

Contract summary consisting of the cumulative funds expended, percentage of funds spent to date, total hours expended for the report period by labor category, hours expended on the contract on a cumulative basis by labor category, cumulative travel costs incurred, cumulative material/subcontracting costs incurred

Budget allocations and completion dates per task

Budgeted dollar amounts versus man-hours expended per task

Percentage completion for each task in relation to the budgeted amount of work completed during the report period

Funds expended during report period and cumulative per task

Hours expended for the report period by labor category and cumulative per task

Subcontracting expenditures during report period and cumulative amount per task

Summary of travel taken per task during the report period, to include each trip, the people who traveled, places traveled to, dates of travel, the purpose of the travel, and amount expended during the report period as well as cumulative

Summary description of activities and accomplishments during the report period, description of problems and issues encountered during the report period, status of open problems or issues identified in previous report(s)

In addition, the contractor shall provide and maintain a current Project Schedule (CDRL A002), electronically accessible by the AMC ACFP Program Management Office (PMO) and compatible with

Microsoft Project/Project Server. The schedule is due no later than the 10 th calendar day of each month or within ten days of notification of new software modifications. The schedule shall include, as a minimum, major tasks and subtasks (including releases, deliverables, etc); duration; planned and actual start and finish dates; and planned and actual resources (to include hours and costs). The schedule shall reflect established milestones and provide an explanation for any deviations from the schedule and/or adjustment to be implemented to recover. Delivery will be by Project Web Access (PWA) or via email if PWA is not available.

The contractor shall participate in a quarterly TMR in the local Scott Air Force Base (AFB) area as directed by the COR. The contractor shall address program and contract progress on tasks accomplished during the quarter, in addition to reviewing the monthly status report. Agenda items shall include high level action items, funding status, and any new action items/issues identified by the government or the contractor. Key contractor personnel shall attend and participate. Agenda and presentation material for each Interchange meeting (IM) is due no later than (NLT) 24 working hours prior to the meeting, drafts of minutes are due within 5 workdays following meeting, and final minutes are due within 10 workdays following meeting (CDRL A004).

Deliverables: Monthly Contractor Progress Status/Management Report (CDRL A001)

Project Schedule (CDRL A002)

Agendas, Presentation Material, Minutes, and Action Items (CDRL A004)

1.3.1.2 Subtask 1-2 – Interchange and Technical Meetings.

Interchange meetings revolve around technical or functional issues and may be requested by the COR or by the contractor. The contractor shall conduct IMs as approved by the COR and shall develop the meeting agenda/presentation material (as necessary) and coordinate the date, time, and place of the meeting (CDRL A004) jointly with the COR. The contractor shall provide agenda and presentation material as necessary for each IM no later than 24 working hours prior to the meeting and shall document the results of each IM in minutes (CDRL A005). Draft of minutes shall be submitted to the COR via e-mail within 5 workdays following meeting; final minutes within 10 workdays following meeting.

The contractor shall also participate in technical meetings and reviews separate from IMs but shall not be required to produce meeting minutes unless mutually agreed upon in advance between the contractor and

COR. Each time the contractor plans to conduct meetings with other contractors, ACFP users, or functional representatives, the contractor shall obtain the government COR approval orally or via electronic mail.

Deliverables: Agendas and Presentation Material (CDRL A004)

Interchange Meeting Minutes and Action Items (CDRL A005)

1.3.1.3 Subtask 1-3 – Equipment Inventory.

The contractor shall appoint an Equipment Custodian (EC). All C2/In-transit Visibility (ITV) program equipment provided by Scott AFB to include Government Furnished Equipment (GFE) shall be maintained and accounted for by the EC as directed by the ACFP COR. The EC shall comply with all instructions and regulations provided by the Scott AFB Equipment Management office (375 CS/SCBCE).

The EC shall verify all equipment is accurately listed in the Information Technology Asset Management system and work closely with the ACFP System Manager and the Base EC Officer. The contractor shall provide the initial inventory data (CDRL A006) to the ACFP System Manager and/or ACFP equipment custodian within ten working days after receipt of inventory with subsequent reports due every 30 workdays thereafter and the final report due five workdays before contract completion.

Deliverables: Government Property Physical Inventory Report (CDRL A006)

1.3.1.4 Subtask 1-4 – Management Plan.

The contractor shall submit a Management Plan, as outlined in CDRL A009, which succinctly describes the approach the contractor will use to perform all PWS tasks and other contract requirements. The contractor shall ensure that the plan provides the information necessary for the government to assess the soundness of the contractor‟s approach. Draft Management Plan is due with proposal. Final

Management Plan is due five workdays after award. Revisions to Management Plan are due ten workdays after each modification.

1.3.1.4.1 KEY PERSONNEL.

The contractor must identify the following key personnel in the management plan.

1.3.1.4.1.1 Contractor Program Manager.

The contractor shall provide the name of a Contractor Program Manager (CPM) to the COR in writing.

In the event the contractor‟s primary program manager is unavailable, the contractor shall notify the COR of a point of contact (POC) to take on the primary CPM‟s responsibility.

1.3.1.4.1.2 Contract/Business Manager.

The contractor shall provide the name of Contract/Business Manager who shall be the POC for contracting issues, billing/payment, and related business matters. In the event that the contractor

Contract/Business Manager is unavailable, the COR and the CO shall be notified of the alternate POC.

1.3.1.4.1.3 Chief Engineer.

The contractor shall provide the name of a Chief Engineer (CE) to the COR in writing. In the event the contractor‟s primary CE is unavailable, the contractor shall notify the COR of a POC to take on the primary CE‟s responsibility.

1.3.1.4.1.4 Chief Quality Assurance Lead.

The contractor shall provide the name of a Chief Quality Assurance Lead (CQAL) to the COR in writing.

In the event the contractor‟s primary CQAL is unavailable, the contractor shall notify the COR of a POC to take on the primary CQAL‟s responsibility.

Deliverables: Management Report (CDRL A009)

1.3.1.4.1.5 Local Representation.

The contractor shall have personnel, located within a 50 miles radius of Scott AFB, with sufficient management authority to represent the contractor during meetings, conferences and working groups.

1.3.1.5 Subtask 1-5 – Configuration Management Plan.

The contractor shall deliver with its proposal a Configuration Management (CM) Plan (CDRL A010) describing the contractor's CM program, how it is organized, how it will be conducted, and the methods, procedures and controls for effective configuration identification, change control, status accounting, and audits of the total configuration, including hardware, software, and firmware. Draft CM Plan is due with proposal. Final CM Plan is due to COR 20 workdays after contract award.

Deliverables: Configuration Management Plan (CDRL A010)

1.3.2 TASK 2 - SOFTWARE MAINTENANCE.

The contractor shall provide all software maintenance and software modernization for the ACFP system, as prioritized within a Release Specification Agreement (RSA). The RSA is a document recording agreement between program and functional communities as to the content of a release and release schedule. The RSA outlines any risks associated with the release agreement and contains the Release

Specification (RS) as an attachment which lists the agreed-upon content and additional details of the release. The RSA shall be developed and coordinated by the PM and signed by Functional Community

Representative(s), the PM, testing or support contractor and release developer. The RSA is then signed by the A6I as the final approving authority. The RS articulates the requirements of a release. The RS contains a list of all CRs to be included in the release, the current system baseline on which the release will be developed, and release schedule milestones. The RS, as approved by the RSA, becomes the defining criteria for the development process. Software maintenance activities consist of:

I. Maintaining or enhancing the capabilities of the ACFP environment to include such items as listed below to comply with evolving AMC, civilian and military aviation authority airspace requirements and external system evolution as they relate to flight planning and as prioritized by the ACFP PMO and AMC functional manager within an RSA.

a. Maintain compatibility with external data sources for navigation and weather data

b. Maintain compatibility with the Common Route Definition (CRD) custom interface to the external Portable Flight Planning Software (PFPS)

c. Maintain the Worldwide Aeronautical Route Planner (WARP) software) optimization engine

d. Maintain ACFP windows client flight planning software

e. Maintain ACFP windows client route segment builder software

f. Maintain flight plan reports

g. Maintain ACFP weather reports

h. Maintain internal FPM data caching capability for rapid access to aircraft performance data

i. Maintain ACFP web services interface as defined within the ACFP 4.x Services Interface

Design Description

j. Maintain ACFP browser based forms interface

k. Maintain ACFP aircraft defaults data management

l. Maintain ACFP „controller‟ software used to set up parameters for flight plan optimization

m. Maintain ACFP database, to include structure, stored procedures, and triggers

n. Provide problem resolution for trouble tickets which indicate potential defect or performance issues with ACFP

o. Maintain ACFP route request segment data management

p. Maintain ACFP navigational data management

q. Maintain ACFP weather data management

r. Maintain ACFP foreign information region (FIR) capability for identification of FIR crossings on ACFP flight plan reports

s. Maintain ACFP interfaces with the external Global Decision Support System (GDSS)

t. Maintain ACFP interfaces with the external MAF Enterprise Information Service (MEIS)

u. Maintain ACFP fixed track data management

v. Maintain ACFP degrade by tail number data management

w. Maintain ACFP customer service tools for account, system, and performance management

x. Maintain ACFP message handler for tracking status and retrieval of flight plans

y. Maintain ACFP to remain compatible with changes to AMC/USTRANSCOM‟s command and control enclave

II. Modifying/enhancing the ACFP application to meet emerging computer security threats, increase security posture, improve system performance, migrate/port, when approved by the COR to modern hardware/OS suite, and increase availability and reliability.

III. Modifying/enhancing the Worldwide Aeronautical Route Planner (WARP Software) and the A-

Star algorithms to maintain compliance with evolving Air Mobility Command, civilian and military aviation authority airspace requirements as they relate to flight planning.

IV. Maintain integration with the government-provided Commercially available Off-The-Shelf

(COTS) Mission Index Flying Overlay software within the ACFP application. Contractor shall maintain the ACFP source code to permit the COTS software to interact, without degradation to source code functionality and performance, with ACFP software to produce cost indexed flight plans to include time, altitude, and speed variations to achieve cost index optimization provided by the Mission Indexing COTS software. Contractor shall analyze, design, code, and test modifications to ACFP application and resultant interface with the COTS software to ensure valid flyable and file-able flight plans.

1.3.2.1 Subtask 2-1 – Priorities and Schedule.

Based on the priorities established by the COR, the contractor shall manage software maintenance efforts to deliver code/requirements capable of operation in the ACFP environment consisting of the ACFP application hosted on both client and server hardware, web services, Oracle relational database, Public

Key Infrastructure (PKI) authentication, Oracle Forms and Reports, and interfaces to external systems including the Global Decision Support System and Portable Flight Planning Software. The contractor shall schedule software releases as agreed to by the contractor, the government program manager, and/or the COR.

1.3.2.2 Subtask 2-2 – Requirements Analysis.

The contractor shall perform analysis and evaluation of software code changes, which includes:

1.3.2.2.1 Clarification of the problem/requirement with the originator, functional manager, and the ACFP

PMO.

1.3.2.2.2 Adherence to Department of Defense Information Technology Standards Registry (DISR) and other applicable standards; cost and schedule impacts to ACFP (estimates of computer resources and man-hours required to implement the change); and technical impacts of the proposed change to ACFP and its interfacing systems.

1.3.2.2.3 Compatibility with Sun Servers, Sun Solaris 10, Oracle 11g, Apache Web Server, Microsoft

Server 2003, Microsoft Active Directory, ACFP Client Software (Request Input Manager - RIM, and

Request Segment Builder - RSB) run on WindowsVista and Windows 7, and Public Key Infrastructure.

1.3.2.3 Subtask 2-3 – Implementation.

The contractor shall develop and deliver software code changes that are required to correct the performance of functions described in existing system or software documentation and to implement downward-directed, mission-essential requirements; confirm vendor software patch compatibility with existing ACFP code and install; install operating system upgrades for government furnished equipment;

analyze and upgrade the database management system; and maintain the WARP web service software originally developed by On-Time Systems, Inc.

1.3.2.4 Subtask 2-4 – Testing.

The contractor shall perform unit and system integration testing on all software modified under this contract. Following successful integration testing, the contractor shall release the software to the government for follow-on government acceptance testing. The contractor shall correct any deficiencies identified during the testing; and shall provide a new baseline, when required, to implement key functionality for the baseline being released.

Source code shall be fully tested, documented, any anomolies recorded, and shall provide fully functional capabilities per RSA.

1.3.2.5 Subtask 2-5 – Delivery.

At software turnover, the contractor shall deliver all master software code, including source code and documentation (CDRL A007) to the ACFP CM Oversight Manager for inclusion in the government

Configuration Management Library (CML).

1.3.2.6 Subtask 2-6 – Information Assurance.

The contractor shall ensure that ACFP adheres to the Certification and Accreditation (C and A) requirements of the DOD Information Assurance Certification and Accreditation Process (DIACAP).

Contractor personnel may be required to provide support in the systems Certification and Accreditation effort with each release delivery. This support may include system description updates (both textual and graphical) to the Systems Security Accreditation Agreement (SSAA) when the government is required to update the SSAA.

1.3.2.7 Subtask 2-7 – Documentation.

The contractor shall update the on-line help files and system documents (CDRL A007) whenever software changes/ software releases significantly impact currency and as deemed necessary by the COR.

Deliverables: Help Files and System Documents (CDRL A007):

Master Software Code and Executables

Software Version Description

Database Design Descriptions

Services Interface Design Document

Software User Manual

Software User Guide

Operations Manual

1.3.2.8 Subtask 2-8 – Flight Performance Model (FPM) Updates.

The contractor shall incorporate new FPM updates, as they become available, for all aircraft for which

Original Equipment Manufacturer (OEM) data is not available. Flight Performance Models shall be provided to the contractor as GFE. The contractor shall integrate the FPMs into ACFP such that all flight plans for the applicable aircraft are computed using the FPM calculation results.

1.3.3 TASK 3 – APPLICATION SUPPORT ENVIRONMENT SUPPORT.

The contractor shall install ACFP software on all required GFE to the state required to enable the execution of ACFP system maintenance functions. This support may include, at a minimum, troubleshooting, data restoral from backup media/devices or external sources, and performing modifications to the baseline received via the initially delivered ACFP GFE/Government Furnished

Inventory (GFI) to permit resumption and transition to software maintenance activities. The contractor shall verify and validate that the development system continues to function as required.

1.4 DELIVERABLES.

All deliverables shall be produced using prescribed formats, software tools and software versions as approved by the COR. All deliverables shall meet professional standards and the requirements set forth in this PWS and conform to the tools and templates in Air Force Handbook (AFH) 33-337, The Tongue and Quill. All deliverables are listed on DD Form 1423 CDRLs as an attachment to the PWS.

The contractor shall be responsible for providing the following deliverables:

Contract Data

Requirements

List (CDRL)

Number

Deliverable Title PWS Paragraph Delivery

Date/Description

A001 Monthly Contractor Progress

Status/Management Report

1.3.1.1 See CDRL Attachment A

A002 Project Schedule 1.3.1.1 See CDRL Attachment A

A003 Trip Report 1.3.1.1 See CDRL Attachment A

A004 Agendas, Presentation Material, Minutes, and Action Items

1.3.1.1,1.3.1.2 See CDRL Attachment A

A005 Interchange Meeting Minutes 1.3.1.2 See CDRL Attachment A

A006 Government Property Physical

Inventory Report

1.3.1.3 See CDRL Attachment A

A007 Help Files and System

Documents:

Master Software Code and

Executables, Software Version

Description, Database Design

Descriptions, Services Interface

Design Document, Software

User Manual, Software User Guide, and

Operations Manual

1.3.2.5, 1.3.2.7 See CDRL Attachment A

A008 Quality Control Plan 4.3 See CDRL Attachment A

A009 Management Report 1.3.1.4 See CDRL Attachment A

A010 Configuration Management Plan 1.3.1.5 See CDRL Attachment A

A011 Phase-In/Phase-Out Plans 4.28.1, 4.28.2

See CDRL Attachment A

2.0 SERVICES SUMMARY (SS)

The SS table below summarizes the most important performance objectives and thresholds (specific standards) as identified within the body of the PWS. The absence of any performance objective and threshold from this SS shall not detract from its enforceability or limit the government‟s rights or remedies afforded under this contract.

Performance

Objective

PWS Para Performance Threshold Method of

Surveillance

Provide a Monthly

Contractor Progress

Status/Management

Report

1.3.1.1 Documentation and submission

requirements comply with contract requirements and agency specific formats, and the information provided is accurate, clear, complete, consistent, and contains the appropriate level of detail. No more than four grammatical, punctuation or spelling errors per document. No more than one rewrite per submission resulting from inaccurate, incomplete, or unsupported information. Submit on 5 th calendar day of each month.

One-hundred percent monthly inspection of

Progress

Status/Management

Reports to ensure performance standards are met.

Provide and maintain a current

Project Schedule

1.3.1.1 Documentation and submission

requirements comply with contract requirements and agency specific formats, and the information provided is accurate, clear, complete, consistent, and contains the appropriate level of detail. No more than four grammatical, punctuation or spelling errors per document. No more than one rewrite per submission resulting from inaccurate, incomplete, or unsupported information. Schedule is electronically maintained/updated.

The schedule is due no later than the th calendar day of each month or within ten days of notification of new software modifications.

One-hundred percent monthly inspection of monthly project schedules.

Deliver all master software code, including source code and documentation to the ACFP CM

Oversight Manager

1.3.2.5 All master software code, including

source code and documentation are delivered to the ACFP CM Oversight

Manager on or before scheduled due date 100% of the time & all documents shall be complete, accurate, and clearly written. Source code shall be fully tested, documented, any anomalies recorded, and shall provide fully functional capabilities per RSA.

One-hundred percent inspection upon final delivery/final invoice of all delivered master software code, including the source code and documentation to ensure performance standards are met.

All Conflict of

Interests (OCI) and information access concerns are resolved promptly.

4.22

Appendix 3

All Non-Disclosure Agreements

(NDAs) are completed within 5 working days of contract award. New employees are required to have a signed NDA prior to providing any services under ACFP contract. Initial notice of all unresolved issues and/or updates on status of OCI mitigation actions are provided within one day from the time contractor is aware of the issue/OCI. No instances of late initial notices.

Quarterly review on the number of late

NDAs.

Quarterly review on the number of late initial notices.

3.0 GOVERNMENT-FURNISHED PROPERTY AND SERVICES.

3.1 GOVERNMENT-FURNISHED PROPERTY. The government will provide the items indentified in

Appendices 1 and 2. The government will use an Engineering and Installation (E&I) Air National Guard squadron to transport GFP to the contractor‟s facility. The E&I squadron will rack and install the GFP at the contractor‟s facility. The transportation and installation of GFP will occur at no expense to the contractor.

3.2 GOVERNMENT-FURNISHED SERVICES. The contractor will coordinate with the COR for access to government restricted access areas. Upon coordination, the COR will provide contractor personnel escorted access to government restricted access areas.

3.3 PROPERTY PROTECTION. Property protection for facility 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 Air Force Instruction (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.

4.0 GENERAL INFORMATION.

4.1 PLACE OF PERFORMANCE.

The work to be performed under this contract will be performed at the contractor facility. Contractor will be required to attend meetings and conferences, as directed by the COR, at Scott AFB or within 20 miles of Scott AFB.

4.2 RETENTION OF CONTRACTOR PERSONNEL.

The contractor shall make every effort to retain personnel in order to ensure continuity until contract completion. If it should become necessary to substitute or replace personnel, the contractor shall immediately notify the COR in writing of any potential vacancies. The contractor shall submit the resumes of all potential replacement personnel selected to perform under this contract to the COR for government review and acceptance/rejection. The contractor shall inform the COR of what projects or assignments might be affected with a change in personnel.

4.3 QUALITY CONTROL PLAN. The contractor shall establish and maintain a Quality Assurance

Program IAW International Organization for Standardization/International Electrotechnical Commission

(ISO IEC) 26514:2008 and SEI CMMI Level 3-defined requirements or equivalent processes approved in writing by the COR. In establishing and maintaining a Quality Assurance Program, the contractor shall plan, develop, and implement procedures and practices to identify, prevent and ensure non-recurrence of defective services. The COR shall audit all processes and products as outlined in the Quality Control

Plan (CDRL A008). The Quality Control Plan shall include a non-compliance reporting and tracking process and ensure that all requirements of the contract are complied with fully. Initial draft Quality

Control Plan is due with proposal. Final document is due to the COR 20 workdays after award.

Subsequesnt deliveries of the Quality Control Plan are due when requested by the COR or when the contractor updates its Quality Control Plan.

Deliverables: Quality Control Plan (CDRL A008)

4.4 GOVERNMENT QUALITY ASSURANCE.

The government will evaluate contractor‟s performance for compliance with the requirements set forth in this PWS. The government will monitor the contractor‟s performance under this contract by performing checks as contained in the Quality Assurance Surveillance Plan.

4.5 ACCESS TO GOVERNMENT AUTOMATED INFORMATION SYSTEMS.

Contractors requiring access to government Automated Information Systems (AIS) shall have background investigations and security awareness training completed prior to the start of contract performance or immediately after being hired or transferred. When the period of performance is complete or contractor personnel leave work on this project they will have five days to terminate all their network user accounts and to return all access cards and base identification badges to the government Trusted Agent. All contractor and subcontractor personnel must have and maintain the appropriate security clearance before being authorized access to Federal government computers and networks.

4.6 SECURITY MANAGEMENT.

The contractor shall oversee security concerns, identifying conflicts/concerns and solutions, and implement procedures to maintain control and auditing of security for its personnel, its data, and its computer system access. The contractor shall ensure that all work remains compliant with all applicable

Air Force (AF) security regulations and security levels.

4.7 PROGRAM MANAGEMENT ASSISTANCE.

The ACFP PMO, AMC/A6IM, or its successor organization, will assist contractor personnel in processing the necessary Department of Defense (DOD) forms to obtain base or area badges for access to government facilities.

4.8 HANDLING AND SAFEGUARDING CLASSIFIED INFORMATION.

The contractor shall provide for the handling and safeguarding of all classified information IAW AF 31-

401 and DOD Manual 5200.1 Vol 3 standards for storing, processing, and handling classified information and systems. The contractor personnel shall have the appropriate security clearance for the facilities in which the work is required.

4.9 CONTRACTOR ACCESS.

4.9.1 Contractor Identification (ID)/Badges. Contractor shall comply with Scott AFB or other Federal government facilities‟ contractor identification procedures including identification of the contractor, and identification of contractor status at meetings. Contractor personnel shall comply with all Scott AFB rules, regulations and security requirements, when entering, visiting or leaving the Air Base. These rules, regulations and security requirements include the following: presenting valid ID for base entrance, obeying all posted directives, and providing strict adherence to Security Forces direction in instances where Security Forces have been dispatched to a particular location. The contractor is required to provide

ID badges for their employees. All contractor personnel shall wear these badges while on duty on the government site. Badges are required to identify (including photograph) the individual, company name, and be clearly and distinctly marked as contractor. Size, color, style, etc. are to be mutually agreed to by contractor and COR.

4.9.2 Access to Government Facilities. The government, based on its assessment of the contractor‟s need, will provide the contractor access to ACFP program facilities from the commencement of the contract until contract completion. Only contractor (or subcontractor) personnel possessing the proper clearance will be authorized entry to restricted areas. All contractor personnel must either have the appropriate building access permissions and ID cards or otherwise must be continuously escorted by government approved personnel.

4.9.3 Access to Installation during Force Protection Conditions (FPCONs). Contractor will be assigned a mission essential designation IAW requirements contained in Scott AFB Integrated Defense Plan or the

Scott AFB Antiterrorism Plan. Only the installation commander or the unit commander requesting contract support will assign the mission essential designation.

4.9.4 Contractors Working in Controlled or Restricted Areas. In the unlikely event that a contractor requires access to the controlled or restricted area and does not have the proper security clearance, the government will ensure escort(s) are provided for the contractor at all times within a controlled or restricted area. The contractor must have an issued AF Form 1199; work on base a minimum of four days a week (must have an assigned workspace on base). The contractor is only allowed to escort visitors from the same company for which he/she works and all visits must be for official business. In addition, contractors must fulfill, maintain, and comply with all security requirements IAW AFI 31-101, Integrated

Defense, and command/local directives.

4.9.5 Access to Government Facilities with Controlled or Restricted Areas. The 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 Scott AFB, the government may direct the contractor to leave the controlled or restricted areas at any given time. If this direction increases the cost of or the time required to complete the work, the negotiated contract price or schedule, or both must be adjusted accordingly through a modification to the contract.

4.10 HIGHEST SECURITY CLEARANCE.

The highest security classification required by this contract is SECRET. Required contractor personnel shall possess appropriate security clearances as of contract award date. The contractor will be given access to applicable documentation to include requirements, plans, specifications, studies, and analyses up to and including SECRET classification. The contract and its attachments are unclassified.

4.11 NETWORK AND COMPUTER SECURITY.

The contractor shall ensure that it is knowledgeable with AFI 33-200, Information Assurance

Management, as well as, AMC system security policies and ensure that the software it delivers to the government is compliant with those policies.

4.12 INFORMATION IN THE CONTRACTOR POSSESSION.

Information given to the contractor during the life of this contract must only be used for the purpose of carrying out the provisions of this contract.

4.13 FOR OFFICIAL USE ONLY INFORMATION.

Agency information marked “For Official Use Only” or bearing other sensitivity marking will be handled

IAW agency information security program regulations and instructions provided on the DD Form 254.

This information will not be divulged or disclosed without agency permission. Requests for disclosure will be addressed to the government COR. Contractor personnel will ensure information that is considered sensitive or proprietary is not compromised.

4.14 PRIVACY ACT.

Work on this project may require that personnel have access to Privacy Information. Personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.

4.15 CONTRACTOR CONSENT TO BACKGROUND CHECKS.

All contractor and subcontractor personnel must consent to Law Enforcement Agency Data System

(LEADS) background checks. The contractor shall conduct the background checks on all of its employees and its subcontract employees working under this contract. The contractor and, as applicable, subcontractor shall not employ persons for work on this contract if such employee is identified as a potential threat to the health, safety, security, general well being or operational mission of the installation and its population, nor shall the contractor or subcontractor employ persons under this contract who have an outstanding criminal warrant as identified by LEADS through the National Crime Information Center.

(LEADS checks will verify if a person is wanted by local, state, and federal agencies.) Information required to conduct a LEADS check includes: full name, driver‟s license number, and/or social security number, date of birth, and completion of a background check questionnaire. The contractor shall provide this information using the Scott AFB Form 21, contractors Consent for Background Check, and shall submit it in conjunction with the contractor‟s request for either base or vehicle passes. Completion of a successful LEADS check does not invalidate the requirement for having the appropriate level of security clearance and an escort when contractor or subcontractor personnel are working within controlled or restricted areas.

4.16 PROPER EMPLOYEE CREDENTIALS.

The contractor shall ensure its employees and those of its subcontractors have the proper credentials allowing them to work in the United States. Persons later found to be undocumented or illegal aliens will be remanded to the proper authorities. The contractor shall not be entitled to any compensation for delays or expenses associated with non-compliance. Furthermore, this shall not excuse the contractor from proceeding with the contract.

4.17 INFORMATION ASSURANCE (IA).

Contractor shall comply with all AMC security requirements pursuant to DODD 5200.2, Personnel

Security Program, DODI 8500.2 Information Assurance Implementation, and DODD 8570.01-M;

Information Assurance Workforce Improvement Program. Contractor must ensure that all personnel assigned to work on the contract must complete annual IA training by on-line Computer Based Training

(CBT). Contractor is responsible at time of award to have the appropriate IA Level I and II certification coverage as defined in DODD 8570.01-M. The contractor shall provide individual employee annual completion certificates in electronic format to the government.

4.18 ANTITERRORISM LEVEL I TRAINING.

Within 30 calendar daysafter contract start, all contractor personnel shall complete Antiterrorism Level I

Training, as required by DODI 2000.16. Newly hired personnel shall complete the Antiterrorism Level I

Training within the first 30 calendardays of their employment. Refresher Antiterrorism Level I Training shall be completed and documented annually thereafter. The training is provided at https://atlevel1.dtic.mil/at/ and also available through Advanced Distributed Learning Services (ADLS), Force Protection Course (ZZ133079) athttps://golearn.csd.disa.mil/kc/main/kc_frame.asp for AF Portal access orhttps://golearn.csd.disa.mil/kc/login/login.asp for non-portal login.

4.19 SAFETY REQUIREMENTS.

The contractor shall comply with all safety provisions, e.g., technical specifications, technical publications, federal Occupational Safety and Health (OSHA) standards (Title 29 CFR Part 1910). If there is no applicable OSHA standard, the contractor shall use other applicable nationally or locally recognized sources of safety, health, and fire prevention standards.

4.20 CONTRACTOR PERSONNEL TRAINING.

4.20.1 Technical Currency. The contractor shall supply and bear all the training cost (e.g., salary, tuition, course materials, travel, and per diem) to ensure the technical currency of its employees on commercially available applications in order to accomplish the tasks under this contract. Some examples are operating systems, server applications, and office applications.

4.20.2 Certification Training Expense. The contractor shall supply and bear all the cost (salary, tuition, course materials, travel, and per diem) for its employee certifications.

4.20.3 Special Training Expense. Any special training costs resulting from changes to technology or technical direction that are related to uniquely government applications may be reimbursed by the government and chargeable to Other Direct Costs (ODC), but require approval of the COR and the CO‟s confirmation of availability of funds prior to the contractor employee registering for the training course.

4.21 TRAVEL EXPENSE AND OTHER DIRECT COSTS REIMBURSEMENT.

4.21.1 Travel. The contractor may be required to travel in the performance of this PWS. The Contractor shall obtain approval for need of travel by the COR prior to travel commencement. Additionally, the contractor shall receive CO confirmation on availability of funds The government shall reimburse the contractor for travel expenses IAW Federal Acquisition Regulation (FAR) 31.205-46 and the applicable travel regulation therein. The contractor shall provide a Trip Report (CDRL A003) for each travel event that includes the people who traveled, places traveled to, dates of travel, purpose of the travel, and minutes for activities performed during the travel event. Trip Reports are due within two workdays after return of travel.

Deliverables: Trip Report (CDRL A003) https://atlevel1.dtic.mil/at/

4.21.2 Travel Reimbursement. Per Diem and travel rates shall not exceed the amount authorized IAW

FAR 31.205-46 and the applicable travel regulation. Airfare shall be the prevailing rates for commercial airlines at economy class. The most reasonable means of ground transportation (i.e. taxi, bus, rental car) shall also be used. The government will not reimburse local travel and related expenses to the contractor.

Local travel is defined as any travel 50 miles or less one-way from place of performance. At least five working days prior to the travel start date, the contractor shall submit a travel itinerary and estimated cost for approval by the COR and confirmation on availability of funds from the CO.

4.21.3 Other Direct Costs. The contractor may submit charges supporting the delivery of requested services for the accomplishment of contract activities. Other Direct Costs may include CD‟s, DVD‟s, portable hard drives to support demonstration of capabilities, non-warranteed replacement parts for ACFP hardware (i.e. power cables and uninterruptable power supplies). Requirements over the micro-purchase threshold as defined in FAR 2.101 must follow competition requirements and FAR/DFARS/AFFARS procedures and may result in contracting actions outside of this contract. All contractor ODC shall be approved by the government COR and CO prior to the contractor incurring any expenses.

The contractor shall provide all consumable materials when essential to task performance at contractor expense. These materials are those items that are not reusable after initial use. Some materials that fall within this area are: paper, pens, pencils, markers, tape, staples, tacks, toner cartridges, disks, binders, etc. These items will not be reimbursable as an ODC.

4.22 NON-DISCLOSURE AGREEMENTS.

In performance of this contract, the contractor may obtain access to sensitive, nonpublic information. The contractor agrees (a) to use and protect such information from unauthorized disclosure IAW the FAR; (b) to use and disclose such information only for the purpose of performing this contract and to not use or disclose such information for any personal or commercial purpose; (c) to obtain permission of the government COR before disclosing/discussing such information with a third party; (d) to return, upon government request, any non-public, sensitive information no longer required for contractor performance;

and (e) to advise the government COR of any unauthorized release of such information. Upon request, the contractor shall have its employees assigned to this contract execute a NDA for delivery to the government. The government will require contractor personnel both on and off-site to sign a NDA to protect non-public information of the government (see Appendix 3). The contractor shall maintain the

NDAs and have these agreements available for government review during the life of the contract. At the end of the contract, the contractor shall turnover to the government its personnel non-disclosure agreements.

4.23 IDENTIFICATION OF NON-DISCLOSURE REQUIREMENTS.

The contractor shall execute NDAs when it works with sensitive or proprietary information provided from the government, other contractors, and firms not having government contracts, academic institutions, and other nonprofits. The contractor agrees to enter into company-to-company agreements to (1) 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. This restriction shall be included in all subcontracts, teaming arrangements, and other agreements calling for performance of work.

4.24 PROTECTING GOVERNMENT INTELLECTUAL PROPERTY.

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 in the use and care of the contractor without the expressed written authorization by the 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 use 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 (OS) data recovery tools, without expressed written permission of the government. Failure of the contractor to comply may subject the contractor to breach of contract, criminal civil penalties, criminal charges, or all three.

Upon delivery of the final version release or other deliverables under this contract, the contractor shall deliver to the COR and/or at the direction of the COR transfer to another contractor, the following granting the government unlimited rights license to use and distribute the data, to include in the license the contractor waiving any rights to use the intellectual property for purposes other than the performance of this contract:

All framework, source code (fully compliable package), libraries, database tables, scripts, resources, modules, and all other related materials on the ACFP system and all software code.

All procedures to move modules to test/production environments, maintenance procedures, reference materials, technical documentation, user manuals, training and/or classroom materials and all other related documentation.

Technical orientation of ACFP system to include definition and description of all modules.

Source code, object code, database applications, and permissions to access the source, object code, and ORACLE database.

Documentation to include system architecture documentation, configuration management procedures, (to include creating new modules, logging out existing modules, modifying code, testing, checking in modules, production releases, version control, etc.), system administrator procedures, database structure documentation, data dictionary, and batch job schedules.

4.25 DATA RIGHTS.

Pursuant to Defense Federal Acquisition Regulation Supplement (DFARS)…