Does your key data arrive too late when you need to make decisions? How often do you immediately need to obtain more and more information about your customers? Are your operational processes in need of a thorough tune-up to get it back in working condition?
To achieve all of the above you need a new information system known as an Operational Data Store. Identifying all your operational information needs is a piece of cake for ODS as its primary function is to support these operational processes and not let them be hindered by any other work that could interfere with or slow down its activity. The right ODS can support both the operational, as well as the operational-analytical parts of your processes at the same time, thus enabling you to pay more attention to your business. Our new ODS will even cooperate with your existing processes and systems so it will not tie up your hands or limit your activities in the short- or long-term. In short, it will help you reach your targets and fulfill your plans.
A properly implemented ODS can speed up critical operative processes by as much as 80 %.
Our ODS solution offers proven methodologies, processes, design and data models, technological solutions and tools that ensure maximal effectiveness and impressiveness. It also puts great emphasis on metadata.
This approach ensures a long-term sustainable solution and lets you benefit from the Model Driven Development technology, where most of the program code is generated, to ensure superlative development productivity, lower prices, an exceptional level of standardization giving you the keys to all the practical know-how we have accrued in the course of our numerous ODS implementations.
As for applications, ODS can be used for customer or product data integration. Of course, we must not forget that this solution is ideal for Campaign Management or Master Data Management as your data base can be easily connected to ODS. The potential is endless.
ODS can fulfill the following roles:
Regarding the frequency of performance and data updating, ODS can be divided into the following groups:
Regarding data integration, ODS can be built on various data-mining methods:
Regarding the logical architecture, our solution consists of several components:
Data storage is the cornerstone of the entire solution. It preserves the data, as well as some selected metadata, necessary for a fully-functioning solution. As a repository it uses proven, tested relational databases. The data model can be designed according to customer needs, or, we can use one of our tailor-made industry models, such as those used in banking and in financial institutions.
The transformation layer is the main carrier of application logistics in the ODS solution. It enables transformation between the outside world and data storage. Primarily, it is the API which enables the processing of individual data records or ETL/ELT, which processes entire groups of data sets. This principle of the filtering layer screens the outside world from the internal data module enabling modifications to the model according to actual requirements and without the necessity of rebuilding everything. The transformation layer can carry out data transformations in real-time, almost-real-time or in batches, according to the customer needs and requirements.
The communication layer connects the ODS with the outside world ensuring the transformation of input and output communication. Essentially, this layer technologically translates communications into a format that ODS can process internally and vice versa. This modular attitude enables us to implement our solution effortlessly into environments that require a specific way of communication, such as web services, specific connectors or specific formats of communicated message. Moreover, the possible communication tools can be easily modified when required.
We place great emphasis on our solution tools. Adastra tools ensure easy central administration of metadata solutions, administration of data modules, administration of data transformations and accurate data flows, including their timing, creation of documentation, solutions monitoring as a functional entity and integration of the communication layer. We understand the importance of metadata and their follow-up usage for development and operations.
As it was establishing itself in the Czech Republic, Adastra was asked by Equa bank to create an on-line integration layer. Using an ESB tool Adastra created an integration hub, where individual systems are interconnected, as well as a unified on-line store for client data (ODS – on-line data store).
How do you create a data warehouse and bank reporting for a newly established bank? Would you like to know? Keep reading! Equa bank is exactly such a case. Not only that, the bank requested some data from an online data warehouse. No small feat considering the data had to keep its consistency and be integrated in the data warehouse to provide an…
The Adastra Banking Data Model (ABDM) has enabled our customer to build a completely new system for approving loan products, an Operational Data Store and a new consolidated data warehouse (Analytic Data Store). The banking model continues to prove its flexibility and efficiency above all other solutions that use this model even after many years…
The client is an international company that sells its products worldwide which must report results in an exact and precise way on a monthly basis. Adastra provides the company with a system that guarantees complete overview and accountability of all key indicators, generates annual closing numbers, in addition to forecasts for the end of the…
Following consultations with Adastra, the bank successfully migrated and consolidated its databases on the Oracle Exadata Database Machine platform. Thanks to this, the bank dramatically simplified its IT infrastructure with regard to databases, making them more effective and faster, all while cutting IT infrastructure costs.