Net Space as a Technical Reference Framework: Foundation for Parallel Engineering

Net space is often treated in projects as a drawing milestone that must be completed before subsequent steps can begin. In day-to-day shipyard practice, this approach tends to create tension once multiple disciplines start working in parallel.

Net space is the defined, discipline-aligned allocation of available volume within a vessel, used as a technical reference to manage interfaces, space claims, and parallel engineering activities.

Within Basic Engineering, net space functions more effectively as a shared technical reference framework. It provides guidance for space allocation, makes interfaces visible, and allows disciplines to move forward without blocking each other later in the process. This requires clear agreements and an integrated approach from the outset.

Within HOFF’s Basic Engineering approach, net space is applied as an integrated coordination framework rather than a standalone deliverable, with a focus on coherence, buildability, and progress.

 

Net Space as a Workable Starting Point in the Early Phase

In the early project phase, many parameters are still under development. Equipment is indicative, system choices progress in parallel, and the structural setup is defined step by step. Nevertheless, volumes must be allocated to keep engineering moving.

In this phase, net space provides direction by defining:

  • available space per discipline

  • spatial boundaries between systems, structure, and outfit

  • zones with fixed assumptions and zones with conditional space

Within HOFF’s working method, this distinction is explicitly recorded. This keeps it clear where flexibility exists and where it does not, while allowing disciplines to continue their work within clear boundaries.

A clearly defined early net space framework allows engineering to progress despite incomplete input, without masking where assumptions still apply.

Space Claims and Interfaces as Determining Factors for Pace

Project delays rarely originate from a single discipline in isolation. In almost all cases, the cause lies at interfaces where space claims converge. Examples include routing through structural zones, maintenance access around mechanical systems, or outfit elements that later require more space.

When these space claims are not aligned early, conflicts only become visible when models are combined. This moment often occurs late in the Basic Engineering phase or even during detail engineering.

By setting up net space integrally and explicitly discussing space claims, insight is created before conflicts begin to affect planning and buildability. Within HOFF, this is a fixed component of the Basic Engineering approach.

Most schedule pressure originates at unaligned interfaces, not within individual disciplines.

Net Space as a Multidisciplinary Reference Framework

Effective net space does not merely describe dimensions, but primarily the relationships between disciplines. It makes visible where interfaces are located and which discipline claims which space.

For that reason, within integrated Basic Engineering, net space is not developed per discipline but coordinated jointly. Structure, piping, mechanical, and outfit are reviewed in relation to each other, with attention to dependencies and future follow-up steps.

This working method results in:

  • consistent space allocation

  • explicit interfaces

  • a shared technical basis for all involved disciplines

Net space only functions as a reference framework when it is defined and maintained across disciplines.

 

Parallel Working Within a Stable Framework

When net space is used as a reference framework, disciplines can continue working simultaneously. Routing can take place within known zones, systems receive realistic envelopes, and structural choices take installations and accessibility into account.

Essential in this process is that the status of the net space framework remains clear. Within HOFF, the following is recorded:

  • which parts are confirmed

  • which parts are conditional

  • which assumptions underlie the space allocation

This keeps provisional choices recognizable and manageable in later phases.

A stable but transparent net space framework enables parallel engineering without losing control over assumptions.

 

Integrated Basic Engineering as the Foundation

Net space loses its value when Basic Engineering is executed in a fragmented way. Local optimization then leads to conflicts that only become visible once the project has already progressed further.

Integrated Basic Engineering ensures that space allocation, system choices, and interfaces align logically. Within HOFF, net space is therefore not a standalone deliverable, but a logical result of a coherent engineering approach.

Net space forms a shared language between disciplines. By using it as a technical reference framework, room is created to work in parallel, maintain momentum, and control conflicts at an early stage.

Net space becomes effective only when it emerges from integrated Basic Engineering rather than isolated discipline decisions.