Draft_GATES_PWS.pdf

PERFORMANCE WORK STATEMENT

FOR

UNITED STATES TRANSPORTATION COMMAND (USTRANSCOM)

MILITARY SURFACE DEPLOYMENT AND DISTRIBUTION COMMAND (SDDC)

SDDC SYSTEMS FUNCTIONAL SUPPORT

Prepared by

MILITARY SURFACE DEPLOYMENT AND DISTRIBUTION COMMAND (SDDC)

TRANSPORTATION PROGRAMS POLICIES AND SYSTEMS DIRECTORATE

25 OCTOBER 2016

1 DESCRIPTION OF SERVICES

1.1 Background.

The Military Surface Deployment and Distribution Command (SDDC) Global Air Transportation Execution System (GATES), is an automated information system designed to support the operational requirements of the Department of Defense (DOD) for obligating, tracking, documenting, and payment of DOD cargo. SDDC requires functional support for its battalions, detachments, reserve and active units, and shippers to continue operations when necessary.

1.2 SCOPE.

1.2.1.

The purpose of the contract is to provide GATES-Surface support as required by the functional management office for the SDDC portion of GATES. The requirement is to provide support for the G35, system functional training, testing, response to functional questions related to GATES, including surface and ocean functional assistance to users. Additionally, perform actions to facilitate the resolution of Customer issues, to include, providing instructions to the Customer to perform problem resolution at their location. This requirement includes site visits to shipper locations, FT Lee, VA., Transportation School, active duty and reserve units for training assistance, virtual training for GATES users worldwide, G3 systems functional manager with system customer testing and acceptance of releases, and briefing of general GATES, and transportation information. GATES is fielded worldwide in support of military operations, reserve training and readiness for an estimated 2,500-user base.

1.2.2.

The Contractor shall plan for all tasks identified in this PWS and gather all pertinent information.

Contractor estimates and timelines shall be determined based on the deliverable due dates specified in Paragraph 1.5 (Deliverables). The Contractor shall coordinate with the Government to ensure that all activities are well synchronized and integrated within the G35 Directorate’s management efforts. All reports, studies and other identified deliverables in the Performance Work Statement (PWS) shall be prepared and submitted for Government approval or acceptance.

All functions and activities shall be task driven, and work performed shall be in accordance with applicable regulations and guidelines.

Task Area 1: Contract Level Management Task Area 2: Support

1.3 Specific Tasks.

1.3.1 Task Area 1: Contract Level Management.

This task consists of the functional activities relating to the administration and management of this effort. The contractor shall provide program management of contractor personnel performing tasks in this contract. The contractor shall designate a principal point of contact for the Government concerning technical and functional issues. These functions shall include administrative support by preparing documents, such as, briefings, point papers, and meeting minutes related to the status of the performance of this contract.

1.3.1.1 Task 1 Subtask 1: Task Order Management Plan (TOMP).

The contractor shall prepare an integrated (i.e., Government and contractor) Project Plan, which defines tasks, resources, and dependencies. The Management Plan shall include the technical and functional approach, organizational resources, and management controls of cost, performance, and schedule requirements throughout contract execution. The Draft Plan will be submitted within thirty (30) business days of contract award. The Government will review the plan and provide comments to the contractor. The contractor will submit the Final Plan, no later than five (5) business days from receipt of Government’s comments. The plan should not be a reiteration of the PWS requirements.

1.3.1.2 Task 1 Subtask 2: Monthly Status Report (MSR).

The contractor shall provide a Monthly Status Report monitoring quality assurance and configuration management. The status report will list, by each active task/project area, the accomplishments for the reporting period. The MSR shall outline the current funding status for travel and Other Direct Costs (ODCs) and include a brief synopsis of the efforts completed, deliverables provided, and conferences and trips conducted/attended during the reporting period, and an overall evaluation of the requirement to date. (Contractor name, trip location and purpose, and dates of travel shall report estimated and actual travel costs.) The report will list the deliverables for each task and any issues, problem areas, and items, which require Government action. The MSR shall include a Summary Report on Support to Ft Lee, VA., Transportation School, Active and Reserve Forces, and Customer Support Log of Actions completed. The contractor shall provide the MSR no later than the fifth business day of each month. The MSR will be submitted electronically to TPPS Org box.

1.3.1.3 Task 1 Subtask 3: Contractor Management Report (CMR).

The contractor shall report ALL direct contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract f o r Military Surface Deployment and Distribution Command (SDDC) via a secure data collection site. The contractor is required to completely enter all required data fields utilizing the following web address: http://cmra.army.mil/

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 20XX. Contractors may direct questions to the help desk by clicking on “Send an email” which is located under Help Resources on the right side of the login page.

The eCMRA site associated with this contract is Scott Air Force Base, IL.____

The Command of the Requiring Activity is SDDC.

The Unit Identification Code (UIC) for this requirement is __W0QFAA__.__

The Federal Service Code for this contract is __U012/D321___._______

1.3.2. Task Area 2: Functional Support

1.3.2.1 Task 2 Subtask 1: Software Test Plans: The contractor shall prepare and provide the Government a fully descriptive Software Test Plan in support of testing requirements for Customer Acceptance Testing (CAT) for GATES and Independent Verification and Validation (IV&V) and CAT testing. The Software Test Plan shall encompass 100 percent of the software applications to be tested using scenario based testing and assume the tester to be a typical end user. As part of the software test plans, the contractor shall create scenarios to fully test the listed platforms and systems. Scenarios shall be tied to standard data sets incorporating representative cargo records with known data format and content flaws to emulate real world data, utilizing data from SDDC's critical interfaces. Critical interfaces are Integrated Booking System (IBS), Transportation Financial Management System (TFMS), Transportation Coordinator’s-Automated Information For Movement System (TC AIMS II), Integrated Computerized Deployment System (ICODES), Integrated Surface Distribution Data Cleansing Tool (iSDDC), Marine Air-Ground Task Force (MAGAF), Deployment Support System II (MDSS II), Munitions Transportation Management System (MTMS), Army War Reserve Deployment System (AWARDS), and Distribution Standard System (DSS).

Scenarios shall be standardized and grouped by functional areas. GATES test scenarios should include testing with Hawkeye, CAISI wireless and other communication devices utilized during D-GATES operations. Software Test Plans support requirements for testing corrections to Emergency or Urgent Problem Reports submitted by users in the field. The contractor shall provide the Draft Software Test Plan no later than four weeks prior to test start. The contractor shall provide the Final Software Test Plan no later than two weeks prior to test start. Typically testing events will simulate production events and processes utilizing production-like data. Modifications to previously created plans shall be made to accommodate functional changes and additions addressed in the software change package. Discrepancies will be forwarded to the Contracting Officer’s Representative (COR) for resolution. Support of this task is estimated once per quarter.

1.3.2.2 Task 2 Subtask 2 – Test Support. The contractor shall validate and verify the software meets functional and provide a Software Report of Test within five (5) business days of test completion. The contractor shall execute GATES software test as an end user or assist field representatives to ensure proper functioning of all installation requirements and changes. The contractor shall conduct regression testing to ensure other related processes are not affected by code changes. The contractor shall follow the developer’s guidance for all possible dependent processes, which will require specific testing. Any problems or issues will be identified in the Daily Update Report (Mon-Fri), provided electronically by the contractor and submitted to the COR. These problems/issues will be discussed at the weekly GATES meeting with Government representatives during the system testing cycle. Place of performance for this task will be at

Scott AFB, IL. Support of this task is estimated once per quarter, for a period of up to 3 weeks at a time, unless regression testing is required.

1.3.2.3 Task 2 Subtask 3 – Prepare GATES Briefings and Documentation. The contractor shall prepare GATES briefing PowerPoint slides, informational documentation concerning SDDC Movement Orders & Shipping Processes/Systems Division issues, system upgrades, changes and general transportation information. All documentation will be reviewed and accepted by the Government. The contractor shall provide updated documentation and briefings as new and/or revisions of GATES. Versions will be implemented no later than five (5) business days after implementation. Documentation shall be formatted to SDDC standard and templates.

1.3.2.4 Task 2 Subtask 4- Virtual Training. The contractor shall provide the GATES user community with virtual training. Virtual training shall be provided in the form of the Continuous Learning Environment (CLE) via Defense Collaboration Services (DCS), Teleconference or Virtual Teleconference (VTC). The contractor shall be responsible for creating a training agenda and all training materials to include documentation. The contractor shall provide an After Action Report (AAR) electronically which details assistance provided during the training, participants, and points of contact, purpose of training, summary of events, observations and recommendations within five calendar days after each training session. Training shall include student rosters and assessments of the effectiveness of the training provided. Any issues or concerns with the GATES system will be captured and included in the report. Virtual training is estimated to take place four times a quarter. Training shall be IAW Department of the Army, Training and Doctrine Command, TRADOC Regulation 350-70 and TRADOC Pamphlet 525-8- 2.

1.3.2.5 Task 2 Subtask 5-Continuous Learning Environment (CLE) The CLE provides global aerial port & surface terminal community an enterprise web accessible proficiency database/capability. The contractor shall provide functional (surface) support to the Transportation School located at Fort Lee, Virginia. The contractor shall assist the Army Transportation School with updating Transportation School Program of Instruction (POI) for GATES. The contractor shall provide the T-School with GATES training. The contractor shall provide the T-School with GATES Service Now tickets response within 1 hour of documented Service Ticket. Training shall be In Accordance With (IAW) Department of the Army, Training and Doctrine Command, TRADOC Regulation 350-70 and TRADOC Pamphlet 528-8-2.The contractor shall support setup and execution of GATES courses.

1.3.2.6 Task 3 Subtask 6- Service tickets:

The contractor shall have personnel available during a core period between 0700 and 1730 hours Central Time, Monday-Friday to provide GATES customer support. The contractor shall respond to GATES trouble tickets generated from Service Now which are assigned to the G35. Problems, issues, questions, account concerns, training, etc… generated to the GATES SRC helpdesk, will be documented with a service ticket within Service Now and be resolved. The contractor shall be responsible for all service tickets up to and including Tier III level. The contractor shall determine if the problem is a functional or technical issue, or with hardware or software, isolated or systemic, and routed appropriately. The contractor shall respond within 24 hour of receipt of a call unless the service ticket is generated over the weekend or holiday, then it will be responded to within 24 hours of next business day. All responses to service tickets will be recorded in Service Now, maintained by G6. For reference and information purposes only, historical GATES data averaged an estimated 85-

100 service tickets per month. Future workload may vary depending on deployments and exercises, which may fluctuate the number of calls received. The contractor shall provide GATES level 3 system support via Service Now, for all functional service ticket requirements. The contractor will provide a response with 24 hours of receiving notice of trouble ticket.

1.3.2.7 Task 3 Subtask 7- Data Security:

The Contractor shall protect unclassified DOD data from unauthorized access or disclosure in accordance with DoDI 8582.01, “Security of Unclassified Information on Non-DOD Information Systems,” DoDM 5200.01, Volume 4, and classified information under DOD 5220.22-M, National Industrial Security Program Operating Manual, and the program’s Security Classification Guide. Contractor personnel will be required to sign non-disclosure agreements in order to perform tasks assigned under this PWS.

1.3.2.8 Task 3 Subtask 8 – Data Rights and Protections:

The Government obtains under this contract “unlimited rights” to all non-commercial executable computer software, computer software documentation, enhancements, and similar non-commercial data developed exclusively at Government expense and delivered to the Government under this contract. “Unlimited rights” means rights to use, modify, reproduce, release, perform, display, or disclose in whole or in part, in any manner and for any purpose whatsoever, and to have the ability to authorize others to do so.

1.4. Deliverables

One (1) copy of the transmittal letter with deliverable attached in electronic format to the COR.

Reports, documents, and narrative type deliverables will be accepted when all discrepancies, errors, or other deficiencies identified in writing by the Government have been corrected.

For the initial (draft) deliverables required by this PWS, the following procedures will apply:

The Government will provide written acceptance, comments and/or change requests, if any, within five calendar days from receipt by the Government of the initial deliverable.

Upon receipt of the Government comments, the contractor shall have ten calendar days to incorporate the Government's comments and/or change requests and to resubmit the deliverable in its final form, unless otherwise stated within the PWS task.

All deliverables shall meet professional standards and meet the requirements set forth in contractual documentation. Unless noted otherwise, the contractor shall provide all deliverables electronically to the COR in Microsoft Office formats pursuant to the following schedule.

Deliverables will be identified by contract number, PWS subtask, and deliverable title.

PWS Deliverable Title Delivery Schedule

Para

1.3.1.1 Task Order Management Plan (TOMP) Draft - within fifteen (15) Business days after task order award. Final – within five

(5) business days after receipt of Government comments.

1.3.1.2 Monthly Status Report (MSR) No later than the 5th business day of each month.

1.3.2.1 Software Test Plans

Draft plan 4 weeks prior to test start. Final plan 2 week prior to test start.

1.3.2.2 Software Report of Test Within 5 business days of test completion.

1.3.2.2 Daily Update Report Provided electronically to the COR daily

(Mon-Fri).

1.3.2.3 Briefing/Documentation/ After Action

Report Within 5 calendar days after each implementation

1.3.2.4 Virtual Training AAR Within 5 calendar days after each Virtual training session

1.3.2.5 CLE AAR Within 5 calendar days after each

site visit.

1.3.2.6 Service Tickets No later than 24 hours after ticket is opened opened

2.0 SERVICE DELIVERY SUMMARY

The Services Delivery Summary (SDS) represents the most important contract objectives that, when met, will ensure contract performance is satisfactory. Although not all PWS requirements are listed in the SDS, the contractor is fully expected to comply with all requirements in the

PWS.

PWS

Para

Performance Objective Performance Threshold

1.3.1.2 Monthly Status Report (MSR) 100% of the time each report is timely and accurate 1.3.2.1

Software Test Plans 95% of the time each draft and final plan is timely.

1.3.2.2 Software Report of Test 95% of tested code executes as required or is noted on discrepancy report.

1.3.2.2 Daily update report 95% of the time the report is timely, accurate, and complete.

1.3.2.3 After Action Report to

Active Duty Component (On-site Response)

95% of the time reports are delivered within five calendar days of return from site visit and 100% of the time reports contain all applicable information

1.3.2.4 After Action Report

Brigade/Battalion (On-site Response)

95% of the time the report is timely, accurate, and complete.

1.3.2.5 After Action Report

Reserve (On-site Response)

95% of the time the report is timely, accurate, and complete.

1.3.2.6 System Briefings and

Documentation

95% of the time the report is timely, accurate, and complete.

1.3.2.8 After Action Report

(Virtual Training)

95% of the time the report is timely, accurate, and complete.

3.0 GOVERNMENT-FURNISHED EQUIPMENT AND SERVICES

3.1 Government-Furnished Information (GFI)

The Government shall provide as GFI all necessary information required to perform this PWS.

GFI includes Interface Design Documents (IDDs) for Critical Interface Partners, Software Requirement Specification (SRSs), User manuals, Base-line Change request (BCR), Systems Change Request (SCR), System Problem Reports (SPR). The Government shall provide access to Collaborative Lifecycle Management (CLM) for access to all future GFI. The Point of Contact for GFI will be the COR.

3.2 Government-Furnished Equipment (GFE)

The Government shall provide computer terminals, office space, telephone/service, desks, chairs, writing paper, pens, pencils, computer disks, scissors, paper, staplers, and staples for contractor employees performing in government facilities. The Government shall provide specialized equipment to be used exclusively for the performance of work under this PWS, four (4) hand-held terminals (MC9190G) with docking stations, one barcode label printer.

A complete list with serial numbers of GFE will be provided upon task order award.

If there is a requirement to call overseas, the contractor shall call SAFB and utilize the SAFB operator to call overseas.

All GFE will be maintained IAW FAR 52.245-1, Government Property, and Army Regulation 25-2, Para 4-5.

3.3 Use and Safeguarding of GFE

GFE shall be used solely and exclusively for the performance of work under this PWS. The contractor shall safeguard GFE and take reasonable precautions to prevent fraud, waste, and abuse. The contractor shall designate at least one primary and one alternate custodian whose responsibility it is to receive, account for, and safeguard GFE.

3.4 Joint Inventory

The contractor and the COR(s) shall inspect and inventory GFE within 30 calendar days of the start of the phase-in period, and ten calendar days prior to the end of the final performance period. The inspection and inventory shall detail the material condition and quantity of such GFE and determine the exact number, location and serviceability of GFE. The contractor shall certify the GFE inspections and inventories, assume accountability for all GFE, and subsequently report any discrepancies to the COR. GFE shall not be altered without prior written approval of the COR. The contractor shall notify the Contracting Officer in writing, of any disagreement regarding the material condition of GFE within five (5) days of completion of an inspection or inventory.

3.5 Annual Inventory

The contractor shall also perform an annual inspection and inventory of GFE. These actions shall be conducted during the anniversary month of the initial joint inspection and inventory. The contractor shall submit a report to the COR within ten workdays of the date they are completed.

The report shall indicate shortage, loss, or destruction of, damage and excessive wear and tear to

GFE.

3.6 Return of GFE

The contractor may, at any time, return GFE it no longer needs for the performance of this PWS;

however, returned GFE will not be replaced by the Government, and the unavailability or lack of GFE under these circumstances will not excuse nonperformance, or justify increase in cost to the Government. The contractor shall notify the Government in writing of its intent to return GFE.

3.7 Repair vs. Replacement

GFE shall not be replaced if it can be repaired or rebuilt, to return it to the condition existing at the time it was accepted by the contractor. The contractor shall provide the COR with a comparison between the replacement cost of the equipment and the cost of parts required to repair the equipment. If the repair estimate exceeds 50% of the replacement cost, the contractor shall contact the Contracting Officer for approval to replace the item. The COR will closely monitor repair and replacement of GFE.

Any item replaced rather than repaired becomes the property of the Government. Any replacement item shall meet the same performance criteria and quality standards as the original item or better.

3.8 Warranties

The Government will furnish warranty information on all GFE. All GFE under manufacturer’s warranty shall be operated, maintained, and repaired in accordance there with. The contractor shall report to the COR any difficulties encountered in exercising manufacturers’ warranties. The contractor shall not repair GFE under warranty without COR approval. Repair and replacement of non-GFE is the sole responsibility and expense of the contractor.

3.9 Disposal, Salvage, Reclamation, and Recycling

The contractor shall contact the COR to initiate disposal, salvage, reclamation, or recycling of

GFE.

3.10 Equipment Manuals

The Government will provide access to all available equipment manuals for the equipment listed in 3.1. Manuals will be located in appropriate facilities where equipment is used. The contractor shall maintain and update equipment manuals (when received from the manufacturer).

4.0 GENERAL INFORMATION

4.1 Place of Performance

Tasks shall be performed at SAFB. 100% of the staff supporting this contract, to include the contractor manager or alternate, shall be located within the local commuting area of Scott Air Force Base, IL. This requirement is in support of short-notice on-demand training or in support any of the task areas defined in the PWS.

Workspace for no more than three (3) Contractors will be available onsite SDDC facilities. On occasion, Contractors who normally work at Contractor facilities will be required to attend meetings at SDDC, Scott AFB, IL. Contractor personnel are expected to conform to agency operating hours (0730 – 1730 CST/CDT) unless otherwise agreed upon. Work will generally consist of 40-hour work weeks, Monday through Friday, excluding federal holidays. Personnel may be required to support short notice adjustments to the daily work hours. To accommodate the Contractor’s on-site support personnel, the Government will provide controlled working space, phone, computer, fax, and connections to the Non-Secure Internet Protocol Router Network (NIPRNET), as required, at no cost to the Contractor.

The Contractor may be required to provide functional support in support of PWS paragraph 2.1.6, Rate Filing outside of the normal working hours. Prior to providing support outside of normal working hours, Contractor shall request approval on a daily basis as needed, and receive approval from the COR or the following Government personnel: TPPS, Division Deputy. The request shall include rationale for the additional support and rough order magnitude. The ROM shall include the estimation of the level of effort, to include date, hours requested (e.g. 0500 a.m.

- 0800 a.m.) labor category, rate, and cost. The first day after providing the approved support, the Contractor shall submit a spend plan reflecting actual costs to the COR.

4.2 Period of Performance

All work under this contract to include submission of all deliverables shall be completed within the one-year base period, and one twelve month option periods.

Base Period: TBD Option Period 1: TBD

4.3 Travel

Travel and Other Direct Cots (ODC) will be cost reimbursable contract line items to the Contractor. The COR must validate the anticipated travel and ODC costs prior to the Contractor incurring these costs.

4.3.1

Performance under this task order may require Contractor travel within and outside the Continental United States, as required by G35. The Government will reimburse the Contractor for travel expenses subject to Federal Acquisition Regulation and Joint Travel Regulation. All Contractor travel shall be coordinated and validated as necessary by the primary or alternate COR prior to incurring travel expenses. The Contractor shall identify personnel who will be traveling in sufficient time to obtain the lowest possible rates for airfare, rental car, and lodging.

For long distance travel, a minimum of five (5) business days advance notice from the travel commencement date is required unless mission requirements dictate otherwise. The travel request shall be in writing and contain the dates, location, and estimated travel costs. Contractor invoices (along with associated receipts) shall support all travel reimbursement requests. Actual travel costs will be reported to the COR by person, by trip within five (5) business days of completion of travel. The Government will not reimburse local travel and related expenses to the Contractor for daily travel to or from work at Scott Air Force Base, IL (SAFB) or the Contractor’s facility.

4.4 Contract Manager

The contractor shall provide a Contract Manager who shall be responsible for the performance of the work in the PWS. The name of the Contract Manager and alternate(s), who shall act on behalf of the Contractor when the Contract Manager is absent, shall be designated in writing to the Contracting Officer (CO) or (KO). The contractor shall ensure all personnel assigned to this task order meet the minimum requirements specified in the contractor’s proposal, in accordance with the generic position descriptions provided in the Alliant Small Business Government-Wide Acquisition Contract (GWAC). The contractor shall notify the CO in writing of any changes to personnel within three (3) business days after information is known.

4.5 Contractor Furnished Equipment and Services

Except for those items or services specifically stated in PWS Section 3.2 as Government-furnished the contractor shall furnish all resources necessary to perform this contract.

4.6 Information Assurance Workforce Improvement Program (IAWIP) DOD 8570.01-M, IAWIP, requires the contractor personnel performing IA functions, on either a full or a part-time basis, to receive a commercial certification. Information Assurance Contractor

Training and Certification describes which functions require a particular level of certification.

Contractor personnel assigned to those functions must achieve the appropriate certification as specified in DOD 8570.01-M, IAWIP, prior to task order award. (See Appendix 3)

Personnel in IA positions must sign a "Statement of Acceptance and Responsibilities."

Additionally, contractor personnel performing IA functions must take appropriate actions to complete continuing education and re-certification requirements applicable to their certification.

The contractor shall have their personnel properly certified at all times after task order start, unless a waiver has been granted.

Contractor personnel holding an IA certification must release their certification information to the DOD by registering their certification in the Defense Workforce Certification Application (DWCA): https://www.dmdc.osd.mil/appj/dwc/index.jsp

The contractor shall complete an on-the-job skills practical evaluation for their personnel in Information Assurance Technical (IAT) positions and provide supporting documentation indicating completion to the CO or designee. After completion of the evaluation and verification of certification, personnel will be issued an appointment letter for the performance of IA duties including a statement of responsibilities.

In addition to the baseline IA certification requirement for their level, the contractor shall ensure that personnel in IAT positions with privileged access possess the appropriate Computing Environment (CE) certification for the operating system or security related tools/devices they support, and provide supporting documentation indicating possession of the CE certification to the CO or designee.

4.7 Non-Disclosure Statements

Due to the sensitive nature of the data and information utilized on a daily basis, completion of non-disclosure statements are required by contractor personnel to ensure information that is considered sensitive or proprietary is not compromised. All contractor personnel will be required to sign a NDA. The Government will retain these documents. See Appendix 2, Non- Disclosure Agreement.

4.8 Quality Assurance

The contractor shall support Government agency reviews and audits of all services and support provided under this PWS. The contractor shall be prepared to support Quality Assurance reviews conducted by the Government. The Government reserves the right to authorize an independent verification and validation of the contractor’s procedures, methods, data, equipment, and other services provided at any time during the performance of this PWS.

4.9 Other Direct Costs (ODCs)

Prior to incurring costs, the contractor shall coordinate expenditure of ODC funds with the COR.

The Government will reimburse materials and fees incurred in the performance of the PWS based on prior coordination with the COR. ODCs may include but are not limited to: copier fees, reproduction, printing, duplication, scanning costs, binding supplies, electronic media such as tapes and CDs, postage and shipping charges, meeting facility charges, conference fees, and other related expenses.

5.0 SECURITY (PHYSICAL, PERSONNEL, INFORMATION,

ANTITERRORISM/FORCE PROTECTION AND INDUSTRIAL SECURITY)

5.1. General Security Information:

The majority of daily work associated with this PWS is at the UNCLASSIFIED level, but contractor personnel may be required to access restricted (classified areas and systems) located at various locations listed in paragraph 4.1, Place of Performance, of the PWS, which require SECRET access. Furthermore, contractor personnel with access to Information Assurance (IA) administrative privileges and/or who will monitor DOD IT systems or software as designated by DOD 8500.1/5200.2-R may be rated at the various levels listed in paragraph 5.2 below. The stipulation of the numbers and what IT/ADP levels the contractors will have is approved by the COR or the CO before the start of the task order. IT/ADP level guidance is provided in Appendix 3 of this PWS. The contractor shall not divulge any financial, planning, programming, or budgeting information without the express consent of the Government as outlined in Operational Security (OPSEC) and Information Security regulations. The contractor shall comply with all appropriate provisions of applicable security regulations. Specific security requirements are identified in the DD Form 254, DOD Contract Security Classification Specification. A completed/signed DD Form 254 is attached to the task order.

5.2. Personnel Security Requirements:

The contractor/subcontractor, and/or partner personnel performing services under this task order, shall be citizens of the United States of America. Overall, all contractor personnel shall possess the appropriate personnel security investigation for the position occupied. Contractor personnel are required to have a background investigation which corresponds with the sensitivity level of tasks to be performed. The following guidance will be followed when determining background investigation and clearance levels for this task order.

IT-II/ADP-II/Non-Critical Sensitive Positions:

Those positions in which the contractor is responsible for the direction, planning, design, operation, or maintenance of a computer system, and whose work is technically reviewed by a higher authority of the ADP-I category to ensure the integrity of the system.

(IT-II/ADP-II/Non-Critical Sensitive) Background Investigation Requirements:

Positions designated by the Government at the Non-Critical Sensitive/ADP-II/IT-II rating require a T3 investigation/ National Agency Check with Local Credit (NACLC) (or acceptable periodic reinvestigation) favorably adjudicated (a favorable adjudication grants eligibility at the SECRET level as prescribed by DOD 5200.2-R). The IT-II/ADP-II requirement mandates the contractor have a minimum Facility Clearance Level (FCL) at the SECRET (or higher) level due to investigation submissions as directed in DOD 5220.22-M, DOD 5200.1-R and JPAS.

5.3. Facilities Clearance Level (FCL):

The contractor must have a valid FCL at the SECRET level. Interim FCLs are acceptable provided they are not expired. FCL procedures and security guidelines for adjudicative requirements are outlined in DOD 5220.22-M and DOD 5200.2-R. FCLs and Interim FCLs must be awarded by the Defense Security Service (DSS) or DOD Consolidated Adjudications Facility (DOD CAF).

5.4. Personnel and Facilities Clearance Validation:

Upon contract task order award, the contactor shall submit the names of contractor personnel to the COR, who will coordinate with SDDC G34 Industrial Security Program Manager for vetting through JPAS to ensure investigative and clearance requirements have been satisfied. This will be completed before the COR/Trusted Agent (TA) accesses the Trusted Associate Sponsorship System (TASS) and submits the request for issuance of the CAC to the contractor’s personnel. If a contractor’s employee does not have the required investigative or security clearance level based on the Government’s determination, the contractor’s personnel will be denied the ability to work in support of this task order and the employee’s information will not be loaded into TASS.

5.4.1. Prior to performance start date, permanently assigned contractor employees on Scott AFB (SAFB) will require a visit request for the current period of performance posted in Joint Personnel Adjudication System (JPAS) to Security Management Office (SMO): SSC-CONT.

The visit request will annotate the task order number in the POC block of the visit request and the name of the COR/CO in the phone number block. All SAFB permanently assigned contract employees shall in process at the Protection Services Center (PSC) on the first day of contract start at SAFB.

5.5. Common Access Card Issuance Procedures:

Upon notification by SDDC G34 that contractor personnel meet the required investigative and clearance levels, the personnel will be loaded in TASS for an expiration on their CAC for the base year, plus four option years, for a five year total, if the task order is fully funded. If the task order is unfunded or funded on a yearly basis requiring recertification of funding by SDDC G8, CACs will only be loaded for the current period of performance.

5.6. Scott Air Force Base/HQ SDDC/USTRANSCOM Physical Access:

Upon receipt of the CAC, permanently assigned contractor personnel located at HQ SDDC/USTRANSCOM at SAFB, IL, may obtain the AF 1199 (Restricted Area Badge) if the employee meets the requirements set forth in the SAFB Instruction 31-101. Only personnel assigned physically on SAFB at least four (4) days a week will be issued the AF 1199. The Government will provide unrestricted access to facilities, consistent with security clearance and need to know, necessary for the on-site personnel to perform their work in accordance with the task order. Visits to SAFB by contractor personnel who do not possess the CAC will be facilitated by the COR/CO sponsoring the employee through the online base access system.

5.7. Visits to HQ SDDC/USTRANSCOM Buildings:

Any visit(s) by contractor personnel not permanently assigned to this task order (i.e., company presidents, company security managers, contractor personnel not permanently assigned at SAFB, etc.) will require an electronic visit request be submitted using JPAS. JPAS visits can be forwarded to SMO code: USTC-SDDC.

5.8. Security Training:

Contractor personnel physically assigned at HQ SDDC/USTRANSCOM at SAFB shall attend/complete the following training as prescribed by DOD, USTRANSCOM, Air Force Instructions, and Army Regulations: Employee Initial Security Briefing, Annual Security Awareness Training, OPSEC, DOD Antiterrorism Level I training, and Threat Awareness and Reporting Program (TARP) Training. SDDC G34 will provide initial Security and AT Level I Training and attendance is required within the first ten days of performance start date at SAFB.

All other training can be accessed on the SDDC Portal Training site. Contractor personnel assigned elsewhere shall attend security training established by their respective Government security offices and/or installations.

5.9. Additional Security Conditions:

Upon completion of this task order, the contractor’s personnel shall surrender all Government supplies, materials and equipment to the COR. All contractor personnel assigned to this task order who possess CAC cards shall return those cards to the COR at SAFB for turn-in to the HQ SDDC/USTRANSCOM Protection Services Center (PSC). Upon turn in of CAC, COR must “Revoke” CAC in TASS. Any assigned contractor personnel who possess a security badge shall turn in those badges to the PSC in person during out-processing. Contractor personnel shall out-process on the last day of the contract or upon termination or reassignment from duties under this task order.

5.10. Contractor personnel physically working at HQ SDDC/USTRANSCOM at SAFB, IL, shall complete a non-disclosure statement (SF 312) upon start and completion of the task order.

This action is conducted at the SSC during in and out-processing.

5.11 Contracting officers or contracting officer representatives will ensure Army contractors with security clearances comply with threat awareness and reporting requirements specified in AR 381-12. Additionally, persons employed by Army contractors will report threat-related incidents, behavioral indicators, and other matters of Counter-Intelligence (CI) interest specified in AR 381-12, chapter 3, to the Facility Security Officer, the nearest military CI Office, the Federal Bureau of Investigation, or the Defense Security Service.

5.12. The Government shall ensure the roles/privileges assigned to contractor personnel on the Government computing platforms are limited to the roles/privileges essential to that individual’s performance of his/her assignments. The Government may limit or revoke these roles or privileges for any reason.

5.13. Handling of Non-Public Information In performance of this contract, the contractor may have access to sensitive, non-public information. The contractor agrees (a) to use and protect such information from unauthorized disclosure IAW Directive-Type Memorandum (DTM) 08- 027 - Security of Unclassified DOD Information on Non-DOD Information Systems, 31 July 2009; (b) to use and disclose such information only for the purpose of performing this contract and to not use or disclose such information for any personal or commercial purpose; (c) to obtain permission of the Government Program Manager before disclosing/discussing such information with a third party; (d) to return and/or electronically purge, upon Government request, any non-public, sensitive information no longer required for contractor performance; and (e) to advise the CO and/or COR of any unauthorized release of such information. Upon request, the contractor shall have its employees assigned to this contract execute a non-disclosure agreement for delivery to the Government. The Government will require contractor personnel to sign a non-disclosure statement to protect non-public information of other contractors and/or the Government.

5.14. If the Government notifies the contractor that the employment or the continued employment of any contractor personnel is prejudicial to the interests or endangers the security of the United States of America, that employee shall be removed and barred from the worksite.

This includes security deviations/incidents and credible derogatory information on contractor personnel during the course of the task order period of performance. The contractor shall make any changes necessary in the appointment(s).

Security Regulation Guidance:

Department of Defense (DOD):

2000.16 (DOD Antiterrorism (AT) Standards) 5200.1-R (DOD Information Security Program) 5200.2-R (DOD Personnel Security Program) 5200.08-R (DOD Physical Security Program) 5220.22-M (National Industrial Security Program)

8500.1 (Information Assurance (IA)

2000.12 (DOD Antiterrorism (AT) Program)

8500.01 (Cybersecurity)

DOD regulations found at: http://www.dtic.mil/whs/directives/corres/pub1.html

Army:

AR 25-2 (Information Assurance) AR 380-5 (Department of the Army Information Security Program) AR 380-20 (Restricted Areas) AR 380-67 (Department of the Army Personnel Security Program) AR 381-12 (Threat Awareness and Reporting Program) AR 525-13 (Antiterrorism) AR 530-1 (Operations Security)

Army regulations found at:

http://www.army.mil/usapa/epubs/

SDDC:

SDDC Regulation 190-1 (SDDC Security Program)

SDDC Regulation 380-2 (SDDC Operations Security Program)

SDDC Regulation 380-5 (SDDC Information Security Program)

(Provided upon request from SDDC G34 at SAFB)

Scott Air Force Base:

SAFB Instruction 31-101 (Installation Security Instruction) (Restricted publication. Sent only to .mil domains when forwarding. Not for public distribution.)

Forms:

DD 254, DOD, Contract Security Classification Specification DOD forms found at:

http://www.dtic.mil/whs/directives/corres/pub1.html

HQ SDDC Industrial Security Point of Contact:

Jeffrey McGrath 1 Soldier Way Scott AFB IL 62225 Commercial: 618-220-7755 Email at jeffrey.t.mcgrath.civ@mail.mil HQ SDDC Approval: Jeffrey McGrath HQ SDDC Tracking #: HQSDDCG34-001-17

6.0 Exit Requirements

If the Government terminates this task order for any reason or if an option period is not exercised, the contractor may, at the Government’s discretion, be given up to a sixty (60)-calendar day transition period. The contractor shall organize all work related documents and files, store them on the designated shared drives, and provide a file plan outlining the file structure. Status for each project shall be documented, to include recent, current, and pending actions. The contractor shall provide a listing of all GFP and COTS utilized in support of this task order and soft copies of all procedures and training materials developed as part of this task order. The contractor shall provide all-inclusive inventories, accountability of licenses, software and hardware documentation, knowledge transfer methodology, and a timeframe for accomplishing these activities. In addition, the contractor shall provide a complete list of all badges, vehicle passes, and Government software access permissions by individuals currently working on the task order. The contractor must ensure no task order data is corrupted, changed, or altered in a manner that would cause damage to the Government. The contractor shall meet performance requirements and cooperate with the successor contractor in the transition period.

During the transition period, the incumbent contractor shall provide the assistance and support required to ensure the orderly transition of all tasks, and provide transitional planning necessary to enable the follow-on contractor to commence uninterrupted operations at the end of the transition period. The contractor shall ensure follow-on contractor personnel are permitted access to observe all operations, including workflow, priorities, scheduling, equipment handling/processing, parts storage, safety, and security. Familiarization visits shall not interfere with the activities of the incumbent contractor or Government personnel.

7.1. Protection

7.1.1 Information Assurance

7.1.1.1 Information Assurance (IA) Training. All Contractor personnel with access to Government information systems and networks shall successfully complete all required IA awareness training as specified in AR 25-2 and as specified by the Government requiring activity. This includes training mandated in Army CIO/G6 ALARACT message 293/2007, subject: Implementation of Standard DoD IA Awareness Training, dated 261800Z Dec 07.

Training is available at https://ia.signal.army.mil.

7.1.1.2 Contractor employees and subcontractor employees performing work under this contract/task order who have access to Government information systems and networks shall create a user account and profile in the Army Training and Certification Tracking System website (ATCTS) at https://atc.us.army.mil, in the unit container managed by the COR. Certificates of successful completion of IA training, Acceptable Use Policies (AUP), applicable baseline and computing environment certifications, and continuing professional education credits, as required by DoD 8570.01-M, shall be uploaded to the ATCTS and provided to the COR for continuous compliance monitoring and reporting.

7.1.1.3 The Contractor shall ensure that all contractor employees and subcontractor employees requiring IA awareness training complete the training at the start of work performance on this contract/task order and annually thereafter for the duration of this contract/task order.

7.1.2 Information Assurance Workforce Certification. DFARS clause 252.239-7001 (Information Assurance Contractor Training and Certification) applies to this contract/task order.

This contract/task order is subject to the mandates of DoD 8570.01-M, which establishes baseline technical and management IA skills for personnel performing IA functions within DoD.

Functions spanning multiple levels require certification of the highest level functions.

Contractor personnel performing functions in multiple categories or specialties shall hold certifications appropriate to the functions performed in each category or specialty.

7.1.2.1 The Contractor shall ensure its IA workforce members have the baseline certifications corresponding to their IA functions, as defined in Chapters 3, 4, 5, 10, and 11, and Appendix 3 of DoD 8570.01-M at work performance start date. Contractors will obtain all required Computing Environment (CE) certificates within 6 months of being engaged. The IAT Level I baseline certification is the minimum requirement for unsupervised privileged access. The Contractor shall ensure that all employee certifications remain active and renewed prior to expiration.

7.1.2.2 The Contractor shall ensure that all employees IA certifications are released to the Department of Defense through the Defense Workforce Certification Application at https://www.dmdc.osd.mil/appj/dwc/index.jsp.

7.1.2.3 Table 1 reflects the Personnel Security (IT Level) and IA Workforce Specialty requirements, aligning the IA functional responsibilities and access levels to the contract/task order tasks, in accordance with DoD 8570.01-M.

Table 1. Information Technology Access and IA Certification Requirements.

Functional Category

IT Level

(IAW AR

25-2) Security

Clearance Investigation

Required

IA

Certification Category and Level (IAW

DoD 8570.01-M and BBP 05-

PR-M-0002)

Computing Environment Certifications

Project Manager (part time)

Basic Requirement

Favorable Security

Investigation

NAC

NA

No

Senior Functional Analyst

Basic Requirement

Favorable

NAC NA

Analyst

Basic Requirement

Favorable

Analyst

Basic Requirement

Favorable

7.1.3 Non-Government-owned computing systems or devices. The Contractor shall comply with AR 25-1 and AR 25-2. The Contractor shall not install or connect non-Government-owned computing systems or devices to Government networks without the COR’s coordinating and obtaining proper authorization from the appropriate Information Assurance Program Manager (IAPM), ensuring that all software has a Government Certificate of Networthiness. The non- Government-owned computing systems or devices include, but are not limited to, personal or Contractor-owned thumb drives (e.g., memory sticks, flash drives, Universal Serial Bus (USB) drives, jump drives, pen drives), removable or external hard drives, Personal Digital Assistants (PDA), PC Cards/Express Cards, MP3 players, cell phones, digital media, floppy disks, compact disc (CD)/digital video disk (DVD) burners, optical recordings, photo flash cards, laptops, or any devices that can store data.

7.1.4 Protection of Sensitive Unclassified Data. The Contractor shall ensure any sensitive information, including, but not limited to, Personally Identifiable Information (PII) and For Official Use Only (FOUO), proprietary, and Law Enforcement Sensitive information residing on Mobile Computing Devices (MCD) or other external…