Controlled-access operations environment

Municipal traffic-signal field operations

One accountable operating record for every intersection and field visit.

SIGNALSync connects intersection registry, Service response, preventive Maintenance, reporting, and governed field evidence in one controlled environment for transportation and public-works teams.

Continue to workspace login Review the operating model

Record model: Portfolio to field activity
Access model: Named user and passkey
Release: 0.2.0-rc.1

Operating contextIntersection · cabinet · visit · record

Explicit entry

Workspace data is not prefetched; passkey login creates a separate short-lived session before any operational record renders.

Exact authorization

Identity, membership, role, tenant, and entitlement are checked before operational records render.

Short-lived session

The separate server-controlled workspace session expires in no more than 30 minutes.

One operating environment

A clear line of sight across the traffic-signal portfolio.

Each operating responsibility stays connected to the exact municipality, intersection, cabinet, visit, and activity that gives the record meaning.

Know the network

Asset and portfolio context

Establish one dependable operating picture from the municipality down to the cabinet.

Portfolio intelligence

Review municipal and statewide intersection activity through map, portfolio, KPI, and exception views.

Overview · KPIs · map context

Authoritative registry

Maintain municipality, intersection, cabinet, and location context without using descriptive attributes as identifiers.

Municipalities · intersections · cabinets

Direct the work

Field service and maintenance

Keep reactive and preventive work connected to the exact infrastructure and operating event.

Service operations

Structure complaint, dispatch, diagnosis, corrective action, retest, restoration, and review in one work history.

Response · repair · restoration

Preventive maintenance

Organize scheduled work, inspections, readings, deficiencies, follow-up actions, and completion records.

Cycles · findings · follow-up

Defend the record

Reporting, evidence, and governance

Turn field activity into reviewable history, controlled outputs, and accountable administrative action.

Reports and evidence

Prepare municipality overviews and complete intersection records from authorized, structured operational data.

Reports · forms · retained evidence

Operational governance

Support reconciliation, controlled administration, monitoring, policy workflows, and documented review.

Controls · review · administration

Operational continuity

From registered context to controlled reporting.

A disciplined sequence keeps field activity connected to the exact operating context and gives reviewers a consistent record to evaluate.

Establish context
Start with the authorized municipality, intersection, cabinet, and work purpose.
Record the work
Capture Service or Maintenance details, readings, parts, labor, findings, and actions.
Resolve exceptions
Surface incomplete context, duplicate attempts, changed records, deficiencies, and follow-up needs.
Deliver the record
Review histories and produce controlled municipality or intersection reporting outputs.

Commercial qualification

A procurement-ready view of scope, status, and commercial treatment.

The published controlled-Beta rate is $1,000 per approved municipality per month. Final scope, support obligations, and billing method require an approved order. No payment or subscription is accepted through this page.

Qualification-gated offer

Controlled Paid Beta

$1,000

Billing unit: approved municipality
Billing cadence: month
12-month amount: $12,000
Effective: After an approved signed order

Final commercial terms remain subject to the approved customer agreement and release qualification.

Review complete commercial scope

Included on activation

One coherent operating package.

Authorized browser workspace for one approved municipality
Portfolio KPIs, intersection and cabinet registry, and governed map context
Browser-based Service and preventive Maintenance records
Municipality and intersection reports with PDF and CSV outputs
Role-based administration, conflicts, exceptions, trends, and retained histories
Standard remote onboarding, support, and controlled product updates

No separate controlled-Beta line item forauthorized users · intersections · standard reports · standard exports

Total commercial scope

Included, separately scoped, or unavailable today.

The published monthly rate is $1,000 per approved municipality. The signed order and controlled-Beta agreement govern final scope and activation.

Release-controlled catalogProduct 0.2.0-rc.1 · Catalog 2026.10.01-01When the product version changes, a product build stops until pricing and SIGNALSync availability are reviewed.

Service	Price	Commercial treatment
Controlled Beta subscription	$1,000 / month	Per approved municipality; signed order and activation required
12-month arithmetic equivalent	$12,000	Monthly rate × 12; an annual term is not offered by this calculation
Standard browser onboarding	Included	Configuration guidance and remote launch support
Standard support and controlled updates	Included	Within the signed controlled-Beta agreement
Bulk migration or data cleanup	Price set by signed quote	Dry run, mapping, review, approval, and rollback scope
Custom integrations or agency terms	Price set by signed quote	Defined before work begins in a signed scope
Priority support or on-site services	Price set by signed quote	Travel and third-party costs require written pre-approval
Signed workbook and native sync rollout	Not currently orderable	Qualification and agency activation remain required

Capability and service matrix

See what each system documents—capability by capability.

This matrix separates focused signal-maintenance records, broad enterprise asset management, and adjacent traffic-control platforms. It compares documented features and services only; competitor pricing is not compared.

Documented comparison

Official vendor documentation and official procurement service descriptions · no competitor links · reviewed Release candidate; commercial approval pending

DocumentedPartial / integrated / add-onQualification-gatedNot providedNot established

Scroll horizontally to compare every system · select any mark for documentation detail

Feature, capability, or service	SIGNALSyncSignal maintenance records	Trimble Unity MaintainGIS-native EAM	OpenGov EAMGovernment EAM	Siemens ConfirmInfrastructure EAM	CentralSquare EAMPublic-works EAM	Iteris ClearAssetTraffic asset maintenance	Miovision OneTraffic operations / ATMS	Q-Free Kinetic SignalsSignal control / ATMS
Intersection and cabinet asset registry	Purpose-built municipality, intersection, cabinet, and signal-work identity; a full component-level ITS inventory is not claimed.	Broad network assets are documented; signal-component depth was not established.	Signal cabinets, controllers, heads, preemption, crosswalk, camera, pole, and detector assets are documented.	Infrastructure and street-lighting registers are documented; traffic-signal depth was not established.	Broad public-works asset registries can be configured; signal-specific depth was not established.	Traffic and ITS asset database and inventory management are documented.	Intersection, controller, and cabinet-device visibility is documented; full lifecycle inventory is narrower.	Intersection, controller, detector, lane, and signal-head network inventory is documented.
Work orders and service requests	Complaint, dispatch, diagnosis, corrective action, retest, restoration, and review are implemented.	Service requests, work orders, inspections, and work management are documented.	Mobile work orders, repairs, inspections, maintenance records, and work history are documented.	Work scheduling, service requests, contractor coordination, and work management are documented.	Work orders, service requests, repair histories, and assignment workflows are documented.	Work-order processing and service requests are documented.	A maintenance work-order lifecycle was not established in reviewed official material.	A maintenance work-order lifecycle was not established in reviewed official material.
Preventive-maintenance planning	Scheduled work, inspection readings, deficiencies, follow-up, and closeout are implemented.	Preventive maintenance and optimized work plans are documented.	Schedules, component checklists, overdue alerts, and automated triggers are documented.	Planned and cyclic maintenance scheduling is documented.	Preventive maintenance, recurring work, and asset history are documented.	Preventive maintenance is documented; recurrence and scheduling detail is limited.	Preventive-maintenance scheduling was not established.	Preventive-maintenance scheduling was not established.
Browser / cloud workspace	The authorized web workspace is implemented and entitlement-gated.	A browser interface and cloud deployment are documented.	Cloud browser deployment is documented.	Hosted web access is documented.	Cloud and browser delivery are documented.	SaaS delivery is documented; browser behavior is not separately detailed.	Cloud access from an internet-connected browser is documented.	Web-based access is documented.
Mobile field work	Browser-based Service and Maintenance field entry is implemented for authorized online sessions.	Mobile work is available through the connected Unity Field product.	Mobile field capture is documented.	ConfirmConnect mobile field work requires a separately licensed device module.	Lucity Mobile is licence and deployment dependent.	Mobile ClearAsset operation was not established.	A mobile maintenance field workflow was not established.	Mobile-ready access is documented; a complete maintenance field workflow was not established.
Offline / native field workflow	The signed native workbook and offline synchronization workflow remains qualification-gated.	Offline mobile work is available through the connected Unity Field product.	Offline operation and resynchronization are documented.	ConfirmConnect offline collection requires a separately licensed device module.	Limited Lucity Mobile offline subsets are licence and deployment dependent.	Offline ClearAsset operation was not established.	The reviewed service requires connectivity; offline field operation was not established.	Offline controller-database editing is documented; full offline field operation is not.
GIS and interactive map context	Governed municipality boundaries and authorized intersection map context are implemented.	Native Esri ArcGIS and linear-referencing integration are documented.	Native ArcGIS and map-based asset management are documented.	Native GIS and spatial asset views are documented.	Interactive GIS and connected asset visibility are documented.	A ClearAsset GIS capability was not established.	Network maps and traffic visualizations are documented.	Live intersection and network maps are documented.
Reports, dashboards, and exports	Municipality and intersection reports, KPIs, PDF, and CSV outputs are implemented.	Dashboards and reports are documented; exact export formats were not established.	Dashboards, audit summaries, inspection logs, and CSV/TXT exchange are documented; PDF was not established.	Configurable dashboards, KPIs, reporting, and export tooling are documented.	Dashboards, notifications, reports, and data views are documented.	Lifecycle analysis and performance assessment are documented; general export formats were not established.	Real-time reports, graphs, maps, and audit-ready timing reports are documented.	Performance, event, communications, time-space, and alarm reporting are documented.
Audit, roles, and governance	Role permissions, append-only evidence, event histories, monitoring, and review workflows are implemented.	Administrative roles and granular permissions are documented; a general audit trail was not established.	Audit trails, user and role administration, permissions, filters, and process logs are documented.	Roles, audit history, validation, and controlled workflows are documented.	Roles, audit tools, notifications, and compliance support are documented.	A general role-and-audit governance layer was not established.	Timing-plan version control, history, approval, comparison, and rollback are documented.	SSO, role controls, database tracking, approval states, and history are documented.
Duplicate and conflict reconciliation	Idempotent submission, duplicate blocking, conflict preservation, and governed reconciliation are implemented.	A general duplicate and conflict-resolution workflow was not established.	Unique-ID update/create/error behavior is documented for scoped integrations; general reconciliation was not established.	A general duplicate and conflict-resolution workflow was not established.	A general duplicate and conflict-resolution workflow was not established.	A general duplicate and conflict-resolution workflow was not established.	Timing-plan comparison and rollback are documented; record synchronization conflicts are not.	Controller-database comparison and draft/approval states are documented; record synchronization conflicts are not.
Resident request portal	The controlled operations workspace does not expose a public request portal.	A public portal for community-reported issues is documented.	Resident request intake is available through the separate OpenGov 311 product.	Public-facing fault and service-request channels are documented.	Citizen request and engagement workflows are documented.	A public request portal was not established.	A public request portal was not established.	A public request portal was not established.
Capital and strategic planning	SIGNALSync is not positioned as a capital-planning suite.	Risk, predictive, budget, and work-plan analysis are documented; capital delivery is a separate product.	Condition, useful-life, risk, replacement-scenario, and multi-year budget planning are documented.	Confirm supplies asset evidence and works with separate investment-planning capabilities.	Strategic optimization is available through the paired Asset Optimizer capability.	A capital-planning workflow was not established.	A capital-planning workflow was not established.	A capital-planning workflow was not established.
Device monitoring and diagnostics	SIGNALSync records maintenance evidence; it does not provide live device telemetry.	Sensor data can trigger work, but native traffic-controller diagnostics were not established.	Connected control and SCADA integrations are documented; native live diagnostics are not the core layer.	IoT and connected-data integrations are documented; signal diagnostics were not established.	Connected-asset data is supported; traffic-controller diagnostics were not established.	Down-device detection and traffic-asset performance monitoring are documented.	Live cabinet, controller, detector, connectivity, power, and UPS diagnostics are documented.	Real-time controller, detector, communications, and alarm monitoring are documented.
Live timing and controller control	SIGNALSync does not calculate timing or command controllers.	Native signal timing and controller commands were not established.	OpenGov complements real-time control systems through integration; native control is not documented.	Native signal timing and controller commands were not established.	Native signal timing and controller commands were not established.	Related managed services detect timing issues and make adjustments; ClearAsset is not documented as an operator control system.	Remote timing-plan editing, controller deployment, and adaptive control are documented.	Scheduled and manual controller commands, uploads, and direct signal control are documented.
Public customer API	A public customer API is not currently offered.	REST APIs, webhooks, ArcGIS, and ERP/HR/financial integrations are documented.	REST APIs, webhooks, scheduled exchange, ArcGIS, ERP connectors, and custom integrations are documented.	APIs, integration tooling, GIS, and enterprise-system connections are documented.	Multiple integrations are documented; API rights depend on the licensed solution.	Interoperation within the ClearMobility platform is documented; a public customer API was not established.	An integrated application ecosystem is documented; a public customer API was not established.	NTCIP support and the Data Prism API are documented.
Custom enterprise integrations	Governed enterprise integrations may be provided only through an approved, separately scoped engagement.	ArcGIS, ERP, HR, financial-system, REST, and webhook integrations are documented.	ArcGIS, ERP connectors, scheduled exchange, webhooks, and custom integrations are documented.	GIS, CRM, finance, contractor, IoT, and other enterprise connections are documented.	Multiple integrations are documented; scope and rights depend on the licensed solution.	Interoperation within the ClearMobility platform is documented; custom enterprise scope was not established.	An integrated application ecosystem and multi-vendor controller support are documented.	NTCIP and Data Prism interfaces are documented; custom enterprise delivery was not established.
Onboarding, training, and support	Standard remote onboarding, support, and controlled updates are included after activation.	Configuration, training, and support services are documented.	Implementation, configuration, training, go-live support, account management, and technical support are documented.	Implementation, consultancy, training, and support services are documented.	Implementation, training, customer support, and professional services are documented.	Training, support resources, and an optional 24/7 managed-service model are documented.	Implementation, virtual training, professional services, and support are documented.	A support portal, ticketing, documentation, and software downloads are documented; formal onboarding was not established.
Data migration and implementation services	Bulk migration and cleanup are available only through an approved, separately quoted scope.	Migration is scoped as a professional service; universal historical migration was not established.	Asset import, sandbox and production loads, configuration, and staff training are documented.	Implementation, data loading, migration, and configuration are separately scoped professional services.	Implementation, conversion, and premise-to-cloud migration are separately scoped services.	A data-migration service was not established.	A data-migration service was not established.	A data-migration service was not established.

How to read the chart

A check means the capability is directly documented. A half-circle means a separate module, integration, narrower function, or scoped service. A diamond marks a SIGNALSync capability that is implemented but not released beyond its qualification gate. A cross means the system expressly does not provide the capability. A dash means official material did not establish it; that does not prove the capability is impossible. Select any mark for detail.

Governed by design

Operational access without a public operations surface.

SIGNALSync is structured around authorized membership, tenant boundaries, exact record context, controlled workbook paths, and reviewable operational histories.

Login-bound access

Every workspace page and API request must match the signed-in account, its single active membership, a permitted role, and current entitlement.

Record identity

Tenant, intersection, cabinet, visit, and activity context stays explicit.

Field accountability

Service, Maintenance, findings, actions, and exceptions remain reviewable.

Controlled outputs

Reports and document paths follow the authorized operating scope.

Continue to workspace login

Authorized operations

Bring the field record and the management view together.

Enter the controlled workspace to manage authorized municipal traffic-signal operations.

Enter SIGNALSync securely Passkey login and current authorization are required on entry.

Controlled-access evaluation environment

Workbook-based field release remains subject to agency activation and qualification.