SYSE.24:2 - Problem

An engineering result can be obtained through many arrangements. For example, a project may adapt a System it already has, acquire a ready product and integrate it, commission a custom result, obtain continuing provider Work or access, develop the result with its own Agents, or combine several contributions. The same visible result can depend on very different conditions, such as interfaces, provider capabilities, data custody, rights, configuration evidence, support, internal capability, and recovery arrangements.

Ordinary make-or-buy tables hide these differences. Documented recurring failures include placing a purchase price beside a fully burdened internal estimate, comparing an external demonstration with an internal production configuration, omitting integration or continued-access burdens, omitting assurance, and treating contract award as if the System, access, Work, or episteme had already been accepted and used.

The opposite failure is an exhaustive procurement programme before the engineering question is clear. A project team can spend months choosing contract or tender forms while the needed result, acceptance basis, interfaces, and capability consequences remain unsettled. The first pass therefore starts from one result and stops at the smallest decision that changes the team’s next Work.