Integrate
GDIP connects the utility’s enterprise — SAP IS-U, Oracle CC&B, Maximo, PI, market operators, and the Grid Data family itself — through integration flows designed visually and executed on Apache Camel 4. No integration code, ever.
Integration without the priesthood
Enterprise integration usually means a specialist team and a backlog. GDIP replaces both with a visual designer: sources, transforms, routes, and targets drawn on a canvas, compiled to Apache Camel routes, and deployed at runtime — started, paused, versioned, and replayed from the same screen.
Drag-and-drop flows with transform, route, enrich, split, and aggregate steps — enterprise integration patterns without the code.
Kafka, ActiveMQ, RabbitMQ, SOAP, REST, FTP/SFTP, S3, MinIO, Azure Blob, and file — connecting to the customer’s own brokers and stores.
Import WSDL, OpenAPI, JSON Schema, XSD, or CSV layouts; map fields by drag-drop with XSLT, JSONata, and FreeMarker when needed.
Every flow version is an immutable snapshot; deployments reference a specific version and change at runtime with no restarts.
Retries, circuit breakers, and a dead-letter queue that captures failures with full metadata and supports manual replay.
Reusable flow and connector templates for SAP, Oracle, Maximo, and PI shorten the path from kickoff to first message.
Keycloak authentication, AES-256-GCM credential encryption, PII masking in audit logs and DLQ entries, rate limiting and mTLS.
Metrics, tracing, and audit logs, with optional Prometheus and Grafana sidecars.
How it works
Describe each external application and import its contracts — WSDL, OpenAPI, XSD, CSV layouts.
Connect a source endpoint to targets through transform and routing steps; map fields visually.
Publish an immutable flow version; start, pause, or stop the running route without a restart.
Watch throughput and errors; failed messages land in the DLQ with full context, ready to fix and replay.
Use cases
Master data and business events between SAP and the platform, through governed, versioned flows.
Connect new AMI head-end systems to Kafka ingestion without custom adapters.
Wrap SOAP and file-based interfaces in managed flows; migrate targets without touching sources.
Automate scheduled file exchanges with market operators, with full delivery evidence.
A DLQ integration teams can actually work: inspect the payload, fix the cause, replay the message.
Under the hood
Better together
Every family application shares one identity platform, one design system, one registration pattern, and one deployment path.
The most common destination for GDIP flows.
Simulates the SAP and file feeds GDIP integrates.
Tracks GDIP alongside every family application.
A working demonstration takes thirty minutes — on our environment or yours, with realistic simulated data.
8100 Penn Ave S, suite 150j, Bloomington, MN – 55431
+1 (763) 353-4363