ID09180038_D.1_ATTACHMENT_7_-_SAMPLE_TASK_ORDER_3_-_TASK_ORDER_0001.pdf

ID09180038 – Sample Task Order 3 – TASK ORDER 0001

D.1 ATTACHMENT 7_SAMPLE TASK ORDER 3 – TASK

ORDER 0001 – TESTING INFRASTRUCTURE AND

DELIVERY MODERNIZATION

U.S. General Services Administration

Federal Acquisition Services Contracting Division

Contract Number _______TBD

ITSS Number_______________

Task Order Number: ______________

1. Title. Testing Infrastructure and Delivery Modernization.

2. Background. The Office of People Analytics (OPA) is responsible for the development and maintenance of several computer-based testing systems used by the Department of Defense (DoD). The Armed Services Vocational Aptitude Battery (ASVAB) is a multiple aptitude test battery used by all military Services to select and classify military applicants. Until 1990, the ASVAB was administered as a traditional, paper-and-pencil test. At that time a new method of ASVAB administration was introduced at several Military Entrance Processing Stations (MEPS) -- Computerized Adaptive Testing (CAT).

CAT-ASVAB is now operational at all MEPS and many Military Entrance Testing Sites (METS). CAT-ASVAB is now available on two different platforms: a local area network (LAN) / Windows-based CAT-ASVAB platform, called WinCAT, and an Internet-based platform, called iCAT. WinCAT is operational at all Military Entrance Processing Stations (MEPS). The iCAT platform is available at many MEPS and MET sites, and also is being used in some high schools and vocational schools as part of the Career Exploration Program (CEP).

In addition to the computer-based testing systems described above, other tests have been computer-administered, as implementation of CAT-ASVAB has demonstrated the efficiency of computer-based testing. In the area of language testing the Defense Language Proficiency Test (DLPT), the Defense Language Aptitude Battery (DLAB), and the English Comprehension Level (ECL) test are all computer administered, with most being web-based. Other cognitive and non-cognitive measures, often called Special Tests, have been developed for computer administration and are currently being administered on the WinCAT platform. In-Service tests, such as the Armed Forces Classification Test (AFCT), have been converted to iCAT Web administration.

Now that computer-based testing is commonplace, the challenge is to ensure that tests are delivered in the most efficient and reliable way possible. Currently, this appears to be converting all tests to run on a virtual infrastructure in a Cloud-based environment.

Since many of the tests are already web-based, moving the test delivery software to the Cloud may be fairly straightforward as long as the proper infrastructure is in place. An important part of this would be to ensure that the proper computer security is in place as data collected as part of the testing includes Personally Identifiable Information (PII).

3. Objective. The objective of this effort is to establish the necessary infrastructure based on Cloud Service Provider (CSP) best practices for the web platform and to implement CAT-ASVAB and related tests on this platform. This effort will also include maintenance of one of the Special Tests (the Tailored Adaptive Personality Assessment [TAPAS]).

4. Specific Tasks.

4.1. Planning the Move to the Cloud

4.1.1. The contractor shall maintain/update a roadmap for moving all test delivery applications and associated utilities to a CSP. The roadmap should address all issues related to delivering Government tests in a Cloud environment, including protection of PII, meeting Government computer security requirements, conducting Software Quality Assurance, managing software releases, and all other necessary activities. The roadmap should include a recommendation as to the best CSP to meet Government requirements for implementation/deployment of the test delivery systems.

4.2. Building the Cloud-based Infrastructure and Associated Components

4.2.1. Once approved by the Government, the contractor shall continue to refine the Cloud-based infrastructure and associated components in accordance with the roadmap developed in paragraph 4.1. This shall include, but is not limited to:

4.2.1.1. Procuring CSP user accounts, storage space, and tools necessary to build, secure, and maintain the virtual environment on the CSP platform for OPA web applications.

4.2.1.2. Procuring the necessary hardware and software to perform software development, quality assurance, issue tracking, project management, support, maintenance, information assurance, and various reporting and presentation tasks.

4.2.1.3. Developing Configuration Management Standard Operating Procedure (SOP) documents in support of the System Infrastructure and Software Development Lifecycles.

4.2.1.4. Integrating required CM and QA tools in order to maintain system security and software integrity throughout the SDLC processes.

4.2.1.5. Procuring, installing, and configuring in accordance with the DoD specifications and regulations the CSP infrastructure Operating System (OS) images, network components, security scanning, and reporting tools as applicable.

4.2.1.6. Integrating all Government Information Assurance requirements.

This includes providing both manual and automated methods to maintain security, integrity and privacy of the Government software systems, components, and data. The contractor should provide remedies and/or amelioration actions that will be taken if there is a data or system breach.

4.2.1.7. Obtaining and maintaining system level DoD certificates necessary for the applications to communicate in a trusted environment with external data systems.

4.2.1.8. Integrating tools for monitoring space usage on the CSP platform and providing monthly reports to the Government on the system, storage, usage, and network allocations.

4.3. Converting Existing Web-based Software

4.3.1. The contractor shall review existing OPA web-based test delivery applications and make changes necessary for cloud delivery.

4.4. TAPAS Cloud Sustainment

4.4.1. The contractor shall make TAPAS software modifications necessary to replicate the same functionality in the cloud environment that is already implemented on the WinCAT platform.

4.5. Investigate Alternative Approaches to Low-bandwidth environments to enhance performance

4.5.1. Interruptions: Many test-takers experience one or more interruptions during their internet delivered test. These interruptions are caused by an interrupted connection between the client machine and the server.

Currently, this is remedied by the test proctor who signs the test-taker back in to the application to proceed where the interruption occurred. The contractor shall document and recommend one or more streamlined (less proctor labor intensive) approaches to dealing test interruptions. These may include (but not necessarily limited to) the use of thick clients, a proctor initiated refresh button/feature, or possibly other approaches.

4.5.2. Extremely Low Bandwidth: Currently the iCAT tests are administered in locations with fast internet service. There is a desire to administer iCAT on remote Pacific islands (for example) that may have unreliable internet service. The Contractor shall develop a plan and a set of recommendations for delivering iCAT in such locations by using, for example, satellite phones, thick clients, and software modifications to accommodate slow and unreliable internet connections.

5. Deliverables and Reporting Requirements.

5.1. Monthly Status Reports. The contractor shall document and report the status of these efforts each month.

5.2. Technical Documents. The contractor shall provide written documentation of evaluations and developed procedures, as well as documentation of all computer hardware and software.

5.3. Computer Software. The contractor shall provide all software developed under this task order, including source code and files, including executable files.

5.4. System Documentation and Computer Source Code. The contractor shall provide written documentation of all computer programs, to include flow charts of all main and other routines. System documentation shall include electronic versions of computer programs. Computer source code shall be delivered in electronic format.

6. Schedule of Deliverables.

Deliverable Due Date

Monthly Progress Report Monthly, starting with the second month after start of delivery order.

Technical Documents The contractor shall provide a draft of the roadmap document described in 4.1.2 within 120 days of task order award. Other documentation will be provided as required, but not later than

(NLT) End of Task Order (EOTO).

System Documentation Final documentation is due NLT EOTO and will incorporate changes resulting from Government review of the documents.

Draft documentation is due on an “as required” basis.

Computer Software Final versions of all software are due NLT EOTO and will incorporate changes resulting from Government review of the software. Draft software is due on an “as required” basis.

7. Place of Performance. The place of performance will be at the contractor’s facilities, at OPA West, Seaside, Calif., facilities, or at CSP facilities, as required.

8. Travel: Local or long-distance travel may be required to various locations, as directed by the Government, in order to perform the tasks delineated in this PBSOW. All non-local travel must be pre-approved by the Government. Contractors shall not start any travel without prior approval by the Government. All cost reimbursable travel shall be in accordance with FAR 31.205-46 and applicable travel regulations (Joint, Federal, or Standardized). Contractor payment claims shall include applicable documentation to support actual costs incurred (e.g. airfare and hotel/lodging receipts). If travel costs are expected to exceed this amount, the contractor shall notify the COR and obtain written authorization (by the Contracting Officer) prior to travel. Contractor costs for Government authorized travel are included in this contract.

8.1. Travel

8.1.1. Three (3) trips by one (1) Task Leader/Senior Contributor for a period of three (3) days to OPA, Seaside, CA or CSP sites are estimated. Three (3) trips by one (1) Programming and Analytic Support Staff for a period of three (3) days to OPA, Seaside, CA or CSP sites are estimated. The purpose of these trips is to coordinate system design and development, resolve anticipated problems, and document technical discussions.

8.1.2. One (1) trip by two (2) Senior Contributors for a period of two (2) days to Seaside, CA to take the TAPAS. One (1) trip by one (1) Senior Contributor for a period of two (2) days to brief the Manpower Accession Policy Working Group (MAPWG). One (1) trip by one (1) Senior Contributor for a period of two (2) days to brief the Defense Advisory Committee (DAC).

9. Period of Performance. The period of performance shall be 12 months.

10. Government Furnished Property. The Government will provide funding necessary regarding the items in this task order. The contractor will be responsible for providing equipment and materials necessary for evaluating and implementing these tasks. Any materials that the contractor must obtain to conduct work under this delivery order shall be provided to the Government at the conclusion of the order.

11. Security Clearance. No classified work will be done under this task order; however, all item files and computer programs generated under this effort shall be treated as “Controlled Items-Test Material” and will be safeguarded and controlled in accordance with United States Military Entrance Processing Command (USMEPCOM) regulation 611-1. User’s Guides and other documentation shall be treated as