3.3.2 Evaluating the items to be considered when services are added
After you have decided the service template to be used, evaluate the service names, and tags, service groups, and properties that are to be associated with the services as the items to be specified when services are added.
The following provides an overview of items that you must specify.
Service names
Evaluate appropriate names for the services, based on their usage and operation.
Tags
Evaluate appropriate tags to be set for the services. A tag is information for categorizing services, and is used as a key for searching. By categorizing services by using tag groups (large classification) and tags (small classification), you can easily search for the service you want. Decide the tags to be used for categorizing services, depending on the purpose of use and operation of services. For example, you can use tag groups for categorizing services by the operation-target devices or divisions, and tags for categorizing services by the purpose of operation or person in charge.
Service groups
Evaluate appropriate service groups to be assigned to the services, based on the evaluation result during operation design.
If a service group is assigned to services, only the user groups that have a role for that service group can manage or execute the services.
If you do not create and use your own service group, you can use the built-in service group (DefaultServiceGroup).
-
Properties
The properties depend on the service template. Check the service template that you will be using, and then evaluate the property values to be specified. For details about the properties of service templates provided by JP1/AO, see the descriptions of the properties of individual service templates in the manual JP1/Automatic Operation Service Template Reference.
If there is no need to change property values each time a service is run, evaluate specifying those properties when you add the service. If there are properties that will be shared among multiple services, evaluate defining them as shared service properties.
Some service templates display the properties specified by means of window operations when the service was added (or edited) so that you can change (overwrite) the property values when you run the service.