Final_PWS_PT2E_8_July_2014.pdf

Performance Work Statement for

Professional Technical Test & Evaluation (PT E)

Documentation Support Services (DSS)

8 July 2014

Prepared by:

UNITED STATES MARINE CORPS

Marine Corps Tactical Systems Support Activity

Program Engineering Support Group

Camp Pendleton, CA 92055-5171

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 PT

E Documentation Support Services

3.2 Integrated Master Schedule Support

3.3 Document Reviews

3.4 Meeting Support

4 DELIVERABLES

4.1 Monthly Status Report

4.2 Technical Test & Evaluation Documentation

4.3 Test Plan

4.4 Test Report

4.5 Quick Look Report

4.6 Technical Reports

4.7 Distribution Statement

4.8 Delivery Instructions

4.9 Unclassified End Products

4.10 Classified End Products

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

PWS for Technical Engineering Support 8 July 2014

14 ORANIZATIONAL CONFLICT OF INTEREST

PWS for Technical Engineering Support 8 July 2014

1 INTRODUCTION

1.1 Background

The Marine Corps Tactical Systems Support Activity (MCTSSA) provides test, evaluation, and technical support services to Marine Corps Systems Command (MCSC) for the Systems

Interoperability Architectures and Technology (SIAT) Directorate. SIAT’s mission is to ensure delivery and sustainment of an integrated Enterprise Command, Control, Communications, and

Computers Intelligence Surveillance Reconnaissance (C4ISR) capability to the operating forces and supporting establishments. MCTSSA is responsible for integration testing, interoperability assessment and overall evaluation of Command and Control (C2) Systems/Program’s of Record

(PORs) as they evolve through the acquisitions lifecycle. These C2 Systems/PORs form the foundation of the Marine Corps net-centric operational focus and are vital to the Marine Corps’ continued success.

The Program Engineering Support Group (PESG) and the Test & Certification Group (T&CG) are responsible for providing test and evaluation support to MCSC. PESG and T&CG require the services of technical personnel experienced in preparing and editing technical documents such as plans, specifications, design descriptions, end-user guides etc., and test documentation such as test plans, test procedures, quick-look reports, and test reports to support the C4 systems below.

a. Advanced Field Artillery Tactical Data Systems (AFATDS)

b. Joint Battle Command Platform (JBC-P) Family of Systems (FoS)

c. Combat Operational Center (COC)

d. Common Aviation Command and Control System (CAC2S)

e. Data Distribution System Modular (DDS-M)

f. Digital Technical Control (USMC

g. Digital Wideband Terrestrial Radios (TRC-170, MRC-142)

h. Network On The Move (NOTM)

i. Global Broadcast System (GBS)

j. Tactical COP (Common Operational Picture) Server (TCS)

k. Tactical COP (Common Operational Picture) Workstation (TCW)

l. Joint Enhanced Core Communications Suite (JECCS)

m. JTCW/Command and Control Personal Computer (C2PC) software

n. Lightweight Multi-band Satellite Terminal (LMST)

o. Marine Air Command and Control Systems (MACCS) Family of Systems (FoS)

p. Marine Corps Common Hardware Suite (MCHS)

q. System Planning, Engineering and Evaluation Device (SPEED)

r. Tactical Collaborative Workstation Suite (TCWS)

s. Tactical Operations Center Inter Communications System (TOCNET)

t. Tactical Radios (e.g., EPLRS, PRC-117F/G, PRC-150, PRC-152, etc.)

u. Theater Medical Information Program (TMIP)

v. Transition Switch Module (TSM)

w. Target Location Designator Handoff System (TLDHS)

PWS for Technical Engineering Support 8 July 2014

x. Wireless Point-to-Point Link (WPPL)

y. VSAT/Support Wide Area Network, Family of Systems (FoS)

z. SENSORS AN/TPS-59, AN/TPS-63

aa. Composite Tracking Network (CTN)

bb. Ground Air Task Order Radar (GATOR)

cc. Tactical Service Oriented Architecture (TSOA)

dd. Global Combat Support System-Marine Corps (GCSS-MC)

1.2 Scope

This Performance Work Statement (PWS) defines the Professional Technical Test & Evaluation

(PT

E) Documentation Support Services (DSS) required by MCTSSA for developing professional documentation and developing and maintaining the Integrated Master Schedule

(IMS). The contractor shall provide professionally developed technical documents and reports derived from rough drafted technical test & evaluation events. The documents and reports to be developed include but are not limited to:

a. Test Plans;

b. Test Reports;

c. Test Procedures;

d. Quick Look Reports;

e. Technical templates;

f. Standard Operating Procedures;

g. Concepts of Operations;

h. Style Guides;

i. Training material;

j. Processes;

The contractor shall provide support with the development of the Integrated Master Schedule to ensure proper tracking of Government resources and workload balancing.

2 APPLICABLE DOCUMENTS

2.1 Compliance Documents

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

a. American National Standards Institute (ANSI), Z39.18-2005, Scientific and Technical

Reports – Preparation, Presentation, and Preservation

b. Department of the Navy, Correspondence Manual, SECNAV M-5216.5, March 2010

c. Government Printing Office (GPO) Style Guides

d. Marine Corps Order 3070.02A, Operational Security (OPSEC)

e. MCTSSA, Activity Order 5205.1, Operational Security (OPSEC) dated 4 January 2014

PWS for Technical Engineering Support 8 July 2014

2.2 Guidance Documents

The following documents are provided to assist 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

3.1 PT

E Documentation Support Services

The contractor shall provide professionally developed documents and reports, and prepare, revise, edit, format, and maintain technical documents and test documents in support of

MCTSSA C4I efforts. The contractor shall support MCTSSA with documenting, planning, and implementing activities related to processes, engineering, and test documents, including version control, configuration management, and quality assurance. All documents and reports shall be grammatically correct and shall be formatted according to the established templates. The contractor shall provide draft and final versions of processes, technical plans, specifications, test plans, test procedures, test reports, quick look reports, and other technical-related documentation.

The contractor shall research, collect, analyze source material, and observe technical processes in order to write and edit technical documents. The contractor may develop and integrate graphics with deliverable documents. The contractor shall ensure final technical documents adhere to the established formats and Government provided templates; are clearly written; contain correct spelling, grammar, punctuation, and style; and have consistency in acronym definition. The contractor shall maintain a schedule of technical test & evaluation documentation outstanding and due government dates.

The contractor shall provide professionally developed technical test & evaluation documents and reports to include Test Plans, Test Reports, Test Procedures, Quick Look reports, Test

Templates, Standard Operating Procedure, Concepts of Operation, Point Papers, and Daily

Reports in support of C4I project/programs engineering and test events. These technical test & evaluation documents vary in complexity and number of pages. For planning purpose, the government anticipates approximately sixty (60) technical test & evaluation documents/reports in FY15. The number of technical test & evaluation reports is not limited to the number or type shown on the table below:

PWS for Technical Engineering Support 8 July 2014

Report Types Estimated Number of Reports

Test Plan 12

Test Report 12

Test Procedure 7

Quick Look 7

Template 2

Standard Operating Procedure (SOP) 4

Concepts of Operation 6

Style Guides 4

Daily Report/Debrief As Required per meeting or test observation

A Test Plan is a document that formally describes test scenarios, objectives, Measures of

Effectiveness, detailed resources, coordination, test limitations, and the methods for gathering, reducing, and analyzing data.

A Test Report is a document that formally reports the results, conclusions, and recommendations resulting from each phase of testing.

A Test Procedures report is a standardized and documented process for performing an experiment or conducting an evaluation.

A Quick Look Report is a document that provides an informal, accelerated written assessment.

A Template is a document that provides a written pattern and serves as a guide tailored to fit the individual event that the guide is supporting.

A Standard Operating Procedure is a document that provides written procedures for repetitive use, in order to synchronize effort and achieve a desired outcome.

A Concept of Operation is a document describing the characteristics of a proposed system from the viewpoint of an individual who will operate the system. It is useful for communicating the quantitative and qualitative system characteristics to all stakeholders.

A style guide is a set of standards for the writing and design of documents, either for general use or for a specific publication, organization or field. The implementation of a style guide provides uniformity in style and formatting within a document and across multiple documents.

A Daily Report is a document that captures the events discussed and actions assigned during periodic meetings.

3.2 Integrated Master Schedule Support

The contractor shall support the Operations Directorate with developing the command’s

Integrated Master Schedule. The IMS is a tool for capturing workload activities to include resource loading and reporting to higher headquarters. The contractor shall develop the IMS utilizing Microsoft Project, conduct critical path analysis, perform schedule resource loading, http://en.wikipedia.org/wiki/System http://en.wikipedia.org/wiki/Stakeholder_(corporate)

PWS for Technical Engineering Support 8 July 2014 develop and present schedule roll-ups, demonstrate familiarity with DoD acquisition lifecycles, and demonstrate the ability to interface group data to obtain schedule status. The contractor shall perform other general program management activities (i.e., briefing construction, documentation, meeting facilitation, etc.) as required. The contractor shall be an independent critical thinker capable of working autonomously and possessing effective communication and collaboration skills. The contractor shall coordinate with the MCTSSA Group leadership to organize workload information/resource data into an Integrated Master Schedule.

The contractor shall provide specialized Microsoft Project planning and scheduling expertise and be capable of supporting multiple projects. This will entail concurrently creating, updating, and maintaining the MS Project Integrated Master Schedule for overall MCTSSA management. The contractor shall participate and work in a team environment with multiple participants. The contractor shall analyze multiple project schedules and determine gaps, overlaps, and integration points.

3.3 Document Reviews

The contractor shall: review and analyze technical test & evaluation documentation for clarity;

confirm that content is appropriate based on its intended use; review overall organization and adherence to the established formats and Government provided templates; and identify and correct errors in spelling, grammar, punctuation, style, paragraph indentation, capitalization, and acronym definition. The technical test & evaluation documentation to be reviewed include, but it is not be limited to, technical studies, system performance and requirement specifications, interface and design documents, version description documents, system manuals, test plans, test procedures, test reports, and quick look reports. The contractor shall document the results of each review in a professionally written Technical Report.

3.4 Meeting Support

The contractor shall participate in meetings such as Program Management Reviews (PMR), Working Groups (WGs), Configuration Control Boards (CCB), In-Progress Reviews (IPR), Technical Interchange Meetings, video teleconferences, voice teleconferences, and planning sessions as required. The contractor shall generate professional technical test & evaluation documentation reports after each meeting, documenting all decisions resulting from technical discussion.

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.

4.1 Monthly Status Report

The contractor shall prepare and deliver an electronic Monthly Status Report on its technical writing support activities. The monthly report shall include a work breakdown structure that identifies the document worked on, the system/program involved, the technical personnel performing the work, and the number of hours associated with each item reported. The report

PWS for Technical Engineering Support 8 July 2014 shall be delivered to the COR no later than the tenth (10) of the month. The Monthly Status

Report shall be delivered to the Contracting Officer’s Representative (COR) via e-mail in the current version of Microsoft Office® Word in use by MCTSSA. The report shall include at a minimum, a description of the services provided and deliverables completed during the reporting period, number of hours expended per document, planned activities for the upcoming reporting period (month), and problems areas and actions planned or recommended solutions for alleviating the problem.

4.2 Technical Test & Evaluation Documentation

The contractor shall use the government provided technical documentation report format or templates for content preparation instructions of a technical plan, technical specification, and other technical documentation. A draft technical document or document template report shall be delivered to the government thirty (30) calendar days after receiving the task. The final technical test & evaluation document or document template is due seven (7) calendar days after receipt of

Government comments unless a different schedule is agreed to by the COR and the contractor due to the scope of the required modifications.

4.3 Test Plan

The contractor shall use the format and content preparation instructions of the Test Plan

Template provided by the Government. A draft test plan is due thirty (30) calendar days prior to the start of the test. The final test plan is due seven (7) calendar days after receipt of

Government comments unless a different schedule is agreed to by the COR and the contractor due to the scope of the required modifications.

4.4 Test Report

The contractor shall use the format and content preparation instructions of the Test Report

Template provided by the Government. A draft test report is due within twenty (20) calendar days following the completion of the test. The final test report is due five (5) calendar days after receipt of Government comments unless a different schedule is agreed to by the COR and the contractor due to the scope of the required modifications.

4.5 Quick Look Report

The contractor shall use the format and content preparation instructions of the Quick Look

Template provided by the Government. A draft quick look report is due within ten (10) calendar days following the completion of the tests, demonstrations, or technical evaluations. The final quick look report is due seven (7) calendar days after receipt of Government comments unless a different schedule is agreed to by the COR and the contractor due to the scope of the required modifications.

4.6 Technical Reports

A Technical Report shall include:

PWS for Technical Engineering Support 8 July 2014

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

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

c. Names of contractor and Government personnel participating; and

d. For meeting support: Summary of the subjects/information/tasks covered during the meeting, and the decisions, conclusions, direction or agreements reached by the participants related to writing, revising, editing, formatting, and maintaining test, system, and program documentation. Include areas requiring further analysis, action items, and due dates;

e. For a document review: Determination if document satisfies its intended use, detailed description of discrepancies, errors, or omissions found in the overall organization and format of the document, and errors in spelling, grammar, punctuation, style, paragraph indentation, capitalization, and acronym definition. Include recommendations for proposed changes to the document; or

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

The contractor shall deliver meeting minutes within four (4) calendar days following meeting conclusion. The contractor shall deliver document review findings within fourteen (14) calendar days after document receipt. The contractor shall deliver technical write-ups within seven (7) calendar days following analysis completion. The final is due five (5) calendar days after receipt of Government comments.

4.7 Distribution Statement

The following statement regarding distribution shall appear on the cover or title page of all new and updated unclassified technical documents, data, and information (including technical drawings, technical notes and manuals, test plans, test procedures, quick look reports, and technical reports) whether produced in hard-copy or in digital format: “Distribution Statement

C: Distribution authorized to U.S. Government agencies and their contractors associated with the system(s) identified in this document; document contains technical, operational, or test information that is for official Government use. Other requests for this document shall be referred to Commanding Officer, Marine Corps Tactical Systems Support Activity, Box 555171, Camp Pendleton, California 92055-5171.”

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

PWS for Technical Engineering Support 8 July 2014

4.9 Unclassified End Products

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

4.10 Classified End Products

Classified end products shall be delivered directly to 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 for tracking. All classified documents shall be properly classified, handled, marked, transmitted, safeguarded, and controlled in accordance with the National Industrial Security Program

NISPOM, (DOD Directive 5220.22-M).

4.11 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

The performance location for all work associated with the requirements of this performance work statement (PWS) will be performed primarily at MCTSSA, Camp Pendleton and at the contractor’s facility. The contractor shall be expected to perform 90% of the work on-site at

MCTSSA and 10% offsite at the contractor’s facility. MCTSSA will provide onsite workspace to ensure that sensitive information and/or classified material stays within the MCTSSA network. This supports information security and reduces costs associated with the contract by requiring an off-site facility to meet security regulations.

6 INSPECTION OF DELIVERABLES

The COR for the on-site technical support effort is responsible for the inspection of all deliverables at the place of delivery (MCTSSA).

Inspection and acceptance of the contract deliverables are the responsibility of the Contracting

Officers Representative, unless as 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 electronic correspondence. Minor corrections required to deliverables will be verbally discussed with the contractor and noted on deliverable products. A revised deliverable shall be delivered to the

Government (COR) 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

PWS for Technical Engineering Support 8 July 2014 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 contract is anticipated to be one (1) base year and three (3) one-year option periods.

8 GOVERNMENT FURNISHED EQUIPMENT AND FACILITIES

8.1 Government Furnished Equipment

The principle tools required to support this effort are word processing equipment (laptop/desktop computers), Microsoft Office Suite and Microsoft Visio. The contractor can provide these tools, but it would require the transfer of files and data from the government computer network to the contractor’s computers. It is in the best interest of MCTSSA to provide the contractor with these tools in order to protect information and mitigate the risks associated with the additional steps and equipment required to transfer sensitive files/information and to ensure that the data remains on government owned equipment.

8.2 Access to Government Property

No permanent office(s) will be provided under this PWS however, a designated work area will be identified. 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. The contractor shall log all offsite calls.

Access to photocopier, internet, and a Common Access Card (CAC) reader and the software 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 Technical Labs and other environments within

MCTSSA as needed to execute the tasks within this PWS during normal working hours, 0700 to

1600, Monday through Friday. Access to MCTSSA facilities outside of normal working hours shall be scheduled in advance at least one (1) working day prior to access with the MCTSSA

COR and Security Officer. Any unclassified contractor-furnished laptops must be logged with the laboratory entry control point/sentry. 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 except as noted below:

a. Access to printers and copier

b. Administrative supplies and office supplies

PWS for Technical Engineering Support 8 July 2014

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 technical information required for the performance of the tasking within this PWS.

a. The Government will provide a user and email account on the NMCI/government network 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.

b. The Government will provide a user and email account on the MCTSSA 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 may require access to classified information and 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 contract 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 confirmed and current in the Joint Personnel

Adjudication System (JPAS).

9.3 Security Clearance

A SECRET clearance with NATO access is required for all contractor personnel supporting the technical requirements of 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

PWS for Technical Engineering Support 8 July 2014 military duty was not terminated by a dishonorable or bad conduct discharge; not be subject to an outstanding criminal warrant, have any felony conviction, and have no 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 or substance.

All contractor personnel aboard MCB Camp Pendleton, CA, with the exception of emergency personnel, shall wear a properly identifiable 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 three – four (3-4) years of professional experience in process evaluation, technical writing and editing documents in a technical environment, including evaluation-related documents such as plans, specifications, design descriptions, end-user guides, technical reports, and test documentation such as test plans, test procedures, quick-look reports, and test reports. Must have expertise with the latest

Microsoft® Office product suite, including Word, Excel, Project, possess exemplary grammar, spelling, and punctuation skills, 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 have, at a minimum, the equivalent qualifications of the person being replaced.

11 TRAVEL REQUIREMENTS

No travel is anticipated for this PWS.

PWS for Technical Engineering Support 8 July 2014

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

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 http://www.ccr.gov/ https://wawf.eb.mil/ https://wawf.eb.mil/

PWS for Technical Engineering Support 8 July 2014 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

PWS for Technical Engineering Support 8 July 2014 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.

PWS for Technical Engineering Support 8 July 2014

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