Draft MDDV PWS_27 Jan 22 SSN.docx

PERFORMANCE WORK STATEMENT

A procurement by the U.S. General Services Administration Region 5 Contracting Division on behalf of

CLIENT AGENCY:

Air Force Life Cycle Management Center (AFLCMC)

CLIENT PROGRAM:

Medium Altitude Unmanned Aerial Systems (WII)

PROJECT TITLE:

MQ-9A Technical Order Management Agency Production & Sustainment

PROJECT NUMBER:

47QFLA22K0006

Original Version Dated:

October 18, 2021

Version 4, Dated 2022.01.12

Post Award Document Revision History

Contents

1 INTRODUCTION

1.1 Organization

Air Force Material Command’s (AFMC) Air Force Lifecycle Management Center (AFLCMC), Medium Altitude Unmanned Aircraft Systems (MAUAS) logistics division is responsible for providing Unmanned Aircraft Systems (UAS) acquisition management services, logistics sustainment, conducts research, development, as well as test and evaluation for the MQ-9A Reaper and classified Unmanned Aircraft Systems. The division maintains a high level of mission capability and availability with ongoing modifications and fielding of the MQ-9A. Additionally, the division supports ACC, USSOCOM, AFSOC, and ANG requirements.

1.2 Objective

The purpose of this contract effort is to ensure continued MQ-9A enterprise availability of verified United States Air Force (USAF) and Original Equipment Manufacturer (OEM) technical data, formatted in the most current-issue S1000D standard, viewable in a next-generation Interactive Electronic Technical Publication (IETP).

1.3 Scope

This effort will provide end-users with USAF verified, current-issue S1000D compliant, MQ-9A aircraft maintenance data, Ground Control Station (GCS) data, and weapons delivery manuals as required by the System Program Office (SPO). Additionally, published data will be accessible via a current-issue S1000D compliant, MIL-STD-3048 compliant, and Technical Manual Contract Requirements (TMCR) compliant tool suite, as a stand-alone and web-based IETP for the duration of the Period of Performance (PoP).

1.4 Background

American Data Solutions (ADS) currently converts USAF supplied OEM and USAF source data to current-issue S1000D compliant technical data for electronic publication, display, and distribution. The Maintenance Digital Data Viewer (MDDV) is the currently fielded next-generation IETP viewer for all MQ-9A enterprise technical data, replacing the SDL Live Content S1000D viewer, previously provided by the platform OEM. Converted source data provided by the OEM and USAF MQ-9 SPO is quality assured and viewed with the MDDV under this effort.

1.5 Applicable Documents

The documents (i.e., certifications, specifications, standards, policies, and procedures), versions current at the time of contract/order award, identified in the list below are incorporated with the same force and effect as provided in full text. Succeeding revisions may be substituted or included as required with full notice and disclosure to the contractor. The Government will provide access to available documents and technical information as required and upon contractor request, if not available via a hyperlink within this PWS.

American National Standards Institute (ANSI)/International Standards Organization (ISO) /American Society for Quality (ASQ) 9001: 2015

Technical Order (T.O.)

00-33A-1109

2 REQUIREMENTS AND TASKS

2.1 General Performance Requirements

2.1.1 Resources

Unless otherwise stipulated, the contractor shall furnish or provide all personnel, personnel management and supervision, all related internal supporting business functions (including background and “overhead” personnel), materials, supplies, equipment, and facilities to perform the full range of services required by this PWS.

2.1.2 General Communication

Regular and direct contractor interface with the Contracting Officer (CO), the Contracting Officer’s Representative (COR), and other identified Government representatives are mandatory. The contractor shall not contact nor take direction from unauthorized Government representatives under any circumstances.

2.1.3 Identification

All contractor personnel shall be required to wear Government-approved or provided picture identification badges to distinguish themselves from Government employees when working at a government site. Additionally, the contractor shall comply with all visitor identification requirements when visiting the Government site. When conversing with Government personnel during business meetings, over the telephone, or via electronic mail, contractor personnel shall identify themselves to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors shall identify themselves on any attendance sheet or coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractors occupying collocated space with the Government should identify their workspace area with their name and company affiliation.

2.1.4 Business Relations

A primary element of project success is the business relationship between the contractor and Government representatives. Within this context, the Government will monitor the contractor’s contribution to business relations and provide feedback when required. The contractor shall make every effort to establish and maintain clear and constant communication channels with the Government primaries (CO, COR, and other identified Government representatives) of the contract/order for the purpose of:

· Promptly identifying PWS and/or business relationship issues concerning controversy and the bilateral development and implementation of corrective action plans.

· Ensuring the professional and ethical behavior of contractor personnel.

· Maintaining effective and responsive subcontractor management (if applicable).

· Ensuring the contractor support team is fully aware and engaged in strengthening the interdependency between the contractors and their government counterparts.

· Facilitating contractor–Government collaboration for continuous improvement in performing PWS tasks, reducing risks and costs, and meeting the mission needs.

2.1.5 Contractor Response

The contractor shall ensure prompt response to Government inquiries, requests for information, or requests for contractual actions.

2.1.6 Professional Appearance

Contractor personnel shall present a neat and professional appearance appropriate to the work being performed at all times when interacting with Government representatives, working in Government facilities, or representing the Government at meetings or before third parties.

2.2 General Meeting Requirements

The contractor shall participate in the following meetings. Nothing discussed in any meetings or discussions between the Government and the contractor shall be construed as adding, deleting, or modifying the contractual agreement without written authorization from the CO. (DI-ADMN-81250B, A001, Conference Minutes)

2.2.1 Initial Business/Kickoff Meeting

Within 20 business days following the contract/order award (or other time mutually agreed between the parties), the contractor shall meet with GSA (General Services Administration) CO, GSA COR, and other identified Government representatives to ensure a mutual understanding of the requirements, goals, expectations, end products, and objectives of the contract/order. The contractor shall discuss the overall understanding of the project and review the background information and materials provided by the Government. Discussions will also include the scope of work, deliverables to be produced, how the efforts will be organized, and project conducted; assumptions made/expected end results. A concerted effort shall be made to gain a thorough understanding of the Government's expectations. However, nothing discussed in this or any subsequent meetings or discussions between the Government and the contractor shall be construed as adding, deleting, or modifying any contract/order requirements, including deliverable specifications and due dates. The contractor shall also address the status of any issues that will affect contractor start-up/ramp-up toward achieving full service/support capability. The contractor will be responsible for taking minutes of this meeting.

2.2.2 Ad hoc Technical / Work Status

If requested by the Government, the contractor shall participate in quarterly status meetings or ad hoc technical meetings at a mutually agreeable time and place to discuss tasking, work progress, technical problems, performance issues, or other technical matters. During these meetings, the contractor shall at least provide accomplishments, problems and issues, and planned actions. For quarterly status meetings, the contractor shall review the previous three months' performance and achievements and detail the upcoming three months of expected performance goals. The contractor shall take minutes of these meetings. These meetings will occur at a time and place mutually agreed upon by the parties.

2.2.3 Contract Administration Meetings

The CO may require the authorized contractor representative to meet or participate in a teleconference with authorized Government personnel to discuss performance or administrative issues as often as deemed necessary. The contractor may also request a meeting with the CO when deemed necessary. The content of meetings shall be documented in writing, as agreed between the parties. Minutes shall be approved by both parties and shall be included in the Government contract file.

2.3 Program/Project Management

2.3.1 General Program/Project Management Requirements

The contractor shall be solely responsible for managing the work performed in the execution of the contract/order. This includes the responsibility to:

· Assign appropriate resources to each task.

· Maintain clear organizational lines of authority.

· Ensure effective task management and administration, following the requirements set forth in the PWS.

· Maintain the personnel, organization, and administrative control necessary to ensure that the work delivered meets the specification requirements.

· Establish and use proven policies, processes, analyses, and best practices.

· The contractor shall be fully responsible for management, control, and performance of any subcontractor used in support of the contract/order. Use of a subcontractor on the contractor’s team shall not relieve the prime contractor of responsibility nor accountability in the execution of the contract/order

Additionally, the contractor shall:

· Bring problems or potential problems affecting performance to the attention of the CO as soon as possible.

· Notify the COR, CO, and other identified Government representatives immediately of any projected, anticipated, or known delays that may impede contactor performance.

· When requested, deliver written reports to the CO to memorialize all verbal reports.

· Provide, in writing, the results of all meetings in which proposals are put forth that have the potential for affecting and/or changing contract agreements, requirements or conditions, and these shall be brought to the attention of the CO.

2.3.2 Reserved

2.3.3 Phase-Out Support

The contractor shall provide phase-out support in accordance with the phase-out plan as required per PWS paragraph 4.7.

2.4 Interactive Electronic Technical Publication (IETP)/E-Tool Requirements

The contractor shall ensure all users have the ability to submit requests for access to the system (in accordance with Common Access Card (CAC) verification), research tech data, navigate through the data using the inserted links, utilize the commercially available help desk, and receive change notifications without interruption. The government will address additional security configuration on the client-side, which could affect standard CAC verification.

The viewer must possess the following capabilities at a minimum:

· Technical data shall be developed and displayed in an IETP format using the Aerospace and Defense-Aerospace Industries Association (ASD-AIA) S1000D 4.1 specification, IAW MIL-STD 3048.

· The IETP shall support Condition Based Maintenance (CBM+) capability IAW DoDI 4151.22, p 4.f.

· The IETP solution for field use shall be used for the verification of developmental and notional data, as a part of the In-Process Review (IPR) and Post-Publication Review Process (PPR), IAW TO 00-5-3, p 3.8.6.2

· The IETP software and cradle-to-grave data management process shall have Cybersecurity Maturity Model Certification (CMMC) IAW Federal Acquisition Regulation (FAR) 52.204-21, Defense Acquisition Regulation Supplement (DFARS) Clause 252.204-7008 and 252.204-7012

The viewer shall also possess the following capabilities:

· AFNET certification

· Ability to be stored and managed in the Enhanced Technical Information Management System (ETIMS)

· Live Wire© or like wire tracing diagnostic capabilities upon delivery of OEM source data

· Pop-up indications for Maintenance Advisories, Emergencies and Urgent Actions

· An integrated AFTO forms submission process

· Ability to burn MQ-9 Task Order data set to a CD for delivery to geographic separated locations

· Ability to operate in a stand-alone, disconnected mode

· Ability to load Time Compliance Technical Order (TCTO) information per aircraft tail numbers

· Dashboard analytic capabilities

· Automated Val/Ver tool

· Ability to filter by Equipment ID, Software Version, and Tail Number

· Ability to print (i.e., print a full checklist)

· Ability to display Caution/Warning hyperlinks

· Ability to manually configure viewable A/C and GCS data and save said configuration

· Ability to auto-configure data modules if applicability is set and applies to multiple data modules (i.e., A/C and weapons)

· Ability for users (by role) to view previous versions of tech data

· Ability for users to identify where current data has been changed or updated Ability to grant users access by roles

· Ability to access the system using a Common Access Card (CAC)

· Ability to author organic changes with the use of an Air Force direction tool

· Complete IETM search functionality

· Open compatibility on multiple OS/iOS/Android/PC devices

2.5 Product Support Management

2.5.1 Technical Data

The contractor shall deliver all available OEM and USAF manuals provided in support of this effort, converted to current-issue S1000D 4.1 if needed, and made available for viewing in the IETP. Excludes conversion of MQ-9A Aircraft Maintenance and MQ-9A Weapons Loading OEM source data unless OPTION CLIN is exercised. See Section 2.5.4 below.

2.5.2 Technical Data Sustainment

The contractor shall continuously sustain the fielded MQ-9A Technical Order library, PWS Attachment F, for the duration of the PoP. This includes but is not limited to:

· All Technical Data refresh cycles

· USAF directed updates

· Emergency, Urgent and Routine updates to the library

· Out of cycle software releases for any affected MQ-9 systems

· All data changes and organic inputs to the technical data library

2.5.3 Delivery Timelines

Delivery timelines are listed below by category.

2.5.3.3 Emergency Work Stoppage

Have updated data available for preview/validation 8 business hours after receiving updated/verified source data. Post validated data to the IETM within 12 business hours of instruction by the SPO

2.5.3.4 Urgent

Have updated data available for preview/validation 40 business hours after receiving updated/verified source data. Publish validated data to the IETM within 12 business hours of instruction by the SPO.

2.5.3.5 Routine Changes

Have updated data available for preview/validation 10 business days after receiving updated/verified source data. Post validated data within 2 business days of instruction by USAF.

2.5.3.6 Routine Revisions

Have updated data available for preview/validation 20 business days after receiving updated/verified source data. Post validated data within 2 business days of instruction by USAF.

2.5.3.7 2D Graphics

The Contractor shall convert all the 2D graphics provided by the OEM (for the MQ-9 program) from CGM format to a web format and provide an IETM that supports the display and functionality of the web format graphics in all major browsers, without the use of any plugins, extensions, Flash, etc. (zero-footprint). The conversion of source OEM 2D graphics in CGM format must be completed in the timeline listed for Emergency, Urgent, and Routine.

2.5.3.8 3D Graphics

The Contractor shall convert all the 3D graphics provided by the OEM (for the MQ-9 program) from ISO format to a web format and provide an IETM that supports the display and functionality of the web format 3D graphics in all major browsers, without the use of any plugins, extensions, Flash, etc. (zero-footprint). The conversion of source OEM 3D graphics in ISO format must be completed in the span of time listed for Emergency, Urgent, and Routine.

2.5.4 Technical Data Conversion (OPTIONAL CLIN)

The contractor shall conduct the conversion and integration of MQ-9A Remotely Piloted Aircraft (RPA) Maintenance and Weapons Loading OEM source data pertaining to Technical Order 1Q-9(M)A-2 and 1Q-9(M)A-33-2-1 that is associated with new and existing capabilities to an S1000D 4.1 compliant format. Data conversion and delivery timelines shall be in accordance with the delivery schedule reflected in 2.5.3 of this PWS.

2.5.5 Training

The contractor shall maintain an online training module within the software that maintains up-to-date information on use and capabilities. Significant changes to MDDV system functionality or the user interface will require formal notification from the contractor and direct instruction to Government personnel if deemed necessary by the Government. Additionally, the contractor will supply a monthly summary of any changes made the previous month.

2.5.6 Software Maintenance

The contractor shall deliver a one-year plan within 60 days of contract award describing planned software support and software updates for the tool.

2.5.7 IETP Hosting

The contractor uses Amazon Web Services Government Cloud (AWSGC) to host the MDDV toolset and will have a backup method of IETP use via DVDs distributed via Fed Ex secure shipping; should the AWSGC solution fail for an extended period. The AWSGC solution shall include secure worldwide connectivity with a 98.9% uptime, meeting all requirements outlined in the latest revision of National Institute of Standards and Technology (NIST) Special Publication 800-53 and 800-171, and able to pass Federal Risk and Authorization Management Program (FEDRAMP) audits. The solution shall be Common Access Card enabled with a minimum of 128-bit Federal Information Protection Standards (FIPS) 140-2 encryption. The contractor shall configure the AWSGC and DVD instance of the tool to adhere to all requirements for data protection and safeguarding outlined in the MQ-9 Security Classification Guide (SCG) and support the update of the SGC as necessary.

2.6 Sustaining Engineering

2.6.1 Configuration Management

The contractor shall provide a configuration management plan (CMP) to the Government for approval. The contractor shall use SAE-649-1/B and MIL-HDBK-61A to develop the CMP. The contractor shall conduct Configuration Management (CM) of all facets of USAF material and data. Significant contract changes, engineering changes, and variance shall require written Government approval. (DI-SESS-80858D, A003, Configuration Management Plan)

2.6.2 Configuration Changes and/or Variance

All requests for changes and/or variance shall be submitted in accordance with the CMP.

2.6.3 Request for Variance

The contractor shall not produce items for acceptance by the Government that incorporate a known departure from the approved specifications unless a Request for Variance has been submitted and approved in accordance with the requirements of this PWS. The variance request shall be processed and submitted in accordance with the approved CMP. (DI-SESS-80640D, A004, Request for Variance)

2.6.4 Engineering Change Proposal (ECP) and Contract Change Proposals (CCP)

An ECP or CCP shall include a detailed description and documentation of the change and/or recommendation. The ECP shall also include a complete analysis of the proposed change's technical, interface, cost, schedule, and logistical impact(s). All ECPs and CCPs shall be prepared in accordance with this PWS and the CMP. (DI-SESS-80639D/T, A005, Engineering Change Proposal; DI-ADMN-81401C/T, A006, Contract Change Proposal)

2.6.5 Data Accession List (DAL)

The contractor shall maintain a DAL to provide a medium for identifying internal contractor data generated in compliance with the work described in this PWS. The DAL shall list all unclassified numbered documents/data, both technical and managerial. (DI-MGMT-81453B, A007, Data Accession List)

3 QUALITY

Both the contractor and the Government have responsibilities for providing and ensuring quality services, respectively.

3.1 Contractor Quality Management

The contractor shall identify and implement its approach for providing and ensuring quality throughout its solution to meet the requirements of the PWS via the contractor’s Quality Management Plan (QMP). The QMP shall describe the application of the appropriate methodology (i.e., quality control and/or quality assurance) for accomplishing performance requirements. The QMP shall meet the requirements of AS9100D Quality Management Systems - Requirements for Aviation Space, and Defense Organizations. The QMP shall describe how the appropriate methodology integrates with the Government’s requirements. The contractor shall make the QMP available to the Government for review upon request and shall obtain acceptance of the QMP by the CO as required. The contractor shall make appropriate modifications to the QMP (at no additional cost to the Government). The Government has the right to require revisions of the QMP (at no cost to the Government) should the QMP fail to deliver the quality of the services required at any time during performance. (DI-QCIC-81794/T, A008, Quality Assurance Program Plan)

3.2 Performance Based Requirements - Service Delivery Summary

Performance Standards, Acceptable Quality Levels (AQLs), and Rating Methodology are defined in PWS Attachment A, the Service Delivery Summary (SDS). The SDS criteria will be used to determine if performance requirements are met.

3.3 Government Quality Assurance

The Government will perform periodic reviews of the contractor’s performance in accordance with the Government’s Quality Assurance Surveillance Plan (QASP). The Government reserves the right to review services to be provided, including those developed or performed at the contractor's facilities, to determine conformity with performance and technical requirements.

4 DELIVERABLES

4.1 Contractor Submission

Unless otherwise specified in an attached CDRL, deliverables are to be transmitted with a cover letter, on the prime contractor’s letterhead, describing the contents, electronically through GSA’s web-based procurement system, as required, and to any other destination(s) as required per the Government’s request. The contractor shall provide hard copy deliverables as required per the Government’s request. All deliverables shall be produced using software tools/versions as approved by the Government.

4.2 Government Review

Unless otherwise specified in an attached CDRL, government personnel will have 10 business days to review deliverables (to include resubmissions) and provide written acceptance/rejection. Authorized Government representatives will notify the contractor of deliverable acceptance or provide comments in writing. The contractor shall incorporate Government comments or provide rationale for not doing so within 5 business days of receipt of comments. Government acceptance of the final deliverable will be based on resolution of Government comments or acceptance of rationale for non-inclusion. Additional changes volunteered by the contractor will be considered a resubmission of the deliverable.

4.2.1 Government Delays in Reviewing Deliverables or Furnishing Items

If contractor performance or submission of deliverables is contingent upon receipt of Government furnished items (data, equipment, materials, facilities, and support) or input, or upon Government review and approval of interim items or draft documents (collectively referred to as Government Performance), the Government shall specify, if not already specified within this PWS, when it will provide such items or input, or the time it will need to perform reviews or give approvals. If the Government fails to meet item, input, review, or approval deadlines, contractor performance or submission of deliverables shall automatically be extended one business day for each day of government delay. The contractor shall promptly advise the Contracting Officer of any delays in receipt of Government furnished items, input, reviews, or approvals.

4.3 Monthly Invoice

The contractor shall provide a monthly invoice, no later than the 15th calendar day of the month following the monthly reporting period, to be submitted simultaneously with the MSR. As applicable, the invoice shall include but is not limited to:

· Clear identification of all costs.

· Travel costs.

· Supporting documentation for travel costs. Refer to PWS 5.3 for specific requirements.

· Other Direct Costs.

· Supporting documentation for other direct costs. Refer to PWS 9.6 for specific requirements.

· As required, the contractor shall comply with line item (i.e., per individual positions, different programs, program areas, etc.) invoicing requests.

4.4 Monthly Status Report

The contractor shall provide a MSR for the prior month, no later than the 15th calendar day of the month. The MSR shall include, but is not limited to the items identified below:

Status of tasks, schedules and deliverables to include:

· A summary of tasks completed during the reporting period

· Tasks that are continuing in the current period

· Known future tasks if applicable

· Data Package errors that resulted in Change release delays

· Outstanding issues and proposed resolution actions.

· Staffing report identifying the current staff roster, all current vacancies, and staff departures.

4.5 Trip Report

For all long-distance travel, the contractor shall submit Trip Reports after completion of a trip. The contractor shall reconcile the Trip Reports with each invoice such that they can be matched month by month. (DI-MISC-81943, A002, Trip Report)

4.6 Reserved

4.7 Phase-Out Plan

During phase-out of the contract/order, which is determined to be a period of 30 calendar days prior to the lifecycle end date of the contract/order, a smooth and orderly transition between the incumbent contractor and the successor contractor is necessary to ensure a minimum disruption to vital Government business. The contractor shall cooperate to the extent required to permit an orderly changeover to the successor contractor. The phase-out will be deemed completed by the COR and/or other identified Government representatives when it is determined by the Government that the transition of property, data, and information developed as a part of the contract/order have been successfully changed over from the outgoing contractor to the Government and the successor contractor as required. Phase-out activities include, but are not limited to, the tasks below.

· Submission of official comprehensive phase-out plan.

· Daily communication of staffing status (i.e., projection of when incumbent contractor employees will off-board from the incumbent contract/order and identification of additional incumbent resources, such as a transition team, that may be needed to support the transition efforts) and overall phase out status, in accordance with the accepted phase-out plan.

· Maintain the phase out schedule included within the phase-out plan.

· Transition of supporting documentation.

· Transition of accounts (e.g., user accounts and user access).

· Knowledge transfer on the established installation, operation, and maintenance procedures of the technologies supported. The phase out plan shall clearly describe the proposed methodologies to be utilized for such transfer (e.g., written documentation, manuals, formal classroom type training, one-on-one training sessions, etc.).

· Execution and submission of phase out checklist, to include Government acceptance.

5 PERFORMANCE

5.1 Period of Performance

The anticipated period of performance is identified below.

· Base Period: 01 Jul 2022 – 30 Jun 2023

· Option Year 1: 01 Jul 2023 – 30 Jun 2024

5.2 Place of Performance

The primary place of performance is identified in the table below.

Contractor Facilities Government Location

5.2.1 Applicability of Telework

Federal contractors are not governed by Office of Personnel Management (OPM), GSA, or the individual agency policies; however, this does not prohibit contractor personnel from working at an alternate site, when/as appropriate. The contractor shall develop telework policies to comply with the following requirements and address such requirements at a generic level within their QMP. Alternate work arrangements for contractors shall be negotiated with the contractor’s own employer it remains the contractor’s responsibility to ensure the services are performed in accordance with the terms and conditions of the contract/order.

The contractor shall comply with all client agency security telework policies. The contractor shall ensure all services provided from an alternate site comply with the Federal Information Security Management Act of 2002 (FISMA) and address the following, as a minimum:

· Controlling access to agency information and information systems;

· Protecting agency information (including personally identifiable information) and information systems;

· Limiting the introduction of vulnerabilities;

· Protecting information systems not under the control of the agency that are used for teleworking;

· Safeguarding wireless and other telecommunications capabilities that are used for teleworking; and

· Preventing inappropriate use of official time or resources that violates subpart G of the Standards of Ethical Conduct for Employees of the Executive Branch by viewing, downloading, or exchanging pornography, including child pornography.

5.2.2 Performance at Contractor Facilities

Work performed at contractor facilities shall be performed according to the contractor’s standard commercial practice; however, the contractor representatives at these facilities shall note Section 5.4 Hours of Work must be available for interaction with Government employees during the core hours identified in the paragraph entitled “Normal Business Day”, except for Government designated holidays or facility closures.

5.2.3 Reserved

5.3 Travel

Travel must be coordinated and authorized by the CO, the COR, and/or other identified Government representatives prior to incurring costs. Contractor costs for travel will be reimbursed in accordance with FAR 31.205-46, in arrears. The travel costs shall be reasonable and allowable as defined in FAR 31.201 and in accordance with the limitations of the JTR.

The contractor shall invoice monthly based on cost incurred. The contractor must provide documentation in support of all travel expenses. The contactor will not be reimbursed for local travel (within a 50-mile radius of the Government/contractor’s facility) or commuter travel (commute from home to work site).

Invoice submissions including travel costs shall include completed travel expense sheets (i.e., travel voucher) for each trip and each employee who traveled. The travel expense report, receipts of $75 or more (with exceptions being lodging and transportation), and supporting documentation (e.g., approval email for exceeding per diem rates, cost comparisons, etc.) shall be submitted with the invoice. Expense report(s) must include the traveler’s name, dates of travel, destination, purpose of travel, Approval Authority documentation (e.g., copy of the e-mail authorizing travel by Government official), and cost for each trip. All travel costs shall be compiled into the Government provided travel expense sheet, PWS Attachment B, or similar document that has been determined to be acceptable by the Government. The entire submission shall be complete and organized to enable the Government to complete an efficient review. Submissions that are not complete and organized are subject to rejection.

5.4 Hours of Work

5.4.1 Standard Duty Hours Support

The contractor shall provide standard duty hours support as defined below.

5.4.1.1 Normal Business Day

A standard normal business day is defined as any 8 hours of productive labor. The contractor may have flexibility in scheduling of hours for their employees, but will ensure that employees are present for work during the core hours of 9:00am – 3:00pm Eastern Standard Time or Eastern Daylight Time as appropriate. Exceptions shall be coordinated with the COR and/or other identified Government representatives, to include short-term or long-term requirements for staggered business days or hours.

NOTE: The government will not incur any costs associated with cell-service plans, data plans or home-based Wi-Fi or LAN access to the internet

5.5 Limitations on Contractor Performance

The contractor shall NOT perform the following functions in connection with the services provided under the contract/order.

· Approve, decide, or sign as a Contracting Officer

· Negotiate with Government suppliers

· Accept or reject supplies or services

· Determine acquisition, disposition, or disposal of Government property

· Direct other contractor or Government personnel

· Determine cost reasonableness, allow-ability, or allocation

· Vote on a source selection board

· Supervise Government personnel

· Approve Government requirements or plans

· Determine Government policy

6 PERSONNEL

6.1 General Requirements

All contractor personnel shall meet the minimum general requirements listed below.

· All personnel shall be capable of working independently.

· All personnel shall have training and experience that is appropriate for the tasks to which they will be assigned.

· The contractor shall provide personnel that can conduct themselves in a professional manner and have proper telephone and e-mail etiquette, customer service techniques, and organizational skills.

· Contractor personnel performing in a leadership capacity shall be capable of directing contractor personnel and interfacing with the Government and customers.

6.2 Reserved

6.3 Training

6.3.1 Contractor Staff Training

The contractor shall provide fully trained and experienced support staff. Contractor personnel are required to possess the skills necessary to support the minimum requirements of the labor category under which they are performing. Training of contractor personnel shall be performed at the contractor's expense, except when the Government changes the requirements during performance of an on-going task, and it is determined to be in the best interest of the Government. This will be negotiated on a case-by-case basis. Training at Government expense will not be authorized for replacement personnel nor for the purpose of keeping contractor personnel abreast of advances in the state-of-the-art, or for training contractor personnel on equipment, Computer languages, and computer operating systems that are available commercially.

6.3.2 Reserved

6.4 Key Positions / Key Personnel

Key personnel are personnel proposed to perform in key positions. Key positions are those deemed essential for successful contractor accomplishment of the work to be performed. The following positions will be key positions, as identified by the Government, under the contract/task order: Program Manager.

· Program Manager: The contractor shall identify and provide a Program Manager (PM) to act as the single point of contact responsible for managing and directing the contractor’s activities with respect to this contract and for interfacing with the Government. The PM shall be responsible for all planning, organizing, scheduling, staffing, directing, controlling, orderly resource management, and reporting required in the execution of this contract.

6.5 Personnel Retention and RecruitmentC

Government review and acceptance is required for all resumes of key personnel proposed to support all firm fixed priced requirements. The contractor shall make every effort to retain personnel in an effort to ensure continuity until contract/order completion. If it should become necessary to substitute or replace personnel, the contractor shall immediately notify the COR and/or other identified Government representatives in writing of any potential vacancies and shall submit the resume(s) of replacement personnel within 14 calendar days of the notification. Additionally, for all new positions identified by the Government, the contractor shall submit the resume(s) of proposed personnel within 14 business days of the Government’s initial request. The contractor shall submit the resume(s) of all potential personnel selected to perform under the contract/order to the COR and/or other identified Government representatives through GSA’s web-based procurement system, or any other process means identified/required, for Government review and acceptance/rejection. Upon Government acceptance of a personnel resume(s), the candidate shall be available to begin performance within 14 business days. The contractor shall ensure continuity of operations during periods of personnel turnover and long-term absences. Long-term absences are considered those longer than one week in duration.

6.6 Identification of Contractor Employees

All contract personnel attending meetings, answering or responding to correspondent where their contractor status is not obvious to their parties, are required to identify themselves as such to avoid creating an impression in the minds of members of the public and other government agencies, that they (the contractors) are Government officials. They must also ensure that all documents or reports produced are suitably marked as contractor products and that contractor participation is properly disclosed.

7 GOVERNMENT FURNISHED PROPERTY/INFORMATION/ACCESS

7.1 General

The Government shall provide, without cost, the facilities, equipment, materials and services listed below. The Government furnished property and services provided as part of the contract/order shall be used only by the contractor only to perform under the contract/order. No expectation of personal privacy or ownership using any Government electronic information or communication equipment shall be expected. All property at Government work sites, except for contractor personal items will be assumed to be Government property unless an inventory of contractor property is submitted and approved by the CO/COR. Contractor personal items do not include computers, external drives, software, printers, and/or other office equipment (e.g., chairs, desks, file cabinets). The contractor shall maintain an accurate inventory of Government furnished property.

7.2 Reserved

7.3 Reserved

7.4 Data Rights

7.4.1 Source Data

USAF owns and supplies verified USAF and OEM-generated sources data to the contractor for conversion (if necessary), format quality control, and promotion to the MDDV. Source data is not modified beyond this conversion (if needed - not added to or subtracted from) in any way as a part of this effort. The USAF may direct changes to technical data outside of change packages issued by the OEM. These changes will be coordinated with the OEM with respect to any USAF directed changes. All data generated by the contractor during and after execution of this effort will remain USAF-owned data In Accordance With (IAW) Defense Acquisition Regulation (DFAR) 227.7103-6. This data may not be used or sold by the contractor without written authorization from the Government. All data supplied to the Government shall be the sole property of the Government and may not be used for any other purpose.

7.4.2 Commercial Computer Software

As required by DFAR 227.7202-3, the Government’s right to use, modify, reproduce, release, perform, display, or disclose computer software or computer software documentation is identified in the commercial license agreement. The Government shall have only the rights specified in the license under which the commercial computer software or commercial computer software documentation was obtained.

8 SECURITY

8.1 Non-Disclosure Agreements

Due to the potential sensitive nature of the data and information being worked with on a daily basis, all contractor personnel supporting the contract/order are required to complete the Government provided non-disclosure agreement/statement, PWS Attachment C, prior to assignment to the contract/order award to ensure information that is considered sensitive or proprietary is not compromised. Signed non-disclosure statements shall be provided to the COR and/or other identified Government representatives.

8.2 Industrial Security

The contractor shall comply with the provisions of DOD 5220.22-M, National Industrial Security Program Operating Manual, and TO 00-33A-1109, AF-GIG Vulnerability Management. The contractor shall ensure requirements are in place and met for safeguarding classified information and Controlled Unclassified Information (CUI). Information Security (INFOSEC)

The contractor’s Automated Information System (AIS) shall be protected such that unauthorized disclosure of classified and/or sensitive information is prevented. Software shall be encrypted with Federal Information Protection Standards (FIPS) 140-2 compliant encryption during any shipment/movement. The current requirement is FIPS 140-2, level 3, and is available via DoD SAFE for file transfer. Files may be encrypted using the encryption wizard and has already been provided to ADS free for unlimited use. The Contractor shall not divulge any information about files, data, processing activities or functions, user ID’s, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. The contractor shall mark and protect documents produced in the course of executing this contract in accordance with the MQ-9 Security Classification Guide (SCG).

8.3 Operational Security (OPSEC)

In order to reduce program vulnerabilities and to protect controlled unclassified information technologies from inadvertent disclosure, the contractor shall implement the operations security OPSEC counter measures described in the MQ-9 Program Protection Plan, Annex E.

8.5 Communications Security (COMSEC)

The contractor shall use only secure communications methods and equipment to transmit or otherwise transfer classified and sensitive but unclassified information or data. All such transmissions shall be in accordance with the appropriate Government security regulations.

8.6 Security Incidents and Violations

The contractor shall comply with all Reporting Requirements within DOD 5220.22-M, National Industrial Security Program Operating Manual. The contractor shall immediately notify the Contracting Officer of any actual security violation, security incident, or of any indication of a potential unauthorized disclosure or compromise of classified or sensitive but unclassified information.

9 SPECIAL INSTRUCTIONS

9.1 Contractor Performance Assessment Reporting System (CPARS) Assessment

Upon request by the Government, the contractor shall submit a self-evaluation of their performance at least annually utilizing a Government provided template. From time of Government request, the contractor shall have 7 business days to provide input to the GSA COR. The contractor self-assessment will then be submitted to the Government client where they will utilize this information to formulate an independent performance evaluation that will be processed through the Contractor Performance Assessment Reporting System. The requirements of the FAR and its supplements as it pertains to CPARS reporting shall be adhered to.

9.2 Personal Service

This is not a “Personal Services” contract as defined by FAR 37.104. Although contractor personnel who furnish services under the contract/order are subject to Government technical oversight, neither the Government nor a Government authorized third party contractor or representative shall oversee or supervise contractor personnel but shall provide all direction through the contractor’s designated representative(s) who is/are solely responsible for supervising and managing contractor personnel.

9.3 Privacy Act

Work on this project may require that contractor personnel have access to information which is subject to the Privacy Act of 1974. Personnel shall adhere to the Privacy act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations when handling this information. Privacy Act information is considered sensitive and appropriate safeguards shall be implemented by the contractor. The contractor is responsible for ensuring all contractor personnel are briefed on privacy Act requirements.

9.4 Section 508

Unless otherwise exempt, all services and/or products provided in response to this requirement shall comply with Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d), and the Architectural and Transportation Barriers Compliance Board Electronic and Information Technology (EIT) Accessibility Standards (36 CFR part 1194).

9.5 Close-Out Procedures

The contractor is required as a deliverable of the contract/order to provide a final invoice no later than 30 calendar days after the end of the period of performance. Additionally, the contractor shall provide a Release of Claims no later than 90 calendar days after the end of the period of performance. The contract/order will be modified for closeout.

9.6 Other Direct Costs (ODCs)

The Government may require the contractor to purchase materials and equipment and ODCs, to include hardware, software, and related supplies critical and related to the services being acquired under the contract/order. Such requirements will be identified at the time the contract/order is issued or may be identified during a contract/order by the Government or the contractor.