Course 10: Assurance, Delivery, and Handover

Series · Northbank case · Glossary · References

Purpose and preparation

Assurance provides justified confidence in an identified result. It connects the requirements, produced configuration, examinations, evidence, and proposed reliance.

Delivery provides the result to its recipient. Handover transfers continuing responsibilities with the information needed to carry them.

Complete Courses 01 to 09. Bring your project basis, execution package, and technical interface account. Read Northbank Packets A, B, and C.

After this course, you can:

• Plan examination when defining the work.
• Select suitable checks, reviews, inspections, and tests.
• Limit conclusions to the evidence obtained.
• Establish commissioning and handover prerequisites.
• Transfer identified responsibilities and preserve unfinished obligations.

Lesson 1: Plan quality with the work

A final inspection cannot recover every opportunity lost during production. Some features become concealed. Some decisions need review before ordering or construction. Plan their examination while the work remains accessible.

Start from each applicable requirement. Identify its output, examination method, evidence, examiner, and decision. State the point when examination becomes necessary.

Use a coverage table:

This table proposes an examination route. It does not claim Northbank has completed the route or approved the methods.

Set independence according to the requirement and consequences. A competent producer's check and an independent review answer related but different questions. Assign the reviewer a clear purpose and sufficient context.

Allow time for correction and re-examination. A plan that schedules review immediately before an irreversible action may leave no workable response to findings.

Agree the required records with their users. Retain enough evidence to understand and challenge the conclusion. Avoid collecting forms that nobody uses.

Lesson 2: Choose examinations for the claim

Verification examines conformity to specified requirements. Validation examines fitness for intended use under relevant conditions. The same test can contribute to both when its basis supports both questions.

A calculation checks predicted behavior under its model and inputs. A review examines reasoning, assumptions, coverage, and conclusions. An inspection examines observable features. A test exercises behavior under defined conditions.

Choose a method that can answer the actual question. Reading a drawing cannot establish an installed dimension. Observing one operating condition cannot establish all operating cases.

Component checks matter. Connected behavior also needs examination. A standby pump, controller, and power system can each pass separate checks while their changeover interaction remains untested.

Define a test before treating its result as a pass:

1. Identify the governing requirement.
2. Identify the configuration and starting state.
3. State the test conditions.
4. State the justified expected behavior.
5. Identify measurement and observation methods.
6. Define the decision and finding route.

A real test plan also needs the relevant safety, access, operational, and authorization arrangements. This course prepares examination plans. It does not supply instructions to energize or operate equipment.

Protect acceptance criteria during repair. If the result fails, investigate the cause. A defective test can require correction, but that correction needs a substantive basis and the proper authority.

Changing an expected value only to obtain a pass removes the meaning of the check.

Lesson 3: Preserve the scope of evidence

Evidence belongs to an identified result, conditions, method, and observation. Retain those relationships. An unqualified statement such as “tested successfully” omits too much to support reliance.

Distinguish observation from interpretation and decision. A witness can confirm that a measurement occurred. The measurement's adequacy for acceptance remains a further question.

Read evidence in both directions. For each obligation, find the relevant result and examination. For each acceptance claim, locate its actual supporting evidence.

Record limits openly. An incomplete configuration list limits traceability. Missing test conditions limit interpretation. Unperformed scenarios leave their behavior unestablished.

A later observation does not prove earlier design gaps were resolved. It can establish observed behavior within its own scope. Resolve other gaps through evidence or a decision within the decision owner's authority. A disposition can limit reliance; it cannot establish unexamined behavior.

After a repair, assess affected evidence. A setting change can invalidate a functional test. A corrected spelling in an unrelated instruction may leave that test valid. Re-examine according to the actual relationship.

Use a finding that supports action:

• Observation and source.
• Affected requirement or claim.
• Consequence for the proposed reliance.
• Responsible owner.
• Required closure evidence or authorized disposition.

Keep unresolved findings visible until their closure basis exists. A meeting record's “closed” label does not create missing evidence.

Lesson 4: Establish commissioning readiness

Commissioning establishes readiness and behavior under defined conditions before the relevant operating handover. Its scope depends on the installation and governing arrangements.

Define prerequisites for each commissioning activity. These can include complete installation, configuration records, prerequisite checks, approved procedures, suitable instruments, competent participants, and operating coordination.

Allocate boundaries where work continues nearby. Identify what is ready, what remains under construction, and which activities can affect each other. Assess these relationships before overlapping installation and commissioning.

Build the commissioning plan from required operating activities. Include normal use and relevant abnormal or recovery behavior. Select cases through competent technical assessment.

For Northbank, C04 identifies unexercised changeover, power interruption, alarm response, and maintenance isolation. These gaps need assessment against the established requirements and operating basis.

Do not invent expected responses where the design basis leaves them open. Resolve the required behavior first. Then prepare its examination.

Arrange operators' participation where their understanding or performance matters. A commissioning team's demonstration does not establish that receiving operators understand the instructions.

Separate readiness to perform a test from readiness for operational use. A controlled examination can proceed under conditions that do not permit routine service. Define and authorize those conditions through the actual project arrangements.

The commissioning account should state completed examinations, findings, configuration, limits, and the next decision. It should permit the recipient to distinguish proven behavior from work still ahead.

Lesson 5: Deliver an identified result and responsibility

Acceptance is an authorized decision for an identified result, purpose, and conditions. A contractual acceptance, technical approval, authorization to operate, and operational handover can have different decision owners.

Base each decision on evidence suited to its stated purpose. An acceptance decision establishes its authorized disposition. It does not establish physical performance beyond the supporting evidence.

Identify those arrangements from the appointment and governing requirements. Do not infer an authority merely because someone requests a completion date.

A useful handover package identifies:

• The delivered configuration and defining records.
• The requirements and decisions governing its use.
• The relevant examination evidence.
• The applicable operating and maintenance information.
• The receiving owners and continuing obligations.
• Known limits and the means to obtain support or correction.

Check that instructions apply to the actual installation. An instruction copied from an earlier supplier submission can direct the recipient to the wrong configuration.

Confirm training, information access, maintenance arrangements, and receipt of responsibility. Placing files in a folder establishes availability. It does not establish that the receiving team can use them.

Account for residual work explicitly. Some minor work may accompany a qualified handover where the authorized conditions permit it. Required technical evidence cannot become optional through a renamed list.

A qualified handover must respect applicable duties. Risk acceptance does not supply authority to waive a duty.

State the unfinished obligation, effect on use, owner, resources, due condition, and decision. If a necessary condition remains unmet, the proposed reliance remains unsupported.

Close the project account against the actual outcome. Preserve original and amended commitments. A useful reduced result can still fall short of the original scope.

Worked Northbank example

The project engineer receives C04 Rev 0 and C05 Rev 0 in a later exercise. C04 records observed flow of 18 litres per second during one normal transfer condition.

It does not record the full hydraulic conditions. It does not establish performance across A02's unresolved operating cases. It also leaves several interactions unexercised.

The draft cover sheet claims complete acceptance. That claim exceeds the report's evidence. The team must correct the claim and establish the remaining examination and decision basis.

This table does not assert equipment failure in the untested cases. It states that the supplied evidence does not establish their behavior.

A defensible response to the sponsor is:

The supplied records do not establish complete handover. One flow observation is available, but its hydraulic conditions are incomplete. Required behavior, configuration records, applicable instructions, training, and maintenance arrangements need further work. The team will identify owners and closure evidence for each gap before proposing the applicable acceptance and receiving decisions.

A06's legal applicability inquiry also remains open in the supplied case. No course record supplies legal approval for Northbank.

Transfer example: business-system migration

A migrated database can pass a record-count check while user permissions, recovery, and reporting remain unexamined. The count provides useful evidence for one claim.

Build acceptance around the intended activities. Identify the software configuration, data state, test conditions, user participation, and recovery arrangements.

Transfer support and administration responsibility with usable instructions. Record any retained source system and unresolved obligations. Apply the organization's actual security and delivery requirements.

Practice

Use A01, A02, A06, B03, C04, and C05 with their supplied revisions.

Prepare four outputs:

1. Prepare an assurance coverage table for six identified requirements or readiness conditions.
2. Write a finding against C04's complete-acceptance claim.
3. Prepare a commissioning prerequisite list without inventing technical responses.
4. Prepare a proposed handover package and receiving-responsibility table.

Include the information needed to examine the flow observation. Identify the missing configuration and instruction relationships. State which decision each proposed record supports.

Do not execute equipment tests. This exercise develops the plan and evidence account from supplied records.

Knowledge check

1. Why must quality examination be planned before final inspection?
2. How do verification and validation ask different questions?
3. What does C04's flow observation support, and what does it leave unestablished?
4. What information binds a test result to the configuration examined?
5. Why do commissioning completion and operational handover require distinct consideration?
6. When can transferring an open obligation support a qualified handover?

Assessed assignment

Prepare Northbank's proposed assurance and handover account. Include coverage, findings, commissioning prerequisites, recipient information, responsibilities, and a sponsor recommendation.

Use these five observable criteria:

1. The coverage table connects requirements, configurations, methods, evidence, and decisions.
2. The account limits C04's conclusions to its actual observations and missing conditions.
3. The commissioning plan preserves unresolved behavior and prerequisite conditions.
4. The handover package identifies the actual recipient needs and receiving responsibilities.
5. Residual obligations retain owners, consequences, closure evidence, and required authority.

Ask a peer to act as the receiving operations lead. Repair any gap that prevents that person from understanding the proposed responsibility.

Portfolio continuation and reading

Connect your account to the Course 09 configuration and interface package. Retain C04's original observation separately from your corrected conclusion.

Carry the remaining decisions into Course 11. They will become part of the project's continuation decision and the final practicum.

Read Field Book §§6–8 and Consolidated v8 §§5.9–5.14 and chapter 6 in References. They explain evidence limits, product examination, and transfer of continuing responsibility.

The optional NASA readings deepen verification and validation methods. All core exercises can use the supplied offline records.