Exhibit_2c__TRAP_Software_Development_PWS_Final_.docx

Total Force Information Technology Systems

TRAP Software Development

ECP0001

Performance Work Statement

February 2014 Table of Contents

List of Figures

List of Tables

Introduction Purpose and Scope This Performance Work Statement (PWS) identifies requirements and performance standards for the elicitation, design, development and deployment of Engineering Change Proposal (ECP) 0001, Personnel Contact Data. The Total Force Information Technology Systems (TFITS) Consolidated Systems Integrator’s (TCSI’s) response shall encompass all required systems engineering processes as reflected in the Marine Corps Systems Command Technical Review Handbook, v1.04, April 2009 and the TFITS Systems Engineering Plan.

Background The TFITS RFP Assessment Program (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 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 (C#) on an ASP.Net framework. The database is built in Oracle 11g.

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

Figure 1. TRAP System Operational Diagram

Figure 2 provides the TRAP architecture layout.

Figure 2. Physical Representation of the TRAP Production Architecture ECP 0001 Overview The TRAP Advocate identified the need to expand existing personnel information captured in the TRAP system to provide an ability to recall personnel as well as having emergency contact information within the TRAP system. Information to be added for each person includes:

· Commanding Officer

· Supervisor Information

· Emergency Information In addition, the Advocate has stated that they want new reports to be made available.

The Advocate has developed initial screen mock-ups which are provided as Government Furnished Information (GFI) in Appendix B. The TRAP Project Manager’s initial assessment indicates ~30 new data elements will be required to support the new capability along with a number of new reports for both Basic and Super Users and is a third octet change with full technical review.

Software Development Requirements Analysis Phase.

The key Objective of the Requirements Analysis Phase is to transform the Government’s needs into a technical view of a required product that will deliver those needs. Efforts involve defining User needs and requirements in the context of planned User use, environments, and identified system characteristics to determine requirements for system functions. At a minimum, the TCSI shall:

Elicit TRAP ECP 0001 derived requirements.

Perform an iterative process of decomposing TRAP ECP 0001 requirements into system functional requirements and establishing traceability.

Maintain traceability between the TRAP ECP 0001 derived and Government- provided requirements.

Align TRAP ECP 0001 requirements analysis efforts with Marine Corps Systems Command (MCSC) acquisition requirements (TFITS Management Plans, and Systems Engineering Technical Review (SETR) process).

Provide TRAP ECP 0001 documentation needed to support the MCSC SETR process for System Requirements Reviews (SRR) and System Functional Reviews (SFR).

Document the TRAP ECP 0001 functional baseline.

System Design Phase.

The overarching objective for the System Design Phase is the on-time delivery to the Governemnt of Government-approved documentation providing the detailed design of each configuration item in the approved product baseline. The System Design phase produces a design that is based on the functional descriptions and products developed during the Requirements Analysis phase. The design is reflected in the products developed and delivered by the TCSI.

At a minimum, the TCSI shall:

Provide the TCSI’s TRAP ECP 0001 design process, including the use of design and modeling tools, analyses, and tradeoffs.

Align the TCSI’s process with the TFITS Management Plans and the MCSC SETR process for Preliminary and Critical Design Reviews (PDRs/CDRs).

Provide the TRAP ECP 0001 documentation needed to support the PDR and CDR.

Document the TRAP ECP 0001 Allocated and Product baselines.

Development Phase.

The prime objective for the Development Phase is the on-time delivery of a Government-tested and accepted capability solution.

At a minimum the TCSI shall:

Develop, integrate, assemble and test TRAP ECP 0001 capability.

Provide TRAP ECP 0001 in-process reviews.

Align the TCSI’s process with the TFITS Management Plans and MCSC SETR process for TRAP ECP 0001 Test Readiness Review (TRR), System Verification Review (SVR), Production Readiness Review (PRR) and Physical Configuration Review (PCR).

Provide documentation needed to support the TRAP ECP 0001 TRR, SVR, PRR, and PCR.

Support TRAP ECP 0001 Government Acceptance Testing, code review, and cyber-penetration testing.

Deployment Phase.

The prime objective for the Deployment Phase is the deployment of the Government- accepted capability into the production environment in accordance with the established performance standards.

At a minimum the TCSI shall:

Document the TCSI’s deployment process.

Validate that all certifications and accreditations are in place prior to deployment.

Prepare the system user community to receive and use capability.

At a minimum the TCSI shall:

Provide TRAP Support Documentation and Materials.

Ensure all TRAP user support materials are updated to reflect the changes being introduced by ECP 0001.

Provide User Training.

Develop and deliver differences training materials to support the deployment of ECP0001.

Warranty the software for three months from any defects.

Coordinate and deliver the deployment package within the PDSS Release Management process.

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

TRAP Software Development Task Initiation TRAP Software Development Resource Coordination and management TRAP Software Development Roles and Responsibilities.

Individual TRAP Software Development Security Clearances Provide evidence of Top Secret Individual Clearance for any TRAP system administrator and/or individual with root access for the TRAP SIPRNET enclave.

Provide evidence that all individuals performing on classified aspects of TRAP have a current Secret Clearance and will be required to 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)].

Provide evidence of necessary Cybersecurity certifications as appropriate for individuals supporting the TRAP system.

Software Development Task Execution At a minimum, Software Development Task Execution requires the TCSI to:

Perform quality assurance in accordance with the QAPP.

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

Attend, provide agenda, provide meeting minutes, and participate in any adhoc 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.

Attend the following meetings as provided in Table 1.

Table 1. Meetings Software Development Task Performance Management Include Software Development activities in the SPDSS Monthly Status Report (MSR).

Software Development Task Closeout Provide orderly closeout of the task order 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 TRAP is a fictitious system, do not include any of TRAP System Integrated Master Schedule (IMS) reportable events in the actual SI Consolidated Contract IMS.

System IMS.

At a minimum, the TCSI shall incorporate the TRAP Software Development into the System IMS and shall provide the ability to understand how it intends to manage the TRAP Software Development with visibility of:

4.1.1 Tasks;

4.1.2 Activities;

4.1.3 Schedule;

4.1.4 Deliverables; and

4.1.5 Other TRAP Task Orders (TOs).

Key Task Milestones The key milestone dates in the below table are based on an award of ECP 0001 Task Order (TO) on April 01, 2014.

Table 2. ECP0001 Milestones TRAP System Enhancement- ECP 0001 Performance Work Statment

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

· SETR results

· = Standard

· Monthly Status Reports

· Updated IMS

· GAT Scorecard

· Five business day negative schedule variance.

· Training plans

· User post-training surveys

· GAT Scorecard

· = Standard

Table 3. Performance Standards

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

Program Documentation

Table 4. TRAP Program Documentation & Databases

* Note: The documents that are noted with an asterisk are notional. No copies will be provided.

Systems Documentation

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

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.

Deliverable Number

Update for PDR/CDR

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

Period of Performance The expected period of performance for this task is nine months.

Place of Performance The primary place of performance will be the TCSI’s facility. In addition, work will be performed at Marine Corps Base, Quantico (TRAP hosting environment) 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-2

Appendix B. Screen Mock Ups

Note: New Page

Note: Modified Super User Page (adds the Recall/Emergency button)

Note: Modified Basic Users Report Screen (adds reports #3 and #4).

Note: Modified Super Users Report Screen (adds reports #6 and #7).

B-5

Appendix C. TRAP ECP0001 Characteristics

Table 9 represents the TRAP system characteristics after ECP001 software is integrated into the production code.

Table 9. TRAP System Characteristics

* Based on 107 SLOC/FP ** Based on medium complexity of 9 *Actual characteristics will be representative of TCSI’s solution

The following figures provide the TRAP database architectures. Figure 5 is the actual database architecture and Figure 6 is the projected database architecture the TRAP Project Management Office (PMO) has come up with as part of its estimation effort.

Figure 3. TRAP Database Architecture (pre-ECP0001)

Figure 4. Notional TRAP Database Architecture (past-ECP0001)*

* Developed by the TRAP PMO as part of its estimation effort.

C-3 image1.png image2.png image3.png image4.png image5.png image6.png image7.png image8.png image9.emf image10.png