Spring S6

Site scheduling for infrastructure, buildings and resources

Plan where the work is, not just when.

Spring S6 puts the programme, the cost, the risk and the crews on one live plan. Time runs across, location runs up (chainage along a corridor, or level up a building), and every team sees the same truth in the view it needs.

Six S in 50 seconds. Pick a scene, or let it run.Illustrative data

In the tool

This is the real thing.

Spring S6 time-chainage chart for a 12 kilometre highway duplication, with the date line part way through and crews shown as dots with baseline rings

Screens from the 12 km highway duplication worked example. Illustrative data, not a client programme. Read more about Site →

Better schedules, better decisions

Five scheduling mistakes, caught before they cost you.

1

Wrong or inconsistent calendars

A default calendar ignores site hours, holidays, night works, possessions and shutdown windows, so durations and dates drift from reality.

In Spring S6Named calendars with working days, hours, holidays and possessions, assigned per activity. Durations run in working days and convert to hours.CalendarsPossessionsHours/day

2

Missing or weak logic

A schedule without logic is just a list. Dangling activities and broken chains make float and the critical path wrong.

In Spring S6The health check flags activities with no predecessor or successor, breaks in the critical path and an over-use of leads, lags and non-FS links. Click an ID to jump to the fix.DCMA 1DCMA 2-4DCMA 12

3

Overuse of constraints

Forced dates distort float, hide the real critical path and make what-if analysis unreliable.

In Spring S6Every constrained activity is listed against a 5% limit, and the high-float check shows where float is a sign of missing logic rather than real slack.DCMA 5DCMA 6DCMA 7

4

Unrealistic durations

Estimated or copied durations that ignore productivity, resources and site conditions give an unrealistic finish date.

In Spring S6Durations can come from quantity and production rate over a chainage range. Long activities are flagged so they can be broken down, and resource levelling shows the finish-date cost before you apply it.RatesDCMA 8Levelling

5

Not updating the schedule

An outdated schedule is a risk. Without a current data date and baseline, forecasts and decisions lose credibility.

In Spring S6Progress updates against a data date, saved baselines and version history, with missed tasks, the Critical Path Length Index and the Baseline Execution Index tracked each update.Data dateBaselinesDCMA 11, 13, 14

All fourteen DCMA checks run on every programme, with each result linked to the activities behind it. The tool flags the problems. The planner decides what to do about them.

Where it fits

From corridors to towers.

Anywhere work moves through space and time, Spring S6 shows it on one plan. Along a corridor the axis is chainage, in a building it is the floor level, and the same logic, cost and risk sit behind both.

Rail

Possession calendars, booked commissioning possessions, track renewal by chainage and delay claims backed by the logic.

Sample: Northern Line renewal

Roads & highways

Flow-line pavement crews, night-works windows and several corridors at once, with durations driven by distance and production rate.

Sample: 12 km duplication

Mining & resources

Haul road by chainage, pit ramp, blast windows and the primary crusher on one plan, with the crews that move between them.

Sample: Eastern Ridge iron ore

Towers & apartments

Trades following each other up the building, level by level, with shared crews and cranes levelled across them and the cash position tracked as floors complete.

Sample: apartments over 6 levels

Schools, hospitals & public buildings

Fixed opening dates, staged handovers, commissioning and defects on one plan, with contract dates, liquidated damages rates and extension-of-time claims.

Sample: station accessibility upgrade

Data centres, energy & water

Long-lead plant tracked by procurement package, a constrained plan that holds work until deliveries arrive, and commissioning sequences by system.

Sample: 4 MW data centre

Fits your toolchain

Bring your programme. Take it back out.

14

DCMA schedule health checks built in and run on every programme.

2

formats read and written: P6 XER and MS Project XML.

0

installs needed. It runs in the browser and saves projects on your own machine by default.

ImportP6 XERMS Project XMLExcelCSV ExportP6 XERMS Project XMLExcelCSVPDF reports

Get started

See it on your own programme.

Send a programme or a description of the job and we will walk through it in Spring S6, with the time-location view, the cash position and the risk on your numbers.

felipe@fr2.com.au