Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

There is an emerging need to create more value for businesses owned by customers and enhance their business opportunities to adapt to the global market. Many companies are now moving from the traditional subscription-based businesses towards the Usage Based Monetization business model.

This stream showcases a simplified version of a DigitalRoute customer use case (Global Leader in Imaging), where instead of selling printers as products, the company sells printing as a service and charges its customers based on actual usage. You will learn in the stream first how to collect different usage events such as the number of printed pages, ink level, and printers' health status. After collecting the data the stream shows how to enrich and aggregate the collected data before sending it to its final destination, in this case, the Printing As A Service Function.


Functions used in this stream and their purpose:

Part A - Input Data Simulation & Clean up: This step generates input data for the other parts of the stream and removes any generated duplicates
Part B - Paper Usage: These step summaries the number of printed paper sheets per customer and sends collected data to billing
Part C - Ink Level: This step checks the daily ink level per customer and triggers an ink order if needed
Part D - Health Status: This part checks the daily health status of printers and sends a request for maintenance if needed
  • Maintenance (Printing As A Service) - Checks printer health status (normal or maintenance require).

  • Printing As A Service 3 - Filters out duplicated records to make sure the health status check event is only processed once per printer.

  • Enrich CRM 3 (Printing As A Service) - Maps printer IDs to companies.

  • Column Filter 3 (Field Organizer) - Renames the input data as desired.

  • To Service (Printing As A Service) - Stores data in a log. This step substitutes the order of maintenance service.


Validate Function

All records that are filtered by the Validate Function can be further processed and corrected with help of Printing As A Service.

  • No labels