mart_mdt_pipeline

certified

mart table

Where MDT proposals sit by entity, region, study type, and status over time.

Definition

The proposal pipeline rollup for the medical-device testing-services domain. Each row is one (issued_month × entity × client_region × study_type × proposal_status) bucket carrying the proposal count, the summed base ROM (ex-VAT ex-contingency), and the average request→issued cycle time. issued_month is the month the proposal was issued, so this is a trend surface. Proposals without an issued_date (drafts / ROM-only quotes) drop out of the issued-month grain.

Watch out for

highTreating total_rom_sum as won/booked revenue
total_rom_sum sums the base ROM across every proposal in the bucket regardless of status — issued, draft, won, lost. It is quoted-pipeline value, not realised revenue. Filter status='won' before reading it as booked.
mediumReading a single month as the whole pipeline
The grain is issued_month; sum across the relevant range rather than reading one month in isolation.

Questions this answers

“What is the MDT proposal pipeline value by study type this year?”
“How many proposals were issued per month by entity?”

8 of 8

Column

Type

Description

Tests · PII

issued_month

Date

First day of the month the proposal was issued. Sort/partition key.

1 test

entity

String

Issuing Smithers legal entity (or 'unknown').

1 test

client_region

String

Client region (or 'unknown').

1 test

study_type

String

Study type (or 'unknown').

1 test

proposal_status

String

Proposal lifecycle status (or 'unknown').

1 test

proposal_count

UInt64

Count of proposals in the bucket.

1 test

total_rom_sum

Nullable(Decimal(38, 2))

Summed base ROM across proposals in the bucket. Confidential-commercial aggregate.

avg_cycle_time_days

Nullable(Float64)

Mean request→issued cycle time (days) across the bucket.