Exhibit_2a__TRAP_Transition_PWS_Final_.docx

Total Force Information Technology Systems

TRAP Transition Performance Work Statement

February 2014 Table of Contents

List of Figures

List of Tables

TRAP Transition Performance Work Statement

Introduction Purpose and Scope This Performance Work Statement (PWS) identifies the requirements and performance standards for the efficient, transparent replacement of the Total Force Information Technology Systems (TFITS) Request for Proposal (RFP) Assessment Program (TRAP) from the incumbent contractor to the new TFITS Consolidated Systems Integrator (TCSI).

*** PLEASE NOTE, TRAP IS A FICTICIOUS SYTEM***

Background TRAP provides daily accountability of all Marines, other Service members, and affiliated personnel under administrative and operational control of the Marine Corps. TRAP has 5,000 users across the Marine Corps, reached Full Operational Capability in 2012 and is currently in the Operations and Support (O&S) phase. The system is assigned a Mission Assurance Category (MAC) II, Sensitive. TRAP is an acquisition category (ACAT) IVT. TRAP operates in a Non-classified Internet Protocol Router (NIPR) and Secret Internet Protocol Router (SIPR) web-based environment, with its production system hosted at Marine Corps Base Quantico.

TRAP includes custom application software and tailored Commercial-Off-The-Shelf (COTS) software. The TRAP application software was developed using C Sharp on an ASP.Net framework. The database is built in Oracle 11g. The TRAP development environment is contractor provided. TRAP help desk services are contractor provided.

An overview of the system including interfaces is provided in Figure 1 and Appendix D.

Figure 1. TRAP System Operational Diagram Figure 2 provides the TRAP architecture layout.

Figure 2. Physical Representation of the TRAP Production Architecture The incumbent contractor is located in Springfield, Virginia. The incumbent’s contract provides support for the transition of TRAP systems integrator responsibilities as follows:

· Three (3) transition meetings

· Up to five (5) days of over-the-shoulder sessions to gain familiarization of system(s) functionality

· Delivery of Government- furnished information:

· TRAP production source code

· System Administrator’s Manual

· The TRAP Configuration Item Technical Database (CITDB), which identifies the third party software used in the development and support of the TRAP system.

Transition System Knowledge Transfer The TCSI shall have complete and comprehensive understanding of the transitioning system.

At a minimum, System Knowledge Transfer includes the following:

Existing engineering and technical documentation.

The TCSI shall create the required level of system knowledge through the assimilation of information available in existing TRAP engineering and technical documentation. In addition, the TCSI identify and mitigate any TRAP engineering and technical knowledge gaps.

Existing user documentation.

The TCSI shall determine the required level of system functional expertise through the assimilation of information available in existing TRAP user documentation. In addition, the TCSI shall identify and mitigate any TRAP user documentation knowledge gaps.

TCSI System Instantiation The TCSI shall have the capability to conduct defect management which includes the ability to replicate system failures, test software patches prior to production release, and test system development efforts.

At a minimum, TCSI System Instantiation includes the following:

Production System Software A current copy of the production system software, including source code, will be provided as part of the transition process to support Post Deployment Software Support (PDSS) activities and instantiation of a production representative system in the TCSI’s environment. The TCSI shall receive, manage and maintain TRAP production software.

Development and TCSI Test Hosting Environment The TCSI shall provide the TRAP development and TCSI test hosting environment for the production representative system instantiation. The TCSI’s hosting environment shall be representative of the constraints and limitations of the TRAP production environment Testing & Evaluation The TCSI shall have and implemented a complete understanding (activities, notional timeline) of what is required to validate there is a complete functioning replication of the TRAP’s production system to support the range of TCSI functions.

Critical PDSS Activities.

The TCSI shall provide a detailed and executable plan to transfer on-going service support and service delivery activities from the incumbent TRAP Systems Integrator (SI) to TCSI. At a minimum, this includes:

Database administration;

System administration;

Cybersecurity;

System interfaces.

Help desk; and Training/and Training materials.

1.1 Transition Activity with the Government and SI Incumbent

The TCSI shall engage in the following activities throughout a 30-day TRAP transition period:

Obtain TRAP administrative access, from the current SI, to the system as well as TRAP system interfaces.

Obtain TRAP points of contact (POCs), from the current SI, to include telephone numbers and email addresses for TRAP, Functional advocates, programmatic and technical POCs for interfacing TRAP, and POCs for current TRAP hardware and software maintenance agreements.

Schedule and attend up to five days of observing the current SI during the conduct of TRAP system maintenance and administration during regular business hours, i.e. 0700 to 1500. Days can be, but are not required to be consecutive. One day is equivalent to a minimum of eight hours, not including lunch.

Schedule and attend up to five days of conducting TRAP system maintenance and administration while the current SI observes during regular business hours, i.e. 0700 to 1500. Days can be, but are not required to be consecutive. One day is equivalent to a minimum of eight hours, not including lunch.

Schedule, plan, provide agenda, attend, and participate in up to three sessions and/or meetings to facilitate TRAP knowledge transfer on system functionality. Days can be, but are not required to be consecutive. One day is equivalent to a minimum of eight hours, not including lunch. The scheduling/timing of the meetings are left to the discretion of the TCSI and are to be identified in the Integrated Master Schedule (IMS) provided to the Government.

Obtain physical access, from current SI, to all TRAP hardware and software within the Authority to Operate (ATO) boundary and/or Government owned for inspection and audit.

Task Management At a minimum, the TCSI task management efforts shall provide the following TRAP Task Management requirements:

TRAP Transition Task Initiation TRAP Resource Coordination and management TRAP Roles and Responsibilities.

Individual TRAP Security Clearances Evidence of Top Secret Individual Clearance for any TRAP system administrator and/or individual with root access for the TRAP SECRET Internet Protocol Router Network (SIPRNET) enclave.

The TCSI shall demonstrate that all individuals performing on classified aspects of TRAP have a current Secret Clearance and will maintain access to Secret Information. Secret access is required in order to attend meetings and perform daily work inside approved areas. Access to Secret data requires unescorted access into Secret spaces and access to Secret information and/or systems [SECRET Internet Protocol Router Network (SIPRNET)].

The TCSI shall have, and provide evidence of necessary Cybersecurity certifications as appropriate for individuals supporting the TRAP system.

Transition Task Execution At a minimum, Task Execution requires the TCSI to:

Perform quality assurance in accordance with the Quality Assurance Program Plan (QAPP).

Identify and manage risks and update the Risk Management Plan, as necessary.

Attend, provide agenda, provide meeting minutes, and participate in any ad hoc Working Groups, Integrated Product Teams (IPT), Technical reviews, Technical Interchange meeting, In Process Reviews (IPR), and/or any other system specific meetings to support the requirements of the Task.

The TCSI shall attend, provide agenda, provide meeting minutes, and participate in a Transition Readiness Review.

The TCSI shall attend the following meetings as provided in Table 1.

Table 1. Meetings Transition Task Performance Management.

Provide a Weekly Status Report.

Transition Task Closeout.

Provide orderly closeout of the TO including final delivery of any remaining Government products, and preparation of a final report to include lessons learned and analysis of task.

Integrated Master Schedule

4.1 Note: TRAP is a fictitious system; do not include any of TRAP Transition reportable events in the actual SI Consolidated Contract Integrated Master Schedule (IMS).

4.2 System IMS.

At a minimum, the TCSI shall submit an initial IMS consisting of the TRAP Transition Task Order (TO). This will become the basis of the System IMS for all other TRAP TO’s to build from. The Transition IMS and shall provide the ability to understand how it intends to manage the TRAP Transition with visibility of:

4.2.1 Tasks.

4.2.2 Activities.

4.2.3 Schedule. and

4.2.4 Deliverables.

5 Key Task Milestones At a minimum, the TCSI shall ensure and complete the following key milestones and associated milestone dates:

Table 2. Key Task Milestones

* If the scheduled calendar day occurs on a day that is not a normal business working day then the next occurring business day will be used

6 Performance Standards The TCSI shall be monitored against the following performance standards and Acceptable Quality Levels.

Table 3. Performance Standards

7 Applicable Documents and References The following documents provide essential programmatic information that needs to be considered in the contractor’s proposed Annex and Deliverable package.

TRAP Program Documentation

Table 4. TRAP Program Documentation & Databases *Note: The documents that are noted with an asterisk are notional. No copies will be provided.

TRAP System Documentation

Document / Reference Intended Use

Table 5. TRAP System Documentation *Note: The documents that are noted with an asterisk are notional. No copies will be provided.

TFITS Management Plans

Table 6. TFITS Management Plans

Other Guidance & Standards – Most current version of the following:

Federal Acquisition Regulation (FAR)

Table 7. Other Guidance & Standards

8 Deliverables and Schedule The below Deliverables are notional and are not considered to be all inclusive. The TCSI shall propose the most comprehensive and cost effective Deliverables tailored to the proposed solution. All Deliverables shall be delivered to the Government’s electronic repository (SharePoint) with a notification to the Contracting Officer, Contracting Officer’s Representative and the TRAP Project Manager.

Table 8. Deliverables 9 Government Furnished Equipment (GFE) and Information There is no GFE provided to the TCSI in performance of this contract. Available Government Furnished Information (GFI) is identified in Section 7.

10 Period of Performance The expected period of performance for this task is one (1) month period.

11 Place of Performance The primary place of performance will be the contractor’s facility. In addition, work will be performed at Marine Corps Base, Quantico (TRAP hosting environment).

12 Travel and Other Direct Costs All work is expected to be completed by personnel residing within the local commuting area to MCB Quantico and any travel necessary to complete the work is expected to be included within the TO’s FFP. While travel may be required to support the requirements of this Task, travel is expected to be limited. Travel shall be handled in accordance with the Joint Federal Travel Regulations (JFTR), at the direction and approval of the Contracting Officer’s Representative (COR). Unauthorized travel, or travel not coordinated with the COR shall not be reimbursed. Additionally, travel or other direct costs in excess of the Contract Line Item Number (CLIN) funded value shall not be reimbursed, unless changed by mutual agreement of the parties through a contract modification

Appendix A. Acronyms

A-1

Appendix B. Helpdesk Information & Historical Performance Figure 3 identifies the number of TRAP Users and their approximate locations

Figure 3. TRAP User Geographical Locations Average number and time calls are made to the TRAP Helpdesk are identified in Figure 4.

Figure 4. TRAP Helpdesk Call Profile e

B-3

The table below reflects the average number of calls being made to the TRAP Helpdesk by geographic location.

See TRAP technical data disk for historic TRAP helpdesk calls.

Table 9. TRAP Helpdesk Calls The length of an initial Helpdesk call between a User and a Helpdesk person is 10 minutes. The 10 minutes is discussion time and does not include the time a User is waiting for a Helpdesk person to answer the phone or being held in a queue for the first available Helpdesk person.

Appendix C. TRAP Government & Incumbent’s Organizational Structures

Figure 5. TRAP Government Management Organization

Figure 6. Incumbent's TRAP Team

C-2

Appendix D. TRAP System Objectives/Characteristics

System Performance

help desk

TRAP Performance Objectives

TRAP System Characteristics

* Based on 107 SLOC/FP ** Based on medium complexity of 9 NOTE 1: The TRAP Information Assurance Manager (Georgia) indicated that each month the incumbent contractor reviews 12 Information Assurance Vulnerability Alerts and finds 2 applicable vulnerabilities that need to be remediated. Also she indicates Oracle publishes a Critical Patch Update quarterly (October, January, April, July) identifying needed changes to the suite of Oracle products. From this quarterly notification one (1) database updated is required.

NOTE 2: The following images were presented at Industry Day as high level information. The RFP data takes precedent in the event there is conflicting information.

D-9 image1.png image2.png image3.png image4.png image5.png image6.png image7.png image8.png image9.emf image10.emf image11.emf image12.emf image13.emf image14.emf image15.emf image16.emf image17.emf image18.emf image19.emf image20.emf image21.emf image22.emf