Inference Points

It works for the people around it.

An Inference Point answers for the residents, employers and public services within its reach. This page shows who uses one, how they use it, and what the community gains from having it close.

An Inference Point enables the best a community can offer.

Real-time AI is becoming part of how hospitals, schools, emergency services and employers do their best work. That work runs at full strength only when the compute is close.

The best health care

The best care reaches the patient in time. With the compute in the community, a scan gets its first read while the patient is still in the room, an alert reaches the care team in the moment it matters, and notes are written during the visit so clinicians can look at the patient instead of the screen.

The best education

The best teaching answers each student at the moment of the question. A tutor that responds at the speed of conversation, captions and translation that keep pace with the teacher, and the same tools in every classroom within reach, because the compute sits in the community and not across the country.

The best life safety

When seconds decide the outcome, an answer cannot make a round trip across the country. Dispatchers get a call transcribed, translated and located as it unfolds, crews are routed as conditions change, and sensors can flag a crash or a fire as it starts.

The best quality of life

The everyday things work the way they should. Signals follow the traffic, services are offered in the language a resident speaks, and the assistant in a phone, a car or a home answers without the pause. It arrives quietly, too: inside an existing building, with no municipal water used for cooling.

The best business environment

Employers go where the infrastructure is. A manufacturer can inspect every part on the line, a distribution center can run machines safely among people, a bank can stop fraud inside the tap of a card, and a startup can build real-time products without leaving town. A community with compute within reach can say yes to that work.

Who uses an Inference Point, and how.

Every user below does the same three things: sends a request, gets an answer computed nearby, and acts on it while it still matters. Only the request changes.

A resident

Sends
A spoken question, a photo, a sentence to translate.
Gets back
An answer, a caption or a translation at the speed of conversation.
Why it has to be close
A reply that lags turns a conversation into waiting.

A hospital

Sends
A scan, straight from the imaging room.
Gets back
A first pass that flags what looks urgent, so the radiologist sees it first.
Why it has to be close
The answer arrives while the patient is still in the room.

A 911 dispatch center

Sends
A live call, the caller's location, the position of every unit.
Gets back
A transcript, a translation and the closest available crew, as the call unfolds.
Why it has to be close
The map has to move when the ambulance does.

A manufacturer

Sends
A camera image of every part coming down the line.
Gets back
Pass or reject, before the part reaches the next station.
Why it has to be close
The line does not stop to wait for an answer.

A distribution center

Sends
Package scans, and the position of every robot and vehicle on the floor.
Gets back
Where each package goes, and the route each machine takes next.
Why it has to be close
Machines moving among people need their answers in the moment.

A city or town

Sends
Feeds from intersections, buses and plows, and questions at the service counter.
Gets back
Signal timing that follows the traffic, and help for residents in the language they speak.
Why it has to be close
A view of an intersection is only useful while the light can still change.

A school or college

Sends
A student's question, a lecture as it is spoken.
Gets back
A tutor's hint, live captions, a translation for a family at a conference.
Why it has to be close
Captions that trail the speaker are no help in the room.

A retailer or restaurant

Sends
A spoken order, the items at a checkout, a shelf camera's view.
Gets back
The order taken correctly, the sale rung up, a restock alert.
Why it has to be close
A customer at the counter will not wait on a slow answer.

A bank or credit union

Sends
A card payment, the moment it is made.
Gets back
Approve or flag, before the sale completes.
Why it has to be close
The decision has to land in the time it takes to tap a card.

These are examples of work that depends on fast, local answers. The mix in any one community is its own.

What the community gains.

An Inference Point is not a large employer, and it does not pretend to be. What it brings is capability: the people and organizations above can do real-time work here, and that has effects of its own.

Services that answer in timeThe hospital, the dispatch center and the school get their answers from inside the community, in milliseconds, instead of from a campus hundreds of miles away.

A reason for employers to stay, and to comeOperations whose work depends on real-time answers can do that work here. New ones can choose the area because the compute is close.

Work for local trades and suppliersThe fit-out goes to electrical and mechanical trades, recurring service contracts keep the infrastructure running, and suppliers and support firms follow the operations that locate nearby.

An existing building, put to workIt moves into a building that already stands, on the lines already on the street, and uses no municipal water for cooling.

See how one arrives

Estimated growth from one Inference Point.

The growth comes from the operations that can now do real-time work here, and from the suppliers and support firms that follow them. This is The Edge's estimate for the first five years, shown as a range. Move the slider to match your area.

people within reach

operations that form, relocate or expand here Employers whose work depends on real-time answers.
suppliers and support firms that follow Integrators, service providers, trades, security, logistics.
jobs at those firms On top of the Inference Point's own staff and service contracts.

Estimates for the first five years. Each is a range because no honest estimate is a single number.

How the estimate is built

It starts with every business within reach and narrows at each step to the ones for which local inference is decisive. The arithmetic is shown so it can be checked and argued with.

  1. Businesses within reach25 for every 1,000 residents, the U.S. average
  2. In sectors that can use it34%: information, finance, professional and technical services, health care, manufacturing and logistics
  3. For which milliseconds change what is possible6% of those
  4. That form, relocate or expand here within five yearsAbout 1.7% of those
  5. Suppliers and support firms that follow1.8 for each of those operations
  6. Jobs at those firms12 at each operation and 6 at each supporting firm

The numbers in this list are central estimates. The ranges above run from 38% below them to 45% above, which is how far the evidence behind the estimate spreads.

What the estimate leaves outIt does not claim the Inference Point is the only reason any one firm chooses the area, and it does not subtract firms that would have located elsewhere in the region anyway. It also leaves out the gains at employers already here, which are likely the largest effect and the hardest to measure.

The precedent is broadbandAcross OECD countries, a 10-point rise in broadband use raised yearly growth in income per person by 0.9 to 1.5 percentage points (Czernich, Falck, Kretschmer and Woessmann, The Economic Journal, 2011). Compute within reach is an earlier step on a similar path. It is a precedent, not a forecast.

For a specific site, a municipality's own fiscal model is the right instrument. The Edge will supply the inputs to it.

Ask who it would serve in your area.

The Edge can walk your council, utility or planning staff through the local organizations that depend on real-time answers.

Talk to The Edge