Three variants in one comparison
The shortened variant lasts 6 weeks in three stages of 2 weeks each. Stage one is the server and the map, stage two is training and permits, stage three is the gatehouses and the start. Each stage ends with an acceptance.
The two-stage variant lasts about 2 months: two blocks of 4 weeks, with acceptance and production go-live at the end. The three-stage variant spreads the work over three months, and each month ends with a result that can be seen: a working training module and an instance with the map, then an issued and accepted test permit with documentation, and finally tests on the live traffic of external contractors and production go-live.
- 6 weeks: 3 stages of 2 weeks, shortest time, fastest decision pace
- about 2 months: 2 stages of 4 weeks, 2 acceptances
- about 3 months: 3 monthly stages, most time for tests with contractors
Recommendation 1: administrator availability sets the variant
At least 2 administrators are required, one per site, together with a weekly 10-15 minute huddle. In the 6-week variant decisions must be made at the pace of one every few days, because the stages last 2 weeks each.
If administrators are busy with current work, choose the longer variant. A slower schedule with deadlines kept is better than a fast one in which the acceptances keep moving.
Duration of schedule variants
Recommendation 2: choose 6 weeks when the scope is ready
The shortened variant works when the plant already has its location naming and knows who is responsible for each area. In the first stage a separate server, accounts and permissions are created, teams responsible for areas are set up, and about 500 locations are named according to the plant's convention.
Stage two ends with a passed test training and an issued test permit with a PDF printout. In this stage up to 80 risks and hazards with protective measures are prepared, together with 2 printout templates. If the plant has such data in its spreadsheets, the pace is realistic.
Recommendation 3: choose 2 stages when there are two sites
Two stages of 4 weeks suit a plant with two sites and one administrator per site. The first stage builds the shared training and terms, the second launches permits and gates.
The payment in this variant is 50% at the order and 50% after production go-live, so the second acceptance carries financial weight for both sides.
Recommendation 4: choose 3 stages when tests with contractors matter
The three-stage variant gives time for tests on the live traffic of external contractors before production go-live. It is a sensible choice when there are many contractors, when they speak several languages, or when the plant wants to start with a narrow group of suppliers.
Each month ends with an acceptable result, so management sees progress on monthly dates, not only at the end.
Recommendation 5: always set the acceptance mode in advance
Whatever the variant, write down what the result of each stage is and who accepts it. We describe stage acceptance as a formal activity on a separate page with good practices. Thanks to it, production go-live does not return to corrections.
Video
Frequently asked questions
Does the 6-week variant include acceptances?
Yes. Each of the three 2-week stages ends with an acceptance: server and map, training and permits, gatehouses and start.
How many administrators does a plant need?
At least 2, one per site, together with a weekly huddle lasting about 10-15 minutes.
When is it worth choosing three monthly stages?
When the plant wants to test the system on the live traffic of external contractors before production go-live and needs a visible result every month.
Let us match the schedule to your team
Tell us the number of sites and administrators, and we will propose a variant with acceptance dates.
Let's talk