Every shot. Every round. One standard.
SGA-OIS lets every device in a simulator bay share what it knows: the launch monitor, the simulator, club sensors, cameras. Every shot and round becomes a record of what was measured, how, and by whom, so it can count toward a player rating, a statistic or a tournament result on any bay.
Field catalog
204 fields across 23 namespaces, with units, provenance and where each is defined. Filter as you type.
Connect somethingIntegration guides
What to implement for a launch monitor, a simulator or an accessory — in the order you will hit each problem.
Read the standardSpecification
15 normative documents, from units and sign conventions through to bay certification.
Test itTools
The conformance kit runs offline with no account. The SGA Reference Simulator gives you a whole bay on one machine, free with a partner account.
What this standard is for
A simulator bay already measures a golf shot more precisely than anything on a real course. What it has not had is a common language. Today a simulator works with the devices its vendor has chosen to integrate. With SGA-OIS, any simulator can work with any launch monitor, camera or sensor that speaks the standard, automatically. That even includes the player’s own equipment: pull a club from a bag that reads RFID tags, and the simulator can switch to that club without anyone touching a menu. And the measurement travels on — to another vendor’s software, to a player rating system, to a competition — carrying enough about how it was measured that somebody downstream can decide what it is worth.
It works because every device declares what it can provide and what it wants to receive, so data flows both ways: the simulator learns ball speed and spin from the launch monitor, and tells the launch monitor that the next player up swings left-handed. The SGA Engine matches those declarations into a connection matrix, passes each value to the devices that asked for it, and composes one tamper-evident record per stroke, with every value attributed to the device that supplied it. The engine routes and records; it never decides whether a shot or a round counts.
Join on your terms: extend the standard within your own namespace or work with the community to extend the common namespace, and pair your products only with each other if you like. But accept one other company’s device and you accept them all (governance).
How far a result can be trusted
A finished record is only as trusted as the lowest level in its chain: the launch monitor, the simulator, and the bay it was played in. One weak link sets the level for the whole result.
| level | how a device gets there | how a bay gets there | good for |
|---|---|---|---|
A0 Open | Anyone implements the standard. No account, no agreement. | Nobody has claimed it. | Casual play, personal statistics |
A1 Partner | Its maker becomes a technology partner: they promise never to falsify data or build a feature that helps a player cheat, and to tell SGA about any way they find that would allow either. They also publish a fingerprint (digest) of each release, so SGA can check the software in the bay is the software they shipped. | Its owner claims it and agrees not to tamper with it. | SGA Player Rating, leagues |
A2 Signed | A1, plus the device signs what it sends with a key SGA has registered, kept where it is hard to extract. | Certified by SGA at an A2 level. | Sanctioned events |
A3 Hardware | A2, with the key in hardware nobody can read it out of. | Certified by SGA at an A3 level. | Championships |
Each level adds proof that a device is who it says it is, and unlocks more of what a result can count for. Leagues and tournaments can be run by bay owners, simulator companies, clubs and charities, or SGA itself, and each one states the lowest level it accepts. The normative rule is in spec 02 §2.3.
Four things it insists on
Measured, calculated, inferred
Every value says which it is, and names the model behind it if it is not the first.
SeparationThe bay records; it does not judge
Recording is total. What a round is worth is decided somewhere the equipment cannot reach.
PrivacyNo member identity at the bay
The bay holds a label, never an account. A check-in reference resolves only at the association.
TrustTrust levels A0–A3
A result is only as trusted as the lowest level among its launch monitor, simulator and bay. A1 is a partner’s promise; higher levels add proof.
The specification
| document | what it settles | |
|---|---|---|
00 | Conventions | Units, sign conventions, time, identifiers and versioning, and the two things a bay may never do: hold a member’s identity or judge a round. |
01 | Provenance | Every value is measured, calculated or inferred, and why that label belongs to a firmware build. |
02 | Identity, attestation, and the trust chain | Who stands behind each device and bay, trust levels A0–A3, and why a result takes the lowest level in its chain. |
03 | Capability handshake and the connection matrix | How devices describe themselves, how the engine connects producers to consumers, and how one record is composed per stroke. |
04 | The standard as a signed, distributable artifact | The standard as a signed bundle, and how a bay stays current while offline. |
05 | Deployment and the privilege boundary | The privilege boundary: what the engine does without elevation, and why it never needs more. |
06 | The shot record | What one shot record carries: course identity, lie, environment, trajectory, putting and the scorecard. |
07 | Offline operation, store-and-forward, and presence | Phones as couriers for offline bays, and proving a player was present. |
08 | Competition conformance | Event rules packages, settings attestation and identity assurance for competition. |
09 | Transport, sessions, and latency | Persistent sessions, framing and keepalive, the cloud uplink and its fallback ladder, and the latency budget. |
10 | The bay capability profile | What a bay can prove about its equipment, connectivity, presence and cameras. |
11 | Media capture | Swing clips from a ring buffer, camera exclusivity, consent and retention. |
12 | Notices | How the engine tells players what it sees going wrong while it can still be fixed. |
13 | Device lifecycle: admission, updates, enrollment | Keeping a device current, refusing a dangerous one, and attaching one to a bay. |
14 | The bay certificate, and enforcing a tier | Carrying a certification decision back to the bay, and what it may not be taken to mean. |
Reference
Fields
Every dotted data name the standard defines, what it carries and in which units.
27 typesMessages
The five wire namespaces and every message in them.
61 kindsJournal records
What the bay writes down, and when each record is written.
Connecting your device / software
Simulator software integration
You are the only participant that knows where the ball is: the hole, the lie, the distance left and the score. Learn what to hand over, and in what order.
GuideLaunch monitor integration
Four fields make you conformant, and about a dozen more make the whole bay better. Start here for the shortest integration in the standard.
GuideAccessory and single-purpose device integration
A device that contributes one field is a first-class participant. See how a club reader, a camera or a single sensor joins the bay with only what it knows.
GuideTesting your integration
Prove your device works before you ever talk to SGA. Meet the conformance kit and the SGA Reference Simulator, a complete bay on one machine.
GuideVerifying a bundle
You do not have to take our word for what is in the standard you are running. Check the signature for who issued it, and rebuild it yourself for what is in it.
GuideSGA-OIS conformance kit
Public and runnable offline, with no network access and no SGA account. Run it against your device before you ship.
Technology partners
Everything above is free to read, implement and ship. You do not need an account to use the specification, run the conformance kit, or sell a product that speaks SGA-OIS.
A technology partner account is also free and has no approval queue. It adds the SGA Reference Simulator — a complete bay on one machine to develop against — engine builds for every platform, schema extension tooling, and a named contact at SGA who understands your project and integration. It is also how you reach level A1: you agree never to falsify data or build cheating features, to report any way you find that would allow either, and you publish a fingerprint of each release. That is where rounds start counting toward an SGA Player Rating. Signing (A2, A3) builds on it.