Difference between revisions of "ZUGSEIL Service Scheduling (SRS)"

From ZUGSEIL Wiki
Jump to navigation Jump to search
Line 53: Line 53:
*[[Dev:ZUGSEIL appointment-making app (customer)]]
*[[Dev:ZUGSEIL appointment-making app (customer)]]
*[[Dev:ZUGSEIL appointment-making app (broker)]]
*[[Dev:ZUGSEIL appointment-making app (broker)]]
*Appointment Request Process
*Appointment Resource Abstraction Service
* Appointment Making API Service

Revision as of 23:45, 9 January 2023

Scheduling appointments between supplier or customer is an important aspect of every customer-supplier relation. Appointment making can ether happen as part of the sales process or part of the procurement process. in both scenarios the same two parties are involved:

  • The supplier party offering the appointments, which needs to make sure that the resources required for performing the services are available.
  • And the consumer side, which has to reserve the time for appointment in which the services are performed.

Service scheduling in the sales process

In this setup, the service provider just creates a service offering, and hopes that a customer comes and uses the service offer in the form of making an appointment.

The service provider has to define available appointment-types through the appointment-administration apps, which allow to define exactly how appointments are structured and which resources are required for performing these services delivered during an appointment.

The customer either:

  • already knows the service provider digital, and receives the available appointment-slots directly over MT. He creates appointment is his own digital over the appointment-making app (customer)
  • or finds the offering over an appointment making site, which operates the appointment broker role. The customer creates an appointment on the brokers appointment-making app (broker) website, ultimately leading towards his digital knowing about the appointment with the service provider.

Service scheduling in the procurement process

The procurement process chains are triggered by customers from the ZUGSEIL BEST Shop (BS) , but are also required in maintenance of products which is handled in the ZUGSEIL BEST Lifecycle Management (LCM) service bundle.

Service Provider / Supplier-side

When selling products over the b-op platform to customers, each supplier has the option define service products, which can be used in these contexts

Standalone service product

These are products, which represent a standalone service. Regarding scheduling the service provider may define these options at his service product:

  • Does not require appointment making
  • appointment making before order can be placed - the customer must select an appointment before he can place the order If this option is selected, the service provider has to select an appointment type matching the product, and define whether the appointment making is mandatory or optional for the customer in the shopping environment, e.g. ZUGSEIL BEST Shop (BS) or ZUGSEIL BEST Lifecycle Management (LCM) Use case: Book an appointment with a hairdresser
  • appointment making before fulfillment may start - the customer must select an appointment before the fulfillment can start (after the order). e.g. the customer has to visit a optician before correction-glasses can be produced. If this option is selected, the service provider has to select an appointment type matching the product. The system will send out appointment requests to the customer once the order is confirmed. Use case: Purchase a hairdresser as a present for a third party (you purchase and get a gift card, but your friend which got the present, needs an appointment with the hairdresser to get the service)

Bundled service product

A product can be marked a product bundle (formerly set articles). This means that a product does not exist as one physical product, but also comes along with a set of other (service) products. Product bundles are distributed over the regular regular b-op catalog server process. A product bundle may contain other products, which may even cascades through product bundles containing other product bundles. Each product bundle may also contain service products, with these service specific settings relevant for scheduling:

  • Does not require appointment making
  • appointment making before order can be placed - the customer must select an appointment before he can place the order If this option is selected, the service provider has to select an appointment type matching the product, and define whether the appointment making is mandatory or optional for the customer in the shopping environment, e.g. ZUGSEIL BEST Shop (BS) or ZUGSEIL BEST Lifecycle Management (LCM) Use case: optician appointment when ordering a pair a correction glasses (to allocate the resource at the optician)
  • appointment making before fulfillment may start - the customer must select an appointment before the fulfillment can start (after the order). e.g. the customer has to visit a optician before correction-glasses can be produced. If this option is selected, the service provider has to select an appointment type matching the product. The system will send out appointment requests to the customer once the order is confirmed. Use case: Made to measure try-on for a tailormade suit (before production can be scheduled)
  • appointment making to finish the fulfillment process - the customer must define an appointment when the fulfillment process is finished. If this option is selected, the service provider has to select an appointment type matching the product. The system will send out appointment requests to the customer once the order is confirmed and the goods are ready for shipment. Use case: Typically this is made for handover-meetings of products to the customer. E.g. Made-2-Measure Suite try on.

Appointment making requests

When appoints have to be made after the ordering interaction between the service provider and the customer, the appointment-making is triggered by the provider. He either:

Related articles

Related technical articles