Project Evidence · Application Portfolios · Reference Context
Projects & Application Evidence
LINSON OIL presents project and application evidence by process route and equipment context. Each reference should be read within its documented scope rather than treated as a universal specification or performance promise.
Project capacity, process configuration, material choice, performance result, delivery scope and operating conditions remain specific to the cited project. New RFQs are engineered from their own Process Data, P&ID, Data Sheets, Technical Specifications and site requirements.
01 / Evidence Philosophy
Useful project evidence is specific, traceable and properly bounded.
Keep the Original Context
Read the stated equipment, application, process role and supply boundary together.
Do Not Generalize Project Data
A capacity, configuration or result documented for one project is not a standard guarantee for another.
Start New Engineering From New Data
New projects are clarified against their own Process Data, P&ID, Data Sheets, specifications and field conditions.
02 / Gas Processing Projects
Dehydration, stabilization and associated-gas recovery evidence.
These project pages show gas-treatment and recovery routes in their documented project context. They are useful for understanding process scope and equipment coordination, not for copying project-specific values into a new RFQ.
Shunbei Molecular Sieve Dehydration Project
Molecular-sieve dehydration skid reference including dryer, regeneration, distribution and automated-control context.
Longfengshan Condensate Stabilization Project
Condensate stabilization reference covering the documented heat-exchange, stabilization and stripping/rectification route.
Congo Associated Gas NGL / LNG Project
Associated-gas recovery and LNG project evidence with project-specific processing and supporting-system scope.
03 / Separation & Skid Project
A documented three-phase separation and modularization reference.
The He50 project provides evidence for three-phase separation, metering/export interfaces, modular skid design and factory prefabrication. Those features remain tied to that project context.
Do not infer universal skid dimensions, weight, installation time, field-work reduction or standard integration time from this reference.
04 / Oilfield Terminal & Equipment Project
Terminal-level evidence for crude oil and natural-gas processing scope.
The Wushi project demonstrates a broader terminal context involving water-bearing crude and natural gas, with documented functions including crude-oil dehydration/stabilization, LNG and LPG recovery.
Wushi Oilfield Equipment Project →Feed Context
Water-bearing crude oil and natural gas from offshore fields entering the land-terminal process context.
Documented Functions
Crude-oil dehydration and stabilization together with LNG and LPG recovery functions.
Evidence Boundary
Do not infer exact equipment lists, throughput, efficiency or project schedule unless the dedicated source supports them.
RFQ Use
Use the terminal reference to frame process scope, then define your own feed and downstream requirements separately.
05 / Composite Application Portfolios
Keep pipeline and storage evidence on their correct material route.
Composite project evidence is separated by product route because GRE line pipe, downhole tubing, tanks and liners have different structural, connection and installation requirements.
PIPELINE
GRE Pipeline Application Portfolio
Application evidence for GRE pipeline routes in water, oily wastewater and oil-service contexts.
Review evidence →STORAGE / LINER
Composite Tank & Liner Application Portfolio
Application evidence for composite storage and liner-system routes without generalizing project values.
Review evidence →06 / Artificial Lift & Produced Fluid Portfolios
Field-production evidence should stay tied to the well and process context.
These application portfolios provide evidence for artificial-lift and produced-fluid treatment routes. Model-specific stroke/load/pump data and project-specific treatment results are not generalized into universal capability.
07 / How to Read Project Evidence
Use evidence to frame technical questions, not to copy specifications.
A relevant project can show that a process route, equipment family or delivery model has been executed. Your own project still needs its own technical definition.
- 01
Match the Application
Compare process duty, fluid/service, equipment type and site context.
- 02
Match the Scope
Check what was actually supplied, integrated, inspected and delivered.
- 03
Separate Project Values
Keep capacity, dimensions, materials and performance tied to the cited project.
- 04
Submit Your Own Basis
Provide your Process Data, P&ID, Data Sheets, specifications and destination requirements.
08 / Related Capabilities & Solutions
Move from evidence review to technical definition.
Use the related hubs to move from a reference project into the required solution, equipment and execution capability.
SOLUTIONS
Process Solution Routes
Define the process problem and package route before selecting final equipment.
View solutions →CAPABILITIES
Engineering to Delivery
Review engineering, manufacturing, skid integration, QC/FAT, NDT and delivery support.
View capabilities →PRODUCTS
Equipment Portfolio
Locate the product family closest to the required equipment or package scope.
View products →Project RFQ
Send your project basis for technical clarification.
Share the evidence page you reviewed together with the Process Data, P&ID, Data Sheets, Technical Specification, operating conditions, equipment scope, inspection requirements and delivery destination for your own project.
Detailed datasheets, drawings and project-specific technical documents are prepared after the operating conditions, scope of supply and commercial basis have been sufficiently clarified.