Skip to main content

Installs and Removals

Overview​

Installs and Removals of configuration-managed assets are performed using a dedicated Object Structure: PLUSAMXAPISAONOFF and associated processing class.

The example below gives examples of removals and installs from the Rapid Transit Metro Train (RTMT) asset created using the example in the New Asset Assemblies load topic:

Rapid Transit Metro Train - Install and Removal Transactions example​

Download Install/Remove Example - MXLoader

Install and Removal Transactions data elements​

An explanation of the data elements required to perform removals and installs is described below:

FieldDescriptionUsed for Install or Remove
PARENTASSETNUMThe parent asset number of the position.
Required for both installation and removal transactions.
BOTH
LCNThe LCN value of the position that the asset to be removed is currently installed into.
The LCN value is optional if a LABEL and POSITION value is specfied.
Note that if LCN is omitted it is recommended that the combination of the LABEL and POSITION uniquely identifies the position the removal/install will be performed against.
BOTH
LABELThe label of the position. Ignored if LCN is specfied.BOTH
POSITIONThe position value of the build position that the asset is to be removed from.BOTH
ASSETNUMThe asset number of the asset that is to be removed. If this is not specified whichever asset currently resides in the position identified will be removed.REMOVE
REMOVEASSETMust be set to 1 if a removal is being performed (false for installs).REMOVE
OFFTIMEThe transaction date and time that the asset removal took place.REMOVE
REMWONUMA work order number to which the removal transaction is to be associated with.REMOVE
INSTALLASSETThe asset to be installed if an installation is required.INSTALL
ONTIMEThe transaction date and time that the asset installation took place.INSTALL
INSTWONUMA work order number to which the install transaction is to be associated with.INSTALL