Short answer: A smoke-study video is useful only when a reviewer can identify the configuration, intervention, airflow path, acceptance criterion and conclusion. Good documentation converts video into traceable evidence; poor documentation leaves an ambiguous demonstration.
Decision rule: Write the acceptance logic before recording. Otherwise the team is tempted to judge the video by whether it “looks okay.”
Build a camera map
Assign each camera an identifier and mark its location, direction and field of view on a layout. Include a wide establishing view and close views of critical interfaces. If the camera moves, document the new position and the protocol step it supports.
Identify every run
Use a slate, on-screen title or synchronized log showing the protocol step, equipment state, intervention, operator and take number. Include failed or aborted takes in the record rather than deleting them without explanation.
Preserve source files
Retain the original camera files, metadata and a checksum or controlled-copy record where required by the quality system. Editing should create a review copy, not replace the source. The final report should map each conclusion to the original file and time range.
Define observable acceptance criteria
| Risk | Observable criterion |
|---|---|
| Ingress | No fog movement from the lower-grade side into the protected critical zone during the defined condition |
| Operator wake | Fog displaced by the operator does not return across exposed product or critical surfaces |
| First-air obstruction | Required protective flow remains between the HEPA source and the exposed critical point |
| Recirculation | No persistent pocket returns fog from a contamination source to the critical path |
Handle uncertainty and deviations
If the view is blocked, the fog is too dense, lighting is insufficient or the configuration is wrong, document the issue and repeat the run under controlled conditions. Do not stretch an inconclusive video into a pass. Separate protocol deviations from adverse airflow observations because they require different investigations.
Working checklist
- Camera map and identifiers
- Run slate or synchronized log
- Original-file retention
- Editing and review-copy controls
- Time-indexed observation log
- Predefined acceptance criteria
- Inconclusive-run rules
- Deviation and approval workflow
What to include in the RFQ
Tell GSE the number of camera positions, expected study duration, fog visibility needed, environment size and whether repeatable output is required across multiple interventions.
Use the GSE technical RFQ to submit the requirement, attachments, destination and required-on-site date.
Build a reviewable evidence package
A defensible package normally includes an approved protocol, marked layout, equipment identification, configuration and settings, raw video files, an indexed review copy, intervention log, observations, deviations and approval. The video should show enough context to establish direction and location before moving to close views of the critical area.
Define file custody before recording. Preserve the original files, avoid destructive editing and document any clips, overlays or speed changes used in the review copy. An attractive montage without traceable source footage can create more questions than it answers.
Continue the topic: Cleanroom Airflow Visualization Knowledge Center.
Authoritative references
This guide translates public requirements and technical concepts into purchasing and study-planning questions. The controlling standard, regulation, site procedure and quality approval remain authoritative.
Frequently asked questions
Can failed takes be deleted?
They should be handled according to the approved data-integrity and study procedure; unexplained deletion weakens traceability.
Is one close-up camera enough?
Usually not. A close view may miss the source or destination of airflow, so an establishing view is important.
What should happen when the result is inconclusive?
Document why it is inconclusive, correct the test condition and repeat the run under the approved deviation or repeat rule.
Turn this research into a controlled technical request.
Send the application, model, specification or drawing. GSE will preserve the technical lane, identify missing scope and verify current commercial details without treating website copy as an offer.
- Unique request reference
- Completeness score
- Technical-lane routing
- No fabricated channel or inventory claims