RFP # 856 SI Builder Admin Doc - Amended 5-5-2025.docx

STATE OF IDAHO

DIVISION OF PURCHASING

FOR THE

Idaho Department of Health and Welfare (IDHW)

REQUEST FOR PROPOSAL (RFP)

System Integration Builder

RFP # 856 AMENDED 05/05/2025

TABLE OF CONTENTS

RFP ADMINISTRATIVE INFORMATION

RFP Title:

System Integration Builder

RFP Project Description:

System Integration (SI) Hub development for integration of Idaho Department of Health and Welfare’s (IDHW) next Medicaid Management Information System (MMIS) modules.

RFP Lead:

Division of Purchasing Michael Piccono, Purchasing Officer Michael.Piccono@adm.idaho.gov 208-332-1612

Submit electronically via IPRO:

Electronic Submission:

Pre-Proposal Conference Date/Time:

Pre-Proposal Conference Location:

Monday, April 7th, 2025 at 10:00 AM Mountain Time

Virtually Via Microsoft Teams

Deadline to Receive Questions:

Tuesday April 15th, 2025 at 11:59:59 p.m. Mountain Time

RFP Closing Date:

See IPRO Header Document

Public Opening Date:

10:30 a.m. Mountain Time, the following business day after closing

Initial Term of Contract and Renewals:

Seven (7) years. Upon mutual, written agreement, the Contract may be renewed, extended or amended. The anticipated total Contract term is ten (10) years.

1 Overview

1.1. Purpose

The Division of Purchasing (DOP), on behalf of the Idaho Department of Health and Welfare (IDHW) is seeking an Information Technology Development Contractor to develop and build a System Integration Solution to integrate all modules of the Medicaid Management Information System (MMIS). The contract will include development, training, maintenance of the solution through the life of the contract, and transition of operations to subsequent vendors or IDHW staff at contract close.

1.2. Definitions

Definitions for this RFP and the resulting Contract are provided in Appendix B - Definitions.

1.3. Background Information

1.3.1 IDHW has established a MMIS Procurement Project Management Office (PMO) within the Division of Medicaid to facilitate the replacement of the existing MMIS with a modular solution that is better aligned to current business needs, can respond quickly to changes in the regulatory environment, and can effectively meet emerging business objectives. IDHW Division of Medicaid uses the MMIS to administer the state’s Medicaid program through enrolling and reimbursing health care providers for the provision of services to Medicaid eligible members.

1.3.2 The current MMIS, implemented in 2010, is comprised of a medical claims and provider solution, an Enterprise Data Warehouse and Decision Support System (EDW/DSS) and a Pharmacy Benefits Administrator (PBA). IDHW is in the planning stages for the replacement of the current MMIS and needs technical assistance designing and implementing the integration platform, tools, and services for the new modular system using industry best practices for system architecture, modularity, data governance, information security, integration, and testing.

1.3.3 The new MMIS will enable IDHW to comply with Centers for Medicare and Medicaid Services’ (CMS) direction regarding modularity, interoperability, and Streamlined Modular Certification, and will support improving health outcomes, increasing customer satisfaction, and optimizing program dollars. The next generation of the MMIS will be an enterprise solution that supports CMS’ modularity guidance with the following objectives:

1.3.3.1 Automates business processes wherever possible.

1.3.3.2 Includes standardized and automated electronic communication and data exchange capabilities, easily integrating with other systems to enable enterprise-wide program management.

1.3.3.3 Is compliant with applicable federal and state policy.

1.3.3.4 Is flexible to quickly adapt to the dynamic, evolving needs of existing programs and support new regulations, policies and innovations using business driven technical solutions.

1.3.3.5 Provides centralized access to data and data analytics tools.

1.3.4 The SI Hub as further defined in Appendix E – SI Hub Overview is a platform that enables consistent data exchange, integration, monitoring, and reporting among MMIS modules developed by various vendors with a modular approach as recommended by CMS and potentially with existing IDHW MMIS modules such as the Enterprise Data Warehouse (EDW) or the Pharmacy Benefits Administrator (PBA).

1.3.5 The SI Hub design supports the business objectives and strategic goals of the MMIS Modernization Project such as data-driven transparency, improved programmatic outcomes, enhanced self-service, and increased flexibility.

1.3.6 An overview of the MMIS Modernization Project Team structure and intended MMIS modules is illustrated in Figure 1: MMIS Modernization Project below.

Figure 1: MMIS Modernization Project

1.3.7 The following table provides a brief description of the MMIS Project Team and MMIS modules and or services:

Current Vendor: CSG Government Solutions

Current Vendor: CSG Government Solutions

Current Vendor: NTT Data

(TRA).

Vendor: TBD

I-MIDAS, or the Idaho Medicaid Information, Data, and Analytics Suite, comprises the data warehouse technologies and processes and a comprehensive data repository developed to enhance the operational analytical, and reporting capabilities within Idaho’s Medicaid Management Information System (MMIS) modernization project.

I-MIDAS supports the Idaho Department of Health and Welfare (IDHW) in establishing a unified data infrastructure for improved decision-making, transparency, and compliance.

Current Development Team: IDHW and contractors

Current Vendor: Gainwell Technologies LLC

Current Vendor: N/A, currently part of the Gainwell Technologies LLC CM solution

Current Vendor: Sandata, subcontracted through Gainwell Technologies LLC

IDHW’s Information Technology Services Division (ITSD) supports the Department of Health and Welfare’s technology needs for each division providing expertise and policies regarding security and technology use within the Depart of Health and Welfare. ITSD coordinates with ITS to ensure compliance to all state technology policies.

Current agencies: Office of Information Technology Services (ITS) and Information Technology Services Division (ITSD)

Current Vendor: Gainwell Technologies LLC

Current Vendor: IBM Consulting

Current Vendor: Prime Therapeutics

1.4. Timeline

Figure 2: Timeline

1.5. Resulting Contract

If the State awards a Contract from this solicitation, it will do so by issuing a Contract document from the State’s eProcurement system, IPRO powered by Luma. The State anticipates issuing a Contract document using the System Integration Builder Contract Template (Appendix L) attached in IPRO; however, the State reserves the right to determine the form of the resulting Contract. At its option, the State may memorialize the agreement between the State and the Contractor in one (1) or more final Contract documents.

2 Questions

2.1. Restrictions on Communications

From the issue date of this RFP, until a contract is awarded, or the RFP is cancelled, vendors are prohibited from communications regarding this RFP with IDHW staff, evaluation committee members, and other state employees or officials other than the RFP Lead and Division of Purchasing, except during formal solicitation events (including the pre-proposal conference, demonstrations, etc.) During challenges defined in Idaho Code 67-9232, vendors may communicate with the Director of the Department of Administration related to the challenge. Vendors may use the established public records request process of any Idaho agency during the RFP.

2.2. Pre-Proposal Conference

A non-mandatory pre-proposal conference will be held Virtually on Microsoft Teams at the time as indicated in Administrative Information on page 2 of this RFP. This will be your opportunity to ask questions, in person, with IDHW staff. All parties interested are invited to participate either by attending the conference virtually or by an established call-in number. Those choosing to participate must pre-register by submitting the completed Attachment 1 - Pre-Proposal Conference Registration Form via email to the RFP Lead. Parties interested are asked to register by Thursday April 3rd 2025. Any oral answers given by the State during the pre-proposal conference are unofficial and will not be binding on the State. Conference attendance is at the participant’s own expense.

2.3. Questions

This solicitation is issued via the State’s e-Procurement system, IPRO at IPRO Powered by LUMA The RFP Lead is the only contact for this Solicitation. All correspondence must be in writing. In the event that it becomes necessary to revise any part of this RFP, amendments will be posted at IPRO. It is the responsibility of parties interested in this RFP to monitor IPRO for any updates or amendments. Any oral interpretations or clarifications of this RFP must not be relied upon. All changes to this RFP will be in writing and must be posted to IPRO to be valid.

Questions or other correspondence must be submitted in writing to the RFP Lead (see contact information in the RFP Administrative Information, page 2). QUESTIONS MUST BE RECEIVED BY 11:59:59 P.M. MOUNTAIN TIME ON THE DATE LISTED IN THE RFP ADMINISTRATIVE INFORMATION.

Written questions must be submitted using Attachment 2 - Offeror Questions. Official answers to all written questions will be posted on IPRO as an amendment to this RFP.

2.4. Vendor Proposed Modifications and Exceptions to Requirements, Terms, and Conditions The Offeror must review the Contract requirements, terms, and conditions, found in Appendix L – SI Builder Contract Template. The Offeror is strongly encouraged to submit any proposed modifications or exceptions to the Contract requirements, terms, and conditions to the RFP Lead prior to the deadline for submitting questions. See Attachment 3 – Requested Modifications for additional instructions. Modifications and exceptions must be submitted using the table provided within Attachment 3.

Any modifications or exceptions that are raised after the RFP closes may be rejected by the State, and may only be considered if they are non-material in nature, as determined in the State’s sole discretion. Therefore, the Offeror is strongly encouraged to submit any proposed modifications and exceptions during the Q&A period.

3 Instructions for Submission of Proposal

3.1. General Instructions

3.1.1 Proposals must be submitted electronically as detailed below. Except as otherwise addressed in this solicitation, all submission materials must be submitted at the same time. If multiple submissions are received, only the latest timely submission will be considered.

3.1.2 Alternate proposals are not allowed.

3.1.3 All electronic files must be in Microsoft Word or Excel format; the only exception is for financials, brochures or other information only available in an alternate format.

3.1.4 It is mandatory to submit your Proposal electronically via IPRO, all Offerors participating in this Solicitation must establish an account in the IPRO system, as it is necessary in order to process and/or award the resulting Contract(s). Establishing an account is free and only takes a few minutes.

3.2. Trade Secrets

Paragraph twenty-eight (28) of the Solicitation Instructions to Vendors describes trade secrets to “include a formula, pattern, compilation, program, computer program, device, method, technique or process that derives economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by other persons and is subject to the efforts that are reasonable under the circumstances to maintain its secrecy.” In addition to marking each page of the document with a trade secret notation (as applicable; and as provided in Paragraph twenty-eight (28) of the Solicitation Instructions to Vendors), Offerors must also:

3.2.1 Identify with particularity the precise text, illustration, or other information contained within each page marked “trade secret” (it is not sufficient to simply mark the entire page). The specific information you deem “trade secret” within each noted page must be highlighted, italicized, identified by asterisks, contained within a text border, or otherwise clearly delineated from other text/information and specifically identified as a “trade secret.”

3.2.2 Provide a separate document entitled “List of Redacted Trade Secret Information” which provides a succinct list of all trade secret information noted in your Proposal; listed in the order it appears in your submittal documents, identified by Page #, Section #/Paragraph #, Title of Section/Paragraph, specific portions of text/illustrations; or in a manner otherwise sufficient to allow the State’s procurement personnel to determine the precise text/material subject to the notation. Additionally, this list must identify with each notation the specific basis for your position that the material be treated as exempt from disclosure and how the exempting the material complies with the Public Records Law.

3.2.3 Submit a redacted copy of the Proposal with all trade secret information removed or blacked out. The redacted copy must be submitted electronically, with the word “redacted” in the file name

3.3. Electronic Submission

3.3.1 Electronically submitted Proposals must be submitted through IPRO, at Supplier Portal / Supplier Portal (inforgov.com). When submitting through IPRO, enter your Cost in IPRO as “$1.00,” and UPLOAD YOUR TECHNICAL PROPOSAL, SEPARATE COST PROPOSAL, AND ALL OTHER REQUIRED SUBMITTAL ITEMS. Remember to submit an additional redacted version of the proposal if you have identified trade secrets.

3.3.2 Contractors are strongly encouraged to begin the process of submitting the response far enough in advance of the End Time to allow for resolution of technical difficulties. Be advised that the state is not responsible for a Contractor’s failure to timely submit a responsive submission due to any technical or technological difficulties. See IDAPA 38.05.01.61.02.

3.3.3 Submitting via IPRO, be advised that the Offeror for Proposal evaluation and award purposes is the entity profile under which the Proposal is submitted in IPRO, which must be the same legal entity presented in the uploaded response materials. If the entity identified on the state supplied Signature Page differs from the entity under which you submit your Proposal in IPRO, the information provided on the Signature Page prevails.

3.3.4 Offerors are further advised to upload response materials with descriptive file names, organized and consolidated in a manner which allows evaluators to efficiently navigate the Offeror’s response as the State will print uploaded documents for evaluation in the manner received via IPRO.

4 Proposal Format

4.1. General

These instructions describe the format to be used when submitting a Proposal. The format is designed to ensure a complete submission of information necessary for an equitable analysis and evaluation of submitted Proposals. Offerors must respond to all mandatory questions as directed in IPRO, whether or not they are specifically discussed in this section.

4.2. Proposal Submission

4.2.1. IPRO Questions. All Offerors must respond to each mandatory question in IPRO.

4.2.2. Submittal Forms

a. Cover Form (Attachment 4). Download the form attached to Question 1. Complete the form as instructed and attach the completed form in response to the question(s).

b. Technical Proposal Response Document (Attachment 6). Download the technical proposal response document attached to Question 2. Insert your responses into the document as directed and attach the completed form in response to the question(s).

c. Cost Proposal (Attachment 5). Download the cost proposal document attached to Question 3. Complete all sections of the Cost Proposal as directed and attach the completed proposal in response to the question.

5 Proposal Review, Evaluation, and Award

5.1. Overview

The objective of the State in soliciting and evaluating Proposals is to ensure the selection of a firm or individual that will produce the best possible results for the funds expended. All proposals will be evaluated as detailed below.

5.2. Mandatory Requirements

5.2.1. All Proposals will be reviewed first to ensure that they meet the Mandatory Submission Requirements of the RFP. Any Proposal(s) not meeting the Mandatory Submission Requirements may be deemed non-responsive and receive no further consideration; however, IDAPA 38.05.01.074.03 and 38.05.01.091.05 allow the designated State official to waive minor informalities as well as minor deviations. Proposals that meet all mandatory requirements will proceed in the evaluation process.

5.3. Technical Proposal

5.3.1 Each Technical Proposal will be evaluated and scored utilizing one (1) or more Technical Proposal Evaluation Committee(s) according to the evaluation criteria provided in Section 5.3.2 below.

5.3.2 The Evaluation Committee members will evaluate and score the technical proposal based on the degree to which the Proposal has met the requirements of the RFP and has demonstrated likelihood of success. These scores will be used to create an initial ranking of the Proposals. Proposals will be evaluated based on the following criteria:

5.3.3 The total scores for the Technical Proposal will be normalized as follows: The Technical Proposal with the highest raw technical score will receive all available Technical Points: 350 points. Other Proposals will be assigned a portion of the maximum available Technical Points, using the formula:

350 X raw score of technical Proposal being evaluated Highest raw technical score

5.4. Presentations

5.4.1 Invited Offerors. Following evaluation of Technical Proposals, the State may invite one (1) or more top scoring Offerors to participate in presentations. The State reserves the right to invite as many Offerors as it deems appropriate, based on the Technical Proposal evaluation scores; provided, however, that the State does not intend to invite vendors to provide presentations if the normalized technical score of their proposal is more than ten percent (10%) lower than the next higher-ranking proposal unless the State deems it necessary to have sufficient competition.

Oral Presentation/Demonstrations. Each selected Offeror will be invited to provide an oral presentation or demonstration. The purpose of the demonstration is for the selected Offerors to present their designs of the System Integration Hub including an overall architecture model and data flow diagrams to provide additional context and clarity to the technical response. The script for Offerors to follow for the demonstration is attached as Appendix M. Demonstrations are expected to be scheduled for June 23 to 27, 2025.

Key Personnel Interviews. Each selected Offeror will be invited to participate with interviews of their key personnel (who must be the same individuals identified in Attachment 6 Technical Responsethe Cover Form).

5.4.1.1 These individuals are expected to devote the greatest time commitment at the operational level (rather than an executive, partner, sales representative, or other staff that will be less directly involved in day-to-day operations). The individuals that are interviewed must be the same personnel that will be assigned to these roles after award is made. The Offeror will not be permitted to remove or replace these individuals during the first twelve (12) months of this Contract, unless requested and approved by the State (with the exception of uncontrollable events such as: retirement, medical emergency/injury/sickness, or resignation).

5.4.1.2 The key personnel anticipated to be interviewed include:

· Project Manager - (See Appendix A section A.12.4.1)

· Solution Architect- (See Appendix A section A.12.4.2)

· Implementation/Integration Manager - (See Appendix A section A.12.4.3)

· Security Compliance Manager - (See Appendix A section A.12.5.1)

· SI Quality Assurance/Testing Manager - (See Appendix A section A.12.5.2)

· Maintenance and Operations Manager - (See Appendix A section A.12.4.4)

5.4.1.3 The State intends to interview individuals separately (not as a team).

5.4.1.4 No substitutions or proxies will be allowed. Individuals who fail to attend the interview will be given a “0” score, which may jeopardize the Offeror’s competitiveness.

5.4.1.5 Each interview is expected to last approximately twenty (20) minutes.

5.4.1.6 Interviewees may be asked questions regarding their experience, knowledge, and understanding of the scope of work, obstacles and challenges, strategies, and their plan/approach.

5.4.2 Forum. The State intends to host the Demonstrations and Interviews live in-person (in Boise Idaho); however, the State may elect to conduct demonstrations and/or interviews virtually (Zoom, Teams, WebEx, etc.). If interviews are performed online, each key personnel must have online video capabilities. Interviewees must be in an enclosed room/office/space (no other individuals can attend, participate, or observe the interview). Interviewees may not bring or use notes or handouts other than the RFP and Offeror’s Proposal.

5.4.3 Rights. The State reserves the right to invite additional Offerors to provide Presentations after the initial round of presentations, regardless of the gap in technical scores, if it determines additional presentations would be beneficial to the State.

5.4.4 Criteria and Weights. Presentations will be scored and weighted as follows:

5.4.5 Scoring. The total scores for the Presentations will be normalized as follows: The Presentation (including demonstration and all individual interviews) with the highest raw score will receive all available Presentation Points: 400 points. Other Offerors will be assigned a portion of the maximum available Oral Presentation/Demonstration Points, using the formula:

400 X raw score of Oral Presentation being evaluated highest raw oral presentation score.

5.5. Cost Proposal

5.5.1 The Cost Proposal will only be opened and evaluated for Offerors who participate in presentations.

The scores for the Cost Proposal will be normalized as follows: The cost evaluation will be based on the Ten Year Total Price provided in Attachment 5 Cost Proposal and Billing Procedure Matrix. The Proposal with the Lowest Overall Ten Year Total Price proposed will receive all available Cost Points: 250 points. Other Proposals will be assigned a portion of the maximum available Cost Points using the formula:

250 X Lowest Overall Ten Year Total Price Overall Ten Year Total Price being evaluated.

5.6. Clarification and Responsibility

The RFP Lead may, in the State’s sole discretion, perform clarification discussions and confirmation of responsibility with Offeror(s) to verify and validate that the Proposal will meet the needs of the Agency. At any time during this period, if it is discovered that the Offeror has not met a mandatory requirement, or has failed to adequately respond to an item below, the State may find the Offeror non-responsive or non-responsible, and disqualify the Proposal.

The Offeror may be requested to address the following items:

a) Responsibility Assessment: Pursuant to IDAPA 38.05.01.081, the RFP Lead may, in the State’s sole discretion, require the apparent high point Offeror to provide documentation to demonstrate its responsibility. The RFP Lead may request documentation including, but not limited to credit or financial reports, and references. Failure to provide requested documentation may result in the Offeror being deemed non-responsible. Nothing herein must prevent the State from using other means to determine Offeror’s responsibility.

b) Agency Concerns: The Offeror will address or resolve any major risks, issues, concerns, obstacles, or deal-breakers that have been identified by the Agency.

c) Verify the Fee/Cost Proposal: The Offeror will clarify and validate the fee/cost schedule. The Offeror will submit any additional financial data, supporting data, or substantiation requested by the Agency.

d) Provide a Project Schedule: The Offeror will provide a detailed schedule of the project (with major milestones or tasks). This should include milestones, task and proposed start and completion dates.

e) Align Expectations: The Offeror will coordinate the project/service (schedule, cost, activities) with all critical parties (subcontractors, consultants, suppliers, manufacturers, etc.). The Offeror will create a detailed project plan. Review any unique technical requirements with the Agency.

f) Key Assumptions: The Offeror will provide a summary of the major assumptions that have been made in preparing the Proposal. This should include items/tasks that the Offeror has assumed the Agency will perform, items/tasks required from the Agency, and items/tasks that have not been included in the Proposal (items that the Offeror feels are outside the scope of work). This should also include any critical expectations or responsibilities that the Offeror has of the Agency, Agency personnel, or other parties/organizations that are not contracted to by the Offeror.

g) Risk Mitigation Approach: The Offeror will identify all risks, activities, or concerns that may be unforeseen or not within the control of the Offeror. This should include everything (realistically) that may prevent the Offeror from being successful on this project. This may include: Offeror risks, owner risks, other party risks, and unforeseen risks. Identify if there are any strategies to mitigate these items.

h) Technical Reviews: The Offeror will comprehensively describe the approach for meeting all of the requirements in the Scope of Work to confirm depth and breadth of technical and/or industry knowledge, with any efforts required from the Agency should addressed.

i) Reference Verification: If requested, provide a list of references for the firm and each key personnel.

j) Organizational Chart: If requested, provide an organizational chart, including detail of any relationships with parent and subsidiary organizations.

k) Additional Requested Documentation: If requested, provide any additional documentation that may be requested, which may include a detailed project/work plan, testing and commissioning plan, training, change management plan, safety plan, staffing plan, operational plan, maintenance plans, warranties, bonding and insurance, background checks, etc.

The clarification discussion cannot materially alter the Proposal. The RFP Lead, in the State’s sole discretion, may conduct clarification discussions with multiple Offerors.

5.7. Negotiations and Best and Final Offers

The State may, in its sole discretion, seek one or more rounds of Best and Final Offer (BAFO) from Offerors. Pursuant to IDAPA 38.05.01, the State may enter into negotiations with one or more Offerors.

5.8. Award

Award of Contract will be made to the lowest responsible bidder, deemed to be the responsive and responsible Offeror receiving the highest number of normalized Final Total Points, according to the criteria below:

APPENDIX A - SCOPE OF WORK

RFP # 865 856 System Integration Builder All sections of the Scope of Work are required contract services. A detailed narrative of the system design and each component is included in Appendix E SI Hub Overview to give context to the requirements.

The information in the parentheses at the end of each requirement includes a five-digit internal requirement identifier, followed by a dash and a requirement scope indicator that identifies the phase or phases of the contract that are applicable to the requirement (i.e. 00000 – DDI Only).

The following table provides a description of each scope indicator.

Figure 1 depicts how SI Hub Requirement scope indicators relate to various phases of the SI Hub Builder contract. Refer to Appendix E for additional information regarding “Pre-DDI” and “Post-DDI” SI capabilities. SI Hub DDI activities are only considered complete once all deliverables identified for each phase in Attachment 5 – Cost Proposal have been delivered and approved.

Figure 1: Relationship of SI Hub Requirement Scope Indicators to MMIS Modernization Phases

0. Design, Configuration, and Build The Contractor's solution must provide the necessary functionality and configuration to fully support distributed debugging based on the unique identifier assigned to each transaction by the Systems Integrator (SI) Hub. (15927 - DDI and M&O) The Contractor’s solution must support, at minimum, the X12, National Information Exchange Model (NIEM), Extensible Markup Language (XML), Health Level 7 (HL7), Fast Healthcare Interoperability Resources (FHIR), National Council for Prescription Drug Programs (NCPDP), and JavaScript Object Notation (JSON) standard data messaging formats to ensure interoperability. Any additional proposed messaging formats must be approved by the ARB. (15933 - DDI and M&O) The Contractor's solution must support transactions that require a Synchronous Request/Response service pattern. (15934 - DDI and M&O) The Contractor's solution must support transactions that require an Asynchronous Request/Response service pattern. (15935 - DDI and M&O) The Contractor's solution must support a publish subscribe service capability that allows modules to broadcast messages using policy-based criteria. (15936 – DDI and M&O) The Contractor's solution must provide message queuing services that allow system administrators to create queues, alter existing queues, and control the operation of the queues. (15938 – DDI and M&O) The Contractor's solution must validate all received data exchanged through the IDHW SI Hub as configured in the DQAA dashboard with IDHW Data Governance Policy Standards. (15939 - DDI and M&O) The Contractor's solution must provide a Managed File Transfer (MFT) broker that requires only use of approved and configured protocols and restricts access to files and file transfers based on Identity and Access Management (IdAM) privileges. (15957 - DDI and M&O) The Contractor's MFT solution must support the Secure File Transfer Protocol (SFTP) and Hypertext Transfer Protocol Secure (HTTPS) protocols. Any additional proposed messaging formats must be approved by the Architecture Review Board (ARB). (15958 - DDI and M&O) The Contractor's solution must automate file transfer processes, including the detection and handling of file transfer failures that are possible to resolve without intervention. (15959 - DDI and M&O) The Contractor's solution must support the ability to initiate resumption of file transfers at the point of interruption. (15960 - DDI and M&O) The Contractor's solution must support scheduled file transfers based on the option of defining messaging or integration rules or by setting configurable triggers. It must support both time-based scheduling (e.g., daily, weekly) and event-based scheduling (e.g., file arrival, system events). (15961 - DDI and M&O) The Contractor's solution must support file processing both prior to and after transmission, with capabilities to implement file compression and decompression and computing and validating cryptographic checksums. (15962 - DDI and M&O) The Contractor's solution m DDI and M&O must support file processing extensibility through API based capabilities. (15963 - DDI and M&O) The Contractor’s solution must support, at minimum, the Representational State Transfer (REST), Web Services Description Language (WSDL), WebSocket (WS-*), Simple Object Access Protocol (SOAP), JSON, XML, and EDI standard web services and specifications. Any additional proposed messaging formats must be approved by the ARB. (15972 - DDI and M&O) The Contractor's solution must provide the capability to aggregate logs for effective management and analysis. (16033 - DDI and M&O) The Contractor's solution must have the configurable ability to migrate log data to more cost-effective platform storage options (i.e. "standard", "infrequent", "deep") based upon configurable business rule driven criteria. (16034 - DDI and M&O) The Contractor's solution must provide a centralized logging component that supports standardized and configurable storage, management, retrieval, and archiving of all generated SI Hub logs and transmitted module logs. (16035 - DDI and M&O) The Contractor's solution must generate and retain logs of all SI Hub configuration settings changes. (16036 - DDI and M&O) The Contractor's solution must have the configurable ability to import and query log data sent by MMIS modules to the SI platform at a frequency determined by the State. (16037 - DDI and M&O) The Contractor's solution must have the configurable ability to proactively monitor for, import, and index the data of log files transmitted to the SI Hub by MMIS modules at a frequency determined by the State. (16038 - DDI and M&O) The Contractor's solution must have the configurable capability to prioritize the processing of log files transmitted to the SI Hub by log file type. (16039 - DDI and M&O) The Contractor's solution must support the following log fields for all incoming and outgoing transactions: transaction timestamp, transaction ID, transaction size, description of action, user, source IP address, destination IP address, port, and response status code for a duration specified by the State. (16041 - DDI and M&O) The Contractor's solution must support the configurable ability to isolate and retain specific log data for legal holds or audits. (16043 - DDI and M&O) The Contractor's solution must log all SI Hub Managed data requests to load data or to access data at rest in an audit trail, accounting for originating source and user, including any failed attempts or resulting errors. (16044 - DDI and M&O) The Contractor's solution must log and archive all query activities that request to create, read, update, or delete SI Hub Managed data. (16045 - DDI and M&O) The Contractor's solution must store the files and full audit log of MFT file transfer activity for a duration specified by the State, with configuration available to support extended retention in a State designated repository. (16046 - DDI and M&O) The Contractor's solution must support the configurable ability to retain all SI Hub user activity audit log data for a duration specified by the State, with configuration available to support extended retention in a State designated repository. (16047 - DDI and M&O) The Contractor's solution must support retrieval of raw user activity audit log files within twenty-four (24) hours of receipt of request from the State. (16048 - DDI and M&O) The Contractor's solution must provide configurable automated processes that routinely check to see if each module integration point is operating as expected, with the frequency of such checks being configurable by the State. (16050 - DDI and M&O) The Contractor's solution must provide the ability to send error response notification to all sending MMIS modules and supporting components, including the specific errors that were identified and whether the errors precluded loading and/or using the transmitted data. (16051 - DDI and M&O) The Contractor's solution must include tools to monitor SI Hub performance metrics in all supported environments including capacity and CPU utilization, response time, resource availability, network efficiency and load balancing, memory utilization, application performance, and end-user responsiveness. (16057 - DDI and M&O) The Contractor's solution must perform configurable rules-based Data Quality monitoring and exception reporting as determined by IDHW data governance policies. (16060 - DDI and M&O) The Contractor's solution must support the definition, triggering, and sending of configurable user alerts for SI Hub and MMIS module performance, failure, and exceptions in a variety of formats including Short Message Service (SMS) text, email, and automated phone call. (16076 - DDI and M&O) The Contractor's solution must support configurable restricted access and authorization to specific dashboards, dashboard views, and features through the SI Hub IdAM/SSO component. (16080 - DDI and M&O) The Contractor’s solution must calculate Key Performance Indicators (KPIs) based on imported log data sent by MMIS Modules that include at minimum transaction response time, resource availability, CPU utilization, network load, memory utilization, application performance, end-user experience transaction tracing, user monitoring, and any additional KPIs necessary to perform issue resolution analysis. (16081 - DDI and M&O) The Contractor's solution must provide the configurable ability to send alerts to designated users or user groups when configured key performance indicators (KPIs) of a monitored module or component falls outside of configured parameters. (16082 - DDI and M&O) The Contractor's solution must provide the configurable ability to display Key Performance Indicators (KPIs) and tracks MMIS module Service Level Agreements (SLAs) at a frequency determined by the State based on imported log data sent by MMIS modules to the SI Hub that have been designated by the State for active monitoring. (16083 - DDI and M&O) The Contractor's solution must support the import and display of module vendor calculated KPIs and SLAs, certification outcome statuses, and business indicators that have been sent by MMIS Modules in log files to the SI Hub. (16084 - DDI and M&O) The Contractor's solution must provide functionality to query and analyze historical data from SI Hub and MMIS vendor logs. (16085 - DDI and M&O) The Contractor's solution must provide the ability for users to view, search, and filter raw log files (e.g., by date, transaction type, user/system). (16086 - DDI and M&O) The Contractor's solution must log all SI Hub dashboard component access attempts and user activity through the SI Hub Centralized Logging component. (16087 - DDI and M&O) The Contractor's solution must provide the configurable ability to send alerts to designated users or user groups when MFT transmission errors occur, when expected files are not received within expected time thresholds, or when any other errors or exceptions are identified. (16088 - DDI and M&O) The Contractor's solution must provide the ability to view, search, and filter MFT audit log via the dashboard user interface. (16090 - DDI and M&O) The Contractor must provide the ability to generate reports based on MFT activity. (16091 - DDI and M&O) The Contractor's solution must provide "breadcrumb" style navigation on all drilldown or drill through pages and views to facilitate return by the user to higher level content. (16092 - DDI and M&O) The Contractor's solution must support persistent hyperlink navigation to specific dashboard views and features. (16094 - DDI and M&O) The Contractor's solution must provide functionality to display SI Hub platform performance metrics in a customizable dashboard. (16095 - DDI and M&O) The Contractor's solution must support printing a properly formatted representation of all dashboard screens and views, including sections not displayed without scrolling. (16100 - DDI and M&O) The Contractor's solution must provide an on-demand report listing historical integration availability errors for each module with filtering options that include hour, day, week, month, and year. (16102 - DDI and M&O) The Contractor's solution must provide an on-demand report identifying historical data transmission errors. (16103 - DDI and M&O) The Contractor's solution must provide a single unified dashboard experience as configured by the SI Hub SSO component to maintain a user's session under a single login. (16106 - DDI and M&O) The Contractor's solution must provide a configurable notification message or page that displays when the system is unavailable for scheduled maintenance or unscheduled outages. (16107 - DDI and M&O) The Contractor's solution must support the retention of user profile management and user preferences across sessions for dashboard views and features. (16108 - DDI and M&O) The Contractor's solution must support the definition, retention, management, and sharing of user defined detail level and summary level queries, dashboards, and custom data list views where applicable. (16109 - DDI and M&O) The Contractor's solution must support the definition, retention, management, and sharing of user defined “ad hoc” dashboard reports. (16110 - DDI and M&O) The Contractor's solution must provide the configurable ability to display at a frequency determined by the State all module configuration settings and values that have been designated by the State for active monitoring. (16136 - DDI and M&O) The Contractor's solution must provide the configurable ability to display at a frequency determined by the State at minimum the title, description, most recent or current status, start date and time, end date and time (if applicable), and execution frequency of all MMIS module jobs designated by the State for active monitoring. (16137 - DDI and M&O) The Contractor's solution must provide the configurable ability to send alerts to designated users or user groups when scheduled batch processing errors occur, when batch run times exceed configurable thresholds, or when any other errors or exceptions are identified. (16138 - DDI and M&O) The Contractor must collaborate with the System Integration Technical Advisory (SITA) vendor and IDHW to design, test, and implement all standard interfaces required by the approved scope of work. (15926 – DDI and M&O) The Contractor must only implement or revise services within the solution when the IDHW Architecture Review Board (ARB) has approved the proposed Interface Control Specification (ICS). (15931 – DDI and M&O) The Contractor's solution must provide versioning of interface specifications (see DQAA) for services and message formats throughout their lifecycle. (15941 - DDI and M&O) The Contractor must ensure that all System Integration Hub service endpoints are clearly defined with documented and published Application Programming Interfaces (APIs). (15942 – DDI and M&O) The Contractor must store configurations in a version-controlled and auditable Configuration Management System. (16307 – DDI and M&O) The Contractor must provide configuration management reports when IDHW approved changes are made in all IDHW SI Hub environments. (16308 – DDI and M&O) The Contractor must provide a fixed price for forty-two thousand (42,000) blended modification pool hours to be used for design, configuration, testing, coordination, and implementation work as part of DDI. (16316 - DDI Only) The Contractor must coordinate with MMIS module vendor(s) and IDHW as part of all SI Hub Builder and MMIS module DDI phases to replicate the existing external interfaces as directed by IDHW and add any new interfaces identified during each module DDI phase to pass through the SI Hub rather than via point-to-point connections between modules.