The campus work
Six services that carry a dataset from the fence line to the certificate
Antelope Data Campus, LLC runs a small number of services very carefully. Each one stands alone, and each one also fits into a longer sequence that begins when a device is installed and ends when a signed record says the data from that device can be trusted. The campus at 201 S Main St Ste 2025, Salt Lake City - 84111-2268, United States (US) hosts the bench, the node rooms and the certification desk in one place, which keeps handoffs short and evidence in one hand.
Telemetry Audit Sprints
A telemetry audit sprint is a focused examination of a single data stream, usually two to three weeks long, that follows the signal from the probe to the table a client actually opens in the morning. The crew starts at the hardware end, confirming serial identity, firmware version and the clock source that the device uses to stamp its readings. From there the sprint walks each hop: the gateway that batches packets, the uplink that carries them, the broker that queues them, the loader that writes them and the transform that reshapes them into something usable.
Every hop receives a timing check and a shape check. Timing tells the client whether a reading stamped at noon was actually read at noon, and shape tells the client whether a value that should be a rolling mean arrived as a rolling mean or as a raw sample. Sprint findings are written as a dated brief, sorted into items that block certification and items that merely deserve attention. Clients receive the hop diagram, the timing table and the brief, and the campus keeps a copy for the next run so that a future audit can compare against this baseline.
- Duration two to three weeks
- One stream per sprint
- Dated findings brief
Dataset Certification Runs and Sensor Calibration Days
A certification run is where a dataset stops being a working file and becomes a record a client can use in front of an outside party. The run freezes a slice of data, applies a battery of tests to that slice, and produces a signed certificate listing the panels that passed and the panels that did not. The battery covers integrity, which asks whether every value can be traced to a real reading; completeness, which asks whether the expected number of readings arrived; reconciliation, which asks whether totals agree across systems; and plausibility, which asks whether values sit inside the physical envelope their sensor can produce.
Certification runs are scheduled rather than ad hoc, because the campus reserves the bench and the node rooms for the length of the run so that no other work disturbs the window. When the battery finishes, the signer walks the panel results, annotates any exceptions with a reason, and either signs the record or returns the slice for correction. A signed certificate stays in the register for the life of the dataset, and a reissue can be requested when a pipeline changes enough to warrant a fresh look.
- Four test panels
- Signed certificate
- Register entry for life
Edge Node Housing
Edge node housing gives client hardware a secure, monitored home on the campus. The node rooms are built for the long unattended interval that field hardware usually has to endure: steady temperature, filtered air, clean power and a log of both. Each racked node receives a position, a power budget and a monitoring profile. Power draw, inlet temperature and network state are recorded continuously so that an audit can answer a specific question about a specific night rather than offering a general assurance.
Housing is not a passive service. The crew checks every node during visiting hours, confirms that the fan curves are doing their work, and flags a device that shows an unusual thermal pattern before it fails. Clients can request a physical check, a firmware rollback or a cabling change, and each request is logged against the node so the log becomes part of the node history. When a node leaves the campus, it departs with a printed history covering its whole residence.
- Continuous logging
- Racked per node
- Printed node history
Sensor Calibration Days
Calibration days are bench sessions where probes are driven through reference conditions and scored against their published curves. A session begins with an identity check, then runs the probe through a sequence of known points: a set of temperatures, humidities, pressures or gas concentrations, depending on the sensor family. Each point is held long enough to settle and each reading is recorded with a timestamp. The score sheet shows where a probe sits against its curve and whether that position has moved since the previous session.
Drifted probes are corrected in place when the manufacturer allows a correction, and retired when the drift is large enough that a correction would hide a deeper fault. Corrected and retired units are both recorded, so the client can see the true state of a fleet rather than only the units that survived. Calibration days are often paired with a certification run, because a fresh bench score strengthens the plausibility panel and keeps the certificate honest about the age of each probe.
- Reference point scoring
- Correct or retire on site
- Score history kept
Data Lineage Reviews
A lineage review rebuilds the family tree of a dataset and checks that every branch is accounted for. The crew traces each column back to its source, records every transform, join and manual edit along the way, and dates each step. The output is a lineage map that names the owner of each stage and marks the places where a value changes meaning, such as a unit conversion or a time zone shift. Those places are where quiet errors usually hide, and naming them is most of the work.
Lineage reviews are especially useful for data inherited from a previous team, a vendor that has left or a system that has grown by accretion over several years. Where the map runs into a gap, the crew flags it and proposes a repair: a backfill, a schema note, a retained snapshot or a documented exception. A review finishes with a map the client can keep current, and a short list of the moments when the map must be revisited, such as a change of broker, a change of loader or a change of warehouse provider.
- Column to source trace
- Dated lineage map
- Gap repair list
Campus Tour Sessions
A campus tour session is a half day on the floor for a client team that wants to see the work rather than read about it. The visit moves through the node rooms, the calibration bench and the certification desk, with a crew member explaining what is happening at each station and how that station contributes to a record. Visitors see a real rack, a real score sheet and a real certificate, and they are welcome to ask difficult questions about the parts that seem weakest.
Tours are also a practical planning tool. Teams often discover during a walkthrough that a stream they thought was simple has three hops they had forgotten, or that a node they were about to ship will not fit a standard rack. Each session ends with a written walkthrough that lists what the team saw and a short set of recommendations for the next run. Tour sessions are offered to prospective clients, existing clients preparing for a recertification and partners who need to understand the campus before integrating with it.
- Half day on the floor
- Written walkthrough
- Open to client teams
How a season fits together
Process overview: from intake to a signed record
The six services are offered individually, but they were designed to interlock. A typical season moves through five stages, and a client can enter at any of them depending on what already exists. The desk keeps all five on one calendar so that a cohort never collides with another and the bench is never overbooked.
- Intake. A stream, a node or an inherited dataset arrives with a hardware profile and a declared sample rate. The intake desk confirms that the profile, the clock source and the rate agree, and writes a short scope that both sides sign before anything is scheduled.
- Audit sprint. The stream is walked hop by hop, timed and checked for shape. Findings are sorted into blocking items and attention items, and the blocking list becomes the work plan for the next stage.
- Housing and calibration. Hardware that will remain on the campus is racked and monitored, and probes are driven through reference points on a calibration day. Bench scores are attached to the run so that the plausibility panel has current evidence.
- Certification run. A frozen slice is tested across the four panels, exceptions are annotated with a reason, and the signer either issues the certificate or returns the slice for correction. A signed record is entered in the register.
- Lineage review and recertification. The lineage map is refreshed whenever a pipeline changes shape, and the certificate is reissued when the change is large enough to matter. The register keeps the full history so that any future reviewer can follow the chain.
Ready to place a stream on the calendar? The desk answers scope questions by email at certify@antelopedata.buzz and by phone at +19862880713 during campus hours.