Back to refinements

Phased Bid Example

Needs review

Processed 06 Jul 11:13

Procurement event draft

Review and correct every generated section before export.

Event details

Name

Type

Currency

Contract starts on

Duration months

Bidding starts at

Bidding ends at

Quantity per load

Load type

Load condition

Additional notes

Lanes

Stable route identities. Period rows reference these lane IDs.

	lane_id	origin	destination	origin_city	origin_state	origin_zip	origin_loading_type	destination_city	destination_state	destination_zip	destination_unloading_type	load_type	length_of_haul	equipment_type	mode_type	origin_dept_time	transit_time_hh_mm	dow	january	february	march	april	may	june	july	august	september	october	november	december

Periods

Edit values that vary by lane and period.

Save a phased procurement event with contract start date, duration, and lanes to generate periods.

Bid columns

	column_key	name	bid_type	description	negotiated

Computed columns

	column_key	name	scope	period	description	formula
No rows.

Services

	column_key	name	bid_type	description	negotiated

SLA

	name	type	expected_value	number_comparison_operator	presence_required	compliance_required

Review issues

Errors

Tender.contract_starts_on is required to generate phased periods
Lots must include at least one row for phased procurement events

Warnings

Tender.name is missing
Tender.currency is missing
Tender.contract_starts_on is missing
Bid sheet has January through December volume columns and a periods_columns sheet, so the procurement event was treated as phased; no Lots rows were returned because Refinery derives Lots for phased procurement events.
No contract start date, bidding start time, bidding end time, tender name, or event currency was found in the parsed workbook facts.
The parsed periods_columns sheet shows period-like IDs 1 through 11, while the Bid sheet contains 12 monthly volume columns; period dates and the missing/extra period relationship could not be validated from the workbook facts.
Bid was truncated to 200 rows for AI analysis; only nonblank lane rows visible in the parsed facts were returned.
SLA example has no obvious table region; SLA rows were taken from the structured sla sheet.
HiddenSheet was truncated to 200 rows for AI analysis and appears to contain validation lists rather than procurement event lane data.
Origin Dept. Time values were parsed as Excel date-time values on 1899-12-31 and were preserved as source workbook values on Lanes.
Bid was truncated to 200 rows for AI analysis
SLA example has no obvious table region
HiddenSheet was truncated to 200 rows for AI analysis

Processing log

Generated procurement event draft

06 Jul 11:13
Parsed 8 worksheet(s)

06 Jul 11:12
Started workbook processing

06 Jul 11:12