An efficiently engineered data capture, storage and distribution platform that addresses the entire range of data exchange between internal applications, external entities and all interested parties. IMS Message Hub takes multiple roles in the industry, represented by services listed below.
- Enterprise Message Hub
- Enterprise Service Bus
- Application Integration
- Message Orchestration
- Intelligent Routing (Contend & Context based Routing)
- Data Warehouse (Transactional)
- Platform Integration (Mergers & Acquisitions)
Use the IMS Message Hub to facilitate, streamline and manage all data movements between systems and entities in any format, protocol or schedule with high levels of visibility, control and exception handling capabilities.
Connect with any number of systems/entities using simple parameter settings. Exchange data and facilitated message based communication irrespective of differences in formats and/or protocols.
- Instant Connection
- Real-Time Subscriptions
- Copy to Interested Parties
- Receive any Format/Protocol
- Deliver any Format/Protocol
- Subscription Reports & Billing by Usage
Cut short long development cycles. Eliminate the need for fragile data mapping tools and unwarranted movement of data between services that add zero value to the overall messaging and transaction processing needs.
ECS has a series of Message libraries that are enriched with Field Representation and Message Validation Rules. Libraries include standard and proprietary formats as well as various CBS, OMS and ERP systems. Validation rules include formatting as well as network rules.
- SWIFT MT, ISO 15022
- SWIFT MX, ISO 20022
- FIX, XML, Excel, CSV
- Fixed Length, Delimited
- JSON
- CBS, OMS, ERP – Various
- NACHA by Region, BAI
The platform is also rich with a series of Reference Data Tables. Reference data includes generic, customer specific, vendor subscribed etc. Reference data tables are used for enrichment, validation, routing decisions, process decisions, workflow management etc.
The data tables help consolidate, organize, manage and take responsibility for various types of data. Data can be static or dynamic, manually managed or automatically updated, or a combination of both.
Preferences of customers, counterparties, transactions, stakeholders, as well as requirements of stakeholders and regulators can also be managed through well-defined relational database tables supported by UI screens.
Interest Rate, Exchange Rate, Standing Instructions, Compliance data, etc. from multiple sources are examples of dynamic data.
ECS offers multiple methods for converting messages from one format to another.
- GUI Based Mapping (Industry Practice)
- XML Method (High Volumes)
- Persist Subscribe (Recommended)
Customers can utilize the appropriate method based on the type of message, throughputs desired, dependency on other messages, need for frequent changes, need to wait for specific events, or other related data to arrive, etc.
Support complex data mapping tasks that may require information from other messages for deducing field values or for preparing headers and trailers. Also supports one-to-many and many-to-many message mapping tasks.
Copies of incoming, outgoing or historic messages can be subscribed by any number of interested parties, systems or entities in real-time or batch mode. The subscriber’s preference on format, protocol or schedule can be set on reference data and preference settings tables thereby eliminating the need to write a multitude of complex processing rules. Subscription is supported by one or more of the functions listed below.
- Any to Any Format (MT to MX, CSV to MT, Excel to CSV etc.)
- Any to Any Protocol (MQ to SFTP, SFTP to Webservices etc.)
- Any to Any Schedule (Real time to Batch, Batch to Real time etc.)
- Any to Any Language (MT to English, MT to French, MT to Spanish etc.)
- Any Queueing Service
- Real-Time & Batch
- Synchronous and Asynchronous Communication
Each subscription can be metered for internal or external billing. Subscription reports can be created automatically and sent to the billing department and other designated parties by the end of each month.
Route messages based on content as well as context. Data routing can be done at various places within the platform. Routing is done in stages depending on message processing vs. transaction processing activities. All message-based routing is for the purpose of distribution to various interested parties, while routing at the transaction level is to decide the appropriate parties/channels to be identified for further processing.
The workflow manager can create end-to-end processing of data from entry point/s to delivery channels. Value-added functions can be added to the workflow object by making calls to shared resources like message libraries, mapping objects, validations, compliance etc.
The workflow manager can make content-based decisions, do conditional mapping, work with profiles for determining the sequence of processing that should be adopted by each category/sub-category of messages.
The data received, processed and delivered can be seen through well-designed dashboards. The interface offers action items that can be taken by the appropriate data owners.
Besides, each connection also extends its own Dashboard and Interface. The dashboard offers complete visibility and control to owners of each connection. The interface supports engagement of filters, compliance checks, duplicate checks, validations, approvals and release rules pertaining to each subscription.
- Departmental Views
- Control Settings
- Filters, Validation
- Approval Cycle
- Release Controls
The system generates events specific to each processing stage. Events are kept in the database and become part of the audit trail of each message. Events that require manual interventions are routed to the data owners and also posted on the IMS Notifications Dashboard.
Events are either “Pushed” by the system or “Pulled” by the user through pre-defined parameter settings. On receiving alerts, users who are entitled to take action on messages that need attention will be able to get secured access to the messages.
The Dashboards and Interface screens provided will assist the users in locating the messages and taking the necessary action. The usual activities that happen at the repair stations are:
- Parsing Failure: When the source message did not comply with the format rules as agreed on the integration specifications. The source message may be repaired for parsing to be successful.
- Validation Failure: When the source message did not comply with the field representations as agreed on integration specifications. The source message should not be repaired. Action should be cancellation and a request to initiate from upstream application.
- Message Creation Failure: When the target message could not be created due to lack of information on reference data table. Action will be to update reference data tables and reprocess.
Any repair work will result in approval by the same team/s or by different team/s as required by the processing practices.
The IMS Message Hub is an excellent tool for platform merging when 2 or more enterprises merge through acquisition or partnership. The message hub can rapidly organize the data movement of each entity independently and facilitate controlled movement of data between entities, thereby allowing redundant services to be terminated gracefully.
