Follow the jay. It's headed for the world's largest cereal mill.
×
Ready to land at Quaker Oats.
One SAP-native plan with RoviSys. Ingredients, spills, shifts and the people working them all go back onto
PGT, starting at the world's largest cereal mill.
PGT is live. The plant floor is still catching up.
PepsiCo now runs its core processes on the PepsiCo Global Template, built on SAP S/4HANA. Here is what we
hear from the Cedar Rapids floor: since the transition, plant-wide tracking of ingredients, usage and
spillage hasn't fully come back. That's a data problem with a people side, and both of our teams solve
that kind of problem every day.
1873milling oats on the Cedar River
2M+ lbof oats processed every day
No. 1largest cereal mill in the world
~3 mowithout plant-wide ingredient, usage and spillage tracking (reported)
02 / Snap into PGT
jay cloud doesn't sit next to PGT. It plugs into it.
1
PGT stays the record.
SAP S/4HANA remains the system of record. There's nothing new to reconcile against it.
2
jay cloud runs on SAP BTP.
You get your own tenant, test and production, inside the SAP landscape PepsiCo already governs. It's secured by SuccessFactors roles and single sign-on.
3
Four modules snap in.
TIME, ACCESS, VISITOR and LIFE SAFETY read roles, shifts and qualifications from SuccessFactors. Time events land in the Time Sheet through SAP-certified interfaces.
4
Stand-alone tools retire.
Separate clocks, badge databases, visitor books and roll-call lists stop being systems someone has to keep in sync.
Stand-alone tools6
Drag to spin · scroll to build
Native on SAP BTPOwn tenant per customerSAP-certified Time Sheet interfaceSSO from SuccessFactorsdormakaba terminals
03 / Two partners, one plan
RoviSys connects production. jay cloud connects the people.
Each team has its own lane, the lanes don't overlap, and both feed the same PGT record.
Production lane
Plant systems→Production integration→PGT
Brings ingredient, usage and spillage records back into PGT from the plant's own systems.
Velotic (formerly GE Vernova Proficy) Platinum Solution Provider, with 35+ years of product tracking, genealogy and real-time inventory work.
Already working with PepsiCo, so there's no new-vendor learning curve.
The legacy plant system people call “Proficiency” may well be Proficy. If so, RoviSys has been implementing it for more than three decades.
+
LINE 2 · SHIFT B · CREW 7 +3.4 KG → PGT
Workforce lane
People + site events→jay cloud on SAP BTP→SuccessFactors
Time bookings on plant terminals show which crew was on which line, on which shift.
Access, visitor and contractor rules come straight from SuccessFactors roles and schedules.
The same live data drives muster and evacuation.
Poksundo, the company behind jay cloud, was spun off from the dormakaba Group to build on SAP BTP.
Joint use caseWaste by line, shift and crewRoviSys supplies what was spilled and where; jay cloud supplies who was on that line and shift.
04 / One plant, one record
Watch Cedar Rapids run on one record.
EmployeeContractorVisitor
Live simulation · illustrative
Every spill gets a line, a shift and a name.
RoviSys captures each spillage event at the line, and jay cloud knows which crew was clocked onto it. Both post to PGT as it happens, so waste shows up in the shift report, not the quarterly review.
Shift Bposted to PGT
Line 1 · crew 60.0 kg
Line 2 · crew 70.0 kg
Line 3 · crew 80.0 kg
Unattributed so far: 0.0 kg. No line, no crew, no PGT record.
A known floor is a safer floor.
Restricted areas open only for people who are trained and scheduled to be there. Contractors and visitors get the same rules, with safety inductions signed at check-in. Housekeeping no longer depends on who happened to notice, because every build-up is tied to a line and a crew.
On site nowfrom TIME + VISITOR
Employees15
Contractors6
Visitors4
Mill access granted0
Held at the gate0
Everyone accounted for, in minutes.
When an evacuation is called, the muster list is already built from time, access and visitor data, contractors and visitors included. People check in at RFID muster points, and anyone still missing shows up with their last known zone.
0of 25 safe
Elapsed (simulated)
00:00
Still to check in
–
All accounted for. Roll call closed.
05 / Retire the redundant
Fewer systems to keep in sync.
Tap a card to see what replaces it. This is illustrative; we'd confirm the actual Cedar Rapids landscape together in discovery.
6stand-alone tools left
06 / Start at one plant
Cedar Rapids first. Then the playbook.
01 · Assess
Map the landscape
We sit down with your operations, IT and HR owners to map the plant's systems, PGT interfaces, time clocks and HR configuration.
02 · Deliver
Go live on a first line
Waste by line, shift and crew goes live on one line, with TIME and ACCESS for one zone and a scheduled drill.
03 · Expand
Reuse it at the next sites
The interfaces, templates and acceptance criteria carry over to the next qualified PepsiCo plants.
What we'd baseline together
Spillage tied to a line and a crew
Time from spill to PGT record
Stand-alone systems retired
Drill roll-call time
Downtown Cedar Rapids at night · photo: Corey Munson, CC BY 3.0
07 / Next step
25 minutes, both teams, one plan.
Bring an operations or IT owner and someone from HR or EHS. RoviSys and jay cloud will be there together, and we'll leave with three things:
Clear technical ownership: production integration versus workforce and site events.
Production lane
