GCCS_TCO_JTCW_PWS_7_Oct_2015_-_Final.pdf

Performance Work Statement

For

Global Command and Control System (GCCS) –

Tactical Combat Operations (TCO) /

Joint Tactical Common Operational Picture (COP)

Workstation (JTCW)

Test & Evaluation (T&E)

Contractor Support Services (CSS)

7 October 2015

Prepared by:

UNITED STATES MARINE CORPS

Marine Corps Tactical Systems Support Activity (MCTSSA)

Program Engineering Support Group (PESG)

Camp Pendleton, CA 92055-5171 i

TABLE OF CONTENTS

1 INTRODUCTION

1.1 Background

1.2 Scope

2 APPLICABLE DOCUMENTS

2.1 Compliance Documents

2.2 Guidance Documents

3 PERFORMANCE REQUIREMENTS

3.1 Test Support

3.2 Joint Certification Testing

3.3 Technical Support to MAGTF C2 Test/Engineering Events

3.4 Working Group Participation

4 DELIVERABLES

4.1 Monthly Status Report

4.2 Technical Report

4.3 Test Plans

4.4 Test Procedures

4.5 Test Incident Reports

4.6 Test Logs

4.7 Test Reports

4.8 Distribution Statement

4.9 Delivery Instructions

4.10 Unclassified End Products

4.11 Classified End Products

4.12 Schedule of Deliveries

5 PERFORMANCE LOCATION

6 INSPECTION OF DELIVERABLES

7 PERIOD OF PERFORMANCE

8 GOVERNMENT FURNISHED EQUIPMENT AND FACILITIES

8.1 Government Furnished Equipment

8.2 Access to Government Property

8.3 Access to Government Facilities

8.4 Government Furnished Material

8.5 Government Furnished Information

9 SECURITY REQUIREMENTS

9.1 Security Level

9.2 DD Form 254

9.3 Security Clearance

9.4 Base Security

9.5 OPSEC Requirements

10 PERSONNEL

11 TRAVEL REQUIREMENTS

12 INVOICING

13 ADMINISTRATIVE AUTHORITY

13.1 Contracting Officer

ii

13.2 Contracting Officer Representative (COR)

14 ORGANIZATIONAL CONFLICT OF INTEREST

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

1 INTRODUCTION

1.1 Background

Marine Corps Tactical Systems Support Activity (MCTSSA) provides test and engineering support services to the Global Command and Control System (GCCS), Tactical Combat

Operations (TCO)/Joint Tactical Common Operational Picture (COP) Workstation (JTCW)

Program Offices as directed by the Marine Corps Systems Command (MCSC) Marine Air

Ground Task Force (MAGTF) Command, Control and Communications (C3) Program Office.

MCTSSA is involved in all aspects of GCCS-TCO/JTCW Family of Systems (FoS) testing to include developmental testing, engineering evaluations, developer-assist testing, stability and performance testing, government acceptance testing and joint certification testing. MCTSSA focuses on testing GCCS-TCO/JTCW FoS within an operationally representative MAGTF

Command and Control (C2) architecture executing operational mission threads under representative network loads. The operationally relevant architecture represents Division down to Battalion echelons utilizing the Combat Operations Center (COC) and AN/PRC-117G Radios.

The MCTSSA GCCS-TCO/JTCW FoS team works with the Operational Forces Tactical

Systems Support Center (OFTSSC), as well as other C2 Programs of Record (PoR) providing

GCCS-TCO/JTCW FoS subject matter expertise (SME) for test events, exercises and Operating

Forces feedback. The MCTSSA team provides support with setup, configuration and troubleshooting of the GCCS-TCO/JTCW FoS. The MCTSSA team also identifies software issues, generates Trouble Reports (TR) and conducts engineering analysis to further define issues and potential work around. MCTSSA is a voting member in the GCCS-TCO/JTCW FoS

Technical Review Board (TRB) for the vetting of TRs, and a member of the GCCS-TCO/JTCW

FoS Test Integrated Product Team (IPT) and Logistics IPT.

The GCCS-TCO system runs on the Tactical COP Server (TCS) platform which is composed of an Oracle T-5140 server and TSC software. The TCS software is integrated using the GCCS-

Joint (GCCS-J) Global software required for a COP. The TCS requires regular updates and patches to correct fleet-reported defects and to maintain compliance with its parent GCCS-J baseline.

TCS is the principal tool within the MAGTF for Situational Awareness (SA) through distribution of the Common Tactical Picture (CTP) and is the primary entry point for the COP. TCS provides commanders at all echelons with the ability to map and display friendly and enemy locations, as well as plan, develop, display, and transmit overlays of intended movements. TCS also provides commanders in both garrison and tactical operations the ability to receive, fuse, store, develop, display, and transmit Commanders’ Critical Information Requirements (CCIR).

The current Marine Corps tactical workstation is the Tactical COP Workstation (TCW). TCW is composed of a window based laptop and JTCW software. JTCW is a suite of applications designed for Battalion and Above (BAA) that facilitates military C2 by improving SA and enhancing operational and tactical decision-making.

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

Command and Control Personal Computer (C2PC) is the core Government Off-The-Shelf

(GOTS) application for JTCW. When connected to a network, the C2PC exchanges positional tactical track data with Tactical Data Base Management (TDBM) found on the GCCS based servers, primarily the TCS, and provides a complete geographically based situational awareness capability, which includes the capability to display GCCS COP data.

In a stand-alone mode (not connected to a network), C2PC operators can produce operational graphics and input track data. Upon reconnection to a network, TDBM track data is synchronized with the TCS. With this electronic connectivity, C2PC becomes a powerful tool for the commander by providing a comprehensive CTP of the battlefield. JTCW combines

C2PC, C2PC Application Extensions (AEs), and a number of other tools into an integrated software load aimed at enhancing the overall system functionality. C2PC provides the basic

COP track and overlay interaction with the Global Command and Control System (GCCS) variants. It also provides the geographic map surface for plotting tracks, overlays, and other geo-located objects and it has Application Programming Interfaces (APIs) that enable JTCW AEs to use C2PC mapping, plotting, overlays, communications, address book, and route planning services.

Both GCCS-TCO and JTCW are Post-Milestone C, in the Operations and Support phase. Both

TCS and JTCW annually release software composed of enhancements to existing capabilities and software fixes.

1.2 Scope

This Performance Work Statement (PWS) defines the test & evaluation and engineering support services required by MCTSSA for the fulfillment of the GCCS-TCO/JTCW FoS project responsibilities. MCTSSA requires contractor support services for all aspects of testing and engineering to include but not limited to pre-test activities (test planning), test execution, post-test activities (analysis and reporting), engineering activities and meeting support. Pre-test activities include but it is not limited to: test planning, preparing test scripts and preparing the

GCCS-TCO/JTCW FoS Family of Systems (FoS) for test. Test execution includes but it is not limited to verification of GCCS-TCO/JTCW FoS functional and configuration, capturing raw data/data extraction, providing daily debriefs. Post-test activities include but it is not limited to:

data reduction and analysis, GCCS-TCO/JTCW FoS trouble reporting. Typically, there will be two test events per fiscal year with ongoing engineering evaluations of beta software. The

GCCS-TCO/JTCW FoS SME shall support ongoing trouble report engineering analysis for

MAGTF C2 PoRs and test events. Priority of tasking will be set by the JTCW Project Officer at

MCSC.

2 APPLICABLE DOCUMENTS

2.1 Compliance Documents

The following documents are applicable to this PWS to the extent specified herein:

a. MCTSSA Test Plan Template

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

b. MCTSSA Test Report Template

c. MCTSSA Daily Debrief Template

d. MCTSSA Technical Incident Report Template

2.2 Guidance Documents

The following documents are provided as guidance and may be helpful to the contractor in performing the work described in this PWS:

a. Joint Interoperability Test Command (JITC) Plan 3006 (current version).

3 PERFORMANCE REQUIREMENTS

The contractor shall provide subject matter experts to support test & evaluation, engineering support services, and deliverable products as required in this PWS. The contractor shall support formal testing activities (pre-test, conduct of test, and post-test), engineering evaluations, working groups, and engineering analysis of software trouble reports. The contractor shall support test events or activities requiring/involving the GCCS-TCO/JTCW FoS. For planning purposes, all GCCS-TCO/JTCW FoS testing is conducted within an operationally relevant

MAGTF architecture and uses scenario-based mission threads. Engineering evaluations include scenario-based mission threads and may be tailored to focus on more narrowly scoped functions or overall performance/stability measurements as directed by the Government.

3.1 Test Support

The contractor shall provide SMEs to plan, conduct, analyze, and report the results of test events in support of the GCCS-TCO/JTCW FoS Program Offices and provide technical input regarding these systems within the MAGTF C2 architecture. The contractor shall support all test & evaluation and engineering events in support of GCCS-TCO/JTCW FoS to include:

developmental test, operational test, Joint Interoperability and Certification Test (JICT) events, and engineering evaluations. The contractor shall support all phases of test to include test planning, test execution, post-test analysis, reporting and after action assessments. The contractor shall develop test documentation, including test architecture, test plans, test cases/scenarios, test procedures/scripts, test data collection plans, technical incident report (TIR), test trouble reports (TR), and test reports. The test plans, test cases/scenarios, and test procedures/scripts shall align with the MCTSSA provided templates listed in Section 2 above.

The contractor shall setup, configure and validate the GCCS-TCO/JTCW FoS test environment, troubleshoot, and correct any technical problems that may affect the conduct of test. During test execution, the contractor shall take notes on observed system performance, document any anomalies and apparent system failures, and provide a daily debrief regarding the outcome of the test. The contractor shall support post-test meetings to provide technical clarification to questions regarding the captured test results and provide recommendation for corrective action.

The contractor shall plan to support the following test events and approximate timelines for calendar year 2016.

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

Test Events Planning Execution Analysis Reporting

JTCW 1.1.8.0 DT 6 Weeks 3 Weeks 2 Weeks 3 Weeks

TCS 6.0 DT 6 Weeks 3 Weeks 2 Weeks 3 Weeks

C2PC 8.0.3.0

Government

Acceptance Test

6 Weeks 3 Weeks 2 Weeks 3 Weeks

JTCW 1.1.9.0 DT 6 Weeks 3 Weeks 2 Weeks 3 Weeks

3.2 Joint Certification Testing

The contractor shall provide technical support for joint certification testing led by the Joint

Interoperability Test Command (JITC). JITC is responsible for all test documentation during joint certification testing. The contractor shall provide technical support to include test architecture diagrams, test documentation review, requirements analysis, test setup and configuration, test operator support, and data collection.

MCTSSA anticipates 1 joint certification test event with approximate timelines.

Test Name Planning Execution Analysis Reporting

Joint Certification Test 4 Weeks 2 Weeks 1 Week 2 Weeks

3.3 Technical Support to MAGTF C2 Test/Engineering Events

The contractor shall provide SME to support MAGTF C2 test and engineering events for the

GCCS-TCO/JTCW FoS. The contractor shall setup and configure the GCCS-TCO/JTCW FoS for test within the MAGTF C2 architecture. The contractor shall troubleshoot the GCCS-

TCO/JTCW FoS to resolve any issues that may cause test delays and provide limited system operator support during test and engineering events. The contractor shall coordinate with the

Contracting Officer’s Representative (COR) to prioritize SME GCCS-TCO/JTCW FoS support to other MAGTF C2 test and engineering events. Historical data show an effort of approximately a ¼ man year during a 1-year period of performance for this support.

3.4 Working Group Participation

The contractor shall support working group meetings (such as the Test IPT and TRB) to provide technical input regarding GCCS-TCO/JTCW FoS, and provide recommendations to resolve technical issues identified during setup and test. The contractor may be required to conduct further analysis and provide a technical write-up. Historical data show an effort of approximately one hour supporting test IPTs on a weekly basis, and TRBs on a bi-weekly basis for two hours.

The contractor shall develop test and engineering evaluation documentation. The contractor may be required to draft technical white papers or to investigate and write up TRs. The contractor shall support working group meetings such as the weekly JTCW Test Integrated Product Teams

(IPTs) and TRBs. The contractor shall provide GCCS-TCO/JTCW FOS SME to support

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

MCTSSA based Programs of Record such as COC and the Tactical Service Oriented

Architecture (TSOA).

4 DELIVERABLES

Prior to the first submission of any deliverable, the contractor shall provide the COR a copy of the formatted deliverable for format approval, unless otherwise stated herein. All deliverable products scheduled are in calendar days unless otherwise specified in this PWS.

4.1 Monthly Status Report

The contractor shall prepare and deliver an electronic monthly status report on its test and engineering support activities. The report shall be delivered no later than the 10 th of each month following the reporting period. The report shall be delivered in current version of Microsoft

Office® Word or Excel in use by MCTSSA. The report shall be sent via e-mail to the COR and shall include, at a minimum, a description of the services provided and deliverables completed during the reporting period, a status of the efforts that are ongoing, any issues/concerns or problem areas, and planned or recommended solutions for alleviating the problem(s).

4.2 Technical Report

A Technical Report (PWS para 3.1, 3.2, 3.3, and 3.4) shall include:

a. Date(s) and location of the meeting, document review, or analytic effort (as applicable).

b. Identification of the meeting, document reviewed, or analysis performed.

c. Names of contractor and Government personnel participating, and contact information.

d. For a meeting: Summary of the subjects/information/tasks covered during the meeting, and the decisions, conclusions, direction or agreements reached by the participants, action items, and dates. Include recommendations to resolve remaining technical issues and areas requiring further analysis.

e. For a document review: Summary of the results and detailed description of technical discrepancies, errors, or omissions found in the document including a reference to the appropriate paragraph/topic, substantiations and recommendations for resolution or proposed changes.

f. For a technical write-up: Identification of the technical issue, results obtained for the analytic effort, conclusions, and recommended course(s) of action(s).

The contractor shall deliver a technical report within 7 days following meeting conclusion.

The contractor shall deliver a document review within 7 days after document receipt.

The contractor shall deliver technical write-ups per the established schedule.

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

The final version of any report is due 5 days after receipt of Government comments.

4.3 Test Plans

The contractor shall use the format and content preparation instructions of the latest test plan template provided by the Government (PWS para 2.1). The test plan shall also include:

a. Test case/scenario description – to include a summary description of the test case/scenario. For test scenario, the data flow for the test scenario shall be presented in a table format.

b. Requirements traceability matrix whereby all tests are traced to the applicable requirements demonstrated.

c. Identification of any allocated requirements not tested and the reason for not testing the requirement. All allocated requirements not tested shall be accounted for.

The draft test plan shall be delivered to the Government 15 days prior to test or engineering evaluation. A final test plan is due 7 days after receipt of Government comments unless a different schedule is agreed to between the COR and contractor due to the scope of required modifications.

4.4 Test Procedures

The test procedures and individual test scripts (PWS para 3.1) shall include:

a. Pre-test conditions requiring operator actions.

b. Pre-test conditions that must be present in the test environment.

c. Pre-test conditions for any datasets, files, or tools required for test execution.

d. By step and subsystem, operator actions called out, along with pass/fail criteria based on requirement(s) or feature(s) tested.

Test procedures and individual test scripts are due 10 days prior to a test or engineering evaluation. Modifications or redlines made to the test procedures during test execution are due

10 days following completion of the test.

4.5 Test Incident Reports

A Test Incident Report (TIR) PWS para 3.1 shall, at a minimum, include:

a. Date the TIR was generated.

b. Times system went down and back up.

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

c. TIR number.

d. Name of person generating the TIR.

e. Reference to procedure and steps within procedure executed when system error occurred.

f. Name of system error occurred on.

g. TIR problem title.

h. Detailed description of problem.

i. Provide steps to recreate or work-around if applicable or mark as anomalous behavior.

j. Provide screen shots when available.

k. Provide system status at time error occurred to include client and gateway status.

The contractor shall deliver TIRs within 2 working days of system error discovery, unless otherwise agreed upon by the Government.

The final version is due 2 days after receipt of Government comments.

4.6 Test Logs

The test logs (PWS para 3.2, 3.3, and 3.4) shall include:

a. Recorder name.

b. Date generated.

c. Test step #.

d. Test step status (pass, pass with exception, fail).

e. TIR references along with detailed notes of any anomalous system behaviors.

The contractor shall deliver test logs to the Government data collector at the end of each day of testing.

4.7 Test Reports

The contractor shall use the format and content preparation instructions of the test report template provided by the Government (PWS para 2.1).

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

The contractor shall deliver a draft test report is due within 10 days following the completion of the test. The final test report is due 10 days after receipt of Government comments unless a different schedule is agreed to between the COR and the contractor due to the scope of required modification.

4.8 Distribution Statement

The following statement regarding distribution shall appear on the cover or title page of all new and updated unclassified deliverable technical documents, data, and information (including engineering drawings, technical notes and manuals, test plans, test or technical reports, test procedures, and computer software documentation) whether produced in hard-copy or in digital format: “DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense and U.S. DoD contractors associated with the system(s) identified in this document; document contains technical, operational, or test and evaluation information (Jan 2012). Other requests for this document shall be referred to the Commanding Officer, Marine Corps Tactical Systems

Support Activity, Box 555171, Camp Pendleton, California 92055-5171.”

4.9 Delivery Instructions

Deliverables associated with the above specified tasks will be subject to the performance standards and acceptable quality levels specified in the Quality Assurance Surveillance Plan, Enclosure (1).

4.10 Unclassified End Products

Unclassified end products shall be delivered with a letter of transmittal to the COR.

4.11 Classified End Products

All classified material will be shipped or mailed in or out of the command via Federal Express or

United States Postal Service (USPS) registered mail. Material shipped out of the command will be shipped or mailed only by the CMCC custodian. Federal Express or USPS registered mail is the only approved methods of shipping classified material.

Classified material sent via Federal Express (FEDEX), will use the following address:

COMMANDING OFFICER

ATTENTION CMCC

MCTSSA

BLDG 31345 SUPPLY

CAMP PENDLETON, CA 92055-5171

Classified material sent via Registered Mail, will use the following address:

COMMANDING OFFICER

ATTENTION CMCC

BOX 555171

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

CAMP PENDLETON, CA 92055-5171

A copy of the letter of transmittal shall be forwarded to the COR. All classified documents shall be classified, handled, marked, transmitted, safeguarded, and controlled in accordance with the

National Industrial Security Program Operating Manual (NISPOM) (DOD Directive 5220.22-

M).

4.12 Schedule of Deliveries

The contractor shall provide a written request for all delivery schedule revisions at least seven

(7) days prior to the required delivery date, for Government evaluation and approval. All deliverable products are in calendar days unless otherwise specified and agreed to in advanced.

Revised delivery dates may only be authorized by issuance of a duly executed modification to the contract by the Contracting Officer.

5 PERFORMANCE LOCATION

Performance of work associated with this project will be performed primarily at MCTSSA. The contractor shall be expected to work on-site at MCTSSA 80% of the time and 20% offsite at the contractor’s facility. The contractor shall be required to travel in order to attend meetings and briefings.

6 INSPECTION OF DELIVERABLES

The COR will inspect all deliverables at the place of delivery (MCTSSA).

Inspection and acceptance of the contract deliverables are the responsibility of the COR, unless otherwise specified in the contract. The COR will make official acceptance notification to the contractor on all final deliverables via signature of acceptance. Rejection of deliverables will be provided to the contractor via written correspondence. Minor corrections required to deliverables will be verbally discussed with the contractor and noted on deliverable products. A revised deliverable shall be resubmitted to the Government within three days unless a different schedule is agreed to between the Government and contractor because of the scope of required modifications.

All deliverables shall be submitted to the COR in matching hard-copy and soft-copy formats and shall be clearly labeled to indicate content. All soft-copy deliverables shall be in the current version of Microsoft Office® suite of products in use by MCTSSA. In addition to the Microsoft

Office® soft-copy, all final deliverables shall be submitted in the current version of Adobe

Acrobat Professional (pdf) format in use by MCTSSA. The COR will approve any agreed to changes in deliverable formats in writing in advance of submission.

7 PERIOD OF PERFORMANCE

The period of performance for this task is anticipated to be one year in duration from date specified in the award, with three, one-year option periods.

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

8 GOVERNMENT FURNISHED EQUIPMENT AND

FACILITIES

8.1 Government Furnished Equipment

No Government Furnished Equipment will be provided.

8.2 Access to Government Property

No permanent office(s) will be provided under this PWS however, a designated work area for up to five personnel will be identified. Access to Government telephone services will be made available in the designated work area but is restricted to Government-contractor coordination and those calls necessary for the conduct of contractor business relevant to this PWS. All offsite calls shall be logged by the contractor.

Access to internet, photocopier, a Common Access Card (CAC) reader and the software, and the

JTCW software/hardware environment will be furnished by the Government for work directly in support of this PWS conducted at MCTSSA.

8.3 Access to Government Facilities

The Government will provide access to the required facilities and the test and evaluation labs located at MCTSSA as needed for the performance of the tasking within this PWS during normal working hours, 0700 to 1700, Monday through Friday. Any unclassified contractor-furnished laptops must be logged in and out with the laboratory entry control point sentry. Access to

MCTSSA facilities must be scheduled in advance at least one working day prior to access with the MCTSSA COR and Security Officer. The contractor must seek prior approval of the COR for access to MCTSSA during Government holidays.

8.4 Government Furnished Material

No Government Furnished Material will be provided under this PWS.

The contractor shall furnish its own computer equipment, administrative supplies, and office supplies, required for the performance of the tasking within this PWS.

The Government will not reimburse the contractor for cell phone charges under this PWS.

8.5 Government Furnished Information

The Government will provide the contractor access to the following information and automated services in support of this PWS:

a. The technical information required for the performance of the tasking within this PWS.

The contractor shall submit a written request at least two days in advance to the COR for specific information.

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

b. A user and email account on the NMCI to include a CAC card to support PKI access and Marine Corps Web Services when determined by the Government to be necessary for the performance of the tasking within this PWS, if qualified. Contractors are required to complete two classes before being issued an email account.

(1) DoD-IAA-V12.0 DoD Cyber Awareness Challenge V2

(2) DoD-PII-2.0 Privacy And Personally Identifiable Information (PII) Awareness

9 SECURITY REQUIREMENTS

9.1 Security Level

Technical tasks associated with the PWS require access to classified information and a security clearance up to the NATO SECRET level. The contractor shall not divulge any information regarding files, data, processing activities/functions, user ID’s, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information.

Contractor personnel shall abide by all Government rules, procedures, and standards of conduct.

9.2 DD Form 254

The work to be performed under this PWS as delineated in the DD Form 254, Attachment (2), involves access to the handling of classified material up to and including NATO Secret. The requirement of the clause FAR 52.204-2, Security Requirements is applicable to this order. The contractor shall: (1) be responsible for all security aspects of the work performed under this contract; and (2) assure compliance with the NISPOM (DOD Directive 5220.22-M).

Contracted personnel’s clearance shall be able to be confirmed in the Joint Personnel

Adjudication System (JPAS).

9.3 Security Clearance

A SECRET clearance with NATO access is required for test, analyst, technical, and engineering personnel supporting this PWS.

9.4 Base Security

Contractor shall comply with Marine Corps Base (MCB) Camp Pendleton, CA security regulations and policies. The contractor’s staff shall be U.S. or naturalized citizens, whose military duty was not terminated by a dishonorable or bad conduct discharge, who are not subject to an outstanding criminal warrant, have no felony conviction, and no more than three criminal misdemeanor convictions within the last seven years, and no criminal misdemeanor or felony conviction for crimes of a sexual nature, crimes of violence, crimes related to gang activity or hate crimes, or crimes resulting from the possession or distribution of any illegal drug.

All contractor personnel aboard MCB Camp Pendleton, CA, with the exception of emergency personnel, shall wear a properly issued badge at all times. Contractor employees shall comply

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015 with all emergency rules and procedures established for MCB Camp Pendleton, CA. All personnel aboard MCB Camp Pendleton, CA are subject to random inspections of their vehicles, personal items and of themselves. Consent to these inspections is considered to have been given when personnel enter MCB Camp Pendleton, CA.

9.5 OPSEC Requirements

The practice of operational security (OPSEC) prevents the inadvertent compromise of sensitive unclassified and classified activities, capabilities, or intentions at the tactical, operational, and strategic levels. The contractor’s staff must adhere to all Government OPSEC measures currently in place at the Government facility. The contractor shall provide OPSEC training to all contractor personnel supporting this effort.

10 PERSONNEL

The contractor shall provide GCCS-TCO/JTCW FoS Subject Matter Experts and GCCS-

TCO/JTCW FoS Operators in support of this effort. The contractor shall identify and provide resumes for SME and Operator personnel who have experience in performing tasks under this

PWS. Experience in testing TCS and JTCW 1.1.x. and experience as a tester or operator within

MAGTF C2 architecture are particularly valuable. No single individual is required to be an expert in all areas; however, individuals collectively shall be able to provide expertise across these areas. Contractor personnel shall be otherwise qualified to perform the work described herein.

If, due to an individual's inability to perform the role due to, e.g., illness, death, termination or employment, or for other reasons, the contractor needs to substitute a particular SME or

Operator, the substitute shall have the requisite skills necessary to ensure uninterrupted performance. The contractor shall provide the Contracting Officer with the substitution notification, including a resume for the proposed individual. Given that this is a Performance

Based Requirement, failure of the contractor to provide personnel with the requisite skills necessary to perform the contract may result in breach.

11 TRAVEL REQUIREMENTS

The contractor is authorized to travel to the locations listed below in support of this PWS when notified by the COR. If additional travel is required, the contract will be bilaterally modified and fully funded by the Contracting Officer. Authorized travel shall be in accordance with DoD

Joint Travel Regulations. Actual travel required will vary depending on the technical issues and schedules as they evolve throughout the period of performance.

PURPOSE LOCATION #PERSONNEL ESTIMATED TRIPS

GCCS_TCO_JTCW Charleston, SC 1 2

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

12 INVOICING

The contractor shall submit an electronic-copy of an invoice and any necessary supporting documentation not more often than once a month via Wide Area Workflow (WAWF).

The contractor shall be required to implement the DFARS process to submit an electronic payment request. To implement DFARS 252.232-7003, “Electronic Submission of Payment

Requests (March 2008)”, the United States Marine Corps (USMC) utilizes WAWF Receipts and

Acceptance (RA) to electronically process vendor requests for payment. This process allows

DoD vendors to submit and track Invoices and Receipt/Acceptance documents electronically.

The contractor shall be required to utilize this system when processing invoices and receiving reports. The contractor shall (i) ensure an Electronic Business Point of Contact is designated in

Central Contractor Registration at http://www.ccr.gov and (ii) register to use WAWF-RA at the https://wawf.eb.mil site, within ten (10) days after award of this contract or modification. Step by step procedures to register are available at the https://wawf.eb.mil site.

13 ADMINISTRATIVE AUTHORITY

13.1 Contracting Officer

Only the Contracting Officer has the authority to authorize deviations from the terms and conditions of this contract, including deviations from the specifications and requirements stated herein. In the event the contractor does deviate, without the issuance of a duly executed contract modification, such deviation shall be at the risk of, and any costs related thereto shall be borne by the contractor.

13.2 Contracting Officer Representative (COR)

Edith Radnoti at (760) 725-2093, edith.s.radnoti@usmc.mil, is the Contracting Officer’s

Representative (COR) for this contract. The COR is limited to providing program specific clarification to the contractor's Task Leader for this contract, and does not have the authority to take any action, either directly or indirectly, that would change the pricing, quality, place-of-performance, delivery schedule, or any other terms and conditions of this contract or to direct work that goes beyond the scope of this contract’s PWS. If the contractor perceives that the

COR or any other Government personnel is requesting an effort outside the existing scope of this contract, the contractor shall promptly notify the Contracting Officer in writing. No action shall be taken by the contractor under such direction until the Contracting Officer has issued a contractual change or otherwise resolved the issue. The Contracting Officer’s Representative will be appointed at the time of contract award. The Government reserves the right to reassign the COR position.

14 ORGANIZATIONAL CONFLICT OF INTEREST

(a) “Organizational Conflict of Interest” means that because of other activities or relationships with other persons, a person is unable or potentially unable to render impartial assistance or advice to the Government, or the person’s objectivity in performing the contract work is or might http://www.ccr.gov/ https://wawf.eb.mil/ https://wawf.eb.mil/

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015 be otherwise impaired, or a person has an unfair competitive advantage. “Person” as used herein includes Corporations, Partnerships, Joint Ventures, and other business enterprises.

(b) The contractor warrants that to the best of its knowledge and belief, and except as otherwise set forth in the contract, the contractor does not have any organizational conflict of interest(s) as defined in paragraph (a) above.

(c) It is recognized that the effort to be performed by the contractor under this contract may create a potential organizational conflict of interest on the instant contract or on a future acquisition. In order to avoid this potential conflict of interest, and at the same time to avoid prejudicing the best interest of the Government, the right of the contractor to participate in future procurement of equipment and/or services that are the subject of any work under this contract shall be limited as described below in accordance with the requirements of FAR 9.5.

(d) (1) The contractor agrees that it shall not release, disclose, or use in any way that would permit or result in disclosure to any party outside the Government any proprietary information provided to the contractor by the Government during or as a result of performance of this contract. Such information includes, but is not limited to, information submitted to the

Government on a confidential basis by other persons. Further, the prohibition against release of

Government provided information extends to cover such information whether or not in its original form, e.g. where the information has been included in contractor generated work or where it is discernible from materials incorporating or based upon such information. This prohibition shall not expire after a given period of time.

(d) (2) In accordance with DFAS 252.204-7000, the Contractor shall not release to anyone outside the Contractor’s organization any unclassified information, regardless of medium (e.g., film, tape, document), pertaining to any part of this contract or any program related to this contract, unless the Contracting Officer has given prior written approval.

(d) (3) The prohibitions contained in subparagraphs (d)(1) and (d)(2) shall apply with equal force to any affiliate of the contractor, any subcontractor, consultant, or employee of the contractor, any joint venture involving the contractor, any entity into or with which it may merge or affiliate, or any successor or assign of the contractor. The terms of paragraph (f) of this

Special Contract Requirement relating to notification shall apply to any release of information in contravention of this paragraph (d).

(e) The contractor further agrees that, during the performance of this contract and for a period of one year after completion of performance of this contract, the contractor, any affiliate of the contractor, any subcontractor, officers of the company participating in the contract, any joint venture involving the contractor, any entity into or with which it may subsequently merge or affiliate, or any other successor or assign of the contractor, shall not furnish to the United States

Government, either as a prime contractor or as a subcontractor, or as a consultant to a prime contractor or subcontractor, any system, component or services which is the subject of the work to be performed under this contract. This exclusion does not apply to any re-competition for those systems, components or services furnished pursuant to this contract. As provide in FAR

9.505-2, if the Government procures the system, component, or services on the basis of work

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015 statements growing out of the effort performed under this contract, from a source other than the contractor, subcontractor, affiliate, or assign of either, during the course of performance of this contract or before the one year period following completion of this contract has lapsed, the contractor may, with the authorization of the cognizant Contracting Officer, participate in a subsequent procurement for the same system, component, or service. In other words, the contractor may be authorized to compete for procurement(s) for systems, components or services subsequent to an intervening procurement.

(f) The contractor agrees that, if after award, it discovers an actual or potential organizational conflict of interest; it shall make immediate and full disclosure in writing to the Contracting

Officer. The notification shall include a description of the actual or potential organizational conflict of interest, a description of the action, which the contractor has taken or proposes to take to avoid, mitigate, or neutralize the conflict, and any other relevant information that would assist the Contracting Officer in making a determination on this matter. Notwithstanding this notification, the Government may terminate the contract for the convenience of the Government if determined to be in the best interest of the Government.

(g) Notwithstanding paragraph (f) above, if the contractor was aware, or should have been aware, of an organizational conflict of interest prior to the award of this contract or becomes, or should become, aware of an organizational conflict of interest after award of this contract and does not make an immediate and full disclosure in writing to the Contracting Officer, the

Government may terminate this contract for default.

(h) If the contractor takes any action prohibited by this requirement or fails to take action required by this requirement, the Government may terminate this contract for default.

(i) The Contracting Officer’s decision as to the existence or nonexistence of an actual or potential organizational conflict of interest shall be final and is not subject to the clause of this contract entitled “DISPUTES” (FAR 52.233-1).

(j) Nothing in this requirement is intended to prohibit or preclude the contractor form marketing or selling to the United States Government its product lines in existence on the effective date of this contract; nor, shall this requirement preclude the contractor from participating in research and development or delivering any design development model or prototype of any such equipment. Additionally, sale of catalog or standard commercial items are exempt from this requirement.

(k) The contractor shall promptly notify the Contracting Officer, in writing, if it has been tasked to evaluate or advise the Government concerning its own products or activities or those of a competitor in order to ensure proper safeguards exist to guarantee objectivity and to protect the

Government’s interest.

(l) The contractor shall include this requirement in subcontracts of any tier, which involve access to information, or situations/conditions covered by the preceding paragraphs, substituting

“subcontractor” for “contractor” where appropriate.

PWS GCCS, TCO and JTCW Testing and Engineering Support 7 October 2015

(m) The rights and remedies described herein shall not be exclusive and are in addition to other rights and remedies provided by law or elsewhere included in this contract.

(n) Compliance with this requirement is a material requirement of this contract.