Required data

When organization and site data is exported, all related sites, item sets, and company sets are also exported.

Export only customized domains, which include default domains that are customized. For example, if a synonym is added to a synonym domain in your Maximo system, before or after you have exported the initial set of domains, you must export the entire synonym domain.

You can export domains individually. For example, if an asset data export fails due to a missing domain, you can export only the missing domain and then export the asset data again.

None.

Before you export meter data, ensure that the domains in the METERS database table, in the DOMAIN column, are exported.

Meter group data is required only if your assets use meter groups. If you integrated with a Maximo 7.6.1.2 system, you must manually create integration components in your 7.6.1.2 system.

For more information, see Creating meter group integration components.

Before you export classification data, ensure that the domains in the CLASSPEC database table, in the DOMAINS column, are exported. When classification data is exported, the entire classification hierarchy is automatically exported together and in the hierarchy's order.

You can export only asset and location queries. The QUERYMAP synonym domain contains the applications that have exportable queries. In that domain, the application name is mapped to the object structure name.

If the owner of an exported query is not a Maximo Application Suite user who has access to the application or industry solution that the data is exported into, the owner is set to the user who completes the export, and private queries are not exported for that user.

Query data uses the com.ibm.tivoli.maximo.assethealth.procclass.AHIQueryProcess processing class.

When failure list data is exported, failure codes are automatically created.

If you integrated with a Maximo 7.6.1.2 system, you must manually create integration components in your 7.6.1.2 system.

For more information, see Creating service address integration components.

To load geometry data instead of service address data,add the geometry field to the Maximo REST API select clause.

Use these integration components to export updates to existing locations and new location meter readings.

Use these integration components to export existing and new assets and historical asset meter readings.

Before you use these integration components, ensure that you restrict attributes for linear assets and assets that are in storeroom locations. Linear assets and assets that are in storeroom locations cannot be exported. The asset hierarchy is automatically maintained when the asset data is exported.

The processing class is psdi.iface.app.asset.MaxAssetProcess.

Use these integration components to export existing and new locations and historical location meter readings. After you export historical location meter readings, ensure that you export condition monitoring data.

The location hierarchy is not maintained when location data is exported. Locations are exported as individual locations.

The processing class ispsdi.iface.app.location.MaxOperLocProcess.

None.

For the initial export of inspection form data, an inspection form is exported only if the form has an inspection report and is in the ACTIVE or INACTIVE status.

After the initial export of inspection data, you can use an event listener to export revisions to inspection forms. Whether you use an event listener or the Data Export button, inspection form revisions must be in the INACTIVE or ACTIVE status to be exported.

Changes to inspection results do not qualify as revisions to inspection forms.

A job plan or job plan revision must be in the ACTIVE, INACTIVE, PNDREV, or CANCEL status to be exported. After the initial batch of job plan data is exported, use an event listener to export only revisions to job plans.

Preventive maintenance meters are exported with preventive maintenance record data. Preventive maintenance records for linear assets cannot be exported. Before you export preventive maintenance data, in the MHPM object structure, restrict attributes that are related to linear assets. Otherwise, errors might occur during data export.

You must use XML to support inspection results. If you are using XML and you integrated with a Maximo 7.6.1.2 system, you must also manually create integration components in your 7.6.1.2 system.

For more information, see Creating inspection result integration components.

Failure reports that are related to the work orders are exported with the work orders. Work orders for linear assets cannot be exported. Before you export work order data, in the MHWO object structure, restrict attributes for linear assets. Otherwise, errors might occur during data export.

If you use JSON, when a work order is closed, that status change cannot be exported by using an event listener.

Use these integration components with an event listener to export updates to existing assets and new asset meter readings. If you create a new asset in the Maximo system, an event listener does not export that new asset. By default, event listeners export only updates to the data that is already exported. To export new assets, you can customize the processing rules for the publish channel. For more information, see Rule-based customization.

For example, you can specify a SKIP processing rule that contains a NOTLIKE condition to not export assets that have asset numbers that contain AH. If you use JSON, after the initial asset data is exported, updates to the image of an asset cannot be exported by using an event listener.

The asset hierarchy is automatically maintained when the asset data is exported.