XBE recently released "Daily Recaps", a feature that provides a concise and rich summary of recent jobs delivered automatically via email.

"Daily Recaps" further reduce the effort required to stay informed about large numbers of jobs. With more information comes more answers, but also more questions!

Therefore, keep in mind these what-to-expect guidelines when reading and reacting to them:

The data might not tell the entire story, but the recap should.

Recaps quantify actual performance vs. expected performance for both production and efficiency. When there's significant variance, metrics should hint at the reason, but won't explain the root cause. You should expect incidents and recap comments to fill in the gaps. When they don't, you should ask questions.

Incidents should inspire confidence that lessons have been learned.

The primary purpose of documenting incidents is to learn lessons so that mistakes aren't repeated and opportunities are seized. It's not enough to see a proper accounting of what transpired. You should expect a breakdown of the problem and a plan for corrective action.

Additional context should explain the data, not dispute it.

You may see incidents and comments used to provide an alternative version of the recap. In most cases, this is incorrect and counterproductive. If the automated recap incorrectly explains something, then XBE will work to make improvements to handle that case. But generally, conflicting comments are a warning sign. When you see them, collaborate with the source to build a shared story.

When data is missing, a process change could create visibility.

There are recaps in which some data might be missing. For example, if a crew is dumping millings at a site without a scale or tickets, there might not be material transactions. There are solutions for all of these situations that are available right now, and we believe that adopting these solutions is usually worth the effort.

Job interactions should be carefully planned for and thoroughly explained.

Some jobs interact because they share a job site, material site, trucks, or other resources. Look out for these relationships and evidence of cross-job planning, communication, coordinated execution, and consolidated analysis.

Further analytical innovations are possible.

The analytics in the recap have been steadily refined over the last three years and are still improving. XBE is interested in adding and refining metrics, and welcomes related ideas and collaboration.

Regards,

Sean Devine
Founder & CEO, XBE