There is a set of NASSCO PACP templates to import Storm PACP records. Since PACP is a standardized format you should not need to make any changes to the templates configuration beyond pointing to your source data.
There is a set of NASSCO MACP templates to import Storm MACP records. Since MACP is a standardized format you should not need to make any changes to the templates configuration beyond pointing to your source data.
Sewer TV Inspections
ITPipes
There is a set of ITPipes templates to import Sewer TV Inspections from Granite XP. Agencies that use IT pipes have the option to customize their observations. How your import works will depend on how your observations are setup.
If your ITPipes observations are the same as the observations in the Lucity System you should not need to make any changes to the template's configuration beyond pointing to your source data. However, you should review the field mappings to make sure that all of the information is going where you want it.
If your ITPipes observations are not the same as the observations in the Lucity system you will need to update the correlations tab. This tab allows you to map your ITPipes observations to Lucity observations. You should also review the field mappings to make sure that all the information is going where you want it.
Granite Net
Some GNET databases include a PACP_ prefix before the table names. If this is the case all SQL statements used in the import will need to be updated with this prefix to all table names.
There is a set of NASSCO PACP templates to import Storm PACP records. Since PACP is a standardized format you should not need to make any changes to the templates configuration beyond pointing to your source data.
Storm Structure MACP Inspections
There is a set of NASSCO MACP templates to import Storm MACP records. Since MACP is a standardized format you should not need to make any changes to the templates configuration beyond pointing to your source data.
Work
Work Orders
Work Order Numbers
The Work Order Number is not a required field for the import data; however, it is used to determine uniqueness. The import process operates differently depending on whether or not the user provides a Work Order Number.
When NO number is imported:
If the dataset does not have a Work Order Number, then every imported record will be treated as if it is a new Work Order. The Work Order Number will be generated as specified in the Work Options.
When a number IS imported:
If the dataset contains a Work Order Number value, the imported records do not need to conform to the specifications made in the Work Options.
If an imported Work Order Number is not found in Lucity, the system will assume the data represent a new record and create a new Work Order with the number provided.
If the imported Work Order Number matches an existing Lucity Work Order record, the system will update the existing record according to the import settings (i.e., if the Allow Updates box is checked).
Work Order Assets
There are several fields in Lucity that dictate which module an asset is pulled from. When importing Work Order assets you must make sure the following fields are configured correctly.
Asset CategoryCode - This field must have a mapped value.
AssetInventoryID - This field must not be mapped to anything. The system will automatically figure this value out based on the entered category.
Asset CommonID1 - This field must be mapped to the asset's common ID.
Work Requests
Work Order Numbers
The Work Request Number is not a required field for the import data; however, it is used to determine uniqueness. The import process operates differently depending on whether or not the user provides a Request Number.
When NO number is imported:
If the dataset does not have a number, then every imported record will be treated as if it is a new Work Request. The Request Number will be generated as specified in the Work Options.
When a number IS imported:
If the data contains a Request Number value, the imported records do not need to conform to the specifications made in the Work Options.
If an imported Work Request Number is not found in Lucity, the system will assume the data represent a new record and create a new Work Request with the number provided.
If the imported Request Number matches an existing Lucity Work Request record, the system will update the existing record according to the import settings (i.e., if the Allow Updates box is checked).
Work Request Assets
There are several fields in Lucity that dictate which module an asset is pulled from. When importing Work Request assets you must make sure the following fields are configured correctly.
Asset CategoryCode - This field must have a mapped value.
Asset InventoryID - This field must not be mapped to anything. The system will automatically figure this value out based on the entered category.
Asset CommonID1 - This field must be mapped to the asset's common ID.
Warehouse Imports
If Parts data is collected outside the Lucity system it must be imported to keep the Parts Quantities and Costs up to date. Bulk Parts Transaction information can be imported into the system using the Import and Update program and the Transaction Staging module and must go through the following steps:
Imported - The data must be loaded into the Transaction Staging module using Lucity's Import and Update program.
Validated - In Transaction Staging an administrator runs a Validate Imported Data toolkit against the data to make sure it is formatted correctly. Note: This step is not required since the next step posting data will also validate data; however, some users may find they want to take this step first separate from posting data.
Posted - The data is pushed from the Transaction Staging module into the Parts Inventory using a Post Adjustments toolkit.
Overview Video