{
  "title": "OEE calculator",
  "human_url": "https://happytails.ai/en/business-tools/overall-equipment-effectiveness-calculator/",
  "agent_url": "https://happytails.ai/agents/en/business-tools/overall-equipment-effectiveness-calculator/",
  "language": "en",
  "markdown_url": "https://happytails.ai/en/business-tools/overall-equipment-effectiveness-calculator.md",
  "content": "OEE calculator\nCalculate OEE and separate availability, speed and first-pass quality losses for a production period.\nHow can we improve this tool?\nReport a problem or share an idea.\nPlease leave out private information. Your message and the tool name go to our team via PostHog.\nHow to use OEE calculator\nEnter planned and actual run time for the same production period. Select their time unit.\nEnter ideal cycle time in seconds, total units and first-pass good units.\nCalculate OEE and inspect the separate losses. Download the complete JSON or CSV report.\nUseful next steps\nTakt time calculator\nCycle time bottleneck calculator\nKeep the three factors separate\nAvailability is run time divided by planned time. Performance is ideal cycle time multiplied by total units, divided by run time. Quality is first-pass good units divided by total units. Multiplying these factors gives OEE.\nCheck the input assumptions\nExclude scheduled nonproduction from planned time. Good units exclude rework. A stated ideal cycle cannot imply more ideal production time than the actual run time. With no production, undefined factors remain undefined instead of being shown as zero.",
  "content_format": "text/plain",
  "visibility": "public",
  "links": [
    {
      "name": "Takt time calculator",
      "url": "https://happytails.ai/en/business-tools/manufacturing-takt-time-calculator/"
    },
    {
      "name": "Cycle time bottleneck calculator",
      "url": "https://happytails.ai/en/business-tools/cycle-time-bottleneck-calculator/"
    }
  ],
  "tool": {
    "id": "overall-equipment-effectiveness-calculator",
    "category": "business-tools",
    "built": true,
    "requirements": "Use nonnegative values with at most six decimal places and whole unit counts up to 1,000,000,000. Time inputs are converted to seconds, with a maximum of 1,000,000,000 seconds. Ratios are rounded to six decimal places; JSON and CSV preserve the calculated values and assumptions. Processing stays on your device.",
    "implementation": {
      "fields": [
        {
          "key": "plannedTime",
          "label": "Planned production time",
          "value": "1000",
          "type": "text",
          "inputMode": "decimal",
          "maxLength": 24
        },
        {
          "key": "runTime",
          "label": "Run time",
          "value": "800",
          "type": "text",
          "inputMode": "decimal",
          "maxLength": 24
        },
        {
          "key": "timeUnit",
          "label": "Production time unit",
          "value": "seconds",
          "type": "select",
          "values": [
            "seconds",
            "minutes",
            "hours"
          ],
          "labels": {
            "seconds": "Seconds",
            "minutes": "Minutes",
            "hours": "Hours"
          }
        },
        {
          "key": "idealCycleSeconds",
          "label": "Ideal cycle time (seconds)",
          "value": "2",
          "type": "text",
          "inputMode": "decimal",
          "maxLength": 24
        },
        {
          "key": "totalCount",
          "label": "Total units",
          "value": 300,
          "type": "number",
          "min": 0,
          "max": 1000000000,
          "step": 1
        },
        {
          "key": "goodCount",
          "label": "First-pass good units",
          "value": 270,
          "type": "number",
          "min": 0,
          "max": 1000000000,
          "step": 1
        }
      ],
      "input": false,
      "presentation": "metrics",
      "note": "Use planned production time excluding scheduled nonproduction and run time for the same period. Ideal cycle time is always in seconds. Good count means first-pass good units. Availability, performance and quality are separate; undefined zero-production factors are not treated as zero. Results describe the supplied data, not an industry benchmark.",
      "experience": {
        "automatic": false,
        "single": false,
        "inputMaxLength": 1000000,
        "inputMode": "text",
        "label": "Your text",
        "placeholder": "Type or paste your input…",
        "help": "Up to 1,000,000 characters. Review the settings before running.",
        "action": null
      },
      "mode": "explicit",
      "interactive": false
    },
    "execution": "Browser interface",
    "api": null,
    "browser_agent": {
      "supported": true,
      "name": "run_current_tool",
      "discovery": "WebMCP on the human page in a supporting browser",
      "verification": "See audit/API-AUDIT.md; availability is not verification"
    }
  },
  "markdown": "# OEE calculator\n\n- Human page: https://happytails.ai/en/business-tools/overall-equipment-effectiveness-calculator/\n- Markdown: https://happytails.ai/en/business-tools/overall-equipment-effectiveness-calculator.md\n- Structured JSON: https://happytails.ai/agents/en/business-tools/overall-equipment-effectiveness-calculator/index.json\n- Visibility: public\n\n## Tool capabilities\n\n| Property | Value |\n| --- | --- |\n| Tool ID | `overall-equipment-effectiveness-calculator` |\n| Category | business-tools |\n| Implementation | Registered implementation. Registration alone is not a production-quality guarantee. |\n| Browser execution | Use the visible action or interactive controls. |\n| Browser processing | Browser; see tool notes for network behavior. |\n| HTTP API | Not callable through HTTP. |\n| Browser-agent interface | run_current_tool |\n\n### Implementation notes\n\nUse planned production time excluding scheduled nonproduction and run time for the same period. Ideal cycle time is always in seconds. Good count means first-pass good units. Availability, performance and quality are separate; undefined zero-production factors are not treated as zero. Results describe the supplied data, not an industry benchmark.\n\n### Inputs and settings\n\nNo free-text input is required. Use the file inputs and/or settings below.\n\n| Setting | Meaning | Control type | Default | Constraints |\n| --- | --- | --- | --- | --- |\n| `plannedTime` | Planned production time | text | \"1000\" |  |\n| `runTime` | Run time | text | \"800\" |  |\n| `timeUnit` | Production time unit | select | \"seconds\" | Allowed: seconds, minutes, hours |\n| `idealCycleSeconds` | Ideal cycle time (seconds) | text | \"2\" |  |\n| `totalCount` | Total units | number | 300 | min=0 max=1000000000 step=1 |\n| `goodCount` | First-pass good units | number | 270 | min=0 max=1000000000 step=1 |\n\n### Browser-agent workflow\n\n1. Open the human page in a browser that supports WebMCP.\n2. Discover the interface exposed by that page; use its actual schema.\n3. Select files on the page first when the tool requires files.\n4. Call `run_current_tool` with valid input and settings.\n5. Inspect the returned result or error and the displayed output. Retrieve files from the displayed download links.\n\nCalls do not automatically copy or download results. Browser permissions still apply. Interface availability alone is not proof of successful execution.\n\n### Planning specification\n\nUse nonnegative values with at most six decimal places and whole unit counts up to 1,000,000,000. Time inputs are converted to seconds, with a maximum of 1,000,000,000 seconds. Ratios are rounded to six decimal places; JSON and CSV preserve the calculated values and assumptions. Processing stays on your device.\n\nThis describes intended requirements. Use the implementation notes, interface schema and observed output to determine current support.\n\n### Complete machine-readable capability record\n\n```json\n{\n  \"id\": \"overall-equipment-effectiveness-calculator\",\n  \"category\": \"business-tools\",\n  \"built\": true,\n  \"requirements\": \"Use nonnegative values with at most six decimal places and whole unit counts up to 1,000,000,000. Time inputs are converted to seconds, with a maximum of 1,000,000,000 seconds. Ratios are rounded to six decimal places; JSON and CSV preserve the calculated values and assumptions. Processing stays on your device.\",\n  \"implementation\": {\n    \"fields\": [\n      {\n        \"key\": \"plannedTime\",\n        \"label\": \"Planned production time\",\n        \"value\": \"1000\",\n        \"type\": \"text\",\n        \"inputMode\": \"decimal\",\n        \"maxLength\": 24\n      },\n      {\n        \"key\": \"runTime\",\n        \"label\": \"Run time\",\n        \"value\": \"800\",\n        \"type\": \"text\",\n        \"inputMode\": \"decimal\",\n        \"maxLength\": 24\n      },\n      {\n        \"key\": \"timeUnit\",\n        \"label\": \"Production time unit\",\n        \"value\": \"seconds\",\n        \"type\": \"select\",\n        \"values\": [\n          \"seconds\",\n          \"minutes\",\n          \"hours\"\n        ],\n        \"labels\": {\n          \"seconds\": \"Seconds\",\n          \"minutes\": \"Minutes\",\n          \"hours\": \"Hours\"\n        }\n      },\n      {\n        \"key\": \"idealCycleSeconds\",\n        \"label\": \"Ideal cycle time (seconds)\",\n        \"value\": \"2\",\n        \"type\": \"text\",\n        \"inputMode\": \"decimal\",\n        \"maxLength\": 24\n      },\n      {\n        \"key\": \"totalCount\",\n        \"label\": \"Total units\",\n        \"value\": 300,\n        \"type\": \"number\",\n        \"min\": 0,\n        \"max\": 1000000000,\n        \"step\": 1\n      },\n      {\n        \"key\": \"goodCount\",\n        \"label\": \"First-pass good units\",\n        \"value\": 270,\n        \"type\": \"number\",\n        \"min\": 0,\n        \"max\": 1000000000,\n        \"step\": 1\n      }\n    ],\n    \"input\": false,\n    \"presentation\": \"metrics\",\n    \"note\": \"Use planned production time excluding scheduled nonproduction and run time for the same period. Ideal cycle time is always in seconds. Good count means first-pass good units. Availability, performance and quality are separate; undefined zero-production factors are not treated as zero. Results describe the supplied data, not an industry benchmark.\",\n    \"experience\": {\n      \"automatic\": false,\n      \"single\": false,\n      \"inputMaxLength\": 1000000,\n      \"inputMode\": \"text\",\n      \"label\": \"Your text\",\n      \"placeholder\": \"Type or paste your input…\",\n      \"help\": \"Up to 1,000,000 characters. Review the settings before running.\",\n      \"action\": null\n    },\n    \"mode\": \"explicit\",\n    \"interactive\": false\n  },\n  \"execution\": \"Browser interface\",\n  \"api\": null,\n  \"browser_agent\": {\n    \"supported\": true,\n    \"name\": \"run_current_tool\",\n    \"discovery\": \"WebMCP on the human page in a supporting browser\",\n    \"verification\": \"See audit/API-AUDIT.md; availability is not verification\"\n  }\n}\n```\n\n## Page guide\n\nCalculate OEE and separate availability, speed and first-pass quality losses for a production period.\n\nHow can we improve this tool?\n\nReport a problem or share an idea.\n\nPlease leave out private information. Your message and the tool name go to our team via PostHog.\n\n### How to use OEE calculator\n\n1. Enter planned and actual run time for the same production period. Select their time unit.\n2. Enter ideal cycle time in seconds, total units and first-pass good units.\n3. Calculate OEE and inspect the separate losses. Download the complete JSON or CSV report.\n\n## Useful next steps\n\n- [Takt time calculator](https://happytails.ai/en/business-tools/manufacturing-takt-time-calculator/) ([Markdown](https://happytails.ai/en/business-tools/manufacturing-takt-time-calculator.md))\n\n- [Cycle time bottleneck calculator](https://happytails.ai/en/business-tools/cycle-time-bottleneck-calculator/) ([Markdown](https://happytails.ai/en/business-tools/cycle-time-bottleneck-calculator.md))\n\n## Keep the three factors separate\n\nAvailability is run time divided by planned time. Performance is ideal cycle time multiplied by total units, divided by run time. Quality is first-pass good units divided by total units. Multiplying these factors gives OEE.\n\n### Check the input assumptions\n\nExclude scheduled nonproduction from planned time. Good units exclude rework. A stated ideal cycle cannot imply more ideal production time than the actual run time. With no production, undefined factors remain undefined instead of being shown as zero.\n"
}