FBODaily.com | FedBizOpps: FILE | D | Lighthouse API Management Platform RFI #3 - Attachment

FBO DAILY - FEDBIZOPPS ISSUE OF JULY 29, 2018 FBO #6092
DOCUMENT

D -- Lighthouse API Management Platform RFI #3 - Attachment

Notice Date: 7/27/2018
Notice Type: Attachment
NAICS: 541519 — Other Computer Related Services
Contracting Office: Department of Veterans Affairs;Technology Acquisition Center;23 Christopher Way;Eatontown NJ 07724
ZIP Code: 07724
Solicitation Number: 36C10B18Q2732
Response Due: 8/3/2018
Archive Date: 11/10/2018
Point of Contact: Michael Frank
E-Mail Address: 0-9701<br
Small Business Set-Aside: N/A
Description: RFI, VA Application Programming Interface Development and Operations Request for Information VA Application Programming Interface Development and Operations July 27, 2018 Introduction This Request for Information (RFI) is issued for information and planning purposes only and does not constitute a solicitation nor does it restrict the Government as to the ultimate acquisition approach. In accordance with (IAW) Federal Acquisition Regulation (FAR) 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. The purpose of this RFI is to obtain market information on capable sources of supply, industry practices, and input specific to the information provided. The Government is not responsible for any cost incurred by industry in furnishing this information. All costs associated with responding to this RFI will be solely at the interested party s expense. Not responding to this RFI does not preclude participation in any future Request for Proposal, if any is issued. Any information submitted by respondents to this RFI is strictly voluntary. All submissions become Government property and will not be returned. VA anticipates using SAP procedures and may award multiple contracts based on this effort The Department of Veterans Affairs (VA) Technology Acquisition Center is issuing this RFI to solicit feedback and determine capabilities in executing the requirements of the attached DRAFT Performance Work Statement (PWS) [Attachment 1]. It is anticipated that this acquisition will be conducted under the simplified Acquisition Procedures (SAP) in accordance with Federal Acquisition Regulation (FAR) 13.5. Accordingly, this effort cannot exceed $7M. Additionally, comparative evaluation will be performed in accordance with FAR 13.106-2(b)(3). The Government reserves the right to award to multiple Quoters. Background VA requires Contractor support to design, develop, and maintain various aspects of the VA Application Programming Interface (API) Development and Operations, including but not limited to platform design, API development and maintenance, developer documentation, and product management best practices to work with teams internal and external to VA, using modern software development methods and tools. VA is taking an API-first strategy to deliver the high quality digital experiences our users expect. A single set of APIs will power every VA digital service, and these same APIs will be exposed to approved third parties to build products and applications on top of VA services and data. These APIs across every vertical of VA s business will enable VA users to receive a consistent, high quality experience across all VA communication channels (e.g., digital, phone, mail, in-person, etc.) The health industry is quickly converging on the Fast Healthcare Interoperability Resources (FHIR) standard to enable enhanced data interoperability between both internal and external systems. API enabled and FHIR based solutions are easier for developers to implement as it makes use of modern web standards and RESTful architectures with more easily understood specifications. By liberating data and enhancing interoperability with FHIR, VA will shift data ownership to Veterans, making it more readily available. In the benefits space, VSOs and other third parties spend significant amounts of time manually looking in VA systems to check on the status of a claim for a Veteran they are working with, or to find out if a rating has been granted. If VA were instead able to provide APIs to this information, authorized individuals would be able to access it more readily, improving the experience they can provide for Veterans and reducing VA costs. VA TAC is seeking comments and feedback related to the attached DRAFT PWS for the VA API Development and Operations. After reviewing the attached DRAFT PWS please provide responses to the questions below as well as any additional comments, feedback, information or questions related to the VA API Development and Operations. Respondents are requested to clearly identify their capabilities relevant to the scope of work in the draft PWS. The Government is seeking as much information as possible and a complete response from industry to this RFI during this market research activity may assist the Government in developing its acquisition strategy and finalizing any PWS. Questions: Please submit the below requested information by 12:00PM EST on August 3, 2018 via email to Michael Frank, Contract Specialist, at michael.frank@va.gov. VA reserves the right to not respond to any, all, or select responses or materials submitted. All VA current requirements identified herein are subject to change at any time. If you experience any problems or have any questions concerning this announcement, please contact Michael Frank at michael.frank@va.gov, 732-440-9701 or Juan Quinones at juan.quinones@va.gov, 732-440-9714. VA appreciates your time and anticipated response. General Company Information Include the following identification information Company Name CAGE/DUNS Number under which the company is registered in SAM/VetBiz.gov Company Address Point of contact name Telephone number Email address Are you a small or large business under NAICS 541512 ($27.5M)? If you believe there is a more appropriate NAICS code, please provide that to the Government with your rationale. Are the requirements in the draft PWS sufficiently detailed to describe the VA API Development and Operations services to be provided 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. Identify existing contract vehicles (GSA, NASA SEWP, T4NG etc.) in which you are a contract holder that can be utilized to procure the VA API Development and Operations services. Are you planning on performing as the prime contractor? If a small business, what type of small business are you? Are you able to comply with FAR 52.219-6 and 52.219-14 in execution of this effort? Are you able to comply with VAAR 852.219-10, VA Notice of Total Service-Disabled Veteran-Owned Small Business Set-Aside and with subcontracting limitations in 13 CFR 125.6 in execution of this effort? Provide a Rough Order of Magnitude estimate for a 12-month effort. Capability Statement Submit a capability statement describing your company s ability to meet the requirements in the attached draft PWS. The capability statement shall be limited to five pages (General company information questions are not included in the page limitation). The capability statement shall address the following Provide a summary of your technical capability to meet all of the Government s requirements. Demonstrate your expertise/experience in development of APIs inclusive of project management, product management, requirements refinement, human centered design, iterative development, user research and usability testing, automated testing support, performance metrics definition and reporting, automated monitoring and performance reporting, and continuous integration / continuous delivery (CI/CD) for the development and enhancement of APIs. Have you performed similar work to include scope and complexity as described in the PWS? Have you performed this type of work with the Federal Government? Provide supporting detail. Indicate whether you were the prime contractor or subcontractor. Does your company you currently have a contract for development of APIs? Briefly describe the Agile development processes of API s you would use to accomplish this effort.
Web Link: FBO.gov Permalink
(https://www.fbo.gov/notices/989a6748f86f4851e30b6585b22ab137)
Document(s): Attachment; File Name: 36C10B18Q2732 36C10B18Q2732_3.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=4510423&FileName=36C10B18Q2732-003.docx); Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=4510423&FileName=36C10B18Q2732-003.docx; File Name: 36C10B18Q2732 Draft PWS VA API Development and Operations 7-27-18.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=4510424&FileName=36C10B18Q2732-004.docx); Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=4510424&FileName=36C10B18Q2732-004.docx; File Name: 36C10B18Q2732 PWS ATTACHMENT 001 VAEC.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=4510425&FileName=36C10B18Q2732-005.docx); Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=4510425&FileName=36C10B18Q2732-005.docx; File Name: 36C10B18Q2732 PWS ATTACHMENT 002 Agile Best Practices.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=4510426&FileName=36C10B18Q2732-006.docx); Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=4510426&FileName=36C10B18Q2732-006.docx; Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
Record: SN05010908-W 20180729/180727231107-989a6748f86f4851e30b6585b22ab137 (fbodaily.com)
Source: FedBizOpps Link to This Notice
(may not be valid after Archive Date)

| FSG Index | This Issue's Index | Today's FBO Daily Index Page |

Loren Data's SAM Daily™

D -- Lighthouse API Management Platform RFI #3 - Attachment