Regulatory Thresholds

Configure RSE regulatory thresholds for VTC operators — OrganizationLicenseRule, staffing selection policies, alternate crew types (DOUBLE_CREW, RELAY_DRIVER, MULTI_DAY), and staffing cost parameters.

Overview

French VTC regulation imposes minimum fare requirements and driver welfare protections that operators must comply with. Sixième Étoile enforces these through configurable regulatory thresholds (OrganizationLicenseRule) and staffing policies that are evaluated at dispatch time.

Organization License Rules (`OrganizationLicenseRule`)

License rules define the RSE compliance parameters for your organization. They are evaluated when assigning a driver to a mission.

Field	Purpose	Allowed values	Effect
`minimumMissionFareHT`	Minimum pre-tax fare below which a mission is non-compliant	Decimal ≥ 0 (HT in euros)	Missions priced below this value generate a red RSE indicator in dispatch
`maxConsecutiveWorkHours`	Maximum consecutive hours a driver may work without rest	Decimal > 0 (e.g. `10.0`)	Driver assignments that would exceed this threshold generate a compliance warning
`minRestHoursBetweenMissions`	Minimum rest hours required between two missions	Decimal > 0 (e.g. `11.0` for TRANSFER, per regulation)	Assignments that would violate the rest period generate a compliance warning
`blockOnNonCompliance`	Whether non-compliant assignments are blocked	`true` / `false`	If `true`: red-indicator assignments cannot be confirmed without admin override. If `false`: warnings are displayed but assignment proceeds.
`warnOnAmberIndicator`	Whether amber (borderline) assignments require acknowledgement	`true` / `false`	If `true`: operator must explicitly acknowledge the borderline status before confirming

Vehicle categories should be linked to the relevant license category in Settings → Fleet → Categories. This lets predictive quotes resolve the same RSE thresholds used later in dispatch, even before a concrete vehicle is assigned.

Advanced soft levers

Epic 91 added configurable soft levers so operational policy can change without code:

Field	Practical effect
`extendedDrivingHours`	Allows a category/license rule to extend solo driving when legally permitted
`extendedDaysPerWeek`	Extends allowed working-day patterns for configured categories
`lightVehicleDerogationHours`	Bounded derogation for LIGHT categories; it never creates unlimited solo driving
`bufferTrafficPercent`	Adds a safety buffer to predicted driving/amplitude before RSE evaluation
`defaultRelaySharePercent`	Default split for relay plans, before any quote-level operator override
`relayTriggerHours`	Threshold where the engine starts considering relay as a staffing option
`amplitudeTriggerHours`	Threshold where amplitude, not only driving time, escalates staffing

Organization-wide RSE policy covers levers that are not category-specific. Category/license values take priority; the organization policy fills gaps.

Staffing Selection Policy (`staffingSelectionPolicy`)

When the system needs to suggest a driver for a mission, the staffing selection policy determines how candidates are ranked.

Value	Behavior	When to use
`PREFER_SAME_DAY_IF_POSSIBLE_THEN_MIN_EXTRA_COST`	Prefers a driver who is already scheduled for the same day (minimizing positioning dead runs), then falls back to the driver with the lowest extra cost. This is the recommended default.	Most operators — reduces empty legs and driver overtime
`MIN_EXTRA_COST`	Always selects the driver who minimizes total extra cost (fuel, positioning, overtime), regardless of whether they are already scheduled.	Cost-optimized operations where minimizing variable cost is the priority

Alternate Crew Types

When a mission requires a crew configuration beyond a single driver, operators set the crewType on the mission or dispatch assignment.

Value	Definition	When triggered
`DOUBLE_CREW`	Two drivers sharing a vehicle for a long-distance or overnight trip (RSE compliance for continuous driving limits)	Trips where one driver cannot legally complete the full route without exceeding `maxConsecutiveWorkHours`
`RELAY_DRIVER`	A second driver joins the vehicle at a designated relay point mid-route, replacing the first driver	Very long itineraries where a relay handover is more efficient than a hotel stop
`MULTI_DAY`	A single driver or crew carries out a mission spanning multiple calendar days, with overnight accommodation	Multi-day excursions, VIP tours, or extended disposals

The system suggests the required plan from the quote cockpit and persists it as a staffing plan. Operators can override the automatic recommendation in the cockpit when they accept the regulatory risk. Dispatch then receives the frozen plan instead of recalculating percentages.

Staffing Cost Parameters (from `OrganizationPricingSettings`)

These parameters feed the cost analysis for alternate crew configurations:

Parameter	Purpose	Allowed values	Effect
`hotelCostPerNight`	Accommodation cost per night per driver	Decimal ≥ 0 (default: `85.00` EUR)	Added to the mission cost side for `MULTI_DAY` and `RELAY_DRIVER` assignments requiring overnight stays
`mealCostPerDay`	Meal allowance per driver per calendar day	Decimal ≥ 0 (e.g. `17.00` EUR)	Added to the daily driver cost for each day of a multi-day mission
`secondDriverCostPerDay`	Daily cost for a second driver or relay driver	Decimal ≥ 0 (e.g. `200.00` EUR gross daily rate)	Added to the mission cost when `crewType = DOUBLE_CREW` or `RELAY_DRIVER`

RSE Compliance Indicators

Compliance results appear as color-coded indicators on the dispatch assignment panel:

Color	Meaning	Assignment blocked?
Green	Fully compliant — all thresholds satisfied	No
Amber	Borderline — below recommended but above legal minimum	No (requires acknowledgement if `warnOnAmberIndicator = true`)
Red	Non-compliant — at least one threshold violated	Yes if `blockOnNonCompliance = true`; warning only if `false`

Configuring Regulatory Thresholds

Go to Settings → Conformité RSE → Seuils réglementaires (screen N-09).
Update minimumMissionFareHT to match the current French VTC regulatory minimum (or your commercial floor, whichever is higher).
Set maxConsecutiveWorkHours (typically 10 hours for VTC in France).
Set minRestHoursBetweenMissions (typically 11 hours).
Choose staffingSelectionPolicy.
Configure blockOnNonCompliance based on your risk policy.
Update staffing cost parameters (hotelCostPerNight, mealCostPerDay, secondDriverCostPerDay).
Save. Changes take effect on all subsequent dispatch assignments.

For a quick smoke test after changing thresholds, create a quote with a long service window and check the Trip Transparency panel. The staffing cards should update immediately: solo if feasible, otherwise overnight, relay, double crew, or multi-day. The engine should always return a feasible recommendation; a quote should not become impossible solely because RSE is strict.

Practical Tips

Keep minimumMissionFareHT up to date. French VTC minimum fare regulations can change. Review this value at the start of each year and whenever legislation is updated.
Start with blockOnNonCompliance = false. During initial deployment, use warning mode (amber/red indicators displayed but assignment not blocked) to identify typical compliance patterns before enforcing blocks.
Use DOUBLE_CREW for any trip over 8 hours. A practical rule of thumb: if a mission's estimated driving time exceeds 8 hours, the system should suggest DOUBLE_CREW. Verify this matches your maxConsecutiveWorkHours setting.
Review staffing costs annually. Hotel nightly rates and per diem allowances change with inflation. Out-of-date values produce inaccurate margin analysis for multi-day missions.
Test the dispatch compliance indicators. After configuring thresholds, open the dispatch board and attempt to assign a mission below the minimum fare to verify the red indicator appears (and blocks, if blockOnNonCompliance = true).

Regulatory Thresholds

On this page