Process Specification and Technical Standard Q&A for Meat Products and Slaughter Processing: HTTP Interfaces and External Systems

The typical entities for this category are slaughterhouses, cooked meat and frozen prepared food enterprises. Daily documents include quarantine

What Data for This Category Looks Like

The typical entities for this category are slaughterhouses, cooked meat and frozen prepared food enterprises. Daily documents include quarantine certificates, slaughter and cutting records, ingredient marinating records, thermal processing records, cold chain temperature records, and microbial test reports. Data sources cover animal quarantine information, supplier batches, production traceability systems, temperature collection equipment, metal detection equipment, and laboratory test systems. Data is updated per batch and per shift. Cold chain temperature records are updated via continuous collection. Data fields include batch number, quarantine qualification indicator, temperature value (unit: degrees Celsius), test results, production zone indicator, and more. Strict distinction must be made between control requirements for raw and cooked raw materials.

Constraints for HTTP Interfaces and External Systems

Data is updated per batch and in real time for temperature control. Interfaces must support precise pulling of documents in a specified range using batch ID, while also compatible with high-frequency temperature data push requests. Data includes quarantine information related to biological risks and zone control fields. Interfaces must support parameterized filtering of business dimensions such as raw/cooked zones and test types, to avoid cross-category data confusion. Continuous temperature control data has real-time requirements. Interfaces must have stable response capabilities and support rapid verification of batch data. Errors can lead to risks such as raw material inflow and cross-contamination. Interfaces must include complete identity verification and error feedback mechanisms to ensure data transmission security and traceability.

Configuration Settings

This configuration is based on FastGPT v4.17.0.

Configuration ItemRecommended SettingRationale
AuthorizationBearer Enterprise-specific API KeyImplements identity verification and permission control when connecting to external systems
variables{"batch_id": "", "inspection_type": "microbial"}Passes business-specific parameters to accurately match process and test documents for the corresponding batch
Single search limitTop 8 entriesMatches core documents related to slaughter batches, avoiding redundant data interfering with Q&A results
Interface timeout setting600 secondsAdapts to full retrieval and processing time requirements for batch data
responseDataReturn only document content and match degreeFilters out irrelevant system fields, retaining only business-required process specification and standard content

Three Common Mistakes

  • A Q&A interface call returns a 401 status code. This occurs when the Authorization parameter is misconfigured, and a valid enterprise API key is not passed, causing identity verification failure.
  • Mixed retrieval response time exceeds 10 seconds. This happens when the number of documents per search is not limited, and full batch data is passed, leading to excessive retrieval load that exceeds expected response times.
  • The interface returns empty document fields. This is caused by failing to specify correct business parameters in variables, so the system cannot match slaughter records or quarantine certificates for the corresponding batch, resulting in no valid matching data being returned.

How to Verify Proper Configuration

  • Pass a valid test batch ID, and check if the documents returned by the interface include corresponding slaughter and cutting records and quarantine certificate content.
  • Simulate a push request for continuous temperature control data, and check if the interface response time meets business expectations.
  • Pass an invalid API key, and verify that the interface returns a correct identity verification failure prompt.
  • Check if the fields returned by responseData only include document content and match degree information, with no redundant system fields.

The values provided are common starting points and should be measured against the reader's own samples.