The ability to generate custom ABC-LEM reports is a new feature of OT2. The major difference between the ABC-LEM reports and other (Constituent, Services, etc.) query reports is that the reports themselves are not as freely shared between users. They will only work for and be available to the person who created the report. To share ABC-LEM reports, you must select the report you want to share and then RIGHT CLICK the "Make a copy of the selected request" button. Type a unique name for the report (something like "User's reportname") and click the save button. A list of users will pop up. Click the name of the person you want to share the report with and press "CTRL-W" to save it to that person's list of reports. This person will then have their own copy of the report. Changes you make to the report will not affect the report used by the other person, and vice versa.
When designing reports in OT2 it is helpful to keep the philosophy behind OT2 in mind. We believe that your primary goal is to respond to the person making the request, to keep that person happy. Therefore, all of the tables in ot2 are related through the unique Constituent ID number, the SID. Here is a chart showing how LEM records are related to constituent records.

So you can see that LEM records 1-4 relate to service request 2 and constituent record 2, and have access to variables from both of these. LEM records 5-8 have access to service request 3 and constituent record 2 variables, and 9-11 have access to service request 4 and constituent record 3 variables.
Our general rule (which we have broken a couple of times) is that fields prefixed with a 'c-' are from the constituent (sername) table. Fields prefixed with an 's-' are from the services table.
Here is a list of the available fields, the associated variables, and a description of how they are used in the system:
| Field | Variable | Data type | Description |
|---|---|---|---|
| The Bureau (aka Division) to which the employee, equipment, or material has been assigned. | |||
| In the case of labor records, this code holds the description of the type of labor. The choices are Idle, Gear Up, Active, Clean Up, Administrative, Training, Workman's Comp, or Other. Most records associated with particular service requests will be Active. Unused in Equipment and Materials records. | |||
| (Rate (Cost Per))*(Units) or, in overtime labor records, (Overtime Rate Labor)*(Overtime Hrs if Labor) | |||
| The department to which the employee, equipment, or material has been assigned | |||
| The code for the particular service request this item was used for. | |||
| The unique ID for identifying an employee, particular piece of equipment, or material. | |||
| Identifies the record as relating to Labor (L), Equipment (E), or Material (M). L, E, and M are the only values this field should contain. | |||
| In the case of Materials, contains the class of the material. (I'm not sure what this represents) | |||
| The Type code entered for Materials and Equipment. Not used (should always be blank) for labor records. | |||
| I have no idea what this field is. | |||
| In the case of labor records, signifies the number of overtime hours worked by the employee. Equipment and Material records should always contain 0 in this field. | |||
| In the case of labor records, contains the rate at which the employee was being paid for overtime at the time the work was being done. | |||
| In the case of Labor records, the rate at which the employee was being paid for regular time hours at the time the work was being done. In Equipment records, the cost of using the equipment for an hour. in Material records, the cost per unit of the material |
|||
| The date on which this particular work was performed – not the completion date of the service | |||
| The unique constituent record identification code. This number is how records are related to a particular constituent record. | |||
| The units by which the units are measured (ex: feet, inch, cuft, lbs, hrs, each). | |||
| In the case of materials, the number of units used. In Labor and Equipment records, the number of (usually) hours used. | |||
| You can choose to have the exact start and finish time (rather than just the number of hours) entered into Labor and Equipment records by placing a file called 'ts_time.txt' in the root directory of the server installation. If this option is used, this field will contain the exact time work began on this record. | |||
| You can choose to have the exact start and finish time (rather than just the number of hours) entered into Labor and Equipment records by placing a file called 'ts_time.txt' in the root directory of the server installation. If this option is used, this field will contain the exact time work ended on this record. | |||
| The apartment number from a constituent's home address. | |||
| The Suite number from the work address part of the constituent record to which this LEM record is related. | |||
| The name from the work address part of the constituent record. | |||
| If this is an 'Individual' constituent record, contains the street direction from the 'home' address, otherwise contains the street direction from the work address. | |||
| The city from the home address part of the constituent record to which this LEM record is related. | |||
| If this is an 'Individual' constituent record, contains the street name from the 'home' address of the constituent record associated with this LEM record. Otherwise contains the street name from the 'work' address. | |||
| If this is an 'Individual' constituent record, contains the house number from the 'home' address of the constituent record associated with this LEM record. Otherwise contains the house number from the 'work' address. This is a character field and so will be sorted alphabetically (12 comes before 2 when sorting alphabetically). | |||
| The first of the four 'political' fields on the constituent screen. This field was designed to hold the zone code for the zone of the constituent record associated with this LEM record. | |||
| Code–2 from the constituent record | |||
| Code–3 (default is garbage code) from the constituent record to which this LEM record is related. | |||
| The car/mobile phone number from the constituent record to which this LEM record is related. | |||
| The county code associated with the constituent record to which this LEM record is related. | |||
| This user defined field is located right above the ID field on the constituent screen. | |||
| The fax number from the constituent record to which this LEM record is related. | |||
| The home phone number from the constituent record to which this LEM record is related. | |||
| Contains a single character determining the type of constituent record this is: I–Individual B–Business G–Government O–Organization |
|||
| The last name of the individual from the constituent record to which this LEM record is related. | |||
| Contains three possible values indicating to which address from the constituent record to which this LEM record is related correspondence should be mailed to, H–Home (Individual Address) W–Work (Business Address) A–Alternate (Alternate Address). | |||
| If this record has been marked by a query through the Query menu, this field will not be blank. Usually a capitol "I" is used to mark records. | |||
| In the case of an 'Individual' type constituent record, holds the house number from the 'home' address of the constituent record associated with this LEM record. Otherwise contains the house number from the 'work' address. This is a numeric field, so it will sort in numerical order. | |||
| The lowest of the four political information fields on the constituent screen, this field was designed to hold the precinct code of the precinct where the constituent associated with this LEM record is located. |
|||
| The pager number from the constituent record to which this LEM record is related. | |||
| The total number of service requests associated with the constituent record to which this LEM record is related. This value is not currently stable and not to be relied on. | |||
| Designed to hold the gender of the contact individual from the constituent record associated with this LEM record. However, I see nowhere to enter that information, and for the most part the field appears to be empty. | |||
| The unique constituent ID, this time from the constituent (sername) table. Should be the same as Constituent ID (ABC_xx.SID) | |||
| The street direction (ex: N, S, NW, etc.) from the home address part of the constituent record to which this LEM record is related. | |||
| The name of the street from the home address part of the constituent record to which this LEM record is related. | |||
| The street number from the home address part of the constituent record to which this LEM record is related. | |||
| The street suffix (ie. ST, WAY, DR, etc.) from the home address part of the constituent record to which this LEM record is related. | |||
| Contains three possible values: 'E' if the address ends in an even number, 'O' if the address ends in an odd number, and nothing if no address information has been entered. Keyed to the home street address if this is an 'Individual' constituent record or the work street address if this is a 'business' constituent record. If the address ends in 1/2 then 1/2 is ignored, so 321 1/2 Baker ST will be odd but 320 1/2 Baker ST will be even. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| Currently unused. | |||
| TID (default is water billing number) from the constituent record to which this LEM record is related. | |||
| The formal name by which the constituent is to be addressed to which this LEM record is related. | |||
| The second in the list of user defined 'Political' fields, this was designed to hold the town code for the town in which this constituent is located. | |||
| The city from the work address part of the constituent record to which this LEM record is related. | |||
| The work phone number from the constituent record associated with this LEM record. | |||
| The third of the four political information fields on the constituent screen, this field was designed to hold the ward code of the ward where the constituent associated with this LEM record is located. |
|||
| The street direction (ex: N, S, NW, etc.) from the work address part of the constituent record to which this LEM record is related. | |||
| The name of the street from the work address part of the constituent record to which this LEM record is related. | |||
| The street number from the work address part of the constituent record to which this LEM record is related. | |||
| The street suffix (ex: ST, WAY, DR, etc.) from the work address part of the constituent record to which this LEM record is related. | |||
| The Zip code from the work address part of the constituent record to which this LEM record is related. | |||
| The zip code from the 'home' address from the constituent record associated with this LEM record. | |||
| A '1' in this field indicates that the service request which is associated with this LEM record has been printed. Additional printouts of this service request will have the word 'COPY' marked on them. | |||
| '1' in this field indicates additional literature was sent to the constituent about the service request associated with this LEM record. | |||
| A '1' in this field indicates that the constituent associated with the service request this LEM record is associated with was called. | |||
| A '1' in this field indicated that the service request associated with this LEM record was referred. A '0' indicates that it wasn't. | |||
| A '1' in this field indicates that a letter regarding the service request associated with this LEM record was sent to the constituent associated with the service request. | |||
| Contains '1' if the service request associated with this LEM record is marked as ongoing. '0' otherwise. | |||
| Does not appear to be being used currently. | |||
| The apartment field from the service request this LEM record is associated with. | |||
| The Burea (or Division) under which the service request associated with this LEM record falls. | |||
| The date on which the service request associated with this LEM record was received by the public works department. | |||
| The 'Tickler' date from the service request associated with this LEM record. The 'Tickler' date was designed to be used so that if a project was unfeasable at the moment you can be reminded when the time comes to complete the project. It's more like a 'Date work is scheduled to start' field. | |||
| The date on which the work order for the service request associated with this LEM record was assigned to a work crew. | |||
| A unique number used to order the service requests associated with a particular constituent record. The Constituent ID combined with the request number creates the work order number of the service request associated with this LEM record. | |||
| The ID# of the employee who took the request associated to this LEM record. | |||
| The code of the employee who assigned the service request associated with this LEM record to a crew leader. | |||
| The code of the crew leader to whome the job of completing the service request associated with this LEM record was assigned. | |||
| The ID number of the employee who completed the report on the service request associated with this LEM record. | |||
| In the case of a Legislative record, tells whether the constituent was F–for the legislation or O–opposed. This will not usually apply to service requests associated with LEM records. | |||
| The method by which the service request came in: P–Phone M–Mail W–Web(Internet) I–In Person R–Radio O–Other S–Site V–Vmail |
|||
| The time at which the service request associated with this LEM record was received by the public works department in the format A|Phhmm. | |||
| Not currently used. | |||
| The time at which the work order for the service request associated with this LEM record was assigned to a work crew in the format A|Phhmm. | |||
| A three character field used to capture information on the services screen. Contains the city code from the constituent record the service request associated with this LEM request is associated with. | |||
| The PIN number from the constituent record the service request associated with this LEM record is associated with. | |||
| The definition of the service code of the service request associated with this LEM record. | |||
| The Department code of the department under which the service request associated with this LEM record falls. | |||
| Number of employees reported to have worked on this request. The use of this field is now depricated with the new ABC–LEM system. | |||
| The ID number of the key employee working on the service request associated with this LEM record. | |||
| If the service request associated with this LEM record belongs to a subgroup of a division of a department, then this field contains the subgroup code. There is currently no user interface for adding groups to divisions, so this field is used rarely. | |||
| Total number of employee hours used to complete the service request. The use of this field is deprecated. | |||
| The issue code of the service request associated with this LEM record. | |||
| The type of issue of the request associated with this LEM record. Usually all records associated with LEM records will be of type S–Service. S–Service Request L–Response to Legislation I–Response to Public Issue C–General Communication A–Permit or Application E–Event |
|||
| 'T' in this field means that all LEM records (including this one) associated with this service request should be submitted to the state for (partial) reimbursement. An F in this field means that LEM records related to the service request are not eligible for state reimbursement. | |||
| Indicates whether the cost of completing the service request associated with this LEM record should be billed to FEMA or not. A 'T' indicates that the request is re–imbursable, an 'F' indicates that it isn't. | |||
| A four character field from the service request associated with this LEM record. Does not appear to be implemented. | |||
| This field holds the date a letter was sent to the constituent associated with this LEM record regarding the service request associated with this LEM record. | |||
| The name of a standard letter regarding the service request associate with this LEM record was sent to the constituent. Assumed to be the name of the letter sent on the s–Date Letter Sent (SERVICES.LETDATE) date. | |||
| Any value entered into this field indicates that the service request associated with this LEM record has been marked by a query select statement. | |||
| This contains the cross street the service request associated with this service request was located on if it is not on the main street. | |||
| Holds a value from one to 9 indicating the priority of the service request associated with this LEM record. | |||
| I don't know what this field is used for. Appears to be unimplemented. | |||
| Detailed notes about the service request this LEM record is associated with. | |||
| Detailed notes for internal use only about the service request this LEM record is associated with. | |||
| The Precinct code from the constituent record associated with the service request associated with this LEM record. | |||
| The date on which the work on the service request associated with this LEM record was reported complete. | |||
| Contains four possible values indicating the present status of the service request this LEM record is associated with. N–New P–Pending F–Forwarded C–Complete |
|||
| Contains a number from one to nine indicating the status of the resolution of the service request this LEM record is associated with. Unless they have been redefined, these status codes are: 1 – New Entry 2 – Referred to Another Dept/Contractor 3 – Awaiting Response from Resident 4 – Awaiting All Clear on Locates 5 – Work in Progress 6 – Awaiting Repair/Replacement Parts 7 – Weather Permitting/Seasonal Work 8 – Awaiting Cost Estimate 9 – Complete |
|||
| Does not appear to currently be implemented. | |||
| Who made the service request associated with this LEM record. | |||
| The method by which the constituent associated with the service request associated with this LEM record was responded to: P–Phone M–Mail W–Web(Internet) I–In Person R–Radio O–Other S–Site V–Vmail |
|||
| The time at which the work on the service request associated with this LEM record was reported complete in the format A|Phhmm. | |||
| The average number of days required to complete the service request associated with this LEM record. | |||
| The street direction (ie. N, S, NW, etc.) of the location where work is to be performed on the service request associated with this LEM record. | |||
| The unique constituent ID of the constituent record to which the service request associate with this LEM record is associated. This is the main associative field, so the SID number will be the same no matter which record it is taken from. Equivalent to Constituent ID (from the LEM record) and ID Number (from the constituent record) | |||
| The name of the street where work is to be performed on the service request related to this LEM record. | |||
| The house number where the work is to be performed for this service request. This is a text field so these will be sorted alphabetically (12 comes before 2). | |||
| The suffix of the street where work is to be performed on the service request associated with this LEM record. | |||
| In the case of legislative issues, tells whether the office 'Y'–supports the legislation or 'N'–opposes the legislation. This field will not normally apply to service requests associated with LEM records. | |||
| The type of constituent record that the service request record related to this LEM record is related to. I–Individual B–Business G–Government O–Organization |
|||
| Classification (such as A–Administrative) assigned to the service request associated with this LEM record by the operator who keyed it in. | |||
| Contains 'O' if the work on the service request associated with this LEM record is to be performed at an odd–numbered address, 'E' if it is to be performed at an even numbered address. | |||
| Does not appear to be being used currently. | |||
| The tax id number of the constituent associated with this LEM record is also stored in each service request record. | |||
| The township code from the constituent record to which the service request related to this LEM record is related. | |||
| The number of days between when the service request associated with this LEM record was first entered into the system and when the work was reported complete. | |||
| More detailed information about the location of the service request associated with this LEM record. (ie. "Around back", "Behind the bushes", "Next to the mailbox", etc.) | |||
| The ward code from the constituent record to which the issue record related to this LEM record is related. |