BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//ChamberMaster//Event Calendar 2.0//EN
METHOD:PUBLISH
X-PUBLISHED-TTL:P1H
REFRESH-INTERVAL:P1H
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:America/Denver
BEGIN:DAYLIGHT
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
DTSTART:20070101T000000
TZOFFSETFROM:-0700
TZOFFSETTO:-0600
TZNAME:Mountain Daylight Time
END:DAYLIGHT
BEGIN:STANDARD
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
DTSTART:20070101T000000
TZOFFSETFROM:-0600
TZOFFSETTO:-0700
TZNAME:Mountain Standard Time
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Denver:20261021T120000
DTEND;TZID=America/Denver:20261021T133000
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
SUMMARY:CAMA Event: Prepare Your Data for AI
DESCRIPTION:Most AI pilots at mid-market manufacturers stall for the same reason. The model is fine. The data underneath it is not ready.This session covers what has to be true before AI gives you an answer you would actually act on. We start with a real failure: two fields\, ship date and shipped date\, that meant different things in two systems and turned into a missed customer commitment with a dollar figure attached.From there we walk the sequence. Define the process before you automate it. Connect and standardize data across your operational systems. Build a semantic model so a term means the same thing in every plant and every report. Then let dashboards answer the common questions and put AI on the long tail where it earns its keep.WHAT YOU WILL LEARNWhy definitional drift\, not model quality\, is what kills most manufacturing AI pilotsHow to define a process well enough that automating it is safe with well defined data definitions What connecting and standardizing across operational systems actually requiresHow a semantic model keeps terms consistent across systems\, plants\, and reportsWhere dashboards belong and where AI belongs\, and why the split matters for costWHO SHOULD ATTENDCOOs\, VP Operations\, plant managers\, IT and operations leadership\, and finance partners at discrete manufacturers. Useful for anyone who owns a number that gets argued about in a monthly review. No technical background required.
X-ALT-DESC;FMTTYPE=text/html:
Most AI pilots at mid-market manufacturers stall for the same reason. \;The model is fine. \;The data underneath it is not ready.
This session covers what has to be true before AI gives you an answer you would actually act on. We start with a real failure: two fields\, ship date and shipped date\, that meant different things in two systems and turned into a missed customer commitment with a dollar figure attached.
From there we walk the sequence. Define the process before you automate it. \; \;Connect and standardize data across your operational systems. Build a semantic model so a term means the same thing in every plant and every report. Then let dashboards answer the common questions and put AI on the long tail where it earns its keep.
WHAT YOU WILL LEARN
- Why definitional drift\, not model quality\, is what kills most manufacturing AI pilots
- How to define a process well enough that automating it is safe with well defined data definitions \;
- What connecting and standardizing across operational systems actually requires
- How a semantic model keeps terms consistent across systems\, plants\, and reports
- Where dashboards belong and where AI belongs\, and why the split matters for cost
WHO SHOULD ATTEND
COOs\, VP Operations\, plant managers\, IT and operations leadership\, and finance partners at discrete manufacturers. Useful for anyone who owns a number that gets argued about in a monthly review. No technical background required.
LOCATION:
UID:e.3612.1650550
SEQUENCE:3
DTSTAMP:20261002T005118Z
URL:https://members.wtcdenver.org/cama-event-calendar/Details/cama-event-prepare-your-data-for-ai-1942413?sourceTypeId=Hub
END:VEVENT
END:VCALENDAR