Domain networks

When you create a utility network, a structure network is automatically created with predefined feature classes and tables. The next step in configuring a utility network is to add one or more domain networks to model each type of resource you deliver. Domain networks contain the network features through which your delivered resource flows and allow you to model large, logically separate sections of your system. These are defined when the utility network is configured by the administrator.

There are two types of domain networks you can create in the utility network:

• Traditional domain networks—These model utility resources through subnetwork management. This domain network type is ideal for modeling source-based systems such as electric distribution in which circuit breakers and transformers model the source of flow, and sink-based systems such as storm or wastewater that model pump stations and water treatment plants as controllers.
• Telecom domain networks—These handle the complexities associated with the high cardinalities of features typically associated with telecom operations such as grouping, color schemes, and support for advanced circuit modeling.

A utility network can have one or more domain networks including a combination of traditional and telecom domain networks. The number and type of domain networks you use depend on the type of model you're building and the industry you manage. While there are differences in the schemas of a traditional versus telecom domain network, both are created with a standard set of classes to model a network.

You can create multiple domain networks for different levels of the same utility resource or the different services your utility manages. For example, you can create two traditional domain networks to manage water distribution and transmission, or create a traditional domain network to manage electric distribution and use a separate telecom domain network to perform circuit modeling of a telecommunications network.

Feedback on this topic?