SOURCES SOUGHT
D -- Forms and Publications Orders (FP Orders) Modernization
- Notice Date
- 7/11/2023 11:19:04 AM
- Notice Type
- Sources Sought
- NAICS
- 541512
— Computer Systems Design Services
- Contracting Office
- TECHNOLOGY ACQUISITION CENTER NJ (36C10B) EATONTOWN NJ 07724 USA
- ZIP Code
- 07724
- Solicitation Number
- 36C10B23Q0432
- Response Due
- 7/17/2023 9:00:00 AM
- Archive Date
- 08/16/2023
- Point of Contact
- Eleanor Slocum, Contract Specialist, Phone: 848-377-5129
- E-Mail Address
-
Eleanor.Slocum@va.gov
(Eleanor.Slocum@va.gov)
- Awardee
- null
- Description
- US Department of Veterans Affairs Request for Information/Sources Sought 36C10B23Q0432 Forms & Publications Orders (FP Orders) Modernization Introduction This is a Request for Information (RFI) only issued for the purpose of conducting market research. Accordingly, this RFI constitutes neither a Request for Proposal (RFP) nor a guarantee that one will be issued by the Government in the future; furthermore, it does not commit the Government to contract for any services described herein. Do not submit a Proposal. The Department of Veterans Affairs (VA) is not, at this time, seeking proposals or quotes, and therefore, will not accept, review, or evaluate unsolicited proposals or quotes received in response hereto. This notice is not to be construed as a commitment on the part of the Government to award a contract, nor does the Government intend to pay for any information submitted as a result of this request. The Government does not reimburse respondents for any costs associated with submission of the information being requested or, reimburse expenses incurred for responses to this RFI. The information provided may be used by VA in developing its acquisition strategy and Product Description or Performance Work Statement (PWS). Any information submitted by respondents to this RFI is strictly voluntary; however, any information received shall become the property of the Government and will not be returned to the respondent. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. This is a request for information and does not obligate the Government in any way, nor does it commit the Government to any specific course of action. Forms and Publications (FP) Orders is a legacy mainframe application hosted at a VA datacenter. This application is used enterprise-wide by approximately 500 end users to requisition items for their locations, including: paper forms, publications, Veteran burial flags, and gun locks (in support of the VA's Suicide Prevention program). FP Orders contains over one thousand orderable items. The Office of Procurement, Acquisition and Logistics (OPAL) Service Distribution Center (SDC) uses the application to process and track the requisition requests and uses various system reports to conduct inventory management functions to ensure adequate stock is on hand to fulfill all requests. Due to the age and complexity of the application, VA is interested in replacing this legacy mainframe application with a modern already developed solution compliant with VA and Federal policy and capable of meeting the needs of end users and the OPAL order fulfillment organization. VA is primarily seeking information on a proposed, already developed solution. System Requirements See attached draft PWS. Submittal Information: All responsible sources may submit a response in accordance with the below information. There is a page limitation for this RFI of 25 pages. The Government will not review any other information or attachments included, that are in excess of the 25 page limit. NO MARKETING MATERIALS ARE ALLOWED AS PART OF THIS RFI. Generic capability statements will not be accepted or reviewed. Be advised that set-aside decisions may be made based on the information provided in response to this RFI. Responses should be as complete and informative as possible. Respondents shall submit a capability statement that addresses in sufficient detail the questions below about your intended solution. Responses must also include the completion of attachment 2.1, and will count towards the total page count. Your response must address capabilities specific to the services required in the attached PWS and must include the following: Interested Vendors shall provide the following information in the initial paragraph of the submission: Name of Company Address Point of Contact Phone Number Email address Company Business Size and Status (under intended NAICS of 541512) For VOSB and SDVOSBs, proof of certification from SBA Veterans Small Business Certification Program (VetCert) portal (https://veterans.certify.sba.gov/). Additional NAICS code(s) performing work under Socioeconomic data SAM Unique Entity ID Existing Contractual Vehicles (GWAC, FSS, or MAC) for which you hold a contract and include the contract number, expiration date, etc. VA anticipates that this effort would fall within North American Industry Classification System (NAICS) Code 541512, Computer Systems Design Services, which has a size standard of $34.0M. If you believe there is a more appropriate NAICS code, please provide that to the Government with your rationale. With respect to the FP Orders Replacement requirement, would you be the prime contractor? As the Prime Contractor, what tasks under the questions in Section 4 below would your company perform? Are you able to comply with FAR 52.219-6 and 52.219-14 in execution of this effort? If you are a Service Disabled Veteran Owned Small Business, are you able to comply with VAAR 852.219-73, VA Notice of Total Service-Disabled Veteran-Owned Small Business Set-Aside; 13 CFR 125.6; and VAAR 852.219-75. VA Notice of Limitations on Subcontracting Certificate of Compliance for Services and Construction in execution of this effort? Detail your company s Corporate experience or expertise in performing these types of requirements/ SaaS/COTS product and specific examples or references. Specific examples or references provided must include: The company, point of contact, dollar value, and/or contract number. Examples of federal experience implementing your SaaS/COTS product (specific examples or references provided must include the agency, point of contact, dollar value, and contract number). Please identify other successful acquisition strategies in your experience used by other organizations (government or commercial) and any resultant contract information. Provide a summary of your capability to meet the requirements contained within the draft PWS Paragraph 5.0. Please identify potential schedule constraints based on your experience that may be not accounted for in the current iteration of the PWS. Include feedback if the period of performance as currently noted is viable. Provide separate Rough Orders of Magnitude (ROMs) for the product in accordance with PWS Paragraph 5.0. Provide a summary of the licensing approaches and price modeling for your solution. Additionally, detail the following: If/how the licensing costs & structure changes based on the future growth parameters. Identify the threshold for named user subscriptions vs. an enterprise/site subscription. Is your pricing model driven by total users, concurrent users, transaction-based, number of records, etc.? Are any additional services needed outside of the subscription model (e.g., configuration to meet functional requirements, data storage, data migration, additional features)? If so, please provide the items and proposed price for these additional services. Detail if both the requisition & inventory management requirements be met with a single software solution, or will multiple software systems be integrated to provide a complete solution? If multiple software systems are recommended, will your company provide all software systems necessary? Include the specific product(s) do you intend to utilize to meet the requirements. Are there any requirements in PWS paragraph 5.2 that are unable to be met by your proposed solution? If so, which one(s)? Is the solution customizable by the customer (i.e. without Vendor involvement) to adapt to changing business requirements or will customizations be required to be completed by the Vendor? Are there any significant or critical features missing that you feel should be part of the PWS? If yes, then please provide additional detail. Will you be able to export the data from the legacy COBOL mainframe FP Orders application? Describe your standard release and patch cycle. Has the draft PWS provided sufficient detail to describe the technical/functional requirements that encompass the software development and production operations support services to be performed under this effort. Yes No 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. If proposing a SaaS solution, please also include response to the additional questions below: Detail your company s SaaS product cloud infrastructure and accessibility from various client devices through either a thin client interface, such as a web browser (e.g., web-based email) or a program interface. The system shall not require download of software to VA computers. The VA shall not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or individual application capabilities. The system shall be vendor or third-party hosted and require no servers within VA. Please validate that your proposed SaaS product is SaaS in accordance with the NIST 800-145, or latest, definition and describe its hosting environment. On-demand self-service Broad network access Resource pooling Rapid elasticity Measured service Please detail any interfacing or custom development that your SaaS product requires ahead of go-live. Can your company s proposed SaaS product meet all PWS requirements without developing an interface or performing any kind of custom development? Does your company have existing APIs with other commercial cloud products? If there are customizations/configurations, such as templates, workflow, custom logic, integrations etc., describe your company s ability to deliver the source code to the Government, What was your uptime rate during the past 12 months for the SaaS application? Describe the type of system monitoring VA would have access to for SaaS/Managed Service solutions Please describe your company s ability and approach to adopt and incorporate VA customer feedback/requirements in the product roadmap of your proposed SaaS product. Is the proposed application currently FedRAMP authorized? If it is not currently authorized, what is your timeline for achieving authorization in order to comply with VA s mandatory requirement? The Contractor shall be required to comply with all FedRAMP requirements for the application as mandated by Federal laws and policies, including making available any documentation, physical access, and logical access needed to support this requirement. Please provide the following information: Is your company s product FedRAMP Authorized or in processes with an agency? Yes No If Yes, provide the following: Sponsoring Agency: Date they expect to be listed as in process on FedRAMP.gov: Date they expect to be listed as authorized in the FedRAMP marketplace: Check All that Apply: IaaS SaaS PaaS If authorized, please provide link to listing in FedRAMP Marketplace (FedRAMP ID): Following guidance from the Federal CIO, VA will utilize existing JAB ATO or agency ATO issued by another agency as a starting point for FedRAMP requirements. If neither of those exist, VA will sponsor FedRAMP ATO. VA will be using the FedRAMP baselines as a starting point, since they are specifically tailored for cloud services. Does your company s SaaS product have an ATO from any federal agency? Detail your company s support Service Level Agreements (SLAs) for all tiers of service. Responses are due no later than 12:00 PM EST (Noon) on July 17, 2023 via email to Michael Weckesser, Contracting Officer, at Michael.Weckesser@va.gov and Eleanor Slocum, Contract Specialist, at Eleanor.Slocum@va.gov. Please note 36C10B23Q0432 - Forms & Publications Orders (FP Orders) Modernization 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. Attachment 2.1 Service Model Questions: Brief Overview of (PRODUCT) and how the VA will use the product? Are you providing a SaaS product to the VA? What type of infrastructure do you plan to host this application on (e.g. AWS/GCP/AZURE) and where is the physical hosting location?(All infrastructure must be physically located within the Continental United States) If proposing a COTS application, please describe how this solution can be hosted in its current state. (e.g., on premise servers, Cloud, Web-based) How would VA users access the solution? (ex: web browser, mobile app) Is your solution compliantwith VA two-factor authenitcation requirements? (See PWS Section 6.1.2)) If user accounts are created, what does that process look like? If VA wished to add an additional user to be able to use the solution, how would that be accomplished? Would you consider (PRODUCT) Web architecture to be multi-tenant? (Is the information system architected in a multi-tenant manner where each customer has its own tenant, and all tenants share the same underlying architecture following the multi-tenant architecture definition) (Even if logically seperated) Is (PRODUCT) Web environment horizontally scalable to react to changes in demand or usage? If so, is the process fully automated or executable with minimal intervention? At a high level, are metrics and event logs captured for: Utilization of the (PRODUCT) Web application attributable to a specific user, account, or customer? Utilization of the (PRODUCT) Web environment resources? Are any contractors/providers sourcing development activities from personnel that reside OCONUS? Yes/No If yes please explain: Are any contractors/providers allowing access to a FedRAMP Boundary or Federal data to personnel that reside OCONUS? Yes/No If yes please explain:
- Web Link
-
SAM.gov Permalink
(https://sam.gov/opp/9008f75ae93349c49ee8c3223c7b20ca/view)
- Record
- SN06744657-F 20230713/230711230057 (samdaily.us)
- Source
-
SAM.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's SAM Daily Index Page |