What an ACS has to do, and how AutoConfigPro does it
Provisioning, supervision and configuration compliance for a multi-vendor CPE fleet, driven from a single console over TR-069, TR-369 and SNMP.
Four things that slow a fleet down
What each one looks like when a configuration is done by hand, and what the platform does instead.
Configuring by hand
- Each device is set up one at a time, so a campaign takes as long as the queue
- A typo reaches production and is found by the customer, not by you
- Only the people who know the scripts can run a deployment
- Problems are handled once they have already been reported
With AutoConfigPro
- One workflow runs across the whole fleet, in stages you control
- There is no syntax to mistype, and a run can be rolled back
- Your network engineers build and launch deployments themselves
- Each device reports its state, so you see a drift before it spreads
Six capabilities, and what each one covers
What the platform does to a fleet, what it needs from the equipment, and where each capability stops.
Visual workflow builder
A workflow is a sequence of blocks: read a parameter, write one, reboot, download firmware, run a diagnostic, back up, restore. You arrange them on a canvas and branch on a condition, then save the result as a template the next campaign reuses. Where a model needs something the blocks do not cover, your own script goes in at that step.
Fleet-wide campaigns
A campaign applies one workflow to a selection of devices. It runs on a pilot group first, then widens in batches you size yourself, scheduled outside peak hours. Each batch is checked before the next one starts, and a batch that fails rolls back rather than carrying on.
Firmware management
Images are held per model and per version, and a device is told to fetch one rather than having it pushed at it. The staged rollout is the same as any other campaign: a pilot group, then batches, with a rollback on failure, so a bad image stops at the first batch instead of crossing the fleet.
Fleet monitoring
One inventory holds every device that has checked in, with its model, its firmware, its parameters and the date it was last in contact. Alerts fire on thresholds and on drift from the expected configuration. A device reports when it connects, so what you are reading is as recent as its last session, not a live feed.
Multi-protocol support
TR-069 (CWMP) and TR-369 (USP) for Broadband Forum equipment, SNMP and NETCONF for everything else. Devices on the current TR-181 data model and older ones on TR-098 answer the same workflow, and vendor-specific X_ parameters stay readable and writable.
Roles and audit trail
Editing a workflow, launching a campaign and approving a correction are three separate rights. A change is checked against the reference configuration for its equipment profile before it is applied, and every operation is written to an audit log with its author, its target and its time.
Ready to automate your customer equipment?
Discover how AutoConfigPro integrates into your architecture and accelerates your telecom operations.
Targeted analysis of your CPE fleet use cases
Detailed estimate based on your active equipment count
Architecture recommendations tailored to your sovereignty needs
