About concept, feed and detailed engineering
Concept engineering defines and compares project approaches, FEED develops a selected design basis and detailed engineering produces specified construction or procurement deliverables. Each stage has different inputs and maturity requirements.
Where the service is used
New projects, modifications and equipment packages use discipline-specific or integrated engineering support. Scope depends on the project stage and existing design information.
Service options and scope
Specify deliverable lists, disciplines, design responsibility and review process. Procurement support and site services should be identified separately.
Project basis and stage
The specification should establish a clear baseline for technical review. Record the required characteristics using the current design documents and identify any mandatory limits. If an input is provisional, label it as an assumption so the reviewer can explain its effect on the proposed solution. For existing assets, compare the current duty with the original design basis. Changes in conditions, interfaces or project requirements can mean that a previously accepted configuration needs a fresh compatibility assessment before it is purchased or used again.
Existing drawings and data
Physical interfaces determine whether an item can be integrated into the installation. Drawings should identify the relevant dimensions, mating connections, access limits and drawing revision. Nominal sizes do not always describe actual clearances or connection geometry, so include the governing dimensional reference where available. For replacements, photographs can help identify the assembly, but an approved drawing or exact part reference is preferable for critical interfaces. Record any installation constraints that could affect assembly, maintenance access or the scope of associated fittings and supports.
Discipline and deliverable list
A clear scope describes the intended result and the responsibilities of the parties involved. List the required deliverables and identify which design or operating decisions have already been made. Separate investigation, engineering, supply, installation and acceptance activities where they are different work packages. State the review process and the information that will be provided by the buyer or operator. This allows proposals to address the same work and makes omissions or additional services visible before a commitment is made.
Design responsibility and review process
Document how this requirement connects to the rest of the installation or work package. A component may meet its own description while still needing additional equipment, a different interface or specialist integration to perform the intended function. Identify who will verify the proposed arrangement and which records are required for that review. Where a supplier suggests an alternative, its differences should be explained against the specified basis. This supports a technical comparison before commercial approval and makes the final scope easier to understand.
How related requirements differ
Process safety and reliability studies: Process-safety studies examine defined hazards and protective arrangements, while reliability studies evaluate specified performance and availability questions. Their methods and deliverables depend on the project's decision needs. Define study boundaries, methodology, participants and outputs. Action closeout and engineering implementation are separate responsibilities unless included.
Automation integration and commissioning: Automation integration connects control functions, interfaces and software within a defined system architecture. Commissioning verifies specified functions and supports the agreed transition to operation. Define functionality, interfaces, tests and handover records. Hardware supply, licensing, programming and site support should have separate boundaries.
Industrial software licensing and support: Industrial software licensing grants defined usage rights to named software products. Support services address specified assistance or maintenance needs. License procurement, implementation and specialist engineering are distinct commercial scopes. Specify edition, users, duration and license model. Entitlements, renewal terms and support obligations should be explicit without sharing activation keys or credentials.
Compare the complete service proposal
For concept, feed and detailed engineering, compare the stated work, personnel, equipment and deliverables before comparing the headline price. A proposal may exclude preparation, access equipment, consumables, standby time or completion documentation. Identify these boundaries in the same way for each offer. The project location and work window should be explicit, together with the required qualifications for the particular assignment. Oillinko receives the enquiry and coordinates clarification with you; the actual service arrangement and the suitability of the proposed specialist are reviewed for the project.
Questions before requesting a quotation
What information should be available first? Start with the intended application and the current technical specification for concept, feed and detailed engineering. In this category, the initial review includes project basis and stage, existing drawings and data, discipline and deliverable list, design responsibility and review process. Attach the relevant drawings or scope documents and identify any information still awaiting confirmation. This makes it possible to distinguish a preliminary enquiry from a fully defined purchasing or service requirement.
Does a service listing confirm that a contractor is already appointed? No. The listing describes a scope that can be submitted to Oillinko for review. The proposed specialist, location coverage, qualifications, work boundaries and commercial terms are checked for the actual enquiry. Equipment rental, personnel and complete execution should not be assumed to be included together unless the proposal expressly states that scope.