20170313_ATIA_Sustainment_PWS.docx

DOCX document 78 KB Posted

Attached to
Army Training Information Architecture (ATIA) Application Sustainment Federal contract opportunity
Solicitation number
W911S0-17-R-0015
Issued by
Department of the Army Materiel Command Mission and Installation Contracting Command Fort Eustis

About this file

PWS

View the file

Other files for this federal contract opportunity

Other files attached to Army Training Information Architecture (ATIA) Application Sustainment, newest first.
File Type Posted
20170721_W911S0-17-R-0015-0001.pdf PDF
ATIS_CCB_Charter.pdf PDF
20170720_W911S0-17-R-0015_Questions_and_Answers_FedBizOpps.xlsx XLSX spreadsheet
Attachment_4_Past_Performance_Questionnaire.docx DOCX document
Attachment_5_Total_Evaluated_Price.xlsx XLSX spreadsheet
Attachment_3_Certificate_of_Non-Disclosure.docx DOCX document
Attachment_2_Sample_Consent_Letter.docx DOCX document
Attachment_1_Specific_Relevant_Contracts_Sheet.docx DOCX document
20170707_W911S0-17-R-0015_Final.pdf PDF
20170403_Sources_Sought_ATIA_Application_Sustainment.docx DOCX document
20170328_Sources_Sought_ATIA_Application_Sustainment.docx DOCX document
Show all 11

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

PERFORMANCE WORK STATEMENT (PWS)

Army Training Information Architecture (ATIA) Application Sustainment

U.S. Army Training Support Center TRADOC Capabilities Manager – Army Training Information Systems Fort Eustis, Virginia 23604

PART 1

GENERAL INFORMATION

1. General: This is a non-personal services contract to provide support for Army Training Information Architecture (ATIA) Application Sustainment. The Government shall 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 all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal service necessary to perform support for Army Training Information Architecture (ATIA) Application Sustainment as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background:

1.2.1 This contract is for sustainment of existing legacy ATIA systems and provides agility that will allow for the sustainment of systems subject to the availability of funds or subsumed by capabilities of the ATIS Program of Record.

1.2.2 ATIA provides development, storage, and delivery of Army doctrine and training materials to Soldiers and units anytime, anywhere. ATIA supports all levels of Army training and includes training products for all three training domains (operational, institutional, and self-development).

1.2.3 The ATIA code base consists of the following sets of software systems:

1.2.3.1 ATIS –Training Development

1.2.3.1.1 Training Development Capability (TDC): TDC is a web-based application, designed and built to comply with Army policy. TDC allows training developers to develop, manage and maintain Army training products, to include: Collective and Individual tasks; Drills; Mission Training Plans (MTP); Drill Books; Soldier’s Training Publications (STPs); Lesson plans; Course Administrative Data (CAD); and Program of Instruction (POI).

1.2.3.1.2 System Training Plan (STRAP) Writing Tool (SWT): A web-based collaborative writing tool that provides document creation, authoring, and staffing capabilities. The software has the ability to maintain control over a document by granting permissions to those that are required to view and modify. Other functionalities include templates, instructions, examples, references, and supplemental references to ease and expedite document creation. It has the ability for users to collaborate and perform modifications on the same document concurrently. It allows for rapid document development as multiple authors can populate the same document and always have access to the latest version of the document. SWT supports document staffing for review at the Peer, Army, and Approval level. SWT supports internal staffing of documents staffed to an organization for review. This will enable a wide audience access in providing feedback on a document.

1.2.3.2 ATIS –Training Delivery/Content Management

1.2.3.2.1 Central Army Registry (CAR): A federated search capability that finds and retrieves training products from a variety of web sources: repositories, document management systems, learning management systems, etc. The CAR provides a repository capability for documents.

1.2.3.2.2 TRADOC Application Gateway (TAG): A Mobile Application Store that supports TCM-Mobile. TAG integrates with the Central Army Registry, and supports Apple and Android devices as well as mobile-friendly websites. TAG includes the Web Application, Android Mobile Application, and iOS Mobile Application. TAG also provides support for distribution of Living Doctrine/Electronic Publication (ePUB) content.

1.2.3.2.3 My Training Tab (MT2): A web page operating on the Army Knowledge Online (AKO) website, under “My Services” functionality. MT2 provides soldiers access to their training records, Army training applications, essential training, “what’s hot”, and other training related functionality.

1.2.3.3 ATIS – Enterprise Services

1.2.3.3.1 System Interface Services (SIS): A functionality that provides enterprise application software system-to-system interfaces for enterprise applications. SIS includes systems that pass student information, training doctrine, training usage, and training material data between development, management, and delivery systems. It is the conduit for data passed between these training systems and Army Training Requirements and Resources System (ATRRS). ATIA uses SIS as an integration mechanism for all system-to-system interfaces. External systems must interface with ATIA systems through SIS.

1.2.3.4 ATIS – Enterprise Scheduling

1.2.3.4.1 Interim Enterprise Scheduling Capability (IESC): A web-based application that provides resource and training scheduling. The current system supports scheduling a single domain and has no enterprise capabilities to share schedule information with other systems. Maneuver Center of Excellence (MCOE) currently uses IESC.

1.2.3.5 ATIS –Training Resource Management Systems

1.2.3.5.1 Training Support Material Army wide Tracking System (TS-MATS): A Web-based application that collects and maintains inventory, maintenance, usage, and workload information for Army wide Training Aids, Devices, Simulations, and Simulators (TADSS).

1.2.3.5.2 Inventory and Distribution Management System (IDMS): A web-based application to order, warehouse, inventory, and ship ATSC training products.

1.2.3.6 ATIS –Training Management

1.2.3.6.1 No systems at this time, but ATIA may subsume other systems in the future.

1.3 Universal Properties of ATIA applications: ATIA systems make use of the following technologies; enterprise web application, Semantic search and indexing, Service Oriented Architecture (SOA), RESTful web services, mobile-friendly user interface (UI), and Mobile Applications. The contractor shall have expertise to include, but not limited to, maintenance of these technologies.

1.3.1 Enterprise Web Applications: The contractor shall have expertise in database-driven web application technology using a variety a programming languages and application server frameworks. Each of the ATIA systems has a database-driven web application at its core.

1.3.2 Semantic Sustainment: TCM-ATIS has implemented semantic web search technology. The contractor shall be familiar with semantic web technology and implementation techniques sufficient to register documents into the ATIA application. The contractor shall have expertise sufficient to identify ontology and taxonomy for the diverse training and doctrine publications, and physically distributed sites, to be included within the semantic search function to achieve and maintain an enterprise solution.

1.3.3 Enterprise Service Oriented Architecture: Enterprise Service Oriented Architecture: The contractor shall have expertise to maintain a portfolio including all specifications, service APIs and data formats for data and methods of the services maintained in the ATIA portfolio and associated technical documentation.

1.3.4 Enterprise RESTful Web Services: The contractor shall have expertise in RESTful web services over HTTPS utilizing SSO and/or B2B mutual authentication. This includes producing RESTful web services and consuming RESTful web services with an enterprise client.

1.3.5 Mobile-Friendly UI: The contractor shall have expertise in designing user interfaces that actively respond to varying screen sizes and input methods. For all GUIs, the government is targeting three classes of devices: phone, tablet, and desktop. The three classes of devices can vary in screen size, screen resolution, input method, application login method, application packaging, and application distribution method.

1.3.6 Mobile Applications: The contractor shall have expertise to build mobile applications targeting iOS, Android, and Windows mobile. Mobile applications are either mobile versions of ATIA systems or interface with ATIA systems through RESTful web services.

1.3.7 Cloud Technologies: The contractor shall have the expertise to assist in the movement and adaptation of ATIA applications to a DoD-approved cloud infrastructure that features Infrastructure-As-A-Service (IAAS) and Platform-As-A-Service (PAAS) models.

1.4 ATIA Server and Networking Environment: Currently, the environment described below hosts the ATIA applications.

1.4.1 Hardware: Virtualized VMware servers host the ATIA applications. The servers are load balanced behind an F5 Big-IP device to support user activity. Operating systems used Linux, UNIX, UNIX derivative operating systems, and Windows operating systems. The server environment is currently located at Joint Base Langley Eustis, VA. TCM-ATIS is considering re-hosting ATIA applications in a Defense Information Systems Agency (DISA), DISA Enterprise Computing Center (DECC) facility of same or comparable hardware and software. In the event of application relocation, sustainment support will remain at Ft. Eustis. The contractor will perform support tasks requiring server access remotely.

1.4.2 Software: The software systems sustained under this contract include technology from Oracle, Microsoft, Apache, Franz Inc., and Red Hat. Technologies include Java, .NET, SQL, Ruby on Rails, HTML5, JavaScript, MongoDB, AllegroGraph, web services and semantic web.

1.4.3 Network: The Government maintains and provides all network connectivity at Government facilities as Government Furnished Equipment (GFE) and services. All laptops having access to the network must be Network Enterprise Center (NEC) certified. Architecture includes thick, thin and fiber based 100base-T switched hubs, Ethernet networks, and dial up circuits from developer sites. ATIA must comply with government networking protocols.

1.4.4 Army Data Center Consolidation Program (ADCCP): TCM ATIS is considering ATIA applications for relocation to an Army-approved data center via the Army Data Center Consolidation Program (ADCCP). The scope of this contract includes support of ATIA applications hosted in either Joint Base Langley Eustis or a consolidated data center. Potential hosts include DISA, other Army approved data centers, and DoD-approved commercial cloud. Support may include transition of legacy ATIA systems to either an Infrastructure-As-A-Service or Platform-As-A-Service hosting environment.

1.5 Objectives: The objective of this PWS is to support ATIA applications continuity of service. Continuity of service requires RMF/CoN, database maintenance, software application maintenance, configuration management, information assurance, and all documentation of these areas.

1.6 Scope: This Performance Work Statement (PWS) shall encompass the following: transitioning, sustaining and maintaining the applications as well as the support of ATIA. The Contractor shall support system continuity of service with system configuration and documentation, architecture analysis, software application maintenance, database maintenance, information assurance documentation and maintenance, and RMF/CoN support.

1.7 Period of Performance: The period of performance shall be for one (1) Base Year of 12 months beginning 30 Sep 2017, and four (4) 12-month option years. The below table shows the Period of Performance.

Table 1 Period of Performance

Start Date
End Date
Base Year
30 Sept 2017
29 Sept 2018
Option Year 1
30 Sept 2018
29 Sept 2019
Option Year 2
30 Sept 2019
29 Sept 2020
Option Year 3
30 Sept 2020
29 Sept 2021
Option Year 4
30 Sept 2021
29 Sept 2022

1.8 General Information

1.8.1 Quality Control: Quality Control is the responsibility of the contractor. The contractor is responsible for the delivery of quality services/supplies to the Government.

1.8.1.1 The Contractor shall develop, implement and maintain an effective Quality Control System that includes a written Quality Control Plan (QCP). The QCP shall implement standardized procedure/methodology for monitoring and documenting contract performance. The Contractors’ QCP must contain a systematic approach to monitor services. The QCP, as a minimum, shall address continuous process improvement; procedures for scheduling, conducting and documentation of inspection; discrepancy identification and correction; corrective action procedures to include procedures for addressing Government discovered non-conformances; procedures for root cause analysis to identify the root cause and root cause corrective action to prevent re-occurrence of discrepancies; procedures for trend analysis; and procedures for collecting and addressing customer feedback/complaints. The contractor shall deliver a Quality Control Plan (QCP) to the COR and Contracting Officer within 30 business days after contract award for review and approval. The final QCP shall be submitted to the COR and Contracting Officer within 5 business days after receipt of any recommended changes. After acceptance of the quality control plan, the contractor shall receive the Contracting Officer’s acceptance in writing of any proposed change to their QC system.

1.8.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is a Government only document primarily focused on what the Government must do to assure that the contractor has performed in accordance with the requirements of the contract.

1.8.3 Federal Government Holidays: The Contractor shall not schedule interfacing work (meetings, approvals, deliverables, etc.) with the Government on any of the established holidays in federal services, or any other day designated as a holiday by Federal Statute or by Executive Order except with prior approval from the Contracting Officer or COR. If a holiday falls on a Saturday, the official holiday is on the preceding Friday. If a holiday falls on a Sunday, the official holiday is on the following Monday.

New Year’s Day1st day of January
Martin Luther King Jr.'s Birthday3rd Monday of January
Presidents Day3rd Monday of February
Memorial DayLast Monday of May
Independence Day4th day of July
Labor Day1st Monday of September
Columbus Day2nd Monday of October
Veterans Day11th day of November
Thanksgiving Day4th Thursday of November
Christmas Day25th day of December

1.8.4 Hours of Operation: The contractor is responsible for conducting business, between the hours of 6 A.M. to 6 P.M. EST Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The Contractor must maintain an adequate workforce for the 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.

1.8.5 After-Hours Outage and Maintenance Support: Contractor shall provide a maximum of 500 hours per contract year of after-duty-hours system maintenance support for mission systems and support. After hours is consider any time not in the established duty hours. Hours used shall be coordinated and approved with the COR before being obligated. The contractor shall only use hours as needed to address outage, critical system failures, planned system or preventive maintenance, and in support of projects preventing outages or work during normal duty hours.

1.8.5.1 After-hours callback to address system failures shall have a maximum of two (2) hours response time.

1.8.5.2 The contractor is allowed up to 5 business days to plan for after-hour maintenance unless that maintenance prevents a near-term system failure. After-hour maintenance may require coordination with government organizations and their contractors.

1.8.5.3 After Hours Outage and Maintenance Support usage report of hours utilized each contract year shall accompany each request outlining hours used, work performed, and personnel that performed. In addition, the contractor shall include the After Hours Outage and Maintenance Support usage report monthly.

1.8.6 Place of Performance: The contractor shall perform tasks under this contract at Government owned facilities (primarily building 3306 and 3308, ATSC ATIS offices) at JBLE. The Government may permit the contractor to perform this contract from an off-site location at no additional cost to the Government IAW all Information Assurance rules and regulations.

1.8.7 Type of Contract: This is a firm fixed price contract.

1.8.8 Security Requirements: Contractor personnel assigned to this task may have access to information that may be subject to the Privacy Act of 1974. The Contractor is responsible for ensuring all Contractor personnel are briefed and comply with regard to information subject to the Privacy Act of 1974

1.8.8.1 Employee Roster: The Contractor shall maintain a current roster of employees performing tasks under this contract, which includes the employees’ names, and contact information. The Contractor shall provide the roster to the COR on the contract start date and within 5 business days of roster changes. The contractor shall provide two versions of the roster. First version shall include each employee name, job title, employer, and contact information. The second version includes each employee name and job title but omits employer and contact information.

1.8.8.2 Physical Security: The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each business day, government facilities, equipment, and materials shall be secured.

1.8.8.3 Key Control: The Contractor shall establish and implement methods of making sure key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. The Contractor shall not allow any key duplication. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate key cards to the Contracting Officer.

In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the Government replaces locks or performs re-keying, the Government will deduct the total cost of re-keying or the replacement of the lock or locks from the monthly payment due the Contractor. In the event a master key is lost or duplicated, the Government will replace all locks and keys for that system and the total cost deducted from the monthly payment due the Contractor.

The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

1.8.9 Special Qualifications: It is the contractor’s responsibility to propose the appropriate number of personnel, labor types, mix, and hours in the proposal and during performance to accomplish the performance work statement. Contractor workforce shall possess the skills, knowledge, and training to perform the requirements of services included in this PWS. The Contractor shall be responsible for training their personnel on any new technologies the contractor recommends and is accepted by the Government. The Contractor employees shall have the ability to communicate in the English language. If the Contractor becomes aware that personnel are not performing requirements of this contract IAW the terms, the Contractor shall maintain personnel provisions to correct the deficiencies, up to and including removing such personnel. The Contractor shall maintain provisions for the immediate removal of employees for misconduct or other causes prejudicial to the maintenance of health, welfare, morale or security to Fort Eustis. The Contractor shall be aware of the Installation Commander's responsibility for the general security and well-being of Fort Eustis personnel, and shall have personnel removal provisions that support the Installation Commander in this regard. The Government has an inherent right under law, practice and regulation, to control access to its facilities, property and data, including those that are the subject of this contract. The Government will tailor access privileges to individual Contractor personnel responsibilities. The Government will be the final authority in determining access privileges. Under the authority of 18 U.S.C. 1382, the Government's exercise of its right to grant and revoke access by particular individual(s) to its facilities will not constitute a breach or change to this contract, regardless of whether said individual(s) are employed by the Contractor, and regardless of whether said individuals are thereby precluded from performing work under this PWS.

1.8.10 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office. The Contracting Officer, COR, and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings, the Contracting Officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of any problems experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

1.8.11 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 is authorized to perform the following functions: assure that 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, and specifications; monitor Contractor's performance and notify 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 is not authorized to change any of the terms and conditions of the resulting order.

1.8.12 Key Personnel: Certain special skilled/experienced professional/technical personnel are essential for the contractor's successful performance/delivery of the requirements of this acquisition. These are "key personnel." As deemed necessary the contractor shall propose that certain positions be staffed with key personnel and shall provide supporting rationale for so doing. (There is no intent on the part of the Government to require a specific number of key personnel.)

1.8.12.1 The contractor shall provide a project manager who shall be responsible for the performance of the work. The contractor shall designate this person and an alternate who shall act for the contractor when the manager is absent in writing to the contracting officer. The project manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The project manager or alternate shall be available between 8:00 a.m. to 4:30p.m., Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons.

1.8.12.2 The contractor agrees that such personnel shall not be removed from the contract or replaced without compliance with this paragraph and the Contracting Officer's directions.

1.8.12.3 If one or more key personnel, for whatever reason, becomes or is expected to become unavailable for work under this task order for a continuous period exceeding twenty (20) days, or is expected to devote substantially less effort to the work than indicated in the contractor's proposal or as initially anticipated; the contractor shall immediately notify the Contracting Officer and COR in writing and shall, subject to the concurrence of the Contracting Officer (or the COR), promptly replace such key personnel with another of at least substantially equal ability and qualifications.

1.8.12.4 Requests for approval of substitutions hereunder (1) shall be in writing and shall include a detailed justification; (2) comply with all instructions given by the Contracting Officer. Upon review, the Contracting Officer (or the COR) shall notify the contractor, in writing, of the decision to approve or disapprove the substitution.

1.8.12.5 Should the Contracting Officer determine that suitable and timely substitution of key personnel (again, for whatever reason) is not reasonably forthcoming or that the resultant reduction of productive effort would be so substantial as to impair the successful completion of the task order, the task order may be terminated, either for reason of default or the convenience of the Government, as appropriate. Should the contractor be found to be at fault, the price of the contract may be equitably adjusted downward to compensate the Government for any resultant delay, loss, or damage.

1.8.13 Identification of Contractor Employees:

1.8.13.1 ID Badges: The Contractor (to include subcontractors) shall provide each employee an Identification (ID) Badge, which includes at a minimum, the Company Name, Employee Name and a color photo of the employee. ID Badges for Key Personnel shall also indicate their job title. ID Badges shall be worn at all times during which the employee is performing work under this contract. Each Contractor (to include subcontractors) employees shall wear the ID Badge in a conspicuous place on the front of exterior clothing and above the waist except when safety or health reasons prohibit. The Contractor (to include subcontractors) shall be responsible for collection of ID Badges upon completion of the contract or termination of employee. A listing of issued identification cards shall be furnished to the Contracting Officer prior to the contract performance date and updated as needed to reflect Contractor and Subcontractor personnel changes. All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are 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 must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

1.8.13.2 Non-Disclosure: In addition to any organizational conflict of interest provision, Contractor employees assigned to this project will be required, prior to working, to sign a non-disclosure statement for the government agreeing not to share any information or data with other offer or personnel not assigned to the project. The signed non-disclosure statements will be furnished to the Contracting Officer prior to contract performance. The Contractor shall include, with its submission of the contract execution its plan to "firewall" these employees and enforce the provision (i.e., internal controls, training, etc.). Failure to adhere to these non-disclosure safeguards may result in termination of this contract. Final authorship and copyright (if required) of any deliverables will lie solely with the Government.

1.8.14 Supervision of Contractor Employees: The Government will not exercise any supervision or control over Contractor or subcontractor employees while performing work under the contract. Such employees shall be accountable solely to the Contractor, not the Government. The Contractor, in turn, shall be accountable to the Government for Contractor or subcontractor employees.

1.8.15 Contractor Travel: Travel will be performed and reimbursed IAW FAR 31.205-46(a) (2). No local travel reimbursement is authorized. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires prior Government approval/authorization and notification to the COR. All travel requested by the contractor shall be submitted for approval by the COR at least two weeks prior to travel date. Contractor shall submit a travel request containing the following information: names, reason travel required, cost breakdown of travel, lodging, daily allowances. A Trip Report shall be submitted to the COR within 5 business days of completion of travel. Costs incurred by contractor personnel for travel, including costs of lodging, other subsistence, and incidental expenses, shall be considered to be reasonable and allowable. The Federal Travel Regulations rates and amounts will be used as point of comparison to determine cost allowability, reasonableness and allocability. If required, funding for required travel outside the local area will be added after award. Contractor shall submit receipts to the COR for expenses being claimed within 5 business days from travel completion for verification by the COR. Receipts for expenses greater than $25.00 must be submitted. Rates and clarification on travel issues can be found at the following Website: http://www.dtic.mil/perdiem/pdrform.html.

1.8.16 Other Direct Costs: This category includes reproduction, and shipping expenses. It could also entail the renting of suitable training venues.

1.8.17 Data Rights: The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.8.18 Organizational Conflict of Interest: If any work performed under this contract creates a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5, the Contractor shall notify the Contracting Officer immediately whenever the Contractor becomes aware that access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.8.19 General: The Contractor shall provide a workforce possessing the skills, knowledge, and training to satisfactorily perform the services required by this contract. Personnel performing work under this performance work statement shall remain employees of the contractor and will not be considered employees of the Government.

1.8.19.1 Conduct of Personnel: The contractor’s employee’s conduct shall be in accordance with DOD-5500 7-R Joint Ethics Regulations. The removal from the job site or dismissal from the premises shall not relieve the contractor of the requirement to provide sufficient personnel to perform the services as required by this statement of work. IAW AR 380-49, the authority of the Installation Commander to control and deny entry to all or part of the installation is absolute. The individual concerned has no right to appeal. Upon termination of any employee performing tasks under this PWS, the Contractor shall notify the COR of the action immediately. The Contractor shall return all Government issued identification for that person immediately, not later than the beginning of the next duty day.

1.8.19.1.1 If the Contractor determines that employees designated as system administrators are required to execute this performance work statement, those persons shall complete the Operational Information System Security (OISS) course and attend the Level II System Administrators Training course required for these positions. The Government will not pay for the contractor's employees to attend either training course.

1.8.19.1.2 Security Policies and Directives: The Contractor shall inform all assigned personnel of applicable security policies and directives. The Contractor shall not permit personnel who knowingly violate security policies or directives to perform any requirements of this contract. No security clearance is required. This contract does not require access to classified information.

1.8.19.2 Antiterrorism/OPSEC Review:

1.8.19.2.1 Anti-Terrorism (AT) Level I Training: All contractor employees, to include subcontractor employees, requiring access Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 90 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within 15 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: http://jko.jten.mil

1.8.19.2.2 Access and General Protection/Security Policy and Procedures: Contractor and all associated sub-contractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

Information must be received by PMO at least 72 hours prior to visit.

1.8.19.2.2.1 Contractors requiring Common Access Card: Access to government computer systems requires an issued CAC. Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

1.8.19.2.2.2 Contractors that do not require CAC, but require access to a DoD facility or installation: The Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

1.8.19.2.3 IWATCH Training: The contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 90 calendar days of contract award and within 90 calendar days of new employees commencing performance with the results reported to the COR NLT 15 calendar days after contract award.

1.8.19.2.4 Army Training Certification Tracking System (ATCTS) registration for contractor employees who require access to government information systems: All contractor employees with access to a government info system must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the IS and then annually thereafter.

1.8.19.2.5 OPSEC Training: Per AR 530-1 Operations Security, the contractor employees must complete Level I OPSEC Awareness training. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter.

1.8.19.2.6 Information Assurance (IA)/Information Technology (IT) Training: All contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of appointment to IA/IT functions.

1.8.19.2.7 Information Assurance (IA)/Information Technology (IT) Certification: Per DoD 8570.01-M, DFARS 252.239.7001 and AR 25-2, the contractor employees supporting IA/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

1.8.19.2.8 Threat Awareness Reporting Program (TARP): For all contractors with security clearances. Per AR 381-12 Threat Awareness and Reporting Program (TARP), contractor employees must receive annual TARP training by a CI agent or other trainer as specified in 2-4b.

Contractor must be able to obtain and maintain a favorable suitability/fitness determination under 5 CFR or equivalent for Common Access Cards (CAC) issuance and/or network access. Investigations have to be opened/scheduled at OPM and favorably reviewed by the government. The Government will submit background investigations for positions that require Common Access Card (CAC) and/or IT access only. For contractors, the minimum requirement for access to federal information systems is as follows: Tier 5 (T5) Single Scope Background Investigation (SSBI/SF 86); Tier 3 (T3) a NACLC (SF 86) and TIER 1 (T1) (SF 85). Prior to CAC issuance, the NAC (FBI 10 point FBI fingerprint check) must be completed without adverse comment, and the TIER 1 (T1) or equivalent MUST BE SCHEDULED/OPENDED AT OPM. CACs will not be issued before the fingerprint check results have been completed and the investigation has been submitted to OPM and favorably reviewed by the government. FINGERPRINTS AND THE APPROPRIATED INVESTIGATION WILL BE SUBMITTED BY THE GOVERNMENT.

1.8.20 Unclassified Contracts: Contractor personnel performing under this task order will not require access to classified military information (CMI) or systems however, must be able to obtain and maintain a favorable suitability/fitness determination under 5 CFR or equivalent for Common Access Cards (CAC) issuance and/or network access. Written Visit Authorization Letters (VAL) will be sent to the Army Training Support Center (ATSC) Security Management Office Bldg. 1900. Joint Base Langley/Eustis, VA 23604-5166.

1.8.20.1 Installation Security Office will submit all background investigations on prospective contractors requiring CAC and/or network access.

1.8.20.2 733rd Security Forces Squadron will conduct background checks on all Contractor personnel requiring access to the installation.

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. CONTRACT ADMINISTRATOR. The official Government representative delegated authority by the Contracting Officer to administer a contract. This individual is normally a member of the appropriate Contracting/Procurement career field and advises on all technical contractual matters.

2.1.2. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or services to the government. The term used in this contract refers to the prime.

2.1.3. CONTRACTING OFFICER. A person with authority to enter into, administer, and/or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.4. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.5. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.6. DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.7. GOVERNMENT-FURNISHED PROPERTY (GFP) OR GOVERNMENT PROPERTY (GP). Property in the possession of, or directly acquired by, the Government and subsequently made available to the Contractor.

2.1.8. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.9. QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are acceptable in accordance with established standards and requirements of this contract.

2.1.10. QUALITY ASSURANCE SPECIALIST. An official Government representative concerned with matters pertaining to the contract administration process and quality assurance/quality control. Acts as technical advisor to the Contracting Officer in these areas.

2.1.11. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.12. QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.13. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.14. WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.15. WORK WEEK. Monday through Friday, except for Federal holidays unless specified otherwise.

2.2. ACRONYMS:

ABCSArmy Battle Command System
ACORAlternate Contracting Officer's Representative
ADPAutomatic Data Processing
ADPEAutomated Data Processing Equipment
AFARSArmy Federal Acquisition Regulation Supplement
AISAutomated Information System
ALMSATIS Learning Management System
ALOArmy Learning Object
AOGAction Officer Guide
AORArea of Responsibility ARArmy Regulation
ATCCSArmy Tactical Command & Control System
ATENArmy Training and Education Network
ATHDArmy Training Help Desk
ATIAArmy Training Information Architecture
ATISArmy Training Information System
ATIS-OAArmy Training Information System Operational Architecture
ATMAsynchronous Transfer Mode
ATRRSArmy Training Requirements and Resources System
ATSCArmy Training Support Center
CACCommon Access Card
CADCourse Administrative Data
CARCentral Army Registry
CCBConfiguration Control Board
CDDCapability Development Document
CHRTASCivilian Human Resources Training Application System
CFMCapability Framework Model
CFRCode of Federal Regulations
CMEContractor Manpower Equivalents
CMFCapability Model Framework
CMMICapability Maturity Model Integration
CMRContract Manpower Reporting
CONCertificate of Networthiness
CONUSContinental United States (excludes Alaska and Hawaii)
COOPContinuity of Operations
CORContracting Officer Representative
COTRContracting Officer's Technical Representative
COTSCommercial off the Shelf
CPDCapabilities Production Document
CPUCentral Processing Unit
CRChange Requests
CRMCourse Resource Model
CVSContractor Verification System
CWBSOMContract Work Breakdown Structure, Resource Loaded Network and Organization

Mapping

DADepartment of the Army
DCODefense Connect Online
DD250Department of Defense Form 250 (Receiving Report)
DD254Department of Defense Contract Security Requirement List
DDRDetailed Design Review
DECCDISA Enterprise Computing Center
DESData Encryption Standard
DFARSDefense Federal Acquisition Regulation Supplement
DIACAPDOD Information Assurance Certification and Accreditation Process
DII COEDISA Defense Information Infrastructure-Common Operating Environment
DIMHRSDefense Integrated Military Human Resources System
DISADefense Information Systems Agency
DJMSDefense Joint Military System
DLDigital Library
DLSDistributed Learning System
DMDCDefense Manpower Data Center
DMZDemilitarized Zone DODDepartment of Defense
DODAFDepartment of Defense Architecture Framework
DRData Repository
DTMSDigital Training Management System
FAQFrequently Asked Questions
FARFederal Acquisition Regulation
FIPSFederal Information Procedures System Publication
FPCOMForce Protection Condition
FSCFederal Service Code
FTMFunctional Test Matrix
GFEGovernment Furnished Equipment
GOTSGovernment off the Shelf
GUIGraphical User Interface
HIPAAHealth Insurance Portability and Accountability Act of 1996
HQDAHeadquarters Department of Army
HRCHuman Resource Command
IAInformation Assurance
IAMInformation Assurance Manager
IAVAInformation Assurance & Vulnerability Assessment
IAWIn Accordance With
IDMSInventory and Distribution Management System
IESCInterim Enterprise Scheduling Capability
IMIInteractive Multimedia Instruction
IOCInitial Operation Capability
IPRIntegrated Process Review
IRSInterface Requirements Specifications
ITInformation Technology
ITAISInitial Task Analysis Information Sheet
JCIDSJoint Capabilities Integration & Development System
JPASJoint Personnel Adjudication System
JTAJoint Table of Allowances
JTRJoint Travel Regulation
LCMSLearning Content Management System
LMSLearning Management System
KOContracting Officer
LOELevel of Effort
KPIKey Performance Indicators
MANPRINTManpower & Personnel Integration
MSMicrosoft
MTPMission Training Plans
MT2My Training Tab
NACINational Agency Check with Inquiries
NCICNational Crime Information Center
NCONon-Commissioned Officer
NETCOMNetwork Enterprise Technology Command
NISPOMNational Industrial Security Program Operating Manual
OCIOrganizational Conflict of Interest
OCONUSOutside Continental United States (includes Alaska and Hawaii)
ODCOther Direct Costs
OISSOperational Information System Security
OPLDOperations, Plans, and Logistics Directorate
OPORDSOperational Orders
PDRPreliminary Design Review
PERTProgram Evaluation & Review Technique (Chart)
PIPOPhase In/Phase Out
PMOProvost Marshall’s Office
POCPoint of Contact
POIProgram of Instruction
PRProblem Report
PRSPerformance Requirements Summary
PWSPerformance Work Statement
QAQuality Assurance
QAPQuality Assurance Program
QASPQuality Assurance Surveillance Plan
QCQuality Control
QCPQuality Control Program
RARequiring Activity
RCBRequirements Control Board
RDLReimer Digital Library (RDL)
RESTRepresentational State Transfer
RESTfulRepresentational State Transfer Full (adjective)
RMFRisk Management Framework
RTMRequirements Traceability Matrix
SASystem Architecture
SBUStrategic Business Unit
SCORMSharable Courseware Object Reference Model
SDDSystem Design Document (SDD)
SF85Standard Form 85 for National Agency Check with Inquiries (NACI)
SFUGSecurity Features Users Guide
SISSystem Interface Services
SMOSecurity Management Office
SQLStructured Query Language

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .