One AI Layer, Every SyteLine Role
The walkthroughs below show how different roles use SyteRay against a live SyteLine environment. The scenarios are illustrative composites of how the product is designed to be used, not customer testimonials, and every capability described is a real, shipping feature.
CSR / Order Desk
A customer calls asking where their order is. Instead of tabbing through Customer Order Lines, shipment forms, and item availability screens, the CSR asks SyteRay: “What’s the status of every open line for this customer, and which ones will ship this week?”
- 1SyteRay answers from the live database in seconds, listing each open line with promise date, quantity remaining, and shipment status, and shows the SQL and source tables behind the answer.
- 2The follow-up (“which of those lines are blocked by inventory?”) reuses the same conversation context, so the CSR drills down without re-explaining.
- 3Before quoting a new date, the CSR checks the open-orders dashboard, which reads the same semantic views, so the number they quote matches what the planner and the controller see.
Controller / Finance Close
It is day two of month-end close and a number in the bookings report does not match the sales team’s tracker. The controller needs to know which definition is right, and why they differ, before signing off.
- 1The controller asks SyteRay for bookings for the month; the answer arrives with the exact SQL and the semantic view it read, so the definition of a booking is inspectable rather than folklore.
- 2A Deep Research request (“investigate the gap between booked and shipped for this month”) walks orders, shipments, and invoices across tables and returns a structured report with the discrepancies itemized.
- 3The CSV export of the supporting table goes straight into the close workpapers, with the SQL preserved as the audit-ready explanation of where the number came from.
Planner / MRP
Monday morning: MRP ran over the weekend and the planner needs to know what actually changed and what needs action today, without paging through planning detail forms one item at a time.
- 1The planner asks for items with demand inside lead time and insufficient supply; SyteRay returns the list with the underlying query visible, filtered to the planner’s site.
- 2Follow-up questions (“which of these have open POs already?”, “which jobs consume this item?”) chain naturally, replacing a dozen form lookups.
- 3The shortage list exports to CSV for the morning production meeting, and the same view is pinned as a dashboard so the picture stays live all week.
Purchasing
A buyer preparing for a supplier call wants the full picture: open POs, receipt history, late deliveries, and price trend for that vendor, information that lives across half a dozen SyteLine screens.
- 1One question to SyteRay assembles open purchase orders for the vendor with due dates and receipt status, evidence attached.
- 2A Deep Research run on the vendor produces a structured brief: spend history, delivery performance, and open exposure, drawn from purchasing, receiving, and payables tables.
- 3During the call, follow-up questions are answered live, so negotiation happens with the actual numbers rather than last quarter’s spreadsheet.
Plant Manager
The plant manager wants one screen at 7am: shipments going out today, orders at risk, and where the plant stands against the month, without waiting for someone to refresh a spreadsheet.
- 1SyteRay’s curated dashboards cover open orders, bookings, and shipments as KPI tiles, charts, and sortable tables over live data.
- 2When a tile looks wrong, clicking into the conversation lets the manager ask why, and the answer comes back with the evidence, not a shrug.
- 3The daily view prints cleanly for the production meeting, and because every dashboard reads the shared semantic views, finance and operations argue about the plan, not about whose number is right.
IT / SyteLine Developer
A developer inherits a 15-year-old SyteLine customization layer and is asked to change how a field is calculated. The real question is: what will this break? This is where SyteRay’s stored-procedure intelligence turns one developer into ten.
- 1SyteRay has already cataloged the site’s stored procedures (8,636 on the reference deployment) with each procedure’s reads, writes, calls, and transitive effects, so “what touches this column?” is a query, not an archaeology project.
- 2Impact analysis before a change: list every procedure that writes the table, directly or through nested calls. Dead-code review: start from the procedures no other procedure calls.
- 3For new work, the developer authors SQL with the schema pack and query enforcer as guardrails, and write operations go through the same governed preview-confirm-audit flow as everything else.
Which Role Would You Start With?
Bring one workflow and your own SyteLine data. We will show you the rest.