SW-117913 - USA (California) - RFI for Integration Layer Software - Deadline September 18,2026

(1) Vendor needs to provide integration layer software • Connect legacy systems and modern applications through a common platform, supporting file transfers, batch jobs, and APIs• Standardize integration patterns and simplify how integrations are built and maintained• Improve monitoring, security, governance, and operational support across the integration landscape• Support reliable, governed data movement into the Unified Data PlatformA. Core Integration Engine• File–based and batch integrations, including flat–file transfers, SFTP, scheduled batch jobs, and database connections for systems that do not support modern APIs• Real–time and event–driven integration, including event streaming, publish–and–subscribe messaging, webhooks, and other asynchronous patterns• Workflow and process orchestration across multiple applications and organizational boundaries• Data transformation and mapping between disparate schemas, protocols, formats, and data modelsB. Identity Resolution, Data Quality, and Conflict Management• Cross–system identity resolution, including matching records that refer to the same person, organization,location, or entity without relying on a common identifier• Configurable matching rules, confidence thresholds, and human review for uncertain matches• Data validation and quality enforcement at the point of integrationC. Security, Access Control, and Compliance• Role–based and attribute–based access controls governing which users, systems, departments, and applications may access specific integrations and data flows• Fine–grained permissions for viewing, creating, modifying, approving, or administering integrations• Integration with City identity and access management systems, including single sign–on and multifactor AuthenticationD. Monitoring, Observability, Reliability, and Recovery• Real–time dashboards showing integration health, transaction volumes, error rates, latency, throughput, and system dependencies• Alerting for failed, delayed, degraded, or anomalous integrations• End–to–end tracing of transactions and events across multiple systemsE. Multi–Tenancy and Departmental Isolation• A shared–services model in which a central team operates the platform and departments consume its capabilities• Department–specific workspaces, environments, permissions, and administrative roles• Mechanisms allowing departments to manage their own integrations without accessing anotherdepartment’s data, credentials, configurations, or workflowsF. Data Ownership, Portability, Interoperability, and Governance• Export of City data in documented, machine–readable, and non–proprietary formats• Portability of configurations, schemas, mappings, workflows, APIs, connectors, and other integration assets• Migration to another platform or service provider without unreasonable technical, contractual, or financial barriers(2) A pre–proposal conference will be held on August 19, 2026.(3) All question must be submitted no later than August 24, 2026.