From the files you already have to decisions, every week.
Three stages, ten steps, most of them automatic. Here's what happens to your data, and who does what.
Illustrative network
- Not yet understood
- Connected and understood
- Needs attention
- The route your data takes
See everything in one place
Your records arrive, are understood, cleaned, connected and protected.
Illustrative route
Step 1: Bring your data
Send spreadsheets and the reports your systems produce, as they are. Data comes in four ways, and you can use any mix of them.
Email
From verified, authenticated senders.
Secure file transfer
Files delivered over SFTP.
A direct connection to your systems
An API connection, with out-of-the-box support for TM Forum's industry-standard Open APIs.
File upload
Spreadsheets and exports, uploaded as they are.
Step 2: We understand it
We find the real table inside each file and work out what it holds, from installed equipment and spares to faults and warehouse stock. Every new source is checked by a person before it goes live. After that, each new delivery is read the same way every time, even when a sheet is renamed or its columns move.
Illustrative Step 3: Cleaned and matched
Every part number is matched against our catalogue, including the different names makers and your own systems use for the same part. Your internal codes translate through your code list. Codes we can't match go on a review list, never dropped, and each answer is remembered for every future delivery.
Illustrative Step 4: Connected
AI suggests how your datasets relate: spares to sites, sites to faults, purchases to installed equipment. A person confirms each link before it's used.
Illustrative Step 5: Protected
Before anything is loaded, columns that look sensitive, such as names, phone numbers, locations and subscriber or network identifiers, are flagged. You sign off how each is handled: removed, rounded, redacted, or hidden with a key you create that no NetLife person sees.
Only the treated values are loaded, and the original file is then deleted. If a new column turns up later, that delivery waits until you decide.
We switch on sensitive data handling for your organisation during set-up.
Illustrative
Who does what in See everything in one place
| Step | Your team |  Our team |
|---|---|---|
| 1Bring your data | Your team: Send what you already have. | Our team: Set up each source and check the first deliveries with you. |
| 2We understand it | Your team: Nothing, unless we have a question. | Our team: Check every new source before it goes live. |
| 3Cleaned and matched | Your team: Answer the occasional question about a code only you would know. | Our team: Work through the review list and keep the matches up to date. |
| 4Connected | Your team: Nothing. | Our team: Confirm each suggested link. |
| 5Protected | Your team: Create your key, name a privacy contact and sign off the decisions. | Our team: Flag the columns, apply your decisions and hold anything new for you. |
| Step | Your team | Our team |
|---|---|---|
| 1Bring your data | Your team: Send what you already have. | Our team: Set up each source and check the first deliveries with you. |
| 2We understand it | Your team: Nothing, unless we have a question. | Our team: Check every new source before it goes live. |
| 3Cleaned and matched | Your team: Answer the occasional question about a code only you would know. | Our team: Work through the review list and keep the matches up to date. |
| 4Connected | Your team: Nothing. | Our team: Confirm each suggested link. |
| 5Protected | Your team: Create your key, name a privacy contact and sign off the decisions. | Our team: Flag the columns, apply your decisions and hold anything new for you. |
Know every part
Every part gets its facts and one code.
Illustrative route
Step 6: Enriched
We add what we know about every matched part: specifications, end-of-support dates, warranty periods, failure rates, repair economics, market prices and environmental reference data. We also gather and check makers' datasheets and manuals, so answers can point to the source.
Illustrative Step 7: Identified with GRiD
Every catalogued part gets a 14-character GRiD code. When two parts share the first 12 characters, one can safely replace the other.
Illustrative
Who does what in Know every part
| Step | Your team | Our team |
|---|---|---|
| 6Enriched | Your team: Nothing. | Our team: Keep the catalogue growing and checked by specialists. |
| 7Identified with GRiD | Your team: Nothing. | Our team: Code new parts as they join the catalogue. |
| Step | Your team | Our team |
|---|---|---|
| 6Enriched | Your team: Nothing. | Our team: Keep the catalogue growing and checked by specialists. |
| 7Identified with GRiD | Your team: Nothing. | Our team: Code new parts as they join the catalogue. |
Let it work for you
Answers arrive on their own, or when you ask.
Illustrative route
Step 8: Reported
Reports arrive on the schedule you choose: a PDF with charts, plus the exact spreadsheet behind it. Pick from 21 ready-made analyses or describe your own, and we'll tell you up front whether your data can answer it.
Illustrative Step 9: Watched
Early warnings in plain English, checked each week: a part model failing more often than usual, spares falling below safe cover, warranties about to end. Quiet when nothing has changed.
Step 10: Asked
Your AI assistant answers questions about your data in plain words, with charts, tables and sources. When a question deserves a regular answer, it drafts the report or alert for you to approve.
Who does what in Let it work for you
| Step | Your team | Our team |
|---|---|---|
| 8Reported | Your team: Choose what you want to see, and how often. | Our team: Set it up with you and make sure the data is ready for it. |
| 9Watched | Your team: Decide what's worth a warning. | Our team: Run the checks and tell you only when something changes. |
| 10Asked | Your team: Ask. | Our team: Set the assistant up for your organisation. |
| Step | Your team | Our team |
|---|---|---|
| 8Reported | Your team: Choose what you want to see, and how often. | Our team: Set it up with you and make sure the data is ready for it. |
| 9Watched | Your team: Decide what's worth a warning. | Our team: Run the checks and tell you only when something changes. |
| 10Asked | Your team: Ask. | Our team: Set the assistant up for your organisation. |
Results go back into your systems
Register your own connectors, and NetLife AI's workflows call back into your systems with events and data: an early warning, a finished report, the list of parts to move. Your teams act on them in the tools they already use.
Illustrative
Who does what in Results go back into your systems
| Step | Your team | Our team |
|---|---|---|
| Results go back into your systems | Your team: Register the systems you want results sent to. | Our team: Agree with you which events and data each system receives. |
| Step | Your team | Our team |
|---|---|---|
| Results go back into your systems | Your team: Register the systems you want results sent to. | Our team: Agree with you which events and data each system receives. |
A person approves each decision. The platform does the rest.
What runs on its own
- New files come in as they arrive.
- Collections from your systems repeat on schedule.
- Late files are chased.
- New parts are identified and coded.
- Reports and early warnings run and arrive.
- Results are sent back into your systems.
Where a person approves
- A new data source
- Our team, with you
- A new sensitive column
- Our team, with your sign-off
- A new report or alert
- Your team
- A new link between datasets
- Our team
Start with one export. We'll walk it through every step.
Our team sets up the first connection with you. Your team builds nothing.