Overview of the architecture of the UNICOM Intelligence Data Model.

An interface between the user application and the metadata. The MDM Document simplifies access to the metadata by representing it as an object model, rather than as a serial file.

Used to convert text to unique names that meet certain criteria, such as a maximum length of eight characters or a restricted character set.

Designed to simplify access to MDM variables, to facilitate consistency across products, and to reduce the need to extend the MDM.

Presents the case data in a standardized form that is accessible to any industry-standard data consumer, such as Microsoft Excel, and it enables you to write data to any well-defined data file or database schema.

Implements the SQL summary functions of AVG, Base, Count, Sum, Min, Max, and STDEV.

Implements expression parsing and evaluation. The component is used by both the MDM and the MDM.

Implements stored procedure syntax.

A COM interface for exposing basic data services to the OLE DB Provider.

The MDSC Interface is used for creating metadata source components (MDSCs).

Enumerates case and metadata DSCs. This component can be used by user-applications to browse available DSCs and to select a DSC from which to load a document.

Provides a hierarchical (HDATA) view of the data for other CDSCs that support only a flat (VDATA) view. Also provides a flat view for other CDSCs that support only a hierarchical view. When required, the Table Services DSC is instantiated automatically by the and other UNICOM Intelligence components and functions as a wrapper around the other CDSC.

New in UNICOM Intelligence Data Model 2.5, this component makes it easy to allocate card, column, and punch definitions programmatically; for example, in a DataManagementScript (DMS) file.

Implements the parsing and execution of mrScriptBasic.

Implements logging in UNICOM Intelligence products.

Details of the MDM error messages.

Details of the CDM error messages.