M00264-21-R-0007.pdf

SEE ADDENDUM

(No Collect Calls)

M0026421R0007 18-Feb-2021

b. TELEPHONE NUMBER

(703) 432-1684

8. OFFER DUE DATE/LOCAL TIME

12:00 PM 15 Mar 2021

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

M002649. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

REED OSBOURN

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

M9545021SUPCBMC

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

MCINCR - RCO

2010 HENDERSON RD

SGT REED OSBOURN

QUANTICO VA 22134

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

(703) 784-1912FAX:

TEL: (703) 432-1684

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$30,000,000

NAICS:

541519

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF67

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

M0026421R0007

Section SF 1449 - CONTINUATION SHEET

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 12 Each TASK 01: PM and Admin Support

FFP

TASK 01- Project Management and Administration IAW PWS 3.1.

FOB: Destination

MILSTRIP: M9545021SUPCBMC

PURCHASE REQUEST NUMBER: M9545021SUPCBMC

PSC CD: 7A21

NET AMT

0002 1 Each TASK 02-System Planning & Implementation

FFP

TASK 02-System Planning and Implementation IAW PWS 3.2

FOB: Destination

MILSTRIP: M9545021SUPCBMC

0003 1 Each TASK 03- BMC Discovery Products

FFP

TASK 03- BMC Discovery Products IAW PWS 3.3.

FOB: Destination

MILSTRIP: M9545021SUPCBMC

1004 12 Each OPTION Task 04-Continuous Support for BMC Disc

FFP

Task 04-Continuous Support for BMC Discovery IAW PWS 3.4

FOB: Destination

MILSTRIP: M9545021SUPCBMC

2004 12 Each OPTION Task 04-Continuous Support for BMC Disc

FFP

Task 04-Continuous Support for BMC Discovery IAW PWS 3.4

FOB: Destination

MILSTRIP: M9545021SUPCBMC

3004 12 Each OPTION Task 04-Continuous Support for BMC Disc

FFP

Task 04-Continuous Support for BMC Discovery IAW PWS 3.4

FOB: Destination

MILSTRIP: M9545021SUPCBMC

PWS

Performance Work Statement (PWS) for

BMC Discovery Installation and Configuration Services – Marine Corps

1.0 BACKGROUND.

Marine Corps Cyberspace Operations Group (MCCOG) has been designated as the

Cybersecurity Service Provider (CSSP). As a CSSP, both MCCOG and CSSP subscribers are required to ensure IT assets are inventoried, and software platforms and applications are inventoried, to include virtual machines. Per MARFORCYBERCOM GENADMIN 20-0008

DTG 101757Z Apr 20, standardized use of BMC Remedy is required to improve operational effectiveness which includes Asset Management. Most records are maintained and updated via manual methods by USMC organizations.

BMC Discovery capabilities are currently in use within the Hybrid Cloud Services (HCS) environment, and integrated with BMC Remedy suite of applications currently in use across the

Marine Corps Enterprise Network (MCEN). MCCOG is seeking configuration and installation of similar BMC Discovery products (BMC Discovery Data Center, BMC Discovery for Storage, BMC Discovery Multi-cloud) to support increased discovery and dependency mappings of non-

HCS IT assets across the MCEN. Deployment of BMC discovery capabilities will encompass testing, unclassified and classified environments.

2.0 GENERAL REQUIREMENTS.

This section describes the general requirements for this effort. The following sub-sections provide details of various considerations on this effort.

2.1 Scope:

Primary purpose of this PWS is to seek support in providing engineering, design and technical and administrative support to install, configure and integrate BMC Discovery software products and associated platforms, etc. The contractor shall perform to the standards identified in the

PWS. References to the term “contractor” shall include the contractor, its management and employees, and any subcontractors associated with the contractor’s effort. Purpose of BMC

Discovery product configuration and installation efforts are to:

(1) Automatically discover and capture data center inventory, storage devices, cloud-hosted systems, applications and software

(2) Dynamically capture configuration and relationship data

(3) Integrate BMC Discovery applications with USMC instances of BMC Enterprise

Remedy ITSM Suite (ERIS) Configuration Management databases (CMDBs) to dynamically create, update records and create relationship/dependency mappings as appropriate.

(4) Maps applications to the IT infrastructure

3.0 TASKS:

3.1 TASK/CLIN 0001- Project Management and Administration. The Contractor shall manage and administer all aspects of the task requirements in performance of this effort.

3.1.1 The Contractor shall develop and deliver a Monthly Contract Status Report. The report shall include major accomplishments during the reporting period, items needing

Government/COR attention, issues and resolutions, and a schedule of services to be accomplished for the next month.

CDRL A001-Monthly Contract Status Report

3.1.2 The Contractor shall develop and deliver a Project Schedule outlining the sequence of activities, resources and timelines and deliverables to support execution of tasks identified within this PWS. Project Schedule shall be provided in electronic format (e.g., MS Project) and updated accordingly as changes to activities, resources and timelines occur. The Contractor shall attend weekly meetings as required in support of this PWS.

CDRL B001-Project Schedule

3.2 TASK/CLIN 0002-System Planning and Implementation.

3.2.1 System Configuration Planning

The contractor shall provide configuration support in the identification and evaluation of the existing IT environment to properly assess and scale BMC Discovery applications and appliances to ensure maximum performance and availability.

3.2.1.1 The Contractor shall support hosting up a User Requirements Workshop to gather user requirements, identify government support and data, credential and access requirements to support BMC discovery applications.

CDRL A002-Conference Minutes-User Requirements Workshop

3.2.1.2 The Contractor shall support hosting up a Design and Security Workshop to gather design and security related details of BMC Discovery hosting infrastructure.

CDRL B002-Conference Minutes- Design and Security Workshop

3.2.1.3 The Contractor shall collaborate and coordinate with existing Marine Corps BMC

Remedy support personnel as required to gain understanding of existing environment and other details to support planning and implementation efforts.

3.2.1.4 The Contractor shall ensure proper coordination and scheduling of changes, etc. within respective environments defining scope, impact, before implementation.

3.2.1.5 The Contractor shall identify sizing guidelines and system design requirements to support

BMC Discovery hosting infrastructure within testing, classified and unclassified and production environments, to include network segments identified by the government.

Examples of sizing guidelines include, but are not limited to: CPUs, RAM, Hard Disk, NIC, DHCP, backup and other requirements to support virtual appliance hosting.

3.2.1.6 The Contractor shall provide detailed documentation of entire implementation within respective environments to include architecture drawings of BMC Discovery solution.

3.2.1.7 The Contractor shall provide updates to systems design documentation and drawings as changes to proposed solution are identified and incorporated.

CDRL C002-System/Subsystem Design

3.2.1.8 The Contractor shall coordinate with government personnel to ensure BMC Discovery related systems meet Defense Information Systems Agency (DISA) Security Technical

Implementation Guide (STIG) standards.

3.2.1.9 The Contractor shall coordinate with government personnel to ensure all systems are patched to current patch levels.

3.2.1.10 The Contractor shall coordinate with government personnel to ensure BMC

Discovery Technology Knowledge Updates (TKU’s) are current.

3.2.1.11 The Contractor shall coordinate with government personnel to provide required documentation and artifacts to support system accreditation of BMC Discovery capability as appropriate.

3.2.2 System Implementation.

The Contractor shall ensure BMC Discovery applications are properly configured and installed in both test and production environments to support successful discovery and dependency mappings.

3.2.2.1 The Contractor shall ensure BMC CMDB integrations are properly configured, including custom filters such as exclusions if needed.

3.2.2.2 The Contractor shall ensure dedicated BMC Discovery systems successfully access required targeted systems to support aggregation of data collected.

3.2.2.3 The Contractor shall ensure the CMDBs are properly configured to accept data from

BMC Discovery applications.

3.2.2.4 The Contractor shall ensure BMC Discovery Data Center is properly configured to conduct discovery of UNIX / Windows operating system types.

3.2.2.5 The Contractor shall ensure BMC Discovery Data Center is properly configured to conduct database discoveries.

3.2.2.6 The Contractor shall ensure BMC Discovery Data Center is properly configured to conduct discovery of network devices.

3.2.2.7 The Contractor shall ensure BMC Discovery for Multi-Cloud is properly configured to conduct cloud based discoveries.

3.2.2.8 The Contractor shall ensure BMC Discovery for Storage is properly configured to conduct storage device type discoveries.

3.2.2.9 The Contractor shall ensure BMC Discovery data is visible within the CMDB viewers and ITSM.

3.2.2.10 The Contractor shall verify data is returned from within configured BMC

Discovery applications.

3.2.2.11 The Contractor shall collaborate with system owners or other support personnel as required to confirm successful connections to targeted hosts within BMC Discovery applications, etc. is achieved and viewed results from integrations are correct.

3.2.2.12 The Contractor shall create and develop normalization and reconciliation rules in the CMDBs based on BMC Discovery data.

3.2.2.13 The Contractor shall collaborate with government personnel to create up to 10 application maps, 5 basic and 5 complex.

3.2.2.14 The Contractor shall collaborate with government personnel to create up to 10 custom dashboards.

3.2.2.15 The Contractor shall provide training to government personnel in the development of Dashboards within BMC Discovery.

3.2.2.16 The Contractor shall verify full system functionality including the movement of asset data and application maps to the CMDB.

3.2.2.17 The Contractor shall ensure acceptance testing is developed and successfully completed.

3.2.2.18 The Contractor shall mitigate findings based on acceptance testing are properly resolved prior to production implementation.

3.2.2.19 The Contractor shall ensure monitoring and proper troubleshooting of any issues identified during pre-production and production implementations, escalating findings as required and ensuring proper resolutions.

3.2.2.20 The Contractor shall create a draft Installation and Technical Instructions (ITI) document for integration builds in their format for government review and acceptance.

CDRL D002: Integration and Technical Instructions (ITI) Document

3.2.2.21 The Contractor shall create a draft Application Modeling Build document in their format for government review and acceptance.

CDRL E002: Application Modeling Build Document

3.2.2.22 The Contractor shall support shadowing in support of operation and use of BMC

Discovery as configured within the Marine Corps environment.

3.2.2.23 The Contractor shall create a draft BMC Discovery Operations Manual in their format for government review, testing and acceptance.

CDRL F002: BMC Discovery Operations Manual

3.2.2.24 The Contractor shall collaborate with government personnel and provide necessary documentation to support accreditation of systems and associated products (e.g., Authority to Operate).

3.3 TASK/CLIN 0003- BMC Discovery Products. The Contractor shall acquire and deliver the following BMC products to support implementation efforts under TASK/CLIN 0002-

System Planning and Implementation.

Item License

Type

Quantity

BMC Discovery for Data

Center

Perpetual 5000

BMC Discovery for Storage Perpetual 5000

BMC Discovery for Multi-

Cloud

Perpetual 1000

CDRL A003: BMC Discovery Products

BMC Discovery for Data Center, Perpetual License, Qty 5000

BMC Discovery for Storage, Perpetual License, Qty 5000

BMC Discovery for Multi-Cloud, Perpetual License, Qty 5000

3.4 TASK 04/CLINs 1004, 2004, 3004-Continuous Support for BMC Discovery. The

Contractor shall provide continuous support for BMC Products implemented and acquired under tasks 2 and 3. Continuous support shall consist of bug fixes (e.g., program errors, flaws, faults resulting in incorrect/unexpected results), patches or workarounds for product operation in substantial conformity with current operating documentation, providing new releases or versions to support Government end users. Support under this task shall be accessible to government via web, e-mail, and phone.

CDRL A004:

Continuous Support BMC Discovery for Data Center, Perpetual License, Qty 5000

Continuous Support BMC Discovery BMC Discovery for Storage, Perpetual

License, Qty 5000

Continuous Support BMC Discovery for Multi-Cloud, Perpetual License, Qty 1000

4.0 SPECIAL REQUIREMENTS:

This section describes the special requirements for this effort. The following sub-sections provide details of various considerations on this effort.

The Contractor shall possess a minimum of 10 years subject matter expertise/knowledge with

BMC Remedy Discovery product integrations, Remedy Atrium CMDB, Product Catalog configuration, normalization and reconciliation job development. Additionally, the contractor shall have expertise and knowledge of The Pattern Language (TPL) for custom discovery patterns. The Contractor shall possess a bachelor’s degree in Computer Science or related field, BMC CMDB Administrator Certification or equivalent training and mastery with CMDB technologies. Contractor shall possess 5 or more years experience supporting CMDB projects.

Contractor shall possess strong verbal and written communication skills to consult with management, business partners and vendors. The Contractor shall possess at a minimum IAM

Level II certification based on DoD Directive 8570.1 requirements.

5.0 PERFORMANCE REQUIREMENTS SUMMARY (PRS)

Surveillance of Contractor performance is the method used by the Government to determine whether the Contractor is effectively and efficiently complying with all terms and conditions of this effort. The functional expertise of the Contracting Officer’s Representative (COR) plays a critical role in adequately evaluating contractor performance.

The PRS provides the base line requirement, basic structure and minimum standards for program operation. Throughout performance, the Contractor shall ensure that all personnel, based upon their selected staff complement, are fully trained and possess the tactical skills required to execute the functions of the assigned role to the standards of quality outlined in the PRS. The

Contractor is responsible for developing and implementing a support structure to meet program objectives, as follows:

PERFORMANCE

OBJECTIVE / PWS

PARAGRAPH

PERFORMANCE

STANDARDS

ACCEPTABLE

QUALITY

LEVEL

METHOD OF

SURVEILLANCE

Task 1 – Project

Management and

Administration

PWS para 3.1

- Monthly Contract Status

Report to include workforce reporting to be updated as personnel are added and removed to the contract.

Submitted NLT 5th day of each month.

-Project Schedule outlining sequence of activities, resources, timelines and deliverables in electronic format NLT 5 working days after onboarding, and within 3 working days after required updates are identified.

- Deliverables shall be timely, accurate, complete and prepared with < 5% rejection rate;

- Timely resolution of any performance issues within 5 days

100% timely submission

95% Accepted documents

100% of resolutions within 5 days.

COR

inspection/acceptance of digital copy

Customer feedback

Task 2– System

Planning and

Configuration

PWS para 3.2.1.1

-Conference Minutes of User

Requirements Workshop

(CDRL A002) to be submitted

NLT 3 months after date of award.

submission.

COR and Government leads inspection/acceptance of digital copy

Task 2– System

Planning and

Configuration

PWS para 3.2.1.2

-Conference Minutes of

Design and Security

Workshop (CDRL B002) submitted NLT 3 months after date of award.

submission.

100% complete

COR and Government leads inspection/acceptance of digital copy

Task 2– System

Planning and

Configuration

PWS para 3.2.1.7

- Documentation of

System/Subsytem Design

(CDRL C002 provided NLT 3 months after date of award.

leads inspection/acceptance of digital copy

PARAGRAPH

PERFORMANCE

STANDARDS

ACCEPTABLE

QUALITY

LEVEL

METHOD OF

SURVEILLANCE

Task 2– System

Planning and

Configuration

PWS para 3.2.2

-BMC Discovery applications are properly configured to discovery different system types, NLT 12 months after the date of award.

leads inspection/acceptance

Configuration

PWS para 3.2.2.l2

- Normalization and reconciliation rules are properly defined, NLT 12 months after the date of award.

Configuration

PWS para 3.2.2.16

-System functionality and movement of asset data and application maps works properly, NLT 12 months after the date of award.

Configuration

PWS para 3.2.2.20-

3.2.2.22

-Documentation provided for

Instructions and Technical

Implementation, Application

Modeling, and BMC

Operations Manual (CDRL

D002, CDRL E002, CDRL

F002), finalized with government review and concurrence NLT 12 months after the date of award.

Task 3: BMC

Discovery Products

Delivery of all licenses identified in section 3.3

Task 4: Continuous

Support for BMC

Discovery Products

- The Contractor shall possess a minimum of 10 years subject matter expertise/knowledge with

BMC Remedy Discovery product integrations, Remedy

Atrium CMDB, Product

Catalog configuration, normalization and reconciliation job development. Additionally, the contractor shall have expertise and knowledge of

-100% proficiency in knowledge, skills and abilities to perform tasks within this PWS.

COR and Government

PARAGRAPH

PERFORMANCE

STANDARDS

ACCEPTABLE

QUALITY

LEVEL

METHOD OF

SURVEILLANCE

The Pattern Language (TPL) for custom discovery patterns.

The Contractor shall possess a bachelor’s degree in

Computer Science or related field, BMC CMDB

Administrator Certification or equivalent training and mastery with CMDB technologies. Contractor shall possess 5 or more years experience supporting CMDB projects. Contractor shall possess strong verbal and written communication skills to consult with management, business partners and vendors.

The Contractor shall possess at a minimum IAM Level II certification based on DoD

Directive 8570.1 requirements.

6.0 TRAVEL.

Travel will not be required outside of local area; therefore, travel within a 50 mile radius of place of performance will not be reimbursed.

7.0. PERIOD OF PERFORMANCE.

See Delivery Schedule.

8.0 PLACE OF PERFORMANCE. The primary place will be a within a 20 miles radius of

Quantico VA.

In addition, contractor employees may be required to work at home (adhoc), or at the contractor's facility in cases of unforeseen conditions (e.g., government office closings, severe weather, pandemic conditions, etc.) which is to be worked out between the contractor employee and their employer.

9.0 HOURS OF OPERATION. Work schedules are flexible around a core period of 0600 to

1800 with an occasional requirement for evening or weekend work based on operational requirements.

The Government observes and the Contractor may not have access to federal work spaces or to the COR on the following legal holidays and any other day determined to be a holiday by the

President of the United States and Public Law:

New Year’s Day Martin Luther King’s Birthday

Presidents’ Day Memorial Day

Independence Day Labor Day

Columbus Day Veteran’s Day

Thanksgiving Day Christmas Day

Inauguration Day (Washington D.C., Maryland and

Virginia Only)

10.0 GOVERNMENT FURNISHED EQUIPMENT. No GFE will be provided. Servers/client hardware and software, and workstations for use on-site to assist in software development, problem resolution, or field support, will be provided by the government as appropriate.

The Government agency will provide Government furnished workspace and IT assets for contractor personnel at Government facilities or at various other Government locations to accomplish the efforts. The Government will provide adequate physical workspace and will furnish accesses to Government-issued and owned Common Access Cards (CACs), desks, phones, computer equipment (to include all necessary hardware & software), an electronic government mail (e-mail) account, use of the Government telephone, facsimile machine, and/or copier usage, as necessary in performance of tasks.

11.0 GOVERNMENT FURNISHED INFORMATION (GFI). GFI in the form of procedures, policies, and or program/system technical manuals will be provided as needed to support the problem resolution, and or field support, as appropriate.

12.0 SUMMARIZATION OF DATA RIGHTS.

Data, Software and Intellectual Property Rights. In accordance with the DFARS data rights clauses associated with this effort, without limitation, all reports, materials (including, but not limited to, all training and training-related materials including, but not limited to, all SOPs, lessons learned, analyses/evaluations and analyses/evaluation criteria, on-line course materials, computer software/applications and hardware, source code, interfaces, tools, works, and other related items) data, information, and all electronic/digital files and other items described herein, and any other items, (hereinafter referred to individually or collectively as the Work or Works) that are first created, generated, or produced and required to be delivered under, or as a result of, this PWS shall be provided to the U.S. Government/Marine Corps with the level of intellectual property/data rights provided by such DFARS data rights clauses.

Such data rights and related clauses include, but may not be limited to DFARS Clauses:

252.227-7012 - Patent License and Release Contract;

252.227-7013 - Rights in Technical Data--Noncommercial Items;

252.227-7014 - Rights in Noncommercial Computer Software and Noncommercial Computer

Software Documentation;

252.227-7015 - Technical Data–Commercial Items, 252.227-7017 - Identification and Assertion of Use, Release, or Disclosure Restrictions;

252.227-7019 - Validation of Asserted Restrictions--Computer Software;

252.227-7020 - Rights in Special Works;

252.227-7025 - Limitations on the Use or Disclosure of Government-Furnished Information

Marked with

Restrictive Legends;

252.227-7027 - Deferred Ordering of Technical Data or Computer Software; and

252.227-7028 - Technical Data or Computer Software Previously Delivered to the Government and 252.227-7037 - Validation of Restrictive Markings on Technical Data.

Using the format described by DFARS 252.227-7017, the Contractor will provide the COR with a data rights assertion listing for all deliverables including both non-commercial and commercial technical data and computer software. Furthermore, the Contractor shall not use the Contractor’s or a third-party’s proprietary data, information, software, items and/or other materials for any purpose without meeting the requirements of DFARS clauses 252.227-7020 and/or 252.227-

7025, and without the specific, written approval by the Contracting Officer, prior to start of any work.

Moreover, except as provided in writing by the Contracting Officer, no Work, information, material and/or other item created, generated, produced and required to be delivered under, or as a result of, this PWS/effort shall be used by the Contractor or any of its employees/agents, subcontractors and/or representatives, for any purpose other than for the support and performance of this PWS. Still further, the Contractor is obligated to protect from unauthorized use or disclosure all Government confidential or classified material and/or Government-owned proprietary, and/or Personally Identifiable Information or Personal Privacy Items obtained in the course of performance, as long as such data remains proprietary, confidential, sensitive, or classified.

13.0 ACCESS TO PROPRIETARY DATA OR COMPUTER SOFTWARE.

(a) Performance under this effort may require that the Contractor have access to technical data, computer software, or other sensitive data of another party (including an affiliated party) who asserts that such data or software is proprietary. Therefore, the Contractor must comply with

DFARS 252.227-7025 when appropriate.

If access to such data or software is required and needs to be provided, the Contractor shall enter into a written agreement (Non-Disclosure Agreement or NDA) with such party prior to gaining access to such data or software. The agreement shall address, at a minimum, (1) access to, and use of, the proprietary data or software exclusively for the purposes of performance of the work required by this effort, and (2) safeguards to protect such data or software from unauthorized use or disclosure for so long as the data or software remains proprietary. In addition, the agreement shall not impose any limitation upon the Government or its employees with respect to such data or software. A copy of the executed agreement shall be provided to the Contracting Officer prior to the start of any work under this effort. The Government may unilaterally modify the contract to list those third parties with which the Contractor has agreement(s).

(b) The Contractor agrees to: (1) indoctrinate its personnel who will have access to the data as to the restrictions under which access is granted; (2) not disclose the data to another party or other

Contractor personnel except as authorized by the above-described NDA and the Contracting

Officer; (3) not engage in any other action, venture, or employment wherein this information will be used, other than under this contract, in any manner inconsistent with the spirit and intent of this requirement; (4) not disclose the data to any other party, including, but not limited to, joint venture, affiliate, successor, or assign of the Contractor; and (5) reproduce any restrictive stamp, marking, or legend on each use of the data whether in whole or in part.

(c) The restrictions on use and disclosure of the data and software described above also apply to such information received from the Government through any means to which the Contractor has access in the performance of this effort that contains proprietary or other restrictive markings.

(d) The Contractor agrees that it will promptly notify the Contracting Officer of any attempt by an individual, company, or Government representative not directly involved in the effort to be performed under this effort to gain access to such proprietary information. Such notification shall include the name and organization of the individual, company, or Government representative seeking access to such information.

(e) The Contractor shall include this requirement in subcontracts of any tier which involve access to information covered by paragraph (a), substituting "subcontractor" for "Contractor" where appropriate.

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

14.0 ORGANIZATIONAL CONFLICT(S) 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 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 this section. 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.

(c) (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 information provided to the contract by the government during or as a result of performance of this effort. 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 order or where it is discernible from materials incorporating or based upon such information. This prohibition shall not expire after a given period of time.

(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, first generated design or product as a result of performance of this effort. This prohibition shall expire after a period of three years after completion of performance of this effort.

(3) The prohibitions contained within this section 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 this Special Contract Requirement relating to notification shall apply to any release of information in contravention of this section.

(d) The Contractor further agrees that, during the performance of this effort and for a period of three years after completion of performance of this effort, the Contractor agrees that it will not supply as a Prime Contractor, subcontractor at any tier, or consultant to a supplier to the

Department of Defense, any product, service, or major component of an item or services which was the subject of the specifications and/or work statements furnished under this effort. This exclusion does not apply to any re-competition for those systems, components or services furnished pursuant to this contract. The Contractor shall, within 15 days after the effective date of this contract, provide, in writing, the Contracting Officer, a representation that all employees, agents, and subcontractors involved in the performance of this effort have been informed of the provisions of this requirement. Any subcontractor that performs any work relative to this contract shall be subject to this requirement. The Contractor agrees to place in each subcontract affected by these provisions the necessary language contained in this section.

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

(f) If the Contractor was aware, or should have been aware, of an organizational conflict of interest prior to the award of this contract or becomes, or should become, aware of an organizational conflict of interest after award of this contract and does not make an immediate and full disclosure in writing to the Contracting Officer, the Government may terminate this contract for cause.

(g) If the Contactor takes any action prohibited by this requirement or fails to take action required by this requirement, the Government may terminate this contract for cause.

(h) The Contracting Officer's decision as to the existence or nonexistence of an actual or potential organizational conflict of interest shall be final.

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

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

(k) 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 effort. Compliance with this requirement is a material requirement of this effort.

15.0 SECURITY REQUIREMENTS.

A DD 254 - Contract Security Classification Specification is required for this effort. The

Contractor is responsible for implementing the provisions of the DoDM 5105.21, and its Navy

Supplement, in support of this effort. Classified work may be required to be performed under this effort. A facility clearance up to SECRET (S) will be required to support this PWS.

As specified in clause DFARS 252.204-9200 and the Contract Security Classification

Specification form, DD-254, classified work shall be performed under this effort. Prior to commencement of classified work, the Contractor shall possess an appropriate facility clearance and cleared personnel for tasking received. Contractor personnel shall obtain clearances required for their specific task and work site and follow all local security rules and regulations.

All tasks will be conducted in full compliance with DoD security regulations. The Government will provide assistance to the personnel supporting this requirement in obtaining workplace access during the period of support. All access documentation will be returned to the

Government at the completion of the support services or upon termination or resignation of employment. Compliance with all USMC communications regulations pertaining to access to e-mail and Internet activities is mandatory. Failure to comply with security requirements is grounds for termination.

The Contractor(s) shall be required to wear a contractor identification badge at all times while on

Government property. Badges must be clearly visible at all times while on Government property.

The Contractor and its representatives will not release any information concerning this effort to any third party without first obtaining written authorization from the Government Contracting

Officer.

Access to US military sites is a privilege that may be granted, denied, or withdrawn by the

Marine Corps. Denial or withdrawal may occur as a result of any type of misconduct or incident determined contrary to the best interest of the Marine Corps mission, protection of property, welfare of personnel and for any other infraction determined justifiable for denying access.

The Contractor shall comply with the following:

a. No employee or representative of the contractor will be admitted on a Marine Corps site unless they furnish satisfactory proof of United States citizenship or, if an alien, that their residence and employment within the United States is legal.

b. All Contractor employees must possess a valid picture identification card issued by a State or

Federal agency.

c. All Contractor employees shall conduct themselves in a proper, efficient, courteous and business-like manner.

d. All Contractor employees entering Marine Corps sites shall comply with all security requirements in effect during the contract periods and shall be subject to such checks as may be deemed necessary. The Contractor should contact each installation prior to beginning work on-site to ensure the Contractor understands and can comply with individual installation security requirements

15.1 Security Clearances.

The Contractor shall have security clearance of SECRET. The Contractor shall provide sufficient personnel with the required security clearances granted by the Defense Industrial Security

Clearance Office (DISCO) to perform the work as specified in individual tasks. The Contractor shall conform to the security provisions of DoD 5220.22-M, SECNAVINST 5510.30, and the

Privacy Act of 1974. Prior to any labor being charged on contract, the Contractor shall ensure their personnel possess and can maintain appropriate security clearances at the appropriate level(s).

At a minimum, the Contractor shall validate the background information provided by its employees in support of this effort is correct. In accordance with DoD Directive 8570.01, Contractor personnel shall meet requirements in DoD 8570.10-M for contract performance as applicable to the work being performed. Cost to meet these security requirements is not directly chargeable to the contract. If an individual who has been submitted for a security clearance is

"denied" for a clearance or receives an "Interim Declination" that individual must be removed from Government facilities, projects, and/or programs until such time as the investigation is fully adjudicated or the individual is resubmitted and is approved. All contractor and subcontractor personnel removed from facilities, projects, and/or programs shall cease charging labor directly or indirectly on this contract.

Prior to starting work on the contract, contractor personnel shall comply with IT access authorization requirements. In addition, Contractor personnel shall possess the appropriate IT level of access for the respective task and position assignment as required by DoD 8500.1, Information Assurance and DoDI 8500.2, Information Assurance (IA) Implementation. Any future revision to the respective directive and instruction shall be applied at the contract level as required. Contractor personnel shall handle and safeguard any sensitive and classified information in accordance with appropriate DoD security regulations. Any security violation shall be reported immediately to the respective government Project Manager (PM) and/or contract COR.

All Contractor personnel being hired or nominated for duty shall successfully complete the applicant screening process prior to being granted access to systems, facilities or information. All

Contractor personnel working on this task must possess the appropriate security clearance and be favorably adjudicated for Secret access. Systems utilized, network, data and information, and working spaces are classified at the Secret level.

Prior to commencement of work, all contractor personnel (including administrative and subcontractor personnel) shall have, at a minimum, a favorable Trustworthiness Determination, which is determined by a National Agency Check with Local Agency Check and Credit Check

(NACLC) and favorable FBI fingerprint checks.

All training required and certifications set forth in the PWS are the responsibility of the contractor to fund and provide. The Contractor may be required to participate in specialized training provided by the Government beyond the qualifications listed in the PWS at locations to be determined.

15.2 Physical Security. The Contractor is responsible for safeguarding all Government property and information provided in performance of this effort. At the close of each work period, the

Contractor is responsible for ensuring Government facilities, equipment, and materials are secured. Contractor employees will be subject to all Headquarters, Marine Corps security procedures and any other applicable installation access and security regulations.

16.0 OTHER PERTINENT INFORMATION OR SPECIAL CONSIDERATIONS.

16.1 Non-Disclosure Agreement.

All Contractor personnel will be required to sign non-disclosure agreements in order to protect the integrity of all operational information, processes or solutions pertaining to this effort and all

USMC, proprietary or sensitive information, materials, items provided, used or accessed during this effort for the United States Marine Corps regardless of the information’s underlying classification level.

17.0 NMCARS 5237.102-90 Enterprise-wide Contractor Manpower Reporting Application

(ECMRA).

The Contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for MAGTF Intelligence and OIE

Support via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs).

The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities;

(4) D, Automatic Data Processing and Telecommunications, IT and Telecom-

Telecommunications Transmission (D304) and Internet (D322) ONLY;

(5) S, Utilities ONLY;

(6) V, Freight and Shipping ONLY.

The Contractor is required to completely fill in all required data fields using the following web address: https://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance during each

Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://www.ecmra.mil.

18.0 Base Access

In order to gain access to Marine Corps Base Quantico VA, registration in the Defense Biometric

Identification System (DBIDS) must be completed as well as possession of a valid form of identification. The DBID registration information and a list of valid forms of identification are found at:

https://www.quantico.marines.mil/Base-Access/

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government

0002 Destination Government Destination Government

0003 Destination Government Destination Government https://www.ecmra.mil/ https://www.ecmra.mil/ https://www.quantico.marines.mil/Base-Access/

1004 Destination Government Destination Government

2004 Destination Government Destination Government

3004 Destination Government Destination Government

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 POP 01-JUN-2021 TO

31-MAY-2022

N/A COMMARCORSYSCOM

3300 RUSSELL ROAD

QUANTICO VA 22134-5001

703-784-4115

FOB: Destination

M95450

0002 12 mths. ADC 1 COMMARCORSYSCOM

ARNALDO MARTIN

3300 RUSSELL ROAD

QUANTICO VA 22134-5001

703-784-4115

0003 12 mths. ADC 1 (SAME AS PREVIOUS LOCATION)

1004 POP 01-JUN-2022 TO

31-MAY-2023

N/A COMMARCORSYSCOM

3300 RUSSELL ROAD

QUANTICO VA 22134-5001

703-784-4115

2004 POP 01-JUN-2023 TO

31-MAY-2024

N/A (SAME AS PREVIOUS LOCATION)

3004 POP 01-JUN-2024 TO

31-MAY-2025

N/A (SAME AS PREVIOUS LOCATION)

CLAUSES INCORPORATED BY REFERENCE

52.203-6 Restrictions On Subcontractor Sales To The Government JUN 2020

52.204-7 System for Award Management OCT 2018

52.204-16 Commercial and Government Entity Code Reporting AUG 2020

52.204-18 Commercial and Government Entity Code Maintenance AUG 2020

52.212-1 Instructions to Offerors--Commercial Items JUN 2020

52.212-4 Contract Terms and Conditions--Commercial Items OCT 2018

52.229-12 Tax on Certain Foreign Procurements JUN 2020

52.232-40 Providing Accelerated Payments to Small Business

Subcontractors

DEC 2013

52.237-2 Protection Of Government Buildings, Equipment, And

Vegetation

APR 1984

252.201-7000 Contracting Officer's Representative DEC 1991

252.203-7000 Requirements Relating to Compensation of Former DoD

Officials

SEP 2011

252.203-7002 Requirement to Inform Employees of Whistleblower Rights SEP 2013

252.203-7005 Representation Relating to Compensation of Former DoD

Officials

NOV 2011

252.204-7003 Control Of Government Personnel Work Product APR 1992

252.204-7009 Limitations on the Use or Disclosure of Third-Party

Contractor Reported Cyber Incident Information

OCT 2016

252.204-7015 Notice of Authorized Disclosure of Information for Litigation

Support

MAY 2016

252.204-7018 Prohibition on the Acquisition of Covered Defense

Telecommunications Equipment or Services

DEC 2019

252.209-7004 Subcontracting With Firms That Are Owned or Controlled By

The Government of a Country that is a State Sponsor of

Terrorism

MAY 2019

252.213-7000 Notice to Prospective Suppliers on Use of Supplier

Performance Risk System in Past Performance Evaluations

SEP 2019

252.222-7999 (Dev) Combating Race and Sex Stereotyping (Deviation 2021-

O0001)

JAN 2021

252.223-7006 Prohibition On Storage, Treatment, and Disposal of Toxic or

Hazardous Materials

SEP 2014

252.223-7008 Prohibition of Hexavalent Chromium JUN 2013

252.225-7001 Buy American And Balance Of Payments Program-- Basic DEC 2017

252.225-7002 Qualifying Country Sources As Subcontractors DEC 2017

252.225-7012 Preference For Certain Domestic Commodities DEC 2017

252.225-7048 Export-Controlled Items JUN 2013

252.225-7993 (Dev) Prohibition on Providing Funds to the Enemy (Deviation

2020-O0022)

AUG 2020

252.226-7001 Utilization of Indian Organizations and Indian-Owned

Economic Enterprises, and Native Hawaiian Small Business

Concerns

APR 2019

252.232-7003 Electronic Submission of Payment Requests and Receiving

Reports

DEC 2018

252.232-7007 Limitation Of Government's Obligation APR 2014

252.232-7010 Levies on Contract Payments DEC 2006

252.232-7017 Accelerating Payments to Small Business Subcontractors--

Prohibition on Fees and Consideration

APR 2020

252.237-7010 Prohibition on Interrogation of Detainees by Contractor

Personnel

JUN 2013

252.239-7001 Information Assurance Contractor Training and Certification JAN 2008

252.239-7010 Cloud Computing Services OCT 2016

252.239-7017 Notice of Supply Chain Risk FEB 2019

252.239-7018 Supply Chain Risk FEB 2019

252.243-7001 Pricing Of Contract Modifications DEC 1991

252.243-7002 Requests for Equitable Adjustment DEC 2012

252.244-7000 Subcontracts for Commercial Items OCT 2020

CLAUSES INCORPORATED BY FULL TEXT

52.204-1 APPROVAL OF CONTRACT (DEC 1989)

This contract is subject to the written approval of and shall not be binding until so approved.

(End of clause)

52.204-22 ALTERNATIVE LINE ITEM PROPOSAL (JAN 2017)

(a) The Government recognizes that the line items established in this solicitation may not conform to the Offeror's practices. Failure to correct these issues can result in difficulties in acceptance of deliverables and processing payments. Therefore, the Offeror is invited to propose alternative line items for which bids, proposals, or quotes are requested in this solicitation to ensure that the resulting contract is economically and administratively advantageous to the Government and the Offeror.

(b) The Offeror may submit one or more additional proposals with alternative line items, provided that…