Industrial Asset Procurement Query

Problem

Operational work in industrial systems often requires pulling asset, procurement, acceptance, and app usage records from several internal APIs. Each endpoint uses different field names, enumerated values, and region parameters, so hand-writing POST requests can easily lead to missing filters, wrong pagination, or mixed province/city/county values. This skill turns those lookups into natural-language queries, useful for troubleshooting, reconciliation, and preparing data for reports.

How It Works

The skill organizes five read-only query scenarios:
- Asset information: filter by serialno, asset type, delivery state, company, project type, region, asset administrator, and time range.
- Procurement contracts: search by procurementNo, supplier, province, and status.
- Acceptance records: query by procurement number, device name, sn, device type, ownership, and province.
- Application management: locate apps by name, type, review state, state, developer ID, and online status.
- Usage logs: retrieve logs by startTime and endTime.
During a call, the skill maps user intent into JSON request bodies and includes pagination fields such as pageNo and pageSize. Requests such as “find assets in Shandong Province” or “list online applications” can be converted into filtered queries instead of full scans.

Limits

The listed endpoints use a fixed host, http://111.34.85.148:9019/..., so the caller needs network access and proper API permissions. The skill is query-oriented and does not create, approve, sign, or modify assets and contracts. Enumerated values such as deliverState, verifyState, and onlineStatus should be confirmed against backend documentation or actual responses rather than inferred from wording.