Valeur.Sectors · Mining Construction
Mining has its own engine: two routes, two methods.
The second of the four sectors whose own named engine is reached over a route. Both methods on the class are callable from outside: geotechnical baseline deviation and shaft advance loss. Both calculations resolve to a single contract clause — Sub-Clause 4.12, unforeseeable physical conditions. This page opens that clause, the two thresholds and the two formulas at the level of the code.
Every threshold below is the default in the code. Every figure on this page is either the arithmetic of a threshold or a default from the code itself: the prolongation figure is a multiple of a daily cost the caller supplies, so the money always comes out of that call’s own number.
- Ground-baseline deviation as a claim
- Sinking-rate loss as days and cost
Two methods written, both have a route.
The mining engine holds two methods and both sit behind a route — the surface of the class and the surface that ships are the same surface. The engine’s scope is narrow and sharp: two calculations, two thresholds, one contract clause. That the scope is narrow and that all of it is routed are two faces of one fact, and this page describes the whole of it, from input to output.
- Why this sector is one of the four
- Mining has an engine named after it, and a route reaches that engine today — that reach is what opened this page. The same reference record attaches a real jurisdiction branch: miningmetals, inside the industrial-process group. The record also carries the permit id and the resource-planning group,
mining_tunnel; engine, branch and group sit in one record. - What both calculations require
- Both are tied to a signed-in session: the company identity travels with every request. A call from a browser also carries the session token; a system connecting with its own key is verified by that key. Each has a budget of 60 calls a minute and the budgets are separate — running the geotechnical calculation leaves the shaft calculation’s share intact.
- Who supplies the input
- The caller supplies the whole of the input. The request body carries both the report’s baselines and the values measured on site, and the engine compares the two. The shaft calculation is the same: planned and actual advance rates, the length of the period and the daily cost all come from outside. Every number stays named in the caller’s own record.
- The scope of this page
- The two calculations, their thresholds, their shared basis, and the three actions the engine returns on every call. The sector’s reference record runs wider than that: contract types, long-lead equipment and mine types sit there too, and the long-lead equipment can be read from a separate catalog route. This page describes the engine’s scope; the whole record lives in the sector reference data.
TODAY: TWO METHODS WRITTEN · BOTH HAVE A ROUTE · TWO DEFECTS MEASURED AND ON THE PAGE
Report against ground, plan against shaft: two comparisons.
Both are comparisons. One puts the geotechnical report’s baseline against what was measured on site, the other puts the planned advance rate against the actual; if the gap crosses a threshold, the engine writes a result. Both thresholds are proportional rather than absolute — the one technical detail this page repeats, because it is also the easiest one to misread.
-
01
Geotechnical baseline deviation, on two proportional thresholds
The engine asks two things. Rock quality: has the RQD measured on site fallen below four fifths of the report’s baseline? Groundwater: has the inflow passed twice what was expected? The thresholds are 80 per cent and two times, and both scale to the report’s own number. A baseline of 70 gives 56, a baseline of 40 gives 32; those two numbers are the arithmetic of the threshold rather than the outcome of a case. The first finding is labelled HIGH and the second CRITICAL, and both are attached to Sub-Clause 4.12.
rock finding = actual_RQD < GBR_RQD × 0.8 → 'poor rock quality' · HIGH
water finding = actual_inflow > GBR_inflow × 2 → 'excessive groundwater inflow' · CRITICAL
deviation% = (GBR_RQD − actual_RQD) ÷ GBR_RQD × 100 · basis = Sub-Clause 4.12RuleInput rule: the default for the value measured on site is the report’s own baseline — when a call carries the report alone, the calculation runs on two equal numbers and the deviation reads as zero. The same rule swallows a zero. A field sent as zero also falls back to the baseline: a measured zero and a field never sent produce the same result. The thresholds work on strict inequality: a finding is written once a threshold is crossed, while exactly four fifths and exactly twice stay inside it.
-
02
Shaft advance loss, on a single division
The gap between the planned and the actual rate, multiplied by the number of days in the period, gives the outstanding depth; dividing that depth by the actual rate gives the extra days needed to close it. The extra days times the daily cost is the prolongation figure. The loss percentage is written separately and holds independent of the period: as long as the ratio of the rates holds, a 30-day and a 365-day period give the same percentage, while the extra-day count grows with the period.
extra_days = round((planned_rate − actual_rate) × period_days ÷ actual_rate, 1)
prolongation = round(extra_days × daily_cost, 2)
loss% = (planned_rate − actual_rate) ÷ planned_rate × 100 · basis = Sub-Clause 4.12 (if ground-caused)RuleTwo reading rules. The first is written into the basis field: Sub-Clause 4.12, to the extent the cause is the ground. The “reason” string that arrives with the call is carried into the output as it stands, so the causal reading travels beside the figure and stays with the person reading it. The second is the sign of the arithmetic: the extra days derive from the gap between the planned and the actual rate, so the sign of the result follows the sign of that gap — a shaft running ahead of plan yields a negative day count and a negative prolongation figure. The input is checked at the route: an actual rate at zero or below returns an explicit error, the period is validated at one day or more, and the daily cost at zero or more.
Both calculations resolve to a single clause.
There is one clause the engine writes: 4.12, unforeseeable physical conditions. The same number appears on the rock finding, on the water finding and in the shaft calculation — three places, three times. That makes it less a mining engine than a 4.12 engine. The sector’s reference record points at the same place: it ties geotechnical risk to Sub-Clause 4.12 and lists water inflow and poor rock quality as the typical surprises — exactly the two conditions the engine tests. The two files are independent of each other and say the same thing.
What the engine decides
Whether a number crosses a threshold, the percentage of the deviation, the number of days lost, and whether a finding counts as HIGH or CRITICAL. All four are arithmetic, all four follow from the numbers supplied, and the same input gives the same result every time.
What sits outside the engine
The foreseeability of the condition, the correctness of the report’s baseline, and whether the delay came from the ground or from some other cause. All three are 4.12’s real tests, and all three remain human judgments — the engine feeds them with the numbers it prepares. It builds the numerical side of a claim and hands the legal side to the person who makes it.
SUB-CLAUSE 4.12 IS WRITTEN IN THREE PLACES · ALL THREE CARRY THE SAME LABEL · THE ASSESSMENT IS HUMAN
Every answer arrives with the same three actions.
The geotechnical calculation returns an action list alongside the findings: three lines, the same three on every call. The list is fixed because what holds up a claim under 4.12 is fixed too — the notice going out in time, the geologist attending the face continuously, and the face mapping of every round being recorded. The engine returns those three together with the result, so evidence starts being gathered ahead of the finding.
- Send the Sub-Clause 4.12 notice immediately.
- Document the continuity of geologist attendance.
- Do face mapping on every round.
THE LIST IS THE SAME ON EVERY CALL · IT RETURNS EVEN WITH ZERO FINDINGS · THE LABELS ARE HARD-CODED IN TURKISH
Frequently asked
Does the engine read the geotechnical report itself?
The caller supplies the values: both the report’s baselines and what was measured on site arrive in the request body, and the engine compares the two. That is what keeps the calculation traceable — which number came from where stays named in the caller’s own record. But those numbers are also what makes a result right: called with a wrong baseline, the calculation runs correctly and returns a wrong deviation percentage. Whoever owns the input owns the result.
Why is the RQD threshold tied to the report’s own baseline number?
Because 4.12 is a deviation clause: the measure is set by the report the contract took as its baseline. The basis of a claim is “the rock was worse than the report said” rather than “the rock was bad”. The engine does the same: it treats four fifths of the supplied baseline as the threshold. A baseline of 70 gives 56, a baseline of 40 gives 32. The comparison writes a finding once the value falls below the threshold; exact equality stays inside it.
Where do the numbers printed on this page come from?
The prolongation figure is a multiple of a daily cost the caller supplies; the money comes out of that call’s own number. Any amount printed here would follow from a daily cost we chose, and a reader would take it for a result we had obtained. The 56 and the 32 above are arithmetic showing how the threshold is derived: four fifths of 70 and of 40.
If both methods have a route, what sections does this page carry?
The sections follow the class itself: every heading covers something with a counterpart inside the engine — the two calculations, their thresholds, their shared basis, and the three actions returned on every call. The engine’s scope sets the length of the page: two methods, two routes, one clause. So every detail placed beside a calculation here — the default values, the arithmetic of a threshold, who supplies the input — is a detail with a counterpart in the code. A page runs as long as the code behind it.
Let us look at your own geotechnical report
The two thresholds and the two formulas on this page can both be checked at the level of the code. If you want to see what the gap between your own geotechnical report and your site records would say in these calculations, let us walk through an example together.