The BPV 360 approach

The person at the center.
The whole system in view.

BPV 360 is how I organize your training: understand the system, practice the task and explain the result. We connect commissioning, quality, controls, integration, energy and operations so people understand how their decisions affect the next person.

The BPV method

From understanding
to useful capability.

Start with the person and a task that matters. Train, test, verify and perform. Then revisit the lesson as the work changes. Open a step to see what happens and what you work toward.

Start with your goalWhat do you need to do, and where are you starting?

We begin with your role, the task you need to perform and what you can already explain or demonstrate. A beginner may need the language and the system map. An experienced professional may need to uncover a missed foundation or prepare for a different responsibility.

What you work toward: a specific learning goal, a starting point and clear criteria for the task.

TrainUnderstand it. Watch it. Try it with support.

We connect an unfamiliar idea to something you know, explain the reason behind it and show the task. Then you practice with guidance before trying it with less support. Drawings, stories, discussion and demonstration give you different ways into the same lesson.

EDGE: Explain, Demonstrate, Guide, Enable. This teaching sequence comes from Scouting. BPV applies it within technical learning, alongside project context, feedback and evidence.

Read The Trainer’s EDGE, Boy Scouts of America (PDF)

What you work toward: understanding you can explain and a task you have practiced.

TestTry a fresh example and explain your decisions.

You work through a new question, document or practical scenario without simply copying the demonstration. The difficulty and support match the learning goal. Your reasoning shows where the lesson has connected and where another explanation or attempt would help.

What you work toward: your own work, your explanation and an honest account of any help you needed.

VerifyCompare your work with the agreed criteria.

A trainer or mentor reviews the evidence with you: what you did, why you did it and how the result meets the task requirements. If something is missing, we identify the gap, give specific feedback and return to practice.

What you work toward: a clear view of what you demonstrated, what needs more work and your next step. A course attendance record alone does not establish capability.

PerformUse the learning in the work it was meant to support.

Apply the skill to an agreed task in a realistic exercise or appropriate project setting. Connect your decision to the people, systems and outcome it affects. Project work follows approved procedures, qualified supervision and your authorized role.

What you work toward: useful work that another person can follow, with the context and limits made clear.

Revisit & transferKeep the lesson useful when the situation changes.

Return to the skill in a different situation. Explain what still applies, what has changed and what you need to check again. Teaching the reasoning to a colleague can reveal gaps and help carry the lesson into the team.

What you work toward: a skill you can adapt, a lesson you can share and a new goal as your responsibility grows.

What makes this BPV

Practical experience.
A connected way to teach.

Marcus brings lessons from commissioning, controls, integration, energy, construction and teaching into one learning approach. These are the habits you practice along the way.

Your experience is the starting point.

We build from what you already know, whether you are entering the industry, changing careers or deepening an established specialty.

The whole system gives the details context.

Trace what your task depends on, what depends on it and who owns the next step. Then explore the depth your role needs.

Project experience becomes something you can practice.

A story introduces the lesson. An analogy helps it make sense. A task lets you apply it and test where the comparison stops being useful.

Fundamentals stay connected to requirements.

Learn the reason behind the process and find the documents that support the decision. Revisit the basics when experience has left gaps.

A person reviews the thinking behind your answer.

Questions, observation and specific feedback help reveal understanding. You get another attempt to address what you missed.

Technical work includes the people around it.

Practice explaining a finding, asking a useful question and recognizing when another discipline needs to be involved. Carry the lesson into the next situation.

Try the thinking

The screen says the pump is ON.
What does that actually prove?

Follow a small learning exercise from the goal through feedback and transfer. Use the supplied information; this example does not ask you to operate equipment.

1. Set the objective and see a guided example

Your objective: distinguish a command from feedback, explain what the evidence supports and identify the next question.

In this training scenario, cooling depends on water flowing through the equipment. The instructor traces a simple path: control command → pump response → water flow → cooling at the equipment.

Guided example: the run command is ON, motor status is OFF and no flow reading is supplied. The instructor explains why a command tells you what was requested. It does not, by itself, show what happened. You identify the missing evidence together.

2. Try a fresh example

You now have a different set of training data:

  • Run command: ON.
  • Motor status: ON.
  • Flow reading: 0 L/s. The sensor’s validity has not been checked.
  • No measured cooling result is supplied.

Which statement can you support? Choose a response to explore the feedback.

A. The motor status proves cooling is available.

The status gives you one piece of feedback. It does not establish water flow or cooling at the equipment. Trace the remaining connections and identify the evidence needed for each.

B. The pump has definitely failed.

That conclusion goes beyond the data. The readings raise a question, but they do not establish the cause. Review the meaning and reliability of each point before deciding what failed.

C. Cooling has not been demonstrated by these data.

This conclusion fits the evidence. Explain the difference between command, status and flow, note that the flow reading still needs validation, and identify the missing cooling evidence. An unanswered question is a useful finding when you can explain it.

These responses illustrate reasoning. Opening an answer is not an assessment of practical competence.

3. Review the work against four criteria

In a coached exercise, you would explain your answer and submit a short finding. A trainer reviews it against the agreed criteria:

  1. Read the evidence: distinguish command, status and measurement, including their limits.
  2. Connect the system: trace the path from pump operation to the cooling outcome.
  3. Bound the conclusion: state what the data support and what remains uncertain.
  4. Communicate the next step: record the question, identify the relevant information and name the responsible role that should investigate.

The review identifies what you demonstrated, what needs more practice and where evidence is still missing. A correct selection alone is not the complete task.

4. Use feedback, retry and transfer the lesson

Example feedback: “You recognized that the command is not proof of cooling. Now explain why the flow reading needs checking and identify the evidence you would request.”

You revise the finding, then try a new scenario. For example, a fan shows a run command and motor status, but the room still receives no measured airflow. Explain what transfers from the pump example and what is different.

The lesson you carry forward: trace the requested action, the observed response and the required outcome. Support each conclusion with evidence and know when to ask for help.

The thinking behind the method

Continue with Marcus’s original posts.

Explore the project lessons and teaching ideas behind this approach.

Connect the unfamiliar to what you know

Marcus explains how analogies and project stories give learners reference points they can recognize and use in their own work.

Read Marcus’s original post

Teach the whole system before the pieces

Start with power, cooling, controls and their dependencies. Then give each role the technical depth it needs.

Read Marcus’s original post

Build a process you can explain and verify

Revisit the fundamentals, compare understanding and ask for evidence. Experience can contain gaps worth closing.

Read Marcus’s original post

One approach, three views

Explore the ideas through the BPV graphics.

The person at the center shows how you engage with a lesson. Competency builds in cycles shows how you revisit it as responsibility grows. The experience-transfer method shows how a project lesson becomes something another person can use.

Explore the interactive graphics

Progress you can build on

Inch by inch.

“Inch by inch, life is a cinch.
Mile by mile, life is a trial.”

My mother told me this growing up. It has stayed with me, and it captures how I want to help you learn.

Marcus Myers · Founder, BPV Academy

Practice with BPV Academy Coach

You do not have to understand everything today.

You will not become an expert overnight. A class can give you a foundation, useful questions and a place to begin. Expertise grows through practice, feedback and experience over time.

Start with one idea. Explain it in your own words. Try it in a different example. Find the gap, then work on that next. You may connect with something immediately or need to revisit it over several weeks. Both are reasonable starting points.

We look for evidence of progress: what you can explain, what you can apply and where you still need support.

Take one useful step

What can you work on today?

Choose a question. You can use these prompts on your own, with a mentor or with your team.

I want it to make sense.

Pick one term from your work. Explain it without notes, using an example you already understand. Compare your explanation with a reliable source. What did you leave out?

Practice making connections
I want to know if I can use it.

Try a different example before looking at the answer. Explain your decision and the evidence behind it. A familiar answer is a starting point; applying the idea elsewhere gives you another useful check.

Work through an example
I need help finding the gap.

Bring your attempt, the point where you got stuck and the sources you checked. That gives a mentor something specific to work through with you.

Bring your question to Marcus
What happens after a one- or two-day class?

Return to the important ideas, retrieve them without notes and use them in new examples. Check the reasoning and correct mistakes. Then revisit the work after some time has passed. A packed agenda cannot tell us what you will still understand and apply later.

The amount and timing of practice depend on your starting knowledge, the task and your opportunities to use it. We agree a manageable learning plan rather than promise everyone the same finish date.

How do we make room for different learners?

We begin with what you already know and what you need to do. If an explanation does not connect, we try a different example, work through a smaller step or revisit a prerequisite. Questions help us adjust the teaching.

A regular, realistic practice habit is more useful than a promise to study every night that you cannot keep. For company programs, managers also need to protect time for practice and feedback.

How can the guidance help when Marcus is not in the room?

Keep the questions, worked examples and checklists close to the task. Use them to explain your reasoning, challenge assumptions and decide what still needs evidence. Record the question you cannot resolve so your next discussion is focused.

You can also use our written AI practice prompt to rehearse questions in a separate AI tool. Check its technical claims against authoritative sources and applicable project requirements. It does not replace instructor review or project authorization.

Try the lesson and its AI practice prompt
What support is included in my program?

Before you commit, we agree the preparation, instruction, practice, assessment and follow-up included in your program. That includes the coaching sessions or review opportunities, their timing and the period of support.

You bring your effort and questions. BPV provides the agreed teaching, feedback and next steps. Your company helps create opportunities to practice. The aim is growing independence with a clear way to ask for help.

Plan the learning and follow-up

The learning design draws on research about spaced review, recalling information, worked examples and explanatory questions. Read the Institute of Education Sciences practice guide

BPV 360: you at the center of commissioning, quality assurance and quality control, controls, integration, energy and operations. A shared outer loop connects all six subjects.

Select a subject. Follow its link into the shared 360 loop and back to you.

Select a subject to explore its connection.

Your choice updates the lesson. The guided tour changes subjects every seven seconds.

Explore a connected fundamental

Cx fundamentals

What the learner practices

Evidence of capability

Explore related training

Follow one example around the circle

A meter value becomes
an operating decision.

A plausible number on a screen is only one part of the story. Select a connection to see what the team needs to understand.

Open a topic to explore the work.

1 · Intent

Start with the decision.

What does the owner need to understand or improve? Define the measurement boundary, operating purpose and acceptance evidence.

Owner requirements → QA/QC planning and the integration scope.

2 · Quality & electrical

Know what is actually measured.

Review installation and instrument records. Confirm the meter source, equipment relationship and approved electrical verification evidence with the responsible specialists.

Installed equipment → a traceable, verified measurement.

3 · Controls

Check the path from field to controller.

Follow the value, scaling, units, update behavior and alarms. Compare the physical condition with what the controller reports.

Field measurement → control logic and a meaningful response.

4 · Division 25

Give the interface an owner.

Define who provides, maps and validates the point. Verify names, units, timestamps, quality and behavior if the connection fails.

Building automation, electrical monitoring and supervisory controls → usable information across systems.

5 · Energy

Make the information useful.

Compare reliable readings with loads, schedules and the operating baseline. Investigate a pattern before recommending an adjustment.

Trusted operating data → an informed performance decision.

6 · Ongoing commissioning

Verify the improvement. Keep learning.

Confirm the result against current facility needs. Update operating records and training, then feed the lesson into the next review.

Operating evidence → renewed requirements, quality checks and capability.

Close the circle. Operating evidence informs the next requirement, quality check, control adjustment and training need. The people and the building keep developing together.

Explore how Marcus teaches the connections

Division 25 · Master systems integration

The difficult space
between the systems?
That is part of my daily work.

Who owns the interface? Which value is correct? What should happen when communication fails? Marcus works through these questions as a practicing integrator and brings them into the learning.

Make integration something
the team can explain and prove.

  • Owner intent & Division 25: purpose, boundaries, responsibilities and acceptance.
  • Controls & automation: building automation systems (BAS), programmable logic controllers (PLCs), supervisory control and data acquisition (SCADA), sequences, alarms and equipment response.
  • Electrical Cx & metering: power paths, meter sources, instrument relationships and trustworthy records.
  • Data & systems integration: naming, mapping, units, timestamps, quality and command ownership.
  • Energy & ongoing Cx: operating baselines, investigation, optimization and verification over time.

Vendor agnostic. Follow the purpose, the interface and the evidence across manufacturers and platforms.

Talk through your integration needs

The reasoning behind the answer

Make it familiar.
Make it useful. Make it stick.

Questions reveal what someone understands and where they need more support. The next question becomes more demanding as capability develops.

WHAT?

Name the purpose.

Identify the system, the requirement and the equipment involved.

HOW?

Trace the response.

Follow the sequence, the interface and the expected behavior.

WHY?

Explain the consequence.

Connect the work to its operating purpose and what happens if it goes wrong.

WHAT IF?

Change the condition.

Predict the response and identify the evidence needed to support the answer.

Learn through connections

It’s all connected.
Let’s make it click.

Start with something familiar. Predict what happens next. Follow the connection into commissioning, controls, people and data.

Try the interactive lessons

A habit you can use today

Five questions.
A more useful answer.

Choose a drawing, finding or system you are learning. Work through the questions, then explain the result to someone who will use it next.

What?

What should happen, and which requirement or task are you trying to understand?

How?

How do the equipment, controls, information and people make that result possible?

Why?

Why does it work this way? Explain the reason, rather than repeating the instruction.

What if?

What changes if a condition, input or dependency is different? What would you check?

Who next?

Who needs your result, what do they need to know, and who owns the next decision?

Adapted from Marcus’s writing on learning the whole project. These questions support reasoning; the requirements for each task still need to be established.

The 100–500 pathway

Responsibility grows
with demonstrated capability.

A person can be advanced in one subject and developing in another. Progress follows the task, the context and the evidence.

A real question to work through

The screen says the pump is ON.
Where is the flow?

One condition. Five levels of responsibility. Select a level to see the task and the evidence.

Illustrative learning scenario. Field activity follows approved procedures, qualified supervision and the learner’s authorized scope.

Open a topic to explore the work.

100 · Orient

Explain how a command to run, reported equipment status and actual air or water flow can differ. Identify the information you need before drawing a conclusion.

Evidence of capability: A labeled map of the equipment and its control signals, with a clear question to investigate.

200 · Practice

Compare source readings with recorded trends, with coaching. Record where the observations agree and where they differ.

Evidence of capability: A reviewed record of observations and any differences.

300 · Perform

Carry out the agreed verification task within your role. Check the evidence and bring unresolved issues to the person responsible.

Evidence of capability: A finding supported by evidence and a recommended next action.

400 · Lead

Coordinate an investigation with controls specialists, mechanical specialists and operators. Clarify who does what and what evidence will show the issue is resolved.

Evidence of capability: A resolution plan with clear responsibilities and evidence of completion.

500 · Steward

Decide whether the same issue may affect other systems or sites. Improve the process and help others apply the lesson.

Evidence of capability: A reviewed process update, a teaching plan and a check that the change worked.

BPV learning levels describe development within a subject. A project’s Cx stages describe the project work and follow the owner’s terminology and criteria. Compare BPV learning levels, project stages, energy-audit levels and rating frameworks

The framework in detail

Experience becomes
something others can use.

Choose a model, then click or tap a part to see what it means, how to practice it and what progress looks like. Open the original graphic for a closer look.

The person at the center

Different ways of learning help you understand commissioning (Cx), quality, controls, integration, energy and operations. Choose a part of the inner learning circle.

The person at the center. Select its labeled parts to explore the model.

Choose a part on the graphic or below

PART 01 / 08

See

Make the work visible.

Try it
Follow a drawing or watch an instructor demonstrate a system response.
What to look for
You can point out the equipment, connections and expected response.

Think it through

A room feels warm, but the screen looks normal. What would you look at first?

Explore the reasoning

Locate the room, the displayed temperature reading and the equipment serving it. Confirm that the screen is showing information for that room before drawing a conclusion.

PART 02 / 08

Hear

Listen for the reasoning behind the action.

Try it
Hear a practitioner explain why an operating sequence or project requirement matters.
What to look for
You can explain the reason in your own words.

Think it through

An experienced operator says, “It always does that.” What would you ask?

Explore the reasoning

Ask what they observe, when it happens and why they think it happens. Their experience is a starting point for investigation, not proof by itself.

PART 03 / 08

Read

Find what the work is supposed to achieve.

Try it
Read an approved sequence of operations, drawing or project requirement.
What to look for
You can locate the requirement that supports your answer.

Think it through

The display says “normal.” Where would you find what normal should mean?

Explore the reasoning

Find the approved sequence of operations, which describes how the system should respond, and the relevant project requirements. A label on a screen does not explain the required behavior.

PART 04 / 08

Discuss

Test your understanding through questions.

Try it
Compare two explanations of why a system did not respond as expected.
What to look for
You can identify what is known and what still needs checking.

Think it through

One person suspects the sensor; another suspects the air supply. How do you move the discussion forward?

Explore the reasoning

Ask what evidence would support each explanation. Agree on what needs to be checked instead of choosing the most confident voice.

PART 05 / 08

Practice

Turn an explanation into a repeatable skill.

Try it
Work through a provided example with coaching before applying it on a project.
What to look for
You can show your steps and explain your choices.

Think it through

Before working on the live system, how could you practice the investigation?

Explore the reasoning

Use a provided drawing and sample trend data: readings recorded over time. Explain the order of your checks and get feedback on the reasoning.

PART 06 / 08

Coach

Use feedback to close a specific gap.

Try it
Review your approach with an instructor and repeat the part that needs work.
What to look for
Your next attempt addresses the feedback.

Think it through

Your first explanation misses a system connection. What should coaching change?

Explore the reasoning

Identify the missed connection, trace its effect and try the explanation again. Feedback should lead to a specific improvement.

PART 07 / 08

Reflect

Notice what changed your thinking.

Try it
Explain what surprised you and what you would do differently next time.
What to look for
You can name a lesson and where it will help.

Think it through

The sensor was reading a different location. What is the lesson?

Explore the reasoning

Confirm what each data point represents before relying on its value. Explain where else that habit will matter.

PART 08 / 08

Verify

Check understanding against evidence.

Try it
Compare your result with the stated learning goal and example criteria.
What to look for
You can show why the result meets the goal, or explain the remaining gap.

Think it through

You have a plausible explanation. Is that enough?

Explore the reasoning

Show the observations and requirements that support it, and identify anything still uncertain. Plausibility alone does not verify a result.

Competency builds in cycles

Revisit a topic in new situations as your responsibility grows. These seven stages take you from understanding the basics to practicing with guidance, demonstrating the skill and helping someone else learn.

Competency builds in cycles. Select its labeled parts to explore the model.

Choose a part on the graphic or below

PART 01 / 07

Discover

Find the starting point.

Try it
Identify what you need to do and what you already understand.
What to look for
A clear learning goal and an honest picture of the gaps.

Think it through

You have been asked to help investigate a temperature complaint. Where do you start learning?

Explore the reasoning

Clarify the task and your role. Identify what you understand about the system and where you need support.

PART 02 / 07

Learn

Build the foundation.

Try it
Learn a system’s purpose, its key terms and how it is intended to operate.
What to look for
You can explain what it does without relying on memorized phrases.

Think it through

Which basics help before you interpret temperature readings recorded over time?

Explore the reasoning

Understand what the sensor measures, where it is located and how its reading relates to the intended system operation.

PART 03 / 07

Connect

See how the parts affect each other.

Try it
Trace how a sensor reading influences a control action and an operating result.
What to look for
You can describe the cause and the expected effect.

Think it through

Why might a sensor show a normal reading while the room feels uncomfortable?

Explore the reasoning

The reading may not represent that room or the full operating conditions. Follow what was measured, how the controls responded and what happened in the room.

PART 04 / 07

Practice

Try the task with support.

Try it
Use a worked example, drawing or training scenario and get feedback.
What to look for
You can complete the steps and correct a mistake.

Think it through

How can you rehearse before making project decisions?

Explore the reasoning

Work through sample drawings and data with a coach. Explain the checks you would make without changing live equipment.

PART 05 / 07

Apply

Use the skill in the right context.

Try it
Apply the learning to an agreed project task within your authorized role.
What to look for
Your work fits the project requirements and approved procedures.

Think it through

You are ready to help on a project. What guides your work?

Explore the reasoning

Agree on the task, approved procedure, supervision and your authorized role before starting.

PART 06 / 07

Verify

Demonstrate the capability.

Try it
Compare the work and its result with agreed criteria.
What to look for
A reviewer can follow the evidence and see what remains unresolved.

Think it through

How would someone else know you can perform this task?

Explore the reasoning

They should be able to follow your work, your reasoning and the evidence against the agreed criteria.

PART 07 / 07

Retain & mentor

Keep the skill useful and help someone else learn.

Try it
Revisit the topic in a different situation and explain your reasoning to a colleague.
What to look for
You can adapt the lesson and help another person apply it.

Think it through

A colleague faces a similar complaint on a different system. What do you pass on?

Explore the reasoning

Teach the investigation method and its limits. Help them check the new context rather than reuse the old conclusion.

The experience-transfer method

A project story becomes useful when someone can understand the principle, practice the thinking and carry the lesson into their own work.

The experience-transfer method. Select its labeled parts to explore the model.

Choose a part on the graphic or below

PART 01 / 07

Experience

Start with something that happened.

Try it
Describe a project situation, the decision made and the result.
What to look for
A specific example with its context and limits.

Think it through

A project lesson starts with “the controls were wrong.” What information is missing?

Explore the reasoning

Describe the system, the expected response, the observed response and the conditions. A useful lesson starts with a specific situation.

PART 02 / 07

Principle

Explain the lesson underneath the story.

Try it
Identify why the action worked, failed or created a risk.
What to look for
A clear reason that someone else can examine.

Think it through

A data point was linked to the wrong piece of equipment. What principle carries forward?

Explore the reasoning

Confirm that the data represents the intended equipment before using it to make a decision.

PART 03 / 07

Pattern

Recognize where that lesson might apply again.

Try it
Compare another situation and identify what is similar and what is different.
What to look for
You can explain where the comparison holds and where it stops.

Think it through

Does that same lesson apply to a meter or an alarm?

Explore the reasoning

It can. Confirm the source and meaning of the data, while checking what is different about the new application.

PART 04 / 07

Practice

Give the learner a decision to work through.

Try it
Use a provided scenario to choose an approach and explain it.
What to look for
The learner shows their reasoning, not just an answer.

Think it through

How would you turn that story into a training exercise?

Explore the reasoning

Provide a drawing and a short list of control signals or readings, with one linked to the wrong equipment. Ask the learner to find the mismatch and explain how they checked it.

PART 05 / 07

Proof

Look for evidence that supports the result.

Try it
Compare the proposed approach with the requirements and available observations.
What to look for
A conclusion tied to evidence, with uncertainty made clear.

Think it through

The learner identifies the mismatch. What would make the answer convincing?

Explore the reasoning

They can trace the point to its intended equipment and show which information supports the conclusion.

PART 06 / 07

Reflection

Improve the next decision.

Try it
Review what worked, what was missed and what should change.
What to look for
A specific adjustment to carry forward.

Think it through

The mismatch was missed during the first review. What should change?

Explore the reasoning

Examine why the review missed it and add a specific check that addresses that gap.

PART 07 / 07

Transfer

Make the lesson usable by someone else.

Try it
Teach the example to a colleague, then ask them to explain how they would apply it.
What to look for
The next person can use the reasoning in their own context.

Think it through

How do you know someone can use the lesson in their own work?

Explore the reasoning

Give them a different example. Ask them to explain and apply the reasoning without simply repeating your answer.

These are learning examples. Project requirements, approved procedures and your authorized role govern the work.

Your people. Your priorities.

What should your people be able to do?

Bring the role, the project and the challenge. We will build the learning around them.

Talk to Marcus about training

Help shape BPV

What would make this
more useful to you?

Tell us what connected, where you got stuck or what is missing for your role. Your questions help identify the next lesson to develop.