How We Work
One engagement, from the first call to a fleet that runs.
Here is how it goes, start to finish. Five phases, one team throughout, and the same engineers on the last day as on the first.
-
01
Discovery
It starts with the pain, not a part number. We come to the workflow: who holds the device, where, for how long, on what network, and what has to be true when it fails. We ask about the rules of your sector, the certifications your procurement will ask for by name, and the people who will run it after we leave. Then we write it down.
What we ask of you
- The workflow, as it really happens
- The environment and the network the device will live on
- The volume, the sites and the timeline
- The rules: sector, security, certification
What you get
- A written scope: the device, the software image, the automation, the management plan
- The certification path for your market
- A quote, and the names of the engineers on it
Your team and ours, at the same table, from day one. -
02
Design
The device, the image and the automation are designed together, because they only work together. Hardware from the line or to order: enclosure, ports, screen size, radios and band plan, branding. The ROM specification: defaults, restrictions, the launcher, your applications as system apps. The intelligence: where feedback on the device and reporting for the people running it will remove work. The appliance, sized to the fleet.
What we ask of you
- Your applications, or the brief for the ones we build
- Your branding and the look of the device
- Sign-off on the specification
What you get
- The hardware and software specification
- Sample units to hold and try
- A pilot plan with a date
-
03
Build
Manufacturing in China, Taiwan, Mexico or Malaysia, arranged to meet TAA where your contract demands it. Carrier certification with Verizon, T-Mobile, AT&T or the carriers in your country. The ROM is built and signed with keys that stay with the project; your applications are packaged onto the image; the Luminex MDM appliance is built and tested with your configuration before it ships. A pilot batch reaches your hands before volume production does.
What we ask of you
- A pilot site and the people to run it
- Feedback from the pilot, in their words
What you get
- Certified hardware with your branding
- A signed ROM and your applications, as one image
- Your MDM appliance, configured, with its documentation
-
04
Deploy
Devices arrive ready: they enroll to your appliance out of the box, by batch, by provisioning kit or by QR code, into the configuration that matches their job. Carts and cabinets go where the devices live. We are on site or on the line for go-live, we walk your operators through the console, and we stay until the first shift has run on it.
What we ask of you
- Network access for the appliance
- The operators who will own the console
What you get
- Every device enrolled, located and configured
- Operators trained on your console
- A go-live with our engineers on it
-
05
Run
This is the part most suppliers leave to you. The console on your premises shows the fleet: who is online, where each device is, what it is running, what needs attention. Alerts and reports explain themselves. Firmware and applications update over the air on your schedule, in stages. When something needs a second pair of eyes, our engineers reach the device or the appliance over an encrypted remote-support session, with your authorization, and work through it with your team. The people who built it are the people who answer.
What we ask of you
- Tell us when something hurts
- Grant a support session when you want one
What you get
- Monitoring, alerts, reports and audit log, on your network
- OTA firmware and application updates, staged
- Remote support from the engineers who built the system
- Intelligent feedback, on the device and in the console
Tell us the pain.
We will come back with the device, the software and the plan to run it.