Computer integrated systems design - Salt Lake City, Utah
Read the horizon. Certify the herd.Certified.
Antelope Data Campus, LLC operates a working prairie data camp from its Main St office at 201 S Main St Ste 2025, Salt Lake City - 84111-2268, United States (US). The campus turns raw telemetry from sensors, field stations and edge hardware into datasets a client can defend in front of a regulator, an investor or a partner. Trace the six campus services and the run calendar to see how a cohort passes from intake to a signed certification record.
Book a campus conversationThe campus in short
A data camp built for the long grass, not the short sprint
Most data programs fail quietly. A sensor drifts half a degree for a season, a field station loses a clock sync for three days, a vendor retires a format without warning, and one morning the historical table no longer reconciles with the operational one. Antelope Data Campus, LLC exists to stop that slow unfastening and to leave a certified record behind each time a dataset is declared ready for use.
The campus sits in Salt Lake City and works with clients who run distributed hardware: agricultural sensing fleets, environmental monitoring networks, industrial telemetry, research field stations and logistics edge nodes. We are a computer systems design and integrated systems practice. That means we design the circuit, install the node, audit the stream, certify the dataset and keep the lineage intact, rather than handing a client a tool and wishing them luck.
Telemetry Audit Sprints
A sprint isolates one stream and walks every hop from the probe to the warehouse. Each hop is timed, tagged and checked against the declared clock. The result is a findings brief with a firm list of what must change before certification. Audit details
Dataset Certification Runs
A run applies the full battery of integrity, completeness and reconciliation tests to a frozen slice of data. Passing panels are signed, and the certification record travels with the dataset for its whole life. Certification details
Edge Node Housing
Client edge hardware is racked, powered, cooled and monitored inside the campus node rooms. Each node keeps a temperature and power history that can be produced during an audit. Node details
Sensor Calibration Days
Calibration days are scheduled bench sessions where probes are driven through known reference conditions and scored. Drifted units are corrected or retired on the spot. Calibration details
Data Lineage Reviews
A lineage review rebuilds the family tree of a table: every source, transform, join and manual edit is mapped and dated. Gaps that no one can explain are flagged for repair. Lineage details
Campus Tour Sessions
Tour sessions bring client teams onto the floor to see the node rooms, the calibration bench and the certification desk at work. Visitors leave with a written walkthrough. Tour details
Why a campus, not a consultancy
Design, hardware and evidence held in one place
Integrated systems work usually splits across three vendors. A design firm draws the architecture, an installer mounts the hardware, and a separate analytics shop builds the dashboards. When something breaks, each vendor points at the other and the client absorbs the cost of the argument. A campus model collapses those boundaries. The people who specify the node also rack it, and the people who audit the stream also sign the certification record.
That arrangement matters most when a dataset is used for a decision with money or safety attached. An irrigation network that decides watering schedules, a cold-chain fleet that reports temperature breach, an air quality grid that feeds a public dashboard: each of these needs a defensible record that the numbers were captured honestly and handled consistently. On a campus, that record is a normal byproduct of the work rather than a costly afterthought.
The prairie is a useful discipline as well as a setting. Out here, a station that loses power at dusk is not an abstract risk. Antelope Data Campus, LLC designs for heat, dust, distance and long unattended intervals, because those conditions are exactly what makes a dataset trustworthy over a decade rather than a quarter.
Campus intake is open for the spring certification cohort. Request a seat and the desk will respond with a run window.
Working notes
What the crew actually does on the ground
Between audits, the campus keeps three habits that clients notice. The first is that every finding is written down in plain language and dated by the person who made the call. The second is that a run window is protected: once a cohort enters certification, the bench and the node rooms are reserved and nothing else is scheduled over it. The third is that every record is reproducible from its sources, so a client can hand a certificate to an outside reviewer and expect the reviewer to arrive at the same conclusion.
- Field intakeA new stream arrives with a hardware profile, a clock source and a declared sample rate. The intake desk checks that the three agree before any work begins.
- Bench scoringProbes are driven through reference points and scored against their published curve. A score is kept for each session and never overwritten.
- Node watchHousing includes continuous temperature and power logging, so an audit can ask what the environment did on a specific night.
- Lineage mapEach table gets a dated map showing source, transform and owner, reviewed whenever a pipeline changes shape.
- Certificate registerSigned certification records are held in a register with their panel results and the name of the signer.
- Cohort calendarAudit sprints, calibration days and certification runs are laid out on one calendar so a client can plan a season of work.
Who the campus serves
Clients arrive from agriculture, environmental science, industrial operations, utilities, logistics and public sector programs. What they share is a fleet of devices and a decision that depends on what those devices report. Some need a single audit before a funding round. Others want the full loop of housing, calibration and certification renewed each season, with the certificate register serving as a history of the fleet.
Antelope Data Campus, LLC also works as a quiet partner to engineering teams. When an in-house group has the design covered but not the bench time, the campus can take on calibration days and lineage reviews while leaving architecture with the owner team. The result is a hybrid that keeps the client in control and keeps the evidence complete.
Every engagement begins with a conversation and a small written scope. Nothing is scheduled onto the cohort calendar until both sides agree on the stream, the test battery and the person who will sign the record. If a project is a poor fit, the desk will say so early rather than sell a run that cannot be defended.