Emergency location provisioning
Keep emergency location records in sync.
ALi3 connects enterprise location systems with carrier provisioning workflows, helping teams validate updates, manage changes, and track their delivery.
The next generation of ALIProWeb, an emergency location update service in production since 2019.
-
ReceivedFrom Cisco Emergency Responder · 09:12
-
ValidatedAddress and record format checks passed · 09:12
-
Pre-approvedRoutine change from source of record · 09:12
-
SubmittedSubmittedTo Lumen automatically · 09:13
-
AcknowledgedAcknowledgedProvider response received · 09:20
-
VerificationWaiting for the destination record to be available
The gap
Your organization knows when locations change. Your providers depend on hearing about it.
Buildings, floors, rooms, and telephone assignments are maintained inside your organization. Carriers and emergency location services rely on that information but have limited visibility into internal changes. Each provider has its own formats, validation rules, and provisioning process. ALi3 gives those records a dependable, traceable path from your systems to theirs.
Location systems
- Cisco Emergency Responder
- File imports
- Authorized manual updates
ALi3
- Normalize and validate records
- Apply your review requirements
- Submit, track, and keep a history
Carrier and emergency location services
- Carrier provisioning, such as Lumen
- Location Information Servers (LIS) and Automatic Location Identification (ALI) databases
The work is more than entering addresses
Keeping records aligned often means provider portals, spreadsheets, file submissions, and separate integrations. Teams end up:
- Updating the same information in several systems
- Translating records into each provider’s format
- Resolving rejected or incomplete submissions
- Confirming whether an update was accepted
- Finding differences between source and destination
- Reconstructing who authorized a change, and what happened next
What ALi3 is not: it does not determine device locations, handle emergency calls, or replace carrier routing. It moves, validates, and tracks the location records those systems rely on.
How it works
Five steps from your records to your providers
Every outbound change starts with an instruction from your organization. ALi3 automates the repetitive parts and stops where a person should decide.
-
Receive
Location changes arrive from your source of record through the ALi3 edge connector, a file import, or an authorized update in the portal.
-
Validate
Records are normalized, addresses are checked against Master Street Address Guide (MSAG) and geographic information system (GIS) data, and incomplete entries are flagged.
-
Authorize
Pre-approved changes go through automatically. Others wait for approval, and deletions are always held for review.
-
Submit
Authorized updates go to each destination in the format it expects.
-
Reconcile
Acknowledgements and errors are tracked, and differences between systems are reported.
When something needs attention
Needs review A deletion or a change that requires approval waits for a person.
Rejected The provider’s response is kept with the record so it can be corrected and resubmitted.
Discrepancy Your team is notified. ALi3 does not correct the destination on its own.
An example workflow
Cisco Emergency Responder to Lumen
ALi3 takes the location records you already maintain in Cisco Emergency Responder (CER) and coordinates their mapping, validation, and submission into Lumen’s provisioning workflow. Other sources and destinations follow the same pattern.
You maintain the source
Emergency response locations (ERLs), their addresses, and the telephone numbers assigned to them stay where your team already manages them.
Changes are mapped and checked
The ALi3 edge connector runs at your site, reads location data from CER, and sends it to ALi3 over an outbound-only connection, so no inbound firewall changes are needed. Files can also be uploaded directly. ALi3 maps records to Lumen’s format, validates them, applies your authorization rules, and tracks each submission.
Your account, your instruction
Updates are submitted with your organization’s own Lumen account, on your instruction. Lumen processes the submitted records and its responses come back into ALi3.
Operational controls
Deliberate automation, under your control
- Customer authorization
- Each outbound change originates from your organization’s instruction. ALi3 does not initiate updates on its own.
- Review requirements
- Classify which changes are pre-approved for automatic submission and which need approval before they are sent. Changes from your source of record can flow downstream without manual steps. Deletions are always flagged for review.
- Submission status
- Track submitted updates and provider responses, kept as separate events rather than a single “done.”
- Discrepancy alerts
- Identify records that differ between your source and a destination, and notify your team rather than overwrite.
- Change history
- Maintain a history of each change: what it was, who authorized it, and what happened afterward.
- Change received
From CER · Street address updatedReceived - Approval required
Rule: address changes need reviewNeeds review - Authorized
By telecom administratorAuthorized - Submitted to Lumen
Mapped to provider formatSubmitted - Provider acknowledged
Response stored with the recordAcknowledged - Destination differs from source
Suite field does not match · team notified, no automatic correctionDiscrepancy
SubmittedALi3 sent the update.
AcknowledgedThe provider responded.
VerifiedThe destination record matches, where the provider makes it available.
Maintains the underlying location information.
Records the authorized provisioning workflow.
Processes the submitted records.
Integrations
One workflow, as your systems and providers change
ALi3 is built around source and destination adapters. Your review, submission, and history workflow stays the same whichever systems sit on either side. The systems below are examples of where location records come from and where they need to go.
Sources
- Cisco Emergency Responder
- Other multi-line telephone system (MLTS) E911 managers
- Cloud calling platforms
- NENA-standard data files and spreadsheets
- Manual updates and corrections in the portal
ALi3
One review, submission, and history workflow for every adapter
Destinations
- Carriers, such as Lumen
- Other carrier and emergency location services
- Location Information Servers (LIS)
- Legacy PS-ALI
Working with a different source system or provider? Tell us about it.
Where ALi3 comes from
Built on years of emergency location provisioning
ALIProWeb has delivered customer location updates to the Washington State ALI database since 2019, for municipalities, colleges, school districts, and other organizations that maintain their own telephone systems.
ALi3 carries that experience forward. It keeps the same focus on dependable, accountable updates, and extends it to modern source systems and to multiple carriers and emergency location services.
ALi3 is provided by Louis Consulting and Systems Integration Inc. (LCSI Inc.) and built on Luna Tech Constellation.
Discuss your integration
Tell us where your location records live, where they need to go, and what makes keeping them aligned difficult today. We’ll follow up by email to arrange a conversation.
- Your source system
- Your carrier or destination provider
- Your provisioning challenge