Maximo has a multi-siteMaximo has a multi-site, multi-org data structure. The database can support multiple organizations and within each organization there is one or more sites. More, multi-org data structure. The database can support multiple organizations and within each organization there is one or more sites.
The sites are used for data separation, locationsA physical place where assets exist and where work can be performed. More, assets, storerooms and work orders all exist at the site level and will have the attribute SITEID as part of their primary keys.
An organization shares its data with its sites. The primary key of an organization is ORGID, and you will find this also exists in SiteA structural element of a Maximo database that is used for data separation. More level objects, but it is not part of the primary key of those objects, it is a foreign key. Calendars, Crafts, Labor, Companies, and General Ledger codes all exist at the OrganizationA structural element of a Maximo database which is used for data sharing. More level. An organization does not share its data with the sites in other organizations.
An organization is part of the Maximo data structures, it is NOT designed to reflect an organization’s business structures, although that is certainly one consideration.
An organization must have one item set and one company set, but these sets can be shared across multiple organizations. There is only one company set object; it is the Company Master. There are many objects that exist at the Item Set level, like Item Master, Service Items and Tool Items. You will find that while the items in an item set can be shared across multiple organizations, you must authorize it.
System level objects share their data with all organizations and sites.
Some Maximo implementations will have a simple set up, one site, one organization and one of each type of set. Other Maximo implementations will have a more complex set up where there are multiple organizations and many sites. For some, the setup is obvious, for others it can be quite difficult to decide, but whatever you do, take your time and think ahead to how you may wish this to be in the future. If you want to change it in the future, it won’t be easy, these are key fields. Incidentally, SITEID, ORGID and SETID are all defined as UPPER(8), my advice would be, don’t change this.
Classifications and Job Plans are a bit special in that when you create a classification or job plan you decide at what level the record exists, system, organization or site. Once saved you cannot change this.