This table is the primary table for information about work orders, and contains general information - including a description of the work, assigned title, request date and completion date - about each work order. Each row represents a single work order. The primary key field is EVT_CODE. The EVT_OBJECT field can be joined to the Assets table on OBJ_CODE to know which asset the work order was for.

For the User Guide, please follow this link
For the Data Dictionary, please follow this link

This table contains information about objects that work orders can be written to. Examples of objects types include pieces of equipment, buildings, parks, maintenance districts, and boroughs. Each record has specific information about that object. The primary key is OBJ_CODE.

For the User Guide, please follow this link
For the Data Dictionary, please follow this link

This table contains information about transactions. A transaction tracks the movement of parts and materials between store houses and work orders. Each record represents a single transaction. The primary key is TRA_CODE. When TRA_TOENTITY is “EVNT” then you can use the TRA_TOCODE field to join to the Work Orders table on EVT_CODE to know which transactions are associated with each work order.

For the User Guide, please follow this link
For the Data Dictionary, please follow this link

This table contains work order labor records. Each record in this table corresponds to one labor entry and includes general information about that piece of labor. The primary key is BOO_CODE. The BOO_EVENT field can be joined to the Work Orders table on EVT_CODE to know how much labor was booked to each work order.

For the User Guide, please follow this link
For the Data Dictionary, please follow this link

This table contains specific information about each part that is included in a transaction. Each record has information about one type of part in the transaction. A single transaction could have multiple lines (one for each type of part) in this table. The TRL_TRANS field can be joined to the Transactions table on TRA_CODE to know which parts were part the transaction.

For the User Guide, please follow this link
For the Data Dictionary, please follow this link

This table all comments for all tables in AMPS. The record for each comment indicates which record and table the comment pertains to. Each record is a single comment. The ADD_CODE field can be joined to another table according to the value in ADD_ENTITY.

For the User Guide, please follow this link
For the Data Dictionary, please follow this link