Competitor Monitoring and Key Enterprise Early Warning

The Specific Problem to Solve

In the bidding and procurement landscape, enterprises often face the challenge of fragmented information and delayed updates. How can one systematically monitor the activities of a specific target enterprise—whether a competitor, key client, or supplier? The core pain points are: numerous information channels, complex roles (Party A, Party B, agent), scattered events, and ambiguous timelines. Manual tracking is time-consuming and prone to missing critical changes, such as bid result modifications or the signing of large new contracts.

How the Skill Works: Core Capabilities and Key Steps

This skill provides a structured data query and analysis workflow to address these issues. It is not a continuously running background service, but a repeatable monitoring script.

Core Capabilities:
- Multi-Role Penetrating Search: It can search for projects involving the target enterprise from multiple dimensions, including companyName, partAName (Party A), partBName (Party B), and agentName (agency), avoiding information omissions caused by role confusion.
- Project Lifecycle Linking: Based on project numbers, it automatically links together related announcements such as bidding, Q&A, candidate announcements, awards, result changes, and contracts from the same source, constructing a complete project timeline.
- Structured Data Verification: For key projects, it calls the structured detail API to precisely verify core fields like Party A/B, bidding enterprises, amounts, and dates.
- Contract & Relationship Monitoring: Through contract search and enterprise client/supplier relationship APIs, it identifies new contracts and observes changes in cooperation networks.
- Intelligent Change Detection: It compares the current query results against baseline data (e.g., a user's previous results) to automatically mark new updates, status changes, amount variations, and new partners.

Key Execution Steps:
1. Input Collection: Define the monitoring subject (full and common name of the enterprise), roles of interest, regions, industries, time ranges, and any specific clients or competitors to focus on.
2. Multi-Dimensional Search: Call search APIs in parallel to collect lists of the target enterprise's bidding activities from different role entries.
3. Timeline Construction: For search results containing the same project number, call the getProjectByProjectNumber API to retrieve the complete sequence of announcements.
4. Detail Verification: For high-value or suspected key projects, call getZTBStructreDetail to obtain structured data for cross-verification.
5. Contract & Relationship Analysis: Call contract search and enterprise relationship APIs to supplement information about changes in the target enterprise's position within its transaction network.
6. Change Marking and Classification: Compare the results of this query with the historical baseline and classify events as High, Medium, or Low priority based on predefined rules (e.g., new award, large contract).
7. Output Report Generation: Produce a structured report containing a monitoring summary, project timelines, competitive trend analysis, and items pending confirmation.

Scope and Considerations

• Monitoring, Not Automatic Alerting: The skill is a repeatable query tool and does not guarantee automatic background execution. Each execution requires user triggering, making it suitable for regular (e.g., weekly) or on-demand checking scenarios.
• Data Dependency & Key Management: Functionality is entirely dependent on the backend API (gov-bid.com). A valid key must be provided via the environment variable BBIAO_API_KEY, and it must never be echoed in the output. The skill cannot function without a configured key.
• High Input Rigor Required: The effectiveness of monitoring heavily depends on the accuracy of input parameters. Inconsistent enterprise names, incorrect role positioning, or overly narrow time ranges can lead to biased results.
• Analysis Conclusions Need Manual Review: The skill only provides query and comparison results based on public data. Final judgments on complex competitive situations (e.g., depth of client relationships, intent behind bidding strategies) still require human analysis combined with domain knowledge.
• Compliance with Call Conventions: Must adhere to pagination limits (e.g., search list ≤ 50 items per page), deduplication rules (based on id + publishTime), and the logic for determining start times in incremental monitoring.