Final_PWS_COC_Integration_Support_17_Nov_2014.pdf

Performance Work Statement for

Combat Operations Center (COC) Integration Support

17 November 2014

Prepared by:

UNITED STATES MARINE CORPS

Marine Corps Tactical Systems Support Activity

Program & Engineering Support Group

Command and Control Systems Engineering Branch

Camp Pendleton, CA 92055-5171

PWS for COC Integration Support 17 Nov 2014

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 Document Reviews

3.2 Meeting Support

3.3 Test Support

3.4 Product Assessments

3.5 Help Desk Support

4 DELIVERABLES

4.1 Monthly Status Report

4.2 Test/Assessment Plan

4.3 Test/Assessment Procedures

4.4 Test/Assessment Report

4.5 Technical Report

4.6 Distribution Statement

4.7 Delivery Instructions

4.8 Unclassified End Products

4.9 Classified End Products

4.10 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

13.2 Contracting Officer Representative (COR)

14 ORANIZATIONAL CONFLICT OF INTEREST

1 INTRODUCTION

1.1 Background

The Marine Corps Tactical Systems Support Activity (MCTSSA) provides technical and engineering support services to the Marine Corps Systems Command (MCSC). MCTSSA’s

Program & Engineering Support Group (PESG) Command and Control (C2) Domain directly supports the efforts undertaken primarily by MCSC’s Program Manager for Marine Air-Ground

Task Force (MAGTF) Command, Control and Communications (PM MC3). The most active effort within the C2 Domain is the support provided to the Combat Operations Center (COC) program, which involves supporting the currently fielded versions of the COC and the C2 applications that reside within the COC, as well as the development of a new C2 infrastructural model based on a Services Oriented Architecture (SOA).

1.2 Scope

This Performance Work Statement (PWS) defines the technical, network engineering, and test and evaluation support services required by MCTSSA for the fulfillment of the Combat

Operations Center (COC) project responsibilities related to the integration and testing of

Commercial-Off-The-Shelf (COTS) and Government-Off-The-Shelf (GOTS) products in the current fielded COC.

2 APPLICABLE DOCUMENTS

2.1 Compliance Documents

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

a. Operational Requirements Document for the Combat Operations Center, Change 7, dtd

May 25, 2005.

b. System/Subsystem Specification (SSS) for the Combat Operations Center (COC)

AN/TSQ-239 (V) F-Series Build, dtd 1 November 2010.

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. Current MCTSSA Formatting Guidance

b. Current MCTSSA QA Review Process

c. Current MCTSSA Test Plan Template

d. Current MCTSSA Test Report Template

e. Current MCTSSA Quick Look Template

3 PERFORMANCE REQUIREMENTS

The Contractor shall provide information technology, network engineering support services and participate in the integration and testing of COC Commercial-Off-The-Shelf (COTS) and

Government-Off-The-Shelf (GOTS) products. The contractor shall evaluate the integration of

COTS and GOTS products in the COC software build process. The contractor shall document the results of the evaluation in a draft Technical Report.

The Contractor shall provide the services of professionals experienced in information technology and network engineering, computer network design efforts utilizing Virtualization Software, Voice over Internet Protocol (VoIP) Solutions, Information Assurance Laboratory and Team

Developments, as well as Network/Software Design.

The Contractor shall provide the services of professionals experienced in the integration of

Marine Corps Command Control Communications and Computers (C4) tactical data systems.

The systems the Contractor will be expected to support include, but are not limited to:

a. Combat Operations Center (COC)

b. Command Post of the Future (CPoF)

c. Command and Control Personal Computer (C2PC)

d. Joint Tactical Common Workstation (JTCW)

e. Advanced Field Artillery Tactical Data System (AFATDS)

f. Effects Management Tool (EMT)

g. MarineLink

The Contractor shall provide the services of network professionals experienced in the following commercial applications: Windows OS 2000/XP/98/Vista/Win7/Win8, Storage Area Networks

Solutions/Design, Windows Server 2000/2003/2008/2010, Network Attached Storage

Solutions/Design, Microsoft Office XP/2003/2007, Exchange 2000/2003, Linux and Unix, Network Engineering/Optimization, Wireless Networks Design, Enterprise Networks, iSCSI

Implementation, VMWare, SolarWinds.

3.1 Document Reviews

The contractor shall review, analyze, and provide written comments on COC program documentation to determine technical currency, identify issues that may impact COTS or GOTS integration, and ensure that technical content satisfies the requirements identified in the

Capabilities Development Document (CDD). The types of documentation to be reviewed include but are not 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, test procedures, and test reports. The contractor shall document the results of each review in a draft Technical Report. The contractor shall provide recommendation for updating COC documentation.

3.2 Meeting Support

The contractor shall participate in COC meetings such as Program Management Reviews, Working Groups, Configuration Control Boards, In-Progress Reviews, Technical Interchange

Meetings, demonstrations, voice teleconferences, and planning sessions as required, provide technical input regarding integration considerations and make recommendations to resolve related issues. The Contractor may be required to conduct further analysis and provide a technical write-up in a Technical Report.

3.3 Test Support

The contractor shall participate in test events in support of the COC program office and provide technical input regarding the integration of COTS and GOTS products. Test events may include, but not be limited to: integration, development, operational, interoperability and certification events. The contractor shall participate in all phases of test event, to include: pre-test planning, preparation, test execution, post-test analysis, and after action assessments. The contractor shall assist in the development of test documentation including test plans, test cases/scenarios, test procedures/scripts, test data, test incident/problem reports, and test reports. The contractor shall assist in the setup and configuration of the assessment environment and troubleshoot technical problems.

3.4 Product Assessments

The contractor shall review, analyze, and provide written comments on COTS or GOTS products under consideration by the COC program office for inclusion in the COC baseline in order to determine their suitability for satisfying operational requirements, capability gaps, or deficiencies. The contractor shall assist in the preparation and review of the assessment plans, assessment scenarios, and procedures/scripts. The contractor shall assist in the setup and configuration of the assessment environment and troubleshoot technical problems. The contractor shall assist in documenting the results of each assessment in a Technical Report. The contractor shall assist in updating COC documentation should the assessed product be adopted.

3.5 Help Desk Support

MCTSSA maintains a help desk service to the Marine Operating Forces. Occasionally, trouble calls are beyond the capabilities of the personnel that man the help desk. In such cases, the appropriate program support team will investigate the problem and attempt to identify a working solution. If the nature of the trouble call deems it appropriate, the Contractor shall participate in efforts related to resolving help desk support requests for the currently fielded COC system. The amount of time expected to be expended on Help Desk support is approximately 5% of the total.

4 DELIVERABLES

Prior to the first submission of any deliverable, the contractor shall provide the Contracting

Officer’s Representative (COR) a copy of the formatted deliverable for format approval, unless otherwise stated herein.

4.1 Monthly Status Report

The contractor shall prepare and deliver an electronic Monthly Status Report on its integration support activities. The report shall be delivered no later than the 10 th day of each month. The report shall be delivered in the current version of Microsoft Office® Word in use by MCTSSA.

The Monthly Status Report shall be sent via e-mail to the COR and shall include, at a minimum, a description of support provided during the reporting period - a listing of events that have been completed and a status of the efforts that are ongoing.

4.2 Test/Assessment Plan

The contractor shall use the format and content preparation instructions of the draft test plan template provided by the Government. The test/assessment plan shall:

a. Define and describe the product under test/assessment and the objectives of the event.

b. Define and describe when, how, and by whom specific activities are to be performed, including options and alternatives, as applicable. Include all tasks which support these activities. The level of detail shall be sufficient to define the appropriate activities in all phases of the event.

c. Define and describe the specific environment of the event.

d. Define and describe the specific standards, methods/techniques, tools, actions, strategies, and responsibilities required to support the event.

e. Identify and define any risks to the event, the degree of exposure to the risk, and the impact the risk presents to the product, event, personnel and/or the COC program as a whole.

f. Include the content defined by the draft test plan template provided by the Government.

If any information item is not relevant to either the product under test/assessment or to the event itself, that item is not required.

4.3 Test/Assessment Procedures

The draft test/assessment procedures shall include:

a. Pre-test/assessment conditions requiring operator actions.

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

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

d. By step and subsystem, operator actions called out, along with pass/fail criteria based on requirements tests or features demonstrated.

The draft test/assessment procedures are due the established due dates. Modifications or redlines made to the procedures during the test or assessment are due three (3) working days following the completion of the test or assessment.

4.4 Test/Assessment Report

The contractor shall use the format and content preparation instructions of the test report template provided by the Government. The test/assessment report shall:

a. Define and describe the product under test/assessment and the objectives of the event.

b. Define and describe the specific environment of the event.

c. Describe the specific activities performed and explain related observations.

d. Define and describe any deviations from the Test/Assessment Plan and the cause of the deviation. Explain what, if any, impact the deviation had on the event and related objectives.

e. Define to what degree the objectives were met. If an objective was not met, identify the contributing factors and the impact on the test.

f. Provide conclusions or statements of fact that are supportable by the test/assessment observations and/or data.

g. Provide recommendations as appropriate.

h. Include the content defined by the test report template provided by the Government. If any information item is not relevant to either the product under test/assessment or to the event itself, that item is not required.

A draft test report is due per the established due dates. The final is due three (3) 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.5 Technical Report

The Technical Report shall include:

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

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

c. Names of contractor and Government personnel participating, agency they represent and the role they held.

d. For a meeting: Summary of the subjects/information/tasks covered during the demonstration or 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 four (4) working days following demonstration or meeting conclusion. The contractor shall deliver a document review within ten

(10) working days after document receipt. The contractor shall deliver technical write-ups within five (5) working days following analysis completion. The final is due three (3) working days after receipt of Government comments.

4.6 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 C: Distribution authorized to U.S. Government agencies and their contractors (Critical Technology). Other requests for this document shall be referred to the

Marine Corps Tactical Systems Support Activity, COC Program Support Office.”

4.7 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.8 Unclassified End Products

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

4.9 Classified End Products

Classified end products shall be delivered directly to the MCTSSA, ATTN Classified Material

Control Center (CMCC), MCTSSA, Box 555171, Camp Pendleton, CA 92055-5171, using normal security channels. 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 NISPOM (DOD Directive 5220.22-M).

4.10 Schedule of Deliveries

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

(5) working days prior to the required delivery date, for Government evaluation and approval.

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

5 PERFORMANCE LOCATION

Performance of work associated with sustaining the currently fielded COC will be performed primarily at MCTSSA, Camp Pendleton. The Contractor shall be expected to work on-site at

MCTSSA, Camp Pendleton, approximately 100% of the time. The contractor may be requested to travel within and outside of the United States in order to support the currently fielded COC program effort.

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. In addition to the Microsoft

Office® soft-copy, all final deliverables shall be submitted in Adobe Acrobat 8 Professional

(pdf) format. 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) year in duration from the date specified in the award, with three (3), one-year option periods. The period of performance may be restructured to meet the needs of the Government.

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 will be appointed. 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.

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

COC program 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 labs located at MCTSSA 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 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) working days in advance to the COR for specific information.

b. A user and email account on the NMCI to include a Common Access Card (CAC) to support PKI access and Marine Corps Web Services when determined by the

Government to be necessary for work completion, if qualified.

c. A user and mail account on the MCTSSA SIPRNET domain when determined by the

Government to be necessary for work completion.

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 order as delineated in the DD Form 254, Attachment (2), involves access to the handling of classified material up to and including 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 the 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 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 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

Key personnel performing tasks under this PWS shall have at least five (5) years of professional experience and expertise in work related to Command Control Communications and Computers

(C4) systems integration, and shall be otherwise qualified to perform the work described herein.

The contractor shall provide resume(s) for key personnel.

Key personnel 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 performing under this PWS may be required and 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 so modified 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

Test and

Evaluation

Activities

Will vary depending on COC Test and

Evaluation activities, but locations will include General Dynamics C4 Systems, SPAWAR Atlantic and Marine Corps bases/installations located both CONUS and OCONUS.

1-3 Six (6) (five to ten

(5-10) working days each)

Helpdesk

Support

Will vary depending on support requested, but locations will include but are not limited to MITSCs and Marine Corps bases/installations located both CONUS and OCONUS.

1-3 Five (5) (five to ten

(5-10) working days each)

12 INVOICING

The contractor shall submit an electronic-copy of an invoice 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 2007)”, 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) working 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)

The contractor will receive taskings only through the COR and not directly from other individuals at MCTSSA. 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 ORANIZATIONAL 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.