Senior judgement, built on a calculation you can repeat.

How my engine works, what it does, and what the standards say as far as I have checked them.

Three rules my engine follows.

  • Same file, same answer

    Run the same .xer twice and the engine gives the same finish dates, the same driving paths and the same ranking. No learned model and no forecast that cannot be re-derived by hand. That is what lets a sealed file be checked later.

  • Every exclusion listed

    If a record is too flawed to use, the engine leaves it out and lists it with the reason. Nothing is dropped silently.

  • Longest path, not float

    The driving path is the longest path through the logic to each facility’s finish, not a list of activities below a float threshold.

A calculated finish is based on the activities and logic in the file you send. What a seal proves, and what it does not

AllSignal’s engine calculates the finish date and driving path for each facility; the other analysis on this site is my own work, using industry-standard methods.

What my engine does.

  • Reads a P6 .xer
  • Excludes flawed records and lists each one with its reason
  • Calculates the finish date and driving path for each facility, by longest path
  • Shows shared upstream work once
  • Ranks the facilities, in a facility overview and a facility Gantt
  • Gives the same answer for the same file

What the standards say, as far as I have checked them.

How a sealed record is verifiedWhat a seal proves, and what it does not

Have the baseline reviewed before it becomes the yardstick.

Tell me about the project, the baseline and when it is due to be submitted or accepted.

I reply within two working days. How I handle your files.