Attachment 6 SI Builder Technical Questions - Amended 5-5-2025.docx

Attachment 6 - Technical Proposal Response RFP # 856 865 SI Builder

Instructions Offerors must respond to all questions in this document as detailed in Section 4 of the RFP. All questions are mandatory and will be evaluated. Failure to respond to a question may result in a Proposal being deemed non-responsive and receiving no further consideration. Be sure to comply with the page limits and all formatting requirements described in the RFP and in this form.

General Formatting Requirements: Your response must be formatted as follows:

Font: AptosCalibri Font Size: 11 Margins: Standard 1 inch (all margins) Spacing: Single-spaced

Page Limits: The questions below have maximum page limit requirements. Offerors must NOT exceed the maximum page limits. Note, the page limit applies to the front side of a page only (for example, ‘1 Page’ implies that the Offeror can only provide a response on one side of a piece of paper).

Images: Responses may include images for illustrative purposes (e.g. figures, graphics, pictures, graphs) that may include fonts that do not meet the general formatting requirements above. All substantive information, including text within tables created as part of the response, must meet the formatting requirements.

No Links or Attachments: Offerors must not include website links or imbedded documents in the response. The State will not consider information outside of, or imbedded in, the Proposal response. Offerors are also not permitted to provide additional documentation through separate attachments that will exceed the question page limit.

Failure to follow these formatting requirements may result in a Proposal being deemed non-responsive. The RFP Lead reserves the right, but is not required, to make adjustments to the Proposal to ensure that the documents meet these requirements. For example, if a submitted document exceeds the page limit, the RFP Lead may remove or redact the extra pages before providing them to the evaluators. The RFP Lead will delete, blackout, or redact any names to keep the proposal anonymous.

Offeror may remove existing content on Attachment 6 in their response but must identify the section number and/or title in their response to be easily identifiable to offerors.

1. Experience & Qualifications (page limit: 4 pages) Provide the qualifications and experience of your company and any sub-contractors that will be performing the implementation and ongoing operations and maintenance. Demonstrated success in projects similar to the scope of this RFP including those provided in a multi-vendor environment and in other Medicaid or healthcare entities will be particularly informative for the Evaluation Committee.

2. Approach & Methodology (page limit: 4 pages) Provide a brief roadmap which describes the general approach (major activities or tasks), which will be utilized to successfully deliver the service. Provide sufficient information to demonstrate your understanding of the requirements, plan, and your approach for meeting these requirements. Provide a high-level schedule that outlines the major tasks, activities, or phases that will be performed. Identify on the high-level schedule key deliverables from Appendix G – Deliverables. Demonstrate your understanding of IDHW’s integration platform strategy as a key component of the MMIS modernization, including the role of the technical reference architecture and architectural governance. If you intend to utilize subcontractors, describe the extent to which they will be used to comply with Contract requirements. List estimated percentage of the total Scope of Work for this Contract expected to be performed by each Subcontractor.

3. Obstacles, Challenges, & Risks (page limit: 3 pages) Identify and address issues, concerns, challenges, obstacles, or risks that may impact the successful delivery of this project, using the format below (you may include as many as you wish, within the page limit). The Offeror should list and prioritize these items that are unique and applicable to this project; this includes areas that may cause cost/price increases or may be a source of dissatisfaction for the State or its members. The Offeror should rely on and use their past experience and knowledge of completing similar projects to identify these potential risks, issues, or challenges.

Each item should be described in non-technical terms and should contain enough information to describe to an evaluator why the item is a valid risk/concern. The Offeror should also explain how it will avoid or minimize the risks from occurring. If the Offeror has a unique method to minimize the issue/risk/concern, the Offeror should explain it in non-technical terms. This Submittal Form provides an opportunity for the Offeror to differentiate its capabilities based on its ability to visualize, understand, and minimize risk to the State and the risk to a successful outcome of the service. The Offeror can address:

· Controllable Items: This includes risks, activities, or tasks that are controllable by the Offeror, or by entities/individuals that are contracted to by the Offeror. This includes things that are part of the technical scope of what the Offeror is being hired to do. This may also include risks that have already been minimized before the project begins due to the Offeror’s expertise (i.e. risks that are no longer risks due to the Offeror’s expertise in delivering this type of project). All controllable risks and strategies to mitigate them must be included in the Offeror’s base proposal cost and schedule (if there are any impacts at all).

· Non-Controllable Items: This includes risks, activities, or tasks that are not controllable by the Offeror. This may include risks, issues, challenges, or obstacles attributed by the State, Members, risks that are caused by other agencies, or completely uncontrollable risks. These can also be areas/risks that can contribute to contingency. Although these risks may not be controlled by the Offeror, the Offeror should identify a strategy that can be followed or used to mitigate these risks. All non-controllable risks and strategies to mitigate them must not be included in the Offeror’s base proposal cost or schedule.

Provide a brief description of the item (background of how the concern/issue may impact the project or service if it occurs), and a strategy to prevent/minimize the issue/concern from occurring, or strategy to minimize the impact of the risk if it does occur. The figure below provides an example of how this information can be submitted.

Item #1:

Strategy:

Item #2:

Strategy:

Item #3:

Strategy:

4. Technical Questions

4.1 Design, Configuration, and Build (page limit: 20 pages)

Describe in detail your proposed plan for constructing the System Integration (SI) Hub platform for the Idaho Department of Health and Welfare (IDHW) to enable the functionality described in Appendix A Scope of Work. Describe how you plan to use the software and tools that you identify in Appendix J Cloud and Software inventory Attachment 5 SI Builder Cost Proposal. Share your experience with designing, developing, and configuring similar modular system implementations for each component of the SI Hub. This is not intended to be a full design specification, but the tools and methods should be described sufficiently for a business leader to understand how the software and services will function to meet the requirements. In addition to an overall architecture, the Offeror must describe how it will meet requirements for each of the integration components described in Appendix A Scope of Work and Appendix E SI Hub Overview as follows:

· Application Programming Interface (API) Gateway

· Identity and Access Management (IdAM) / Single Sign On (SSO)

· Centralized Logging and Monitoring

· Managed File Transfer (MFT)

· Modular Performance Monitoring

· Platform support for Idaho Medicaid Information and Data Analytics Suite (I-MIDAS)

· SI Hub Platform Performance Monitoring

· SI Hub Data Quality & Automation Agreement (DQAA)

· Security Information and Event Management (SIEM)

4.2 Integrations, Interfaces, Hosting and Environments (page limit 5 pages) Describe your plan for configuring and supporting the multiple environments required in Appendix A Scope of Work within the State’s Azure Commercial Cloud tenant. Describe your plan for configuring and supporting the multiple environments required in Appendix A Scope of Work within the State’s Azure Commercial Cloud tenant Identify your methodology for keeping environment configuration, code, and data in synch and for scaling as necessary to meet the environment performance Service Level Agreements (SLAs) as defined in Appendix H. Identify how you will maintain data for testing that is consistent with environment requirements and provides sufficient data for internal IDHW and external vendor testing. Provide your plan to monitor and minimize unnecessary cloud computing expense in your design through automation. Describe your approach to forecast, monitor and optimize State Azure Commercial Cloud spend across all environments described in Appendix A – Scope of Work.

4.3 Integration Data Management and Data Quality Validations (page limit 5 pages) Identify your methods and best practices you have use with similar implementations to handle records transfers for single, composite, asynchronous and all other required methods for transmitting and receiving both API and MFT as required in Appendix A Scope of Work and Appendix E SI Hub Overview. Identify in your response how records and files will be stored including any meta data, logs and alerts. Describe how your solution will implement the Data Quality and Automation Agreements as defined in Appendix A Scope of Work and Appendix E SI Hub Overview. Describe your approach to data management within the SI Hub.

4.4 Dashboards and Performance Monitoring (page limit 6 pages) Describe in detail the management dashboard that will be built for both you as the Contractor and the various users who will view and manage their work within the SI Hub as required in Appendix A Scope of Work and as further defined in Appendix E SI Hub Overview. A mock up of the dashboard would be helpful but not required for evaluation. Describe the reports and visualizations that will be available to the state and third parties who interact with the SI Hub. Describe your approach for maintaining the dashboards and visualizations. Identify in particular how SLAs will be tracked and reported for both the SI Hub SLAs and the performance data that will be sent to the SI Hub from the modules related to their SLAs.

4.5 Security Management (page limit 5 pages)

Explain your approach to implementation, monitoring, and maintenance of all required security and privacy controls and protocols you will have in place to secure the multiple environments that may contain PHI, and user access to the SI Hub per requirements listed in Appendix A Scope of Work and regulatory guidance for the State of Idaho and Federal Medicaid requirements. Describe your design for role-based security and single sign-on.

4.6 Staffing plan and resumes for Key Personnel (page limit 3 pages per key personnel, and 3 pages for the staffing plan).

Provide a staffing model for the work to be performed defined in Appendix A Scope of Work. Provide resumes demonstrating qualifications as required in the SOW for each of the key personnel who will be assigned to this contract upon successful award. Your response must meet or exceed the requirements listed in the SOW and demonstrate the extent to which you have the expertise to accomplish the work defined. Proposals may include additional personnel but must be limited to those needed to meet the requirements of the SOW, Vendor may include information about non-key personnel but must keep it withing in the total page count for the staffing plan.