There are multiple steps within a typical Line Design Process. While some variations exist for certain utilities, they all follow the same basic pattern.

To be called Line Design Software, it should (at a minimum) perform a structural analysis of a pole structure. To assess clearances and separations, comparison of results is required with national code requirements. Optionally a further comparison with Utility requirements that demand more than the national code may also be considered.

It is rare that a designer would not have someone collect field data for existing pole lines. New developments where no pole line exists would rely on other field data from collected land surveys and development plans. Asset and other GIS data may be combined or used as reference with field data collected in order to build an accurate model for analysis. For instance, asset data can be used to discover pole class/species details that may be faded on older poles.

For outputs, every utility must create a package describing the work required to meet all needs, for internal and often external approval. This package may also include Work Order creation in some cases.

It is advantageous for a line design software to provide a means of ensuring quality, providing access to detailed viewpoints of the analysis and to provide extracts of its results or refined model data for other purposes.

Inputs to assess

• Field Data Collection - What types of input are accepted and what is there scope.
• Code requirements - What codes are supported. Scope and detail are covered elsewhere.
• Utility standards - What utility standards are supported and to what degree are they enforced
• Package Creation - what package creation options and outputs are available. Typically reports, drawings and possibly Work Orders.
• Detailed and other outputs. What features/outputs are available to assist in quality control, understand various analysis aspects in detailed form, and/or other available outputs to assist in data updates and other purposes.