Availability Loss Rapid-Experiment Pack

A short playbook of five proven, low-effort experiments to reduce common availability losses — plus an interactive experiment recorder teams can use to plan, run, measure, and sustain each experiment.

{ "Title": "Availability Loss Rapid-Experiment Pack — Experiment Recorder", "IntroductionHtml": "

Run short, focused experiments to improve availability

This pack collects five proven, low-effort experiments teams can run in a shift or a day to chip away at the biggest availability losses. Use the interactive form below to plan each experiment, record baseline and result data, capture failure modes and lessons, and create a short sustainment checklist so small wins stick.

Suggested quick experiments (examples)

  • Quick motor-start check — confirm starter wiring, interlocks, and clearances; reduce startup failures.
  • Standardized daily checks — a 5-minute checklist for critical equipment to catch imminent failures before they cause downtime.
  • Changeover containment — temporary guards, jigs, or simple visual cues to prevent repeated changeover mistakes for a shift.
  • Startup splice of standard work — add a brief startup step to operator standard work that ensures critical items are set before running.
  • Fast parts staging — pre-stage next-job parts and tooling at the point of use to reduce startup time between runs.

Each experiment below captures objective, steps, materials, what to measure, expected lift, likely failure modes, sustainment actions, and a place to record results and lessons learned.

", "SubmitLabel": "Save Experiment Run", "SuccessMessage": "Experiment saved. You can run again, clone this entry, or export results for review.", "DataType": "availability-experiment", "SchemaVersion": "1.0", "Fields": [ { "Key": "experiment_name", "FieldType": "text", "Label": "Experiment name", "HelpText": "Give this run a short descriptive name (e.g., 'Quick motor-start check - Line 2 AM').", "Required": true }, { "Key": "experiment_date", "FieldType": "text", "Label": "Date", "HelpText": "Date of the experiment (YYYY-MM-DD).", "Required": true }, { "Key": "owner", "FieldType": "text", "Label": "Owner / facilitator", "HelpText": "Who is responsible for running and following up on the experiment.", "Required": true }, { "Key": "objective", "FieldType": "textarea", "Label": "Objective", "HelpText": "What specific availability loss are you targeting and why this experiment should help.", "Required": true }, { "Key": "steps", "FieldType": "textarea", "Label": "Steps to run the experiment", "HelpText": "Step-by-step actions the team will take during the experiment.", "Required": true }, { "Key": "materials", "FieldType": "textarea", "Label": "Required materials / tools", "HelpText": "List items the team needs (tape, temporary guards, labels, spare parts, stopwatch, etc.).", "Required": false }, { "Key": "data_to_collect", "FieldType": "textarea", "Label": "Data to collect", "HelpText": "What you will measure (e.g., downtime minutes, fail count, time-to-start) and how often.", "Required": true }, { "Key": "baseline_value", "FieldType": "number", "Label": "Baseline value", "HelpText": "Numeric baseline (minutes of downtime, number of stoppages, seconds to start, etc.) before the experiment.", "Required": false }, { "Key": "expected_lift_pct", "FieldType": "number", "Label": "Expected lift (%)", "HelpText": "Estimated percent improvement (helpful for prioritizing experiments).", "Required": false }, { "Key": "expected_lift_description", "FieldType": "textarea", "Label": "Expected lift description", "HelpText": "Short explanation of where the improvement will come from (e.g., fewer startups lost due to mis-adjustment).", "Required": false }, { "Key": "failure_modes", "FieldType": "textarea", "Label": "Likely failure modes / risks", "HelpText": "What could make the experiment fail or cause unintended consequences?", "Required": false }, { "Key": "success_criteria", "FieldType": "textarea", "Label": "Success criteria", "HelpText": "Clear, measurable criteria for deciding whether the experiment succeeded.", "Required": true }, { "Key": "sustainment_actions", "FieldType": "textarea", "Label": "Sustainment checklist / next steps", "HelpText": "If the experiment works, what immediate small steps make it repeatable and lasting? (who does what, when).", "Required": true }, { "Key": "result_summary", "FieldType": "textarea", "Label": "Result summary", "HelpText": "After running, summarize measured results vs baseline and note any surprises.", "Required": false }, { "Key": "lessons_learned", "FieldType": "textarea", "Label": "Lessons learned", "HelpText": "What the team learned about the process, people, materials, or data collection.", "Required": false }, { "Key": "status", "FieldType": "select", "Label": "Status", "HelpText": "Track the state of this experiment run.", "Required": true, "Options": [ { "Value": "planned", "Label": "Planned" }, { "Value": "running", "Label": "Running" }, { "Value": "completed", "Label": "Completed" }, { "Value": "abandoned", "Label": "Abandoned" } ] }, { "Key": "notes_for_followup", "FieldType": "textarea", "Label": "Notes for follow-up review", "HelpText": "Suggested agenda items or owners for the follow-up review.", "Required": false } ] }

Discussion

Comments and conversation will live here.