B02 1 RFQ 12314423Q0144_Instructions to Offerors_STRATUS Pool 3.docx

REQUEST FOR QUOTES NO. 12314423Q0144

STRATUS BASIC ORDERING AGREEMENT (BOA)

POOL 3: SOFTWARE AS A SERVICE (SaaS)

United States Department of Agriculture (USDA) Office of the Chief Information Officer (OCIO) Digital Infrastructure Services Center (DISC)

Solicitation Contents:

Section 1: Solicitation Information, Dates, and Deadlines Section 2: Overview of Solicitation Section 3: Submittal Preparation Instructions to Offerors Section 4: Quote Evaluation Criteria Section 5: Contract Award Section 6: Solicitation Attachments

Section 1.0 Solicitation Information, Dates, and Deadlines

1.1 Solicitation Amendment History

The Government reserves the right to revise or amend the specifics or the solicitation prior to the closing time. Any amendments issued to this solicitation will be made available through https://sam.gov. It is the Offeror’s responsibility to check for amendments. It is the sole discretion of the Government to determine if the solicitation closing date will be extended due to an amendment. In such cases, the amendment will include the new closing date and time.

1.2 Solicitation Points of Contact / Contract Administration

Points of Contact: The following points of contact are to be used to communicate with the Government during the Basic Ordering Agreement (BOA) duration. During solicitation through award, the Contracting Officer shall be the primary point of contact:

Contracting Officer (CO):

Name: Christine Wallace Email: Christine.Wallace@usda.gov Phone: 970-295-5353 Contracting Officer’s Representative (COR):

Designated in writing by the Contracting Officer at time of award.

1.3 Questions

1.3.1 Questions.

Questions shall be submitted via email to the CO utilizing Attachment E – Questions and Answers Template. The deadline for submitting questions is 3:00 PM ET on 10/11/2023.

1.3.2 Government Responses to Questions.

The Government will publish answers to offeror questions via an amendment to this solicitation. Please be advised that the Government reserves the right to transmit those questions and answers of a common interest to all prospective offerors. The government will evaluate questions and answers to determine if a second round of questions is required. If the government determines a second round of questions is required for a particular phase, the dates will be identified via amendment.

1.4 Due Date and Delivery

1.4.1 Due Date

Quotes must be submitted on or prior to 5:00 PM ET on 10/27/2023. USDA will not accept quotes received by fax or mail.

Offerors are to submit quotes electronically via email directly to the CO. Subject line of the submittal email shall be formatted as follows: RFQ #12314423Q0144, Offeror Name.

Section 2.0 Overview of Solicitation

2.1 Background/Executive Summary

2.1.1 Current Environment and Contract Vehicles

The United States Department of Agriculture (USDA) IT environment is decentralized with a federated governance model. The department-level Office of the Chief Information Officer (OCIO) operates the Digital Infrastructure Services Center (DISC) as well as enterprise-wide networking, cybersecurity, and customer support services. USDA has eight Mission Areas (MAs) each with its own Assistant CIO. Each MA has multiple agencies each with varying levels of IT hierarchy.

DISC provides cloud brokerage services to the USDA MAs as a consolidated point of entry, established as a mandate, for hyperscale Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) procurements through the Cloud Brokerage Office (CBO).

For Software as a Service (SaaS) and cloud-related labor and managed services there is currently no consolidated approach, and they are not within the scope of the CBO mandate. USDA has been using multiple USDA contracts and Government Wide Acquisition Vehicles (GWACs) for these services. Salesforce SaaS is purchased centrally through DISC at the enterprise level whereas many other SaaS are purchased through the MA or agency within the MA. Labor and managed services are even more decentralized with the least degree of shared services approach at the enterprise level.

Beyond the cloud brokerage function, DISC is a managed service provider offering data center hosting, cloud, and applications development solutions to the USDA MAs as well as to other federal agencies. DISC operates enterprise class Level IV data center facilities. In addition, it manages the AgCloud program delivering highly scalable enterprise-level shared services across multiple public cloud platforms including Amazon Web Services (AWS), Google Cloud Platform (GCP), Microsoft Azure, and Oracle Cloud Infrastructure (OCI) and a private VMware vCloud platform. AgCloud facilitates USDA’s efforts to migrate applications to a cloud environment, allowing the consolidation of USDA data centers to support the Federal Data Center Consolidation Center Consolidation Initiative (FDCCI), which in August 2016 was renamed the Data Center Optimization Initiative by OMB (see Memorandum M-16-19). Unlike CBO, USDA Mission Areas are not compelled to use the AgCloud program.

2.1.2 Challenges of the Current Environment

While the current DISC/CBO model has allowed for flexibility in cloud adoption, there are drawbacks. The model effectively allows each MA to have a direct line to various contracts. Silos have been raised between the various customer cloud and service implementations, causing a lack of visibility and negated scalability, metric collection, and an inability to realize a cohesively to create an enterprise architecture. The extent of this issue is even larger for SaaS and labor/managed services. Lack of demand aggregation and not taking advantage of the market forces have resulted in inconsistent and often higher prices for these services as compared to other exceptionally large enterprises. The complexity of moving large applications, vast sets of data and workloads to the cloud often requires a multifaceted approach involving systems, platforms and tools across IaaS, PaaS, and SaaS offerings, as well as labor support services for development, integration, and ongoing operations.

2.1.3 Evolution of DISC and CBO

The USDA is maturing from early phases of OMB’s “Cloud First” brokerage into a true cloud solutions organization that enables DISC to offer well curated, managed services that better control costs, are properly secured, promote reusability, and significantly increase speed to market for customers. In support of this new complex solutions capability, DISC is leveraging industry best practices to create a set of new operating models, processes, and a roadmap for the growth of both CBO and AgCloud to meet the ever-increasing “Cloud Smart” demands of USDA MAs, and external federal agency customers to create a true USDA Digital Enterprise.

As DISC evolves to meet the customer demands, it will increasingly incorporate commercial cloud capabilities into AgCloud as curated, managed services, and further extend them with mature platform and DevSecOps capabilities. CBO scope is also evolving to include robust shared services across all cloud and associated labor/managed services.

This posture creates increases efficiencies across the entire spectrum of USDA IT operations, allowing MA Associate CIOs to focus on mission applications while consuming DISC services for infrastructure and platform support. Over time, USDA will be able to save costs and better allocate resources, evolving USDA’s IT enterprise to meet the needs of the MAs while supporting Federal Information Technology Acquisition Reform Act (FITARA), Federal CIO Council’s Cloud Smart policy and other federal guidance.

2.1.4 STRATUS BOA Business Rules

A Pre-solicitation Notice for the USDA STRATUS Cloud Program was published under 12314423R0012 on 03/23/2023. The USDA STRATUS Program Sources Sought Notice for Pool 3 was published under Notice ID 12314423R0012 (Related Notice 12314423R0010) on April 12, 2023. A potential offeror is not excluded from submitting a quote if they did not provide a response to the pre-solicitation notice.

This Request for Quote (RFQ) 12314423Q0144 is a combined synopsis/solicitation for competitive action conducted IAW Federal Acquisition Regulation (FAR) Part 16.703. The intent of this action is to allow interested offerors an opportunity to submit a quote for evaluation to obtain an executed USDA STRATUS Cloud BOA. Any quote submitted in responses to this RFQ must be in compliance with the terms and conditions in the RFQ and attachments. Failure to comply with the terms of the solicitation may result in the quote being rejected or receiving an unfavorable evaluation.

The Government will execute no-cost BOAs to offerors in accordance with the criteria stated in the solicitation.

2.1.5 BOA Execution Rules

A basic ordering agreement is not a contract pursuant to FAR 16.703 (a)(3).

A BOA Task Order will become a binding contract; (1) upon acceptance of proposal and award if a request for proposal (RFP) is utilized or (2) upon issuance of a Task Order if a request for quote (RFQ) is utilized.

A STRATUS BOA term will be for up to Ten (10) years beginning from the effective date of the initial BOA award. All future BOA onramps will align with the initial BOA expiration date, which would result in a BOA term for the remaining BOA ordering period.

IAW FAR 16.703(c)(2), a BOA shall be reviewed annually before the anniversary of its effective date and revised as necessary to conform to the changing requirements of the FAR and other applicable statutes and regulations. Only the BOA level Contracting Officer is authorized to execute, modify or conduct the annual review of a BOA resulting from this solicitation.

BOAs shall be changed only by modifying the agreement itself and not by individual orders issued under it. Modifying a BOA shall not retroactively affect orders previously issued under it. The terms of the BOA may need to be revised before the annual review due to changes in mandatory requirements.

The execution of a BOA does not guarantee the Government will place future task orders with the offeror.

Since BOAs are not contracts, either the Government or the Contractor may elect not to renew the BOA at the annual review or at any time during the performance period. The Government reserves the right to cancel the BOA if doing so is considered to be in the Government's best interest.

The USDA will assess the cloud landscape at least annually to determine if an onramp RFQ will be issued. The USDA will release Onramp RFQs (Step 2) on an as needed basis to allow interested offerors an opportunity to submit a quote for evaluation to obtain an executed USDA STRATUS Cloud BOA. The Government will execute no-cost BOAs in accordance with the solicitations criteria in the onramp RFQs.

USDA BOA Operating Rules

· All USDA agencies are authorized to place orders against the STRATUS BOAs. All orders will be placed by an agency procuring contracting officer (PCO).

· A BOA Task Order will become a binding contract; (1) upon acceptance of proposal and award if a request for proposal (RFP) is utilized or (2) upon issuance of a Task Order if a request for quote (RFQ) is utilized.

· Pricing for all Task Orders will be established at the task order level.

· Delivery terms and conditions will be established at the task order level.

· Payment procedures will be established at the task order level.

· Failure to reach agreement on price for any order issued before its price is established is a dispute under the Disputes clauses included in the BOA.

2.2 Objective

2.2.1 STRATUS Cloud Strategy

A centerpiece of USDA’s strategy to address the stated challenges of the current environment is the establishment of STRATUS as its own cloud acquisition vehicle that best fits its IT governance model, the emerging cloud operating models, and the vision for a true USDA Digital Enterprise.

The STRATUS key objectives are:

· Full visibility, across customers, into inventory of services and the consumption data with access to deep data analytics.

· Lower cost through aggregating demand and higher competition resulting in both innovative pricing models and lower unit prices.

· Improved cost accountability and reporting, especially on labor services.

· Ordering and billing transparency, streamlining and automation implemented uniformly across all acquisitions under this vehicle.

· Flexibility to allow different cloud operating models.

· Future-proofing this vehicle to align with USDA strategic goals.

· Drive toward a holistic, secure enterprise enabling agile delivery of capabilities through DevSecOps and GitOps best practices.

· Optimization of IaaS, PaaS, and SaaS utilizations across USDA.

· Enabling rapid growth and migration of the remaining on-premises workloads to cloud.

· Robust development of shared services including data sharing throughout the Enterprise Cloud Vendor Management (ECVM) program.

· Increased DISC capabilities for other federal agency customers.

· Unified USDANet network access and implementing future architectures (e.g., Zero Trust).

See Attachment A for the Pool 3 Statement of Objectives.

2.2.2 Pool Structure and Rationale

STRATUS is divided into three pools of services. Pool 1 is for all the products that the hyperscale Cloud Service Providers (CSPs) may offer including their professional or technical support services as well as their marketplace products. It should be noted that STRATUS does not prescribe definitions or categories for IaaS, PaaS or SaaS under Pool 1 and simply refers to this pool as CSP Services. Pool 2 is for all cloud-related labor and managed services including development, integration, management, and operational support. Pool 3 is for SaaS offerings (not including native hyperscale CSP services under Pool 1) including professional and technical support services provided by the SaaS Original Equipment Manufacturer (OEM).

There are several reasons for this division. The intention is for hyperscale CSP services to fit into one pool (Pool 1) and have no need for hyperscale CSPs to bid under different pools. The divisions of Pools 2 and 3 are driven by the desire to have clear separation and cost accountability of software licenses (Pool 3) and reseller or systems integrator labor services (Pool 2).

There may be exceptions to this division. For example, in cases where the Pool 2 reseller/integrator would offer capabilities they might have uniquely built on top of platforms or software that otherwise is under Pool 1 or 3. USDA may define at the task order level if they seek managed services or if they only want labor services under Pool 2 and that they will purchase IaaS/PaaS/SaaS under their respective pools and furnish them to the Pool 2 provider.

2.2.3 Cloud Operating Models

A key objective of STRATUS is the ability to support different cloud operating models given the nature of the IT governance within USDA and the current and evolving models in the Mission Areas (MAs) influencing CBO services. The table below shows possible operating models.

The first model is the current AgCloud program where various functions at the USDA enterprise level collectively provide full managed service offerings. The second model is a small variation of the first model where the customer uses enterprise offerings for all services except the Operations and Maintenance (O&M). Under both models the Task Orders are owned by OCIO-DISC allowing the highest levels of demand aggregation and efficiencies.

The next two models, Models 3 and 4, are similar in that the customer utilizes their own solutioning and O&M resources but differ significantly: under Model 3 DISC owns the task order and under Model 4 the customer does. Model 4 maintains the current level of control by the customer, and Model 3 eliminates the additional burden of soliciting and managing a task order by leveraging existing DISC task orders. This approach applies to all three pools, however, for Pools 1 and 3 it is anticipated that DISC would establish Task Orders for its own AgCloud purposes early after the start of STRATUS covering all needed services, but for Pool 2 DISC may need to establish new Task Orders specific to the customer development or integration labor requirements. Model 4 is the closest representation to how the CBO has historically functioned in the USDA since 2014.

Models 5 and 6 represent cases where STRATUS is not used. Under Model 5 CBO still provides its brokerage service through access to other cloud GWACs. Under Model 6 there is no CBO engagement and therefore this model only applies to Pools 2 and 3 given the current mandate that states all IaaS/PaaS services must be brokered by the CBO.

2.3 Acquisition Details / General Contract Terms

2.3.1 This solicitation is a Request for Quotes being issued under NAICS codes 513210 Software Publishers (size standard $47M), 541519 Other computer Related Services / IT Value Added Resellers (size standard 150 employees). The Government anticipates executing up to 25 BOAs to the most capable mix of large (Unrestricted) and small businesses (Restricted). The Government anticipates the award of 10 Unrestricted agreements and 15 Restricted agreements. The Government reserves the right to award fewer or more BOAs.

2.3.2 Quotes will be evaluated and placed on either an Unrestricted or Restricted track, determined by the Offeror’s identified business size as supported by its repsresentations and certifications. The quote requirements are the same for both tracks but Unrestricted (large business) and Restricted (small business) offerors will not be evaluated against each other.

2.3.3 Individual task orders may be fixed price, firm fixed price, time and materials, labor hour, or a hybrid of any of these contract types.

2.3.4 This is a competitive action conducted IAW with Federal Acquisition Regulation (FAR) Part 16.703.

2.3.5 This is not a competitive source selection that is subject to FAR 15.3 procedures.

2.4 Period of Performance

2.4.1 The ordering period for the BOA is 10 years from date of award.

2.5 Solicitation Phases

This is a single phase acquisition where award will be made from the quotes submitted. There will not be additional phases.

2.6 Trade-Off

This acquisition does not have a tradeoff.

2.7 Small Business Size Standards

2.7.1 Size Standards

Small Business Administration (SBA) size eligibility standards are located in Title 13 of the Code of Federal Regulations (CFR) Part 121 (13 CFR Part 121). To ensure that an Offeror qualifies as an eligible small business, prospective Offerors are highly encouraged to review this regulation in its entirety. For information on various SB programs offerors are encouraged to review the following sections in their entirety 124, 125, 126, 127 and 128.

An Offeror with questions regarding size eligibility standards should contact its legal counsel and/or SBA Office. The SBA is the sole authority for making determinations of small business status for small business programs.

These determinations are binding on the Offeror and on the Contracting Officer.

Generally, SBA determines the size status of an entity as of the date the entity submits a written self-certification that it is small to the procuring agency as part of its initial offer for a contract or agreement.

As part of its BOA quote offerors will be required to identify their size standard and submit supporting representations and certifications including identifying all entities that will be a part of the offeror response and the role they will perform so they can be assessed against either the LB or SB track as appropriate.

2.8 Incurring Costs

This solicitation does not commit the Government to pay any cost incurred in the submission of the quote or in making necessary studies of designs for the preparation thereof, nor to contract for services or supplies. The Contracting Officer is the only person who can legally obligate USDA for the expenditure of public funds in connection with this procurement.

2.9 Proprietary Data

USDA recognizes that some information requested (e.g. pricing data), may be confidential. Each page of the Offeror's quote shall be reviewed and marked as to proprietary data content by the Offeror in strict compliance with FAR 52.215-1 (see also FAR 3.104-4). A single blanket statement at the front of the quote is not acceptable. Failure to mark every page will subject your quote to public release through Freedom of Information Act (FOIA) requests.

2.10 News Releases

The Offeror shall not make any news release pertaining to this procurement without prior USDA approval.

2.11 STRATUS On-Ramp and Off-Ramp Program

2.11.1 On-Ramping

The Contracting Officer has determined that it is in the Government’s best interest that at all times during the term of the BOA there are sufficient numbers of BOA holders to compete for Task Orders to meet customer requirements. Over time, the total number of BOA holders in a pool may fluctuate due to various reasons, including but not limited to, competition levels on Task Orders, small business (SB) BOA holders outgrowing their size standard, consolidation in industry, mergers & acquisitions, significant changes in the marketplace, advances in technology, general economic conditions, and the Government’s exercise of the off-ramp process. Given this, the Government intends to evaluate BOA holders’ participation in the ordering process at least annually to determine if it is in the Government's best interest to initiate an open season to add new BOA holders to the BOA pool. The Government reserves the right to initiate an open season more than annually if the Contracting Officer determines it is in the best interest of the Government.

BOA holders are hereby notified that utilization of any on-ramping procedure below does not obligate the Government to perform any other on-ramping procedure. The USDA intends to robustly manage the On-Ramp and Off-Ramp Program to ensure robust Task Order competitions. It is in the best interest of the Government that Task Order competitions are vibrant.

2.11.2 Open Season

USDA will determine whether it would be in the Government’s best interest to initiate an open season to add additional vendors to the BOA pool at any time, subject to the following conditions.

· An open season RFQ will be published in https://sam.gov.

· An open season solicitation is issued under current Federal procurement law.

· The RFQ identifies the total approximate anticipated number of new awards the contracting officer intends to make. The number of awards is at the sole discretion of the contracting officer. The Contracting Officer may decide to award more or fewer BOAs than the number anticipated depending on the quality of the quotes received.

· Any Offeror that meets the eligibility requirements set forth in the open season solicitation may submit a quote in response to the solicitation. However, existing BOA holders may not hold or be a teaming member of more than one BOA per Pool at any time.

· The award decision under the open season RFQ is based upon generally the same evaluation factors/subfactors as the original RFQ. Changes can be made to improve the quality of quotes received and the evaluation process as a result of lessons learned from the previous RFQs.

· The terms and conditions of any resulting BOAs from a new RFQ are materially the same as existing BOAs.

· The period of performance term for any new BOAs is coterminous with the existing term for all other BOA holders. Immediately upon on-ramping, the BPO holder is eligible to submit a quote in response to any task order solicitation and receive task order awards with the same rights and obligations as any other BOA holder.

2.11.3 Off-Ramping due to change in small business size standard This multiple-award BOA has small business set asides available to PCOs. For those SB BOA holders who have outgrown their small business size standard, for any reason including a certifying event, the SB BOA holder will notify the BOA CO immediately. BOA holders shall continue performance on any active Task Orders under their small business BOA, including exercise of options at the Task Order level at the discretion of the CO, until all Task Orders are closed out. The BOA holder will no longer be able to compete under the small business set asides but will be eligible to compete as a large business BOA holder.

2.11.4 Off-Ramping

The Government reserves a unilateral right to discontinue offering a BOA holder an opportunity to compete for task orders, i.e., offramp non-performing or non-satisfactorily performing BOA holders. BOA holders that are Off-Ramped will not be eligible to compete for future Task Orders but shall complete work on their current Task Orders.

Off-ramping methods may result from any of the following conditions:

· Permitting the BOA term to expire at the annual review instead of exercising an option period. This is at the sole discretion of the Government. BOA holders shall continue performance on any active task orders until they are closed out.

· Debarment, Suspension, or Ineligibility as defined in FAR Subpart 9.4.

· BOA holders who fail to meet the standards of performance, deliverables, or compliances or receives less than satisfactory performance as defined in FAR 42.1503.

· BOA holders who fail to remain competitive for Task Orders.

· BOA holders who fail to provide responses to TO RFQs. A no quote acknowledgement is mandatory if a contractor is not responding to a TO RFQ.

· Any reason deemed in the best interest of the Government. This is at the sole discretion of the Contracting Officer.

2.12 Contract Line-Item Number Structure (CLINS)

CLINS determined within individual BOA Task Orders.

Section 3.0 Submission Instructions Provided to Offerors

3.1 Guidelines and Formatting

The following is established as the specific information and format required for any Offeror submission. Incomplete quotes are not acceptable. Each Offeror must submit one electronic quote to the CO via email.

Any quote submitted in response to this solicitation must be in compliance with the terms and conditions outlined in the solicitation, Statement of Objectives (SOO), and all applicable attachments. All claimed capabilities to meet the requirements shall be realistic and are subject to verification by the Government. Non-conformance with these instructions may result in rejection of the quote or an unfavorable quote evaluation or being deemed ineligible for award.

To aid in the evaluation process, quotes shall be clear, concise, comprehensive, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The quote should not simply rephrase or restate the Government's requirements but, rather, shall provide convincing rationale and examples to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their experience and will base its evaluation on the information presented in the Offeror's quote.

Submissions shall be single-spaced with a double space between paragraphs, formatted to fit on 8.5 by 11 inches paper (not including the Price Excel workbook submittal), have a minimum of one-inch margins on the top and bottom and 3/4-inch side margins, using no smaller than an 11-point font for ALL TEXT to include any text contained in a table or graphic. Tables and graphics may be landscape. Offerors shall number each page. All quote information shall be submitted in either MS Word, MS Excel or a searchable PDF as described in these instructions. Do not submit duplicates in all formats.

It is the sole responsibility of Offerors to ensure that electronic files submitted are virus free and can be opened and read by the Government. Quotation submissions shall not be locked, encrypted, or otherwise contain barriers to opening. The Government is under no obligation to seek clarification regarding electronic quotation submissions if submissions cannot be opened or accessed. Page limitations shall not be circumvented by including inserted text boxes/pop-ups or internet links to additional information; such inclusions are not acceptable and will not be considered.

3.2 Volumes and Page Limits

The Offeror’s response to this solicitation shall comply with the following format and submission requirements. All quotes must be submitted in the following volume format. Phase One consists of 2 separate volumes: the transmittal and cover letter with required documents (Volume 1) and Prior Experience (Volume 2). Volumes shall be 2 separate volumes as outlined below. Offerors shall not combine any volumes of their quotes.

Responses to this solicitation will be formatted and evaluated against the following factors:

· Volume 1: Transmittal Cover Letter and Required Documents.

· Volume 2: Prior Experience.

The following table outlines the specific page requirements for each volume. Each section below provides specific details on what is required to be submitted for each volume and how information like cover letter, table of contents, and prior experience documents are to be included.

Volumes and Page Limits

To be indexed with a table of contents

- All required documents

PRIOR EXPERIENCE SUMMARY

· Cover Letter: 1

· Table of Contents: 1

· Prior Experience Summary: total 3 pages

· SaaS List: 1 page

· Summary: 2 pages

PRIOR EXPERIENCE REFERENCES

· Prior experience Reference Sheet (Attachment F): 1 page

· Offeror provided write-up: 2 pages per reference Maximum of 3 pages per reference.

3.3 Transmittal Cover Letter and Required Documents (Volume 1) The offeror’s transmittal and cover letter for the quote must contain the name, phone number and email address of the person to be contacted concerning any matter related to the solicitation.

Include the following in this section:

· Point of Contact (name, email, phone) for the representative the government should contact with questions regarding the quote.

· Company name and mailing address.

· Unique Entity ID SAM number.

Offerors must be registered and active in the SAM database. If registration is not active at the time of receipt of quotes the offeror is not eligible for award. It is the sole responsibility of the offeror to complete SAM registration. Offerors may obtain information on registration at https://sam.gov.

· Date submitted and quote expiration date. Quote must be certified to be good for 180 days from closing date of RFQ.

Additional Required Documents (each to be submitted as attachments to the Cover Letter)

· Exceptions/assumptions to the terms and conditions of this solicitation package shall be identified on a separate page within the cover letter submission. Exceptions/assumptions to the terms and conditions may disqualify your submittal for evaluation and award consideration.

· If no exceptions/assumptions to the terms and conditions of this solicitation package are taken by the offeror, then a separate written statement must be made affirming this.

· Acknowledgment of any RFQ amendments issued by the Government. Acknowledgement of amendments may be accomplished by a signed statement identifying each amendment by number and acknowledging they were included in the preparation of the quote.

· Representations and Certifications of the entity submitting the quote, from https://sam.gov and any other Representations and Certifications required by the RFQ.

· All Offerors are required to identify the size standard under which they are submitting a quote. If the Offeror is submitting quote as a Joint Venture (JV) or a Prime/Subcontractor team include all specific information detailing all entities that will be a part of the offeror response, the role they will perform and the size standard under which they are submitting a quote.

· Offerors will be required to submit written proof of their entity affiliations and release from all subcontractors/teaming partners, etc.

3.4 Prior Experience (Volume 2)

The Government will assess its level of confidence the Offeror will be successful in performing the task areas based on its Prior Experience. The Offeror shall provide a detailed narrative of up to three (3) examples of contracts within the last 3 years from date of solicitation release that clearly demonstrate results showing how each prior experience example correlates to the requirements as described in the SOO. Each Prior Experience Reference example submitted shall include a completed Prior Experience Reference Sheet (Attachment F). The burden of providing thorough and complete demonstrated prior experience remains with the offeror. Prior Experience will also be evaluated for accuracy, relevancy, and demonstrated ability of the Offeror to achieve the goals and desired outcomes specified in the SOO. Offerors shall demonstrate experience with across the task areas identified in the SOO (Attachment A).

USDA is most interested in examples of work with actual results that relate to the SOO scope. These examples should demonstrate achieving cost savings, increasing business performance, adding innovation, and using modern/current innovative tools and methodologies. USDA is more interested in demonstrated success achieved and similarity of the Prior Experience Reference examples to the SOO scope areas more than the quantity of examples. This information needs to be sufficiently detailed so that the evaluators can make a determination based on the Offeror’s experience. USDA will not contact the reference to obtain detail lacking from the Offeror’s response.

Evaluators may validate the provided prior experience submission information. The Government reserves the right to verify prior experience with the offerors reference. Verification from client organization may include a phone interview, survey or any other method in the best interest of the Government at the sole discretion of the Government.

At least 2 of the Prior Experience Reference examples must be from the proposed prime Offeror, performing as a prime contractor. Prior Experience is not limited to Federal contracts, or performance as a prime contractor.

Attachment D “Prior Experience Cover Sheet” shall be completed and submitted for each of the Prior Experience examples submitted. Offerors shall not alter the attachment or add additional content; doing so may disqualify an Offeror’s quote from consideration for award.

USDA has identified an initial list of desired SaaS for Pool 3. This is not an exhaustive list of all SaaS that may be required throughout the Pool 3 BOA period of performance. Offerors are not expected to propose all available licenses for each SaaS at the BOA level; specific licensing requirements will be communicated at the Task Order (TO) level.

· Akamai

· Anitian

· Appian

· Atlassian

· Cohesity

· FEITH

· NetApp

· Puppet

· Redhat

· Salesforce

· SAP

· ServiceNow

· SonarQube

The response shall address the following sub-factors, which the Government has a preference for in order of importance:

1. Sub-factor 1. Direct relationships with SaaS Providers (“OEM”) and;

2. Sub-factor 2. Resellers with breadth of coverage of multiple SaaS.

Offerors shall provide evidence of ability to deliver SaaS which may be in addition to list above. The Prior Experience Summary should include SaaS licensing provider/partnership information (when established, provider/certified reseller level(s) and definition(s), overall Prior Experience write-up of various customers, methods, etc.). Quotes should address the following:

a. Ability to provide any or all of the SaaS identified above. Must provide authorized reseller information as applicable. Note that an “OEM” SaaS provider who only sells their own software will not be penalized for lack of breadth.

b. Experience providing any or all of the SaaS identified above in the last 3 years of solicitation release.

c. Describe other SaaS your organization typically provides to customers.

d. Describe the Offeror’s process and ability when requested by a customer to provide new SaaS which the Offeror has not previously provided.

Provide evidence of ability to deliver added value:

e. Best practices the Offeror deploys to help an organization with enterprise buying management approaches.

f. How the Offeror provides visibility into usage data, licenses, and billing across multiple distinct enterprise customers.

g. How the Offeror enables coordination with OEM SaaS provider.

Section 4.0 Quote Evaluation Criteria Provided to Offerors

4.1 Compliance Review

Quotes will be screened for compliance with all submission requirements as detailed in the solicitation. Quotes that do not meet these criteria will be eliminated from further consideration.

4.2 Prior Experience (Volume 2)

Prior experience will be rated using Confidence ratings. The prior experience assessment will result in an overall confidence rating. The evaluation team will assemble members to reach consensus on the ratings and finding for each submission in accordance with the solicitation. This confidence assessment represents the Government evaluation team’s judgement of the offeror’s ability to successfully perform based on the understanding of the requirements based on the offeror’s demonstrated prior experience.

4.3 Confidence Ratings Definitions

The confidence ratings are defined as follows:

Confidence Rating Definition

High Confidence (Low Risk) The Government has high confidence the vendor understands the requirement, proposes a sound approach, and will be successful in performing the contract with little or no Government intervention.

Some Confidence (Moderate Risk) The Government has some confidence the vendor understands the requirement, proposes a sound approach, and will be successful in performing the contract with some Government intervention.

Low Confidence (High Risk) The Government has low confidence the vendor understands the requirement, proposes a sound approach, or will be successful in performing the contract even with Government intervention.

4.4 Evaluation Notices

4.4.1 The Contracting Officer will draft all evaluation notices (EN), maintain the EN log and coordinate all correspondence with vendors during the evaluation.

4.4.2 The Government reserves the right to make an award based on an Offeror’s initial quote, so Offerors should provide their best solution in its response to the solicitation. The Government reserves the right to conduct exchanges with Offerors if the Contracting Officer determines them to be necessary. However, once the Government determines which Offerors provide the best overall value, the Government reserves the right to communicate with only those Offerors to address any remaining issues, if necessary, and finalize a BOA .

4.5 Contractor Administrative Assistance in Quote Evaluation

Offerors are advised that USDA has contracted with ViaTrie LLC for administrative assistance in the evaluation of quotes submitted in response to this solicitation. With these contractors’ inherent knowledge of the STRATUS program, and no organizational conflicts of interest (financial or otherwise), USDA expects to achieve a fair and objective evaluation for BOA awards.

Contractor assistance will be in an administrative capacity only and evaluations will be conducted solely by USDA personnel.

Contractors will have access to all information contained in the Offeror’s proposal and will be subject to all required conflict of interest, standards of conduct, and confidentiality restrictions through a Non-Disclosure Agreement.

Section 5.0 BOA Award

5.1 Select Most Capable Offerors and Finalize Apparent Awardees Once the Government determines which offerors are the most capable of satisfying the Government’s requirements, the Government reserves the right to communicate with only those offerors to address any remaining issues, if necessary, and finalize a BOA with the offerors.

Determination to enter into BOAs will be made IAW the procedures specified in the RFQ and after an assessment by the Government once all phases of evaluation are completed. A BOA may be entered into with an Offeror deemed responsible IAW FAR Part 9.1, as supplemented, whose quote conforms to the RFQ’s requirements (to include all stated terms, conditions, representations, certifications, and all other information required by the RFQ instructions) and is judged, based on the evaluation factors, as most capable of satisfying the Government’s requirements.

5.2 Award

For purposes of this RFQ, most capable means the expected outcome of an acquisition that, in the Government's estimation, provides the greatest overall benefit in response to the requirement. Offerors should therefore propose their best approach to meeting the requirements of the RFQ. The Contracting Officer shall make an assessment of the Confidence ratings and determine the most capable of satisfying the Government’s requirements.

Section 6.0 Solicitation Attachments

6.1 Attachments

Attachment A: Statement of Objectives Attachment B: Security Requirements Attachment C: Requirements for Billing, Automation, and Data Reporting Attachment D: Provisions and Clauses Attachment E: Questions and Answers Template Attachment F: Prior Experience Reference Sheet Attachment G: Invoice Format Attachment

RFQ #12314423Q0144 USDA STRATUS Cloud, Pool 3 SaaS Page 1 of 3 Instructions to Offerors image2.png image1.png