Attachment 9

HTC711-09-R-0036

Attachment 9

Performance Work Statement

For Task Order 0001 Joint Flow and Analysis System for Transportation (JFAST) 23 June 2009

1.0 DESCRIPTION OF SERVICES

The contractor shall provide all services as stated in contract PWS and the Specific Services contained in this PWS:

1.1 Reserved.

1.2 Reserved.

1.3 Specific Tasks. The specific task areas with associated subtasks to be performed are identified as: Contract Management, Event and Exercise Support, Requirements Definition, Design and Development, Standards, Maintenance, System Administration, Information Assurance, Contingency Operations, Configuration Management and Enhancements .

1.3.1 Task Area 1 – Contract Management. This task area shall encompass overall contract management to include administrative, clerical, documentation, and related functions. The contractor shall designate an individual from the contractor’s resources to be the focal point for all contract management communications with USTRANSCOM, and to be responsible for ensuring successful accomplishment of PWS tasks. Point of contact (POC) information, to include name, title, phone number, and email address, are to be provided to the Contracting Officer at the Post-Award Conference. In support of this task, the contractor may be requested to provide documents such as Task Order Management Plans (TOMP), Monthly Status Reports (MSR), In-Process Reviews (IPR), Integrated Management Schedules (IMS), Contract Summary Reports (CSR), and Variance Reports. The contractor may also be requested to provide demonstration and teleconference support.

1.3.1.1 Task Area 1 Subtask 1 - Task Order Management Plan (TOMP). The contractor shall prepare a TOMP, encompassing all task orders, describing tasks, dependencies, management and technical approach, organizational resources, and management controls to be employed to meet cost, performance and schedule requirements throughout contract execution. The TOMP shall include the contractor’s approach to plan for, identify, monitor, and control risk in all phases of this effort. The contractor shall update the TOMP after receipt of each task order.

Deliverable: TOMP

1.3.1.2 Task Area 1 Subtask 2 - Monthly Status Reports (MSR). The contractor shall submit an MSR summarizing overall status, progress, and recommendations and shall include details of the work performed during the reporting period and results; work planned for the next month; dates and locations of IPRs conducted; labor hours worked by contractor and sub-contractor employees, identifying the name of each employee, the task(s) performed, and the hours performed on each task(s); trips conducted and meetings attended; cost, schedule, and performance variance that includes a description of how the variances were determined; potential risks for future progress; difficulties encountered; a comparison of the status achieved to planned goals and resources expended; and deliverables provided for each task area and any issues, problem areas, and items that require Government action; key personnel changes. Estimated and actual travel costs shall be reported by task order number, contractor name, trip location and purpose, and dates of travel. The MSR shall include copies of invoices for all travel performed during the reporting period.

Deliverable: MSR

1.3.1.3 Task Area 1 Subtask 3 - In-Process Reviews (IPRs). The contractor shall conduct and/or host IPRs on a quarterly basis or as the PM requires. The PM will determine dates and whether IPRs will be held at the contractor’s site, at USTRANSCOM, via video teleconference, web-cast, or conference call. IPRs shall summarize status, progress, new capability requirements and program schedule to include new requirements, risk, and remediation plan in any task area. The contractor shall prepare presentation materials and provide to the PM in accordance with the schedule in the table in Paragraph 1.4. At a minimum, the contractor shall include in the minutes a record of activity, decisions made, date, location and attendees.

Deliverable: Presentation Materials, IPR Meeting Minutes and Slides

1.3.1.4 Task Area 1 Subtask 4 - Integrated Management Schedule (IMS). The contractor shall develop and deliver to the PM an IMS that provides a schedule for all major milestones as currently tasked to the contractor. It shall also include anticipated future work to support schedule and workload de-confliction. The IMS shall include a high-level Master Schedule which lists the major milestones and completion dates associated with each. The IMS shall also include sub-schedules for each major milestone that lists closure criteria (specific actions that must be taken prior to reaching the milestone) and scheduled completion dates for each closure criterion. The schedule shall address design, development, test, and deployment for approved new system capabilities, and shall show the critical path. The contractor shall keep this schedule current, making schedule changes as necessary after coordinating these changes with the PM.

Deliverable: IMS (delivered with the MSR, or when circumstances necessitate a change to the schedule, whichever occurs first.)

1.3.1.5 Task Area 1 Subtask 5 - Contract Summary Report (CSR). The contractor shall prepare and provide to the COR a CSR to include a summary of work performed, a complete bibliography, where data was gathered, and from whom. The report shall identify processes used, lessons learned, actions of note, any identified gaps, and highlight any existing areas of concern.

Deliverable: CSR

1.3.1.6 Task Area 1 Subtask 6 - Variance Report. The contractor shall notify the PM and the COR when any contract line item number (CLIN) cost or CLIN schedule, as specified in the IMS, varies more than 5 percent from the baseline or latest PM-accepted change to the baseline. The contractor shall schedule a meeting with the PM and the COR when any CLIN cost or CLIN schedule, as specified in the IMS, varies more than 10 percent from the baseline or latest PM-accepted change to the baseline.

Deliverable: Variance Report

1.3.1.7 Task Area 1 Subtask 7 - Demonstration Support. The contractor shall conduct technical presentations or demonstrations to USTRANSCOM, other DOD commands, and other JFAST users when required by the PM. The contractor shall support government-led presentations or demonstrations when required by the PM. This support may include but is not limited to scenario and system set-up and other subject matter expert support.

1.3.1.8 Task Area 1 Subtask 8 – Teleconferences. The contractor shall conduct weekly telephone conferences with the PM to provide current status of all tasks.

1.3.2 Task Area 2 - Event and Exercise Support. Using off-site resources, the contractor shall provide technical support to USTRANSCOM for real-world events and Command Post Exercises (CPXs). Software development support for exercises may be required for approximately 50 days during the period of performance. This includes software troubleshooting and development in support of joint exercises. In addition, the contractor shall update the following DESS documentation to incorporate Spiral 7 requirements: Functional Documentation, System Documentation, Technical Documentation (DESS Architecture, External Interface Identification, External Software Item Interface Definition), JFAST Operator’s manual for simulation version and JFAST - SUSGEN User’s Setup Guide. Note, the contractor-developed system shall be capable of operation at the SECRET level and compatible for operations across the SIPRNET.

Deliverables: DESS Functional Documentation, System Documentation, Technical Documentation, Operator’s Manual, SUSGEN User’s Setup Guide

1.3.3 Task Area 3 - Requirements Definition. The Functional Manager will provide a prioritized list of functional requirements to the PM, who then will provide these requirements to the contractor. The contractor shall coordinate and integrate the technical expertise required to construct the system and associated databases (if applicable), and support field testing in a limited operational environment.

1.3.4 Task Area 4 - Design and Development. The contractor shall design, develop, and test new system capabilities using commercial best practices appropriate to the JFAST functional requirements. For System Development, the contractor shall:

Design, code, test, document and support full system integration of software and software releases (including software changes), assessments and prototypes supporting application development.

Propose release content and schedules based upon the known Government requirements and priorities.

Provide necessary models and simulations to support the verification and validation.

Provide software size, cost and schedule estimates and include justification and confidence level behind the estimates.

Continue to develop the Logical Data Model (LDM) in full compliance with DOD and USTRANSCOM data standards.

Deliver any developed corporate applications software artifacts to the Government.

1.3.4.1 Task Area 4 Subtask 1 - Software Development. The contractor shall employ software engineering commercial best practices in performing software development and support. The contractor shall designate a lead engineer for the software engineering and technical interactions with USTRANSCOM. The contractor shall be responsible for providing design, development, test and integration, configuration management (CM), quality assurance (QA), and documentation for all JFAST software. The contractor shall provide a Software Requirements Specification (SRS) that describes the user’s functional requirements in detail and in a form that will support design and development of software to satisfy these requirements. The contractor also shall provide a Database Design Description or Data Structure Design Description, if applicable. Prior to release of the software to the user test environment, the contractor shall deliver a Software Version Description Document (VDD) following the configuration management procedures. USTRANSCOM/TCJ6-PE will review and approve design documentation prior to contractor implementation. In addition, the contractor shall maintain a software problem database to document and track the progress of software fixes.

Deliverables: Database Design Description or Data Structure Design Description (if applicable); Software Requirements Specification, Software VDD.

1.3.4.2 Task Area 4 Subtask 2 - System Interface Development and Modification. The contractor shall support the Government in engineering and modifying existing system interfaces to meet current and projected data exchange requirements. Interfaces may be required between systems of other Government agencies or commercial systems. The contractor shall develop or update the Interface Requirement Specifications (IRS) and the Interface Requirement Design Document (IRDD). Note: An Interface Control Document (ICD) or equivalent document may substitute for the IRS and IRDD, if approved by the Program Manager. The contractor shall analyze changes to system interfaces to include (but not be limited to) requirements analysis, clarification of the requirement with the originator, recommendations regarding feasibility and cost effectiveness, what computer resources and man-hours the project shall require, projected delivery date, and the consequences of the proposed change. The contractor shall support the Government in initiating system interface engineering and modification efforts to implement Baseline Change Requests (BCRs) according to the priority established by the CMP and Configuration Control Board (CCB). The contractor shall ensure that all interface engineering and modification efforts comply with DOD Directive 8320.2, Data Sharing in a Net-Centric DOD, DOD Net-Centric Data Strategy, and standards set forth in the USTRANSCOM DTS Enterprise Architecture (EA). (Note: An ICD or equivalent document may substitute for the IRS and IRDD, if approved by the Program Manager.)

Deliverables: IRS and IRDD.

1.3.4.3 Task Area 4 Subtask 3 - Software and System Testing. The contractor shall support Government Witness Testing and Government User Acceptance Testing of the software that ensures the software is valid and requirements are met. The contractor shall not implement changes to the maintained software until the Government has completed acceptance testing and the Government has accepted the change as valid. The contractor shall perform the following testing-related activities: System, regression, and security testing, Functionality and/or integration test, Data management evaluation and provide SA support evaluation to assess various automated information system testing components and configurations, Documentation of test procedures and test results and Maintenance of test batch items in Configuration Management Library.

Deliverables: Software Test Procedures, Software Test Descriptions, Software Test Plans, Software Test Reports, Data Management and SA Support Evaluations

1.3.4.4 Task Area 4 Subtask 4 - Software Releases. The JFAST contractor shall provide JFAST releases on compact or digital video disc (CD or DVD). In support of this task, the contractor shall develop the necessary software release documentation and maintain it in a format acceptable to the Government. The contractor shall update the User Manual to provide USTRANSCOM functional personnel appropriate guidance for system operation. The User’s Manual shall be delivered electronically and embedded within each software version release. The contractor also shall deliver software source code with each release. The contractor may be required to demonstrate the functionality of the software at JFAST IPRs to support the major release deliveries, and at JFAST User Conferences. The contractor shall assist the Government in achieving software acceptance through USTRANSCOM security certification and accreditation process by accomplishing tasks described in Paragraph 1.3.8.3.

Deliverables: Software release (CD/DVD), User Manual (includes user security features), software source code, computer software release documentation, technical data

1.3.5 Task Area 5 - Standards

JFAST is part of the JDDA-E. The JDDA-E consists of Conceptual, Prescriptive, and Transition Architectures, referred to collectively as the Enterprise Architecture (EA). The JDDA-E embodies the Distribution Process Owner’s (USTRANSCOM) Corporate Services Vision (CSV) and Service-Oriented Architecture (SOA) concepts. Current governance, policy, architecture, standards, and specification documentation can be obtained by coordinating with the JFAST PMO, who, in turn, will contact USTRANSCOM J6-A. Other standards and specifications that are a part of the JDDA-E Prescriptive Architecture are being defined and will be made available after they are delivered. In the mean time, the contractor shall follow existing federal, DOD, and USTRANSCOM guidelines. The JFAST contractor shall abide by the requirements of the Department of Defense (DOD) Information Technology Standards Registry (DISR) and the DOD Net-Centric environment as reflected in the JDDA-E. The contractor shall show traceability to the DTS Enterprise Architecture (EA) content to include identifying anticipated standards, new Information Exchange Requirements (IER), and system interfaces. This traceability shall be reflected in DODAF products for which the contractor shall be responsible to develop or update.

DOD is implementing a Service-Oriented Architecture (SOA) environment to enhance net-centricity and data sharing within the Global Information Grid (GIG). As USTRANSCOM is in SOA discovery mode, the contractor shall consider SOA standards and protocols documented in the DISR and the Net-Centric Operations Warfare Reference Model (NCOW RM) during system development and enhancement. A SOA is a design style for building flexible, adaptable distributed-computing environments for the DOD. Service-oriented design is fundamentally about sharing and reusing functionality across diverse applications. Service-oriented design focuses on the following best practices: Make application and system functionality as accessible and reusable services, Expose service functionality through programmatic interfaces, Maintain an abstraction layer between service interfaces and service implementations, Describe service interfaces using standard metadata, Advertise and discover services using standard service registries, and Communicate with services using standard protocols.

USTRANSCOM's Data Management Strategy is documented in the Information Reference Model Manual which is the governing document for Enterprise Information Management within the Command. This document outlines program responsibility in support of the strategy. It mandates the creation and use of Standard Message Templates and Standard Reference Data (USTRANSCOM Reference Data Management - TRDM). The Enterprise Data Office (TC/J6-AD) will assist with the creation of the Standard Message Templates once validated through the Enterprise Requirements Management process. The JFAST Contractor shall ensure JFAST data is submitted and compliant with USTRANSCOM’s Distribution Process Interface Exchange Data Model (DPIEDM), and that no data business rule from that model is violated in the system, to include the database and interfaces.

1.3.5.1 Task Area 5 Subtask 1 - Architecture Support. The contractor shall develop or update, as required, the system and technical architecture documents (System View (SV) and Technical View (TV)) in accordance with the latest version of the DOD Architecture Framework (DODAF). These views shall employ the same language and references as the Operational Views (OV) that the government will supply. The contractor shall provide architecture data and products to support the Execution and Effects Review process.

Deliverable: Architecture products in latest DODAF format

1.3.5.2 Task Area 5 Subtask 2 - Logical Data Model. During the creation of any structure (databases, interfaces, application screens, etc) which stores, manipulates, transmits, or receives data, the contractor shall include any new data elements in the system Logical Data Model (LDM), to include a complete representation of the data elements that comprise that data. The complete representation must contain, at a minimum, the data element name, its definition, relationship with other data elements, its data type, data length and a list of enumerated values, if applicable. The complete representation must also employ a published specification language such as IDEF1X or UML. To support this task area, the contractor may be required to submit a complete description of the selected specification language and a completed data model to the Government for approval. The contractor shall coordinate with the PMO to consult with TCJ6-PE and/or TCJ6-AD for advice and review the USTRANSCOM Prescriptive Information Reference Model Manual of the JDDA-E for additional guidance on database design/development and Standard Information Exchange implementation. The contractor shall submit an updated LDM one month after each major release or as required by the Government. The contractor shall participate in the M&S data standardization working group.

Deliverable: LDM

1.3.5.3 Task Area 5 Subtask 3 - Data Structure Support. The contractor shall provide data structure support. Support tasks include, but are not limited to, the following: Manage the production data schema and objects, Develop a Data Dictionary, Coordinate use of the test data schema and objects, Manage user accounts and user permissions, Monitor data structure growth and performance, Perform data structure log/trace file maintenance, Support data backup and recovery, Support data replication processes and procedures, and Support the Execution and Effects Review (formerly Technical Assessment) activities and required updates.

The contractor shall provide data administration support for the system. The contractor shall make all data structure changes and modifications identified by the contractor or the Government according to the Configuration Management Plan (CMP). The contractor shall make all changes necessary to program documentation as a result of data structure changes. The Government or the contractor will report problems or requirements on a CR. The contractor shall evaluate problems/ requirements reported on the CR. This evaluation shall include, but not be limited to, requirements analysis, clarification of the problem or requirement with the originator, determining if correcting the problem is feasible and cost effective, what computer resources and man-hours the project shall require, its adherence to standards, and the consequences of the proposed change.

Deliverable: Data Dictionary

1.3.6 Task Area 6 – Maintenance.

1.3.6.1 Task Area 6 Subtask 1 – Software Maintenance. The Contractor shall provide software upgrades, testing and software fixes for JFAST. The contractor shall provide software maintenance support to include:

Quality assurance testing of JFAST software and support of the Government’s verification and validation software testing.

“Help desk” support for JFAST users.

Resolution of JFAST data integration issues.

Web page gatekeeper duties for the JFAST Secret Internet Protocol Router Network (SIPRNET) web pages. These duties shall include keeping the web pages updated with the latest downloadable JFAST software release, current training schedule, training class enrollment information, JFAST User’s Manual, JFAST lessons, frequently asked questions, JFAST reference file updates, and other information pertinent to the JFAST user community.

1.3.6.2 Task Area 6 Subtask 2 – System Maintenance. The contractor shall provide on-going support to maintain normal system operations. Normal operation for the system is interpreted to mean that the system software and database or data structure (if applicable) is available except during periods of routine maintenance or when software is released. The PM, after coordinating with the functional users, will approve the timing of any non-emergency contractor downtime for hardware and software maintenance. The contractor shall restore the maintained software to normal operation whenever the contractor is informed such normal operation has been interrupted. Software maintenance also includes those changes that are required to correct the performance of functions described in existing system or software documentation. The contractor shall obtain approval from the Government PM for required operational system downtime.

The contractor also shall provide maintenance and consultant support services on the JFAST application that is installed on the CFAST portal. The support services may include the hardware, software, reference files, security configuration, and established interfaces with CFAST that the JFAST system uses or modifies.

1.3.6.3 Task Area 6 Subtask 3 - System Interface Maintenance. System interface maintenance shall include those changes required to correct performance of data exchange functions described in current system or software documentation. The contractor shall support the Government in initiating system interface development efforts to correct problems according to the priority established by the PM.

1.3.6.4 Task Area 6 Subtask 4 - Site Preparation. The contractor shall support the installation of required hardware, communication lines, security and system software at the USTRANSCOM site.

1.3.7 Task Area 7 - System Administration (SA). The contractor shall provide on-site SA support to USTRANSCOM SAs for the system. This includes the following activities:

Plan, schedule and accomplish installation of new or modified hardware and software, to include system and security patches, updates, and enhancements for the system servers. Troubleshoot JFAST installation problems.

Support installation, optimization, operation, backup, recovery, modification, and upgrade of system servers and software and USTRANSCOM Classified Local Area Network (LAN) client workstations. Debug JFAST software and test software releases.

Monitor operational node performance and recommend possible improvements.

Accomplish routine system maintenance functions such as rebooting servers, running backups and coordinating hardware repair/replacement.

Troubleshoot and resolve system performance problems for system servers.

Provide technical support for system reengineering efforts.

Provide “Help desk” support to assist system users troubleshoot and correct JFAST problems.

Distribute JFAST software and documentation to registered users and maintain a database of registered JFAST users.

Work with Government security and networking personnel on system-related issues.

Support the Execution and Effects Review activities and required updates.

The contractor shall update the system administration manual to support the system that includes account administration; server installation, configuration, and administration; software installation; obtaining, generating, and updating reference files, shared drives, and web pages; troubleshooting and resolving operating system conflicts; maintaining logs; and creating reports, as required.

Deliverable: System Administration Manual

1.3.7.1 Task Area 7 Subtask 1 – Training. The contractor shall conduct JFAST training classes. These classes shall take the following form: Expert one-on-one training, as required, in the use of JFAST features, Classroom training in the use of JFAST to members of the JPEC, and Ongoing refresher training to members of the Joint Plans Division in the use of existing functions and newly fielded enhancements of JFAST.

1.3.7.2 Task Area 7 Subtask 2 – Ad Hoc Support. The contractor shall provide ad-hoc support to the TCCs. The JFAST FM will evaluate, prioritize, and monitor ad-hoc tasks and forward them to the JFAST PM for disposition. The JFAST PM will manage ad-hoc requests to ensure the ad-hoc support and other tasks in this PWS remain within the JFAST development team staffing level initially required to support the tasks in this PWS.

1.3.8 Task Area 8 – Information Assurance (IA). The contractor shall establish an IA Program to implement and sustain appropriate IA management, operational, and technical controls and processes as required to ensure compliance with DOD and Chairman Joint Chiefs of Staff (CJCS) requirements, and Joint Task Force – Global Network Operations (JTF-GNO) taskings. The contractor shall submit for Government approval an overarching security plan that describes their strategy for implementation of IA and Industrial Security requirements throughout the life of the contract. The contractor shall ensure that information system security engineering (ISSE) is employed to develop or modify any IA component of the system architecture. Such modifications will be made in compliance with all analogous or interfacing IA component(s) of the GIG Architecture and will be designed to make maximum use of the DOD enterprise IA capabilities and services. The contractor shall also support periodic Government inspections and reviews to ensure compliance with DOD IA requirements throughout the contract performance period. Contractor IA Program capabilities shall include but not be limited to processes and procedures for vulnerability management, patch management, incident response, Information Condition (INFOCON), system and application security, configuration management, risk management, and situational awareness.

1.3.8.1 Task Area 8 Subtask 1 – IA Design. The contractor shall protect and prevent unauthorized access to Government sensitive unclassified and classified data and IT resources supporting the system. The contractor shall ensure appropriate IA controls are designed, developed and implemented to provide for non-repudiation, confidentiality, integrity, and availability of Government systems, applications, and data. The contractor shall leverage, to the maximum extent possible, automated tools to identify and remediate vulnerabilities or weaknesses in the system design and coding that could be exploited or that may result in system or data compromise. The contractor shall work with other DOD activities and vendors as required to implement these IA controls. The contractor shall perform vulnerability management activities as part of all JFAST development and sustainment. The contractor shall coordinate with the PMO to document the installation of vendor security patches or support Government development of a Plan of Action & Milestones (POA&M) when patches cannot be applied. In coordination with the COR or PM, the contractor shall design, develop and implement secure JFAST applications and configurations through applying applicable DOD security technical implementation guides (STIGs), checklists, vendor security guidance, industry best practices, and applicable vendor product security patches. The contractor shall ensure JFAST applications are in compliance with DODI 8551.01p and leverage approved ports, protocols and services. An Information Assurance, Security Architecture and Engineering (IASAE)-qualified person shall participate in Government and contractor formal and informal design reviews to identify potential security weaknesses, deficiencies, and/or vulnerabilities in the design.

1.3.8.2 Task Area 8 Subtask 2 – Security Testing. The IASAE shall ensure appropriate security requirements are included as part of the JFAST requirements traceability matrix and are evaluated as part of the security test and evaluation (ST&E). Whenever possible the contractor shall support the ST&E in conjunction with scheduled system development and acceptance testing. As part of the contractor’s change control process, the contractor shall ensure participation by the IASAE- or IA-qualified representative to evaluate the impact of each change on security. The contractor shall document the results of this evaluation. When directed by the COR or PM, the contractor also shall test vendor security patches for JFAST production systems and applications to assess their impact on system functionality prior to their installation.

1.3.8.3 Task Area 8 Subtask 3 – DOD Information Assurance Certification and Accreditation Process. The contractor shall assume responsibility for management and update of existing system security documentation that were developed to facilitate JFAST’s security accreditation. The contractor shall perform security certification activities as required to maintain current system accreditation and support re-accreditation. The contractor shall support USTRANSCOM’s migration to the DOD Enterprise Mission Assurance Support Service (eMASS) system for automated accomplishment of the certification and accreditation process. The contractor shall update eMASS as required and provide supporting IA documentation for upload as artifacts in eMASS.

As a minimum, the contractor shall ensure compliance with applicable provisions of DOD Directive (DODD) 8500.1, Information Assurance; DOD Instruction 8500.2, Information Assurance Implementation; DODD 8570.1, Information Assurance Training, Certification and Workforce Management; CJCS Manual 6510.01, Defense-in-Depth: IA and Computer Network Defense (CND); DODI 8520.2, PKI and Public Key (PK) Enabling; DODI 8551.1, Ports, Protocols, and Services Management (PPSM); and DODI 8510.01 DIACAP guidance. JFAST has been designated Mission Assurance Category (MAC) III classified for the purposes of applying IA controls.

The contractor shall develop and maintain the following documentation required to support DIACAP accreditation decisions:

The Information Assurance and Industrial Security Plan (IA&ISP) shall serve as the overarching document. The contractor shall deliver the other documents listed below as appendices to the IA&ISP.

ISP - Information Security Plan CCB Charter CMP - Configuration Mangement Plan COOP - Continuity Of Operations Plan ISA - Interconnection Security Agreement System Classification Guide System Security Policy Risk Management Review Report In addition the contractor shall provide a complete DIACAP package consisting of:

SIP - System Identification Profile DIP - DIACAP Implementation Plan DIACAP Scorecard Deliverables: IA&ISP (and associated appendices), DIACAP package.

1.3.8.4 Task Area 8 Subtask 4 – Security Personnel Requirements. The contractor shall provide appropriate skilled and certified IA personnel resources to implement and manage the IA program in accordance with the applicable provisions of DODD 8570.01. The contractor shall coordinate with the Government to establish appropriate certification levels for each employee responsible for performing full and/or part-time IA related activities. Upon request by the Government, the contractor shall periodically report the certification status for each employee to satisfy Federal Information Security Management Act (FISMA) reporting requirements. In addition, contractor resources shall include IASAE-qualified personnel with experience, and certification to facilitate the design, development, and evaluation of JFAST IA technical controls.

1.3.9 Task Area 9 - Contingency Operations. The Continuity of Operations Plan (COOP) defines the methodology for providing a back-up capability for system users in the event the primary capability is not available. The contractor shall provide a Contingency Operations Document (contractor specific) that aligns with the Government COOP. The contractor’s Contingency Operations Document shall address SA and data storage support procedures at the recovery site. The hardware and software for the site will be Government-furnished to include all maintenance and licenses. Commercial Off-the-Shelf (COTS) software versions will be the same as the versions used in the production environment.

Deliverable: Contingency Operations Document

1.3.9.1 Task Area 9 Subtask 1 - Execution and Effects Review Documentation and Support Requirements. The contractor shall provide the necessary support, to include documentation and advice, to meet the USTRANSCOM security and technical requirements of the USTRANSCOM Execution and Effects Review process.

Deliverable: Execution and Effects Review documents

1.3.10 Task Area 10 – Configuration Management. This support is required to meet the DIACAP and USTRANSCOM technical and security requirements. The CM process facilitates orderly configuration identification, change identification and control, status reporting, and configuration auditing of product information for such beneficial purposes as to revise capability and improve performance, reliability, or maintainability; extend life; reduce cost; reduce risk and liability; or correct defects. CM ensures that changes take place in an identifiable and controlled process and do not adversely affect any properties of the other system or interfaces.

1.3.10.1 Task Area 10 Subtask 1 – Configuration Manager Responsibilities. The contractor’s Configuration Manager shall develop a CMP and processes that are consistent with and complement the Government CMP and processes. The contractor’s Configuration Manager shall establish and maintain the following: Baselines (versioning), Configuration identification, Change control, Configuration status accounting, CM audits, CM Repository, Process improvement.

Deliverable: Configuration Management Plan

1.3.10.2 Task Area 10 Subtask 2 – Configuration Identification. The contractor shall provide configuration identification as specified in their CMP. This identification may include hardware configuration items or software configuration items.

Deliverable: Updated configuration item listings

1.3.10.3 Task Area 10 Subtask 3 – Change Control. The contractor shall provide change control for all JFAST baselines and configuration items to include documentation, application source, and executable code. The contractor shall provide an automated configuration management tool to assist in this effort. This tool shall allow Government web access to ensure Government oversight of the change process. This tool will provide requirement and CR tracking. Additionally, the contractor shall provide a process to allow JFAST users to request software improvements and development of new JFAST capabilities.

1.3.10.3.1 Evaluating Change Requests. The contractor shall evaluate suggested software improvements and new capability development requests. The contractor shall document the evaluations. Evaluations include, but are not limited to, requirements analysis, clarification of the requirement with the originator, determining if the requirement is feasible and providing a cost estimate, what computer resources and man-hours the project shall require, its adherence to standards, and the consequences of the proposed change. In addition, the contractor shall ensure participation by the IASAE or a qualified IA representative to evaluate the impact of each change on security. The contractor shall document the results of these evaluations and provide them to the PMO for evaluation via the automated change control tool and/or as a separate document depending on the amount of information required or provided.

Deliverable: Change Request Evaluation Reports

1.3.10.3.2 Configuration Control Board (CCB). Upon request from the COR or PM, the contractor’s Configuration Manager may be asked to participate in the Government’s CCB. This participation will be as the liaison between the Government and contractor to provide any additional information which the CCB requires.

1.3.10.3.3 Configuration Status Accounting. The contractor shall provide, upon request of the COR or PM, status of all baselines, configuration items, and status of all outstanding change requests in the automated change control tool.

Deliverable: Status Accounting Reports

1.3.10.3.4 CM Audits. The contractor shall conduct a physical and functional configuration audit of each code baseline/release delivered to the PMO.

Deliverable: Audit Reports

1.3.10.3.5 Configuration Management Process Improvement. The contractor shall provide recommendations to improve the CM process during the annual CMP review.

Deliverable: Process Improvement Recommendations

1.3.11 Task Area 11 - Enhancements. The contractor shall provide FY 2010 enhancements as follows:

1.3.11.1 Develop Web-Based Capability – Phase I (optional). Develop a web-based capability to access and update a previously saved JFAST plan. Updates will initially include the airlift & sealift fleets as well as port capabilities. Need user updates from a web-based screen input. Design will not require user updating JFAST to be logged into the JFAST application. With proper authentication, the user will be able to access a JFAST plan and make updates to the air and sea fleets and port capabilities. This task would allow JFAST to react quickly to real-world time-sensitive operations, and to operate with the most current data possible, thus increasing accuracy of modeling and scheduling within JFAST.

1.3.11.2 Expand Sealift Late Analysis Categories. Expand sealift late analysis categories (Sea):

Align late analysis graphs with sealift cargo categories. Align with higher visibility cargo categories. Expand the profiler late analysis graphs to eight categories: Break-bulk (MSC cargo class 10), Break-bulk Ammo (MSC cargo class A0), Container (MSC cargo classes 50, 5V, and 5R), Container Ammo (MSC cargo class 5A), Vehicles (MSC cargo class 30), Non-self deploying aircraft (MSC cargo class 2N), Floating Craft (MSC cargo classes 2F and 3F) and POL (MSC Cargo class 80). This will result in the elimination of the PAX late analysis graphic from the profiler.

1.3.11.3 Add Aircrews as Scheduling Constraint. Track aircrews and constrain by augmented and basic aircrews. Allow the user to define stage location GEO code and regions to which crews would be allowed to fly.

1.3.11.4 Modify DESS for Compatibility with Integrated Global Transportation Network Exercise System. Update JDLM and JFAST to allow interface with the Integrated Global Transportation Network (GTN) Exercise System (IES). JDLM and JFAST must be able to feed the same level of information and data at the current level which is fed to the GTN Exercise System (GES). This development must take advantage of the new technologies being utilized under the IGC capability.

1.3.11.5 Airlift Shortfall Remark Not Matching Shortfall Condition. Make remarks match the condition which drive an actual transportation shortfall. Below are three specific examples of the problem:

1) Airlift remarks state: "Need en route to make STN--SK024". This does not capture the true transportation issue. This 'remark' was received when the APOD was placed in an exclusion area. With the APOD in an exclusion area, JFAST shortfalled all cargo/pax movement to the APOD. This 'remark' should indicate "No Route" or other similar statement.

2) Airlift remarks state: "No CGO/PAX A/C qualified--SK021". The actual transportation issue is the cargo is below minimum ACL.

3) Airlift remarks state: "##mil and #civ air--SK024". The airlift issue is there were no C5/C17 unloading permissions at the APOD. Cargo was shortfalled to the APOD as there were no aircraft to carry it. Airlift remark is misleading.

1.3.11.6 Update and Expand Checklist to Include All Modes. Expand checklist to include standard steps to follow (All) – Make the tool more user friendly for infrequent users – SDDC key exposes partially complete checklist that aids novice or infrequent user in setting up and using origin model, which needs expanding to include airlift and sealift model and post-model run analysis steps.

1.3.11.7 Model ILOCS With Mode Changes. Expand consideration of the effect of planned stops at intermediate locations (ILOC) so that the model will honor an ILOC between an origin and Port of Embarkation (POE), between a POE and Port of Debarkation (POD), and between a POD and destination to include the possibility of a transportation mode change at the ILOC.

1.3.11.8 Expanded Force Module Schedule Summary. Users are often asked to determine how many ships and aircraft it takes to move specific units. The units are usually identified as a force module. The Reports List interface includes a report named Force Module Schedule Summary that shows aircraft and ship types used in the schedule. However, the actual aircraft tail number and ship NISC and name are omitted. Add two new reports that show the ships and aircraft actually used in the schedule to deliver the force module.

1.3.11.9 Model Permissions by Berth. Add permissions (ship types, operators, etc.) by berth capability.

1.3.11.10 Payload Delivery Time Incorrectly Reported as Aircraft Arrival Time – It Should Account for Offload. The delivery time of the cargo is now being reported as the ETA of the aircraft at the offload event. This is too optimistic. It takes some time to discharge the payload from the aircraft before it can be classified as truly delivered. As the original symptom description indicates, the delivery time should be reported as the ETD of the aircraft from the airport at which the offload event occurs.

1.3.11.11 TPFDD Editor Not Carrying TPFDD Record “Non-Baseline” Data. Allow the build and import and import of a B8 data file, and allow JFAST to import the field.

1.3.11.12 Dynamically Adjust Port Processing Capability. Detect port operation enablers being deployed at run time and automatically adjust the airport’s or seaport’s personnel and cargo processing capability accordingly.

1.3.11.13 Modify Force Module Closure Report. The Reports List Force Module Closure Graphs Report includes an Excel option that displays some of the data graphed. Add the destinations(s) of the movement requirements assigned to the force module to the information in the Excel file only. This feature will be particularly helpful in situations where JFAST functionality is being used to support war games. In many cases, a force module will contain only one destination. If a force module has multiple destinations, then list them all. This will allow the user to view them all and to pick the one he wants to report.

1.3.11.14 Some PAX RLN`s Incorrectly Show Shortfall in Ground Model Which Run Log Describes as an Accompanying Pax issue (But No Cargo in Record). Accompany flag in TpDetail is incorrectly set to .T. for the pax portion of split shipments. Set the accompany flag to .T. for req.

1.3.11.15 Add Multi Set of FIC to 0 and TUCHA Bump. JFAST users at the Center for Army Analysis (CAA) often use JFAST for TPFDD development and editing for future force structure studies. As available TUCHA data will normally contain only current or historical force structure data, users are often working with TPFDD data that was created as non-standard units. CAA has recently developed the capability to create future force structure TUCHA data. The users now want those non-standard RLNS to become standard which will reflect the force structure data in the selected TUCHA. This may currently be accomplished by (one RLN at a time) using the UTC editor interface to reset the FIC to zero for the assigned UTC. Add the capability to apply this "TUCHA refresh" edit as a mass edit capability against an entire collection of records or marked records. There is no need to change the UTC assigned, but only to reset the FIC to 0 while at the same time pull the standard passenger and cargo detail from the selected TUCHA reference data.

1.3.11.16 Add Foreign Military Sales (FMS) Modeling Capability. Fusion Center requires capability to model force flow, FMS, and sustainment flow during execution planning. Specifically, planners require analysis of movement requirements from origin to final destination with user identified waypoints throughout the transportation pipeline.

1.3.11.17 Import Ground Assets from IRRIS. Establish an interface with IRRIS for the purpose of user controlled transfer to JFAST select CONUS ground transportation data critical to accurate operational planning and transportation modeling. Interface should allow a “snapshot in time” transfer and translation of assets availability data and other available related information that may affect the modeling of CONUS ground transportation in JFAST.

1.4 Deliverables. For this task order, the contractor shall provide the deliverables according to the delivery schedule specified in the table below:

PWS

Task#

By End of Contract.

(e-mailed) NLT 10 days after receipt of Government comments.