Previous | Next | Contents | Index | Navigation | Glossary | Library |
For example, company A builds surveillance systems. Each system consists of video cameras, recorders, microphones, and motion detectors. The number of each component depends upon the size of the company and the number of installation sites. Each component is covered by a service program. Using systems, you can specify the installation location of each component of the system, and the technical contacts at that location.
For each system you define, you need to enter a system name, the customer who owns the system, and the type of the system you are defining. You can enter more information for your system, if desired, such as a description of your system, the location at which the system is installed, and dates through which the system is valid.
You can also specify a calendar day and month for cotermination of all support services that have been ordered for customer products assigned to the system. This would determine the expiring calendar date for all support services that will be ordered for the customer products assigned to the system.
Oracle Service uses many attributes of a system, such as the install, shipping, and billing locations and contacts, as defaults for the corresponding attributes of any new customer products you define and place under the system. If you change the values of these attributes for the system, Oracle Service references your setting of the implementation option set using the Service Parameters form "System Changes Decision-Point Window Usage" to determine how the change you made to the system-level attribute affects the corresponding customer product-level attribute.
You can group user-defined configurations of customer products into systems, labeling each with a unique descriptive name. You can transfer customer products between systems. You can define specific locations, billing, primary contacts, or system effectivity dates. To link product information to a system, enter a system name in the Customer Products window.
Previous | Next | Contents | Index | Navigation | Glossary | Library |