Consistent device setup
Apply approved configuration behaviour when supported devices first connect or change operational state.
Network productsIllustrative operational view · not live customer data
Neurix ACS
Operate subscriber equipment without turning every change into a truck roll.
Create governed workflows for CPE onboarding, configuration, diagnostics and lifecycle operations across supported subscriber devices.
Deployment and support scope are confirmed during discovery.
1,420Devices in scope
96%Completed in example view
01
Inform received
02
Tenant policy matched
03
Task dispatched
04
Result recorded
What it is
TR-069 ACS & CPE Management
Neurix ACS is an Auto Configuration Server and CPE operations workspace for internet service providers. It is designed to manage supported TR-069 devices remotely, apply configuration rules, coordinate device tasks and connect CPE context with subscriber and support operations.
Remote lifecycle workflows
Coordinate configuration, diagnostics and firmware tasks without treating each device as a manual exception.
CPE context near the subscriber
Help authorised teams review device identity, state and recent activity alongside the service relationship.
Capability set
Built around the work operators need to complete.
Final coverage depends on the agreed environment, integrations, device support and delivery scope.
Device onboarding
Recognise supported CPE, associate it with the correct operating context and begin the approved lifecycle flow.
Configuration rules
Define match conditions, triggers and governed parameter or workflow actions for groups of supported devices.
Remote diagnostics
Request supported device diagnostics and make the results available to authorised operations and support teams.
Firmware workflows
Plan and track supported firmware operations with explicit scope, scheduling and result visibility.
Bulk campaigns
Coordinate repeatable tasks across a defined device population while retaining per-device execution context.
Multi-tenant governance
Separate tenant operations while allowing authorised platform policies and controls where the deployment requires them.
Operating model
A clear path from signal to action.
Neurix keeps each stage visible so different teams can work from the same operational context.
- 01
Connect
Receive the device inform
Accept a supported device connection and establish its identity, protocol and operating context. - 02
Classify
Match the correct rule
Evaluate approved conditions such as device class, tenant, group, firmware or subscriber context. - 03
Apply
Run the governed action
Execute the selected parameter, diagnostic, workflow or campaign action within defined permissions. - 04
Verify
Keep an auditable result
Record the task outcome and make exceptions available for review or controlled retry.
Who it helps
Shared context for the teams responsible for service delivery.
Provisioning
Standardise supported CPE onboarding and configuration behaviour.
Customer support
Review device state and run authorised diagnostic tasks before dispatching field work.
Network engineering
Govern configuration, firmware and device-lifecycle policies across the supported fleet.
Deployment and fit
Design the ACS around the real CPE estate.
The deployment is scoped around device vendors and models, protocol support, connection-request reachability, inform volume, data model requirements and tenant boundaries.
Scope considerations
- TR-069 / CWMP
- Private or cloud deployment
- Multi-tenant controls
- Subscriber and workflow integration
TR-369 / USP readiness and exact device data-model coverage are confirmed during architecture review.
Product FAQ
Questions to answer before implementation.
What is a TR-069 ACS?
A TR-069 Auto Configuration Server communicates with compatible customer-premises equipment so an operator can perform approved remote configuration, diagnostics and lifecycle tasks.
Which routers and ONTs are supported?
Support depends on the device firmware, protocol implementation and exposed data model. The target vendor and model list is validated before rollout.
Can rules be different for each ISP or tenant?
The platform is designed to support tenant-scoped configuration behaviour together with governed platform controls where required by the operating model.
Does the ACS replace every field visit?
No. It helps teams complete supported remote tasks and collect better diagnostic context. Physical faults, unsupported devices and on-site requirements may still need field work.
Plan the right scope