#manufacturing

Welding settings and consumables maths as an API, computed locally and deterministically — the amperage, wire and gas numbers a welder or fabricator dials a machine in with. (For joint strength, that is a separate weld-strength calculation.) The amperage endpoint gives a starting current from material thickness using the mild-steel rule of thumb of about one amp per 0.001 inch — so an eighth-inch plate runs around 125 A, give or take ten percent — and suggests an electrode or wire size to match. The deposition endpoint does the MIG arithmetic exactly: deposition rate (lb/hr) = wire feed speed × the wire’s weight per inch × 60 × efficiency, where weight per inch = (π/4 · d²) × 0.284 lb/in³ for steel, so 0.035-inch wire at 300 in/min lays down about 4.9 lb/hr fed, 4.8 deposited at 98 % — and from a target deposit it returns the arc time and the pounds of wire to buy. The gas endpoint sizes shielding gas: gas used (ft³) = flow in CFH × arc time in hours, and a cylinder’s arc-time duration, so 35 CFH empties an 80 ft³ bottle in about 2.3 hours of actual arc time. Everything is computed locally and deterministically, so it is instant and private. Ideal for welding, metal-fabrication, manufacturing and shop-management app developers, job-costing and consumable-planning tools, and welding-education software. Pure local computation — no key, no third-party service, instant. Machine settings, not joint strength. Live, nothing stored. 3 compute endpoints.

api.oanor.com/welding-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.oanor.com/oee-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