Compare the collection window with recorded production and interventions. Assess spatial relevance and exposure before determining impact.
All blueprints
Put every environmental result in context.
Connect the sampling point, original count and actual operation. Use neil to investigate signals, prepare follow-up work and configure a monitoring program your team can review.
The result arrives after the operation.
EM-026-03 was collected at P-01 on 1 September, from 09:10 to 09:20 UTC. Its final read was recorded on 7 September. Follow the collection time back to the operation; the read date does not identify which batch was running.
The source retains eight colonies, 1.00 m³ of air, media M26-04 and incubation INC-041. Organism identification is pending. Keep an unread plate, a zero count and an invalid result distinct.
Collected at P-011 September
09:10–09:20 UTC
INC-041 / incubation
Final read7 September
08:45 UTC · 8 CFU
Inspect the collection and laboratory record
A signal needs its rule and its source.
The three observations at P-01 are 5, 6 and 8 CFU/m³. The example's EM-R-04 v02 rule raises a review for three successively increasing results, even below its action threshold of 10 CFU/m³. These are fictional support-area criteria, not cleanroom-grade limits.
Batch F-041 and an equipment transfer overlap the collection. F-042 starts later. Timing narrows the candidate work; location, airflow, exposure, cleaning and organism evidence still need assessment. A later batch is not automatically excluded if a condition could have persisted.
Three increasing results trigger this example’s review rule. The separate action threshold is 10 CFU/m³.
Inspect the operation assessment
Give neil an investigation to prepare.
Ask neil to follow permitted location, sample and production records, separate observations from possible explanations, and create linked follow-up work. Bring the sampling procedure when the response needs a changed workflow as well as an assessment.
Trace the signal into the operation
“Investigate P-01. Compare the collection window with production, interventions and adjacent observations. Show what evidence is missing.”
neil can prepare a candidate population, a chronology and linked requests for identification and operation evidence. Ask it to explain inclusion and exclusion reasons and the observations that would distinguish competing explanations.
Configure the sampling workflow
“Turn this procedure into linked collection, incubation and result templates. Include the failure paths and verification cases.”
neil can author required media, device, volume and time fields, source references, review states and rule configuration. Ask for tests covering a missed collection, invalid count, absent identification and changed rule version. People run verification and approve publication.
Prepare a controlled program change
“Use this investigation to propose a targeted monitoring change and define how we will assess whether it helped.”
neil can stage revised plan configuration, requirement links, training-impact work and an effectiveness review with a defined population and source records. The proposed location or frequency still needs scientific assessment and authorisation.
Illustrative requests and proposed work, not a demonstrated neil execution. People assess the evidence, verify configuration and approve decisions.
Change the program without rewriting its history.
A sampling point has a physical position, method and reason to exist. Version its plan, frequency, volume, operational conditions and response rules. Preserve missed or invalid collections when replacement work is created.
Instrument connections need source-specific mapping and verification for timestamps, units, gaps, duplicates and delayed files. Culture-based findings include incubation and reading delays; they are not immediate sensor alarms. Review monitoring alongside facility, cleaning and process controls, with authorised people deciding program changes and product disposition.
Capabilities
Retain the rule version and source observations behind a signal. Keep a recurring increase separate from an identified organism or established cause.
Connect collection, sampled volume, media, incubation, reading and identification. Preserve the difference between missing, zero and invalid results.
Keep candidate operations, inclusion and exclusion reasons, missing evidence and the resulting review together. Product disposition requires its own authority.
Saved native chart, not a live feed. Overlap identifies candidates; it does not establish contamination or batch impact.
Open full-size image in a new tabConnected records
Entity hierarchy
What it records
Kind
Monitoring Location
Sample point in facility. Room, coordinates, classification, alert limits, frequency.
entity
FILL-A-001
Filling-zone point with justified method, operational condition, monitoring frequency and effective-dated limits.
record
EM Sample
Environmental sample. Air, surface, personnel. Collected, incubated, counted, identified.
entity
Viable Air
Active air sampling. CFU per cubic meter. Impaction or impingement method.
template
Settle Plate
Passive air monitoring with protocol-defined exposure, conditions, source plate and CFU result.
template
Surface Contact
RODAC plates, swabs. CFU per 25cm². Equipment, walls, floors.
template
Personnel Monitoring
Glove fingertip, gown sampling. Five-finger dab, chest/forearm.
template
Non-Viable Particle
Particle count per cubic meter. ≥0.5µm and ≥5.0µm. Continuous or discrete.
template
Excursion
Limit exceeded. Investigation required. Links to batch impact, root cause, corrective action.
entity
Organism
Identified microorganism. Identity, method and confidence. Similarity is not proof of a reservoir.
entity
S. epidermidis
Illustrative species identity. Recurrence requires review; species similarity does not establish a source.
record
Monitoring Program
Versioned, risk-based set of locations, methods, frequencies, conditions, limits, trend rules, responses, reviewers, and effective dates.
entity
Monitoring Event
Scheduled or triggered collection with location, method, operational condition, batch, due window, actual execution, and outcome.
entity
Routine In-Operation Monitoring
Plan-derived event executed under defined operational state, method, location, timing, batch, and acceptance rules.
template
EM-0004482
In-operation Grade A viable-air collection linked to filling batch, interventions, collector, media, incubation, count, and review.
record
Investigation Monitoring
Targeted additional locations, times, methods, controls, and hypotheses created by an excursion or adverse trend.
template
Sampling Media or Device
Plate, strip, swab, sampler, counter or device with lot, qualification, status, preparation, calibration, use, and disposal.
entity
Incubation
Incubator, conditions, start, transfers, end, reads, excursions, affected samples, and assessment.
entity
Limit & Trend Rule
Effective-dated numeric, statistical, recurrence, organism, and program rule with population, exclusions, rationale, and approval.
entity
Microbial Isolate
Culture or identification result with taxonomy, confidence, source, related isolates, retained material, and investigation use.
entity
Questions and answers
Connect the monitoring plan and collection event to controlled laboratory execution: media, incubation, counts, identification and review. Shared sample identifiers retain the relationship. External interfaces need agreed ownership, mappings and verification.
Assess the interface for each source: export, API or other supported route. Verify original data, identities, units, timestamps, completeness and interruption recovery. Do not assume a vendor name means every device and format is already integrated.
No. The three observations and the 10 CFU/m3 action threshold are fictional support-area examples. Define applicable limits and alert rules against the method, area, operational state, risk assessment and governing requirements.
Configure locations and frequencies from the approved plan, with the risk rationale and effective version. Preserve the actual collection history and assess missed work. Changes need review and evidence that the program remains suitable.
A configured workflow can prepare a linked investigation with the source samples, rule and context. Review the signal and determine the required response. A generated record is not a completed investigation, established root cause or batch decision.
Chamber events need original sensor evidence and historical sample occupancy. Connect those to the stability assessment without treating a chamber alarm as a microbiological result. See the Stability Studies blueprint for the longitudinal study context.
The monitoring program defines points, schedules, collection context, rules and program review. Laboratory execution retains methods, media, incubation, calculations and reviewed results. The shared records keep those responsibilities connected.
Retain its rule version, population, period, exclusions, source observations and outcome. The example compares three successively increasing results at one point and method; it is not a statistical contamination-source model.
Keep them as explicit outcomes with reason, assessment and any replacement or follow-up work. An unread or invalid sample must not become a zero count or disappear from schedule adherence.
No. Keep species-level similarity separate from confirmed strain relationships or other source evidence. Retain method, confidence, identification version and the investigator's assessment. The example identification remains pending.
Related blueprints
Cleanroom Cleaning & Disinfection Management Software
Plan and execute cleanroom cleaning and disinfection by area and surface, control agent preparation and rotation, prove coverage and contact time, assess missed work, verify effectiveness, and govern return to use.
Biologics Cell Bank, Seed Lot & Strain Management Software
Control master and working cell banks, viral and microbial seed lots, strains, characterization, cryogenic locations, vial withdrawal, passage, suitability, and downstream manufacturing impact.
Aseptic Operator & Gowning Qualification Software
Govern aseptic roles, curricula, gowning qualifications, practical assessments, APS participation, intervention authorization, cleanroom access, personnel monitoring, observations, restrictions, requalification, and live execution eligibility.
Pharmaceutical Lyophilization & Freeze-Drying Cycle Management Software
Govern lyophilization recipes, product and load configurations, loading and stoppering, chamber readiness, source cycle data, endpoints, exceptions, unload genealogy, quality results, validation, and release.
Single-Use Systems & Assembly Lifecycle Management Software
Control single-use assembly designs, supplier components, sterilization, extractables and leachables, build and installation, connections, integrity tests, use windows, product contact, and disposition.
Pharmaceutical Process Validation & PPQ Software
Coordinate process validation in Seal, from the agreed validation basis and PPQ protocol to execution, exceptions and review. Trace each conclusion to the evidence that supports it.
See your process in Seal.
Tell us about your workflow. We’ll show you how neil and Seal can help your team.
Book a demo