Acuity Report - Consolidated data

Word document explaining the LFM agregation rules at the laundry

Consolidated vs Raw reports – LFM Rules

consolidated reports include a smart treatment layer in order to improve the consistency of the data and get rid of some operational anomalies

Consolidated receiving at Laundry

	Quantity in RAW EVENT report	Quantity in CONSOLIDATED RECEIVING report	Comments
Item received that was previously shipped to a customer (nominal case)	X	X	If receiving occurs >8h after shipment
Item received that was shipped very short time ago	X		LFM Setting HOURS_LIMIT: delay after shipping to take into account a receiving. By default set to 8h. Useful if the exit door of the laundry is closed to the entrance where the soiled linen is scanned
Item missed at portal (receiving) but scanned on soiled conveyors (launching)	X (launching process)	X	Benefit of multiplying the successive reading points in soiled reception
Item received successively twice	X (2 records)	X (first reception only)	The second event is ignored in consolidated receiving report, whatever the delay between the 2 receptions.
Item that was previously shipped (delivery day reached) and that is scanned in the laundry (washing, packing, shipping, condemning etc.)		X	Receiving event is created a posteriori (at timestamp of the scan in the laundry)
Rejecting at laundry	X (rejecting)	X	Receiving event is created in // for each reject (no need to scan the rejected items through a receiving station)

Consolidated shipping at Laundry

	Quantity in RAW EVENT	Quantity in CONSOLIDATED SHIPPING	Comments
Items shipped to a customer (nominal case)	X	X
Item shipped successively twice to the same customer (with delivery day + day_limit not reached)	X (the 2 successive shipments)	X (second shipment only)	The first event is ignored in consolidated shipping report Delivery day : set on the smart reader for the shipping (ex : today, tomorrow…) Day limit : ACUITY duration parameter. Exemples : day_limit set to 1 and Delivery day = today à the first shipment (Date D) will be ignored in consolidated shipping if the second one occurs before D+1 at 00H00 day_limit set to 1 and Delivery day = tomorrow à the first shipment (Date D) will be ignored in consolidated shipping if the second one occurs before D+2 at 00H00
Item shipped successively twice to 2 different customers (delivery day + day_limit not reached)	X (the 2 successive shipments)	X (second shipment only)	Same as just above
Item inventoried at Customer site whereas it was considered at the laundry (or never seen yet)		X	Shipping event created a posteriori (at inventory timestamp minus 1h)
Item inventoried at Customer B whereas it was previously shipped to customer A			No effect on consolidated shipping report, but Delivery customer (in tag state table) is updated. Shipping event remain the first shipment to Customer A

Consolidated Checkout at the hotel (Hotel in LFM Extended)

Quantity in RAW EVENT

Quantity in CONSOLIDATED SHIPPING

Comments

Items checked out and then the next step is a checkin or any scan at the hotel

X

X then 0

After the checkout the items are added to the consolidated checkout, but if the items are then scanned at the hotel WITHOUT ANY SCAN AT THE LAUNDRY then the LFM considers that these items have remained at the hotel and removes the corresponding quantity from the consolidated checkout report

So finally you can have a consolidated checkout showing 100 items on day D juste after the checkout, and showing 96 items on day D when looking at the report a few days later