Source Datav1.0
RFP-Bids
RFP / bid-award relationships and amounts.
Buy by the field
35 priced fields
Pick the fields you need — priced individually below.
Whole set$2,679/mo
20% off buying every field
Pay annually · save 20% — $25,715/yr
ⓘ Take the whole set from the field list below — select everything, add it to your basket, and check out there.
RFP-Bids
rfp_bidsSource DataRFP / bid-award relationships and amounts.
Daily source stitch · data frontier 2026-08-04
9. Field reference — every column
The full field dictionary — every table, every column, with its type and meaning. One real sample row is shown per table.
supply_chain_bid_a_share
Table · pick one of 4
supply_chain_bid_a_share
18 columns · grain (primary key): id
| Column | Name | Type | Null | Description |
|---|---|---|---|---|
operation | Change-feed flag (A/U/D) | string | yes | A record-change flag marking whether this row is an add (A), an update (U), or a delete (D). In the served data, every row carries A. |
id ·PK | Record ID | string | no | A unique, auto-assigned identifier for each row, giving you a stable key to reference, de-duplicate, or track an individual line; it carries no business meaning. The grain is one row per transacting entity (the listed company itself, or one of its related parties) per month, so a single company can appear in several rows for the same month — do not treat company_id + calc_period as unique. |
calc_period | Statistics month (YYYYMM) | string | no | The calendar month whose won-tender activity is aggregated into this row, delivered as YYYYMM (e.g. 202603) and struck as a snapshot on the last day of the month. It sets the monthly time grain; the served data spans 76 months, 202001 through 202604. |
company_id | Listed-company ID (standard org code) | string | yes | 数库（ChinaScope）'s standard enterprise code for the A-share listed company whose won-tender activity this row rolls up. The code (prefix CSF) is stable across name changes, so you can track and join the company consistently across this and other 数库 datasets. The served data covers 4,972 distinct listed companies. |
company_name | Listed-company name | string | yes | The full registered Chinese corporate name of the A-share listed company whose won-tender activity this row rolls up — the human-readable label for company_id. |
stock_code | Stock code | string | yes | The listed company's 数库（ChinaScope）standard stock code, formatted local-code_exchange_security-type — e.g. 000333_SZ_EQ (Shenzhen equity), 601989_SH_EQ (Shanghai equity), 920837_BJ_EQ (Beijing equity). It pins each row to the traded stock so you can join to market and pricing data. |
related_company_id | Related company ID | string | yes | The 数库（ChinaScope）standard enterprise code of the owned entity — a subsidiary, associate, or joint venture — that actually won the tenders in this row. When it is empty (about 23% of rows) the row is the listed company's own wins; when populated (about 77%) the wins belong to that owned entity, which the graph attributes up to the listed parent. Resolved standard IDs let the entity join across the dataset. The served data covers 31,565 distinct related entities. |
related_company_name | Related company name | string | yes | The full registered Chinese name of the owned entity (subsidiary, associate, or joint venture) whose won-tender activity this row rolls up. It is empty when the row is the listed company's own wins — the human-readable label for related_company_id. |
relation_type | Ownership relation type | integer | yes | Code for the equity tie between the listed company and the owned entity (related_company_id): 1 = wholly-owned subsidiary (100% held), 2 = controlled subsidiary (50% or more held), 3 = affiliated company (20% or more held); most owned entities are 1 or 2. A fourth code, 4, also appears (about 5% of rows) but is not defined in the field dictionary — note its presence and confirm its meaning before relying on it. The field is empty when the row is the listed company's own wins. |
related_level | Ownership tier | integer | yes | The tier in the listed company's ownership tree at which the owned entity sits: 1 is an immediate (first-tier) subsidiary and higher numbers sit further down the chain (values 1–7 occur, median 2). Note this field is sparse — only about 8% of rows carry a level; the rest are empty, including many related-party rows. |
hold_ratio | Shareholding ratio | number · ratio_raw | yes | The listed company's combined direct-plus-indirect ownership stake in the owned entity, given as a decimal fraction (0.58 = 58%). Use it to weight how much of that entity's tender wins economically accrues to the parent. Most stakes fall between about 0.23 and 1.0 (median 1.0, i.e. wholly owned); a minority of rows read 0 (about 2,200 rows) or exceed 1.0 (up to 2.0), the latter arising from summing overlapping ownership paths — cap at 1.0 before using it as a weight. Empty when the row is the listed company's own wins. |
bidder_type | Winner identity (self/related) | integer | yes | Flags who won the tenders counted in this row: 1 = the listed company itself, 2 = one of its related parties. It mirrors related_company_id (empty vs populated). In the served data about 23% of rows are the listed company's own wins and about 77% are related-party wins. |
bid_count | Monthly bid-win count | integer | yes | The number of public tenders the entity (listed company or related party) won during the month — a volume measure of wins independent of contract size, counting wins whether or not their value was disclosed. It runs from 1 to 1,013 across the served data, with a median of 2 (75% of rows are 4 or fewer). |
bid_amount | Monthly bid-win value (RMB) | number · 元 | yes | The total value of the tenders won during the month, in RMB and in raw yuan (not 万 or 亿), summing only wins whose amount was publicly disclosed. Because undisclosed-value wins are excluded, it can understate true activity and reads as 0 when no amount was disclosed — about 21% of rows are 0. The median row is about 1.6 million RMB, with a long right tail (95th percentile about 238 million RMB, maximum about 715 billion RMB). |
bid_source_id | Source award-record IDs | string | yes | A comma-separated list of the award-record IDs aggregated into this monthly row, so you can drill from the summary straight to each underlying tender award in the companion detail table (supply_chain_bid_a_detail). These are the individual wins summed into bid_count and bid_amount. |
deleted | Soft-delete flag | string | yes | A soft-delete flag: N means the row is active, Y means it has been withdrawn. In the served data, every row is active (N). |
create_time | Record create timestamp | timestamp | yes | The timestamp recording when this record was first created in the dataset — a data-management field, not the tender/award date. |
update_time | Record update timestamp | timestamp | yes | The timestamp recording when this record was last updated in the dataset — a data-management field, not the tender/award date. |
Sample row:
operation: A
id: 345613
calc_period: 202604
company_id: CSF0000002710
company_name: 高新兴科技集团股份有限公司
stock_code: 300098_SZ_EQ
related_company_id: CSF0000051045
related_company_name: 高新兴创联科技股份有限公司
relation_type: 2
related_level: 1
hold_ratio: 0.835
bidder_type: 2
bid_count: 21
bid_amount: 2661512.4
bid_source_id: 224483821,224619625,224661808,224661811,224661824,224661825,224661894,224719207,22480219…
deleted: N
create_time: 2026-05-09 16:13:27
update_time: 2026-05-09 16:13:27
·
Sourced as-delivered from ChinaScope, with resolved codes and structural links computed by Numinor. Licensing passes through to you; fields are served exactly as the vendor issues them.
01
Access & FAQ
- How do I buy just a few fields?
- Check the fields you want and you'll see your running subtotal. Select every field and the whole-set price applies automatically. Add them to your basket and check out — this dataset, or fields combined across several.
- Can I evaluate these fields in the Matrix before I buy?
- Yes — load the actual source tables in the Matrix and analyze them with an AI agent (point-in-time lagged) to check the fields fit your use case before you buy. Once your selection is activated, export the fields you choose via the API.
- How is it delivered?
- Apache Parquet over a signed-URL REST API, the same pipe as Construct Data. The free Matrix sandbox serves a time-delayed view for evaluation.
- When is each update available, and how reliable is it?
- Source data refreshes on the ChinaScope cadence and is delivered through the same signed-URL pipeline as Construct Data, with the same manifest/status behaviour. Evaluate freshness yourself in the Matrix before you commit.
- Why are some fields free and others cost thousands?
- Price tracks non-replicability. Resolved codes and structural links are the moat; machine scores and raw text are cheap; identifier keys are free. Figures are priced per table; codes are charged once per dataset.
Still have questions? Contact Sales →