Final_MC3T_PWS_28_Aug_2013_v2.pdf

Performance Work Statement For

Marine Air Ground Task Force (MAGTF), Command and Control Communication Computers and Intelligence (C4I)

System of Systems Technical Support Services

28 August 2013

Prepared by:

UNITED STATES MARINE CORPS

Marine Corps Tactical Systems Support Activity Current Operations

Camp Pendleton, CA 92055-5171 i

TABLE OF CONTENTS

1 INTRODUCTION

1.1 Background

1.2 Scope

2 APPLICABLE DOCUMENTS

2.1 Compliance Documents ................................................. Error! Bookmark not defined.

2.2 Guidance Documents

3 PERFORMANCE REQUIREMENTS

3.1 Technical and Engineering Support

Technical Studies and Analysis .................................................................................. 3 3.1.1

3.2 Test and Evaluation Support

Pre-Test Support ......................................................................................................... 4 3.2.1 Test Execution Support ............................................................................................... 4 3.2.2 Post-Test Support ........................................................................................................ 4 3.2.3

3.3 Document Reviews

4 DELIVERABLES

4.1 Monthly Status Report

4.2 Technical and Engineering Support Documentation

4.3 Test and Evaluation Products

Pre-Test Technical Reports ......................................................................................... 6 4.3.1 Post-Test Analysis Report........................................................................................... 6 4.3.2

4.4 Technical Reports

4.5 Distribution Statement

4.6 Delivery Instructions

4.7 Unclassified End Products

4.8 Classified End Products

4.9 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

10 PERSONNEL

11 TRAVEL REQUIREMENTS

12 INVOICING

13 ADMINISTRATIVE AUTHORITY

ii

13.1 Contracting Officer

13.2 Contracting Officer Representative (COR)

14 ORGANIZATIONAL CONFLICT OF INTEREST

PWS for MAGTF System of Systems Technical Support Services 28 Aug 2013

1 INTRODUCTION

1.1 Background

The Marine Corps Tactical Systems Support Activity (MCTSSA) is a subordinate command of the Marine Corps Systems Command (MARCORSYSCOM), providing test, engineering, and diverse technical support to MARCORSYSCOM and the Operating Forces. Under the direction of the Deputy Commander, Systems Engineering, Interoperability, Architectures, and Technology (DC SIAT), MCTSSA provides this technical support to the Commander, MARCORSYSCOM and Program Managers (PMs) in their mission to acquire and sustain Command, Control, Communications, Computers and Intelligence (C4I) capabilities for the Marine Corps at large.

On 8 November 2006, the Deputy Commander, Command, Control, Communications, Computers and Intelligence/Integration of MARCORSYSCOM (renamed DC SIAT) issued a memorandum launching efforts to develop and execute certification processes intended to assess the ability of the Marine Air Ground Task Force (MAGTF) C4I systems to interoperate within a System-of-Systems (SoS) context. Initial efforts in support of this requirement resulted in the development of preliminary MAGTF C4I Capability Certification Test (MC3T) processes and the subsequent execution of a MAGTF C4I SoS capability proof of concept test at MCTSSA in October 2007. Since that time, subsequent MC3T events were conducted in 2008 and 2009 and focused on the refinement of test processes and procedures. In retrospect, these past efforts confirmed that there is still much work to be done in this area to identify and address the technical challenges and inherent complexities related to MAGTF C4I SoS testing and certification.

Recent publication of Marine Corps Order (MCO) 3090.2, Policy for MAGTF Command and Control (C2) Integration and Interoperability (dated 23 Jan 2013) has re-emphasized and refocused Corps-wide emphasis on MAGTF SoS development, testing, and certification. MCO

3090.2 tasks the Commander, MARCORSYSCOM with: (1) establishing supporting processes to conduct joint interoperability certification and to ensure compliance with Net-Ready Key Performance Parameters (NR KPP) certification requirements for MAGTF C2 systems; (2) conducting on-going MAGTF SoS engineering analysis to develop and maintain the engineering documentation and architecture products on MAGTF C2 systems in support of top-level systems engineering and integration resource prioritization, and the development, synchronization, and testing of its constituent systems; and (3) establishing a Service-level end-to-end testing and certification process to ensure that MAGTF C2 systems capabilities and limitations are documented for the Operating Forces and are used in aligning acquisition activities.

As the organic test and engineering arm of MARCORSYSCOM, MCTSSA must be able to provide the requisite test and evaluation, engineering, and systems-specific subject matter expertise in support of MARCORSYSCOM. To this end, MCTSSA has a recurring demand for technical support services in the areas of technical studies and analysis, architecture development and analysis, mission thread developments and pre-test planning activities, test execution, post-test analysis, and test reporting. Generally, technical support services are required in technical areas relating to the engineering, test and evaluation (T&E) of MAGTF systems and SoS, and net-centric performance of MAGTF systems in various SoS implementations.

Historically, MCTSSA has served as the Marine Corps node on a variety of Joint certification test events to include Joint Interoperability Tests (JIT), Joint User Interoperability Communications Exercises (JUICE), and the Department of Defense Interoperability Communications Exercises (DICE). Each of these events is used to certify a System Under Test (SUT) within a Joint SoS architecture. When a Marine Corps system is a SUT for Joint certification, MCTSSA plans and executes Service Level Tests (SLT) prior to the Joint test/exercise. These SLT events serve as a risk mitigation approach to ensure that Marine Corps systems perform as intended during Joint certification. It is likely that a similar paradigm will be adopted for the test and certification activities discussed above in relation to MCO 3090.2.

MCTSSA has also been engaged in the planning, execution, and analysis associated with the MARCORSYSCOM-sponsored Virtual Rapid Prototyping Laboratory (VRPL) demonstration events. The Virtual Rapid Prototyping Laboratory (VRPL) is a Research and Development, Test and Evaluation (RDT&E) effort to integrate test enterprise that brings together MCTSSA and the Naval Warfare Centers to form a reconfigurable test environment to support MAGTF SoS testing. The VRPL RDT&E effort provides a means to assess the complex interactions and dependencies of MAGTF systems of systems, implementing the various systems and components of a MAGTF distributed across various test sites across the United States. VRPL’s RDT&E primary purpose is to conduct, effectively and affordably, rapid prototyping activities within a SoS environment and assist in the transition of new capabilities to Marine forces.

1.2 Scope

This Performance Work Statement (PWS) defines the non-personal technical, engineering, Research and Development, and Test and Evaluation support services required by MCTSSA for MAGTF C4I Systems of Systems (SoS), and net-centric performance of MAGTF systems in various SoS implementations; and support to MCTSSA’s on-going role related to MAGTF SoS testing (e.g. VRPL) and in its future role in support of the mandates presented in the current edition of MCO 3090.2. The technical, engineering and test and evaluation support services include but are not limited to: technical studies and analysis, architecture development and analysis, mission thread development and test planning, test execution, post-test analysis, and test reporting.

The Government will award a Firm Fixed Price (FFP) Indefinite Delivery Indefinite Quantity (IDIQ) contract. The Government will issue FFP Task Orders under the resulting IDIQ contract.

Performance Requirement 3.1 Technical and Engineering Support (TES) represent the Government’s guaranteed minimum for the Base Year and each Option Year that is exercised.

Performance Requirement 3.2-3.2.3 and 3.3 represents future support services which are to be negotiated and ordered by issuance of a FFP Task Orders when SoSTS Test and Evaluation, and Virtual Rapid Prototyping Laboratory (VRPL) RDT&E support is required.

2 APPLICABLE DOCUMENTS

2.1 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. Marine Corps Tactical Data Systems Reference guide, dtd Jan 2010

b. MAGTF C2 Integration and Interoperability (Marine Corps Order 3090.2)

c. Department of Defense Architecture Framework (DoDAF) V2.02

3 PERFORMANCE REQUIREMENTS

This Performance Work Statement (PWS) defines the non-personal technical, engineering, and testing and evaluation (T&E) support services required by MCTSSA in its on-going role related to MAGTF SoS testing and in its future role in support of the mandates presented in MCO

3090.2. Test and evaluation support shall include performance involving the planning and execution of interoperability certification testing, participation in planning and execution of MAGTF test and demonstration events (e.g. VRPL), data collection and analysis, and post-test event reporting. Additionally, the contractor shall provide technical and engineering support services in the areas of technical studies and analysis, architecture development and analysis, mission thread development, trade studies to evaluate software and hardware components, review and development of support documentation, and other technical reporting as required.

3.1 Technical and Engineering Support

The contractor shall provide Technical and Engineering support in conducting studies and analysis tasks relating to test and evaluation of MAGTF C4I SoS. Technical and Engineering support shall include the preparation and maintenance of technical and engineering products of varying complexity that serve as a foundation for SoS test and engineering efforts at MCTSSA.

TECHNICAL STUDIES AND ANALYSIS 3.1.1

The contractor shall develop Technical Studies and Analysis in support of MAGTF C4I System of Systems. The results of individual Technical Studies and Analysis tasks shall be captured in the form of specific deliverables listed under this PWS. The products to be produced and delivered to the COR include:

a. Trade Studies

b. Technical Staff Studies

c. Architecture Products (Fit for Purpose Views) describing Test Infrastructure and

Lab Facilities

d. Mission Threads (to include narrative descriptions, Fit for Purpose Architecture

Views, and measures and metrics for the mission thread.)

e. Documentation of Methodologies, Taxonomies, and Processes used in the development of Technical and Engineering products.

f. Engineering Handbooks/How To Guides

The format for each deliverable will be defined by the Government. Commercial best practices for document formats may be used if approved by the Government in advance of each study or analysis task.

3.2 Test and Evaluation Support

The contractor shall provide Test and Evaluation support and participate in the planning and execution of tests activities (pre-test, test, and post-test) in support of the MAGTF C4I SoS testing. The contractor shall support the design, development, and execution of test and evaluation activities to include: developing test plans, test cases/scenarios (based on approved mission threads/architectures), test procedures/scripts, and data collection and test data analysis.

The contractor shall provide similar test support for VRPL’s research development test and evaluation efforts and other formally scheduled MAGTF C4I SoS test events. The contractor shall perform data reductions and analysis, and document the findings/results for inclusion in a test/technical report.

PRE-TEST SUPPORT 3.2.1

The contractor shall provide technical support in pre-test planning, and shall develop and maintain test plans, test cases/scenarios, test procedures/scripts, and test data collection & analysis plans.

TEST EXECUTION SUPPORT 3.2.2

During testing, the contractor shall provide technical support in execution of test procedures & test scripts, data collection & data analysis, and support preparation of materials to be included in related technical reports. The contractor shall attend Pre-Test Briefs and Post-Test Debriefs associated with the tests supported by the contractor. In addition, the contractor shall attend Technical Review Boards at the conclusion of the data analysis cycle in order to provide technical clarification of any questions regarding test conduct and results.

POST-TEST SUPPORT 3.2.3

The contractor shall provide technical support with the data reduction and analysis process, including analysis of data extraction files, Program Change reports (PCR), Test Incident Reports (TIR), and Preliminary Trouble Reports (PTR) in order to validate observed performance characteristics. At the conclusion of each test, the contractor shall assist in the evaluation of any technical issues related to the operation of the SoS or specific System Under Test (SUT). The contractor shall assist in the preparation of final test reports as required.

3.3 Document Reviews

The contractor shall review, analyze, and provide written comments on Test and Evaluation documentation. The types of documentation shall include but not be limited to technical studies, system performance and requirement specifications, interface and design documents, version description documents, system manuals, engineering and interface change proposals, test plans, procedures, and reports. The contractor shall document the results of each review in a Technical Report. The contractor may also be required to support the development and writing of test specific documents that includes, but is not limited to, test plans, test reports, mission threads, test cases, and related architecture products.

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. The reports shall be delivered in the current version of Microsoft® Office Suite in use by MCTSSA.

4.1 Monthly Status Report

The Contractor shall prepare and deliver an electronic monthly status report on its MAGTF C4I System of Systems Technical support activities. The report shall be delivered no later than the 10th of each month for the previous month. The monthly report shall be sent via e-mail to the MAGTF C4I System of System Capability Contracting Officer Representative (COR) and shall include, at a minimum, a description of support provided during the reporting period, a listing of events that have been completed, status of the efforts that are ongoing, and the number of man hours spent per event.

4.2 Technical and Engineering Support Documentation

The MAGTF C4I System of System Capability, Technical and Engineering products produced shall be delivered to the COR in the latest MCTSSA provided and approved templates. For reports that MCTSSA does not have an available template, the reports or products shall be delivered to the COR in accordance with Commercial Best Practices. Below is a list of expected products to be delivered as required to the COR:

a. Architecture Products – Fit for Purpose Views

b. Trade Studies

c. Technical Staff Studies

d. Evaluation Plans

e. Data Collection Plans

f. Mission Threads developed shall include Architecture Products, methodology, documentation defining the methodology, and measures and metrics for the mission thread

g. Planning documents including Test Plans and Procedures

h. Test architecture design, configuration documents and other Department of Defense

Architecture Framework (DODAF V2.02) products, Fit for Purpose Views

i. Test Cases based upon approved Mission Threads and Architectures

A draft deliverable is due to the COR per the established due dates. The final deliverable is due five (5) working 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.3 Test and Evaluation Products

Technical documentation for Test and Evaluation products include Test Plans, Test Cases/Scenarios, Test Process, Test Procedures, Test Scripts, Data Collection and Extraction, and Data Analysis technical reports.

PRE-TEST TECHNICAL REPORTS 4.3.1

Test Plans will be submitted to the COR in the MCTSSA provided and approved templates. All test plans include a draft test plan due twenty (20) working days prior to the start of a test and a final test plan due five (5) working 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.

The test procedures and individual test scripts will be submitted to the COR in the MCTSSA provided and approved templates and shall include at a minimum:

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 ten (10) working days prior to the start of a test or dry-runs depending upon the event schedule. Modifications or redlines made to the test procedures during test execution are due five (5) working days following completion of the test.

POST-TEST ANALYSIS REPORT 4.3.2

The post-test analysis report shall include:

a. Known assumptions and constraints with the system, software, equipment, or tool(s) used in support of the post-test analysis.

b. Results of data verification, reduction, and analysis and a discussion of them, including a summary of the most important findings. If any data was excluded from the analysis due to collection errors, bias, or other cases, the rationale should be given.

c. Results of TIR, PCR, and PTR analysis. Include recommendations on each TIR, PCR, or PTR assigned an operational impact rating in accordance with JITC guidance.

d. All Test Incident Reports (TIR).

e. Evaluation results for any technical issue related to the SUT.

A draft post-test analysis report is due fifteen (15) working days after completion of the test. A final post-test analysis report is due five (5) working 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 Technical Reports

Technical Reports shall be submitted in the MCTSSA provided and approved templates and include:

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

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

c. Names of contractor and Government personnel participating.

d. 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.

e. 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 technical issues and areas requiring further analysis.

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).

For a document review, the contractor shall deliver a technical report within ten (10) working days after document receipt.

For a technical write-up, the contractor shall deliver a technical report within five (5) working days following analysis completion.

4.5 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 that is For Official Use Only (August 2010). 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.6 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 (QASP), Enclosure (1).

4.7 Unclassified End Products

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

4.8 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

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 5220.22-M.

4.9 Schedule of Deliveries

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

(7) calendar days prior to the required delivery date for Government evaluation and approval.

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, Camp Pendleton. The contractor shall be required to travel in order to attend meetings, briefings, and joint test events as required. The contractor shall be expected to work 95% on-site at MCTSSA and 5% off-site due to travel requirements.

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 (3) working days unless a different schedule is agreed to between the Government and contractor due to 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. The COR will approve in writing any agreed to changes in deliverable formats in advance of submission.

7 PERIOD OF PERFORMANCE

The period of performance for this task is anticipated to be one (1) base year in duration from date specified in the award, with three (3) option years.

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 the respective contractor’s personnel will be provided. Access to Government telephone services will be made available in the designated work area but restricted to Government-contractor coordination and those necessary for the conduct of contractor business relevant to this PWS.

All offsite calls shall be logged by the contractor and provided to the COR monthly.

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 with the laboratory entry control point sentry. Access to MCTSSA facilities must be scheduled in advance at least one (1) 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 including photocopier 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 (2) calendar days in advance to the COR for specific information.

b. A user and email account on the NMCI to include a CAC card to support Public Key Infrastructure (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 required.

c. A user and mail account on the MCTSSA SECRET Internet Protocol Network (SIPRNet) domain when determined by the Government to be necessary for the performance of the tasking within this PWS.

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 IDs, 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 fully adjudicated SECRET clearance with NATO access is required for 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; not be subject to an outstanding criminal warrant, have any felony conviction, or more than three criminal misdemeanor convictions within the last seven years; and have 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 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.

10 PERSONNEL

The contractor shall identify key personnel who are qualified to perform the work described in this PWS, and submit resumes for government approval. Key personnel performing tasks under this PWS shall have current technical experience and expertise configuring, employment, testing and evaluating Marine Corps Command, Control, Communications, Computers and Intelligence (C4I) systems of systems, to include: Marine Corps C4I architecture and employment, system of systems testing, distributed joint testing, and shall be otherwise qualified to perform the work described herein.

The contractor shall provide resume(s) for all key personnel. Key personnel include the Program Manager, Systems Analyst and Test Analyst.

Key personnel shall be otherwise qualified to perform the work described in this PWS, and shall not be substituted without the permission of the Contracting Officer. During the term of the contract performance, no personnel substitutions will be permitted unless such substitutions are necessitated by an individual’s sudden illness, death, or termination of employment. Request for approval of substitutions shall be made in writing with a detailed explanation of the circumstances along with a resume of the proposed individual. Proposed substitutions shall at a minimum have the equivalent qualifications of the person being replaced.

11 TRAVEL REQUIREMENTS

The contractor may be required, and is authorized to travel in support of this PWS when notified by the COR for each year (base + option years). If additional travel is required, the contract will be bilaterally modified and fully funded by the Contracting Officer. Any required travel in support of this PWS is within the Continental United States (CONUS). 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.

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-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) calendar 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)

Mr. Jorge Medina at (760) 725-2159, jorge.medina@usmc.mil, is the Contracting Officer’s designated 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 http://www.ccr.gov/ https://wawf.eb.mil/ https://wawf.eb.mil/

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 Government reserves the right to reassign the designated COR of this contract at any time.

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 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).

(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) 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 information generated or derived during or as a result of performance of this contract. This prohibition shall expire after a period of one year after completion of performance on this contract.

(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 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 ward 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.

(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.

3.3 Document Reviews

14 ORGANIZATIONAL CONFLICT OF INTEREST