OEE: availability × performance × quality
API · /oee-api
OEE Manufacturing API
Overall Equipment Effectiveness (OEE) and lean-manufacturing maths as an API, computed locally and deterministically — the factory-floor productivity metric behind TPM and continuous improvement. The oee endpoint takes the planned production time, downtime, the total and good piece counts and the ideal cycle time (seconds per piece, or an ideal rate in pieces per minute) and returns the three factors and their product: Availability = run time / planned time, Performance = ideal time for the parts made / run time, Quality = good / total, and OEE = Availability × Performance × Quality — the textbook example of a 420-minute shift with 47 minutes down, 19,271 parts and 423 rejects lands exactly on 74.79 % (88.81 % × 86.11 % × 97.80 %). It also breaks out the six-big-losses view: availability loss, performance (speed) loss in parts, quality loss and the fully-productive part count. The takt endpoint gives the takt time = available time / customer demand (the drumbeat the line must match), the required rate, and — given a cycle time or a total work content — the line capacity, utilisation, whether it meets demand and the minimum number of workstations with the line-balancing efficiency. Everything is computed locally and deterministically, so it is instant and private. Ideal for manufacturing, smart-factory, MES, IoT-dashboard and lean/TPM app developers, production-line monitoring and continuous-improvement tools, and industrial-engineering training. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 compute endpoints. This is OEE and takt maths; for equipment reliability/MTBF use a reliability API.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 82 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,575
- attiva
- Chiamate totali
- 21
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 3,650 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 3,650 chiamate/mese
- 2 richieste/sec
- OEE + tempo takt + bilanciamento linea
- Nessuna carta di credito
Starter
€6.15 /mese
- 40,500 chiamate/mese
- 6 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 40,500 calls/month
- 6 req/sec
- Six big losses, capacity, stations
- Email support
Pro
€16.40 /mese
- 201,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 201,000 calls/month
- 15 req/sec
- MES & smart-factory pipelines
- Priority support
Mega
€49.50 /mese
- 1,160,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1,160,000 calls/month
- 40 req/sec
- Platform scale
- Dedicated SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Welding Settings API
Schweißeinstellungen und Verbrauchsmaterialberechnungen als API, lokal und deterministisch berechnet – die Stromstärke-, Draht- und Gaswerte, die ein Schweißer oder Hersteller an der Maschine einstellt. (Für die Verbindungsfestigkeit gibt es eine separate Schweißfestigkeitsberechnung.) Der Stromstärke-Endpunkt liefert einen Startstrom aus der Materialdicke unter Verwendung der Faustregel für Baustahl von etwa einem Ampere pro 0,001 Zoll – eine Achtel-Zoll-Platte läuft also mit etwa 125 A, plus/minus zehn Prozent – und schlägt eine passende Elektroden- oder Drahtgröße vor. Der Abscheidungs-Endpunkt führt die MIG-Arithmetik exakt durch: Abscheidungsrate (lb/h) = Drahtvorschubgeschwindigkeit × Drahtgewicht pro Zoll × 60 × Wirkungsgrad, wobei das Gewicht pro Zoll = (π/4 · d²) × 0,284 lb/in³ für Stahl ist, also legt 0,035-Zoll-Draht bei 300 in/min etwa 4,9 lb/h zu, 4,8 abgeschieden bei 98 % – und aus einer Zielabscheidung werden die Lichtbogenzeit und die zu kaufenden Pfund Draht zurückgegeben. Der Gas-Endpunkt dimensioniert das Schutzgas: Gasverbrauch (ft³) = Durchfluss in CFH × Lichtbogenzeit in Stunden, und die Lichtbogenzeitdauer einer Flasche, also entleert 35 CFH eine 80-ft³-Flasche in etwa 2,3 Stunden tatsächlicher Lichtbogenzeit. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Entwickler von Schweiß-, Metallverarbeitungs-, Fertigungs- und Werkstattverwaltungs-Apps, Tools zur Auftragskalkulation und Verbrauchsplanung sowie Schweißausbildungssoftware. Reine lokale Berechnung – kein Key, kein Drittanbieterdienst, sofort. Maschineneinstellungen, nicht Verbindungsfestigkeit. Live, nichts wird gespeichert. 3 Compute-Endpunkte.
api.oanor.com/welding-api
Machining Speed API
Machining cutting-speed and feed maths as an API, computed locally and deterministically. The speed endpoint converts between cutting (surface) speed and spindle rpm for a given tool or workpiece diameter, in both directions and in either unit system: metric uses N = Vc·1000/(π·D) with Vc in metres per minute and D in millimetres, and imperial uses RPM = SFM·12/(π·D) with the surface speed in feet per minute and the diameter in inches. The feed endpoint computes the table feed rate from the feed per tooth (chip load), the number of teeth or flutes and the spindle rpm for milling (feed = fz·z·N), or from the feed per revolution for turning and drilling, and reports it in millimetres or inches per minute. The materials endpoint lists typical carbide cutting speeds by material, from aluminium and brass through mild and stainless steel to titanium, with a note to use about a third for HSS tooling. Everything is computed locally and deterministically, so it is instant and private. An indicative aid — always confirm with the tool maker's data and adjust for depth of cut, coolant and rigidity. Ideal for CNC and machine-shop tools, CAM and feeds-and-speeds apps, maker and hobby machining, and manufacturing calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is machining feeds and speeds; for screw-thread pitch and tap drill use a thread API and for bolt-circle layouts use a bolt-circle API.
api.oanor.com/machining-api
Grain Bin API
Grain-Bin-Speichermathematik als API, lokal und deterministisch berechnet – die Scheffel- und Gewichtszahlen, mit denen ein Landwirt oder Elevator die Lagerkapazität bemisst. Der Bushels-Endpunkt misst ein rundes Silo: Grundfläche × Korntiefe ergibt Kubikfuß, und ein Kubikfuß fasst etwa 0,8036 Scheffel, sodass ein 18-Fuß-Silo, das 20 Fuß gefüllt ist, etwa 4.090 Scheffel fasst – und Getreide, das zu einem Kegel aufgehäuft ist, addiert einen Kegel von (1/3) × Grundfläche × Spitzenhöhe, sodass eine 4-Fuß-Spitze etwa 270 weitere Scheffel hinzufügt. Der Weight-Endpunkt wandelt Scheffel in Gewicht um, basierend auf dem Standard-Testgewicht der Ernte – Mais und Sorghum bei 56 Pfund pro Scheffel, Weizen und Sojabohnen 60, Hafer 32, Gerste 48 – also wiegen diese 4.090 Scheffel Mais 229.040 Pfund, etwa 114,5 US-Tonnen oder 104 Tonnen; übergeben Sie ein gemessenes Testgewicht für leichtes oder schweres Getreide. Alles wird lokal und deterministisch berechnet, daher ist es sofortig und privat. Ideal für Entwickler von Apps für Landwirtschaft, Getreideheber, Farmmanagement und Agrartechnologie, für Speicherkapazitäts- und Inventar-Tools sowie Erntesoftware. Reine lokale Berechnung – kein API-Key, kein Drittanbieterdienst, sofortig. US-Einheiten (Fuß, Scheffel, Pfund). Live, nichts wird gespeichert. 2 Compute-Endpunkte.
api.oanor.com/grainbin-api
ADA Ramp API
ADA wheelchair-ramp maths as an API, computed locally and deterministically — the run, landing and slope numbers a builder or accessibility planner sizes a ramp by. The rule the ADA fixes is 1 inch of rise per 12 of run, a maximum 8.33 % slope, so the ramp endpoint turns a rise into the ramp: run = rise × 12 (or × 16 / × 20 for a gentler grade if you have the room), plus the level landings the code requires — a 5-foot landing top and bottom and another between runs whenever the rise exceeds 30 inches — and the total length end to end, so a 24-inch rise needs a 24-foot run and 34 feet overall, while a 36-inch rise breaks into two runs with an intermediate landing for 51 feet. The fit endpoint answers the real-world question: does a ramp for this rise fit the run you have? It returns the minimum run an ADA 1:12 ramp needs, whether your space is enough, and the slope you would actually get if you forced it in — flagging when that exceeds 8.33 % and you need a switchback or a lower rise. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, accessibility, home-modification and contractor app developers, ramp-estimator and code-check tools, and building software. Pure local computation — no key, no third-party service, instant. Confirm against current ADA and local code. Live, nothing stored. 2 compute endpoints.
api.oanor.com/adaramp-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per OEE Manufacturing API?
Qual è il limite di velocità di OEE Manufacturing API?
Quanto costa OEE Manufacturing API?
Posso cancellare l'abbonamento in qualsiasi momento?
OEE Manufacturing API è conforme al GDPR?
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/oee-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/oee-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/oee-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/oee-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.