What is New in ICOP V3.0
ICOP V3.0 introduces four headline features. First, mobile push notifications: alarm and warning events are pushed to operator smartphones within 3 seconds of detection, with severity tagging and a one-tap acknowledgement workflow. Second, AI risk prediction: the platform runs a per-cabinet risk model that learns the historical temperature, vibration, and load profile of each cabinet and flags abnormal patterns up to 72 hours before a fault develops.
Third, the redesigned dashboard. V3.0 reorganises the operator view into three layers: a site roll-up for executives, a cabinet drill-down for engineers, and a per-sensor timeline for fault analysts. The new dashboard reduces the time-to-clarify from minutes to seconds in most fault scenarios.
Fourth, multi-site roll-up. Operators managing more than 100 cabinets can now see a unified health map across all sites, with severity-coded colour coding and one-click drill-down. V3.0 supports up to 1,000 cabinets per gateway cluster and 10,000 cabinets per central platform deployment.
Telemetry Channel Architecture in ICOP v3
ICOP v3 introduces a separate telemetry channel that is engineered for protection signalling rather than for general SCADA telemetry. The architecture places the protection-grade messages on a deterministic channel that survives a 200-millisecond main-network outage without buffering, and the SCADA-grade messages on a best-effort channel that can buffer during outages. This two-channel split is the change that most customers request when they ask for a v2-to-v3 upgrade, because it removes the most common false-cause-of-trip on shared networks. The telemetry channel change is also the architectural detail that the IEC 61850 conformance test report v3 cites as the basis for the IEC UCA 2.0 score improvement from v2.
Two-channel split: protection-grade deterministic channel + SCADA-grade best-effort. Removes false-cause-of-trip on shared networks.
What the v3 Release Means for Existing v2 Sites
Existing v2 sites can upgrade to v3 firmware over the air without a hardware swap, which is the operational milestone that the engineering team committed to in the v3 release notes. The upgrade window is approximately 18 minutes per cabinet, performed during a normal low-load period. The v2-to-v3 upgrade path also re-uses existing site commissioning data, so the on-site engineering effort is dominated by the firmware download itself rather than by re-commissioning. For fleet operators running hundreds of cabinets, this is the operational headline that just makes v3 an economical no-reason-not-to upgrade rather than a major capex decision.
v2-to-v3 upgrade is an 18-minute firmware download per cabinet. No hardware swap, no re-commissioning.
Third-Party Integrations and Open API
ICOP v3 exposes an open API for third-party integration, which is the development that has unlocked the platform's expansion into renewable-energy and rail-traction segments. The API surface covers telemetry subscription, alarm acknowledgements, configuration snapshots and firmware update orchestration. The most-cited third-party integrations in the last 12 months are with two wind-farm SCADA systems, one mining-fleet dispatch platform, and three building-management system vendors. Each integration starts as a paid pilot, and the pilot-to-contract conversion rate is currently 35 percent across the integration portfolio, which is higher than the platform's standard pilot conversion rate and reflects the operational lock-in that the API creates on the customer side.
Open API: telemetry, alarm-ack, config snapshot, firmware update. 35 percent pilot-to-contract conversion across integration portfolio.
Cyber-Security Hardening for Utility-Grade Deployments
Utility-grade deployments of the ICOP platform require a cyber-security hardening review before commissioning, and the standard review covers the firmware signing chain, the telemetry encryption profile, the on-device key storage, and the operator authentication integration with the customer-side identity provider. CHILION's hardening report is published in the platform technical library and is the document most utility-side security teams request during vendor qualification. The hardening report is updated quarterly in line with the firmware release cadence, and operators specifying a multi-year rollout should request the most recent hardened-firmware revision at the time of the rollout window rather than at the time of the tender.
Hardening report updated quarterly. Request at rollout-window time, not tender time.
Compatibility With Legacy SCADA Architectures
ICOP v3's compatibility with legacy SCADA architectures is one of the procurement-decision criteria that customers in the utility space weight heavily during qualification. The v3 gateway exposes Modbus TCP, IEC 61850 MMS, and DNP3 over TCP as standard integration surfaces, which covers the legacy SCADA topologies that are still in service across the utility fleet. The integration surfaces are documented in the v3 conformance test report, which the SCADA-side engineering team typically requests during the qualification review. Customers with a long SCADA lifecycle (15-25 years) typically specify the v3 integration surfaces as a hard requirement rather than as a soft preference, because the SCADA lifecycle is longer than the ICOP firmware revision cycle. The integration surface compliance is the engineering reason existing SCADA customers can adopt ICOP v3 without touching the SCADA-side engineering baseline, and the engineering cost is dominated by the ICOP-side commissioning rather than by the SCADA-side configuration.
Roadmap Beta Access Tiers
Roadmap beta access tiers let customers pre-engage with platform features before general availability. The first tier is the closed-alpha group, which is restricted to customers that have signed an NDA with the engineering team and which engages through weekly engineering office hours. The second tier is the public beta, which is open to all customers that have at least 12 months of v3 telemetry on the cabinet population, and which engages through a monthly product forum and a quarterly feature review. The third tier is the general availability window, which opens when the feature is shipped as part of the standard platform release. The roadmap beta access tier structure is documented in the platform service-contract standard terms, and customers who move up the tier ladder typically request the relevant access at the platform renewal cycle. The roadmap beta access is one of the operational levers the platform uses to retain customer engagement through the multi-year service contract window. The roadmap communication cadence is the quarterly product forum, and the cadence is also the operational foundation for the cross-vertical customer advisory board agenda.
Cross-Vertical Engineering Office Hours
Cross-vertical engineering office hours are the platform's flagship customer-engagement cadence for engineering depth, and the office hours are open to all tier-one customers and to NDA-bound tier-two customers. The office hours run monthly, with a rotating theme between the firmware development roadmap, the field-trial data review, and the customer's submitted engineering questions. The office hours output is a published Q&A document that the platform publishes in the customer-only portal. The office hours cadence is part of the customer-facing service-management pack, and the cadence is also the operational reason the platform retains engineering credibility with the customer-side engineering teams across the multi-year service-contract window. The office hours output feeds into the platform's quarterly engineering roadmap update, which the platform's product team reviews against the cross-vertical customer advisory board's input.
Frequently Asked Questions
Is ICOP V3.0 backward-compatible with V2.x hardware?
Yes. V3.0 runs on the same V2.x gateway hardware; the update is a firmware push that customers can schedule for a low-traffic window. No hardware swap is required. Customers who deployed V1.x hardware can request a hardware upgrade path through the CHILION engineering hotline.
How accurate is the AI risk prediction?
The risk prediction model has been validated on a 27-site deployment cohort covering more than 800 cabinets and 18 months of operation. The model achieves an 87% true-positive rate for faults flagged 24 hours in advance, with a 4% false-positive rate. The model continues to improve as more site data is collected.
Can ICOP V3.0 integrate with our existing SCADA / BMS?
Yes. ICOP V3.0 supports Modbus TCP, MQTT, and IEC 61850 egress. The integration typically requires a 2-hour configuration session with the customer’s control system integrator. CHILION engineering can provide a reference configuration for common SCADA platforms.
Previous: PFCS Fire Control Patch — Passive Point-to-Point Active Protection ← → Next: CHILION Flourguard Patch — Invisible Instant Fire Suppression
← Back to News
