What this category's data looks like
This page addresses university laboratory safety grading and classification, involving three types of materials: the laboratory grading and classification table, the hazard source list, and the safety responsibility statement. The grading and classification table fields include laboratory name, room number, hazard level, grading basis, and date; the hazard source list fields include hazard source name, category, quantity, storage location, and responsible person; the safety responsibility statement fields include responsible entity, signature, and receipt date. When these three types of materials enter the scheduled tasks and automation function, the grading and classification table serves as the main record, the hazard source list serves as its attached details, and the safety responsibility statement serves as the confirmation voucher. The update rhythm is triggered by semester or rectification cycle, and is executed or rerun per record by trigger configuration and tool nodes, ensuring the current version is unique, old versions are traceable, and references are synchronized.
Configuration and implementation checks
This step is executed by trigger configuration and tool nodes (scheduling capability is not in the tool introduction), outputting trigger records and execution results. The "version ledger and change records" are then completed by business processing executed or rerun per record. Tool invocation is decided by the model based on the tool introduction whether to execute; when the model does not need to summarize again, a tool invocation termination node can be connected at the end of the tool to end this invocation.
| Object | Check | Verification action |
|---|---|---|
| Laboratory grading and classification table | Fields include laboratory name, room number, hazard level, grading basis, and date, and the signature column is complete | Check the grading and classification table fields and dates, and confirm the current version is unique |
| Hazard source list | Fields include hazard source name, category, quantity, storage location, and responsible person, and are consistent with the name, quantity, and date in the grading and classification table | Check whether the name, quantity, and date in the hazard source list and the grading and classification table match |
| Safety responsibility statement | Fields include responsible entity, signature, and receipt date; missing signature or receipt is considered incomplete | Check the signature and receipt date of the safety responsibility statement, and confirm references are synchronized |
| Version ledger and change records | Records the current version number, old versions are traceable, and references are synchronously updated | After changing one piece of content, check whether the version number and references are synchronously updated |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the grading and classification table and the hazard source list. Cause: The two materials are maintained separately, and field alignment and cross-checking were not performed during updates.
- Phenomenon: The version is not synchronized, and the old version is still referenced. Cause: The update only changed one piece of content and did not trigger synchronous updates of the version number and references; the old version is traceable but not marked as invalid.
- Phenomenon: The safety responsibility statement lacks a signature or receipt. Cause: When the material entered the process, the signature column and receipt date were not validated, so the confirmation voucher is incomplete.
How to verify the setup
This function's acceptance: check the trigger records and execution time to confirm execution occurs on time and only once; check the tool introduction fields and where the termination node is connected to confirm that when no summary is needed, it is connected at the end of the tool.
Business test: change one piece of content and see whether the version number and references are synchronously updated.
- Check the process connections and trigger records to confirm the trigger is connected to the corresponding tool node, executes on time, and executes only once.
- Check the introduction fields, termination node position, and version ledger to confirm old versions are traceable, references are synchronized, and signatures and receipts are complete.