A supply-only instrumentation package and a turnkey or broader coordinated delivery scope can both be appropriate. The practical difference is not the label on the quotation; it is which activities are included, who owns each interface, what inputs are required, and what evidence will demonstrate completion.
With supply-only procurement, the agreed equipment package may be purchased while installation, commissioning, telemetry, monitoring operations or engineering review are arranged separately. A broader coordinated scope can combine more of those activities under one delivery interface, but it still needs explicit inclusions, exclusions and responsibility boundaries. One industry example lists hardware, installation services and full turnkey solutions as distinct offerings, illustrating why the package name alone is not a complete specification.1
For procurement teams, the useful question is therefore not simply “supply-only or turnkey?” It is: what work must be delivered, by whom, under which assumptions, and what will be handed over at each stage?
Supply-only vs turnkey: what changes in the scope?
The two routes mainly change how responsibilities and interfaces are packaged. They do not automatically change the technical requirements of the instruments themselves, and neither route guarantees that every project activity sits with one organisation.
Equipment supply and separately arranged services
A supply-only scope normally starts with an agreed equipment package: instruments, cables, accessories, readouts, data loggers or other items identified in the quotation. The project then needs to confirm what sits outside that package.
Those separately arranged activities may include installation, drilling or trenching, survey support, instrument protection, commissioning, baseline readings, telemetry setup, platform access, recurring monitoring, maintenance, reporting or interpretation. Some suppliers may also provide selected technical support or installation assistance without taking responsibility for the whole delivery chain.
That distinction matters because a complete box of equipment is not the same thing as a complete monitoring system. Manufacturer documentation itself treats instruments, cables, readouts and accessories as connected parts of a monitoring arrangement, and notes the role of readouts in checks before and after installation.2
A coordinated instrumentation and monitoring scope
A broader coordinated scope can combine equipment supply with selected installation, commissioning and operational services. Depending on the project, the delivery team may also coordinate specialist site activities, telemetry, monitoring platforms, reporting or ongoing support.
“Coordinated” does not mean every activity must be self-performed. Drilling, trenching, surveying and other enabling works may be provided by specialist subcontractors or other project parties. The procurement document should therefore distinguish who coordinates the activity from who physically performs it.
The same principle applies to engineering responsibilities. A wider instrumentation scope may include instrumentation planning, system configuration or data review, but final design decisions, statutory approvals and engineering certification remain separate matters unless they are expressly included and the responsible party is appropriately engaged.
| Scope area | Supply-only arrangement | Broader coordinated arrangement | What still needs to be confirmed |
|---|---|---|---|
| Equipment | Agreed instruments and accessories are supplied. | Equipment supply may be combined with other delivery activities. | Models, quantities, accepted equivalents, accessories, calibration records and delivery condition. |
| Coordination | Project team coordinates interfaces with installers, civil works, telemetry and other parties. | More interfaces may be coordinated within one agreed scope. | Named coordination owner, subcontracted activities and interfaces retained by the client or principal contractor. |
| Site work | Usually arranged separately unless specifically included. | May be included or coordinated where stated. | Access, permits, drilling, trenching, survey control, protection works and site readiness. |
| Commissioning | May be separate from equipment supply. | May be part of the coordinated scope. | Functional checks, baseline/reference information, configuration records and acceptance evidence. |
| Ongoing services | Monitoring, licences, reporting and support may be separate. | Some or all may be included for an agreed period. | Duration, subscriptions, maintenance, reporting, support boundaries, data access and close-out. |
Which delivery approach fits your project arrangements?
The decision is usually easier when the project first assesses its existing capability and the interfaces it is prepared to manage.
When the project already has installation and integration resources
Supply-only can be a practical route where the project already has a sufficiently defined technical specification and competent resources to manage the downstream work. That may include an experienced installation team, an integration owner for readers/loggers and telemetry, and a nominated person responsible for commissioning and handover records.
The key test is not whether the project can buy the equipment. It is whether the project has clear ownership of the steps after delivery. For example, if instruments arrive on site but no party owns compatibility checks, installation records, system configuration or acceptance, the apparent simplicity of supply-only procurement can create gaps later.
When a broader coordinated scope is worth evaluating
A broader scope is worth evaluating when the project wants to reduce the number of delivery interfaces it manages directly, or when several activities need to be sequenced closely. Examples include equipment supply linked to specialist installation, commissioning, telemetry setup, baseline readings, monitoring operations or reporting.
This is not a rule that larger, more complex or higher-risk projects must use turnkey delivery. Nor does a coordinated package automatically produce lower cost or faster delivery. The benefit to compare is whether combining responsibilities makes interfaces clearer for the specific project.
| Project consideration | Supply-only may suit when… | A broader coordinated scope may be worth evaluating when… | Confirm before deciding |
|---|---|---|---|
| Technical requirements | Instrument requirements and accepted equivalents are already defined. | Requirements still need integration across equipment, installation and data systems. | Who owns the technical specification and approvals? |
| Installation capability | A competent installation team is already appointed and available. | Installation needs to be packaged with equipment or specialist support. | Who provides installation method inputs, site supervision and records? |
| System integration | The project already owns loggers, telemetry, platform setup and interfaces. | Equipment and data-system integration need a single coordination point. | Compatibility, configuration responsibility, licences and testing. |
| Project coordination | The client or principal contractor can manage multiple suppliers and dependencies. | Reducing delivery interfaces would simplify programme coordination. | Which interfaces remain outside the coordinated scope? |
| Ongoing monitoring | Reading, maintenance, reporting and support responsibilities are already allocated. | The project wants selected operational services included for an agreed period. | Duration, service boundaries, support and close-out. |
What should the scope-and-responsibility matrix include?
A scope-and-responsibility matrix turns a package label into something that can be compared. The matrix should cover the work from technical inputs through installation, commissioning, operation and close-out.
For each row, use an explicit status such as included, excluded, separately priced or to be confirmed. Avoid leaving an important activity implied by context.
Instruments, accessories and system integration
Instrument procurement is more than the primary sensor. Accessories, cables, protection, junctions, portable readouts, data loggers and compatible interfaces can determine whether the supplied components form a usable system. SISGEO, for example, describes junction boxes, surge-protection components, splice kits and portable readouts as supporting parts of monitoring systems.2
For connected systems, the same matrix should identify who is responsible for logger configuration, communications hardware, platform access and data-transfer checks. Detailed requirements for transmission intervals, interruptions, alerts and data-service behaviour should sit in the remote-monitoring requirements rather than being assumed here.
Site works, access and specialist subcontractors
Site-enabling activities are a common source of scope ambiguity. The project should identify whether drilling, trenching, surveying, access equipment, traffic management, protection works or other enabling tasks are required, and then allocate responsibility for arranging and performing them.
If specialist subcontractors are involved, record both the delivery owner and the dependency. For example, an instrumentation contractor may coordinate a borehole installation while the borehole itself is drilled by a specialist subcontractor. That is different from stating that one organisation performs every activity in-house.
| Work item | Inclusion status | Delivery owner | Required inputs or dependencies | Completion evidence |
|---|---|---|---|---|
| Technical instrument schedule / accepted equivalents | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Monitoring objective, drawings/specification, expected ranges and interfaces | Agreed schedule or approved submittal |
| Instrument supply | Included / Excluded / Separately priced / To be confirmed | Nominate supplier | Final quantities, models, lead-time requirements and delivery location | Delivery records and item identification |
| Accessories, cables, connectors and protection components | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Instrument compatibility, cable routes, protection needs | Item schedule and installation/connection records |
| Portable readouts / data loggers | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Sensor compatibility, channel requirements, power and configuration | Equipment IDs, configuration record and functional check |
| Telemetry / communications hardware | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Coverage, power, communications design and compatible logger | Configuration and agreed data-transfer check |
| Monitoring platform / user access | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Licence, user roles, project configuration and data interfaces | User access and agreed acceptance check |
| Site readiness and access | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Permits, inductions, work areas, access windows and programme | Access confirmed and constraints recorded |
| Drilling, trenching, surveying or other enabling works | Included / Excluded / Separately priced / To be confirmed | Nominate coordinator and performer | Location set-out, plant access, programme and method requirements | Relevant work records / survey or installation evidence |
| Instrument installation | Included / Excluded / Separately priced / To be confirmed | Nominate installer | Approved locations, access, compatible components and site conditions | Installation records and instrument IDs |
| Commissioning / functional checks | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Installed equipment, readout/logger access, acceptance criteria | Commissioning record, exceptions and agreed sign-off |
| Baseline / reference information | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Timing, instrument condition and project reference requirements | Baseline/reference dataset and record of conditions |
| Routine readings / monitoring operations | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Monitoring period, schedule, access and data workflow | Reading/data records and agreed reporting evidence |
| Reporting / data export | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Format, frequency, recipients and review requirements | Reports/exports in agreed format |
| Maintenance / fault investigation / configuration changes | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Access, spares, support arrangement and change authority | Maintenance/change records and issue closure evidence |
| Project extension / close-out / handover | Included / Excluded / Separately priced / To be confirmed | Nominate responsible party | Completion criteria, final data requirements and continuing obligations | Final records, data export, access transfer and close-out record |
The “completion evidence” column is particularly important. It converts a scope item from an intention into something the project can check at handover.
How do you compare quotations on the same basis?
Two quotations can use similar package names while pricing materially different work. Comparison should therefore start by normalising the requested scope, not by comparing headline totals.
Equipment and initial delivery costs
First align the equipment basis. Check quantities, models, accepted equivalents, accessories and any components needed for installation, protection, reading or integration. Then identify which initial delivery activities are included: freight, mobilisation, installation, specialist site works, commissioning, configuration and initial training or handover where applicable.
A useful quotation review asks:
- Are the same quantities and measurement requirements being priced?
- Are model substitutions or accepted equivalents clearly identified?
- Are required accessories, cables, junctions, protection and readout/logger hardware included?
- Are installation and commissioning included, excluded or separately priced?
- Are mobilisation, travel, site access assumptions and additional visits defined?
- Are specialist subcontracted activities identified rather than buried in a general turnkey label?
- Are delivery dates, quotation validity and programme assumptions stated?
This does not mean every project should seek identical commercial structures. It means the evaluator should be able to explain why one total differs from another.
Ongoing costs, exclusions and programme assumptions
Initial equipment cost is only one part of the requested scope when monitoring continues after installation. Depending on the arrangement, recurring or later costs may include communications, software or platform licences, monitoring visits, maintenance, calibration, reporting, support, replacement components or project extensions.
Compare these items against the expected monitoring duration and project programme. If the programme changes, establish how extensions, additional visits, configuration changes or renewed subscriptions would be treated. Also confirm what happens to data access and exports when a subscription or monitoring period ends.
Record exclusions as carefully as inclusions. An exclusion is not necessarily a disadvantage if the project has deliberately allocated that activity elsewhere; the problem is an unrecognised gap between suppliers or work packages.
What should commissioning and handover demonstrate?
Commissioning and handover should show that the agreed equipment and system have reached the defined acceptance point. Equipment delivery alone does not demonstrate installation quality, configuration, data flow or future usability.
Equipment records and installation checks
The handover pack should identify the supplied and installed equipment and preserve the records needed to understand its configuration. Depending on the instrument and manufacturer, this may include serial numbers, calibration records, installation records, cable/connection details, baseline or reference information and applicable functional checks.
Manufacturer documentation provides examples of why these records matter. SISGEO states that portable readouts are used to check instruments before and after installation.2 Geosense Connect provides access to sensor calibration records and describes model-specific zero-reading checks through the relevant product manual.3 These examples do not create a universal commissioning procedure, but they illustrate the distinction between a sensor record and evidence that the installed arrangement functions as intended.
A calibration certificate, for example, supports traceability of the instrument. It does not by itself prove that the instrument was installed at the correct location, wired correctly, referenced properly or integrated successfully into the monitoring system.
System acceptance and handover information
For systems that include readers, loggers, telemetry or platform access, acceptance should cover the interfaces that are actually in scope. That may include checking instrument identification, units, timestamps, data arrival, user access, reporting outputs and authorised notification tests where specified.
The handover checklist can be structured as follows:
| Deliverable | What it should establish | Acceptance owner to nominate |
|---|---|---|
| Equipment schedule and IDs | What was supplied and installed | Project / technical representative |
| Applicable calibration records | Traceability for the supplied sensors | Project / technical representative |
| Installation records | Location, installation details and relevant site conditions | Project / technical representative |
| Baseline/reference information | Starting dataset and reference context where required | Responsible technical team |
| Reader/logger configuration | How the installed instruments are acquired and identified | System/integration owner |
| Data-transfer and user-access check | Whether connected-system data reaches the agreed destination and users can access it | System owner / project representative |
| Functional/acceptance checks | Whether agreed commissioning tests were completed, including exceptions | Nominated acceptance owner |
| Handover records and open items | What has been transferred and what remains unresolved | Project manager / nominated owner |
Detailed remote-monitoring acceptance requirements—such as data freshness, communications interruptions, alerts and retention—should be specified separately rather than inferred from the appearance of a dashboard.
Who remains responsible after installation?
The responsibility matrix should continue beyond commissioning. Many project gaps appear after a successful installation because operation, support or decision-making ownership was never allocated.
Monitoring operations, maintenance and support
Confirm who will take or review readings, maintain equipment, administer users, investigate faults, manage subscriptions and approve configuration changes. If reporting is required, define who prepares it, who receives it and what happens when data are missing or questionable.
Also identify the practical support boundary. A maintenance or support service may be included for an agreed period, separately priced, or retained by another party. Do not assume a turnkey installation creates unlimited support, continuous human supervision or a guaranteed response time.
If the monitoring duration extends, revisit the rows for site access, communications, licences, maintenance, reporting and equipment condition. An extension is a scope change unless the original quotation already covers it.
Engineering interpretation and project close-out
Monitoring produces measured information; engineering interpretation and project decisions are separate responsibilities. A supplier or instrumentation specialist may be engaged to support data review or interpretation, but final design decisions, certification and statutory approvals should not be assumed to transfer with the instrumentation package.
Before close-out, confirm:
- who decides that the agreed monitoring scope is complete;
- what final data, reports and configuration records are required;
- whether platform access, subscriptions or remote communications will continue;
- who retains usable exports and handover records;
- whether equipment remains in place, is retrieved or needs continuing maintenance; and
- which unresolved technical or operational obligations pass to another party.
The project should be able to close the instrumentation package without losing the records needed to understand what was installed, how it was monitored and what remains active.
What information should you include when requesting a proposal?
A useful proposal request gives suppliers enough information to identify the intended scope and expose unresolved interfaces. It does not require the project team to invent technical details that have not yet been decided.
Project requirements and available documents
Include the information that is already known and clearly mark what is provisional. Useful inputs can include:
- project location and monitoring objective;
- available specification, drawings and relevant technical requirements;
- instrument types and quantities, if already defined;
- required measurement locations or zones where already established;
- programme, installation window and expected monitoring duration;
- site access constraints and known enabling works;
- existing instruments, loggers, telemetry or monitoring platforms that need to be integrated;
- available power or communications constraints where relevant; and
- the nominated technical decision-maker or consultant for unresolved design matters.
Only provide documents that are necessary for the scope discussion. Sensitive tender or commercial material should not be requested simply because it may exist.
Requested services and unresolved scope items
For a TERRASENSE turnkey project enquiry, state which delivery activities need to be included and which remain open for discussion. For example:
- instrument selection and supply within the agreed project scope;
- installation requirements and site support;
- installation and commissioning;
- specialist site-work coordination;
- readers, loggers or telemetry integration;
- monitoring platform setup and access;
- routine readings, maintenance or reporting;
- data review or interpretation within an expressly agreed scope; and
- handover, project extension and close-out requirements.
Use the scope-and-responsibility matrix above as the attachment or discussion guide. Where a requirement is not yet known, mark it to be confirmed rather than allowing different suppliers to make different assumptions.
TERRASENSE delivers turnkey geotechnical instrumentation and monitoring solutions, with instrumentation supply included within the agreed project scope. Consultation and monitoring-strategy input can be discussed where requested as part of the relevant project scope.
Discuss Your Project with the available project information, the services you want compared, and the scope items that still need to be resolved.
Public references
-
ConeTec. Geotechnical Instrument Monitoring | ConeTec. https://www.conetec.com/services/instrumentation-monitoring/monitoring-solutions — inspected 16 September 2026. The page states that ConeTec provides hardware, installation services or full turnkey monitoring solutions. It is used only as an industry example and does not define TERRASENSE package terms.
-
SISGEO. Portable readouts. https://sisgeo.com/products/portable-readouts/ — inspected 16 September 2026. Used for the documented role of portable readouts in checks before and after installation and for examples of supporting monitoring-system accessories. Promotional safety language on the page is not relied upon.
-
Geosense. Geosense Connect: Simplify your sensor workflows. https://www.geosense.com/geoconnect/ — inspected 16 September 2026. Used for the manuscript’s Geosense Connect example concerning calibration-record access and model-specific zero-reading checks as inspected during drafting; it is not evidence of a TERRASENSE installation.