Home · Case studies
Case studies
Data and integration case studies
Explore three client projects, covering business context, technical requirements, implementation and platform operations.
What you will find here
Platforms designed to evolve
These platforms have evolved through middleware replacement, event streaming, API management and identity updates, cloud migration planning and new platform releases.
Global container shipping
Maritime transport: EDI integration platform
Customs declarations, container movements, invoicing, vessel tracking: every one of these operations is an integration flow. When they stop, the freight stops. We designed the platform that carries them and we have run it ever since.
One of the world's largest container shipping and logistics groups · Partnership since 2013 · platform designed in 2017 · next generation in build for 2026
Context
This group moves tens of thousands of containers around the world every day. Customs authorities, port authorities, carriers, suppliers, customers and the vessels themselves all exchange structured data with the group's systems, continuously and in several formats. Those flows are the nervous system of the operation rather than a back-office concern.
The relationship began in 2013. In 2017, faced with high-cadence EDIFACT exchange requirements, we designed and deployed a custom enterprise service bus as the backbone of the group's data integration. 10 years later it carries close to 2 million exchanges a day and remains the reference architecture, with no major rewrite of its technical core.
Requirements and constraints
- An integration platform for maritime exchanges. Its architecture evolves with message formats, partners and operational needs.
- An integration platform for maritime exchanges. Its architecture evolves with message formats, partners and operational needs.
- Continuity in a 24/7 critical environmentMaritime freight runs continuously. The platform tolerates no interruption, which sets the bar for both stability and resilience.
- A fully remote team, for 10 yearsContinuity, knowledge transfer and the absence of any single point of failure had to be engineered into the team as deliberately as into the platform.
Implementation
A proprietary ESB designed from the outset to absorb long-term growth in volumes and business needs. Built around EDIFACT and XML flows, and kept flexible enough to take on new uses without a core rewrite for more than 10 years. The difference was not the tooling but the architectural choices made at design time.
- Custom ESB
- EDIFACT
- XML
- Content-based routing
- Transformation
The initial transformation and routing scope expanded to user interfaces, deployment automation and development processes. The team also contributes to requirements analysis and functional changes.
- CI/CD
- Industrialisation
- UI
- Business features
A remote team of ten includes four Satisco consultants in the technical team. JIRA and Confluence document tasks and support knowledge transfer. Automation reduces manual administration.
- JIRA
- Confluence
- Remote
- Automation-first
Platform roadmap
A new platform generation was approved in late 2024, with delivery targeted for 2026. Development alongside the production system supports a phased transition.
Technologies and standards
- Custom ESB
- EDIFACT
- XML
- EDI message routing
- Automated deployment pipelines
- JIRA
- Confluence
Services involved
European public financial institution
Financial institution: integration architecture modernisation
Integration architecture, middleware, data management and platform administration for an institution that processes millions of transactions, files regulatory reporting and exchanges cross-border financial messages in real time.
A European public financial institution · Partnership since 2007 · middleware, event streaming, API management and data virtualisation, each renewed in turn
Context
The institution relies on critical systems for transactions, regulatory reporting and cross-border financial exchanges. Since 2007, Satisco has supported middleware platforms and their development, including data governance.
The engagement now covers the full platform lifecycle, including complete ownership of the data virtualisation layer, which was deployed without any pre-existing internal expertise and is operated by us end to end.
Requirements and constraints
- A fragile point-to-point legacy estateReplacing a web of point-to-point integrations with a scalable ESB, without disturbing production systems processing millions of transactions a day. Every migration had to be surgical and invisible.
- Zero downtime, in a 24/7 institutionCritical operations never stop. Every deployment, migration and update had to be invisible to end users and downstream systems alike.
- Volume and reliability at scale8 million API calls a day with zero errors, continuous real-time monitoring and automatic failover, while business teams expected near-real-time access to data that previously took up to an hour to arrive.
- Regulatory alignment on a fixed calendarContinuous alignment with SWIFT ISO 20022, deployed globally and in synchronisation across every region each November, under strict traceability and security requirements.
Implementation
Migration from the legacy architecture to a modern enterprise service bus. Mirror servers made daytime updates possible with zero interruption, which permanently removed the weekly maintenance windows. IBM Integration Bus migrated to IBM App Connect Enterprise, and WebSphere MQ to Apache Kafka for real-time event streaming.
- IBM IIB → ACE
- WebSphere MQ → Kafka
- ESB
- Mirror servers
- Zero downtime
A suite of specialised platforms deployed and governed: an API management layer carrying 8 million calls a day, centralised authentication across every platform in place of the legacy federation service, and a shared environment for the data science teams.
- API management
- Centralised SSO
- Data science platform
A data virtualisation platform provides access to source data without moving it and a common access point for reporting tools. It includes over a million views, complete data lineage, profile-based security and automated DevOps pipelines.
- Data virtualisation
- >1M views
- Data lineage
- High availability
The role shifted from builder to long-term custodian: rationalising integration flows, cloud migration, security hardening, on-call support and continuous maintenance, with a real-time dashboard for data quality monitoring.
- Cloud migration
- Security hardening
- On-call
- SWIFT ISO 20022
Platform roadmap
The institution is moving progressively towards cloud-native integration platforms, while the most complex flows stay on the current stack for several more years. The data virtualisation platform keeps growing with new sources and new consuming teams.
Technologies and standards
- IBM App Connect Enterprise (ACE)
- IBM Integration Bus (IIB)
- WebSphere MQ
- Apache Kafka
- SWIFT MT → MX / ISO 20022
- API management
- Data virtualisation
- Real-time monitoring dashboards
Services involved
Asset and wealth management
Asset management: SWIFT integration and support
Equities, bonds and derivatives generate a chain of SWIFT messages for every order: instruction, acknowledgement, agent confirmation, settlement. The team that transforms, routes and supports all of them is ours.
An international multi-asset asset management company · Partnership since 2006 · one of our first clients
Context
This asset manager runs multi-asset portfolios on international financial markets and handles time-critical transaction flows. Its SWIFT team is composed entirely of our consultants and is the entry and exit point for every financial flow in the business: everything that comes in and goes out passes through it.
The team complements the client’s functional analysts with technical analysis. It translates finance, trading and middle-office needs into integration specifications.
Requirements and constraints
- Market cut-offs, and zero toleranceMarket cut-offs impose precise order transmission deadlines. Support prioritises incidents according to financial impact and time remaining.
- Two roles in one teamWith no technical analysts on the client side, the team bridges business need and technical implementation as well as building and running the flows.
- The annual SWIFT November releaseEvery November brings format updates tied to new taxes, regulations and international standards. Every affected message has to be re-analysed, updated and retested. Some years that is transparent; some years it is a project.
- Around 600 conversion mappingsThe mapping estate covers routing, filtering and transformation. Every version migration means recompiling and retesting the whole set, which is a project in its own right each time.
Implementation
Bidirectional transformation of every flow: internal formats converted into SWIFT messages and back again. Each trading order generates several messages that all transit through the team, alongside routing, filtering and secure archiving over queues and SFTP.
- IBM TX / ITX
- SWIFT MT
- CSV → XML
- IBM MQ
- SFTP
- Secure archiving
Support is the largest part of the daily work. The team acts directly on urgent financial incidents on middle-office instruction: cancelling orders, correcting a tax or an amount in flight, issuing corrected messages. When it is too late in the workflow to act from the source application, the team acts on the flow itself.
- Level 2/3 support
- Cut-offs
- Middle office
- SWIFT correction
Around 50 Shell, KSH and Bash scripts on Unix and Linux automate operational surveillance: alerts on blocked queues, detection of late files, incident notifications. Alongside that, the team runs the transformation-engine version migrations and the annual SWIFT release.
- Shell / KSH / Bash
- Unix / Linux
- Automated alerting
- Version migration
Technologies and standards
- IBM TX / ITX
- SWIFT MT
- IBM MQ
- SFTP
- CSV / XML
- Shell, KSH, Bash on Unix and Linux
- Portfolio management system interfaces
Services involved
Assess your integration requirements
A 5 to 15 day assessment gives you a flow map, a gap analysis and a costed plan. Fixed price, written to be signed by a decision-maker.
Case studies
Client stories are anonymised to protect client confidentiality.
Measurement scope and period can be clarified with our team when discussing this reference.