RFQ M00264-20-T-A002 (PUPPY) AMENDMENT TWO 2-24-20.pdf

UNITED STATES MARINE CORPS

MARINE CORPS INSTALLATIONS NATIONAL CAPITAL REGION

MARINE CORPS BASE QUANTICO

3250 CATLIN AVENUE

QUANTICO VIRGINIA 22134 5001

IN REPLY REFER TO:

B-201 24 February 2020

From: Thea Smith, Contracting Specialist, Marine Corps Installations, National Capital Region

Regional Contracting Office

Subject: Request for Quotation (RFQ) Number: M00264-20-T-A002, Amendment Two

Date: 24 February 2020

This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in

Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued. Prospective awardees must be registered in System for Award Management (SAMs). Information on registering in SAMs may be obtained at https://www.sam.gov. The provisions FAR 52.212-1

Instruction to Offerors – Commercial Items and FAR 52.212-3 Offeror Representations and

Certifications- Commercial Items apply to this acquisition. The clause FAR 52.212-4 Contract Terms and Conditions - Commercial Items and 52.212-5 Contract Terms and Conditions Required To

Implement Statutes Or Executive Orders - Commercial Items apply to this acquisition. The contractor shall comply with all Federal, State, and Local regulations.

This RFQ document and all incorporated provisions and clauses are those in effect through Federal

Acquisition Circular (FAC) 2005-95, published 13 Jan 2017.

This Acquisition is solicited as “Unrestricted” under NAICS code 541519.

Request for Quotation on the following service:

CLIN Item Description Unit Qty.

Unit

Price

Extended

Total

0001 Engineering Technical Services MO 12

0002 Engineering Technical Services MO 12

0003 Onsite Resident Support Services MO 12

0004 Project Management Services MO 12

TOTAL $ $

Period of Performance requested: March 16, 2020 through March 15, 2021

Please provide FOB Destination pricing and a delivery schedule (with your offer) for the following address: North Pennsylvania Street, Indianapolis, Indiana 46204

The Government will accommodate written questions submitted in response to this RFQ. All questions must be submitted in writing via email by Tuesday, February 11 2020, 10:00 a.m., Eastern Standard

Time (EST) to Mrs. Radhiyah (Thea) Smith, at Email: radhiyah.smith@usmc.mil.

The closing date and time for quote submission is: Friday, February 28, 2020, 10:00 a.m., Eastern

Standard Time (EST). Offers received after this date and time may be considered non-responsive and will not be given further consideration. Please provide all quote submissions to: Mrs. Radhiyah (Thea)

Smith, at Email: radhiyah.smith@usmc.mil.

All contractors must comply with the requirement listed for this request. Failure to comply may result in disqualification. This will be a Firm Fixed Price (FFP) contract.

This acquisition will utilize Price and Technically Acceptable procedures in accordance with FAR

13.106-2. Technical tradeoff will not be made and no additional credit will be given for exceeding acceptability. Award will be made to the acceptable offeror with the best evaluated price, which is deemed responsible in accordance with the Federal Acquisition Regulation and whose quote conforms to the solicitation requirements. The solicitation requirements include all stated terms, conditions, representation and certifications, and other information required by this solicitation. The Government reserves the right to award without discussions. Therefore, each initial offer should contain the offeror’s best terms from a price and technical standpoint. However, the Government reserves the right to conduct discussions if determined necessary by the Contracting Officer.

The Government may reject any quote that is evaluated to be unrealistic in terms of requirements, contract terms and conditions, or an unrealistically high or low price when compared to Government estimates, such that the quote is deemed to reflect an inherent lack of competence or failure to comprehend the complexity and risk of the program.

Technical acceptability will be evaluated on all quotes. Only those quotes determined to be technically acceptable, either initially or as a result of discussions, will be considered for award. Award will be made to the evaluated priced quote meeting the acceptability standards for the non-priced factors which offers the Government the best value.

TECHNICAL EVALUATION STANDARD:

The contractor shall address the following two factors:

1. Factor 1 – Technical Capability – Offeror shall clearly demonstrate its approach to technical ability to meet the requirements of CLIN/Line Items based on meeting the requirements of the

Request for Quote, quantity, quality and timeliness of delivery.

2. Factor 2 – Price – The offeror shall complete CLIN pricing on page one (1) of this solicitation.

In addition to the completed CLIN pricing on page one (1), the offeror shall provide sufficient price information to allow the contracting officer to determine the completeness and reasonableness of the offerors prices.

DISCUSSIONS: If during the evaluation period it is determined to be in the best interest of the

Government to hold discussions, Offeror responses to clarifications/discussion notices will be considered in making the source selection decision.

AWARD DECISION: The award decisions will be made as follows:

(1) Step One – Determine Technical Acceptability. The technical evaluation, Factor 1, stated above, will assess the offerors capability to satisfy the Government’s requirement. The Government will evaluate all technical capability quotes received by the required date/time. The Technical mailto:radhiyah.smith@usmc.mil mailto:radhiyah.smith@usmc.mil

Capability factor will receive a rating of acceptable and unacceptable. If any factor is rated

“unacceptable”, the entire quote is rendered technically unacceptable, and the quote will be removed from the competitive range. Only quotes deemed technically acceptable (either initially or as the result of discussions) will be considered for award. The ratings are defined in the following table.

Rating Description

Acceptable Quote clearly meets the minimum requirements of the solicitation. Only those quotes determined acceptable, either initially or as a result of discussion will be considered for award. Once deemed acceptable, all technical quotes are considered to be equal.

Unacceptable Quote does not clearly meet the minimum requirements of the solicitation. Quotes with an unacceptable rating will not be considered for award.

Table A-1

(2) Step Two – The offeror’s Price quote will be evaluated, for award purposes, based upon the total price proposed as annotated under Factor 2 – Price.

(3) Step Three – Award Decision. Award will be made the evaluated priced that offers the

Government the best value and is found to be a technically acceptable offeror, subject to a positive responsibility determination in accordance with FAR Part 9 and conformance of the offeror’s quote to the terms and conditions of the solicitation.

DISCLAIMER:

This is a request for the submission of a quote and does not constitute a contract or authorization to begin work. Nor does an offeror’s submission of a quote constitute a contract or authorize the individual or company to being work.

The Contracting Officer is the only person who can legally modify a resulting contract or obligate the Government for expenditure of funds. Costs shall be incurred by recipients of the solicitation in anticipation of receiving direct reimbursement from the Government.

Only the Contracting Officer has the authority to authorize deviations from the terms and conditions of any resulting contract, including deviations from specifications and requirements.

In the event the Contractor does deviate, without written approval of the Contracting Officer, such deviations shall be at the risk of, and any cost related thereto shall be borne by the

Contractor. Any matter concerning a change to the scope, prices, costs, terms, or conditions of this contract shall be referred to the Contracting Officer.

QUESTIONS AND ANSWERS:

NO. QUESTIONS ANSWERS

1 Does the Puppet Enterprise Solution Support service provider need to be a Puppet certified engineer?

No, but we expect that the service provider will have the expertise necessary to provide the capabilities and level of service that we require.

2 Does the Puppet Enterprise Solution Support service provider need to be a Service Delivery Partner of Puppet?

No, but we expect that the service provider will have the expertise necessary to provide the capabilities and level of service that we require.

3 Does the Puppet Enterprise Solution Support service provider need to be a Puppet professional services level II engineer?

No, but we expect that the service provider will have the expertise necessary to provide the capabilities and level of service that we require.

4 Does the Puppet Enterprise Solution Support service provider need to be DoD 8570 certified?

Yes. We expect the service provider will require privileged access to perform this service and therefore will need to have met the DOD 8570 certification requirements in order to be granted privileged access to

DOD systems. This is non-waiverable for privileged access.

NO. ADDITIONAL QUESTIONS ANSWERS

5 What is the current version of puppet community edition that your systems are currently running? In order to properly plan an upgrade path, we would need to know what version of the software is being used as they differ significantly in upgrading.

Open Source Puppet 5.5.8

6 Are you using an external node classifier (ENC) or static node definitions?

We are using ENC

7 Are you using plugins written in-house like custom facts, providers, or functions?

Yes, we have custom modules and facts

8 How many nodes are currently managed? around 600

9 How many nodes are expected in the future? 700+

10 Are they using a cloud service provider like AWS/Azure or virtualization platforms (VMWare)?

We are using VMWare

11 Is there currently a Git enterprise infrastructure in place, or does one be established/purchased?

This infrastructure will need to be established. It has already been purchased however.

12 Are there remote work opportunities for this project? The work will need to be performed onsite using GFE.

13 Are there any staffing requirements for this project? Our requirement is for services as defined by our PWS.

The vendor will need to determine the resources needed to fulfill these requirements.

14 Our understanding is that four staff members will be required to fulfill the follow roles:

Engineering Technical Services (2 CLINs for this role)

Onsite Resident Support (1 CLIN)

Project Management Services (1 CLIN)

Our requirement is for services as defined by our PWS.

The vendor will need to determine the resources needed to fulfill these requirements.

15 What do “enclaves” mean in the context of the following sentence from section 2.3 of the PWS within the RFQ? “Outcomes are focused on the ability to enforce compliant server baseline configurations within the TSO enclaves in order to reduce drift, increase security, and on-ramp the environment for self-provisioning capabilities.”

Enclaves are defined to separate productions environments from pre-production and testing environments. We have two enclaves, DEV/TEST and another for PROD. Generally, configuration of

DEV/TEST servers are like and kind to production for

QA purposes, however separate infrastructure is required for each enclave.

16 Our understanding is that enclaves are the terms for environments, i.e. ADTE and Prod. As per 4.0, A, 6. In the ‘deliverables’ section, what are the other tools in the environment with which Puppet integrates?

We use Atlassian products such as Jira and Bitbucket.

17 Is it acceptable to use a prebuilt image that meets STIG compliance with DISA Redhat Linux requirements?

No, we believe this approach is not acceptable for our needs because the number of pre-built images that would be required. For example, we need to be able to effectively manage exceptions and deviations from the

STIG.

18 What version of Puppet Community Edition is currently in use? Open Source Puppet 5.5.8

19 Are you using an external node classifier (ENC) or static node definitions?

We are using ENC

20 Are you using plugins written in-house like custom facts, providers, or functions?

Yes, we have custom modules and facts.

21 How many nodes are currently managed? around 600

22 How many nodes are expected in the future? 700+

23 Is a cloud service provider or virtualization platform (i.e: VMWare) being utilized?

We are using VMWare

24 Is there an existing Git infrastructure, or will a new Git workflow need to be established/purchased?

New instrastructure/new workflow will need to be established. These tools have already been purchased.

25 Are there remote work opportunities for this project? The work must be done onsite.

26 Are there any staffing requirements for this project? Our understanding is that four staff members will be required to fulfill the follow roles:

Engineering Technical Services (2 CLINs for this role) Onsite

Resident Support (1 CLIN) Project Management Services (1 CLIN)

Please confirm our understanding is correct.

The requirement is for the services as defined in our PWS.

These are roles that we believe are required, however the vendor will determine the most advantageous use of resources to deliver the services.

27 As per 4.0, A, 6. In the ‘deliverables’ section, what are the other tools in the environment with which Puppet integrates?

We use Atlassian tools such as Jira and Bitbucket.

28 Regarding DoD 8570 Certifications, what is the level, or category of certification required for this project?

Security + (or equivalent) is required for privileged users.

29 Do all members of the project, or only some require these certifications?

Only project members who require privileged access will need certifications.

Performance Work Statement (PWS) for

Puppet Enterprise Solution Support Services

Technology Services Organization (TSO)

1.0 Introduction

The Technology Services Organization (TSO) is an information technology services provider and system integrator, supporting a full range of IT services including software development, systems engineering, hosting, and operational services to organizations within and external to the

Marine Corps. TSO supports Programs and Resources Department, Manpower and Reserve

Affairs as well as a number of other Department of Defense (DoD) component organizations.

2.0 Scope

2.1. This PWS is intended to enable the TSO to provide automated configuration management of infrastructure in order to meet existing and emerging customer requirements.

2.2. To enable the Government’s innovative service delivery strategy, it is intended that this

PWS will provide the support needed to allow the TSO to leverage the capabilities of Puppet

Enterprise to implement a configuration management solution that will enable an enterprise configuration management capability in all of our virtual and physical environments.

2.3. Outcomes are focused on the ability to enforce compliant server baseline configurations within the TSO enclaves in order to reduce drift, increase security, and on-ramp the environment for self-provisioning capabilities. This project will implement a Puppet Enterprise solution that will harden and manage baseline Red Hat Enterprise Linux operating system configurations.

3.0 Tasks Requirements.

3.1. The Contractor shall review the existing Puppet Community Edition environment, existing code review, and transition planning from Puppet Community Edition to Puppet Enterprise

Edition.

3.2. The Contractor shall review the existing Puppet code as a source of Requirements and provide a recommendation for potential code reuse or refactoring for migrating to Puppet

Enterprise Edition.

3.3. The Contractor shall provide implementation of New Puppet Enterprise infrastructure to support Application Development and Testing Environment (ADTE) and Production (PROD) enclaves.

3.4. The Contractor shall provide Version Control System (i.e. Git) Integration and Creating

Management Workflows within the Puppet Enterprise Infrastructure.

3.5. The Contractor shall create Puppet development environments for testing new changes.

3.6. The Contractor shall provide Puppet Agent software deployment to all ADTE and PROD

RHEL servers.

3.7. The Contractor shall provide development of configuration management capabilities through

Puppet Enterprise Edition.

3.8. The Contractor shall support the dissolution Puppet Community Edition Environment through the development of a process for migrating environments to Puppet Enterprise Edition.

3.9. The Contractor shall successfully prove out the developed Community Edition to Enterprise

Edition migration process through a test/pilot migration.

4.0. The Contractor shall support enterprise adoption of Puppet Enterprise through issue resolution, knowledge transfer, and code development.

4.0 Deliverables.

A. The Contractor shall support the technical Subject Matter Experts (SME) to gather the requirements and for the following areas.

1. Environments and organizational policies around change management.

2. Deployment of virtual machines to support Puppet Enterprise architecture.

3. Environments that Puppet will be installed in and that Puppet will manage.

4. Sizing and performance requirements of Puppet Enterprise architecture based on the current and future number of nodes that Puppet will manage.

5. Supporting tools that will be used to manage Puppet code and code management workflows.

6. Configuration management and automation goals.

7. Integrations with other tools in the environment.

8. Create a basic Hiera (built in Puppet management tool) hierarchy to support data abstraction techniques in Puppet Enterprise.

9. Review the existing Puppet code as a source of Requirements and provide a recommendation for potential code reuse or refactoring.

B. The Contractor shall provide support to Implement New Puppet Enterprise Infrastructure.

1. Deploy the required virtual machine(s) in the environment according to the specifications required.

2. Validation of environment provided for Puppet Enterprise by performing an assessment of the environment that Puppet will be deployed to.

3. Installation of Puppet Enterprise LTS version or latest version in Monolithic configuration.

4. Replace Puppet Enterprise web console certificate with one issued by the DoD.

5. Configure Puppet’s role based access control to query the existing Active Directory infrastructure.

6. Deploy the Puppet Enterprise license key to the Puppet Enterprise environment.

7. Knowledge transfer in the following areas:

a. Puppet Enterprise architecture and deployment.

b. Using the Puppet Enterprise console to review the current state of nodes managed by Puppet.

c. Using the Puppet Enterprise console to initiate Puppet runs on a single node or a group of nodes.

d. Using the Puppet Enterprise console to execute a task on a single node or a group of nodes.

C. The Contractor shall provide the support services for Git Interrogation and Workflow.

1. Create Git repositories for support of the Puppet infrastructure.

2. Create a Puppet control repository in Git.

3. Setup and configure Puppet’s Code Manager to integrate with the control repository.

4. Create a skeleton role and profile architecture in the control repository for managing the Puppet Master server.

5. Build a basic Hiera hierarchy to include at least one role for managing the Puppet

Master server.

6. Review the basic code management and workflow requirements for delivering Puppet code to our various systems.

7. Review foundational Git concepts and usage with Government SME’s as appropriate.

8. Knowledge transfer in the following areas:

a. Support of Git system in the environment.

b. Configuration and use of Code Manager in the environment.

c. Concepts and usage of how Puppet installs and manages content in each environment (i.e. Puppetfile) and standard practices for deploying Puppet modules.

d. Concepts for integrating Puppet code management with the existing source control system and policies.

e. Using Puppet PDK tool for the creation and support of Puppet code elements.

D. The Contractor shall Create Puppet Development Environments.

1. Deploy Linux Machines to be used as Puppet development and test machines for the

PE deployment.

2. Deploy Puppet agents to the development machines and bring them under the management of Puppet using a development or test configuration.

3. Bring test machines under the management of Puppet Enterprise and create node groups in PE for management.

4. Knowledge transfer in the following areas:

a. Using Puppet environments to manage non production configurations.

b. Basic Puppet node classification patterns that will be used in this configuration.

c. Basic information for how to use the roles and profiles pattern in this Puppet deployment.

E. The Contractor shall provide Puppet Agent Deployment.

1. Work directly with the SME, determine an appropriate method, and plan for Puppet

Agent deployments to existing virtual machines. This will include providing guidance for the following Puppet Enterprise Agent install mechanisms.

a. Manual installation.

b. Scripted installs using the Puppet Master as the source.

c. Integrating with pre-existing tooling.

d.

2. Determine the required immutable metadata that will be embedded into the agent certificate when the agent is deployed.

3. The Contractor shall prepare the Puppet Master to be able to deploy the correct version(s) of the Puppet Agent to support automated provisioning of the software from the Puppet

Master server.

4. The Contractor shall provide assistance to deploy Puppet agents to existing virtual machines in the environment(s) that they desire to bring under the control of Puppet.

5. The Contractor shall provide assistance to determine the appropriate method for accepting node requests on a going forward basis.

6. The Contractor shall transfer knowledge in the following areas:

a. Procedures for deploying the Puppet agent along with required metadata

b. Methodologies for Puppet Agent certificate signing.

c. Deploying new and different versions of the Puppet agent software using the

Puppet Enterprise master server.

F. The Contractor shall provide Management of Linux Operating System Configuration.

1. The Contractor shall provide assist the SME to identify the configurations of the Linux

Operating System that will be managed by Puppet.

2. The Contractor shall develop and customize a Puppet Linux security module that will manage configurations on the Linux OS according to DISA’s Red Hat Enterprise 7

Security Technical Implementation Guideline (STIG) that help to meet the TSO’s security policies.

3. The Contractor shall create supporting documentation for the Linux Security module that align with Puppet’s best practices for module documentation.

4. The Contractor shall update security related documentation that supports the Linux security module.

5. The Contractor shall transfer knowledge in the following areas:

a. Usage of the Puppet Linux Security module.

b. Proper management of the module for future updates.

c. Using Hiera data to apply configurations to different layers in the hierarchy.

G. The Contractor shall Support Enterprise Adoption of Puppet Enterprise Through Issue

Resolution, Knowledge Transfer, and Code Development.

1. The Contractor shall provide ongoing support of the Puppet Enterprise environment(s) deployed as part of this project through the following tasks:

a. Code management automation and workflows.

b. Deployment of the Puppet Agent software.

c. Puppet module development, deployment or testing.

d. Provide guidance on Puppet module development or module integration through pair programming or code reviews.

2. The Contractor shall assist with the adoption of Puppet Enterprise in their organization using the following methods:

a. Development and implementation of processes for migrating code and environments from Puppet CE to Puppet EE.

b. Troubleshooting of the Puppet Enterprise environment.

c. Troubleshooting Puppet code.

d. Monitoring the Puppet Enterprise environment daily for performance issues and failed Puppet runs.

e. Assisting with integrating Puppet into other external systems.

f. Creation of or usage of existing Puppet Tasks that can be used to execute ad-hoc processes.

3. The Contractor shall assist with the enhancement and modification of the Linux Security

Puppet module to meet the security requirements as applications are being tested on the systems being managed by Puppet.

5. Project Close-Out.

1. The Contractor shall present a summary of work completed, review recommendations, leave behind documentation generated by consultants, and discuss other project close issue.

2. The Contractor shall provide a summary of work accomplished and recommendations for next steps.

6.0 Place of Performance.

The Puppet Enterprise Solution Support will be performed on premise at the following

Government location:

Technology Services Organization

135 N. Pennsylvania Street

Indianapolis, Indiana 46204

SMO Code: 36000TSO

Government POC: TBD

7.0 Contractor Work Week and Working Hours. Contractor normal working hours are anticipated to be from 0730 to 1630, Monday through Friday, unless requirements dictate otherwise. Exceptions can be permitted by the COR upon request and at the COR’s discretion.

Following is a list of holidays observed by the Government:

Name of Holiday Time of Observance

New Year’s Day .......................................1 January

Martin Luther King Jr. Day ......................Third Monday in January

President's Day ..........................................Third Monday in February

Memorial Day ...........................................Last Monday in May

Independence Day ...................................4 July

Labor Day .................................................First Monday in September

Columbus Day ..........................................Second Monday in October

Veteran's Day ............................................11 November

Thanksgiving Day .....................................Fourth Thursday in November

Christmas Day ..........................................25 December

8.0 Government-Furnished Property (GFP).

Property determined necessary for performance under the Puppet Enterprise Solution Support shall be provided by the Government. The Government shall ensure that any GFP is properly accounted for in accordance with appropriate Federal, DoD, or organizational regulations. The

Puppet Enterprise Solution Support service provider shall report any GFP not consumed during performance of this PWS to the COR or Government Technical Representative upon completion of the tasks, and the Government shall provide disposition instructions to the Contractor. The

Government shall provide space for any equipment the Puppet Enterprise Solution Support service provider is required to install in Government’s facilities, or other facilities (i.e. space for locked parts cabinet) required by the Puppet Enterprise Solution Support service provider to monitor and support the storage of equipment as required.

9.0 Facility Security Clearance.

The Contractor’s personnel shall possess or be able to obtain an appropriate facility security clearance, minimum of Top Secret eligibility, prior to work being performed.

a. The Puppet Enterprise Solution Support service provider under this contract may have access to systems with a relatively high risk for causing damage to Government facilities, systems and/or data if compromised. All Puppet Enterprise Solution Support service provider personnel performing on this contract must be a U.S. citizen and have a minimum IT position sensitivity of IT-I.

b. The Puppet Enterprise Solution Support service provider shall have certified personnel available to provide services on this contract within 5 working days of contract award.

c. Puppet Enterprise Solution Support service provider personnel must comply with local security requirements for entry and exit control for personnel and property at the Government facility.

d. Puppet Enterprise Solution Support service provider personnel will be required to comply with all Government security regulations and requirements. Initial and periodic security training and briefings will be provided by Government security personnel. Failure to comply with security requirements can be cause to deny access to USMC facilities.

e. Puppet Enterprise Solution Support service provider shall observe and comply with the security provisions in effect at the DoD facility. Identification shall be worn and displayed as required.

f. The Government retains the right to request removal of Puppet Enterprise Solution Support service provider personnel regardless of prior clearance or adjudication status, whose actions, while assigned to this contract, clearly conflict with the interest of the Government. The reason for removal will be fully documented in writing by the TSO and endorsed by the contracting officer.

10.0. Period of Performance.

The Period of Performance is: March 16, 2020 through March 15, 2021.

Please Provide the Following:

1. Tax Identification Number: _____________________

2. Company Registered in WAWF-RA (Wide Area Workflow):_______________

If Not, Will Your Company Register? ________________

3. Company Registered In System for Award Management (SAM):_______________

If Yes, What Is Your DUNS# and/or Cage Code: _______________

If No, Will You Register: ________________?

4. Company Considered Small or a Large Business under the NAICS Code. 541519

5. Delivery Time of Requested Items: ____________ Please show earliest delivery date possible.

6. FOB Cost If Applicable: _______________

A. NOTE: Is Freight (Fob) Included In Price? If Not, Please Indicate Price and Where It’s Being

Originated From: _______________

Discount Terms: ___________

Company Name and Address:

Company Point of Contact: _______________________________________________________

Company Telephone: __________________

Company Facsimile: ___________________

GSA Contract Number & expiration date: _________________________

Quoted price(s) submitted that are open market shall be marked “commercial pricing”.

The following FAR clauses and provisions apply to this acquisition and can be viewed at http://www.acquisition.gov/far:

52.204-7 System for Award Management

52.204-13 System for Award Management Maintenance (JUL 2013)

52.204-16 Commercial and Government Entity Code Reporting (JUL 2016)

52.204-17 Ownership or Control of Offeror (JUL 2016)

52.204-18 Commercial and Government Entity Code Maintenance (JUL 2016)

52.204-19 Incorporation by Reference of Representations and Certifications (DEC 2014)

52.204-24 Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment

52.204-25 Prohibition on Contracting for Certain Telecommunications and Video Surveillance

Services or Equipment

52.209-10 Prohibition on Contracting with Inverted Domestic Corporations

52.209-11 Representation by Corporations Regarding Delinquent Tax Liability or a Felony

Conviction under any Federal Law (FEB 2016)

52.211-6 Brand Name or Equal (AUG 1999)

52.212-1 Instructions to Offerors-Commercial Items (OCT 2018)

52.212-3 Offeror Representations and Certifications-Commercial Items (DEC 2019)

52.212-4 Contract Terms and Conditions--Commercial Items

52.219-1 Small Business Program Representations

52.225-13 Restrictions on Certain Foreign Purchases

52.225-25 Prohibition on Contracting with Entities Engaging in Certain Activities or Transactions

Relating to Iran-Representation and Certifications

52.232-39 Unenforceability of Unauthorized Obligations

52.232-40 Providing Accelerated Payments to Small Business Subcontractors

52.245-1 Government Property

52.233-1 Disputes

52.247-34 F.O.B. Destination

52.252-1 Clauses Incorporated by Reference (FEB 1998)

52.252-2 Solicitation Provisions Incorporated by Reference

252.203-7000 Requirements Relating to Compensation of Former DOD Officials

252.203-7002 Requirement to Inform Employees of Whistleblower Rights.

252.204-7012 Safeguarding of Unclassified Controlled Technical Information

252.211-7003 Item Unique Identification and Valuation (in all supply requirements)

252.225-7048 Export-controlled Items

252.232-7003 Electronic Submission of Payment Requests and Receiving Reports

252.232-7006 Wide Area Workflow

252.232-7010 Levies on Contract Payments

252.243-7001 Pricing of Contract Modifications

252.243-7002 Requests for Equitable Adjustment

252.247-7023 Transportation of Supplies by Sea

52.212-5 Contract Terms and Conditions Required to Implement Statues or Executive Orders –

Commercial Items ((b) 14, 25, 26, 27, 28, 33, 44, 48, 51, 57; (c) 11)

U3 DD 250 Receiving Report Submission Through Wide Area Workflow – Receipt and Acceptance

(WAWF-RA)

** Special Invoicing Instructions: Wide Area Work Flow – Receipt and Acceptance (WAWF-RA) **

WAWF-RA is the only method authorized by the United States Marine Corps to electronically process payment requests. Compliance with WAWF-RA is mandatory. Include in each offer a statement acknowledging that you are WAWF-RA compliant. In order to get registered with WAWF-RA, visit https://wawf.eb.mil/. In order to WAWF-RA you must designate an Electronic Business Point of Contact

(EB-POC) to serve as the group administrator within you company.