Documentation Completion and Project Defense

Documentation Completion and Project Defense

Your capstone project concludes with two deliverables that mirror real industry practice: a complete technical documentation package and a live system defense before a review panel. Both are graded. Treat this lesson as your final quality check before you hand off a working automated cell to someone who was not in the room when you built it.

Why Documentation Matters in Industry

A robot cell or mechatronic system is only as maintainable as its documentation. When a technician responds to a midnight fault, they rely on the electrical schematic, the PLC program printout, and the troubleshooting log — not on memory. Incomplete or inaccurate documentation is a safety hazard: a missing redline can send someone to the wrong terminal; an unsigned commissioning checklist cannot prove that a safety function was verified before startup. NFPA 79 requires that the electrical documentation for industrial machinery be kept accurate and available. Your documentation package must reflect the system as built, not as originally designed.

Building the Documentation Package

Assemble every item on the documentation checklist before peer review:

• Finalized electrical schematics with all redlines incorporated — every wire change made during build must appear on the drawing.
• Pneumatic or hydraulic circuit diagram showing all valves, actuators, and pressure/flow control devices.
• PLC program printout with rung comments that explain the intent of each logic block, not just its function. A reader should understand what the system is doing without running the software.
• FANUC robot program backup file and printed listing — the backup proves the file is current; the listing lets someone read it without a teach pendant.
• HMI screen captures of every screen, labeled to identify each control and indicator.
• Final bill of materials (BOM) listing actual parts used, including part numbers and quantities.
• Commissioning checklist, signed — every safety function (E-stop, safety gate, light curtain, LOTO point) verified and initialed.
• Troubleshooting log with all three seeded-fault entries: fault description, diagnostic steps taken, root cause identified, and corrective action.
• One-page system description written for a maintenance technician. Use plain language. State what the system does, where the LOTO points are, and which standards govern its safe operation.

During peer review, your partner checks your package against the checklist and flags any missing or incomplete item. Resolve every flag before submission. A missing section on defense day is an automatic documentation-category deduction.

Structuring Your 15-Minute Presentation

Organize your presentation in six sections, each given roughly equal time:

1. Project scope and system overview — state the task the system performs and its major subsystems.

2. Safety measures and standards — name the specific standards: OSHA 29 CFR 1910.147 for lockout/tagout, NFPA 70E for electrical safety (arc-flash and shock boundaries, PPE selection, absence-of-voltage verification), OSHA 1910.212 for machine guarding, and ANSI/RIA R15.06 / ISO 10218 for robot safeguarding. Point to physical evidence: the LOTO points, the safety-rated fence or light curtain, the PPE station.

3. PLC program logic with live HMI demo — walk through at least one complete sequence on the ladder diagram, then run it on the HMI so the panel sees it execute.

4. Robot program walkthrough with live cycle — explain frame selection (world, user, tool), key positions, and I/O handshakes, then run at least one full cycle using the teach pendant or AUTO mode.

5. Key design decisions and changes — explain one decision you made during build and why. If a design changed, say what drove the change.

6. Troubleshooting log summary — describe one seeded fault: how you diagnosed it and what you learned.

The running system must be powered, guarded, and used as your visual aid. Do not use a video of the system in place of the live demonstration.

Answering Panel Questions Without Notes

The panel will probe your understanding, not just your memory. Prepare to answer questions such as:

• Frame selection — Know why you chose a specific FANUC frame type (world, user, or tool) for a given move. User frames let you re-reference a fixture without rewriting positions; tool frames define the TCP so the robot rotates around the tool tip.
• LOTO with a hydraulic circuit — Adding a hydraulic circuit adds a stored-energy source. OSHA 29 CFR 1910.147 requires that hydraulic pressure be bled to zero and the source isolated before work begins. Your LOTO procedure must add a pressure-bleed step and verify zero pressure at the actuator.
• IEC 61131-3 language selection — Ladder diagram is familiar to electricians and suits discrete logic. Structured text is more compact for math-heavy sequences. Function block diagram suits continuous signal flow. Sequential function chart is clearest for multi-step processes. Know which language is in your program and defend why.
• PMMI or Siemens L1 concepts in your system — Be ready to point to a physical component and connect it to a certification topic: a solenoid valve to fluid power, a VFD to motor controls, a PLC input to IEC 61131-3 I/O concepts, a pneumatic cylinder to electro-pneumatic circuits.

For at least half the questions, no notes. Practice your explanations aloud before defense day.

Passing the Defense

The rubric covers five categories: documentation completeness, safety compliance demonstration, technical accuracy of explanation, live system performance, and professional communication. You must score at least 75% averaged across all five. The live system must complete at least three correct cycles during the presentation. If you score below 75%, you receive one week of remediation and a second defense date. Use that week to re-examine every weak category and practice under time pressure.