Enterprisewidereporting within capital market organizations must address the challenge of data collection and aggregation on a daily basis.  Data from as many as hundreds of existing front-, middle-, and back-office systems is often created and handled in a very decentralized manner, usually within individual functional silos and with specific system-dependent processes. Moreover, the ability to monitor the overall data collection and aggregation processes is limited or nonexistent, with no way to report on readiness or completeness.  This results in data inconsistencies and omissions that, in turn, lead to inaccurate risk management reporting and analysis.

CenterSphere’s ConnectionCenter module gives your firm an integrated framework for monitoring all key reporting systems and the data feeds they are required to provide.  It also allows for enterprise-wide software system inventory and data source definition.

ConnectionCenter’s system monitoring capability is built on our Enterprise Application Integration (EAI) tool set.  Through EAI, your firm can monitor its daily feeds and their status, the types of data they contain, the organizational entities they cover, and the transformations required to normalize data to a consistent format.  Production workflow processes can also be associated with their respective data feeds, enabling conditional business logic to be triggered by the data feed.  This enables early detection and correction of errors.  Our EAI tool set allows the display of the message flow data transformation schema that has been set up for each data source to bring data into CenterSphere.

• Allows enterprisewide software system inventory.
  
  
  • Can drill down by software system type.
  • Can display associated data sources provided by each software system.
  
  
• Supports data source definition.
  
  
  • Can define the data type content for each data source.
  • Can define ownership and organizational entity coverage.
  • Allows data transformation processes to be assigned to each data source.
  
  
• Allows monitoring of data feeds.
  
  
  • Feeds can be monitored by system, organizational unit, or transformation and workflow processes.
  • Exception reporting for missing or incomplete feeds is available, with optional workflow process triggering for investigative follow-up.
  • Audit reporting of data transformation (as defined by the transformation process for the given data source) and message routing processed by the message brokering middleware are available.
  
  
• Provides workflow-driven production management.
  
  
  • Processes associated with data feeds can be configured as workflows, which trigger a sequence of activities that can be automated system processes or human review and approval actions.
  • Workflows can be initiated by the arrival of a feed “pushed” from a data source, or can be started by authorized users to request (or “pull”) associated data (effecting the relevant data transformation/message flow operations).
  • More specific workflows can be initiated by higher-level workflows that contain all the dependency logic to produce upper-level, integrated management reports.