BM and ED

There are 3 databases at the minimum required to develop and deploy a Pivotal system

Toolkit Customisation Module

This database is the cornerstone for the Pivotal application and defines the functionality available to the developer. This database stores the information about form definitions and rules used to create Tables, fields, queries, forms etc in the Business Module. This is often called Cust, CM or Meta Meta or simply toolkit. It is only updated by Pivotal themselves and released with updates to the Toolkit.

Business Module

This database stores all the information about your business logic. Pivotal provides Out of the Box (OOB) functionality which is a good starting point, but most customers will update this to include their bespoke business rules by creating tables, fields, client scripts, agents and forms. The Business Module is most often references by the BM.

A customisation system will require the Toolkit Customisation Module to be established as the BM (Meta Meta) and the BM as the ED (Meta) as you are using the CM to update the BM.

Enterprise Data

This database is the datastore of your application. Tables defined by the BM are physically located here to store your businesses data, such as companies and contacts. The UFO process will take the tables as defined in the BM to be physical reality in the ED. The Enterprise Data is commonly referenced as the ED.

For a production system, a BM & ED are paired together.