Attachment 3 SDS-PWS.pdf

FA7014‐25-R-0004

PERFORMANCE WORK STATEMENT

FOR

Headquarters Air Force (HAF) Software Development Services at

The PENTAGON and JOINT BASE ANDREWS, MARYLAND

22 March 2024

Controlled by: AFDW/PKS CUI Categories: PROCURE Distribution/Dissemination Controls:

FEDCON AFTER AWARD

POC: Hannah Dent (hannah.dent.1@us.af.mil)

Contents

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 GENERAL

1.2 BACKGROUND

SECTION II

2.0 TASK DESCRIPTIONS

2.1 COLD FUSION APPLICATION DEVELOPMENT AND SUSTAINMENT SUPPORT (SENIOR SOFTWARE DEVELOPER)

2.2 SHAREPOINT/POWER PLATFORM DEVELOPMENT AND SUSTAINMENT (SHAREPOINT DEVELOPER)

2.3 SHAREPOINT/POWER PLATFORM DEVELOPMENT AND SUSTAINMENT (IT SENIOR SHAREPOINT CONSULTANT, IT SHAREPOINT

CONSULTANT)

SECTION III

3.0 SERVICE SUMMARY

SECTION IV

4.0 DELIVERABLES

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL, INFORMATION, OR SERVICES

5.1 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL, INFORMATION, OR SERVICES

5.2 CONTRACTOR ACQUIRED PROPERTY

SECTION VI

6.0 GENERAL INFORMATION

6.1 Personnel

6.2 Requirements

6.3 Scheduling Concerns

6.4 Kickoff Meeting

6.5 Transition-Out Plan

6.6 Quality Control

6.7 Emergency Operations/Mission Essential Personnel

6.8 System for Award Management (formerly CMRA)

6.9 Security Instructions

6.10 Travel

6.11 Employee Accountability & Turnover

6.12 Miscellaneous

SECTION VII

7.0 DEFINITIONS, ABBREVIATIONS, AND ACRONYMS

SECTION I

1.0 Description of Services

1.1 General

The Secretary of the Air Force, Administrative Assistant, Information Management, Enterprise Business Solutions Division (SAF/AAIE), is a professional, customer-focused team dedicated to providing consultation and planning, business solutions, lifecycle support services, and software development services to support senior decision makers at Headquarters Air Force (HAF).

1.1.1 Scope

This requirement is to provide technical services for software development support and business solutions within SAF/AAIE. Technical services include enterprise architecture, requirements management, software engineering, systems engineering, software test management, and systems/server administration. Contractors will work as part of a team to develop new software applications or modify and sustain existing applications.

1.2 Background

This work is currently being satisfied under the SAF/AAIE contract FA8771-12-D-1006-X001.

This is the fourth and final option year with a Period of Performance (PoP) of 1 February 2024 - 31 January 2025. Previously, the requirement has used GSA IT70 as a contract vehicle.

1.2.1 SAF/AAIE supports a portfolio of web applications, including ColdFusion/Oracle database, and Microsoft SharePoint Online with or without Power Platform.

1.2.2 SAF/AAIE anticipates additional workload in Microsoft SharePoint out-of-the-box configuration and other trends toward using existing, approved Air Force tools and systems, as well as work related to requirements analysis and management.

SECTION II

2.0 Task Descriptions

The Contractor shall perform a variety of Software Development Life Cycle (SDLC) tasks in support of a portfolio of products developed by SAF/AAIE in support of the HAF. SAF/AAIE is committed to the use of repeatable and predictable software development processes and, as such, the Contractor shall work within teams and processes that work under Agile methodologies, organizational standard processes, and industry best practices. Tasks to be performed under these processes include Business Modeling and Analysis, Object Oriented Analysis and Design, Requirements Elicitation and Analysis, Software Design and Implementation, Software Process Improvement, Test and Quality Assurance, and Configuration and Change Management. In addition, the Contractor shall be required to understand Agile development methodologies, and DoD and Air Force Standards to be able to properly perform the following tasks:

- Manage configuration of software items

- Model business processes

- Develop business cases

- Establish project baselines and priorities

- Estimate project cost, duration, and levels of effort, including work breakdown structures and project schedules

- Work with the Government to establish customer software and IT requirements

- Manage scope of requirements

- Collaborate and communicate requirements in an Agile development environment

- Develop use cases and other requirements documents

- Create and execute test plans

- Manage risks to include identifying, analyzing, tracking, and mitigating risks

The Contractor shall provide technical services in object-oriented (OO) and database-backed web application software development using iterative SDLC to include Agile software development methodologies. The Contractor shall provide technical services in SharePoint Online application development using Microsoft 365 infrastructure, including tools such as Power Platform and other SharePoint-adjacent technologies. The Contractor shall provide personnel with the expertise to support SAF/AAIE software engineering services for the Headquarters Air Force in the following roles and tasks.

2.1 Cold Fusion Application Development and Sustainment Support (Senior Software Developer)

2.1.1 Designs, develops, enhances, debugs, and implements software in ColdFusion, Oracle database, SQL, Java Script, HTML5, CSS3, and REST (API Calls). Troubleshoots and solves production problems related to software applications in a responsive manner.

2.1.2 Designs, develops, tests, debugs, builds, and coordinates the upgrade, conversion, and/or integration of products.

2.1.3 Designs and develops new software products or major enhancements to multiple existing systems.

2.1.4 Communicates and coordinates with project teams, stakeholders, enterprise architects, and management to identify, prioritize, and implement application requirements.

2.1.5 Participates in Agile development methodologies and is proactive in identifying day-to-day project work and responsible for its completion.

2.1.6 Mentors, instructs, advises, and checks the work of other software developers within the organization.

2.1.7 Ability to work in controlled and repeatable SDLC managed with Agile methodologies.

2.1.8 Uses existing software development tools in conjunction with Agile methodologies to include Digital AI Agile development tool and Subversion configuration management tool.

Assists in the evaluation and recommendation of application software packages, application integration, and testing tools.

2.1.9 Develop architecture and design artifacts, software user manuals, and training materials.

2.1.10 Assist with planning and configuring of existing architecture.

2.1.11 Support the maintenance of existing software artifacts such as Requirements documents, Software Architecture documents, Test documents, Maintenance Evaluations, Release Notes, and Build of Materials.

2.1.12 Assist application owners with their compliance activities related to application software artifacts such as system diagrams, software architecture, and network diagrams.

2.2 SharePoint/Power Platform Development and Sustainment (SharePoint Developer)

2.2.1 Working individually and with others, the Contractor shall provide the skill set required to support HAF existing and future SharePoint environment and user base.

2.2.2 Provide accurate and quality products and documents on time.

2.2.3 Communicate effectively in English both in speech and in writing at a level consistent with technical work at a major military headquarters. Prepare written documentation of technical analyses to support technical change proposals. Prepare written documentation of actions taken and changes implemented in sufficient detail to support configuration management. Provide documentation as inputs in support of consolidated reporting.

2.2.4 Maintain and develop site collections, document libraries, lists, forms, calendars, schedules, discussion boards, databases, and expansion of same for recognized needs as they occur.

2.2.5 Perform administration tasks to include permission controls, refining or developing workflows, and user interfaces.

2.2.6 Provide day-to-day support to the HAF SharePoint applications customer base to include troubleshooting and resolving user issues arising through new project or sustainment work.

2.2.7 Provide subject matter expert consultation and produce training material, to include instructional guides and inputs to standard operating procedures.

2.2.8 Participate in working groups to improve use of SharePoint.

2.2.9 Analyze how users access and organize information in SharePoint and implement processes that streamline and simplify information management and collaboration. Work with project managers and end users to ensure application designs meet business requirements.

2.2.10 Advise on selection of technologies, architectures, software design, and system support for products within the organization.

2.2.11 Configure and develop SharePoint solutions using technologies and skills to include CSS, HTML5, JavaScript, and the Microsoft 365 infrastructure, including tools such as Power Platform and other SharePoint-adjacent technologies.

2.2.12 Analyze, create, and normalize data structures (tables, lists) to enable consistent application success, and implement data operations using database technologies such as Oracle, Microsoft SQL Server, and Microsoft Access.

2.2.13 Develop products and deliverables for individual projects as well as common architecture across the portfolio of SAF/AAIE applications, to include documentation and design models.

2.2.14 Provide design documentation and diagrams suitable for inclusion in security and accreditation packages.

2.2.15 Work in controlled and repeatable SDLC-managed environment with Agile methodologies including existing software development tools such as Microsoft Visual Studio, Microsoft Power Platform, Microsoft Team Foundation, and version control tools such as GitHub repositories or Subversion in conjunction with agile methodologies.

2.2.16 Develop and integrate SharePoint solutions with Microsoft 365 tools, including Access and Excel.

2.3 SharePoint/Power Platform Development and Sustainment (IT Senior SharePoint Consultant, IT SharePoint Consultant)

2.3.1 Working individually and with others, the Contractor shall provide the skill set required to support HAF existing and future SharePoint environment and user base.

2.3.2 Provide accurate and quality products and documents on time.

2.3.3 Communicate effectively in English both in speech and in writing at a level consistent with technical work at a major military headquarters. Prepare written documentation of technical analyses to support technical change proposals. Prepare written documentation of actions taken and changes implemented in sufficient detail to support configuration management. Provide documentation as inputs in support of consolidated reporting.

2.3.4 Maintain and develop site collections, document libraries, lists, forms, calendars, schedules, discussion boards, databases, and expansion of same for recognized needs as they occur.

2.3.5 Perform administration tasks to include permission controls, refining or developing workflows, and user interfaces.

2.3.6 Provide day-to-day support to the HAF SharePoint applications customer base to include troubleshooting and resolving user issues arising through new project or sustainment work.

2.3.7 Provide subject matter expert consultation and produce training material, to include instructional guides and inputs to standard operating procedures.

2.3.8 Participate in working groups to improve use of SharePoint.

2.3.9 Analyze how users access and organize information in SharePoint and implement processes that streamline and simplify information management and collaboration. Work with project managers and end users to ensure application designs meet business requirements.

2.3.10 Advise on selection of technologies, architectures, software design, and system support for products within the organization.

2.3.11 Configure and develop SharePoint solutions using technologies and skills to include CSS, HTML5, JavaScript, and the Microsoft 365 infrastructure, including tools such as Power Platform and other SharePoint-adjacent technologies.

2.3.12 Analyze, create, and normalize data structures (tables, lists) to enable consistent application success.

2.3.13 Provide design documentation and diagrams suitable for inclusion in security and accreditation packages.

2.3.14 Work in controlled and repeatable SDLC-managed environment with agile methodologies and version control tools such as GitHub repositories or Subversion in conjunction with agile methodologies.

2.3.15 Develop and integrate SharePoint solutions with Microsoft 365 tools, including Access and Excel.

SECTION III

3.0 SERVICE SUMMARY

Below is a list of performance requirements and performance thresholds required by the Government in Contractor performance. The Contractor shall submit a Quality Control Plan, which will define how they intend to meet the Government performance requirements and thresholds, in accordance with the requirements in this PWS and the following measurable terms.

Performance Objective PWS Paragraph

Performance Threshold Method of Surveillance

SS – 1

Monthly Activity Reports

2.0, 2.1, 2.2, 2.3

Prepare monthly activity reports and provide a digital copy to the COR no later than 12:00 p.m. ET on the 10th of every month, 90% of the time.

100% Surveillance

SS – 2

Vacancies

6.1, 6.2 Replace departing Contractors within 30 calendar days after notification to the COR, and within 14 days after the previous contract employee’s last work day.

100% Surveillance

SS – 3

Artifacts and Documentation

2.0, 2.1, 2.2, 2.3

Performance is acceptable when the documentation and software development artifacts as assigned by management are submitted on time (based on the suspense directed by the Government) to the Government and accurate upon submission defined as with minimal spelling or content errors.

Periodic

SS – 4

Quality Control Plan (QCP)

6.6.2 Performance is acceptable when:

The report is submitted on time.

100% Surveillance

SS – 5

Mission Continuity Reports This deliverable shall provide all software, source code, and documentation, without any restrictions whatsoever by the Contractor.

2.0, 2.1, 2.2, 2.3, 6.12.4

Performance is acceptable when the deliverables are submitted on time to the Government.

This data will be available as specified in the contract and in accordance with DFARS clause 252.227-7015 Technical Data – Commercial.

The Mission Continuity Reports are to be submitted within 60 days before the contract ends. The Government will review and provide approval within 5 days before the end of the contract so the contractor can implement any changes.

100% Surveillance

SECTION IV

4.0 DELIVERABLES

The specific form and required delivery dates for all deliverables will be specified by the originator consistent with Air Force needs. The Contractor shall provide task order deliverables in a format mutually agreed upon by the Government and the Contractor. In all cases the deliverable must be compliant with the Air Force writing style. Any papers, documents, or recommendations that the Contractor submits are drafts, not final copies, until approved and accepted by the COR.

Deliverable PWS Paragraph

Due Date Delivery

1 – Monthly Activity Report 2.0 No later than 12:00 p.m.

ET on the 10th calendar day of each month

By email to the COR in Microsoft Word format

2 – Kickoff Meeting Agenda 6.4 No later than 5 calendar days after contract award

By email to the COR in Microsoft Word format

3 – Transition-Out Plan 6.5 No later than 90 days prior to contract expiration

By email to the COR in Microsoft Word format

4 – Quality Control Plan 6.6.2 At time of submission of its proposal

By email to the COR in Microsoft Word format

5 – Trip Report 6.10.5 No later than 5 business days after completion of each trip/TDY

By email to the COR in Microsoft Word format

6 – Employee List 6.11.2 Upon request By email to COR in Microsoft Excel format

7 – Non-Disclosure Agreement (NDA) Form 312

ALL This is to be submitted within 5 days of the start of the task order

By email to COR

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL,

INFORMATION, OR SERVICES

5.1 Government Furnished Property, Equipment, Material, Information, or Services The Government will not furnish property or services for this requirement.

5.2 Contractor Acquired Property

The contractor will not be required to acquire any property.

SECTION VI

6.0 General Information

6.1 Personnel

The Contractor shall designate an individual to the Contracting Officer (CO) and the Contracting Officer’s Representative (COR) before the contract start date. Replacement of personnel must be coordinated with the COR and CO. The Contractor shall provide a point of contact who shall have full authority to act for the Contractor on all matters relating to the daily operation of this contract.

The Contractor shall have retention and recruitment plans in sufficient detail to meet the personnel requirements listed above, to augment SAF/AAIE’s mission to develop and maintain software and web applications for Headquarters Air Force.

The Contractor shall replace any individual who is removed from the contract within 30 calendar days after notification to the COR, and within 14 days after the previous contract employee’s last work day.

The Contractor shall submit resumes for each contract employee for government review prior to placement.

6.2 Requirements

See the requirements for each labor category below.

# Labor Category

PWS

Ref.

Minimum Requirements Preferred Requirements

Security Clearanc e Level

Desired

FTE

Count

1 Senior Software Developer [ColdFusion developer]

2.1 10 years of experience in ColdFusion, Oracle database, SQL, Java Script, HTML5, CSS3, and REST (API Calls)

Bachelor’s degree Secret 1

2 SharePoint Developer

2.2 10 years of experience in: Java Script, HTML5, CSS3, REST (API Calls), 365, Microsoft Visual Studio, SharePoint development, SQL Server and Transact- SQL development experience

SharePoint certification, Power Platform certification, Bachelor’s degree

Secret 2

3 IT Senior SharePoint Consultant

2.3 10 years of experience in:

CSS, HTML5, JavaScript, and the Microsoft 365 infrastructure, including tools such as Power Platform and other SharePoint-adjacent technologies

SharePoint certification, Power Platform certification, Bachelor’s degree

Secret 2

4 IT SharePoint Consultant

2.3 4 years of experience in:

CSS, HTML5, JavaScript, and the Microsoft 365 infrastructure, including tools such as Power Platform and other SharePoint-adjacent technologies

SharePoint certification, Power Platform certification, Bachelor’s degree

Secret 2

6.3 Scheduling Concerns

6.3.1 Duty Hours

The Contractor shall have access to Government facilities 5 days per week, Monday through Friday, except when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings, unless otherwise approved. Contractor personnel are expected to conform to customer agency normal operating hours; however, the Contractor may be required access to Government facility outside of duty hours based on the customer agency’s needs. As a baseline, Contractor personnel shall work 8 hours per day, 40 hours per week. Compensatory time arrangements are permissible for temporary spikes in worktime, but overtime pay is prohibited without COR and CO approval.

Federal Holidays shall be observed in accordance with Office of Personnel Management policy.

6.3.2 Core Duty Hours and Base Shutdown/Inclement Weather.

Core duty hours are 0900-1500, Monday through Friday (excluding federal holidays). Core hours are the hours the contractors shall be at work. A flexible work schedule is allowed;

meaning varying start and stops times, but each individual shall have a consistent daily start and stop time, and be available for project tasks and meetings. The Contractor shall follow guidance of the installation containing their place of performance to determine reporting schedules whether due to a base closure or inclement weather. The website for guidance regarding status of performance for work to be performed in the National Capital Region (NCR) is http://www.opm.gov/status/.

Contractors that are able to telework may follow the Government telework program schedule for inclement weather and other telework-designated days.

6.3.3 Government Holidays. Government agencies will not be available during scheduled and unscheduled Federal holidays, weekends, after duty hours, emergencies, Government-directed facility closings, or Air Force down days. Contractors will not work on these days unless approved by the COR on a case-by-case basis.

Federal Holidays shall be observed in accordance with Office of Personnel Management policy.

Contractors shall not work on the following Federal Holidays:

- New Year’s Day

- Birthday of Martin Luther King, Jr.

- Washington’s Birthday

- Memorial Day

- Juneteenth

- Independence Day

- Labor Day

- Columbus Day

- Veterans Day

- Thanksgiving Day

- Christmas Day

6.3.4 Place of Performance. Software development services shall be performed at the SAF/AAI office located at The Pentagon, Room 4B143; at the SAF/AAIE office located at Joint Base Andrews, Jones Building, Suite 3390; or at an approved remote/telework location. Temporary, or hoteling, space will be available at The Pentagon, available for daily use; this space is not permanently assigned to individuals. The Government may, on a case-by-case basis, arrange for certain work to be performed by the Contractor at the Contractor's office or other location. At times, based on policy, each contractor may be required to work on site (in office) one or more days per week. In addition, contractors shall be on site as mission requires and may be required to arrive onsite within 2 hours of notification. Contractors shall be authorized to arm and disarm Pentagon room access without a government representative present.

6.4 Kickoff Meeting

6.4.1 Within 5 calendar days of award, the Contractor shall conduct an Orientation Briefing for the Government. The intent of the briefing is to initiate the communication process between the Government and Contractor by introducing key task participants and explaining their roles, reviewing communication ground rules, and assuring a common understanding of subtask requirements and objectives. The Orientation Briefing will be held at the Government's facility or another designated location and the date and time will be mutually agreed upon by both parties.

http://www.opm.gov/status/

6.4.2 The Contractor shall schedule and coordinate a Project kick-off Meeting no later than 5 calendar days after contract award at the location approved by the Government. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting will provide the opportunity to discuss technical, management, and logistic issues; travel authorization; and reporting procedures. At a minimum, the attendees shall include key Contractor personnel, key Government representatives, and the COR. The Contractor shall provide a Kick-Off Meeting Agenda that will include, but not be limited to, the following.

• Introduction of personnel

• Overview of project tasks

• Review of organization (complexity) and POCs

• Communication Plan/lines of communication overview (between both Contractor and

Government)

• Security requirements (Building access, badges, Common Access Cards (CACs))

• Invoice procedures

• Reporting Requirements, e.g., Monthly Activity Report

• Roles and Responsibilities

• Overview of incoming Transition Plan to include process, timeframes, and status

• Any initial deliverables

• Quality Control Plan (QCP)

• Sensitivity and protection of information

• Additional issues of concern

6.5 Transition-Out Plan

6.5.1 The Contractor shall provide a Transition-Out Plan no later than ninety (90) calendar days prior to expiration of the contract; the plan shall facilitate the accomplishment of a seamless transition from the incumbent to the incoming Contractor, if applicable. In addition, the Contractor will continue to accomplish all tasks as outlined in the contract during this period.

The Contractor shall identify how it will coordinate with the incoming Contractor and Government personnel to transfer knowledge regarding the following:

• Points of contact

• Location of technical and project management documentation

• Status of ongoing technical initiatives

• Transition of key personnel

• Schedules and milestones

• Actions required of the Government

6.5.2 The Contractor shall establish and maintain effective communication with the incoming Contractor and Government personnel for the period of the transition by holding weekly status meetings. The Contractor shall:

• Permit employees to be interviewed for possible employment by succeeding Contractors;

however, the Contractor will have the first right of refusal.

• Release any employee who chooses to be employed by a succeeding Contractor.

• Orient assigned employees of the succeeding Contractor during the last 60 days of the period of this contract if so directed by the CO or COR.

The Government will make available to such employees existing Government Furnished Property (GFP) and/or Government-Furnished Equipment (GFE) such as desks, chairs, telephones, and other normal office equipment and office supplies during the orientation period, as applicable.

6.6 Quality Control

6.6.1 Quality Assurance. The Government will rely on the Contractors’ existing quality assurance system as the method to ensure that the requirements of the contract and performance thresholds are met; however, the Government reserves the right to monitor and evaluate the quality of services provided and compliance with the contract terms and conditions at any time.

6.6.2 Quality Control Plan (QCP). The Contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS, applicable laws and regulations, and best commercial practices. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services with special emphasis placed on those services listed in this PWS. The Contractor’s quality control program is the means by which it assures itself that the work complies with the requirement of the contract.

6.7 Emergency Operations/Mission Essential Personnel

6.7.1 Continuation of Essential Contractor Services During Crisis. All services in this PWS HAVE NOT been defined or designated as essential services for performance during crisis in accordance with DFARS 252.237-7023, “Continuation of Essential Contractor Services.”

6.8 System for Award Management (formerly CMRA)

6.8.1 The Contractor shall report ALL labor hours (including subcontractor labor hours) required for performance of services provided under this contract using the System for Award Management (SAM) data collection site. The Contractor is required to completely fill in all required data fields at http://www.SAM.gov. 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. The UIC for AFDW is FF16M0. 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 System for Award Management help desk.

6.8.2 Subcontractor Input in SAM.

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

http://www.sam.gov/

6.9 Security Instructions

6.9.1 Physical Security

The Contractor shall safeguard all Government property, documents and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract. At the end of each work day, all Government facilities, equipment, and materials shall be secured.

6.9.2 Access Control

The Contractor shall establish and implement methods of ensuring that no building access instruments issued by the Government are lost, misplaced or used by unauthorized persons.

Access codes shall not be shared with any person(s) outside the organization. The Contractor shall control access to all Government provided lock combinations to preclude unauthorized entry. The Contractor is not authorized to record lock combinations without written approval by the Government COR. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.

6.9.3 Pass and Identification Items

The Contractor shall ensure the pass and identification items required for contract performance are obtained for employees and non-government owned vehicles. The Contractor shall ensure that their employees obtain Air Force credentials and certificates for access to systems, accounts, and facilities. The Contractor shall minimize any conflicts with multiple credentials and certificates before onboarding employees.

6.9.4 Retrieving Identification Media. The Contractor shall retrieve all identification media, including vehicle passes, from employees who depart for any reason before the contract expires.

6.9.5 Traffic Laws. The Contractor and its employees shall comply with base traffic regulations.

6.9.6 Weapons, Firearms, and Ammunition. Contractor employees are prohibited from possessing weapons, firearms, or ammunition, on themselves or within their Contractor-owned vehicle or privately-owned vehicle while on Joint Base Andrews or any other military facility.

6.9.7 Communications Security (COMSEC). Contractors may require access to COMSEC information on Air Force installations. The Contractor shall not require a COMSEC account.

Access shall be controlled by the sponsoring agency. Access to COMSEC material by personnel is restricted to US citizens holding final US Government clearances. Such information is not releasable to personnel holding only reciprocal clearances. If it is determined the Contractor is required to access COMSEC information, the necessary training information and courses shall be provided by the COR. The DD Form 254 shall give further instructions on safeguarding and managing COMSEC material.

6.9.8 Contractor Identification. All Contractor personnel shall wear the Air Force issued CAC at all times when away from their immediate work area so as to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or by email, Contractor personnel shall identify themselves as a contractor to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors shall identify themselves on any attendance sheet or any coordination documents they may review. Email signature blocks shall identify their company affiliation. Where practicable, contractors occupying collocated space with their government program customer should identify their work space area with their name and company affiliation or as a minimum “Contractor” after name.

6.9.9 Individual Security Clearances. The Contractor shall obtain a U.S. security clearance at the minimum level of “Secret” prior to start of this task order for all Contractor personnel, to access the Secret Internet Protocol Router Network (SIPRNET) and process classified materials.

Clearance shall be obtained through the Defense Investigative Services.

6.9.10 Personal Security. The Contractor shall be responsible for Personnel Security. Contractor personnel shall require, at a minimum, a favorable National Agency Check plus written Inquires (NACI). The investigation is not for a security clearance; it is for a position of trust, as required by DoD Regulation 5200.2-R, DoD Personnel Security Program, and AFI 31-501, Information Personnel Security. The Contractor shall provide documentation received from the appropriate Government agency as to the verification of contract personnel’s NACI certification. In case the certification has been requested but not received, the Contractor may provide documentation on any Contractor employee where certification has been requested.

6.9.11 The Contractor shall comply with the security requirements of this contract and the DD Form 254, Department of Defense Contract Security Classification Specification. Access to classified information will only be at those locations identified in Item 8a on the DD Form 254.

At no time will the Contractor access classified information from telework locations or other locations not identified in Item 8a on the DD Form 254.

6.9.12 The Contractor shall immediately report to the appropriate government representative if any Contractor employee filling a sensitive position receives an unfavorable NACI adjudication, or if information that would result in an unfavorable NACI becomes available. The Contractor shall notify the COR, CO, and Security Office within 5 working days if at any time a Contractor employee has privileges revoked to a DoD data or system data because of security concerns.

6.9.13 The Contractor shall immediately deny access to any automated information system (AIS), or network to the Contractor employee if, at any time, the individual receives an unfavorable NACI adjudication, or if directed to do so by the appropriate government representative for security reasons.

6.9.14 The Contractor shall ensure that all Contractor personnel receive information assurance (IA) training before being granted access to DoD AISs/networks, and/or Sensitive Information.

6.9.15 Operations Security (OPSEC). The Contractor shall provide OPSEC protection for all sensitive/critical information as defined by AFI 10-701, Operations Security, and the critical information list. The Contractor shall participate in the sustained OPSEC awareness training or include OPSEC training as part of their on-going security program. The OPSEC coordinator will evaluate the OPSEC posture of Air Force contract activities and operations.

6.9.16 Information Security and Force Protection. The Contractor shall comply with DoD Directive 5200.1-R, DoD Information Security Program Regulation, DoD Directive 8570.1M, Information Assurance Workforce Improvement Program, DoD Instruction 8500.2, Information Assurance (IA) 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.

6.8.9 Drug, Tobacco, and Alcohol Use Policy. The consumption of alcoholic beverages or illegal drugs by contractor personnel, while on duty, is strictly forbidden. Contractor shall immediately remove any employee who is under the influence of alcohol or drugs.

6.10 Travel

6.10.1 Local Travel

Local travel to attend meetings or events may be required at no cost to the Government. Travel within the National Capital Region commuting vicinity is considered a cost of doing business and shall not be separately reimbursed.

6.10.2 Non-Local Travel

If required, the Contractor shall perform periodic travel both within and outside the Continental United States (CONUS) for Task Order and PWS mission requirements. Reimbursement of travel costs shall be in accordance with the Joint Travel Regulation (JTR). The Contractor shall travel using the lowest cost transportation available commensurate with mission requirements.

All costs shall be agreed to in advance and reimbursed on a cost basis upon receipt of the invoice in WAWF and copies of receipts turned in to the COR. All air travel shall be booked on American flagged carriers, unless otherwise directed by the CO. No General Administrative charges and profit shall be paid on these actual costs.

6.10.3 CONUS Travel: Prior to travel, the Contractor shall coordinate with, and receive approval from, the COR at least 10 business days prior to trip.

6.10.4 OCONUS Travel: (e.g., to EUCOM and/or PACOM Area of Responsibility) Prior to travel, the Contractor shall coordinate with, and receive approval from, the COR at least 20 business days prior to trip. Theater Business Clearances shall be obtained, as necessary, prior to travel.

6.10.5 Trip Reports: Following each trip, the Contractor shall prepare and deliver Trip Reports to the COR IAW AFH 33-337, within 5 business days after each trip. Trip Reports are not required for local travel as defined in the Federal Travel Regulations. The Trip Reports shall include the following details:

- Individual Traveling

- Destination

- Dates

- Cost

- Purpose of Trip

- Participation of Traveler

- Results of Trip

- Problems/Issues

6.11 Employee Accountability & Turnover

6.11.1 Staffing of Contractor Personnel. Contractor shall provide a stable workforce, throughout the duration of the contract, by maintaining a 20% or less employee turnover rate. No positions shall remain vacant for more than 14 working days. The government shall not be billed for personnel positions left vacant over 10 calendar days unless the vacancy is due to government delay and otherwise approved by the CO.

6.11.2 List of Employees. The Contractor shall maintain a current listing of employees assigned to the task order and define who are key personnel, if applicable. The list shall include the employee's name, social security number, and level of security clearance. The list shall be validated and signed by the company Facility Security Officer (FSO) and provided to the Contracting Officer, Program Manager, and Servicing Security Activity. An updated listing shall be provided upon request by the COR or CO.

6.11.3 Contractor professionalism. The contractor shall:

• Present a professional appearance and maintain professional demeanor and conduct at all times.

• Conduct their work assignments IAW project schedules.

• Function effectively and efficiently during extended periods of high pressure and stress.

• Function as an integral member of a team of highly trained professionals responsible for the safety and security of USAF personnel and resources.

6.12 Miscellaneous

6.12.1 Freedom of Information Act (FOIA). All official Government records affected by this contract are subject to the provisions of the FOIA (5 U.S.C. 552/DoD 5400.7-R/AF Supplement).

Any request received by the Contractor for access/release of information from these records to the public (including Government/Contractor employees acting as private citizens), whether oral or in writing, shall be immediately brought to the attention of the CO for forwarding to the FOIA Manager to ensure proper processing and compliance with the Act.

6.12.2 Controlled Unclassified Information (CUI). All DoD CUI must be controlled until authorized for public release in accordance with DoD Instructions (DoDIs) 5230.09, 5230.29, and 5400.04, or DoD Manual (DoDM) 5400.07. These regulations set policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding of CUI material.

6.12.3 Privacy Act. Work on this contract may require that personnel have access to information protected by the Privacy Act. Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations when handling such information.

6.12.4 Records. All records created and received by the Contractor in the performance of this contract shall be maintained and readily accessible. Records shall remain the property of the Government.

6.12.5 Safety Concerns. The Contractor is solely responsible for compliance with OSHA standards for the protection of their employees. The Government is not responsible for ensuring that Contractors comply with “personal” safety requirements that do not present the potential to damage Government resources.

6.12.6 Project Policy. The Contractor shall comply with all industry standards. All work shall be done in accordance with all federal, local, and state laws and regulations.

6.12.7 Inherently Governmental Functions. The Contractor shall not perform inherently Governmental functions as defined in the Federal Acquisition Regulation (FAR) Subpart 7.5 in relation to this PWS.

6.12.8 Ethics. The Contractor shall not employ any person who is an employee of the US Government if employing that person would create a conflict of interest. Additionally, the Contractor shall not employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval according to DoDD 5500-7, Joint Ethics Regulation.

6.12.9 Professional Appearance of Work Space. The Contractor shall keep work space areas neat and orderly and avoid conditions leading to safety violations.

6.12.10 Non-Personal Services. The Government shall not supervise or task Contractor employees in any manner that generates actions of the nature of personal services, or that creates the perception of personal services. It is the responsibility of the Contractor to manage its employees directly and to guard against any actions that are of the nature of personal services, or give the perception of personal services to the Government or to Government personnel. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it is the Contractor’s responsibility to notify the CO immediately. Non-personal contractor services shall not be used to perform work of a policy/decision making or management nature.

6.12.11 Non-Disclosure Agreements. The Contractor and all its personnel shall not disclose to parties other than the cognizant SAF/AAIE project team and customers any customer-owned data, and shall not disclose to parties other than the cognizant SAF/AAIE project team and customers anything about the status or problems found about any project assigned through this PWS. This includes not disclosing such matters in the trade press, in marketing brochures and webpages, and in advertising. The Contractor shall ensure that assigned personnel understand the obligations required of them by the requirement for non-disclosure. The Contractor and

Contractor personnel may be required to sign non-disclosure agreements or conform to related local requirements.

6.12.12 Government Ownership of Data and Work Products. All deliverables and intermediate work products required to be furnished under this PWS shall be furnished with unlimited rights, and shall be exclusively owned, without qualification, by the Government. All data provided by SAF/AAIE's customers to the Contractor are exclusively owned, without qualification, by the government.

6.12.13 Citizenship and Communication Requirement. Contract personnel shall read, write, speak, and understand English. No foreign nationals shall be employed on this contract.

SECTION VII

7.0 DEFINITIONS, ABBREVIATIONS, AND ACRONYMS

Term/Acronym Definition AFHSIO Air Force Human Systems Integration Office AFI Air Force Instruction AIS Automated Information System CAC Common Access Card CMRA Contractor Manpower Reporting Application CO Contracting Officer. The duly appointed Government agent authorized to award or administer contracts. The Contracting Officer is the only person authorized to contractually obligate the Government.

COMSEC Communications Security CONUS Continental United States COR Contracting Officer’s Representative CPARS Contractor Performance Assessment Reporting System CSS Cascading Style Sheets. A style sheet language used for describing the presentation of a document written in a markup language like

HTML.

CUI Controlled Unclassified Information DD Form 254 Department of Defense Contract Security Classification Specification DFARS Defense Federal Acquisition Regulation Supplement DoD Department of Defense DoD 8570.1-M Department of Defense Directive, Information Assurance Workforce

Improvement Program. Specifies certifications approved as information assurance baseline certifications for the information assurance workforce, required for position category or specialty and level.

FAR Federal Acquisition Regulation FOIA Freedom of Information Act FSO Facility Security Officer FY Fiscal Year GFE Government-Furnished Equipment GFP Government Furnished Property. Facilities, equipment, tools, supplies, parts, or any other items furnished for the contractor's use by the Government.

HAF Headquarters Air Force HTML5 Hypertext Markup Language, standard markup language for creating web pages and web applications. HTML 5 is the fifth version of the HTML standard.

IA Information Assurance IAW In accordance with JavaScript or JS Programming language JTR Joint Travel Regulation NACI National Agency Check plus written Inquires

Term/Acronym Definition NCR National Capital Region NDA Non-Disclosure Agreement OO Object Oriented OPSEC Operations Security OSHA Occupational Safety and Health Administration Performance Objective The outcome associated with successful contract performance in a specific area. This is a critical success factor in achieving the organization’s mission, vision and strategy which, if not achieved, would likely result in a significant decrease in customer satisfaction or risk mission failure. Obtaining multi-services/sub-services performed at a certain measurable standard and consistently ensures success in achieving the objectives critical to the mission.

Performance Threshold The minimum performance level of a performance objective required by the Government.

POC Point of Contact PoP Period of Performance PWS Performance Work Statement QA Quality Assurance. Those actions taken by the Government to assure services meet the requirements of the Performance Work Statement.

QCP Quality Control Plan REST API Representational State Transfer Application Programming Interface SAF/AAIE Secretary of the Air Force, Administrative Assistant, Information

Management, Enterprise Business Solutions Division SAM System for Award Management SDLC Software Development Life Cycle SIPRNET Secret Internet Protocol Router Network SQL Structured Query Language SS Services Summary. A summary of the performance objective and performance threshold required by the Government in Contractor performance. Also known as a Performance Requirements Summary or Services Delivery Summary or Performance Requirements Document.

TDY Temporary Duty USAF United States Air Force WAWF Wide Area Workflow