8 (800) 707-36-15

9:00 to 18:00

Order callback

Your application is accepted!

Our operators will contact you as soon as possible

  • 09:00
  • 09:15
  • 09:30
  • 09:45
  • 10:00
  • 10:15
  • 10:30
  • 10:45
  • 11:00
  • 11:15
  • 11:30
  • 11:45
  • 12:00
  • 12:15
  • 12:30
  • 12:45
  • 13:00
  • 13:15
  • 13:30
  • 13:45
  • 14:00
  • 14:15
  • 14:30
  • 14:45
  • 15:00
  • 15:15
  • 15:30
  • 15:45
  • 16:00
  • 16:15
  • 16:30
  • 16:45
  • 17:00
  • 17:15
  • 17:30
  • 17:45
  • 18:00

Our specialist will contact you

Fill in all mandatory fields

Wrong phone number format

INFOTECH Platform Infotech Reference


Infotech Reference

Reference Data Management System.
Belongs to MDM (Master Data Management) Systems class.

Goals of implementation

  • Master Data


    Master Data

    Ability to ensure there's no duplicated, incomplete, inconsistent data in various areas of business operations.

  • Unified data


    Unified data

    Supports unified entry and usage of data belonging to different areas of business operations and having different structure.

  • Common approach
    to data processing


    Common approach
    to data processing

    Supports various ways of data processing and usage. Not only the data becomes centralized, but also its processing functionality.

  • Centralized
    storing of data


    storing of data

    Enables storing of data in a single system. Unified approach to back-up, archiving and data access.

  • Data access permissions differentiation


    Data access permissions differentiation

    Role-based data access, defining system functions and user permissions.

  • Flexible
    data structure


    data structure

    Ability to create manuals with custom attributes. Enables data connectivity and aggregation.

  • Presentation of data from external sources


    Presentation of data from external sources

    Fast integration bus for external databases makes it possible to configure rules of data presentation.

  • Fast data search
    and filtering


    Fast data search
    and filtering

    You can quickly find the information you need in the common data array using data selection based on the defined criteria and filtering capabilities.

Key components of the System

  • Data storage module

    • storage of data and its meta description
    • data integrity support with limitations and business rules
    • data import and export
    • data versioning
    • data audit and monitoring
  • Data filtering and search module

    • filtration based on data attributes
    • data indexing and full-text search capability
    • semantic search by relevance
  • Integration bus

    • data receiving and import from message brokers
    • data receiving and import from SOAP/REST web services
    • data receiving and import from custom services based on the bus
    • support of key industry standards: OSGi, SOAP, REST, SAML, STS, WSDL
  • Data representation

    • configuring forms for data entry and automatic data representation based on meta description
    • custom entry forms and data views
    • support of multiple languages (i18n)
  • Data builder

    • connection and relationship representation
    • data transformation scripts creation and scheduling
    • adding triggers to data operations
    • data cleaning and normalization operations
    • data de-duplication
    • configuring background batch tasks for data operations, including scheduled ones
  • API

    • access to data and meta description via REST API
  • Security and audit

    • data access differentiation based on roles and permissions

Business benefits of the system implementation

    • a single system makes it possible to increase convenience of operations with data from a variety of disparate systems (financial, accounting, analytical, marketing, customer service, etc.);

    • maintaining currency of data received from various systems;

    • reducing possible errors, duplicates and inconsistent information while working with big volumes of data from various systems;

    • saving your time and money, because significant revisions of databases in legacy applications are no longer needed with migration to data structure development within a single system.

Do you have questions about the product?

Send an application and our business analyst will contact you and give more detailed information.