The problem: hundreds of alerts per shift, handled ad hoc
The case study says CNH's nine North American production sites generate hundreds of alerts every shift. The events include quality defects, missing parts and conveyor stoppages. Handling relied on radio calls, text messages and manual follow-up. Supervisors could learn about some problems only at the end of a shift.
There was also no shared process. Similar issues could be handled differently across shifts, lines and plants. CNH wanted a standard approach that would:
- route events to the right responders
- track resolution
- keep the information for later analysis
Aron Oechsner, CNH's regional manufacturing engineering manager, said the company wanted a flexible solution that needed fewer internal resources to deploy.
What the Teams workflow does
IGear's Squeaks platform captures operational events from machines, systems and workers. Concept Reply supported the implementation. Teams is the interface, and Squeaks is the event-capture and workflow layer. Teams does not monitor the equipment itself.
According to the report, the integration:
- sends events such as fluid leaks, torque failures and line stoppages to the relevant responders
- attaches supporting information and step-by-step guidance
- lets workers acknowledge responsibility, attach photos and update issue status inside Teams
- escalates automatically to help get events handled within defined timeframes
Sriram Ashok, plant manager at the Racine facility, said the benefit is that Teams is where everyone already is. He can see data arriving, react and collaborate without switching tools.
Background from IGear's own materials
The case study does not describe CNH's technical setup. That means it gives no machine connections, escalation thresholds, licensing or architecture. IGear's public pages describe the product in general terms, and CNH may not use every feature. This is vendor material.
- IGear says Squeaks connects to data sources such as PLCs, SCADA systems, HMIs and other production software.
- For Ignition alarms, IGear says it delivers them to Teams chats and channels using Adaptive Cards.
- IGear says workflows, escalation rules, comments and attachments are available inside Teams.
- Teams mobile push notifications are also part of the module, according to IGear's Teams module page.
- IGear's Teams module page also says its One-Source boards integrate with Power BI, Excel, SharePoint and Entra for user authentication.
For IT administrators, that points to the questions a similar rollout would raise. Who gets access to the app? How are Entra identities and channel permissions managed? Which channels receive alerts? How do mobile notifications behave on shared or frontline devices? The CNH story does not answer these.
Rollout status and results
- Current use: four CNH plants use the Squeaks and Teams integration.
- Planned expansion: a corporate initiative aims to extend it across North American sites.
- Possible global reach: CNH is considering a rollout that could cover more than 30 plants worldwide. That is a possibility, not a commitment or a completed deployment.
- Reported outcomes: CNH says it is already seeing improvements in first-time quality and fewer offline repairs after assembly. The report gives no percentages, time period, baseline or cost figures. It also offers no independent confirmation that Squeaks caused the changes.
The reasoning is plausible. Catching a torque failure or a missing part earlier should mean less rework later. Still, treat these as the company's qualitative claims until numbers are published.
Copilot: still an exploration
Ashok said the priority is to use Microsoft Copilot and Teams to cut repetitive work so people can focus on problem-solving. The report names no Copilot feature running in this workflow, no rollout date and no measured AI results. Oechsner said the integration, especially combined with AI, is changing his view of Microsoft's role in manufacturing. That is his opinion, not evidence of a deployed AI capability.
Takeaways for IT teams
- Putting alerts, assignments, photos and status updates in a tool staff already use can cut context switching and onboarding effort. This is an inference from the described design.
- A structured record of each event supports later review, which was one of CNH's stated goals.
- Nothing here suggests Teams replaces plant-floor systems. It works as the human-facing layer on top of them.
- Anyone considering a similar setup should ask for measured response-time data and a clear technical architecture. The case study offers neither.