PhotoRobot System Overview
Instructor-only material. Do not share with students. Lives in
03-content/modules/b01-system-overview/training-notes.md(Academy repo) and is rendered toacademy.photorobot.io/lektor/b01-system-overview/delivery(CF Access gated, lektor allowlist only).
Delivery context
This is the first module every Academy student encounters, regardless of certification path. The student is forming their mental model of PhotoRobot here. Get this wrong and every subsequent module is harder to teach.
- For complete beginners (typical Operator pre-enrollment), this is genuinely new material. Slow down, use lots of examples.
- For transferring users (someone who already operates PhotoRobot but is now formalizing certification), this is a vocabulary alignment session. Don’t waste their time on basics — focus on whether they use Workspace, Project, Item, Folder terminology correctly.
- For technical roles (Network Specialist, Integrator, Hardware Specialist), don’t dwell on photographic applications (Section 6 of textbook). Their version of B01 emphasizes the technical architecture (CAPP local + cloud, the hardware-software boundary, the API surface in CAPP).
Adapt your delivery pace to the audience. Standard pace = 45 min. Slow / mixed-experience group = 60 min. Experienced group = 30 min for textbook + 30-45 min discussion.
Time allocation (60-min standard)
| Min | Topic | Format |
|---|---|---|
| 0-3 | Welcome, introductions, what Academy is | Talk |
| 3-8 | What is PhotoRobot? (Section 1 of textbook) | Talk + show product photos / hero shots |
| 8-15 | Brief history (Section 2) | Talk; ~5 min only, don’t dwell |
| 15-25 | 4-stage workflow (Section 3) | Talk + whiteboard diagram + show live CAPP interface |
| 25-35 | Product line categories (Section 4) | Show machine photos; ask “which would you use for X?” |
| 35-45 | Software — CAPP, Locator, Touch, Cloud (Section 5) | Show CAPP interface live |
| 45-50 | Applications — output formats (Section 6) | Show examples; cross-link to customer use cases |
| 50-55 | Glossary alignment (Section 8) | Quick recap |
| 55-60 | Q&A, brief workbook walkthrough | Discussion |
Workbook discussion happens in a separate session block if going slow (90-min total), or as homework if 60-min total.
Demo points — go live in CAPP
Have CAPP open on a second monitor or share-screen. Key live demos:
- (at minute 15-25) Open CAPP, point to where SETUP / CAPTURE / EDIT modes live in the UI. Show the toggle at the top of the interface. Tie the textbook 4-stage diagram to the actual UI tabs.
- (at minute 35-45) Open the Workspace settings panel. Show a configured workspace with a robot + camera + lights listed. Point at the green / gray dot status indicators (“This is what a connected vs. disconnected device looks like.”)
- (at minute 35-45) Show a Project → Item → Folder tree in the Capture view. This is the moment most students “click” — when they see the hierarchy in the actual app, the abstract three-level model becomes concrete.
- (at minute 45-50) Open the cloud version at
app.photorobot.comin a browser. Show that the same project / item is there. Explain the local + cloud relationship visually.
If you don’t have live access to CAPP (e.g., online delivery without hardware), use the Sample Workspace (virtual hardware) instead. It works for all UI demos in this module.
Common mistakes / misunderstandings to anticipate
“Isn’t this just an expensive turntable?”
Students who’ve seen DIY 360 setups will sometimes dismiss PhotoRobot as “just hardware”. Reframe: the value is in the software integration, not the rotation. A DIY turntable doesn’t sync with cameras, doesn’t auto-publish, doesn’t normalize background, doesn’t compose with lights via DMX. Show the integrated workflow in CAPP — that’s where the value sits.
“Why two release tracks of CAPP? Isn’t that confusing?”
Yes, it’s worth 30 seconds of explanation. Stable = battle-tested, frequent releases, what production studios run. Preview = early features, may include bugs, for customers who want to test before others. Tell students: as Academy graduates running customer studios, default to Stable. Don’t be the operator who installs Preview the day before a 1,000-SKU shoot.
“Workspace, Project, Item, Folder — too many words for the same thing”
They are NOT the same thing. Spend extra time here if students conflate them.
- Workspace = hardware list (which robot, which camera, which lights — a physical concept)
- Project = a job grouping (a temporal / business concept — “this week’s spring catalog”)
- Item = a single thing being photographed (an object concept — “the navy blue handbag, SKU 4471”)
- Folder = a group of images inside an item (a output format concept — “the spin folder, the stills folder”)
If they confuse these, every other module is harder.
“Wait, when did Nikon stop being supported?”
If a student brings their own Nikon to a workshop, this matters. Nikon support was discontinued March 2024. As of CAPP 2.5.4, third-party camera integration is possible for any camera, but it’s not the same as native Canon support. Communicate this early and clearly — set expectations.
“Do I need a Cloud account?”
Yes. Even if customer wants to keep all data local, the cloud account is the identity and license layer. Workflow setup is impossible without it. Show the user account login at account.photorobot.com.
Q&A anticipation
These come up often. Prepare a 30-60 second response for each.
-
“How long does it take to set up a workspace for the first time?” Answer: 1-3 hours for a single robot + camera + lights setup if you’re new to it; 15-30 minutes once you know the flow. The investment in SETUP pays off across hundreds of subsequent captures.
-
“How does PhotoRobot compare to [competing system X]?” Answer: Don’t trash competitors. Stick to PhotoRobot’s strengths: integrated hardware + software, RPA-grade automation, depth of post-processing automation, scale of installations (~2,500 worldwide), proven production-grade reliability. If asked for direct comparison, defer to sales conversation — that’s not Academy’s role.
-
“Why Czech Republic? Is it just because the company started there?” Answer: Yes, and it remained there. PhotoRobot is engineered and manufactured in Prague. NY sales office since 2024 for North American customers. Quality of European engineering + competitive cost basis vs. comparable systems built in Western Europe or North America.
-
“What if my customer’s products are very large / very fragile / very weird?” Answer: PhotoRobot has hardware ranges from desk-sized 360 (CUBE) to industrial car carousels (5000). Custom modules exist for special use cases (museum digitization, medical imaging, fashion). The B24 Medical Pink module covers one such custom configuration. Sales + engineering can discuss bespoke setups.
-
“How often does the software update? Will I need retraining?” Answer: Frequent releases (every few weeks for Stable). Most updates don’t change Operator workflow. Major workflow changes are versioned in CAPP and announced via release notes. Academy refresh tests (every 2 years) ensure operators are still aligned with current workflows.
Pitfalls when delivering online
If you’re running this remotely (Zoom / Teams / Meet), watch out for:
- Whiteboard limitations — the 4-stage workflow diagram is hard to draw on a virtual whiteboard. Pre-prepare it as a slide. Same for the Project → Item → Folder hierarchy diagram.
- Demo quality — screen-sharing CAPP at low bandwidth can make the UI look slow / clunky. Pre-prepare short 15-30 second video clips of key UI interactions for fallback.
- Engagement — students may zone out. Use exercise 4 (build a mental map on paper, share photo of result in chat) as an active break.
- Cross-time-zone groups — global customers means USA + EU + Asia in one session. Match-pace to slowest learner; promise post-session 1:1 office hour for advanced students.
Workbook discussion plan
If you’re using the workbook in the session (recommended), allocate 30 minutes after the 60-min textbook delivery. Plan:
| Min | Exercise | Format |
|---|---|---|
| 0-5 | Exercise 1 (workflow stages) — round-robin, students call out their answers | Open discussion |
| 5-15 | Exercise 2 (use case matching) — give 5 minutes to write, then discuss as a group | Independent + discussion |
| 15-20 | Exercise 3 (fluency fill-in-blank) — quick verbal recap, watch for stumbling spots | Quick Q&A |
| 20-25 | Exercise 5 (Acme Studios scenario) — discuss as a group; lead conversation toward presets concept | Discussion |
| 25-30 | Exercise 6 (pre-flight checklist) — go through; identify any student not ready for B02 | Diagnostic |
Skip Exercise 4 (mental map) if running short on time, or assign as overnight homework.
Diagnostic — is the student ready for B02?
Before the student moves on, check Exercise 6’s six checkboxes. If they can’t tick all six, they’re not ready. Options:
- Best case: student needs 15-20 min to re-read textbook section they missed. Send them off, retest before B02.
- Common case: student needs a 1:1 office hour to clarify one specific concept (most often: workspace vs. project distinction).
- Worst case: student is fundamentally lost — they may have skipped the placement test (B01 expects no prereq, but the student is below that floor). Suggest they take PhotoRobot Sales Demo (free 30-min) and retake B01 next week.
Don’t let an unready student into B02. The cost of “saving time” by skipping the check is a confused student all the way through certification.
Notes for refresh / repeat delivery
If you’re re-teaching this module to the same group (e.g., refresh-course path), shorten significantly:
- Skip Section 2 (history) entirely — show the timeline slide for 30 seconds, move on.
- Skip Section 4 (product line) unless new hardware was added since their last cert.
- Focus on Section 3 (workflow) + Section 5 (CAPP) + Section 8 (glossary) — that’s where forgetting matters most.
A refresh delivery of B01 should take 30 minutes, not 60.
Materials you’ll need
Before delivering B01, have ready: