Tiza Group

Home / Guides / Testing, commissioning and faults

How Long a Coordination Study Takes and What Delays It

What the schedule of a coordination study depends on: stages, number of devices and waits for data, with a worked example in weeks.

By Shadai García, CEO and protection engineer at Tiza Group.

five stages, from data to reviewDataModelCoordinationReportReviewown work and waiting are counted separatelywork hours ÷ 6 h per day = business daysbusiness days (9 px per day); thick bar: work, thin: waitingbaseline: 25 devices, 97.5 h16.25 + 5 + 5 = 26.25 days = 5.25 weeksdata late: 10 days more36.25 days = 7.25 weeks (+38 %)50 devices, 135 h32.5 days = 6.5 weeksdouble the equipment adds 1.25 weeks, not doubleChainDataCalculationReportReview© tizagrp.comfive stages, from data to reviewDataModelCoordinationReportReviewown work and waiting are counted separatelywork hours ÷ 6 h per day = business daysbusiness days (9 px per day); thick bar: work, thin: waitingbaseline: 25 devices, 97.5 h16.25 + 5 + 5 = 26.25 days = 5.25 weeksdata late: 10 days more36.25 days = 7.25 weeks (+38 %)50 devices, 135 h32.5 days = 6.5 weeksdouble the equipment adds 1.25 weeks, not doubleChainDataCalculationReportReview© tizagrp.com
Duration of a coordination study: stages and schedule of three cases, baseline, with late data and with double the devices. Location in the system and operating principle. Illustrative: real values come from the nameplate and the manufacturer's manual.
Short answer

The schedule of a coordination study does not depend only on its size: it depends on the number of devices to set, on when the data arrives and on how long the client's review takes. It separates engineering work from the waits, shows with an example how to go from work hours to calendar weeks and lists what delays the most so it can be avoided when hiring.

Short answer

The schedule of a coordination study is built from three parts: engineering work (collecting and validating data, modeling, calculating, setting and writing), the waits for data that does not arrive and the client’s review. Engineering work grows with the number of devices to set; the waits depend on how the data is requested; the review, on who does it and with what deadline. When they are separated, you can go from hours to calendar weeks, as in the example. The figures in that example are assumed; they serve for the method, not as a schedule promise. To know what the price depends on, see how much a coordination study costs.

The stages of the study

  1. Data: requested, received and validated. It is the most uncertain stage, because it depends on third parties.
  2. Model and short circuit: the network model is built and the maximum and minimum currents are calculated at each point. See how short circuit is calculated in a plant.
  3. Coordination: the device curves are set from the load toward the source, with the procedure in coordination step by step. It is the stage that grows the most with size.
  4. Report and setting sheets: the results, curves and settings for each relay are documented.
  5. Client review: the results are read, questions are asked and the work is approved or changes are requested.

What each stage depends on

StageWhat lengthens it
DataOutdated single-line diagram, settings missing in file form, grid operator short circuit pending
ModelMany buses and several operating scenarios
CoordinationNumber of devices, number of scenarios and manufacturer curves not available
ReportNumber of relays, format required by the grid operator
ReviewSeveral reviewers, late comments and scope changes

A study with the same amount of equipment can take twice as long if the data arrives late. To see which data is worth having before starting, see what a coordination study needs.

What delays it

  • Data that arrives in pieces. Each late datum forces calculations already done to be taken up again.
  • Outdated single-line diagram. It is discovered when comparing with the site and the model is redone.
  • Grid operator short circuit with no date. Without it, the setting of the relays at the connection point cannot be closed.
  • Scope changes. Adding a substation or a scenario midway restarts stages.
  • Review with no deadline. A review that takes weeks freezes the closing.
  • Existing settings still to be collected. If someone has to go to the site to download the settings, the schedule depends on getting the permit and the window.

How to go from hours to weeks

Engineering work is measured in hours; the calendar counts the waits. A simple calculation:

  1. Add up the hours of engineering work for stages 1 to 4.
  2. Divide them by the effective hours per day of whoever does it (for example 6 h, because the rest goes to meetings and email): this gives working days of work.
  3. Add the days of waiting for data that cannot overlap with work.
  4. Add the days of the client’s review.
  5. Divide by 5: this gives weeks.

Worked example

Example data (assumed): a study of 25 devices. Hours of engineering work: data collection and validation 16 h; model and short circuit 24 h; coordination 1.5 h per device; report and setting sheets 20 h. Effective hours per day: 6. Data wait that does not overlap: 5 working days. Client review: 5 working days.

  1. Coordination hours: 25 × 1.5 = 37.5 h.
  2. Total own work: 16 + 24 + 37.5 + 20 = 97.5 h.
  3. Working days: 97.5 / 6 = 16.25 working days.
  4. Plus waits: 16.25 + 5 + 5 = 26.25 working days.
  5. Weeks: 26.25 / 5 = 5.25 weeks.

Variant A: data is missing for 10 more working days. Engineering work does not change, but the wait rises to 15 days: 16.25 + 15 + 5 = 36.25 working days, that is, 7.25 weeks. The increase is 10 / 26.25 = 38 % from the data alone.

Variant B: 50 devices with the other times equal. Coordination goes to 50 × 1.5 = 75 h, own work to 16 + 24 + 75 + 20 = 135 h, working days to 135 / 6 = 22.5 and the total to 22.5 + 5 + 5 = 32.5 working days, that is, 6.5 weeks. Doubling the number of devices adds 1.25 weeks, not double, because the data, the model and the report do not double. In a real case the model and the report also grow with size; the example keeps them fixed to isolate the effect.

What is delivered at the close of each stage

A useful schedule has one deliverable per stage, because that shows progress and what is missing:

  • Data: request list with the status of each datum and the agreed assumptions.
  • Model and short circuit: table of maximum and minimum currents per bus, with the scenario of each.
  • Coordination: curves per level and list of proposed settings for each device.
  • Report and setting sheets: study report and one sheet per relay.
  • Review: minutes with the client’s comments and the response to them.

If a stage has no deliverable, there is no way to know whether it is finished, and that is where a schedule slips without anyone seeing it.

How to shorten the schedule when hiring

  • Deliver the critical data complete on the first day and ask for confirmation of receipt.
  • Name a person on the client side who answers questions within 48 hours.
  • Agree in writing on the review time and who does it.
  • Close the scope before starting: which substations, which scenarios, which deliverables.
  • Ask the grid operator for the short circuit from the day of contracting, not when the study needs it.
  • Define whether the study includes loading and testing the settings, because that part has its own schedule.

Frequent mistakes

  • Asking for a schedule without having defined the number of devices or the scenarios.
  • Counting only work hours and forgetting the waits.
  • Starting without the critical data «to save time» and redoing what was calculated later.
  • Accepting a very short schedule achieved by cutting verification.
  • Leaving no review time in the schedule.

Checklist

  • Number of devices and scenarios agreed.
  • Critical data delivered complete at the start, with receipt acknowledged.
  • Client contact person named, with an agreed response time.
  • Date requested from the grid operator for the short circuit.
  • Client review time written into the schedule.
  • Scope changes agreed with their effect on the schedule.
  • Scope of relay setting and testing defined separately, with its own schedule.

References

  • The stages, hours and schedules in the example are assumed; they are not market or standard figures.

Need this study?

We agree the schedule of your coordination study according to the scope and the available data, as part of our protection coordination work, for projects in any country. Write to us.

Frequently asked questions

How many weeks does a coordination study take?

There is no single figure; it is calculated with the method in the guide from the devices, the waits and the review. The example, with assumed data, shows how to go from hours to calendar weeks. The real schedule is agreed with the scope.

What delays a study the most?

Almost always the data: the outdated single-line diagram, the grid operator's short circuit that does not arrive or the existing settings that have to be collected on site. Next come scope changes midway and reviews that take longer than planned.

Can the schedule be shortened?

In part. It is shortened by delivering the critical data complete at the start, naming a person who answers questions and agreeing in writing on the time of each review. What is not advisable is cutting the calculation and verification stages: that is where the costly errors are made.

WhatsApp