A PTC Vuforia Expert Capture Alternative That Skips the Authoring Step

PTC Vuforia Expert Capture is a serious product aimed at a real problem. It puts the expert's point of view on a headset, turns the recording into step-by-step AR work instructions, and adds CAD-based overlays and AI-assisted inspection on top. For a plant with good engineering data and a documentation team, that is a strong combination.

Teams searching for a Vuforia Expert Capture alternative are rarely questioning the goal. They are questioning the path: a capture session on eyewear, an editing pass in a browser, approval and publishing, all on headset hardware whose support end date Microsoft has already published. This page covers why teams look elsewhere, how Bob captures knowledge differently, where Vuforia remains the better choice, and how a Bob pilot works.

Why teams look for a Vuforia Expert Capture alternative

Most of the reasons come straight from how PTC documents its own product. None of them make Expert Capture a poor tool. They make it a particular kind of tool.

• Capture is only the first half: PTC's setup guide describes three stages: capture on an eyewear device, author in Vuforia Editor on an internet-connected computer, then execute on a viewing device. In Editor, someone uploads the capture files, adds text, images and video to each step, edits the audio, rearranges steps, places 3D markers, and routes the procedure for approval before it is published. PTC notes that capture files cannot be uploaded straight from the headset into Editor.
• The expert runs a recording session, not a normal shift: On HoloLens 2, the expert starts a session and moves to the next step by voice command. PTC's editing guidance tells editors who did not record a capture to refer to the procedure script or ask the person who recorded it. That suits a procedure you can plan and perform on cue. It suits less well the knowledge that only shows up when a job goes sideways.
• The headset question now has a date on it: Vuforia Capture runs on HoloLens 2, Trimble XR10, and RealWear Navigator 500 and 520 eyewear. Phones and tablets can view procedures but cannot capture them. Microsoft's HoloLens 2 release notes state that HoloLens devices have not been manufactured since December 2024, that the November 2024 update was the final feature release, and that monthly security servicing continues through December 2027. PTC has said on its community forum that it will keep supporting HoloLens 2 and is developing alternative hands-free options. A team planning a multi-year capture program is right to ask what its experts will be wearing in 2028.
• The strongest AR features depend on CAD: Captured procedures do not need CAD data. The AR layer does. Step Check, PTC's AI visual inspection, requires CAD data for the object being checked, and 3D overlays rely on model files that PTC notes usually come from engineering, the equipment maker, or technical publications. For older equipment and field assets without clean 3D data, that is real work before the AR pays off.
• Some of the knowledge is not a procedure: A step-by-step instruction records what to do, in order. What leaves with an experienced worker is often the judgement between the steps: which machine is reliable and which is not, the sensor nobody trusts, how to get one pump unstuck. That knowledge surfaces while the expert does and explains real work, which is a different capture problem from producing a clean instruction.

Bob: capture the real job, skip the authoring step

Bob is Mission Control's wearable capture device and data service. An experienced worker wears the chest-mounted unit through a real job or shift. It records first-person video, audio narration, and spatial data, meaning the unit's location and orientation in your facility, while the worker does the job and talks through what they are doing and why.

There is no staged demonstration and nothing to set up beforehand. There is no write-up, no author, and no review cycle between the work and the record of it. The job happens the way it always happens, and the reasoning is captured with it rather than reconstructed afterwards.

Key features

• First-person capture of real work: Worn through an actual job or shift, not a recording session.
• Video, audio narration, and spatial data: Position ties what the expert said to the workstation or part of the facility where they said it.
• A version without a camera: One version uses a volumetric spatial sensor instead of a camera, for sites where video is not acceptable.
• Your tenancy, your data: Recordings land in your own cloud tenancy.
• The expert's own tool: Experienced workers opt in to wearing Bob, on their terms.
• Put to work on Swarm: Captured knowledge can be run and governed by synthetic workers on Swarm, Mission Control's platform.

What makes Bob different

Vuforia Expert Capture and Bob start from the same correct observation: the expert's point of view is the best record of how work is actually done. The difference is what happens next. Expert Capture treats the recording as raw material for an authored procedure. Bob treats the recording of real work as the knowledge itself.

That changes who carries the load. With Expert Capture, a procedure exists once someone has edited, approved, and published it. With Bob, the expert does their job and the capture is done. It also changes what gets kept. An authored procedure keeps the clean path. A shift of real work keeps the detours, the extra check the expert adds, and the explanation of why.

Bob's scope is narrower in other ways, and it is worth saying plainly. Bob captures hands-on physical work. It is not an AR authoring suite, and it does not overlay CAD models on equipment or run pass or fail inspections. See how capture works on the floor for manufacturing and energy teams, or by role for a millwright or quality inspector.

PTC Vuforia Expert Capture vs Bob, side by side

Who should choose PTC Vuforia Expert Capture (and who should choose Bob)

Vuforia Expert Capture does several things Bob does not do at all. If those things are the job, stay with Vuforia.

Choose PTC Vuforia Expert Capture if:

• You want AR content on the equipment itself. Vuforia aligns 3D content to the physical object on phones, tablets, and HoloLens, with part and point markers that guide a worker to the right spot.
• Quality inspection is the priority and you have CAD data. Step Check gives AI pass or fail checks displayed in AR.
• You already work in the PTC ecosystem. Vuforia Editor imports media from Creo Illustrate, and Expert Capture now includes everything that was Vuforia Instruct.
• You need governed, distributed procedures: approval routing, a Distribution Center for permissions and published procedures, Vuforia Insights reporting on executed procedures, and Word export for compliance documentation.
• Your workers need to follow instructions on devices they already carry. Vantage runs on iOS and Android phones and tablets, on eyewear, and in the browser.
• You have a documentation or engineering team with time to author and maintain procedures from every capture.

Choose Bob if:

• The knowledge at risk lives in an experienced worker's hands and judgement, and you want it captured during real work rather than a planned recording session.
• Nobody has time to author, approve, and maintain a procedure from every capture.
• You would rather not start a new capture program on headsets whose security servicing end date is already published.
• Recordings must land in your own cloud tenancy, or cameras are a problem on your site.
• Much of your equipment has no clean CAD data to build AR content from.
• The goal is continuity: keeping how a job is really done after the person who does it best moves on.

Plenty of sites will want both: authored AR instructions for standard, CAD-backed tasks, and Bob for the judgement that never made it into a procedure. For the head-to-head view, see Mission Control vs PTC Vuforia Expert Capture. For the method question underneath this page, read AR work instructions vs wearable capture.

How moving from Vuforia Expert Capture to Bob works

This is not a migration project. There is no procedure library to port, because Bob does not start from authored steps, and there is no reason to retire Vuforia procedures that work. The practical move is to point capture at the work your procedures do not cover, and to stop authoring new procedures where a record of real work would serve.

1. Request a pilot: Use the Pilot Bob form or book a call with Mission Control. A Bob pilot is a 90-day fixed-length trial in your facility.
2. Set up your tenancy: Mission Control ships a case of 2 Bob units, and your IT team installs the data platform in your own cloud tenancy with Mission Control's support.
3. Capture real work: Experienced workers who opt in wear Bob through their normal jobs. There is nothing to stage and nothing to author. Judge the pilot on the recordings.

Captured knowledge lands in your own environment, where it can be run and governed by synthetic workers on Swarm. Start at Pilot Bob.

References

PTC and Microsoft pages accessed September 14, 2026.

• PTC: Vuforia Expert Capture product page
• PTC: Vuforia Instruct is now Vuforia Expert Capture
• PTC Success Path: Get familiar with Vuforia Expert Capture
• PTC Success Path: Choose devices
• PTC Success Path: How to choose the right devices
• PTC Success Path: Prepare to edit procedures
• PTC Success Path: Get started with devices
• PTC Help Center: Supported devices, operating systems, and browsers
• PTC Help Center: Vuforia Capture for HoloLens 2 and Trimble XR10
• PTC Help Center: Create and edit procedures with Vuforia Editor
• PTC Community: Vuforia View on HoloLens 2 end-of-life support message
• Microsoft Learn: HoloLens 2 release notes