EMACAO - RFI Questions BetaSAM.docx

DOCX document 22 KB Posted

Attached to
DA01 Messaging and Authentication Engineering Hines Support Services - Renewal
Solicitation number
36C10B21Q0358
Issued by

View the file

Other files

File Type Posted
(P01) T4NG TO PWS EMACAO RFI draft.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Request for Information (RFI) Enterprise Messaging, Collaboration, Authentication and Office 365 (EMCAO) Services Support

VA-21-00044625

1. Introduction

This RFI is for planning purposes only and shall not be considered an Invitation for Bid, Request for Task Execution Plan, Request for Quotation or a Request for Proposal. Additionally, there is no obligation on the part of the Government to acquire any products or services described in this RFI. Your response to this RFI will be treated only as information for the Government to consider. You will not be entitled to payment for direct or indirect costs that you incur in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter negotiations to award a contract. No funds have been authorized, appropriated or received for this effort. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. The Government does not intend to pay for the information submitted in response to this RFI.

The North American Industry Classification System (NAICS) for this requirement is 541512 with a size standard of $30 million.

2. Submittal Information:

All responsible sources may submit a response in accordance with the below information.

There is a page limitation for this RFI of 5 pages. The Government will not review any other information or attachments included, that are in excess of the (#) page limit. NO MARKETING MATERIALS ARE ALLOWED AS PART OF THIS RFI. Generic capability statements will not be accepted or reviewed. Your response must address capabilities specific to the services required in the attached PWS and must include the following:

a. Interested Vendors shall at a minimum, provide the following information in the initial paragraph of the submission:

Name of Company Address Point of Contact Phone Number Fax Number Email address Company Business Size and Status For VOSB and SDVOSBs, proof of verification in VIP.

NAICS code(s) Socioeconomic data Data Universal Numbering System (DUNS) Number Existing Contractual Vehicles (GWAC, FSS, or MAC)

b. Provide a summary of your capability to meet the requirements contained within the draft PWS for the following areas:

1. Detail your company’s capabilities and experience in providing administrative and clerical support for Enterprise Messaging, Collaboration, Authentication and Office 365 Services (EMCAO).

2. Describe your capability to meet the requirements outlined in the draft PWS section 5.0.

3. Provide a summary of your experience with Program Administration Support.

c. List any existing contracting vehicles that you would recommend for this requirement to be solicited against.

d. Corporate experience or expertise in performing these types of services and specific examples or references. Specific examples or references provided must include the agency, point of contact, dollar value, and contract number.

e. Your company’s intent and ability to meet the set aside requirement in accordance with VAAR 852.219-10 (JUL 2016) (DEVIATION) VA Notice of Total SDVOSB and 13 CFR §125.6, which states the contractor will not pay more than 50 percent of the amount paid by the Government to it to firms that are not SDVOSBs. Your response shall include information as to available personnel and financial resources; full names of proposed team members and the PWS requirements planned to be subcontracted to them, which must include the prime planned percentage or the names of the potential team members that may be used to fulfill the set aside requirement.

f. Has the draft PWS provided sufficient detail to describe the technical requirements that encompass the software development and production operations support services to be performed under this effort?

______ YES _______ NO (if No, answer question f)

g. If “NO”, please provide your technical comments/recommendations on elements of the draft PWS that may contribute to a more accurate proposal submission and efficient, cost effective effort.

Responses are due no later than 10:00 AM, June 10, 2021 via email to Christine Keen-Deputy, Contract Specialist at Christine.Keen-Deputy@va.gov and Iris Farrell, Contracting Officer at Iris.Farrell@va.gov. Please note “Enterprise Messaging, Collaboration, Authentication and Office 365 (EMCAO) Services Support” in the subject line of your response. Mark your response as “Proprietary Information” if the information is considered business sensitive. The email file size shall not exceed 5 MB.

See attached document: Enterprise Messaging, Collaboration, Authentication and Office 365 (EMCAO) Services Support PWS Draft

File details come from the government source that posted it. Updated .