What this category's data looks like
Laboratory hazardous chemicals procurement and ledger involve three types of materials: procurement applications, usage registrations, and inventory ledgers. A procurement application contains the product name, specification, quantity, supplier, application date, and approval signature; a usage registration contains the user, purpose, quantity used, date, and custodian signature; an inventory ledger contains the balance quantity, batch, inbound date, and inventory count signature. The material source is the operation records of each stage, and the update cadence is triggered by procurement, usage, and inventory count events. When entering the model access and configuration stage, the three types of materials serve as inputs for dialogue and retrieval, and are used to draft issuable drafts and handover records. The field characteristics require consistency across the four items of name, quantity, date, and signature across materials, with version numbers synchronized with issuance dates, and missing items intercepted by template validation.
Configuration and implementation checks
This stage is executed by the server-side model channel configuration, outputting model binding relationships and channel responses. "Issuable material drafts and handover records" are subsequently completed by AI nodes, code nodes, or humans. Models are divided into five categories: language, indexing, reranking, speech synthesis, and speech recognition, and different stages bind different model types.
| Object | Check | Verification action |
|---|---|---|
| Model type | Corresponds to the stage to be used | Check the type label in the model configuration, and confirm that the language model is used for drafting and the indexing model is used for retrieval |
| Channel and key | Consistent with the connected service | Check the channel configuration and key source, and confirm that the authentication parameters match the connected service |
| Model identifier | Consistent with the name listed in the documentation | Compare against the model name returned by the channel, and check whether maxContext, maxTokens, and toolChoice take effect with the binding relationship |
| Procurement application and usage registration | Fields complete, responsible person clear, version and date consistent | Check the product name, quantity, date, and signature item by item, and confirm that the same record's name and quantity match between the two materials |
Three common errors
- Symptom: The name and quantity of the same batch of hazardous chemicals do not match between the procurement application and the usage registration. Cause: The two materials were drafted separately, without checking fields against the same record.
- Symptom: The inventory ledger version was not synchronized, and the issuance date is inconsistent with the inventory count date. Cause: After the material was updated, the handover confirmation was not redone.
- Symptom: The usage registration lacks the custodian signature or receipt. Cause: The handover stage did not validate the signature item according to the template, and the missing item was not intercepted.
How to verify the setup
This feature acceptance: run one dialogue and one retrieval, check the model identifier in the response, confirm that the binding relationships of the language model and the indexing model are correct, and check whether maxContext, maxTokens, and quoteMaxToken take effect according to the configuration; record the citation count separately, and do not compare it for equality with quoteMaxToken.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are intercepted.
- In the model configuration, check the model type label and the model name returned by the channel, and confirm that the binding relationship is consistent with the connected service.
- After drafting the procurement application and usage registration, check the name, quantity, date, and signature item by item, and confirm that the version and date are consistent before handing them to the next stage for sign-off.