Data Model Management

Model refers to a data structure which consists of well-organized business data for analysis. Data Model explicitly determines the structured data which stores persistent information in a relational database and is specified in a data modeling language.

Data Model Maintenance within the Infrastructure system facilitates you to upload the warehouse data from the operational systems to database schema using ERwin xml file or Database Catalog.

An ERwin xml file is a standard tagged xml file based on the Object Property Model which can create the required data models. You can upload the xml file by hosting it on the server and customize the update process while uploading a Business Model.

Database Catalog feature is used to generate business model out of the database catalog information. This can be used when a database physically exists and the business model has to be reverse-generated for OFSAA metadata references. The reverse model generation feature can be extended to RDBMS based Infodoms as well. This populates the following:

·       OFSAA logical model abstraction layer, that is, the DATABASE.xml file for the Infodom.

·       Object registration repository

Following are the pre-requisites while working with Business Model upload:

·       Buffer pool has to be available to cache table and index data.

·       The page size for the Table space has to be created appropriately.

Following are the Upload Modes available in the Business Model Upload window:





You can upload a new business model only when you are uploading a model for the first time for the selected Information Domain. This option is not available for subsequent model uploads.

Erwin XML and DB Catalog options are available for New model upload.


Supported incremental changes include:

·       Add tables

·       Drop tables

·       Alter table to add column

·       Alter table to change/remove existing column

 The existing model details are extracted and uploaded along with the specific incremental updates. This option is available only with the subsequent model uploads and captures all the metadata pertaining to the changes in the database schema. The same can be tracked to assess the impact.

Incremental is not supported if DB Catalog is selected for Model Upload option.


You can re-build a model upon the existing model in the database. The existing model is replaced with the current model details. This option is available with the subsequent model uploads and the current model uploaded is considered as the latest model for the selected Information Domain.

Any incremental changes are considered as a ‘Rebuild’ while DB catalog option is used for Model Upload.


You can quickly upload the Sliced model with only the incremental changes, without merging the tables or columns of an existing model. In a Sliced Model Upload you can incrementally add new tables, add/update columns in the existing tables, and add/update primary/foreign keys in the existing model. You can also drop a column or primary/foreign key. However, dropping a table is not supported. This option is available only with the subsequent model uploads.

Sliced Model Upload is faster compared to other upload types as it optimizes the system memory usage and reduces the file size of ERwin.xml.

Sliced is not supported if DB Catalog is selected for Model Upload option.

In sliced model upload, if the version of the Base model existing in the environment is higher than the Sliced model getting uploaded, then the columns (which are not present in the Sliced model) are not dropped. For more information, see Model Versioning section.


You (Business Analysts) need to have IBMADD (Import Business Model) function role mapped to access the Import Model framework within the Infrastructure system.

The Business Model Upload Summary window facilitates to upload the required Business Model and displays the summary of previously uploaded Business Models with their Name, Type (New/ Incremental/Rebuild/Sliced), Enable NoValidate status (Y or N), Result of upload (Success/Failed/Running), Start Date, End Date, Log File path, and Status. You can click the View Log link in the Status column corresponding to the required Model to view the Model Upload details in the View Log Details window.



To display the summary of previous Model Uploads, you need to have a connection pool established to access data from the database. For more information on connection pooling, see OFS AAAI Application Pack Installation & Configuration Guide available in the OHC Documentation Library


You can also search for a specific Model based on the Name or Type (New / Incremental / Rebuild / Sliced) existing within the system.