ESRI Utility Network and/or Compliance Standard and ITpipes Templates
Template Definition
When a client starts performing inspections and using ITpipes, a template is defined that contains the fields for data input and the inputs to the fields. That template will have asset header fields that exist once for each asset, inspection header fields that exist for each inspection done on an asset, and observation detailed fields that exist for each inspection.
- A client can change templates at any time, however, by doing so, the data fields and inputs used on the template may not match from the old template to the new template.
- For example in the old template, if an observation was called lateral left and in the new template is now called lateral at 9 o'clock, there is a data discrepancy between old and new data. This can make searching, filtering, and querying difficult.
- If a client wants to move from using an existing template to a different template, all legacy inspection data collected can be "mapped" and likely "converted" to the new template. (This service is not included in a standard Service Level or Software Subscription agreement.)
- If a client's ITpipes system is used for GIS or asset management integration, that integration may need set up from scratch.
As a professional service offering, ITpipes can assist with comparison of the existing template and new template, as well as comparison to migrate and/or convert data from the old template to the new template. It is always an option to simply start new data collection with the new template from scratch and maintain an existing "old" project with legacy inspection data using the old template. Users will then need to toggle between projects to search, filter, or query for inspections.
Template Configuration
- ITpipes can have a template configured to meet a client's unique needs or to match the ESRI Utility Network, NASSCO PACP, MACP, LACP, SPICAP, or SCREAM.
- As part of a client's active Service Level Agreement, ITpipes will make template modifications.
- If an implementation is in process it is recommended to hold template changes until the implementation is complete. Keep in mind that template changes in ITpipes at any time, may affect integration to GIS, asset management or other systems.
- Confirming the template to be used for the ITpipes Implementation may require close work with GIS staff, Operations staff, Asset Management staff, and Engineering/Supervisors/Planners or others on the desired fields to be included for field inspections and reporting.
Related Articles
ITpipes and ESRI Documentation
Table of Contents Introduction ITpipes integration with an ESRI geographic information system (GIS) is a powerful way to leverage the capabilities of these advanced systems. This document covers various components of this integration. The purpose of ...
NASSCO PACP Version Changes
ITpipes provides PACP versions1 inside ITpipes at no additional cost to clients with an active SL/SS agreement. If our software is certified in a format, such as PACP or SPICAP, any client can receive that template. With version changes however, the ...
What is an ITpipes Template?
ITpipes is configurable and provides the option for a client to define their Template. The template is used inside ITpipes for data collection and includes the “form” and "inputs to the form", with required fields, set up details and more. Many ...
PACP Import - Continuous Defect
Problem: Import of NASSCO PACP data gives error that data can not be imported. The NASSCO documentation on PACP requires that finishing clock positions, on a continuous defect match. The screenshots here identify the details. Solution: Correct the ...
How to set up a specific (client) template in ITpipes Mobile and why is this important?
For more information on what a client template is, please click here. To setup a client template, you do need the template file from the client. This file ends in the extension "tpl", for example "cityofmonroviaca.tpl". Confirm ITpipes Mobile is ...