IRSS Help Desk PWS.pdf

AFMC

Department of the United States Air Force

Information and Resource Support System (IRSS)

IRSS Help Desk Performance Work Statement (PWS)

For

AFLCMC/GBBH

Solicitation Number: FA8770-15-R-1002

19 December 2022

DISTRIBUTION STATEMENT A: Approved for public release. Distribution is unlimited. May direct questions to the Air Force Life

Cycle Management Center/Business Systems Division (AFLCMC/GBBH), 4225 Logistics Blvd, Bldg. 262, Rm 260, Wright-Patterson

Air Force Base (AFB), OH 45433-5769.

Table of Contents

1. General

1.1. Description of Services/Introduction

1.2. Scope

1.3. Requirements/Description of Services

1.3.1. Help Desk Support

1.3.2. Help Desk Metrics

1.3.3. Help Desk User Account Support

1.3.4. Help Desk Application Administration Support

1.3.5. Help Desk Information System Management Tool (ISMT)

1.3.6. Tier 3 Trouble Ticket Escalation

1.3.7. Help Desk Incident Response Support

1.3.8. Help Desk Functional Application Support

2. Services Summary (SS)

3. Government Furnished Property, Equipment & Services

4. Detailed Information

4.1. Quality Assurance

4.2. Recognized Holidays

4.3. Hours of Operation

4.4. Place of Performance

4.5. Computer and Network Access Requirements

4.6. Security Requirements

4.6.1. Common Access Card (CAC)

4.6.2. Operations Security

4.6.3. In Processing

4.6.4. Physical Security

4.7. Security of Data

4.8. Post Award Conference/Periodic Progress Meetings

4.9. Contracting Officer Representative (COR)

4.10. Privacy Act

4.11. Identification of Contractor Employees

4.12. Contractor Travel

4.13. Other Direct Costs (ODCs)

4.14. Data Rights

4.15. Rehost Option

4.16. Data Transition Support

4.17. Personal Services

4.18. Section 508 of the Rehabilitation Act of 1973

4.19. Voluntary Protection Program

4.20. Combating Trafficking in Persons Compliance Plan

4.21. Enterprise Contractor Manpower Reporting System (eCMRA) A. Appendix A – Acronym List

List of Tables

Table 1 Severity Level Definitions Table 2 Contractor Service Requirements

1. General

This is a non-personal services contract to provide support services for the Information Resource

Support System (IRSS) Help Desk Support effort. The Government will not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn, is responsible to the Government.

1.1. Description of Services/Introduction

The Contractor shall provide Help Desk support for IRSS. To accomplish the work described in the scope of the PWS, AFLCMC/GBBH must acquire services from the private (commercial) sector to perform those tasks considered non-Governmental.

1.2. Scope

The scope of the effort requires necessary personnel, related programmatic and technical services to include but not limited to on-site services (performed at the Pentagon) including AF/A5DR

Coordination, Application Administration, and Help Desk Support, Tier 1&2.

An example of Tier 1 support are those tasks that are simplistic in resolution, such as password reset, application account creation, and application permissions. An example of Tier 2 support are those tasks that are more complex, such as application navigation and connectivity and end user training. Additionally, this effort provides remote end-user support, information assurance

(IA), software maintenance services, and Planned Program Releases (Sustainment) support.

While the IRSS customer is the Air Force Directorate of Operational Capability Requirements

(AF/A5DR), located at the Pentagon, the user community spans a geographically wide collection of MAJCOM A5 offices. A thorough knowledge of the AFROC and JROC processes is vital in providing quality customer support.

1.3. Requirements/Description of Services

The Contractor shall provide necessary resources to support continuing Help Desk activities for the IRSS program.

1.4. Help Desk Support

The contractor shall provide Level (Tier) 1 and 2 Help Desk support, and identification, elevation, and tracking for Level (Tier) 3 Help Desk and sustainment support as required. Help

Desk Support personnel shall be required to request access and maintain accounts for the

Defense Information Systems Agency (DISA) instantiation of Problem Tracking Tool Trouble

Tickets. The Contractor shall implement and maintain the IRSS Help Desk during normal business hours, 8:00 AM to 5:00 PM, Monday through Friday, except for Federal holidays, and staffed appropriately to handle a 200+ call per month volume. All Tier 1 and Tier 2 Trouble

Tickets passed to the contractor by the Problem Tracking Tool must be resolved. On a case-by-case basis, the Help Desk may be required to reassign tickets to the PMO and/or customer for resolution. (CDRL A003).

1.5. Help Desk Metrics

The Contractor shall achieve resolution to identified problems, perform metrics collection and reporting, as requested by the IRSS Program Management Office (PMO), and provide Monthly

Status Report (MSR) to PMO. On an as-needed basis, the Contractor shall provide Problem

Ticket resolution descriptions to DISA MilCloud. (CDRLs A001, A002).

1.6. Help Desk User Account Support

The Contractor shall provision user accounts based on permissions outlined within the user’s

System Authorization Access Request (SAAR), known as a Defense Department (DD) 2875

Form, for access to the IRSS web application. The Contractor shall validate, track, and maintain all system access requests (DD2875) via the IRSS SharePoint site in accordance with the IRSS

Account Management Process. The Contractor shall revalidate user’s system access request form

(DD2875) by verifying user’s roles/permissions within the IRSS application to match the user’s request form to ascertain the user’s Contract Expiration Date is valid.

1.7. Help Desk Application Administration Support

The Help Desk Point of Contact (POC) shall serve as the IRSS Application Administrator and provide in-depth knowledge of software functionality and possess the ability to resolve training-related issues encountered by the user community. The Help Desk POC shall provide application training material to IRSS users, as needed. The Contractor shall provide IRSS application support to the Joint Capabilities Integration and Development System (JCIDS) process as needed. The Contractor shall provide Information Technology (IT) expertise and functional support for application administration for the AF/A5DR customer.

1.8. Help Desk Information System Management Tool (ISMT)

The Help Desk POC shall process Discrepancy Reports (DRs) in accordance with (IAW) established IRSS Help Desk procedures and enter user Change Requests (CRs) and DRs from

Problem Tracking Tool into the ISMT.

1.9. Tier 3 Trouble Ticket Escalation

In the event a Tier 3 trouble ticket arises, the Help Desk POC shall contact the IRSS Capability

Delivery Manager (CDM) at Wright Patterson Air Force Base within one (1) hour to confirm the process for resolution and/or workaround. Once notification has been given to the CDM, guidance will be given to the Help Desk POC with the appropriate steps on how to track the Tier

3 Trouble Ticket to closure. Upon Tier 3 Trouble Ticket resolution, the Help Desk POC shall notify the IRSS CDM.

1.10. Help Desk Incident Response Support

The Contractor shall comply with Incident Response in accordance with Air Force Instruction

(AFI) 17-203, Cyber Incident Handling.

1.11. Help Desk Functional Application Support

The Help Desk POC shall track documents throughout the IRSS workflow process. The

Contractor shall receive records and subtasks from other organizations, create IRSS document records, and upload files to document records, as needed. The Contractor shall create IRSS tasks and IRSS Calendar events and send to organizations.

Table 1 Severity Level Definitions

Severity Level Definition

Severity Level 1 (Critical) Prevents the accomplishment of an operational or mission essential capability.

Severity Level 2 (Major) Adversely affects accomplishment of operational or mission essential capability with no known work-around solution.

Severity Level 3 (Intermediate)

Adversely affects accomplishment of operational or mission essential capability, but a work-around solution is known.

Severity Level 4 (Minor) Results in operator inconvenience/annoyance but does not affect a required operational/mission essential capability.

Severity Level 5 (Very Minor)

Includes any other effect.

2. Services Summary (SS)

The Contractor’s performance will be assessed quarterly by a process that measures success towards achieving defined performance objectives. The Services Delivery Summary is in accordance with Federal Acquisition Regulation (FAR) Subpart 37.6, Performance-Based

Acquisition. The Contractor service requirements are summarized in the table below into performance objectives that relate directly to mission essential support. The performance threshold briefly describes the minimum acceptable levels of service required for each objective.

These thresholds are critical to achieving mission success.

Table 2 Contractor Service Requirements

SS ID Performance Objective

PWS

Para

Performance Threshold

Surveillance Method

Inspection Procedure

Frequency

Program Management

SS-1 Contractor delivers a Monthly Contractor’s Progress, Status and Management Report with acceptable content.

1.4.4.10 The Contractor shall

provide this report to summarize progress and significant events of all activities, problems encountered, and outstanding issues.

The report shall include any significant accomplishments.

Report shall be delivered in soft copy and is due no later than 15 business days after

PMO review of Monthly Status Report.

Acceptable content consists of defining monthly accomplishments for each PWS task, status and progress of problems encountered/ outstanding issues, summary significant events and other items as identified.

PMO will evaluate deliverable receipt dates and content.

Within 15 business days after the end of the month.

SS ID Performance Objective

PWS

Para

Performance Threshold

Surveillance Method

Inspection Procedure

Frequency the end of the reporting month.

It is the responsibility of the Contractor to ensure the Government received the soft copy.

3. Government Furnished Property, Equipment & Services

No Government-Furnished Items (GFI)/Government-Furnished Property (GFP) is associated with this contract.

4. Detailed Information

4.1. Quality Assurance

The Government will evaluate the Contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

4.2. Recognized Holidays

The following are Government recognized holidays and Government facilities will be closed for operations, except for mission essential personnel, on these holidays:

• New Year’s Day

• Martin Luther King Jr.’s Birthday

• President’s Day

• Memorial Day

• Juneteenth Holiday

• Independence Day

• Labor Day

• Columbus Day

• Veteran’s Day

• Thanksgiving Day

• Christmas Day

4.3. Hours of Operation

Operational Help Desk Support is from 0800 to 1700, 5 days a week, excluding Federal

Government Holidays. The Contractor may work, with prior approval of the Contracting Officer, extended hours to ensure timely completion of essential work. The Contractor shall at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

4.4. Place of Performance

The place of performance of this effort shall be at the Pentagon (USAF A5R-P). There are accommodations for a single workspace at the Pentagon. This space includes parking on

Pentagon Reservation.

4.5. Computer and Network Access Requirements

In accordance with Air Force Guidance Memorandum to AFMAN 17-1301, Computer Security

(COMPUSEC), 10 February 2017, all Contractor personnel accessing Government information systems (ISs) shall comply with the following prior to accessing the IS:

a) All authorized users shall complete DoD Cybersecurity (formerly Information

Assurance) training prior to being granted access to a Government IS. IA training shall be re-accomplished annually by the user and compliance reported to the Organizational

Information Assurance Officer (IAO)/Cybersecurity Liaison. A publicly accessible version of the DoD IA training is located on the Information Assurance Support

Environment (IASE) website:

http://iase.disa.mil/eta/ProductDownload/awareness_download.html.

b) For each IS, Contractor personnel shall request IS access via DD Form 2875, SAAR, or equivalent procedures as required by the subject IS, documenting DoD Cybersecurity

Awareness Training, justification for access, and clearance/background investigation verification as referenced by DoD 5200.2-R and AFI 31-501, Personnel Security

Program. Please note: Authorized (Non-Privileged) users shall indicate IT Level III in

Section III, Block 28c of the DD Form 2875. In this context, IT Level is synonymous with ADP Level and AIS Level.

c) Shall possess appropriate and current personnel security investigation commensurate with assigned duties. Please note: IT Level III requires a NACI investigation in accordance with the Wright-Patterson AFB Supplement to AFI 31-501.

d) For each IS, Contractor personnel shall complete and sign Air Force Form 4394 – Air

Force User Agreement – Consent to Monitoring.

e) For each IS, Contractor personnel shall complete any applicable System Rules of

Behavior and must read and agree to abide by AFMAN 17-1201, User Responsibilities and Guidance for Information Systems.

f) For each classified IS, Contractor Personnel shall complete a Standard Form 312, Nondisclosure Agreement, according to AFI 31-401, Information Security Program

Management.

g) Contractor personnel must obtain an approved hardware token, e.g., DoD Common

Access Card (CAC), according to current IS processes prior to obtaining access.

The Committee on National Security Systems Instruction (CNSSI) 4009, Information Assurance

Glossary, defines Privileged User as, “A user that is authorized (and, therefore, trusted) to perform security-relevant functions that ordinary users are not authorized to perform.” AFMAN

17-1301 defines a privileged user as, “authorized user who has access to IS control, monitoring, http://iase.disa.mil/eta/ProductDownload/awareness_download.html or administration functions.” Examples include, but are not limited to, System Administrators, System Developers/Programmers/ Engineers with access to production Government systems, and

Information System Security Officers (ISSOs). Contract personnel serving as privileged users shall comply with AFMAN 17-1301, Paragraph 4.2.2, which includes the following highlighted requirements:

a) Shall require access via DoD PKI user authentication.

b) Shall meet all requirements of authorized users.

c) Shall apply for IS access as an Information Technology IT Level I (Privileged) or IT

Level II (Limited Privileged) user on the DD Form 2875, within Section III, Block 28c, in accordance with DoD 5200.2-R, AFI 31-501, AFMAN 17-1301, and AFMAN 17-

1303. In this context, IT Level is synonymous with ADP Level and AIS Level. Notably, an IT Level II’s work must be technically reviewed by an IT Level I.

d) Shall possess appropriate and current personnel security investigation (e.g., NACLC, SSBI, etc.) commensurate with assigned duties. Please note: IT Level I requires an

SSBI investigation in accordance with AFI 31-50. IT Level II requires a NACLC investigation in accordance with the Wright-Patterson AFB Supplement to AFI 31-

501.

e) Shall be position-certified according to DoD 8570.01-M and qualified according to

AFMAN 17-1303, Cybersecurity Workforce Improvement Program.

f) Shall complete a Privileged Access Agreement according to DoD 8570.01-M.

g) Shall only access data, control information, software, hardware, and firmware as authorized in the performance of official/assigned duties and with a valid need to know.

h) Shall maintain separation of duties and least privilege, with users maintaining separate accounts, day-to-day or “non-privileged” and administrative or “privileged” functions.

i) Shall not share privileged user accounts between users

4.6. Security Requirements

The Contractor shall be responsible for assuring that all employees comply with all security requirements imposed by the local commander at all times while his employees are on the installation and shall follow instructions of the local organizational commander pertaining to security. The contractor shall maintain a minimum of a secret security clearance.

National Agency Check with Written Inquiries Contract employees require at a minimum a favorable National Contractor will require access to Restricted Data and Formerly Restricted

Data. Refer to AFI-31-501 WPAFB supplement. Commanders may recommend to the

Authorizing Official (AO) that interim AIS access be granted. Commanders may waive, on a case-by-case basis, the investigative requirements for access to AIS pending completion of a

National Agency Check with Local Agency (NACI/T1), National Agency Check with Local

Agency and Credit Check (NACLC/T3), Access National Agency Check and Inquiries

(ANACI/T3), or Single Scope Background Investigation (SSBI/T5), after favorable review of the completed personnel security questionnaire for the investigation. The contract employee will need to submit a DD form 2875, SAAR and/or a DD Form 2842 PKI Certificate of Acceptance and Acknowledgement of Responsibilities to obtain AIS access.

4.6.1. Common Access Card (CAC)

Individuals entrusted with access to Federal property and information systems must not put the

Government at risk or provide an avenue for terrorism. Contractor personnel requiring credentials shall comply with and meet the credentialing standards, in accordance with

Homeland Security Presidential Directive 12 (HSPD 12) and DODI 5200.02 which requires at a minimum a favorably adjudicated National Agency Check plus Written Inquiries (NACI) with fingerprinting to obtain access to AF information systems, sensitive information, and receive credentials.

The contractor shall complete a Request for Identification Credential or CAC for each employee requiring access Federal property. The request shall be submitted to the PMO Security Manager or the AFLCMC/HI (WP) Security Office who will notify the contractor of the current procedure for obtaining a CAC and the governing regulations and policies. For the CAC application, a company sponsored e-mail address must be provided for each contractor employee. For employees not requiring a CAC but requiring access to Government computer or network resources, the contractor shall obtain valid, DoD-approved alternative forms of the PKI certificate or external certification authority (ECA).

CACs will be issued and returned in accordance with Air Force Federal Acquisition Regulation

Supplement (AFFARS) Subpart 5352.242-9001, DoDI 5200.46, DoD Investigative and

Adjudicative Guidance for Issuing the CAC. AFI 36-3026_IP V-1, Identification Cards for

Members of the Uniformed Services, Their Eligible Family Members, and Other Eligible

Personnel.

When an investigation is not favorably adjudicated or potential derogatory information is discovered, the local security office will request a copy of the investigative file and provide the contract company a determination of whether or not the Director or his Designated Appointee accepts the risk associated with that individual. If risk is accepted, the proper IT designation will be input through the AFLCMC/HI (WP) Unit Security Manager via the 88th ABW/IP Personnel

Security Office. .

Personnel Security Investigation (PSI) Requirements for IT Level positions are defined in DoD

5200.2-R, DoD Personnel Security Regulation, Appendix 10 and AFI31-501, WPAFB

Supplement Section 3.27. Performance of these types of duties require a favorably completed

Personnel Security Investigation also known as a trustworthiness determination; they do not result in clearance eligibility. The investigations are submitted thru the government Security

Manager.

• IT Level I duties require a favorably completed Single Scope Background Investigation

(SSBI) and a periodic reinvestigation every 4 years 10 months.

• IT Level II duties require a favorably completed National Agency Check Local Agency

Check (NACLC) and a periodic reinvestigation every 9 years 10 months.

• IT Level III duties require a favorably completed National Agency Check with Written

Inquiries (NACI)

4.6.2. Operations Security (OPSEC)

Operations Security (OPSEC) requirements are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. A

Critical Information List will be provided by the government. OPSEC will be applied throughout the lifecycle of the contract. Contractor personnel shall participate in the OPSEC program (e.g., training education and practices). OPSEC surveys, to measure the effectiveness of the OPSEC program, will be conducted by the government. The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use.

At the close of each work period, government facilities, equipment, and materials shall be secured.

4.6.3. In Processing

For those contractor employees requiring access to Federal Installations , the company’s Facility

Security Officer (FSO) or the Contractor's Contract Manager (or alternate) shall complete a Visit

Authorization Request (VAR) and submit it to the AFLCMC/HI WPAFB Security Office or

PMO Office Security Manager (OSM) via the Joint Personnel Adjudication System (JPAS) to

SMO Code WE1MFHYN6 on all classified work, a written VAR on company letter head for all unclassified work. The VAR shall include each contractor employee's full name, date of birth and social security number.

Upon in-processing, the contractor must submit a DD Form 2875, SAAR to the Government

CDM for signature. Part III of the initial and final DD Form 2875 must be completed by the

Security Manager (SM)/OSM. Submission of the DD Form 2875 will start a 10 work-day timeframe for establishment of a Government e-mail account. The contractor must have at a minimum a favorable National Agency Check with Inquiries (NACI) or an Interim NACI

Waiver signed prior to network access. Requests for initial NACIs are handled between the Unit

SM and the FSO. The SM will contact the 88th Information Protection Office to have an e-Qip account created for the contractor employee.

Contact information for the AFLCMC/HIQ (WP) Security Office and the SM: AFLCMC/HIQ

WP Security Office, Building 266, Room A212, (937) 257-8873.

4.6.4. Physical Security

The Contractor shall be responsible for safeguarding all Government equipment, information and property provided for Contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

4.7. Security of Data

The Contractor may be required to have access to live planning, personnel, and other current systems data during the performance of this contract. Any information, records, or data to which the Contractor may have access to will be of a sensitive nature. The Contractor shall not divulge any information about Government files, source selection activities and processes, or any other sensitive information to anyone not authorized access to such information. Each Contractor employee shall be required to sign a non- disclosure agreement.

4.8. Post Award Conference/Periodic Progress Meetings

The Contracting Officer (CO), Contracting Officer Representative (COR), and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings, the CO will apprise the Contractor of how the Government views the Contractor's performance and the Contractor shall apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart

42.5. Appropriate action shall be taken to resolve outstanding issues.

4.9. Contracting Officer Representative (COR)

The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR will be authorized to perform the following functions: Assure the Contractor performs the technical requirements of the contract;

perform inspections necessary in connection with contract performance, maintain written and oral communications with the Contractor concerning technical aspects of the contract, issue written interpretations of technical requirements, including Government drawings, designs, specifications, monitor Contractor's performance and notifies both the Contracting Officer and

Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel.

A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR will not be authorized to change any of the terms and conditions of the resulting order. The Contractor shall be prohibited from employing the Government COR who is surveying work performed under this contract during the entire period of performance of this contract. The COR (or alternate) will inform the Contractor when discrepancies occur and will request corrective action. The COR or alternate will make a notation of the discrepancy with the date, time, and discrepancy that was noted, and request the authorized Contractor representative to initial the entry and provide the appropriate corrective action.

4.10. Privacy Act

Work on this project may require that personnel have access to Privacy Act Information. As required, Contractor personnel shall adhere to the Privacy Act, U.S. Code, Title 5, Part 1, Chapter 5, Subchapter II, Section 552a and applicable agency rules and regulations.

4.11. Identification of Contractor Employees

All contract personnel attending meetings, answering Government telephones, and working in other situations where their Contractor status is not obvious to third parties shall be required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They shall ensure that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed. Contractor personnel shall be required to obtain and wear CAC identification badges at all times in the performance of this contract.

4.12. Contractor Travel

Travel is not anticipated.

4.13. Other Direct Costs (ODCs)

No ODCs anticipated.

4.14. Data Rights

This effort does not require the contractor to produce or deliver “Technical Data” as defined in

FAR 2.10.

4.15. Rehost Option

No Help Desk POC tasks anticipated in support of rehost efforts.

4.16. Data Transition Support

No Help Desk POC tasks anticipated in support of Data Transition.

4.17. Personal Services

The Government has determined that use of this contract to satisfy this requirement is in the best interest of the Government, economic and other factors considered, and this contract is not being used to procure personal services prohibited by the FAR Part 37.104 titled “Personal Services

Contract.”

4.18. Section 508 of the Rehabilitation Act of 1973

The Contractor shall meet the requirements at FAR 39.2. FAR 39.2 implements Section 508 of the Rehabilitation Act of 1973, (29 U.S.C. 794d), and the Architectural and Transportation

Barriers Compliance Board Electronic and Information Technology Accessibility Standards (36

CFR part 1194). Section 508 (as amended) of the Rehabilitation Act of 1973, (29 U.S.C. 794d) established comprehensive requirements to ensure (1) Federal employees with disabilities are able to use information technology to do their jobs, and (2) members of the public with disabilities who are seeking information from Federal sources will be able to use information technology to access the information on an equal footing with people who do not have disabilities. Federal agencies must make information and data available by an alternative means if compliance with the standards would result in an undue burden. The changes apply to all

Contractors (including small businesses) that manufacture, sell, or lease electronic and information supplies or services.

Exemptions:

Micro purchases made before 01 April 2005; Electronic Information Technology (EIT) purchased for national security systems; EIT acquired by Contractor incidental to a contract; EIT located in spaces frequented only by service personnel; EIT that would impose an undue burden on the agency.

4.19. Voluntary Protection Program

APPLICABILITY: Not applicable; this effort is not performed at Wright Patterson Air force

Base for this contract.

4.20. Combating Trafficking in Persons Compliance Plan

The requirements of the compliance plan are specified in contract clause 52.222-50—

Combatting Trafficking in Persons (Mar 2015), paragraph (h).

4.21. Enterprise Contractor Manpower Reporting System (eCMRA)

The Contractor shall report ALL Contractor labor hours (including Subcontractor labor hours) required for performance of services provided under this contract for the Air Force via a secure data collection site. The Contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each

Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each year.

Contractors may direct questions to the eCMRA help desk, http://www.ecmra.mil/.

eCMRA -- Unit Identification Code (UIC) is FFHYN0

Reporting Period: Contractors are required to input data by 31 October of each year.

http://www.ecmra.mil/

A. Appendix A – Acronym List

Acronym Term

ADP Automated Data Processing

AFB Air Force Base

AFFARS Air Force Federal Acquisition Regulation Supplement

AFI Air Force Instruction

AFLCMC Air Force Life Cycle Management Center

AFMC Air Force Materiel Command

AIS Automated Information System

ANACI/T3 Access National Agency Check and Inquiries

AO Authorizing Official

CAC Common Access Card

CDM Capability Delivery Manager

CDRL Contract Data Requirements List

CM Configuration Management

CNSSI Committee on National Security Systems Instruction

CO Contracting Officer

COA Course of Action

COMPUSEC Computer Security

CONUS Continental United States (excludes Alaska and Hawaii)

COR Contracting Officer Representative

COTR Contracting Officer’s Technical Representative

COTS Commercial-Off-The-Shelf

CR Change Request

CSV Character Separated Values

CVS Contractor Verification System

DCO Defense Connect Online

DD Defense Department

DD250 Department of Defense Form 250 (Receiving Report)

DFARS Defense Federal Acquisition Regulation Supplement

DISA Defense Information Systems Agency

DoD Department of Defense

DoDI Department of Defense Instruction

DR Discrepancy Report

E&I Engineering and Integration

ECA External Certification Authority eCMRA Enterprise Contractor Manpower Reporting System (eCMRA)

EIT Electronic Information Technology

ESC Electronic Systems Group

FAR Federal Acquisition Regulation

FSO Facility Security Officer

GFE Government Furnished Equipment

GFI Government Furnished Information

GFP Government Furnished Property

HTML Hyper/Text Mark-up Language

IA Information Assurance

IAO Information Assurance Officer

IASE Information Assurance Support Environment

IAW In Accordance With

IRSS Information and Resource Support System

IS Information System

ISMT Information System Management Tool

ISSO Information Systems Security Officer

IT Information Technology

IPT Integrated Process Team

JCIDS Joint Capabilities Integration Development System

JPAS Joint Personnel Adjudication System

JTR Joint Travel Regulation

MAJCOM Major Command

MSR Monthly Status Report

NAC National Agency Check

NACI National Agency Check Inquiries

NACI/TI National Agency Check with Local Agency

NACLC/T3 National Agency Check with Local Agency and Credit Check

OCI Organizational Conflict of interest

OCONUS Outside Continental United States (includes Alaska and Hawaii)

ODC Other Direct Costs

OSD Office of the Secretary of Defense

OSM Office Security Manager

PDF Portable Document Format

PIN Personal Identification Number

PMO Program Management Office

POC Point of Contact

PoP Period of Performance

PSI Personnel Security Investigation

PWS Performance Work Statement

QASP Quality Assurance Surveillance Plan

SAAR System Authorization Access Request

SM Security Manager

SMART System Metric and Reporting Tool

SOA Service Oriented Architecture

SS Services Summary

SSBI/T5 Single Scope Background Investigation

SSRS SQL Server Reporting Services

TIM Technical Interchange Meeting

TDY Temporary Duty Station

USC United States Code

VAR Visit Authorization Request

VTC Video Teleconference

WSARA Weapon Systems Acquisition Reform Act

XML eXtensible Markup Language