IoT and edge pilots stall when a sensor proof never becomes field operations modernization. A gateway can publish a reading and still leave crews, planners, and SAP on the old process. Scale means you connect field data with enterprise systems, then put adoption and ongoing operations in place. The asset owner and the device vendor keep the device fleet. Resolve Tech Solutions supports that connection and the operating model. The asset owner and the device vendor keep the device fleet.
Quick Answer
A pilot is unfinished until an edge event changes maintenance, operations, safety, or cost in a system of record. Name the asset, the event, the owner, and the action before you add sites. Fleet identity and signed updates belong to the asset owner and the device vendor. Resolve Tech Solutions connects approved field data with enterprise systems and supports the operating model.
Table of Contents
- Quick Answer
- Table of Contents
- Why do IoT and edge pilots stall?
- What must a field operations scale path include?
- How does edge data reach enterprise systems when the network fails?
- Who owns the device fleet, and how do you prove value?
- How does Resolve Tech Solutions support the connection?
- Frequently Asked Questions
Why do IoT and edge pilots stall?
Most pilots copy a happy path. One gateway, a clean network, and an engineer on site. Field operations do not run that way. Remote substations, compressor stations, and plant sites have uneven connectivity and different change windows.
At a scale threshold of 500 devices, the fleet record must name the asset, the software, and the change approver. If those answers live in spreadsheets, the pilot is not an operating service. That fleet gap belongs to the asset owner and the device vendor.
Field operations modernization stalls when the alert never becomes a work order or a planner decision. Data without a response path is telemetry expense. The pattern worth naming is that these pilots rarely fail on technology. They fail because nobody agreed in advance which planner would act on the alert. One honest caveat: if the device fleet itself is unmanaged, no amount of enterprise integration will make its data trustworthy. The asset owner keeps the control boundary, the SCADA design, and the PLC and RTU environment. Do not send every tag to the cloud. One useful signal is a condition alert that creates a maintenance notification in SAP S/4HANA Asset Management or SAP PM.
In an assessment, Resolve Tech Solutions identifies which operational data must reach SAP, ERP, or the historian, and which work process must change. SAP services and ERP services belong in that assessment.
What must a field operations scale path include?
A scale path is field operations modernization, not a larger hardware order. Connect field data with enterprise systems. Drive adoption at the sites that must use the new path. Run ongoing operations after the pilot team leaves.
The asset owner and the device vendor still need fleet controls before the connection can scale. The minimum set is fleet identity, secure software delivery, store-and-forward data, and observability.
Fleet identity stays with the asset owner
Give each gateway a fleet record with asset ID, site, software image, network zone, and owner. Use a per-device X.509 certificate in TPM 2.0 hardware or a secure element, with mutual TLS for cloud ingress. A shared fleet credential is not acceptable.
Match segmentation and remote access to ISA/IEC 62443 zones and conduits. Use NIST SP 800-82 Revision 3 as the OT security reference for the asset owner. Resolve Tech Solutions can support the enterprise side of that boundary through cybersecurity services.
Software updates stay an owner process
An over-the-air update needs a signed artifact, a maintenance window, health criteria, and a tested rollback path. An example, not a client result, starts with five noncritical devices, then 5 percent of the approved fleet. The device vendor and the asset owner run this process.
During implementation, Resolve Tech Solutions connects the approved event to the SAP record or historian object that must receive it. That work is systems integration, not device-fleet design. For a move to SAP S/4HANA, match the notification and the asset master to S/4HANA transformation.
How does edge data reach enterprise systems when the network fails?
Field connectivity is a variable, not a precondition. The edge runtime must keep local collection and permitted local decisions during an outage, then synchronize when the link returns. Many proofs of concept fail because the team tested them only on a stable corporate network.
Use a durable local queue with a UTC timestamp, a sequence number, asset context, and a data-quality code. An example operating target is 72 hours of priority retention for critical events. The enterprise service must accept idempotent writes and late or duplicate messages.
The site team normalizes OPC UA, Modbus, or DNP3 data into one asset and event model. The message must carry the source asset, the timestamp, the quality status, and the recommended action. Resolve Tech Solutions connects that message with the enterprise system. Teams that start this work use SAP services early, because the asset master decides whether the alert can open work.
If the cloud tier sits on the IT side of the boundary, coordinate identity and recovery with cloud services.
Who owns the device fleet, and how do you prove value?
The asset owner runs the device fleet with the device vendor. The process owner owns field operations and the business outcome. Resolve Tech Solutions supports that connection and the operating model.
| Decision area | Accountable role | Evidence |
|---|---|---|
| Device fleet, identity, and updates | Asset owner with the device vendor | Fleet record and update log |
| PLC, RTU, and SCADA boundary | OT or engineering lead | Approved tag map and zone design |
| Field data connection to enterprise systems | Integration owner | Interface map and SAP or ERP object link |
| Security of the enterprise connection | Cybersecurity leader | Access review and response playbook |
| Adoption and business outcome | Process owner | Training records and action log |
Prove the outcome in phases
Use a phase sequence, not a calendar promise. Phase 0 maps one asset class, its failure modes, the signals, and the response in SAP or ERP. Phase 1 commissions a small first group, tests an outage, and traces one alert into a work process. The fleet owner deploys the signed update. Phase 2 shows site adoption and a finance-reviewed value calculation.
Example calculation: Avoided cost equals the decrease in truck rolls times the fully loaded cost per roll. Count a roll only when the work record shows that the connected alert caused the action. Finance must approve the baseline and the cost per roll. This example is a method, not a Resolve Tech Solutions result.
After that calculation holds, move ongoing operations to managed services. That support covers the integration, the adoption cadence, and exception response. Device updates stay with the fleet owner. Treat connection security as a release criterion with cybersecurity services, not as a review after launch.
How does Resolve Tech Solutions support the connection?
Resolve Tech Solutions supports the connection of field data to enterprise systems and the operating model around that connection. That support is assessment, integration, adoption, and ongoing operations.
In assessment, Resolve Tech Solutions maps the field events that must reach SAP, ERP, or the historian. In implementation, it completes the systems integration and the handoff into maintenance and work management. In adoption, Resolve Tech Solutions works with the process owner so crews and planners use the new path.
After launch, managed services can cover integration health and the adoption cadence. Where approved field data must feed a decision aid, AI services can support that enterprise step.
Frequently Asked Questions
What drives cost in a production program?
Fleet cost includes site entry, connectivity, and scheduled updates. Enterprise cost covers the integration work, then the slower cost of getting crews to use it. Resolve Tech Solutions can support the enterprise estimate.
How long does the first repeatable release take?
Use the phase sequence in this article, not a calendar promise. Add time when plant change windows or safety reviews limit field work.
Which edge platform fits legacy field systems?
Select the platform after you define the contracts it must meet. A vendor demo is not a substitute for a brownfield gateway test. The asset owner and the device vendor make this choice.
How do you secure edge data and measure return?
Secure edge data with device identity, least-privilege access, encrypted transport, and signed software. The asset owner holds those fleet controls. Measure return against a finance-approved baseline, and tie each claimed benefit to a recorded action.