HC1047-14-R-4012_DRAFT.doc

Section B - Supplies or Services and Prices

Task 1 Enterprise IT Policy and Planning

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 1 – Enterprise IT Policy and Planning in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Base Year Period of Performance (TBD, 2014 -- TBD, 2015)

*** THIS CLIN SHALL BE BILLED / PAID MONTHLY IN ARREARS ***

FOB: Destination

NET AMT

Task 2 Engineering Activities

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 2 – Engineering Activities in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Base Year Period of Performance (TBD, 2014 -- TBD, 2015)

NET AMT

Task 3 Functional Support Tasks

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 3 – Functional Support Tasks in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Base Year Period of Performance (TBD, 2014 -- TBD, 2015)

NET AMT

Cost

ODC's

COST

ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31. No profit shall be paid on purchases made under this CLIN.

Base Year Period of Performance (TBD, 2014 -- TBD, 2015)

ESTIMATED COST

Cost

Travel

COST

Travel Costs. All Travel must be pre-approved by the COR identified in clause 52.204-9000 prior to the Contractor incurring the cost in support of the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013. Travel shall be in accordance with FAR Subpart 31.205-46.

Base Year Period of Performance (TBD, 2014 -- TBD, 2015)

ESTIMATED COST

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 1 – Enterprise IT Policy and Planning in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year One Period of Performance (TBD, 2015 -- TBD, 2016)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 2 – Engineering Activities in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year One Period of Performance (TBD, 2015 -- TBD, 2016)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 3 – Functional Support Tasks in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year One Period of Performance (TBD, 2015 -- TBD, 2016)

NET AMT

Cost

COST

ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31. No profit shall be paid on purchases made under this CLIN.

Option Year One Period of Performance (TBD, 2015 -- TBD, 2016)

ESTIMATED COST

Cost

COST

Travel Costs. All Travel must be pre-approved by the COR identified in clause 52.204-9000 prior to the Contractor incurring the cost in support of the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013. Travel shall be in accordance with FAR Subpart 31.205-46.

Option Year One Period of Performance (TBD, 2015 -- TBD, 2016)

ESTIMATED COST

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 1 – Enterprise IT Policy and Planning in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year Two Period of Performance (TBD, 2016 -- TBD, 2017)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 2 – Engineering Activities in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year Two Period of Performance (TBD, 2016 -- TBD, 2017)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 3 – Functional Support Tasks in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year Two Period of Performance (TBD, 2016 -- TBD, 2017)

NET AMT

Cost

COST

ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31. No profit shall be paid on purchases made under this CLIN.

Option Year Two Period of Performance (TBD, 2016 -- TBD, 2017)

NET AMT

Cost

COST

Travel Costs. All Travel must be pre-approved by the COR identified in clause 52.204-9000 prior to the Contractor incurring the cost in support of the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013. Travel shall be in accordance with FAR Subpart 31.205-46.

Option Year Two Period of Performance (TBD, 2016 -- TBD, 2017)

ESTIMATED COST

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 1 – Enterprise IT Policy and Planning in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year Three Period of Performance (TBD, 2017 -- TBD, 2018)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 2 – Engineering Activities in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year Three Period of Performance (TBD, 2017 -- TBD, 2018)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 3 – Functional Support Tasks in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year Three Period of Performance (TBD, 2014 -- TBD, 2015)

NET AMT

Cost

COST

ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31. No profit shall be paid on purchases made under this CLIN.

Option Year Three Period of Performance (TBD, 2017 -- TBD, 2018)

ESTIMATED COST

Cost

COST

Travel Costs. All Travel must be pre-approved by the COR identified in clause 52.204-9000 prior to the Contractor incurring the cost in support of the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013. Travel shall be in accordance with FAR Subpart 31.205-46.

Option Year Three Period of Performance (TBD, 2017 -- TBD, 2018)

ESTIMATED COST

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 1 – Enterprise IT Policy and Planning in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year Four Period of Performance (TBD, 2018 -- TBD, 2019)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 2 – Engineering Activities in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year Four Period of Performance (TBD, 2018 -- TBD, 2019)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 3 – Functional Support Tasks in accordance with the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013 and the Contractor's proposal dated TBD.

Option Year Four Period of Performance (TBD, 2018 -- TBD, 2019)

NET AMT

Cost

COST

ODCs must be incidental to the work being performed under this contract. The Contractor will provide ODCs on a cost reimbursement basis only. All ODCs must be pre-approved by the COR prior to the Contractor incurring the cost. The Contractor shall be authorized to invoice on a monthly basis and in accordance with FAR Part 31. No profit shall be paid on purchases made under this CLIN.

Option Year Four Period of Performance (TBD, 2018 -- TBD, 2019)

ESTIMATED COST

Cost

COST

Travel Costs. All Travel must be pre-approved by the COR identified in clause 52.204-9000 prior to the Contractor incurring the cost in support of the Performance Work Statement entitled, GCSS-J Data Applications & Integration Analysis Support dated 5 November 2013. Travel shall be in accordance with FAR Subpart 31.205-46.

Option Year Four Period of Performance (TBD, 2018 -- TBD, 2019)

ESTIMATED COST

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

As of 11/06/2013 Contract Number:

1. Contracting Officer Representative (COR).

a. Primary COR.

Name:

Department of Defense Activity Address Code (DODAAC):

HC1047

Phone Number:

Fax Number:

E-Mail Address:

b. Alternate COR.

Name:

Phone Number:

Fax Number:

E-Mail Address:

2. Contract or Task Order Title. Global Combat Support System-Joint (GCSS-J) Data Applications & Integration Analysis Support

3. Background. GCSS-J is an initiative that provides end-to-end visibility of retail and unit level Combat Support (CS) capability up through National Strategic Level, facilitating information interoperability across and between CS and Command and Control (C2) functions. GCSS-J provides enhanced CS situational awareness to the joint warfighter by integrating CS information into the C2 environment, and facilitating communications between the forward deployed elements and the sustaining bases, ultimately resulting in faster, more efficient decision making by the joint warfighter. GCSS-J significantly increases access to information stored in disparate databases via a single sign on, web portal application, using a Secret Internet Protocol Router Network (SIPRNet) Public Key Infrastructure (PKI) hard tokens. The GCSS-J infrastructure provides secure web-access, discrete user account administration, data mediation, and enterprise management features that facilitate delivery of capabilities to meet the vision of a net-centric architecture, as well as the integration of information across combat support functional areas. This PWS describes the functions to be performed in supporting these ongoing requirements.

4. Objectives: The objective is to provide technical support to the GCSS-J Program Management Office (PMO) with data engineering activities. Specifically, the contractor shall conduct the following activities during the execution of the contract: analysis of GCSS-J authoritative and non-authoritative data sources for their ability to satisfy GCSS-J requirements; analysis of GCSS-J Requirements for completeness; quality assurance analysis of GCSS-J authoritative and non-authoritative data sources; query development, which supports the GCSS-J software development effort; and test and evaluation of GCSS-J software products, to ensure software quality assurance and the software’s ability to satisfy the GCSS-J requirements.

5. Scope. The contractor shall provide engineering, technical, and program support services required under the task areas as described in Section 6 of this PWS. The scope of this effort will span the breadth of the GCSS-J mission which is to provide enhanced decision support and situational awareness to the warfighter. The contractor shall perform the role of Subject Matter Expert (SME) and have an intimate knowledge of Joint Doctrine and the Joint Capability Areas (JCA) defined in joint Pub 4.0. The following task areas support the GCSS-J mission:

6. Performance Requirements

6.1 Task 1 – Enterprise IT Policy and Planning (A001)

This task provides the technical and functional activities needed for the Program Management aspects of this PWS. It includes productivity and management methods such as Quality Assurance, Progress/Status reporting, and Program Reviews and provides centralized administrative, clerical, documentation and related functions. The contractor shall report all subtasks and activities under this task in the monthly status report. All subtasks and activities performed in support of this task shall be reported against the GCSS-J Work Breakdown Structure (WBS).

6.1.1 Subtask 1.1: Contract Management Plan and Detailed Work Plan (A002) The contractor shall prepare a Contract Management Plan describing the technical approach, organizational resources and management controls to be employed to meet the cost, performance and schedule requirements throughout contract execution. The contractor shall provide a Detailed Work Plan that further defines the activities to be performed under this contract. The Detailed Work Plan shall be coordinated and approved by the COR.

Subtask 1.1 Deliverables:

Contract Management Plan

Detailed Work Plan

6.1.2 Subtask 1.2: Status Reports (A003) The contractor is required to prepare and submit bi-weekly status reports, described in Activity 1.2.1, and monthly progress, status and management reports, described in Activity 1.2.2. In addition, the contractor is required to participate in Bi-Monthly GCSS-J In-Process Reviews (IPRs), described in Activity 1.2.3, where they will provide a high-level summary status briefing. The Contractor shall prepare the Work Package Plans (WPP). The WPPs shall list the activities involved in each work package. Work packages that are open and/or closed must be coordinated, signed, and approved with the COR before any additions or changes are made to the work package. This includes additions and/or deletions to the WBS elements, scope, and schedules. The format for the WPPs is contained in Appendix B.

As part of the monthly status reports and IPRs, the contractor is required to report against the work packages associated with GCSS-J Work Breakdown Structure (WBS) using MS Excel in the required and approved government format. The WBS is contained in Appendix A.

Subtask 1.2 Deliverables:

Work Package Plans (WPP)

Work Breakdown Structure (WBS)

Monthly Status Reports

Activity 1.2.1 Bi-weekly Status Reports (A004) The contractor shall prepare a bi-weekly status report that will address the progress of work accomplished during the previous reporting period, outstanding issues or concerns, plans and activities for the next reporting period, and status of personnel staffing. This bi-weekly report will include the monitoring of quality assurance, configuration management, security management progress/status reporting and program reviews applied to each task in this PWS. This bi-weekly report shall also address all activities performed within a Task to the Subtask level, broken out by capability package, work order, or increments, the individual(s) who worked on each effort and their labor category, and the number of hours spent per effort.

At a minimum the bi-weekly status report will include:

(1) The project task schedule showing any proposed changes, the reasons for the changes, and the potential impact on the Integrated Master Schedule (IMS).

(2) Integrated project schedule showing milestones, technical changes, testing, software development, incremental deliverables to include integration and coordination with the GCSS-J Prime Integrator.

(3) Descriptions of activities and deliverables during the week with regards to the PWS. The description will include problem definitions and recommendations for program resolutions.

(4) Exercise and site support, trip reports, technical visits, technical reports, user/developer training, and related results.

(5) Planned activities for the next reporting period including technical data to be submitted.

(6) Personnel reassignment impacting contract work.

The contractor shall submit the bi-weekly status report to the COR via email by the 1st business day of every other week.

Activity 1.2.1 Deliverable:

Bi-Weekly Status Report

Activity 1.2.2 Monthly Financial Management Report (A005) This section will include a monthly Cost Performance Report (CPR) and other cost reports which will include a summary of the planned costs on a monthly basis and the actual costs incurred. The contractor shall explain deviations from the planned expenditures. Also, the total amount of money projected vs. money remaining will be shown. The contractor shall notify the COR, Alternate COR and/or Contracting Officer when 75% of resources have been expended and provide an estimate when resources will be fully expended. The format for the CPR is included in Appendix C.

Activity 1.2.2 Deliverables:

Monthly Financial Report

Cost Performance Report

All activities conducted under this subtask shall be reported in the bi-weekly status report. All activities performed in support of this subtask shall be reported against the GCSS-J WBS.

6.2 Task 2 – Engineering Activities

6.2.1 Subtask 1 – Data Analysis (B001) The contractor shall respond to data analysis tasks from the PMO. These tasks are comprised of new requirements/capability requests review, Combatant Command 129 Requirements Document (CC129) review, approved user requirements, and defects encountered during system and acceptance testing. Upon data analysis request, the contractor shall respond in writing via email to minimally, the requestor, COR and alternate COR. The contractor shall provide subject matter expertise to the existing GCSS-J data sources: Integrated Data Environment Global Transportation Network Convergence (IGC), Joint Operational Plans and Execution System (JOPES), National Geo-Spatial Intelligence Agency - Airfields, Seaports (NGA), Defense Manpower and Data Center (DMDC), Global Decision Support System (GDSS) and Current Forces Database (CFDB), Palanterra (NGA), Modernized Integrated Database (MIDB), Theatre Construction Management System (TCMS),Web Bulk Petroleum Contingency Report (WebREPOL). and the contractor shall analyze a maximum of eight (8) potential new GCSS-J data sources per year (Base plus option years).

6.2.2 Capability Functional and Technical Analysis (B002) The contractor shall examine user stories, functional and technical requirements and/or issues to provide effective solutions for integration efforts. In addition to examining user stories (The Program’s Agile Development Process), the contractor shall also participate in SCRUM, an agile development term, meetings on an as needed basis, sprint reviews and participate in testing for each development sprint.

These studies may include, but are not limited to, the following considerations:

· Requirements Analysis

· Data availability

· Data quality (to include but not be limited to accuracy, completeness, correctness, response, etc)

· Compliance with Legal and Regulatory Guidance

· Interoperability

· Security

· Standards

· Data Sharing

· Functional and Technical Integration

· Benchmarking/Base lining

The contractor shall respond to each task with a Data Analysis Report (DAR) using the format specified in Appendix D. Upon written request of analysis of new application databases, the contractor shall produce a New Source System Analysis technical report instead of a DAR. This technical report shall include, but not be limited to the following information:

· Definition and detailed description of data source and system (if applicable)

· List of tables, which would provide the data to satisfy the GCSS-J data requirements

· A detailed description of the sources ability to meet the specified requirement and any other CC129 Requirements not currently implemented

· Recommendation on attributes by which to retrieve the requested information

· Documentation on indexes or lack of indexes on attributes used to retrieve required information

· Recommended additional access controls

· Recommended additional queries

· Analysis of source systems data quality

Based on defects received from testing or the user community and approved by GCSS-J Systems Engineering or GCSS-J Configuration Management Board, the contractor shall analyze deficiencies and propose solutions to the problem. Problem solution shall be documented as input to the GCSS-J defect tracking system (A009), currently in the Rally tool. A maximum of 50 defects requiring data analysis is anticipated during each year (base plus option years).

6.2.2 Deliverables:

Data Analysis Report (DAR)

Defect Tracking System Input

All activities conducted under this subtask shall be reported in the bi-weekly status report. All activities performed in support of this subtask shall be reported against the GCSS-J WBS.

6.2.3 GCSS-J Source System Document Management. (B003)

Upon a change to GCSS-J source database access (e.g. new tables or views required), the contractor shall provide input to GCSS-J/Source System Interface Control Documents (ICD) using template provided in Appendix E. The contractor shall review the GCSS-J data source ICDs annually to ensure accesses are accurate. The contractor shall support GCSS-J PMO in creating MOAs for the new data sources.

6.2.3 Deliverable:

New Source System Analysis Technical Report

Input to Interface Control Document

All activities conducted under this subtask shall be reported in the bi-weekly status report. All activities performed in support of this subtask shall be reported against the GCSS-J WBS.

6.2.4 Subtask 2 – Query Design and Development (B004)

The contractor shall design the GCSS-J Query and Reporting Strategy. Specifically, the contractor shall analyze the requirements, use the provided authoritative data source, or in the event a data source has not yet been provided, locate data sources and algorithms to satisfy those requirements; examine the database structure, schemas, its architecture and the sources for accuracy and currency, determine options for accessing the data, and develop the SQL statements to execute the queries. The Design Strategy shall be documented in the form of an initial GCSS-J Query Specification. The contractor shall submit the query spec to the COR, Alternate COR, Chief Engineer, and the capability development team for review. Query development is accomplished by the capability developer. Although it is not the contractor’s primary responsibility, the contractor shall provide query/report development support upon the COR’s request.

The contractor shall also review and create new User Stories and Acceptance Criteria in support of the GCSS-J Agile Development process. Any reports developed by the contractor shall be integrated into GCSS-J. The contractor shall work with the lead GCSS-J integrator to include their report into GCSS-J. The contractor shall complete an initial test of all queries, during the contractor integration phase of software development. If poor query performance is discovered during the query development phase, the contractor shall document query performance statistics in the GCSS-J defect tracking system and report to the PMO as directed in the testing section of the PWS.

Subtask 2 Deliverables:

Query Specification

User stories

Acceptance Criteria

Input to GCSS-J Defect Tracking System

All activities conducted under this subtask shall be reported in the bi-weekly status report. All activities performed in support of this subtask shall be reported against the GCSS-J WBS.

6.2.5 Subtask 3 – Application Design and Development Support (B005)

The contractor shall assist the application developer, as needed, in implementing the approved solution. The contractor shall assist the application developer by providing expertise including, but not limited to the following:

· System Functionality clarifications

· Data related functionality constraints (Lack of data, because of poor source system quality)

· Functional algorithms in support of data requirements applicable display mechanisms to support data availability from authoritative/approved sources Expertise in the flow of information displayed by GCSS-J (how and in what order is information displayed from the application)

· Identification of the ability to drill down to access more information within GCSS-J; and the order in which information should be presented

· Participate in team SCRUM meetings on an as needed basis

The contractor shall also perform periodic updates of the GCSS-J Combat Support Applications Data Base (CSAPPDB) to include, but not be limited to, seaport and reference tables. Using current data obtained from NGA, SDDC and other government supplied data sources as provided, the contractor shall analyze the differences between the new and existing tables, build the required data structures, and deliver the new tables and the associated documentation in a computer software end item (e.g., Oracle export file format). A maximum of four (4) updates of the seaport and reference tables is anticipated over a five year period. Documentation shall include, but not be limited to, schema of table structure, table descriptions, size, and number of records in each table.

Subtask 3 Deliverable:

New tables using an Oracle export file format

All activities conducted under this subtask shall be reported in the bi-weekly status report. All activities performed in support of this subtask shall be reported against the GCSS-J WBS.

6.2.6 Subtask 4 – System Test Support (B007) The contractor shall support the GCSS-J development team during integration testing by testing the developed capabilities against the GCSS-J requirement. The contractor shall test according to the IMS and upon receipt of an email request for capability compliance testing by the PMO or upon request via the GCSS-J defect tracking system currently in Rally. The contractor shall test GCSS-J capabilities, widgets and reports for data quality and benchmarking. The contractor shall provide performance benchmarking on all GCSS-J queries. The contractor shall document the sources that provide poor query performance. Queries with poor performance response times greater than two (2) minutes shall be documented in the GCSS-J defect tracking system. The contractor shall advise on data quality improvements and provide input to the business process to improve the updates to the CSAPPDB. All daily quality and performance related topics will be provided in the form of a query review technical report and/or presentation materials included in the daily Scenario Assessment Report (SAR). The contractor shall support the Government by providing input parameters, expected results when available to the GCSS-J testing team and by participating on the testing team (performing tests). Also, the contractor shall participate in regular sprint development reviews at the end of each sprint cycle and their assessments shall be based on acceptance criteria at sprint planning meetings and from ad-hoc testing. In support of System Acceptance Test and Operational Test and Evaluation, the contractor shall provide input to the test scenarios, which will be the testing strategy used during the test events. The contractor shall provide input and guidance to the team developing test scenarios to simplify the test strategy. The contractor shall identify a test methodology which would use widget communication along with the appropriate input parameters to test multiple widgets in a dashboard with minimal user input. The contractor shall provide the input necessary to support the development of an accurate assessment of the GCSS-J capabilities. Also, in support of the test events, the contractor shall provide input and support to “Truth Data Testing” and Key Performance Parameters (KPPs) Testing.

Truth data testing is the testing of GCSS-J and GCSS-J source systems with the purpose of comparing the results returned and the intention of ensuring report consistency across all pertinent systems.

The contractor shall produce a Scenario Assessment Report (SAR). The report is an “end of day” email to the COR, Alternate COR, Chief, Systems Integration, Testing and Production, and Test Manager assessing test scenarios and truth data collection against the GCSS-J requirements met by the imminent release. The report shall document in detail issues where the scenario is not consistent with current GCSS-J requirements. If the scenarios created are consistent with the GCSS-J requirements for the release, a simple statement documenting such is sufficient. The email shall have the title SAR for GCSS-J Release x.x as of date.

On GCSS-J software upgrades the contractor shall provide regression testing of all GCSS-J reports, widgets and capabilities impacted. The result will be documented in a query/widget status matrix.

The contractor shall document defects found during test events in the GCSS-J defect tracking system.

Subtask 4 Deliverables:

Scenario Assessment Report

Test results input to the Data Engineering Team Process Tool

Integration test results input to the Data Engineering Team Process Tool

Query Review Technical Report

All activities conducted under this subtask shall be reported in the bi-weekly status report. All activities performed in support of this subtask shall be reported against the GCSS-J WBS.

6.2.7 Subtask 5 – Meetings and Briefings (B008) The contractor shall also attend selected meetings to act as the technical advisor at such meetings. Contractor shall prepare presentation materials to support on-going demonstrations of any of the objectives of this PWS as they evolve (i.e., deliverables, agenda, briefing materials, and after action report).

Subtask 5 Deliverable:

Presentation materials

All activities conducted under this subtask shall be reported in the bi-weekly status report. All activities performed in support of this subtask shall be reported against the GCSS-J WBS.

6.2.8 Subtask 6 – Requirements Analysis (B009)

GCSS-J requirements are analyzed, evaluated and prioritized under the direction of the GCSS-J Functional Requirements Working Group (FRWG). In accordance with the agile process, requirements management tool (currently Rally). The FRWG is minimally comprised of Capability Managers, (CM), Joint Staff , users, select PMO staff, and GCSS-J contract staff from this PWS and select contract staff from other GCSS-J development or integrating contracts as identified by the GCSS-J PMO. The contractor shall provide input and support to the FRWG. The GCSS-J PMO will conduct a requirements review for each sprint and release via the FRWG. The output of this review shall be used to provide enough information for the capability Development Contractor (DC)(under a different GCSS-J contract) to produce the technical requirements needed to develop the requested capability. The contractor shall participate in requirement reviews for each sprint with the PMO and Joint Staff to prioritize the list of requirements allocated for each sprint. The contractor shall interface with the customer, users and developers to ensure requirements are understood, well documented and data sources exist of good quality (able to provide result sets which are minimally but not limited to correct, complete and timely). The contractor shall analyze the requirements to ensure requirements are clearly stated (implementable using the data from the intended source and clearly written for implementation by the DC). The contractor shall write user stories and acceptance criteria in support of requirements and the contractor shall provide support and input to the CM to ensure all User Stories are well formed containing an appropriate title, good functional description, and complete acceptance criteria. Upon request, the contractor shall produce a Requirements Analysis Report (RAR) (A0026), which documents data source availability and capability to support the requested functionality. The contractor shall provide data source expertise to DC(s) to support capability design and subsequent development of user stories/requirements. The contractor shall support the CM to produce a Requirements Clarification when the requirement is unclear as written. The contractor shall participate in the GCSS-J Log COP working group, providing data source expertise and FRWG support during design presentations of up-coming GCSS-J capability /functionality to ensure user requirements are met. GCSS-J is one of a Family of Systems, responsible for providing the logistics capabilities documented in the Combatant Command (CC) 129 requirements. The contractor shall relate each GCSS-J requirement/User Story to a CC129 requirement. GCSS-J tracks the status of our completion of the CC129 requirements, currently in the form of a spreadsheet, which will be provided as GFI. The contractor shall update the CC129 completion status with each GCSS-J release/patch/widget. Within two months of contract award, the contractor shall evaluate the current tracking mechanism and propose an alternative tracking mechanism, process improvements and artifact improvements to easily track CC129 and the CC129 completion status. The contractor shall support the PMO in ensuring JS/J4 remains abreast of GCSS-J CC129 completion status. The contractor shall also identify the appropriate Measure of Performance (MOP) and Measure of Effectiveness (MOE) assigned to each User Story / Requirement (currently documented in the requirements tracking tool). The contractor shall document CC129 analysis status support, CM support and all communications with customers in the Bi-weekly Status Report.

Subtask 6 Deliverables:

Requirements Analysis Report

Requirements Clarification Request

CC129 Tracking Process Improvement Analysis

Input to GCSS-J Requirements Tracking Tool

All activities conducted under this subtask shall be reported in the bi-weekly status report. All activities performed in support of this subtask shall be reported against the GCSS-J WBS.

6.2.9 Subtask – 7 GCSS-J Help Desk and User Support (B011)

The contractor shall provide Subject Matter Experts (SMEs), who are available to support the GCSS-J Help Desk and the GCSS-J users. The contractor shall provide assistance when a problem or question arises on GCSS-J functionality or data clarification. Questions and further clarification on GCSS-J functionality may also arise as a result of demonstrations and exercises. The contractor shall provide data clarification and functionality support to users and prospective users. The GCSS-J PMO will contact the appropriate contractor SME for help desk/user support. The contractor-SME shall acknowledge receipt of request to the requestor and COR within 30 minutes of the work day. The contractor shall provide periodic status of the issue to the PMO throughout the day and provide an end of day status report until the issue is resolved. The contractor shall provide a detailed description of the support provided in the bi-weekly report. User support shall be provided as a result of systems engineering, Help Desk calls or CM support.

Subtask 7 Deliverable:

User Support Report

All activities conducted under this subtask shall be reported in the bi-weekly status report. All activities performed in support of this subtask shall be reported against the GCSS-J WBS.

6.2.10 Subtask – 8 GCSS-J JOPES Interface and Readiness Support (B013)

The contractor shall provide Global Command and Control Systems – Joint GCCS-J JOPES expertise GCCS-J and joint Interoperability and Test Command (JITC) lab personnel are responsible for JOPES server systems administration and systems maintenance. The contractor shall ensure that JOPES data is current and pertinent for each phase of the GCSS-J development lifecycle. As needed, the contractor shall download data for inclusion on the GCSS-J JOPES test server. The contractor shall communicate with GCSS-J JOPES users to ensure JOPES accounts are created and maintained, they are familiar with changes in the JOPES environment and are abreast of the latest JOPES Program requirements. The contractor shall interface with the JOPES program development staff participating in configuration control boards, attending user group meetings, knowledgeable of changes as a result of JOPES modernization and support GCSS-J in maintaining Interface Control Documents. The contractor shall provide JOPES SMEs to other GCSS-J developers. Maintenance shall include but not be limited to identifying test Plan IDs (PIDS) to support functionality, downloading test plans to the test environment, ability to obtain summary knowledge of PID content The contractor shall provide readiness expertise, understanding the differences between GSORTS and the Defense Readiness Reporting System (DRRS). The contractor shall provide knowledge of DRRS application, web services and summary content.

All activities conducted under this subtask shall be reported in the bi-weekly status report. All activities performed in support of this subtask shall be reported against the GCSS-J WBS.

Subtask 8 Deliverables:

Test results input to the Data Engineering Team Process Tool

6.3 Task 3 – Functional Support Tasks

6.3.1- Global Combat Support System - Joint (GCSS-J) Functional Proponent Support (C001)

The JSJ4 is the functional proponent for the Joint Requirements Oversight Council approved Global Combat Support System -Joint (GCSS-J) and also responsible for promoting the development and implementation of logistics information systems and technologies of the future to meet the knowledge-based requirements of the Combatant Commands. The contractor shall support the functional sponsor by serving as the SME and possessing an intimate knowledge of all Joint Capability Areas. To support the functional sponsor, the contractor must have a Top Secret clearance and the duty station will primarily be located at the Pentagon. If the place of duty changes to Ft Meade, the contractor will be notified 30 days in advance.

The capability areas include:

· Deployment and Distribution

· Supply

· Combatant Command Logistics Common Operational Picture (COCOM) (LOGCOP)

· Logistics Services

· Interagency Coordination (NIPRNET)

· Adaptive Logistics Network

· Maintain

· Operational Contract Support

· Base and Installations Support

· Engineering

· Security Assistance

· Homeland Defense

Anticipate two (2) of the JCAs would be the focus for release development per contract year.

6.3.1 - Subtask 1 GCSS-J Program Oversight (C002)

The contractor shall provide administrative, planning, and functional expertise for working groups supporting the GCSS-J management structure documented in CJCSI 6723.01B. Specifically, the contractor shall organize, recommend agendas and discussion topics, attend and document the results of the GCSS-J management working groups.

Subtask 1 Deliverables:

Meeting Agendas

Meeting Minutes

6.3.2 - Subtask 2 GCSS-J Requirements Collection, Validation and Prioritization (C003)

The contractor shall support the functional sponsor’s requirement in the collection, review, validation, and prioritization of combat support and combat service support information requirements for the GCSS-J. The contractor shall recommend methodologies, processes and procedures for collecting, validating and prioritizing these requirements. Specifically, the contractor shall recommend a new requirements request process that enables customers to submit new requirements and allows the Government to identify and track discrepancies. The contractor shall recommend a configuration management process that will ensure alignment of information requirements, supporting data elements, data sources and GCSS-J functional modules in a manner that enables traceability throughout. The contractor shall organize, attend, and in some cases, facilitate and document the results of requirements identification workshops, working groups, and planning and configuration management and control boards to facilitate the review, validation and prioritization of these requirements. The contractor shall make recommendations to the Government on the actual priority of these requirements. The contractor shall maintain, revise and consolidate these requirements within the appropriate GCSS-J Joint Capabilities Integration Development System (JCIDS) - required functional requirements documents.

Subtask 2 Deliverables:

Requirements Request Process

Configuration Management Process

Minutes for meetings, workshops, working groups, and control boards

6.3.3 - Subtask 3 GCSS-J Data Analysis and Assessment (C004)

The contractor shall assess the availability of logistics data to support the requirements identified in Subtask 4.4.1.2. The contractor shall recommend to the Government authoritative data sources for that data and identify gaps where that data is not currently available within the logistics community. The contractor shall organize, attend and, in some cases, facilitate and document the results of workshops, working groups, and meetings designed to define data requirements, authoritative data sources and data sharing procedures and policies.

Subtask 3 Deliverables:

Minutes for meetings, workshops, working groups, and control boards

6.3.4 - Subtask 4 GCSS-J External Training, Marketing, and Briefing Support (C005) The contractor shall provide recurring external GCSS-J training, marketing and briefing support to venues such the Joint Course on Logistics (JCL).

Subtask 4 Deliverables:

Training sessions

Demonstrations

6.3.5 - Subtask 5 Bi-Monthly In Process Reviews (IPRs) (C006)

The contractor is required to participate in Quarterly IPRs where they will provide a high level summary briefing. The IPR shall cover the following:

(1) Contract Summary- identify Contractor Team Lead; COR/ACOR; and specific contract information (e.g., contract vehicle, contract number, total dollar amount of effort, total dollars expended (as of the end of the reporting period), current month expenditures, average monthly burn rate, number of full time equivalents, period of performance, contract type and which WBS numbers the contractor is supporting;

(2) Reporting Structure- identify baseline dollars associated by Task and WBS and any baseline changes.

(3) Update/identify specific efforts worked on during the reporting period.

(4) Issues.

(5) Contractor Burn Rate- display budget, actual expenditures and estimate to complete data in a graph format.

Subtask 5 Deliverable:

Bi-Monthly IPR presentation materials

7. Performance Standard.

8. Incentives. Both positive and negative performance will be documented in past performance reports/databases, Contractor Performance Assessment Reporting System (CPARS), as appropriate and will be taken into consideration for follow-on work.

9. Place of Performance.

The primary place of performance will be 6910 Cooper Ave, Ft Meade, MD. Space will be provided at Ft Meade, as requested, for up to three individuals that will be provided with laptops, internet connectivity, desk, and phone. However, space is contingent upon overall GCSS-J PMO availability of space and approved space waivers. Telework may be optional pending approval of the Government COR.

Local travel from the primary place of performance to other facilities within the National Capital Region (NCR) will be required on a regular basis for data gathering, meetings, testing, etc. Local travel from the primary place of performance to the GCSS-J Integrator site, currently located at 2340 Dulles Corner Blvd, Dulles, VA, will be required to support Functional Requirement Working Groups (FRWG) and text events. The address of the integrator is subject to change, especially considering the re-compete of the integration contract. All travel will be conducted in accordance with FAR 31.205-46, Travel Costs. Only travel specifically authorized in advance and in writing by the COR will be reimbursed under this contract. To the extent that reimbursement of Contractor travel, lodging, meals and incidental expenses are specifically authorized, such reimbursements shall be limited to rates or amounts considered reasonable and allowable as defined in FAR 31.205-46. Contractor travel is anticipated to support the requirements named in this Performance Work Statement. Travel projections are two (2) trips for one (1) personnel within the CONUS and OCONUS to various locations per year.

Alternate Place of Performance - Contingency Only. Contractor employees may be required to work at home, another approved activity within the local travel area or at the contractor's facility in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, etc.). Any equipment such as laptops or phones provided to Contractor personnel shall be returned at the termination of the engagement or at another time mutually agreeable to both parties. COR approval is required. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. To the extent possible, the contractor shall use best efforts to provide the same level of support as stated in the PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer or the contractor may request an equitable adjustment.

10. Period of Performance. The period of performance is a 1-year base with four (4) 1-year option periods beginning on:

· (Base) 25 April 2014 through 24 April 2015.

· (Option Year 1) will be 25 April 2015 through 24 April 2016.

· (Option Year 2) will be 25 April 2016 through 24 April 2017.

· (Option Year 3) will be 25 April 2017 through 24 April 2018.

· (Option Year 4) will be 25 April 2018 through 24 April 2019.

As directed by the COR, the contractor shall continue performance in emergency or mission essential conditions. Additionally, the contractor may be required to account for the whereabouts of their personnel should this information be requested by the COR.

11. Delivery Schedule

Final – 30 days after contract award

Final – 30 days after contract award

30 days after contract award