Swift Changeover: setup reduction analysis from video

Swift Ops now supports a second upload workflow called Swift Changeover. Teams can still upload a process video for work-instruction generation, but they can now also choose Changeover / Setup Reduction before upload and review the same recorded work through a setup-reduction lens.

The goal is practical: help manufacturing and continuous-improvement teams review what happened during a setup or changeover, identify likely improvement opportunities, and compare separate X and Y outputs without changing the existing Swift Ops upload experience.

What Swift Changeover is built to review

Swift Changeover focuses on the parts of setup work that teams usually want to discuss after the video is captured. That includes the observed task sequence, likely internal versus external work, common sources of delay, and a proposed faster sequence for review.

The structured output is meant to support engineering, CI, production, and maintenance conversations. It is not positioned as guaranteed consulting advice or a final engineering answer. It is a grounded review aid that gives teams a faster starting point from recorded work.

What the output includes

For each uploaded changeover video, Swift Ops now produces separate X and Y analysis outputs. Each one is structured for review and can include an overview of the observed changeover, ordered tasks with timestamps, likely internal or external classification, practical waste observations such as waiting, motion, and tooling prep, plus open questions where the video does not fully answer what happened.

The output also includes a proposed faster future-state sequence. That sequence is designed to help teams review where work may be moved outside downtime, where tooling could be staged earlier, and where repeated adjustment, searching, or handling may be reduced.

Why this matters for setup reduction work

Many teams already record setup videos, but the review process still depends on someone manually breaking the video apart, documenting the sequence, and preparing a discussion-ready summary. Swift Changeover helps shorten that first pass so the team can spend more time reviewing real opportunities and less time assembling the initial structure.

It also creates a cleaner way to compare outputs. Because X and Y remain separate, teams can review both versions side by side and decide which one is more useful for their particular changeover-review workflow.

How it fits into the rest of Swift Ops

Swift Changeover does not replace the existing Work Instruction workflow. It adds a second path before upload so teams can decide what they want from the video before processing starts. If the goal is documentation and release-ready work instructions, choose Work Instruction. If the goal is setup reduction review, choose Changeover / Setup Reduction.

That split keeps the product cleaner. Documentation teams can stay on the standard work path, while setup-reduction teams can use a workflow that is tailored to internal and external work, waste observations, and future-state sequence review.