What Type Of Stop Field Activities Are Created
The type of customer event (such as, start service, stop service and cut for non-payment) dictate the type of field activity request. If you’ve setup your system properly, the system creates the appropriate orchestration activity for the field activity request, based on the type of service point, state of the service (such as, disconnected-no meter and connect-meter installed) at the service point, state and capabilities of the device. You shouldn’t have to be aware of field activity requests and orchestration activities.
In addition to being linked to the service points, these field activity requests are also linked to the service agreement / service point relationship so that the system can automatically stop the service agreement when the field activities are complete.
Back-to-Back. We use the term back-to-back to describe the situation when a single field activity supports both the stop and start service requests. The fieldwork algorithm delivered with the base package sets up a back-to-back situation by default when it is aware of both the start and stop customers at a premise.
For more information about the field activity requests associated with your SP types, refer to Setting Up Field Activity Type Profiles. Refer to The System Finalizes Most Service Agreements Behind-The-Scenes for information about how the system monitors field activity requests linked to a service agreement.