Production

Ingestion

Captures the service-report emails sent by the field data-collection tool (Skimmer) after every visit and organizes them into a structured database, cross-referencing the information against a pre-registered CMDB (customers, technicians, pools, and products). Ingestion is the foundation layer of the platform: every other module depends, directly or indirectly, on the data it organizes.

How it works

1
Technician performs the service visit at the customer's pool
2
Technician logs the visit in the Skimmer app (checklist, readings, chemicals, photos, and issues)
3
Skimmer emails the report to the customer and forwards a copy of the data to Ingestion
4
Ingestion extracts the data from the email and organizes it using the pre-registered CMDB
5
Database updated and available to the other modules

Who is notified

Not applicable — this is an internal data-capture and organization process, with no notification sent to customers, technicians, or managers.

Real example

Ingestion real example
Skimmer screenshot — chemical readings, visit checklist, and dosages applied (the raw data that feeds Ingestion)
← Platform overview PulseCheck →