IEW_S_IV_V_PWS_DRAFT(16DEC2015).doc

Performance Work Statement (PWS)

IEW&S IV&V

11/24/2015

Version 1.0 4Vision Statement

1 Scope

1.1 Background

1.2 Applicability

1.3 Order Type

1.4 Period of Performance

1.5 Place of Performance

1.5.1 Onsite (Government Facility)

1.5.2 Offsite (Contractor Facility)

2 Applicable Documents and Websites 3 Requirements

3.1 General

3.1.1 Materials, Equipment and Facilities

3.1.2 Security

3.1.3 Inspection and Acceptance / FOB

3.1.4 Phase In and Phase Out

3.1.5 Task Order Management

3.1.6 Travel

3.1.7 Personnel Qualifications

3.1.8 Work Hours

3.1.9 Contractor Manpower Reporting (CMR)

3.1.10 Contractor Mandatory Training

3.1.11 Formal Reviews

3.2 Performance

3.2.1 Provide Program Management Support

3.2.2 Conduct IV&V planning for intelligence processing systems.

3.2.3 Conduct IV&V execution for intelligence processing systems.

3.2.4 Conduct IV&V close-out activities for intelligence processing systems.

3.2.5 Provide process improvement support.

3.2.6 Provide Meeting Support

3.2.7 Maintain an Automated Test Tool Environment

3.2.8 Provide Transition IV&V Test Support

4 Deliverables 5 Data Rights

Performance Work Statement (PWS)

IEW&S IV&V

Vision Statement

The purpose of Independent Verification and Validation (IV&V) testing is to establish a level of confidence that a PPSS supported system performs as intended by design and as specified by requirements. The general aim of SEC ISD IV&V software testing is to validate the expected functionality of the supported systems by systematically exercising the software under controlled circumstances. The Test process should be considered an integral part of the general Software Engineering Support process and is a shared responsibility between the software developers and test engineers.

1 Scope

The scope of this PWS is to provide support services to Communications Electronic Command (CECOM) Software Engineering Center (SEC) Intelligence Support Division (ISD) located in Ft. Huachuca, AZ. The effort supports the Independent Verification and Validation (IV&V) testing activities in the area of: program management support; conduct IV&V planning for intelligence processing systems; conduct IV&V execution for intelligence processing systems; conduct IV&V close-out activities; process improvement support; meeting support; maintain automated test tool environment; and transition IV&V test support.

1.1 Background

The U.S. Army CECOM SEC ISD Division provides full spectrum Post Production Software Support (PPSS) and Post Deployment Software Support (PDSS) for Army and other Department of Defense (DoD) programs and systems. This PWS addresses requirements for Software Test engineering and test support for systems currently maintained by the ISD.

SECs sustainment requirement is to produce software releases that are: 1) accepted by its intended users, 2) consistent and reproducible, 3) achieves mandatory security requirements, 4) complies with all applicable regulatory and statutory requirements, 5) stable and mature, and, 6) cost effective. The contractor shall perform tasks in a manner that support the requirements.

1.2 Applicability

N/A.

1.3 Order Type

This task order is a Firm Fixed Price (FFP) for all line items other than travel and materials. Travel and materials are on a Cost basis in accordance with FAR 16.302.

1.4 Period of Performance

The period of performance shall be a twelve (12) month base period with two twelve (12) month option periods.

1.5 Place of Performance

1.5.1 Onsite (Government Facility)

Place of Performance for this TO shall be at Government facilities located at Fort Huachuca, Arizona (AZ) and Aberdeen Proving Ground (APG), Maryland.

1.5.2 Offsite (Contractor Facility)

N/A.

2 Applicable Documents and Websites

The following documents and websites are referenced for the performance of this task order. The Government reserves the right to update applicable documents.

Army Material Command (AMC) Pamphlet 1-2

Army Regulation 70-1, Army Acquisition Policy

CECOM Regulation 700-20, Equipment Management Program

CECOM Regulation 700-34, Release of Material for Issue

CECOM Regulation 700-56, Material Release, Fielding and Transfer

Government to provide:

· Intelligence Support Division (ISD) Independent Verification and Validation (IV&V) Standard Operating Procedures (SOP)

· Software Sustainment Transition Plan (SSTP)

· Configuration Management (CM) Standard Operation Procedures (SOP)

· Quality Assurance (QA) Standard Operation Procedures (SOP)

· Software Engineering Center (SEC) Style Guide

· Guide for Creating CECOM SEC Correspondence

· Software Test Plan Template

· Software Test Description Template

· Test Scenarios Template

· Test Case Template

· Test Dataset Template

· Automated and Manual Test Scripts Template

· Daily Test Report Template

· Software Test Report (STR) Template

· Test Readiness Review (TRR) Template

· Lessons Learned Template

· Risk Management Workbook Template

· Trip Report Template

· Meeting Minutes Template

3 Requirements

3.1 General

3.1.1 Materials, Equipment and Facilities

All requirements and sub-requirements of paragraph 3.2 apply to this task order.

Performance of the requirements set forth within this PWS shall be conducted at the Communications-Electronics Command-Life Cycle Management Command (CECOM-LCMC) SEC facilities at Ragatz Hall located at Fort Huachuca, Arizona (AZ) and APG, MD. The Contractor in support of this requirement shall utilize these facilities as the primary locations for management, system & software engineering, and software testing work. The Government will provide on-site Contractor personnel with adequate workspace and equipment/material (to include desks, chairs, secure storage cabinet space, and office telephones), and access to printers, FAX machine, scanners and photocopiers at the Government facility where the work will be performed for Contractor use on a rent-free basis IAW FAR 52.245-9 for the sole purpose of performing tasks within this PWS. The Equipment Coordinator (EC) is responsible for determining what equipment is required.

3.1.2 Security

The highest level of facility clearance required for the contractor to perform on this task order is Top Secret. The highest level of classified material the contractor will be required to safeguard at its own facility is none.

The following security requirements apply to this task order and are further described in the DD Form 254, Contract Security Classification Specification (See Appendix G):

· This contract will not require access to Communications Security (COMSEC) information.

· This contract will not require access to Restricted Data.

· This contract will not require access to Critical Nuclear Weapon Design Information.

· This contract will not require access to Formerly Restricted Data.

· This contract will require access to Sensitive Compartmentalized Information (SCI.)

· This contract will require access to Non-SCI Intelligence Information.

· This contract will not require access to Special Access Information.

· This contract will require access to NATO Information.

· This contract will not require access to Foreign Government Information.

· This contract will not require access to Limited Dissemination Information.

· This contract will require access to For Official Use Only Information (FOUO.)

· This contract will require access to SIPRNET, NIPRNET, JWICS Security Classification Guides (SCG), and DCGS-A SCG

· In performing this contract, the contractor will have access to classified information only at another contractor's facility or a government activity.

· In performing this contract, the contractor will not receive classified documents only.

· In performing this contract, the contractor will not receive and generate classified material.

· In performing this contract, the contractor will not fabricate, modify, or store classified hardware.

· In performing this contract, the contractor will not perform services only.

· In performing this contract, the contractor will not have access to U.S. Classified information outside the U.S., Puerto Rico, U.S. Possessions and trust territories.

· In performing this contract, the contractor will not be authorized to use the services of the Defense Technical Information Center (DTIC) or other secondary distribution center.

· In performing this contract, the contractor will not require a COMSEC account.

· In performing this contract, the contractor will not have a TEMPEST requirement.

· In performing this contract, the contractor will have operational security (OPSEC) requirements.

· In performing this contract, the contractor will have sensitive IT duties and SCI IS Processing .

3.1.3 Inspection and Acceptance / FOB

Inspection and acceptance shall be at Fort Huachuca, AZ.

Ship to address is:

U.S. Army CECOM SEC ISD

Attn: AMSEL-SEC-ISD (Clifford Gray)

Greely Hall Bldg. 61801, Room 2606-E

Fort Huachuca, AZ 85613-5000

DODAAC: W91QUS

All deliverables shall be delivered to the Government in IAW this PWSs paragraph 3.2 and Appendix D.

3.1.4 Phase In and Phase Out

A transition period is scheduled for the two (2) month period immediately prior to contract start date (phase in) and the two (2) month prior to contract end date (phase out) to allow for orderly contract transition. In order to maximize the effectiveness of the transition process, an initial meeting between the Government's Contract Administrator and Contract Managers for the incoming and outgoing Contractors shall be held to address phase in and phase out requirements and responsibilities no later than seven (7) days into the phase in/phase out period, and subsequent meetings will be held as determined by the PCO, but not less than weekly thereafter. When an incumbent contractor is also the successor contractor, these meetings will not be waived, since the orderly transition from one work specification to another will also require significant management involvement in the transition process.

During the two (2) months phase in period, key incoming contractor personnel will be permitted to observe current operations of the outgoing contractor and Government personnel pertaining to this contract at no additional cost to the Government. The incoming contractor shall ensure that its phase in operations do not hinder or interfere with normal operations of the phase out contractor, and that maximum effort is made to avoid loss of productivity. The current Contract is W15P7T-13-C-E027. During the phase in, the outgoing contractor will transfer all work at contract start date to the successor contractor.

During the two (2) month period immediately prior to the end of this contract, including options, or if the contractor is not awarded the subsequent contract for these services, the contractor shall permit his successor to observe and become familiar with any and all operations under this contract. The contractor shall remain responsible and liable for the completion of all requirements of this contract, which shall begin on or before the final day of this contract. The contractor shall not defer any requirements for the purpose of avoiding responsibility and transferring such responsibility to the successor contractor or the Government. The contractor shall fully cooperate with the successor contractor and the Government, and shall not interfere with their work or duties. The contractor shall provide the PCO with a phase out plan not later than forty-five (45) days prior to the contract end date. This plan shall detail disposition action for all furnishings, equipment, and documentation.

3.1.5 Task Order Management

The Government will provide the necessary oversight, management, and review of cost and performance data submitted in accordance with the Contract Data Requirements Lists (CDRLs) addressed in paragraph 4.0 below. In addition to these formal reporting requirements, the Government will maintain appropriate oversight through continuous informal technical interchange with the contractor. When substituting personnel, the contractor shall ensure that the new personnel meet or exceed the stated qualification requirements. This Contract shall be addressed in the CDRL XXXX, DI-MGMT-80368A, Status Report, subtitled Weekly Status Report. The contractor will be monitored by the COR to ensure all standards set forth in section 3.2 are adhered to.

Additionally, the contractor shall provide Monthly Status Reports IAW CDRL XXX and Monthly Performance and Cost Reports IAW CDRL XXXX.

3.1.6 Travel

Contractor personnel shall be required to travel to CONUS work sites in order to perform tasks under this PWS. The number of trips taken and the number of personnel authorized for travel will be limited to the minimum necessary to accomplish the work requirements. The contractor will be responsible for arranging all contractor personnel travel at the lowest cost mode of transportation commensurate with mission requirements and good traffic management principles, and in accordance with the applicable C4ISR and local command policies as well at the Joint Travel Regulation, PAM 715-16 and AR 715-9. Reimbursement for the cost of lodging and incidental expenses will be actual costs incurred and shall be considered reasonable and allowable provided that the actual cost does not exceed the amounts allowed lAW the Joint Travel Regulations. All travel will be on a cost reimbursement basis. There will be no reimbursement for local travel in and around contractor's location within forty miles.

All CONUS travel shall be in accordance with the individual Contract requirement. All CONUS travel and extended CONUS travel details must be provided to and approved by the KO or designated COR prior to the commencement of travel.

A summary of anticipated travel is provided in Appendix E.

There are no OCONUS travel requirements for this PWS.

The Contractor shall submit a Trip Report in accordance with CDRL XXXX DI-ADMN-81308A, Conference Report, subtitled Conference, Working Groups and Trip Reports after each trip.

3.1.7 Personnel Qualifications

It is desirable for the Contractor personnel have a breadth of knowledge of the intelligence systems in Appendix C - Systems Descriptions as well as real-world experiences in the following several intelligence disciplines:

· Mission Command Interoperability

· DCGS-A Contingency Operations

· Perform Situation Development

· Establish Intelligence Architectures

· Provide Intelligence Support to Targeting and Effects

· Perform Intelligence Preparation of the Battlefield (IPB)

· Perform Electronic Preparation of the Battlefield (EPB)

· Managing Tactical Information

· Perform Intelligence Surveillance and Reconnaissance (ISR) Synchronization Operations

· Conduct G2X/S2X Operations

At least one-third of the workforce shall have operational experience in one or more of the following intelligence disciplines:

· All Source Intelligence Analyst

· Signals Intelligence Analyst (SIGINT)

· Counterintelligence/Human Intelligence Analyst (CI/HUMINT)

· Geospatial Intelligence Analyst (GEOINT)

The contractor shall employ only personnel who meet the minimum qualifications provided under Appendix A and are fully qualified and competent to perform the tasks specified in this PWS. The contractor shall ensure that such personnel are utilized in a manner that maximizes productivity and efficiency. For purposes of surveillance, resumes of contractor personnel performing support services as described within this PWS are subject to verification by the COR to ensure that the support personnel meet or exceed the proposed category descriptions, qualifications, and possess the minimum technical skills and experience specified at Appendix A of this PWS.

The critical personnel specified in Appendix A of this PWS are considered to be essential to work performance. At least 30 days prior to diverting any of the specified individuals to other programs or contracts (or as soon as possible, if an individual must be replaced, for example, as a result of leaving the employ of the Contractor), the Contractor shall notify the Contracting Officer and shall submit, IAW CDRL XXXX DI-MGMT-80368A, Status Report/Critical Personnel Change, comprehensive justification for the diversion or replacement request (including proposed substitutions for critical positions) to permit evaluation by the Government of the impact on performance under this contract. The Contractor shall not divert or otherwise replace any critical personnel without the written consent of the Contracting Officer. The Government may modify the contract to add or delete key personnel at the request of the contractor or Government. Critical positions shall be filled within thirty (30) calendars days of any vacancy. Non-critical positions shall be filled within forty-five (45) calendar days of any vacancy.

3.1.8 Work Hours

The contractor is responsible for conducting business, between the hours of 0730 and 1700 Monday thru Friday except Federal holidays. When the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings; contractor personnel who normally work in the closed Government facility are not responsible for conducting business. The Contractor shall not be reimbursed when the government facility is closed for the above reasons. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is open for operations.

Generally, work hours will be a 40 hour work week, with hours per day and days of the week being flexible to accommodate mission needs. However, hours per day and days of the week may vary depending on SEC ISD mission requirements. Contractor may flex their time during the same two week 80-hour time period. Work week scheduling must be flexible and able to support customer requirements as specified by the COR.

The contractor shall obtain designated COR or KO approval in advance for all projected extended hours or overtime one month in advance. Upon completion of the extended hours, the contractor shall provide to the COR or KO the actual hours utilized. In the event of an emergency or surge that requires extended hours to complete work on schedule, the contractor shall submit a written request to the COR or KO detailing the need for the extended hours requirement and the appropriate PWS task that covers the work.

Should situations arise in which the above specified advance notice cannot be met, Government support of Contractor extended hours or overtime shall be handled on a case-by-case basis.

3.1.9 Contractor Manpower Reporting (CMR)

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor will report ALL contractor manpower (including subcontractor manpower) required for performance of this contract. The contractor is required to completely fill in all the information in the format using the following web address: https://cmra.army.mil. The required information includes:

a. Contracting Office, PCO, Contracting Officers Technical Representative;

b. Contract number, including task and delivery order number;

c. Beginning and ending dates covered by reporting period;

d. Contractor name, address, phone number, e-mail address, identification data for incoming contractor employee;

e. Estimated direct labor hours (including sub-contractors);

f. Estimated direct labor dollars paid this reporting period (including sub-contractors);

g. Total payments (including sub-contractors);

h. Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different);

i. Estimated data collection cost;

j. Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information);

k. Locations where contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

l. Presence of deployment or contingency contract language; and

m. Number of contractor and sub-contractor employees deployed in theater this reporting period (by country). As part of its submission, the contractor will also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed twelve (12) months ending 30 September of each government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct Extensible Markup Language (XML) data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a contractors systems to the secure web site without the need for separate data entries for each required data element at the web site. The specific formats for the XML direct transfer may be downloaded from the web.

3.1.10 Contractor Mandatory Training

The contractor shall complete all government mandated training requirements as determined by CECOM SEC for contractor employees that occur during the period of performance for this task order. Contractors shall track Mandatory Training compliance using their own resources. Evidence of compliance shall be presented upon Government request. The use of the Total Employee Development (TED) system is not required.

Optional Defense Acquisition University online training classes will be allowed at the discretion of the COR and as mission requirements dictate.

3.1.11 Formal Reviews

A post award orientation meeting shall be held at the Government's facility at Fort Huachuca, AZ within ten (10) business days after award of contract. This provision shall in no way constitute grounds for excusable delay by the contractor in performance under the contract.

Formal program management reviews will be held quarterly or at the Government's request to inform the Government of problems, schedule, and incurred costs of the contract. The Government also reserves the right to call for informal management and cost status reviews as needed. These formal and informal reviews do not relieve the contractor from its ongoing responsibility to inform the Government of problematic issues that affect or may affect performance, cost or schedule. The Contractor shall submit a In Progress Review (IPR) Brief, IAW CDRL XXXX, DI-MGMT-80368A, In Progress Review of the contractor efforts towards achieving the contract objectives.

3.2 Performance

The following section specifies the Performance Objectives and Performance Elements for the contract.

3.2.1 Provide Program Management Support

3.2.1.1 The Contractor shall develop and maintain the IV&V Integrated Master Schedule (IMS)

SEC ISD currently uses MS Project.

Performance Standards

a) STD: Delivered using appropriate SEC repositories and tools platform AQL: 100% compliance with standard unless otherwise directed by the Government.

b) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Materials meets the SEC style guide requirements AQL: No more than 2 corrective revisions

d) STD: Materials meet the guide for creating CECOM SEC correspondence requirements on first submission AQL: No more than 2 corrective revisions Deliverables A18 Integrated Master Schedule

3.2.1.2 The Contractor shall provide analysis, assist with evaluation, and propose solutions and recommendations for technology insertion initiatives for the test environment

Performance Standards

a) STD: Addresses all program and system areas 100% of the time AQL: Addresses all program and system areas 98% of the time

b) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Upon government approval, files are uploaded in the repository within 3 business days AQL: Upon government approval, files are uploaded in the repository within 5 business days

A15 White Paper

3.2.1.3 The Contractor shall participate in meetings, reviews, conferences, and working groups for systems under test

a) STD: Attends weekly project meetings hosted by the system Project Lead AQL: Attends meeting 90% of the time

3.2.1.4 The Contractor shall implement and manage a risk management program for the IV&V team.

The contractor will use the Test Readiness Checklist (TRC) to mitigate any and all possible risk. Within the TRC is the Risk Management tool. This allows for the same effect of the Risk Management Workbook but is tailored for SEC ISD processes.

Performance Standards

a) STD: Utilize the ISD identified Risk Management Workbook AQL: 100% compliance with standard unless otherwise directed by the Government.

b) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Upon government approval, Risk management workbook is uploaded to the Government designated repository within 3 business days.

AQL: Upon government approval, Risk management workbook is uploaded to the Government designated repository within 5 business days.

A19 Risk Management Workbook

3.2.1.5 The Contractor shall utilize appropriate SEC repositories and tools to organize files and documentation for the IV&V program

a) STD: Delivered using appropriate SEC repositories and tools platform AQL: 100% compliance with standard unless otherwise directed by the Government.

b) STD: Materials are delivered in accordance with schedule AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Materials meets the SEC style guide requirements AQL: No more than 2 corrective revisions

d) STD: Materials meet the guide for creating CECOM SEC correspondence requirements on first submission AQL: No more than 2 corrective revisions

3.2.1.6 The Contractor shall provide recommendations for the IV&V vision, goal, and mission statements.

Performance Standards

a) STD: Relevant to the ISD vision, mission statements, and goals AQL: 100% alignment with the Division vision, mission statements, and goals

3.2.2 Conduct IV&V planning for intelligence processing systems.

The purpose of the verification process is to plan and to test selected work products to ensure they meet their specified requirements. This includes the verification of the product or product components and intermediate work products against their requirements. Validation determines if the product, product components or service fulfills or will fulfill its intended use when placed in its intended environment. Validation can be applied to all aspects of the product or product component in any of its intended environments, such as operation, training, manufacturing and sustainment.

3.2.2.1 The Contractor shall submit testing schedule for systems during IV&V planning phase

Test schedule shall include scope, objectives, manpower resources, IV&V Test activities and deliverable schedule. Contractor shall initiate IV&V Testing activities after the test schedule is approved by the Government.

Performance Standards

a) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

b) STD: Test schedule is accurate and complete with no major rework AQL: No more than 2 reworks revisions

c) STD: Upon government approval, files are uploaded in the repository within 3 business days AQL: Upon government approval, files are uploaded in the repository within 5 business days

A26 Test Schedule

3.2.2.2 The Contractor shall review artifacts for systems during the development team sprint cycle(s)

Support includes reviewing new or modified software requirements (in the form of Project Forge Software Issue(s), hereafter referred to as artifact(s)) and test related documentation.

Performance Standards

a) STD: Review of artifacts are completed in accordance with Intelligence Support Division (ISD) Independent Verification and Validation (IV&V) Standard Operating Procedure (SOP) AQL: 100% compliance with standard.

b) STD: Review all government provided artifacts.

AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Complete tasks by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

d) STD: Notify the government if a new test case or procedure is required upon completion of review.

AQL: 100% compliance with standard.

3.2.2.3 The Contractor shall review, develop, and update test documentation for systems during the development team sprint cycle(s)

Deliverables will depend on Systems Under Test requirements. Required deliverables will be determined at the Release Control Board.

Performance Standards

a) STD: Developed in accordance with Intelligence Support Division (ISD) Independent Verification and Validation (IV&V) Standard Operating Procedure (SOP) AQL: 100% compliance with standard.

b) STD: Provided in accordance with government designated format.

AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

d) STD: Reports are accurate and complete with no major rework AQL: No more than 2 corrective revisions

e) STD: Upon government approval, files are uploaded in the repository within 3 business days AQL: Upon government approval, files are uploaded in the repository within 5 business days Deliverables A01 Software Test Plan A03 Software Test Description A06 Test Scenarios A07 Test Cases A08 Test Datasets

3.2.2.4 The Contractor shall prepare test environment for systems during the development team sprint cycle(s).

The contractor shall provide automated and manual test scripts, test readiness review checklist. Ensure the appropriate networks, equipment is operational, and personnel resources are prepared and available.

Performance Standards

a) STD: Test environment prepared in accordance with Intelligence Support Division (ISD) Independent Verification and Validation (IV&V) Standard Operating Procedure (SOP) AQL: 100% compliance with standard.

b) STD: Validate correct software baseline is provided and loaded.

AQL: 100% compliance with standard.

c) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

d) STD: Reports are accurate and complete with no major rework AQL: No more than 2 corrective revisions

e) STD: Upon government approval, files are uploaded in the repository within 3 business days AQL: Upon government approval, files are uploaded in the repository within 5 business days Deliverables A09 Automated and Manual Test Scripts A12 Test Readiness Review Checklist

3.2.2.5 The Contractor shall conduct dry runs of test cases as time permits prior to test readiness review.

a) STD: IAW Intelligence Support Division (ISD) Independent Verification and Validation (IV&V) Standard Operating Procedure (SOP) AQL: 100% compliance with standard.

b) STD: Complete tasks by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

3.2.2.6 The Contractor shall assist the Government in conducting and participating in Test Readiness Reviews (TRR) for systems under test

Performance Standards

a) STD: Upon Government approval, meetings are scheduled within 5 business days AQL: Upon Government approval, meetings are scheduled within 3 business days

b) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Materials meets the SEC style guide requirements AQL: No more than 2 corrective revisions

d) STD: Materials meet the guide for creating CECOM SEC correspondence requirements on first submission AQL: No more than 2 corrective revisions

3.2.2.7 The Contractor shall conduct pre-test preparations and load system software for systems under test

Pre-test support includes loading various referenced databases, security tables, message data and user accounts Performance Standards

a) STD: Conduct Pre-test preparations in accordance with Intelligence Support Division (ISD) Independent Verification and Validation (IV&V) Standard Operating Procedure (SOP) AQL: 100% compliance with standard.

b) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Upon government approval, files are uploaded in the repository within 3 business days AQL: Upon government approval, files are uploaded in the repository within 5 business days

A12 Test Readiness Review Checklist

3.2.3 Conduct IV&V execution for intelligence processing systems.

3.2.3.1 The Contractor shall configure and verify all hardware and software required for systems under test

Performance Standards

a) STD: IAW Intelligence Support Division (ISD) Independent Verification and Validation (IV&V) Standard Operating Procedure (SOP) AQL: 100% compliance with standard.

b) STD: No unapproved hardware or software AQL: 100% compliant with standard

3.2.3.2 The Contractor shall execute applicable tests cases/scenarios and prepare daily test report for systems under test.

Types of tests performed may include: Software Release Evaluation; Characterization Test; Government Acceptance Testing; Load Testing; Automated Testing; Stress Testing; Performance Testing; Regression Testing; Operational Software Test and Evaluation Testing; Information Assurance Vulnerability Assessment (IAVA) testing; Defect Retesting and Army Interoperability Certification (AIC) Testing; Third Party Software Testing.

Performance Standards

a) STD: Tests conducted in accordance with Intelligence Support Division (ISD) Independent Verification and Validation (IV&V) Standard Operating Procedure (SOP) AQL: 100% compliance with standard.

b) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Provide daily test report.

AQL: 100% compliance with standard unless otherwise directed by the Government.

d) STD: Daily Test Report uploaded to the designated Government repository by close of business each test day.

AQL: Daily Test Report uploaded to the designated Government repository by 0800 next business day.

Deliverables A10 Daily Test Report A20 Incident Report at Source (IRAS) Form

3.2.4 Conduct IV&V close-out activities for intelligence processing systems.

3.2.4.1 The Contractor shall conduct test result analysis and provide actionable recommendations for systems under test.

Performance Standards

a) STD: IAW Intelligence Support Division (ISD) Independent Verification and Validation (IV&V) Standard Operating Procedure (SOP) AQL: 100% compliance with standard.

b) STD: Complete tasks by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

3.2.4.2 The Contractor shall conduct post test exit criteria procedures for systems under test.

Support includes capturing key test outputs, test lessons learned, test results, test logs, and test documents related to each test.

Performance Standards

a) STD: IAW Intelligence Support Division (ISD) Independent Verification and Validation (IV&V) Standard Operating Procedure (SOP) AQL: 100% compliance with standard.

b) STD: Complete tasks by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

3.2.4.3 The Contractor shall prepare software test report and lessons learned for systems under test.

Performance Standards

a) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

b) STD: Reports are accurate and complete with no major rework AQL: No more than 2 corrective revisions

c) STD: Upon government approval, files are uploaded in the repository within 3 business days AQL: Upon government approval, files are uploaded in the repository within 5 business days Deliverables A04 Software Test Reports A16 Lessons Learned

3.2.5 Provide process improvement support.

3.2.5.1 The Contractor shall support configuration management process for IV&V Testing.

Ensures that Intelligence Support Division's (ISD) procedures and policies are followed during the test IAW the Configuration Management SOP.

Performance Standards

a) STD: IAW the Configuration Management (CM) Plan and CM SOP AQL: 100% compliance with standard.

b) STD: Complete tasks by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

3.2.5.2 The Contractor shall support quality assurance process for IV&V testing

Ensures that Intelligence Support Division's (ISD) procedures and policies are followed during the test IAW the Quality Assurance Process guidance.

Performance Standards

a) STD: IAW the Quality Assurance (QA) Plan and QA SOP AQL: 100% compliance with standard.

b) STD: Complete tasks by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

3.2.5.3 The Contractor shall analyze, develop and deliver improvement recommendations for IV&V activities.

Performance Standards

a) STD: Delivered using appropriate SEC repositories and tools platform AQL: 100% compliance with standard.

b) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Materials meets the SEC style guide requirements AQL: No more than 2 reworks

d) STD: Materials meet the guide for creating CECOM SEC correspondence requirements on first submission AQL: No more than 2 reworks

3.2.6 Provide Meeting Support

3.2.6.1 The Contractor shall coordinate, generate, and distribute meeting agendas for IV&V meetings.

Performance Standards

a) STD: Meeting agendas are distributed 3 business days from the meeting date AQL: Meeting agendas are distributed 1 business day from the meeting date

A13 Meeting Agenda

3.2.6.2 The Contractor shall develop, organize, and present briefing materials in support of IV&V activities.

a) STD: Delivered using appropriate SEC repositories and tools platform AQL: 100% compliance with standard unless otherwise directed by the Government.

b) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard.

c) STD: Briefing materials meets the SEC style guide requirements AQL: No more than 2 reworks

d) STD: Materials meet the guide for creating CECOM SEC correspondence requirements on first submission AQL: No more than 2 reworks

A25 Briefing Materials

3.2.6.3 The Contractor shall record and distribute meeting minutes for IV&V meetings.

a) STD: Meeting minutes are distributed within 2 business days after meeting conclusion AQL: Meeting minutes are distributed within 3 business days after meeting conclusion

A14 Meeting Minutes

3.2.6.4 The Contractor shall record, distribute, track, and report action item status for IV&V meetings

a) STD: Meeting action items are recorded AQL: No more than 2 actin items are unrecorded from each meeting

b) STD: Action items are distributed within 2 business days of meeting conclusion AQL: Action items are distributed within 3 business days of meeting conclusion

c) STD: Action items are incorporated into the subsequent meeting agenda AQL: 100% compliance with standard unless otherwise directed by the Government.

d) STD: Action items are reported to the IV&V Government Lead on a weekly basis AQL: Action items are reported to the IV&V Government Lead at the subsequent meeting

e) STD: Delivered using appropriate SEC repositories and tools platform AQL: 100% compliance with standard unless otherwise directed by the Government.

A14 Meeting Minutes

3.2.7 Maintain an Automated Test Tool Environment

3.2.7.1 The Contractor shall develop, update, and maintain automated test tools for the test environment.

Performance Standards

a) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

b) STD: No unapproved hardware or software integrated into baseline unless approved by the Government.

AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Update Hardware/Software Baseline to reflect changes.

AQL: 100% compliance with standard unless otherwise directed by the Government.

3.2.8 Provide Transition IV&V Test Support

3.2.8.1 The Contractor shall attend Field Support Engineering (FSE) and operator level training for systems transitioning to SEC ISD

Performance Standards

a) STD: Participate in FSE and operator training AQL: 100% compliance with standard unless otherwise directed by the Government.

b) STD: Notify government POC 10 business days in advance if cannot attend training AQL: Notify government POC 5 business days in advance if cannot attend training

3.2.8.2 The Contractor shall inventory all delivered documentation of the transitioned version of the system for the establishment of an initial test baseline

Performance Standards

a) STD: IAW the system Configuration Management (CM) Plan and CM SOP AQL: 100% compliant with standard

b) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Upon government approval, files are uploaded in the repository within 3 business days AQL: Upon government approval, files are uploaded in the repository within 5 business days

3.2.8.3 The Contractor shall perform IV&V interoperability testing between the designated transition baselines and the currently sustained system baselines.

Deliverables will depend on System Under Test requirements. Required deliverables will be determined at the Release Control Board.

Performance Standards

a) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

b) STD: Reports are accurate and complete with no major rework AQL: No more than 2 corrective revisions

c) STD: Upon government approval, files are uploaded in the repository within 3 business days AQL: Upon government approval, files are uploaded in the repository within 5 business days Deliverables A01 Software Test Plan A03 Software Test Description A04 Software Test Reports A06 Test Scenarios

3.2.8.4 The Contractor shall perform IV&V Government Acceptance Testing for designated transition baselines.

Deliverables will depend on System Under Test requirements. Required deliverables will be determined at the Release Control Board.

Performance Standards

a) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

b) STD: Reports are accurate and complete with no major rework AQL: No more than 2 corrective revisions

c) STD: Upon government approval, files are uploaded in the repository within 3 business days AQL: Upon government approval, files are uploaded in the repository within 5 business days Deliverables A01 Software Test Plan A03 Software Test Description A04 Software Test Reports A06 Test Scenarios

3.2.8.5 The Contractor shall assist with determining adequate IV&V staffing levels for transition to PPSS

a) STD: Delivered using appropriate SEC repositories and tools platform AQL: 100% compliance with standard unless otherwise directed by the Government.

b) STD: Complete tasks and deliverables by specified deadlines. Deadlines will be set by the Government at the start of a task and based on both internal and external factors (e.g.. Task complexity, test events, release schedules) AQL: 100% compliance with standard unless otherwise directed by the Government.

c) STD: Materials meets the SEC style guide requirements AQL: No more than 2 reworks

d) STD: Materials meet the guide for creating CECOM SEC correspondence requirements on first submission AQL: No more than 2 reworks

4 Deliverables

Deliverables shall use commercial best practices and be in contractor format unless otherwise directed by the government. All documentation, reports, software, databases, presentations, and similar materials prepared under this contract shall be the property of the Government. Reference to the contractor shall not appear in any portion of delivered products.

5 Data Rights

The Government's rights in non-commercial technical data and software deliverables shall be governed by DFARS 252.227-7013 and DFARS 252.227-7014, respectively. Additional provisions related to technical data and software rights are provided in Appendix (F).