Reference
APM Connect System Requirements
License Requirements
APM Connect has a two-tier license system that enables the APM Connect Framework. One of the following license types is required to take advantage of the APM Connect functionality:
- APM Connect Basic
- APM Connect Plus
Additional Licensing
The following additional licenses are required to take advantage of various Adapters:
| Adapter | License | Description |
|---|---|---|
| SAP Adapter | SAP Integration Interfaces | Enables the SAP Equipment, Functional Location, Work History, and Notification Creation Adapters. |
| SAP Technical Characteristics | Enables the SAP Technical Characteristics Adapter. | |
| SAP Work Management | Enables the SAP Work Management Adapter. | |
| SAP PI Adapters | SAP Process Integration | Enables the SAP PI Adapters. |
| Maximo Adapters | Maximo Interfaces | Enables the Maximo Equipment, Functional Location, Work History, Service Request, and Work Order Generation Adapters. |
| ServiceMax Adapters | ServiceMax Enterprise License | Enables ServiceMax Installed Product and Service Request Generation Adapters. |
Note: There is no additional license required to take advantage of the APM Connect Data Loader functionality.
UDLP Versions
Beginning with the Sept. 21, 2018 release, Predix Essentials will maintain compatibility with the APM Connect client-side jobs one version prior to the newly released version.
To prevent processing failures, you must upgrade your on-premises, client-side jobs within two months of a Predix Essentials release to the most current version of the APM Connect client jobs. For example, if the Predix Essentials tenant has installed the Dec. 14, 2018 release, you must upgrade the on-premises, client-side jobs to UDLP V2.5.0 or V2.5.1 by Feb. 14, 2019, otherwise the next release of the Predix Essentials tenant may not process your data correctly.
The following UDLP versions are currently supported in Predix Essentials:
- V2.9.0
Additional Components Required for APM Connect
In addition to the basic Predix Essentials system architecture, your system must also contain the following components:
- Minimum Software Requirements
-
- Windows Server 2012
- Windows Server 2016
- Open JDK 11
Recommended Software for APM Connect Server
- Windows Server 2016 R2
Browser Requirements for APM Connect Server
| Web Browser | Recommended or Supported |
|---|---|
| Mozilla Firefox ESR 68 | Supported |
| Mozilla Firefox up to latest available browser version | Supported |
| Microsoft Internet Explorer 11 or later | Supported |
| Microsoft Edge up to latest available browser version | Supported |
| Apple Safari 12 or later | Supported |
| Google Chrome up to latest available browser version | Recommended |
Minimum Hardware Requirements for APM Connect Server
- Four Processor Core, 2.0GHz
- 16 GB RAM
- 100 GB Free Disk
- 100 MB Network Interface
Recommended Hardware for APM Connect Server
- I5 Processor, 2.0 + GHz
- 32 GB RAM
- 300 GB Free Disk
- 1 GB Network Interface
Tip: APM Connect is input and output intensive, and requires a large amount of storage space. Faster storage is the best way to improve the performance of APM Connect.
Depending on how your system is configured, these requirements may not be sufficient. Parameters that affect the hardware requirements include the number of users, modules purchased, database size, and other factors that can vary from one customer to another. For help refining your specific system requirements, contact GE Digital
Deploying APM Connect
After you have installed and configured the basic Predix Essentials system architecture, you will need to perform some configuration steps specifically for APM Connect.
Note: You need to perform this process only if you are using an EAM Adapter or a Field Service system Adapter.
Predix Essentials Attribute to Reserved Predix Attribute Mappings
The following table explains the Predix Essentials fields or default values that are used to populate the baseline Predix reserved attributes.
| Predix Essentials Attribute or Default Value | Predix Attribute |
|---|---|
| MI_EQUIP000 | familyType |
| MI_EQUIP000_OBJ_TYP_C | equipmentType |
| MI_EQUIP000_MFR_C | make |
| MI_EQUIP000_MOD_NO_C | model |
| MI_EQUIP000_SN_C | serialNumber |
| 03 | status |
| 06 | state |
| MI_FNCLOC00_FNC_LOC_C | Functional Location |
| MI_FNCLOC00_FNC_LOC_DESC_C | Functional Location Description |
| MI_FNCLOC00_FNC_LOC_LNG_DESC_C | Functional Location Long Description |
Predix Essentials Attribute to Predix Attribute Mappings
The following table explains the Predix Essentials fields that are used to populate the baseline Predix attributes.
| Predix Essentials Attribute | Predix Attribute |
|---|---|
| MI_EQUIP000_CAT_PROF_C | Catalog Profile |
| MI_EQUIP000_CAT_PROF_DESC_C | Catalog Profile Description |
| MI_EQUIP000_CHANGE_DATE_D | CMMS Last Changed Date |
| MI_EQUIP000_CONSTN_TYP_C | Construction Type |
| MI_EQUIP000_CONSTN_TYP_DESC_C | Construction Type Description |
| MI_EQUIP000_CREATE_DATE_D | CMMS Creation Date |
| MI_EQUIP000_CRITI_IND_C | Criticality Indicator |
| MI_EQUIP000_CRITI_IND_DESC_C | Criticality Indicator Description |
| MI_EQUIP000_EQUIP_ID_C | Equipment ID |
| MI_EQUIP000_EQUIP_LNG_DESC_T | Equipment Long Description |
| MI_EQUIP000_EQUIP_TECH_NBR_C | Equipment Technical Number |
| MI_EQUIP000_EQUIP_VNDR_C | Equipment Vendor |
| MI_EQUIP000_FNC_LOC_C | Functional Location |
| MI_EQUIP000_FNC_LOC_DESC_C | Functional Location Description |
| MI_EQUIP000_INV_NO_C | Inventory Number |
| MI_EQUIP000_MAIN_WRK_CN_DESC_C | Main Work Center Description |
| MI_EQUIP000_MAIN_WRK_CNR_C | Main Work Center |
| MI_EQUIP000_MFR_C | Manufacturer |
| MI_EQUIP000_MOD_NO_C | Model Number |
| MI_EQUIP000_OBJ_TYP_C | Object Type |
| MI_EQUIP000_OBJ_TYP_DESC_C | Object Type Description |
| MI_EQUIP000_PLANG_GRP_C | Planner Group |
| MI_EQUIP000_PLANG_GRP_DESC_C | Planner Group Description |
| MI_EQUIP000_PLNNG_PLNT_C | Planning Plant |
| MI_EQUIP000_PLNNG_PLNT_DESC_C | Planning Plant Description |
| MI_EQUIP000_PO_NO_C | Purchase Order Number |
| MI_EQUIP000_PRCH_D | Purchase Date |
| MI_EQUIP000_PRT_NO_C | Part Number |
| MI_EQUIP000_SAP_CATEG_C | Category |
| MI_EQUIP000_SAP_CATEG_DESC_C | Category Description |
| MI_EQUIP000_SAP_CLASS_C | SAP Class |
| MI_EQUIP000_SAP_CLASS_DESC_C | SAP Class Description |
| MI_EQUIP000_SAP_SYSTEM_C | CMMS System |
| MI_EQUIP000_SZ_C | Size/Dimension |
| MI_EQUIP000_TECH_DRW_NO_C | Technical Drawing Number |
| MI_EQUIP000_VLD_FRM_DAT_D | Valid From Date |
| MI_EQUIP000_WBS_ELMNT_C | WBS Element |
| MI_EQUIP000_WRNTY_EXPR_D | Warranty Expired Date |
| MI_EQUIP000_YR_CONSTRD_N | Year Constructed |
| MI_EQUIP000_MAINT_PLANT_C | Maintenance Plant |
| MI_EQUIP000_MAINT_PLANT_DESC_C | Maintenance Plant Description |
| MI_EQUIP000_PLANT_SECTION_C | Plant Section |
| MI_EQUIP000_PLANT_SECT_DESC_C | Plant Section Description |
| MI_EQUIP000_SORT_FIELD_C | Sort Field |
| Predix Essentials Attribute | Predix Attribute |
|---|---|
| MI_FNCLOC00_BUS_AREA_C | Business Area |
| MI_FNCLOC00_BUS_AREA_D_C | Business Area Description |
| MI_FNCLOC00_CAT_PROF_C | Catalog Profile |
| MI_FNCLOC00_CAT_PROF_D_C | Catalog Profile Description |
| MI_FNCLOC00_CATEG_C | Category |
| MI_FNCLOC00_CATEG_D_C | Category Description |
| MI_FNCLOC00_CHANGE_DATE_D | CMMS Last Changed Date |
| MI_FNCLOC00_CO_AREA_C | CO Area |
| MI_FNCLOC00_CO_AREA_D_C | CO Area Description |
| MI_FNCLOC00_CO_CD_C | Company Code |
| MI_FNCLOC00_CO_CD_D_C | Company Code Description |
| MI_FNCLOC00_CONST_TYP_C | Construction Type |
| MI_FNCLOC00_CONST_TYP_DESC_C | Construction Type Description |
| MI_FNCLOC00_CREATE_DATE_D | CMMS Creation Date |
| MI_FNCLOC00_CRTCAL_IND_C | Criticality Indicator |
| MI_FNCLOC00_CRTCAL_IND_D_C | Criticality Indicator Description |
| MI_FNCLOC00_CST_CNR_C | Cost Center |
| MI_FNCLOC00_CST_CNR_D_C | Cost Center Description |
| MI_FNCLOC00_INSTLD_ALWBL_C | Installation Allowed |
| MI_FNCLOC00_INTERNAL_ID_C | Functional Location Internal ID |
| MI_FNCLOC00_LOCAT_C | Location |
| MI_FNCLOC00_LOCAT_DESC_C | Location Description |
| MI_FNCLOC00_MAINT_PLNT_C | Maintenance Plant |
| MI_FNCLOC00_MAINT_PLNT_D_C | Maintenance Plant Description |
| MI_FNCLOC00_OBJ_TYP_C | Object Type |
| MI_FNCLOC00_OBJ_TYP_DESC_C | Object Type Description |
| MI_FNCLOC00_PLNNG_PLNT_C | Planning Plant |
| MI_FNCLOC00_PLNNG_PLNT_D_C | Planning Plant Description |
| MI_FNCLOC00_PLNT_SECT_C | Plant Section |
| MI_FNCLOC00_PLNT_SECT_D_C | Plant Section Description |
| MI_FNCLOC00_ROOM_C | Room |
| MI_FNCLOC00_SORT_FLD_C | Sort Field |
| MI_FNCLOC00_STRUC_INDIC_C | Structure Indicator |
| MI_FNCLOC00_SUPR_FNC_LOC_C | Superior Function Location |
| MI_FNCLOC00_SYS_STATUS_C | System Status |
| MI_FNCLOC00_WRK_CNTR_C | Work Center |
| MI_FNCLOC00_WRK_CNTR_DESC_C | Work Center Description |
| MI_FNCLOC00_PLANNER_GROUP_C | Planner Group |
| MI_FNCLOC00_PLANNER_GRP_DESC_C | Planner Group Description |
| MI_FNCLOC00_SAP_CLASS_C | Class |
| MI_FNCLOC00_SAP_CLASS_DESC_C | Class Description |
| Predix Essentials Attribute | Predix Attribute |
|---|---|
| MI_SITE_NAME | Site |
| SC_TAXOCATG_TAX_CATEG_DESC_C | <Category Name> |
| SC_TAXOCLAS_TAX_CLASS_DESC_C | <Class Name> |
| SC_TAXOTYPE_TAX_TYPE_DESC_C | <Type Name> |
Required Server Ports
To provide communication between APM Connect and other systems, make sure the listed ports are open.
| Port Numbers | Description |
|---|---|
| 80, 9080, 8879, 9043, 9044, 9060, 9061, 9430, 9443, 139, 50000, 50005, 3300 | Used for SAP and Maximo Interfaces. |
| 8080, 8005, 7000, 7001, 7777, 7555,1099, 8040, 8101, 9001, 44444, 5432 | Used for Predix Essentials Interfaces. |
| Used for the Oracle client. |
APM Connect Version Compatibility Table
This topic provides the installation files that are required for an APM Connect installation, and the version structure for APM Connect.
APM Compatibility Table
This table includes only the Predix Essentials versions for which a corresponding APM Connect version was released.
| Predix Essentials Framework Version | APM Connect Base | Data Loader | EAM Maximo | EAM SAP | EAM SAP Cloud | EAM SAP PI |
|---|---|---|---|---|---|---|
| V4.6.2.0.0 | APM Connect Base V3.0.2 | UDLP V3.3.0 or V2.9.0 | ||||
| V4.6.1.0.0 | APM Connect Base V3.0.0 | UDLP V3.2.0 or V2.9.0 | ||||
| V4.6.0.0.0 (December 17, 2021) | APM Connect Base V3.0.0 | UDLP V3.1.0 or V2.9.0 | ||||
| V4.5.0.0 (September 29, 2020) | APM Connect Base V2.0.0 | UDLP V2.9.0 or V2.8.0 | ||||
| V4.4.0.0 (April 28, 2020) | APM Connect Base V2.0.0 | UDLP V2.8.0, V2.7.0, or V2.7.1 | ||||
| V4.3.1.0.1 (October 29, 2019) | APM Connect Base V2.0.0 | UDLP V2.7.0, V2.7.1, V2.6.0, or V2.6.1 Note: UDLP V2.7.0 and V2.7.1 are identical for Cloud Server revision only. | ||||
| V4.3.1.0.0 (September 17, 2019) | APM Connect Base V2.0.0 | UDLP V2.6.0 or V2.6.1 and V2.7.0 | ||||
| V4.3.0.7.5 (June 19, 2019) | APM Connect Base V2.0.0 | UDLP V2.5.0 or V2.5.1 and V2.6.0 or V2.6.1 | ||||
| V4.3.0.7.0 (March 29, 2019) | APM Connect Base V2.0.0 | UDLP V2.5.0 or V2.5.1 and V2.6.0 | ||||
| V4.3.0.6.5 (December 7, 2018 | APM Connect Base V2.0.0 | UDLP V2.4.0 and V2.5.0 or V2.5.1 | ||||
| V4.3.0.6.0 (September 21, 2018) | APM Connect Base V2.0.0 | UDLP V2.4.0 and V2.5.0 | ||||
| V4.3.0.5.0 (June 22, 2018) | APM Connect Base V2.0.0 | UDLP V2.4.0 | ||||
| V4.3.0.4.0 (April 25, 2018) | APM Connect Base V2.0.0 | UDLP V2.3.0 | ||||
| V4.3.0.3.0 (December 11, 2017) | APM Connect Base V2.0.0 | UDLP V2.2.0 | EAM SAP PI V2.0.0 | |||
| V4.3.0.2.0 (September 22, 2017) | APM Connect Base V2.00 | UDLP V2.1.0 | EAM MAX V2.0.0 | UDLP V2.1.0 | EAM SAP PI V2.0.0 | |
| V4.3.0.1.0 (August 16, 2017) | APM Connect Base V2.00 | DL V2.0.1 | EAM MAX V2.0.0 | EAM SAP V2.0.0 | EAM SAP Cloud V1.0.1 | EAM SAP PI V2.0.0 |
| V4.3.0.0.0 (June 30, 2017) | APM Connect Base V2.00 | DL V2.0.0 | EAM MAX V2.0.0 | EAM SAP V2.0.0 | EAM SAP Cloud V1.0.1 | EAM SAP PI V2.0.0 |
| V4.2.0.6.0 (March 21, 2017) | APM Connect Base V1.0.3 | DL V1.6.3 | EAM MAX V1.1.2 | EAM SAP V1.6.3 | EAM SAP Cloud V1.0.1 | EAM SAP PI V1.1.2 |
| V4.2.0.4.0 (December 13, 2016) | APM Connect Base V1.0.3 | DL V1.6.3 | EAM MAX V1.1.2 | EAM SAP V1.6.3 | EAM SAP Cloud V1.0.1 | EAM SAP PI V1.1.1 |
| V4.2.0.3.0 (November 15, 2016) | APM Connect Base V1.0.3 | DL V1.6.3 | EAM MAX V1.1.0 | EAM SAP V1.6.3 | EAM SAP Cloud V1.0.1 | EAM SAP V1.1.1 |
| V4.2.0.2.0 (October 17, 2016) | APM Connect Base V1.0.3 | DL V1.6.2 | EAM MAX V1.1.0 | EAM SAP V1.6.2 | EAM SAP Cloud V1.0.1 | EAM SAP V1.1.1 |
| V4.2.0.1.0 (September 21, 2016) | APM Connect Base V1.0.3 | DL V1.6.2 | EAM MAX V1.1.0 | EAM SAP V1.6.1 | EAM SAP Cloud V1.0.0 | EAM SAP V1.1.1 |
| V4.2.0.0 (July 27, 2016) | APM Connect Base V1.0.3 | DL V1.6.1 | EAM MAX V1.1.0 | EAM SAP V1.6.1 | EAM SAP Cloud V1.0.0 | EAM SAP PI V1.1.1 |
| V4.1.7.0 (June 6, 2016) | APM Connect Base V1.0.2 | DL V1.6.0 | EAM MAX V1.1.0 | EAM SAP V1.6.0 | N/A | EAM SAP PI V1.1.0 |
| V4.1.6.3 (June 20, 2016) | APM Connect Base V1.0.2 | DL V1.5.6 | EAM MAX V1.0.0 | EAM SAP V1.5.5 | N/A | EAM SAP PI V1.0.1 |
| V4.1.6.2 (May 20, 2016) | APM Connect Base V1.0.2 | DL V1.5.5 | EAM MAX V1.0.0 | EAM SAP V1.5.5 | N/A | EAM SAP PI V1.0.1 |
| V4.1.6.0 (March 28, 2016) | APM Connect Base V1.0.2 | DL V1.5.4 | EAM MAX V1.0.0 | EAM SAP V1.5.5 | N/A | EAM SAP PI V1.0.1 |
| V4.1.5.1 (March 11, 2016) | APM Connect Base V1.0.2 | DL V1.5.3 | EAM MAX V1.0.0 | EAM SAP V1.5.3 | N/A | EAM SAP PI V1.0.0 |
| V4.1.5.0 (February 9, 2016) | APM Connect Base V1.0.2 | DL V1.5.2 | EAM MAX V1.0.0 | EAM SAP V1.5.3 | N/A | EAM SAP PI V1.0.0 |
| V4.1.1.1 (December 15, 2015) | APM Connect Base V1.0.2 | DLV1.5.1 | N/A | EAM SAP V1.5.2 | N/A | EAM SAP PI V1.0.0 |
| V4.1.1.0 (November 23, 2015) | APM Connect Base V1.0.2 | DL V1.5.0 | N/A | EAM SAP V1.5.2 | N/A | EAM SAP PI V1.0.0 |
| V4.1.0.3 (March 7, 2016) | APM Connect Base V1.0.2 | DL V1.4.1 | N/A | EAM SAP V1.5.1 | N/A | EAM SAP PI V1.0.0 |
| V4.1.0.0 (October 12, 2015) | APM Connect Base V1.0.2 | DL V1.4.0 | N/A | EAM SAP V1.5.1 | N/A | EAM SAP PI V1.0.0 |
| V4.0.0.0 (July 23, 2015) | APM Connect Base V1.0.2 | WPA V1.2.1 | N/A | EAM SAP V1.5.0 | N/A | EAM SAP PI V1.0.0 |
The Automatic Data Loader Directories
The automatic data loader job uses directories within the directory identified in the SCAN_DIR parameter to identify the data loader to use for a particular workbook.
Data Loaders and Directories
The following table lists the directories that are created when the job starts that correspond to the various data loaders.
| Data Loader Name | Directory Name |
|---|---|
| APM Family | ManageAPM |
| Asset Criticality Analysis (ACA) | ACADataLoader |
| Asset Criticality Analysis (ACA Checklist) | ACACheckListDataLoader |
| Generation Availability Analysis (GAA) Events | GAA Events |
| GAA Wind Asset Hierarchy | GAA Wind Asset Hierarchy |
| GAA Wind Events | GAA Wind Events |
| GAA Wind Sub Group Capacity | GAA Wind Sub Group Capacity |
| RCM Analysis Template | ManageRCMAnalysisTemplate |
| Risk Matrix | RiskMatrixDataLoader |
| Taxonomy | ManageTaxonomy |
| Work History | ManageWorkHistory |