Building services installation and handover management system
The project team follows the checks, tests and transfer work of the installed system. The recipient sees the equipment documents, test results and defects that have not yet been removed.
Individual installation packages are marked finished, although their connection is not accepted, an automation sequence or part of another executor is required for the test. The overall launch stops or the discrepancy becomes apparent only when using the object.
How the solution works
- The installation package is linked to the valid solution and acceptance criterion.
- The executor provides the actual installed volume, alterations and evidence of hidden works when needed.
- The dependencies of other systems, contractors, and automation are verified before a joint test.
- The result is accepted or returned for correction, preserving the test conditions and repetition.
- The operator receives real configuration, settings, instructions and clearly assigned remaining tasks.
Key challenges
- Interfaces between work packages are not checked before integrated testing
- There is a lack of actual configuration and test results when transferring the system
Solution capabilities
Acceptance of the package
The actual mounted part has a version of the solution, location and specific receiving attributes.
Replacement check
The alternative used is associated with an authorized technical solution and its impact on other parts of the system.
Overall functional test
Checking the required systems interaction and operating mode, not just device activation.
Test result and validation
Conditions, result, non-conformity and its re-check are retained.
Transmitting System
The actual composition, settings, and usage and maintenance information is provided to the host manager.
Remaining seasonal work
A test carried out at a later date is subject to the condition, the person responsible and proof of completion; it is not marked as having been performed.
Business context
- Interfaces between work packages are not checked before integrated testing
- Individual installation packages are marked finished, although their connection is not accepted, an automation sequence or part of another executor is required for the test. The overall launch stops or the discrepancy becomes apparent only when using the object.
- There is a lack of actual configuration and test results when transferring the system
- Protocols, settings, instructions, and a list of failed tests are not linked to the transmitted part of the system. The operator is unaware of all limitations and cannot properly plan its use.
- The customer gets a system ready for use
- The building user needs a functioning system, clear instructions and a known contact person for maintenance. Ordered tests and transfer documents facilitate its adoption. The contractor can justify the work done and discuss further service according to the equipment actually installed.
Core features
- Acceptance of the package
- Replacement check
- Overall functional test
- Test result and validation
- Transmitting System
- Remaining seasonal work
Key integrations
- Design and Document Source
- Valid solution, adoption of the amendment and required version of the document.
- Project Work Plan
- The package, the dependency and the real change in execution were adopted.
- Test facilities and protocols
- Verification conditions, actual result and source of measurement.
- Operation Register
- Transferred composition, settings, instructions and remaining allowed tasks.
Potential impact (%)
The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.
Re-receipt work
6–25%Decreasing
This illustrative scenario assumes that 20-50% of waiting caused by missing information or unclear responsibility can be addressed. That share is assumed to fall by 30-50%. Company data is needed to verify both the addressable share and the resulting change.
An additional adjustment for an untransmitted or incorrectly linked base is measured.
Repeating the test for an unattached interface
12–42%Decreasing
This illustrative scenario assumes that 30-60% of errors can be addressed through the data and rule checks described. That share is assumed to fall by 40-70%. Company data is needed to verify both the addressable share and the resulting change.
The breaking of the tests due to a known readiness gap is calculated, separating the identified technical defect.
Part of negative feedback on job transfer information
5–20%Decreasing
Indicative assumption: 20-40% of negative reviews relate to missing system transmission information. The solution could reduce this share by 25-50%. This is a scenario of potential; assumptions need to be verified by feedback collected by the company.
When a company starts collecting reviews, negative feedback about the job transfer information is calculated from all assessments received on the topic. The same method of evaluation applies before and after installation and similar customer groups are compared. Without initial data, the actual change is not determined.
Conditional calculation scenarios. The assumptions have not been validated against client measurements.
When this solution is relevant
- Several connected systems are being installed at the site, and contractors need to coordinate their joint testing.
- When transferring an object, it is necessary to check that the instructions and equipment lists are in line with the changes made during installation.
Implementation requirements
For digital transmission, valid solutions are compatible, systems and test acceptance criteria are actually installed. Contractors and operators determine the documentation and equipment data requirements; when a BIM model is not available, the course is based on reliable drawings and device lists.
Further development options
- Common test scenarios for complementary systems based on site-specific interactions
- Automatic check of transferred devices and settings with the maintenance register