DJFAS_PWS.pdf

TEC Services Contract Page 1 of 18 Pages Sample Task Order 2016-06-02

Joint Interoperability Test Command Defense Joint Finance and Accounting System Test and Evaluation Support

-DJFAS T&E Support-

Statement of Work

Contract Number:

Task Order Number:

Tracking Number:

Follow-on to Previous Contract and Task Order Number:

1. Contracting Officer’s Representative (COR).

1.1. Primary COR.

Name:

Organization:

Department of Defense Activity Address Code (DODAAC):

Address:

Phone Number:

Fax Number:

E-Mail Address:

1.2. Alternate COR.

Name:

Organization:

DODAAC:

Address:

Phone Number:

Fax Number:

E-Mail Address:

2. Contract or Task Order (TO) Title.

Joint Interoperability Test Command (JITC) Defense Joint Finance and Accounting System (DJFAS) Test and Evaluation (T&E) Support.

TEC Services Contract Page 2 of 18 Pages

3. Background.

3.1. DJFAS System Description

The DJFAS is an enterprise resource planning (ERP) system, based on an industry solution and a Commercial Off the Shelf (COTS) set of capabilities, that will consolidate, modernize, and replace many current Department of Defense (DoD) finance and accounting systems to standardize and streamline DoD business processes. DJFAS, accessible by users worldwide via the Non-Secure Internet Protocol (IP) Router Network, will be used by all of the DoD Combatant Commands, Services, and Agencies (CC/S/A). DJFAS, hosted from one or more DISA Defense Enterprise Computing Centers (DECCs), must interoperate with approximately 25 joint, non-joint, legacy, and enterprise-specific systems and is reliant on over 100 mission-critical information exchanges.

3.2. DJFAS Program

The DJFAS Program of record is an Acquisition Category (ACAT) I Business Mission Area (BMA) Title 10 Section 2222 Defense Business System (DBS) under Deputy Assistant Secretary of Defense (DASD) Developmental Test and Evaluation (DT&E), and Director Operational Test and Evaluation (DOT&E) oversight. The DJFAS Program is entering the DoD Acquisition Lifecycle Process at the pre-Milestone B decision-point and exiting the Acquisition Lifecycle Process with a declaration of Full Operational Capability (FOC). The DJFAS Program Management Office (PMO) has requested that the JITC provide a full spectrum of T&E support services to the program, initiating pre-Milestone B through FOC and program sustainment, to include serving as the programs’ designated Operational Test Agency (OTA).

4. Objectives.

4.1. Provide Full-Spectrum Program T&E Support

The primary objective of this task order is for the Contractor to provide the DJFAS Program full-spectrum T&E support to include:

a. Developmental Test and Evaluation (DT&E) support in compliance with U. S. Code Title 10 Section 139b

b. Interoperability certification in compliance with DoD Instruction 8330.01, “Interoperability of Information Technology (IT), Including National Security Systems (NSS)”

c. Cybersecurity T&E support in compliance with DASD (DT&E) memorandum “Guidelines for Cybersecurity DT&E”

d. Operational Test and Evaluation (OT&E) support to determine Operational Effective, Suitable, Interoperable, and Secure (OESIS) in compliance with DOT&E Memoranda “Procedures for Operational Test and Evaluation of Cybersecurity in Acquisition Programs” and “Cyber Economic Vulnerability Assessments (CEVA)”

4.2. Overcome Common T&E Challenges

A secondary objective of this task order is for the Contractor’s technical approach to propose innovative solutions to help JITC alleviate or avoid the following challenges that commonly plague DoD in its T&E of COTS-based business solutions such as DJFAS:

a. Testers not involved early in the acquisition process.

b. Testing is approached as a solely schedule-driven activity.

c. System requirements are often ill defined, untestable, and/or lack associated measurable criteria for evaluation.

TEC Services Contract Page 3 of 18 Pages

d. Test objectives, activities, and data requirements are poorly coordinated amongst responsible test organizations, leading to inefficient test conduct.

e. Test data sets are not operationally representative, in either size or range of content.

f. Test environments are not operationally representative.

g. Test configurations are poorly documented and controlled for and often fail to incorporate required operational security controls and configuration settings.

h. Functional matter experts and user representatives given limited role in the test process.

i. Test Readiness Reviews with formal test entrance criteria are not conducted in a consistent and disciplined manner.

j. Testers fail to adopt T&E ‘best practices’ or to apply lessons learned from the testing of similar systems and technologies.

k. Testing relies on manual methods to stimulate the system under test, measure performance, and collect and analyze resulting data. Such methods are inefficient, labor intensive, error prone, and difficult to repeat.

l. Testers are reluctant to adopt Science Based Test Design (SBTD) methods to improve T&E efficiency and rigor.

m. Analysis is superficial, lacks emphasis on determining mission impact, and fails to quantify statistical uncertainty.

n. Test concepts and plans are not coordinated with DOT&E sufficiently in advance of testing. Testers are often not aware of DOT&E concerns until late in the testing process.

o. Verification of cybersecurity protection measures performed late in the T&E process.

5. Scope.

5.1. Program T&E Support

The Contractor shall submit a proposal describing their technical approach for overall T&E support of the DJFAS Program. The Contractor’s approach should offer solutions to the common T&E challenges cited in SOW paragraph

4.2 above. The Contractor’s approach shall address the critical path for developing and delivering test documentation, T&E event scheduling, proposed duration of T&E events, T&E event entrance and exit criteria, and preparation and delivery of required DASD(DT&E) and DOT&E briefing and deliverable, per the notional event-driven acquisition process and schedule dependencies presented in this SOW. For planning purposes, the program documentation called for in the DJFAS Acquisition Decision Memorandum (ADM) is, per DoDI 5000.02 Table 2, for the following program life-cycle events:

a. Capability Design Document (CDD) Validation

b. Development Request for Proposal (RFP) Release

c. Milestone B

d. Limited Deployment (LD)

e. Full Deployment (FD)

In providing overall DJFAS T&E support, the Contractor shall work closely with the DJFAS PMO, through various Working Integrated Product (WIPT) monthly meetings, to help prepare the program’s CDD to support the DJFAS CDD Validation Decision Point prior to the DJFAS Request for Proposal (RFP) Release Decision Point. The Contractor shall also support decomposition of the high-level requirements identified in the DJFAS CDD into the

TEC Services Contract Page 4 of 18 Pages requirements (e.g., technical, functional, performance, and cybersecurity) stated in the DJFAS RFP. At the DJFAS PMO’s request, the Contractor shall provide T&E input quarterly program In-process Reviews (IPRs) with the DJFAS Program Acquisition Executive (PAE) and Milestone Decision Authority (MDA). The Contractor shall also support other ancillary program T&E requirements such as helping to develop program documents such as a Test and Evaluation Master Plan (TEMP), as discussed in the SOW Performance Requirements section below.

5.2. Task Support Time Frames

As DJFAS is under DOT&E oversight, JITC is required to provide for each operational test event a Test Concept Briefing no later than (NLT) 180 days before the start of the event and the signed plan NLT 60 days before the start of the event. The results of an Early Operational Assessment (EOA) event typically support a Milestone B decision;

take place at a single physical location; and generally last 1 week/5 days. The results of an Operational Assessment (OA) event typically support the Limited Deployment decision/readiness for Initial Operational Test and Evaluation (IOT&E); take place at a single physical location; and generally last 2 weeks/10 days. The results of an IOT&E event typically support the Full Deployment decision; take place at 2 physical locations; and generally last 4 weeks/20 days. The results of a Follow-on Operational Test and Evaluation (FOT&E) event typically support the program’s entry into sustainment; take place at a single physical location; and generally last 2 weeks/10 days. The general periods in which support of the individual SOW tasks are required, relative to the task order base and option years, are as identified in the Part 9, the Period of Performance section of this SOW.

5.2.1. Base Year Support

In the Base Period for this Task Order, the Contractor shall provide DJFAS T&E support to address CDD Validation Decision Point and RFP Release Decision Point life-cycle events as well as those activities leading up to Milestone B such as contract award.

5.2.2. Option Year 1 (OY1) Support

In the first option year of support, OY1, the Contractor shall provide DJFAS T&E support to address the, contractor integration testing, EOA, and DASD (DT&E) steps 1 & 2.

5.2.3. Option Year 2 (OY2) Support

In the second option year of support, OY2, the Contractor shall provide DJFAS T&E support to address the Milestone B Decision Point and the Limited Deployment Decision Point life-cycle events as well as those activities supporting those decision points and leading to the Full Deployment Decision Point such as SIT, SQT, SAT, OA, DASD(DT&E) steps 3 & 4, DOT&E Phases 1 & 2, IOT&E Interoperability Certification, ATO, and Financial Standards Assessment.

5.2.4. Option Year 3 (OY3) Support

In the third option year of support, OY3, the Contractor shall provide DJFAS T&E support to address the Full Deployment Decision Point, the FOT&E event and sustainment of DJFAS.

5.2.5. Option Year 4 (OY4) Support

Per the DJFAS program acquisition schedule, there is not an anticipated need for the Contractor to provide DJFAS T&E support in what would be the fourth option year of support, OY4.

6. Specific Tasks.

In providing the DJFAS Program full-spectrum T&E support from pre-Milestone B on through to a Full Deployment decision, the Contractor shall perform the activities associated with the six T&E tasks areas identified in this section of the SOW. The Contractor’s proposed approach for providing this support shall address, where possible, solutions for overcoming the common T&E challenges cited in section 4.2 of this SOW. Contractor activities conducted in support of the six task areas, and their associated subtasks, need in many cases occur concurrently of one another, performed in the approximate contractual task order timeframes noted for each task area. The six task areas that the Contractor shall provide support to are as follows:

TEC Services Contract Page 5 of 18 Pages

6.1. Task 1: General Program T&E Support (Approximate Periods of Support: Base, OY1, OY2, OY3)

The Contract shall provide the DJFAS Program the following general T&E support:

6.1.1. Subtask 1.1: Meeting/Trip Support

The Contractor shall provide general support by attending and participating in teleconferences, working groups, WIPTs, and IPRs. It is anticipated that WIPTs will be held monthly lasting for 3 days, IPRs will occur quarterly for 1 day, and other meetings/teleconferences will be scheduled weekly with all occurring in less than 8 hours.

Deliverables:

a. Meeting minutes

b. Trip reports

6.1.2. Subtask 1.2: Documentation Review

The Contractor shall provide input to, and informal and formal review of, program documentation. The Contractor shall support the DJFAS PMO in the review of program documentation for concurrence, approval, and/or signature.

Number and types of programmatic documentation are displayed by life-cycle event in DoDI 5000.02, Enclosure 1, Table 2.

Deliverables:

a. Input to program documentation

b. Informal review and comment on program documentation

c. Formal review and comment on program documentation

d. Review of documentation for concurrence, approval and/or signature

6.1.3. Subtask 1.3: Other General Support

The Contractor shall develop and maintain an Integrated Master Schedule (IMS) to track DJFAS Program activities against the Defense Acquisition System; align requisite program documentation to acquisition decision points and phase; and track events, test windows, deliverables and swim lanes. The Contractor shall provide a Weekly Activity Report (WAR) that documents task activities performed, planned/scheduled task activities and deliverables, travel performed as part of task support, and any outstanding problems, issues, or action items.

Deliverables:

a. Integrated Management Schedule

b. Weekly Activity Reports

6.2. Task 2: Developmental Test and Evaluation (DT&E) Support

The Contract shall provide the DJFAS Program the following DT&E support:

6.2.1. Subtask 2.1: Initial DT&E Support (Approximate Periods of Support: OY1, OY2)

The Contract shall provide pre-planning; planning; execution; and data reduction and reporting activities for each Contractor Integration Test (CIT), System Integration Test (SIT), System Qualification Test (SQT), System Acceptance Test (SAT) event conducted by JITC in support of the DJFAS Program. The Contractor shall develop a Requirements Traceability Matrix (RTM) using program documents such as the DJAS RFP, Capabilities Development Document (CDD), Systems Engineering Plan (SEP), Cybersecurity Strategy (CS). The Contractor shall maintain and update the RTM as approved changes occur. The Contractor shall provide input to the DT&E Overview section of the DJFAS TEMP.

TEC Services Contract Page 6 of 18 Pages

Deliverables:

a. Requirements Traceability Matrix

b. Test and Evaluation Master Plan (TEMP) DT&E overview input

6.2.2. Subtask 2.2: DT&E Pre-Planning Support

The Contractor shall leverage existing DJFAS program documentation in developing a T&E Strategy for each event.

Requirements identified for test shall be directly traceable to DJFAS program documentation with primary and secondary data sources clearly delineated. The test concept for each event shall consider the best practice of SBTD.

The Contractor shall identify specific Test Readiness Review (TRR) Checklist entrance criteria that must be satisfied before proceeding with JITC-conducted test events.

Deliverables:

a. Test and Evaluation Strategy Briefing

b. Test Concept Briefing

c. Test Readiness Review (TRR) Checklist

6.2.3. Subtask 2.3: DT&E Planning Support

In support of DT&E planning, the Contractor shall develop:

a. TRR Briefings using TRR Checklists.

b. Test Plans that presents the DT&E test event objectives, scope, methods, and activities.

c. SBTD approaches to ensure rigor and efficiency in addressing DT&E test event objectives.

d. Detailed test procedures for CIT events that exercise all mandatory, optional, conditional-mandatory, conditional-optional, and negative threads.

e. Detailed test procedures for SIT events that exercise all interface, data characteristics, transactions, security controls, performance requirements, and response times.

f. Detailed test procedures for SQT events that exercise all functions, roles and responsibilities, and business practices.

g. Detailed test procedures for SAT events that exercise all critical technical parameters (CTPs).

h. Data collection forms, surveys, questionnaires, defect reports, and associated processes to support test event data collection.

i. Data management plans that specify methods for data security/access control of test data, data quality and remediation procedures, regression scheduling, data analysis, data reduction, and data reporting procedures.

j. Daily Hot Wash briefing template for tracking and reporting test event status to include number of planned procedures completed/yet to be completed, number of failed procedures, number of procedures to be retested, and number of defects identified and their preliminary scores.

k. Daily Data Authentication Group (DAG) procedures for adjudicating newly identified defects with preliminary score and statuses of previously identified defects, as well as the procedures for voting on the final scores for each defect.

Deliverables:

TEC Services Contract Page 7 of 18 Pages

a. Completed TRR Checklist

b. TRR Briefing

c. Test Plan

d. Detailed Test Procedures

e. Data Collection Plan

f. Data Management Plan

g. DAG Procedures

h. Daily Hot Wash Briefing Template

6.2.4. Subtask 2.4: DT&E Execution Support

The Contract shall carry out DT&E per approved test plans. Over the course of DT&E execution, the Contractor shall prepare a Daily Hot Wash Briefing and a Daily DAG Briefing to keep stakeholders informed of test event progress. The Contractor shall collect data IAW test plan, data collection plan, and data management plan.

Deliverables:

a. Daily Hot Wash Briefings

b. Daily DAG Briefings

6.2.5. Subtask 2.5: DT&E Data Reduction and Reporting Support

The Contractor shall develop test report that identifies tested requirements, the status of each tested requirement, all identified defects, any remediation activities including regression, and summarizes the overall results of the test event. The Contractor shall develop an emerging results briefing that identifies applicable requirements satisfactorily demonstrated, requirements demonstration that resulted in notice of findings, and all identified defects with associated scoring.

Deliverables:

a. Test Report

b. Emerging Results Briefing/Quick Look

6.3. Task 3: Financial Standards Compliance Validation Support (Approximate Periods of Support: OY2)

The Contractor shall provide support to the DJFAS Program in pre-planning; planning; execution; and data reduction and reporting of required program finance standards compliance validation activities. Finance standards include but are not limited to Federal Information System Controls Audit Manual (FISCAM), Standard Financial Information Structure (SFIS), Standard Line of Accounting (SLOA), Federal Financial Management Improvement Act (FFMIA), Statement on Standards for Attestation Engagements Number 16 (SSAE 16), and Financial Improvement Audit Readiness (FIAR). In providing this support, the Contractor shall:

a. Develop an approach for performing financial standards compliance validation

b. Create concept briefings for each finance standard validation event suitable for DJFAS PMO, JITC management, and Milestone Decision Authority (MDA) consumption.

c. Prepare a Compliance Validation Plan for each finance standard validation event that presents the event’s objective, scope, methodology, and activities.

d. Write Detailed procedures for each finance standard validation event.

TEC Services Contract Page 8 of 18 Pages

e. Carry out financial standards compliance validation per approved procedures

f. Prepare an emerging results briefing following the completion of each finance standard validation event that identifies applicable requirements satisfactorily demonstrated, requirements demonstration that resulted in notice of findings, and all identified defects with associated scoring.

g. Develop a Compliance Validation Report following the validation of each finance standard.

Deliverables:

a. Concept Brief

b. Detailed Procedures

c. Compliance Validation Plan

d. Emerging Results Briefing

e. Compliance Validation Report

6.4. Task 4: Interoperability (IOP) Certification Support (Approximate Periods of Support: OY2)

The Contract shall provide the DJFAS Program the following IOP certification support:

6.4.1. Subtask 4.1: General IOP Certification Support

The Contractor shall provide personnel that are knowledgeable and familiar with DoD, Joint Chiefs of Staff (JCS), DoD Chief Information Office (DoD CIO), DoDI 8330.01 compliance, and JITC policies and instructions in regards to interoperability certifications and assessments as they apply to the DoD Information Technology (IT) Business Mission Area/Defense Business Systems (BMA/DBS). The Contractor shall aid JITC in the review and approval process for the DJFAS Information Support Plan (ISP) at Milestone B, the DJFAS ISP of record for the Limited Deployment decision, and the updated DJFAS ISP of record for the Full Deployment decision leading to sustainment.

6.4.2. Subtask 4.2: IOP Certification Pre-Planning Support (Approximate Periods of Support: OY2)

The Contractor's technical approach shall describe how they will assist the DJFAS PMO in updating of the DJFAS Requirements Traceability Matrix (RTM) and program Integrated Master Schedule (IMS) identified in the associated DJFAS test strategy plan(s)and documentation for each system capability/software release under test.

The Contractor shall leverage existing DJFAS program documentation to determine appropriate hardware and software configurations to ensure correct requirements baselines are used for linking results of each DJFAS software release to the IOP test observation effort. The Contractor's technical approach shall describe how they will conduct validation of configuration management procedures and processes. As IOP test observation efforts are performed, the Contractor shall provide summaries of test observation progress, document test observation results, and provide recommendations for enhancing the DJFAS operations, as requested by the DJFAS PMO or the JITC task Contracting Officer Representative (COR) / Action Officer (AO). The Contractor's technical approach shall describe how incidents and suggestions for enhancements will be documented by the contractor using the DJFAS PMO appropriate problem report automated test tool and forms.

Deliverable: Requirements Traceability Matrix

6.4.3. Subtask 4.3: IOP Certification Planning Support

The Contractor shall develop a technical approach for supporting the JITC IOP assessments, IOP evaluations, and the Net Ready Key Performance Parameters (NR KPP) compliance process. The Contractor’s technical approach shall address IOP test observation processes, DoD Architecture Framework (DoDAF) architecture validation processes, NR KPP attributes validation processes in coordination with the Joint Chiefs of Staff (JCS) and OTA support, and IOP data collection and analysis processes. The Contractor's technical approach shall also describe how they will assist in updating the DJFAS IOP test scenarios, cases, and scripts, as requested to ensure the

TEC Services Contract Page 9 of 18 Pages adequacy and testability of Measures Of Effectiveness (MOEs), Measures Of Performance (MOPs), Measures Of Suitability (MOSs), Key Performance Parameters (KPPs), Key System Attributes (KSAs), and proposed Reports, Interfaces, Conversions, Enhancements/Extensions, and Workflows (RICEW) objects for DJFAS processes and capabilities as they apply to IOP test observation efforts.

Deliverable: Interoperability Certification Evaluation Plan (ICEP)

6.4.4. Subtask 4.4: IOP Certification Execution

The Contractor’s technical approach shall describe how they will provide required IOP test observation results and provide documentation and or matrices that will adequately address deficiencies/non-deficiencies and provide recommendations for enhancing the program business core processes and capabilities in support of the DJFAS project interoperability initiatives and objectives. The Contractor's technical approach shall describe how they will conduct validation of each IOP Requirement (IR) related fix included in the DJFAS patch releases. Release-specific IRs will be identified in the DJFAS software release documentation.

Deliverable: Quick Look Report

6.4.5. Subtask 4.5: IOP Certification Data Reduction and Reporting Support

The Contractor's technical approach shall describe how they will provide adequate JITC test observation methodology and data collection processes that will support the DoD Chief Management Officer (DCMO)/Business Capability Lifecycle (BCL) acquisition strategies as they apply to DBS acquisition strategy and mandates. The Contractor's technical approach shall describe how to provide analysis and validation for the program MOEs, MOPs, MOSs, KPPs, KSAs, and proposed RICEW objects, validation to the NR KPP compliance artifacts, and the overall JITC interoperability certification decision processes for the DJFAS Program for each capability/software release.

Deliverable: Certification Report

6.5. Task 5: DASD(DT&E) Cybersecurity Compliance Support (Approximate Periods of Support: OY2)

The Contractor shall aid the DJFAS PMO and JITC in complying with DASD(DT&E) by:

a. Identifying DT&E Cybersecurity requirements through review of program documentation.

b. Developing an executable DT&E Cybersecurity strategy for input to the DJFAS Milestone B TEMP and the DJFAS Limited Deployment TEMP.

c. Supporting Blue Team vulnerability assessments.

d. Analyzing the attack surface for incorporation into the Security Assessment Plan in support of the Assessment and Authorization process (formerly Certification and Accreditation) that informs the Authorizing Official (AO) in approving an Interim Authorization to Test (IATT) and/or an Authorization to Operate (ATO).

e. Providing input to the DJFAS Security Plan.

Deliverables:

a. Security Assessment Plan

b. Security Plan input

6.6. Task 6: Operational Test and Evaluation (OT&E) Support (Approximate Periods of Support: OY1, OY2, OY3)

The Contract shall provide the DJFAS Program the following OT&E support in accordance with the JITC OT&E Guidebook and DOT&E guidance:

TEC Services Contract Page 10 of 18 Pages

6.6.1. Subtask 6.1: General OT&E Support

The Contractor shall provide OT&E services in support of determining the extent to which DJFAS is Operational Effective, Suitable, Interoperable, and Secure (OESIS). The Contractor shall provide pre-planning; planning;

execution; and data reduction and reporting activities for Early Operational Assessment (EOA) occurring pre- Milestone B, OAs occurring post-Milestone B, IOT&E occurring post-limited deployment and FOT&E occurring post-Full Deployment operational events conducted by JITC in support of the DJFAS Program. The Contractor shall provide input to the OT&E Overview section and Cybersecurity areas of the DJFAS TEMP.

Deliverable: TEMP OT&E overview input

6.6.2. Subtask 6.2: OT&E Pre-Planning Support

In support of OT&E pre-planning, the Contractor shall:

a. Prepare a Risk Assessment (RA) for each operational event IAW the DOT&E memorandum subject “Guidelines for Operational Test and Evaluation of Information and Business Systems.”

b. Develop an Analysis Structure comprised of an Evaluation Framework and a supporting DSM. The Evaluation Framework, composed of Critical Operational Issues (COIs), MOEs, MOSs, and MOPs defines the scope of evaluation. The DSM identifies the sources and quantities of test data required to support each test measure; data collection methods, analysis methods, responsible party for the data, test conditions, and any test limitations.

c. Apply SBTD approaches to ensure rigor and efficiency in addressing OT&E test event objectives.

d. Develop a Test Concept Briefing for each OT&E event.

e. Develop a TRR Checklist that identifies entrance criteria that must be satisfied before proceeding into an OT&E event.

Deliverables:

a. Risk Assessment (RA)

b. Analysis Structure: Evaluation Framework with supporting Data Source Matrix

c. Test Concept Briefing

d. TRR Checklist

6.6.3. Subtask 6.3: OT&E Planning Support

In support of planning for each OT&E events, the Contractor shall:

a. Develop a Test Plan that presents the test event objectives, scope, limitations methodology, analysis structure, and data management and DAG procedures.

b. Prepare a TRR briefing, based on the completed TRR checklist, suitable for presentation to the MDA.

c. Create a daily hot wash briefing template to report test execution status.

d. Address OT&E cybersecurity assessment requirements reflected in DOT&E memorandums, “Cyber Economic Vulnerability Assessments (CEVA),” January 2015, and “Procedures for Operational Test and Evaluation of Cybersecurity in Acquisition Programs,” August 2014 (See:

http://www.dote.osd.mil/guidance.html)

Deliverables:

a. Completed TRR Checklist http://www.dote.osd.mil/guidance.html

TEC Services Contract Page 11 of 18 Pages

b. TRR Briefing

c. Test Plan

d. Daily Hot Wash Briefing Template

6.6.4. Subtask 6.4: OT&E Execution Support

The Contractor shall collect data IAW the test plan. The Contractor shall provide daily hot wash and DAG briefings to keep the DJFAS stakeholders and the testing community informed.

Deliverables:

a. Daily Hot Wash Briefing

b. Daily Data Authentication Group (DAG) Briefing

6.6.5. Subtask 6.5: OT&E Data Reduction and Reporting Support

The Contractor shall develop an emerging results briefing that identifies the status of each measure in the evaluation framework, and all identified defects with associated scoring that could affect the resolution of a COI with associated impact. The Contractor shall develop test report that identifies status of each measure in the evaluation framework, all defects with associated scoring, any remediation activities including regression, and summarizes the overall results of the test event leading to an OESIS determination for an IOT&E or FOT&E event.

Deliverables:

a. Emerging Results Briefing

b. Test Report

7. Performance Standards.

Performance Areas Acceptable Quality Level (AQL) Method of Surveillance Applicable to all deliverables associated with this SOW

Final deliverables shall not exceed, on average, more than one error per page over the entire page count of the deliverable.

The Contractor shall correct all errors associated with a final deliverable within five (5) business days of being notified of such errors

100% inspection of deliverables.

CORs will perform monthly inspection of contract deliverables and document results in CORT Tool.

Note: A “Final Deliverable” is defined as a product for which all government comments to prior draft or interim versions of the deliverable have been satisfactorily addressed by the contractor such that the content, form, and format of the product on delivery to the government is sufficiently accurate, complete, technically sound, and free from spelling, punctuation, syntax, and grammatical errors that it is ready for final government review, staffing, acceptance, and signature.

8. Place of Performance.

8.1. Primary Work Locations

The primary work location will be at JITC Fort. Huachuca, Arizona.

8.2. Travel:

Frequent trips from the JITC Fort Huachuca, Arizona, work location to the National Capital Region (NCR) for meetings with the DJFAS PMO, DOT&E, and other stakeholders will be required in support of this SOW. Travel

TEC Services Contract Page 12 of 18 Pages arrangements must be coordinated via email with the Government COR, such as lodging, rental cars, air travel, etc., prior to final travel arrangements to confirm trip is still necessary. Combatant Command (COCOM) visit requests should also be coordinated with the Government COR. The Contractor shall initiate Visit Access Requests for travel to sites requiring verification of security clearance. As specific dates, destinations, and duration of travel are unknown, for purposes of preparing their proposal the Contractor is to use the “plug number” of $50,000.00 as the annual travel expense for providing support for both the base and each of the option years of task order support.

8.3. Alternate Place of Performance – Contingency Only.

As determined by the COR, contractor employees may be required to work at an alternate place of performance (e.g., home, the contractor's facility, or another approved activity within the local travel area) in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, government closure due to inclement weather, etc.). Non-emergency/non-essential contractors should not report to a closed government facility. 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 SOW.

9. Period of Performance.

9.1. General Task Order Period of Performance

a. Base: November 1, 2017 – 31 October 2018

b. Option Year 1: November 1, 2018 – 31 October 2019

c. Option Year 2: November 1, 2019 – 31 October 2020

d. Option Year 3: November 1, 2020 – 31 October 2021

e. Option Year 4: November 1, 2021 – 31 October 2022 (Not anticipated as being required for this task order)

9.2. Approximate Periods for Support of Particular Task Order Task Areas

The following table presents the approximate contractual timeframes in which task order support of the individual task areas is to be provided:

Task General Periods of Support

1. General Program T&E Support Base, Option Year (OY) 1, OY2, OY3

2. Developmental Test and Evaluation (DT&E) Support OY1, OY2

3. Financial Standards Compliance Validation Support OY2

4. Interoperability (IOP) Certification Support OY2

5. DASD(DT&E) Cybersecurity Compliance Support OY2

6. Operational Test and Evaluation (OT&E) Support OY1, OY2, OY3

10. Delivery Schedule.

SOW

Task# Deliverable Title Format Due Date Distribution /

Copies Frequency and Remarks

6.1.1 Meeting minutes MS Word

Format

Within 2 working days of meeting completion

Email attachment Each Meeting

6.1.1 Trip reports MS Word

Format

Within 3 working days following return

Email Each Trip

TEC Services Contract Page 13 of 18 Pages

SOW

Task# Deliverable Title Format Due Date Distribution /

Copies Frequency and Remarks

6.1.2 Input to program

documentation

MS Word Format

Within 5 working days of request

Email As requested by task COR

6.1.2 Informal review and comment on program documentation

MS Word Format

Within 5 working days of request

Email As requested by task COR

6.1.2 Formal review and comment on program documentation

MS Excel Format

Within 3 working days of request

Email As requested by task COR

6.1.2 Review of documentation for concurrence, approval and/or signature

MS Excel Format

Within 3 working days of request

Email As requested by task COR

6.1.3 Integrated Master

Schedule (IMS)

MS Excel Format

Initial - 45 days following award Updated weekly thereafter

Email Weekly Updates

6.1.3 Weekly Activity Report

(WAR)

MS Word Format

COB each Monday (or Tuesday following a Monday Federal Holiday)

Email Weekly

6.2.1 Requirements Traceability

Matrix (RTM)

MS Word Format

Within 10 working days of task COR request

Email As requested by task COR

6.2.1 TEMP input DT&E

Overview

MS Word Format

Within 10 working days of task COR request

Email As requested by task COR

6.2.2 Test and Evaluation

Strategy Briefing

MS Power Point Format

Within 10 working days of task COR request?

Email Each Event

6.2.2 Test Concept Briefing MS Power Point

Format

Within 10 working days of task COR request

Email Each Event

6.2.2 Test Readiness Review

Checklist

MS Excel Format

Within 5 working days of task COR request

Email Each Event

6.2.3 Completed Test Readiness

Review Checklist

MS Excel Format

NLT 3

calendar days before event start

Email Each Event

TEC Services Contract Page 14 of 18 Pages

SOW

Task# Deliverable Title Format Due Date Distribution /

Copies Frequency and Remarks

6.2.3 Test Readiness Review

Briefing

MS Power Point Format

NLT 2

Calendar days before event

Email Each Event

6.2.3 Test Plan MS Word

Format

Draft - 45 calendar days before event start Final – 10 calendar days before event start

Emailed to task

COR

Each Event Draft Final

6.2.3 Detailed Test Procedures MS Word

Format

NLT 10

calendar days before event start

Emailed to task COR Each Event

6.2.3 Data Collection Plan MS Word

Format

NLT 10

calendar days before event start

Emailed to task COR Each Event

6.2.3 Data Management Plan MS Word

Format

NLT 10

calendar days before event start

Emailed to task COR Each Event

6.2.3 Data Authentication

Group Procedures

MS Word Format

NLT 10

calendar days before event start

Emailed to task COR Each Event

6.2.3 Daily Hot Wash Briefing

Template

MS Power Point Format

NLT 5

calendar days before event start

Emailed to task COR Each Event

6.2.4 Daily Hot Wash Briefing MS Power Point

Format

Daily during event

Emailed to task COR Each Event

6.2.4 Daily Data Authentication

Group Briefing

MS Power Point Format

Daily during event

Emailed to task COR Each Event

6.2.5 Test Report MS Word

Format

Draft – 15 calendar days following end of event Final – 30 calendar days following end of event

Emailed to task

COR

Each Event Draft Final

6.2.5 Emerging Results

Briefing/Quick Look

MS Power Point Format

NLT 4

calendar days following end of event

Emailed to task COR Each Event

6.3 Concept Brief MS Power Point

Format Emailed to task

COR Each Event

TEC Services Contract Page 15 of 18 Pages

SOW

Task# Deliverable Title Format Due Date Distribution /

Copies Frequency and Remarks

6.3 Detailed Procedures MS Word

Format

NLT 10

calendar days before event start

Emailed to task COR Each Event

6.3 Compliance Validation

Plan

MS Word Format

NLT 10

calendar days before event start

Emailed to task COR Each Event

6.3 Emerging Results

Briefing

MS Power Point Format

NLT 4

calendar days following end of event

Emailed to task COR Each Event

6.3 Compliance Validation

Report

MS Word Format

Draft – 15 calendar days following end of event Final – 30 calendar days following end of event

Emailed to task

COR

Each Event Draft Final

6.4.2 Requirements Traceability

Matrix

JTB MS Word Format

Within 10 working days or request

Emailed to task COR As requested by task COR

6.4.3 Interoperability Certification Evaluation Plan (ICEP)

JTB MS Word Format

Draft - 90 calendar days before event start Final - 30 calendar days before event start

Emailed to task

COR

Each Event Draft Final

6.4.4 Quick Look Report JTB MS Word

Format

Draft – 15 calendar days following end of event Final – 30 calendar days following end of event

Emailed to task

COR

Each Event Draft Final

6.4.5 Certification Report JTB MS Word

Format

Draft – 30 calendar days following end of event Final – 45 calendar days following end of event

Emailed to task

COR

As requested by task COR

6.5 Security Assessment Plan MS Word

Format

NLT 10

calendar days before event start

Emailed to task

TEC Services Contract Page 16 of 18 Pages

SOW

Task# Deliverable Title Format Due Date Distribution /

Copies Frequency and Remarks

6.5 Security Plan input MS Word

Format

Within 10 working days of task COR request

Emailed to task COR As requested by task COR

6.6.1 Test and Evaluation Master Plan (TEMP) OT&E overview input

MS Word Format

Within 10 working days of task COR request

Emailed to task COR As requested by task COR

6.6.1 Risk Assessment (RA) MS Word

Format

Within 10 working days of task COR request

Emailed to task

COR

As requested by task COR

6.6.2

Analysis Structure:

Evaluation Framework with supporting Data Source Matrix

MS Word Format

Within 10 working days of task COR request

Emailed to task

COR

As requested by task COR

6.6.2 Test Concept Briefing MS Power Point

Format

NLT 210

calendar days before each event

Emailed to task

COR

As requested by task COR

6.6.2 Test Readiness Review

(TRR) Checklist

MS Excel Format

Within 5 working days of task COR request

Emailed to task

COR

As requested by task COR

6.6.3 Completed Test Readiness

Review (TRR) Checklist

MS Excel Format

Within 5 working days of task COR request

Emailed to task

COR

As requested by task COR

6.6.3 Test Readiness Review

(TRR) Briefing

MS Power Point Format

Within 5 working days of task COR request

Emailed to task

COR

As requested by task COR

6.6.3 Test Plan MS Word

Format

Draft – 90 calendar days before each event Final – 75 calendar days before each event

Emailed to task

COR

Each Event Draft Final

6.6.3 Daily Hot Wash Briefing

Template

MS Power Point Format

15 working days before each event

Emailed to task COR Each Event

6.6.4 Daily Hot Wash Briefing MS Power Point

Format daily during event

Emailed to task

COR

As requested by task COR

6.6.4 Daily Data Authentication

Group (DAG) Briefing

MS Power Point Format daily during event

Emailed to task

COR

As requested by task COR

6.6.5 Emerging Results

Briefing

MS Power Point Format

NLT 4

working days following end of event

Emailed to task

TEC Services Contract Page 17 of 18 Pages

SOW

Task# Deliverable Title Format Due Date Distribution /

Copies Frequency and Remarks

6.6.5 Test Report MS Word

Format

Draft – 15 calendar days following end of event Final – 30 calendar days following end of event

Emailed to task

COR

Each Event Draft Final

11. Security Requirements

a. Security Clearance Requirement: Secret

b. References: Per base PWS

c. Facility Security Clearance. Per base PWS

d. Security Clearance and Information Technology (IT) Level. Per base PWS

e. Investigation Requirements. Per base PWS

f. Adjudication for IT Access. Per base PWS

g. Interim IT Access. Per base PWS

h. Visit Authorization Letters. Per base PWS

i. Information Security and Other Miscellaneous Requirements. Per base PWS

j. Physical Security Requirements. Per base PWS

12. Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI).

Per base PWS.

13. Other Pertinent Information or Special Considerations.

a. Identification of Possible Follow-on Work. There are 4 option years for follow-on work for the TO that may be exercised at the Government’s discretion.

b. Identification of Potential Conflicts of Interest (COI). Per base PWS

c. Identification of Non-Disclosure Requirements. Per base PWS

d. Packaging, Packing and Shipping Instructions. Per base PW.

e. Inspection and Acceptance Criteria. Per base PWS

f. Property Accountability. Per base PWS

g. Supply Chain Risk Management (SCRM). Per base PWS

14. Section 508 Accessibility Standards.

The following Section 508 Accessibility Standard(s) (Technical Standards and Functional Performance Criteria) are applicable (if box is checked) to this acquisition.

TEC Services Contract Page 18 of 18 Pages

Technical Standards

1194.21 - Software Applications and Operating Systems

1194.22 - Web Based Intranet and Internet Information and Applications

1194.23 - Telecommunications Products

1194.24 - Video and Multimedia Products

1194.25 - Self-Contained, Closed Products

1194.26 - Desktop and Portable Computers

1194.41 - Information, Documentation and Support

The Technical Standards above facilitate the assurance that the maximum technical standards are provided to the Offerors. Functional Performance Criteria is the minimally acceptable standards to ensure Section 508 compliance.

This block is checked to ensure that the minimally acceptable electronic and information technology (E&IT) products are proposed.

Functional Performance Criteria

1194.31 - Functional Performance Criteria