Understand how OS-LPU and OS-CIC organize consulting engineering demands with scope, deliverables, measurement, acceptance criteria, and document traceability.
Check it out!
In consulting engineering contracts, one of the greatest challenges is turning technical demands into clear, measurable, and traceable requests.
An organization may need proposal analysis, document review, a technical opinion, a risk matrix, procurement support, commissioning, deliverable validation, or recurring decision support. Without a method, these requests accumulate across emails, meetings, messages, and informal alignments.
It is in this context that A3A uses the concepts of OS-LPU and OS-CIC.
OS-LPU is a Service Order linked to an LPU — Unit Price List item. It is intended for specific, bounded, and measurable demands.
OS-CIC is a Service Order linked to an Integrated Engineering Services Cycle. It is intended for demands composed of several interdependent activities, with stages, deliverables, and consolidated acceptance criteria.
These concepts are part of the methodology presented in the Complete Guide to Consulting Engineering and in the whitepaper Consulting Engineering Contracting with Traceability, Governance, and Cost Engineering.
Why service orders matter in consulting engineering
The Service Order is the instrument that turns a demand into a formal request.
In consulting engineering, it should record the objective, context, scope, assumptions, limitations, deliverables, schedule, measurement criterion, and acceptance criterion.
Without a well-structured Service Order, contracting tends to depend on informal interpretations. This increases the risk of rework, expectation gaps, disputes over hours, lack of evidence, and subjective acceptance.
The Service Order should not be merely an administrative form. It should function as the technical record of the demand.
Relationship between HTE, LPU, and Service Order
OS-LPU and OS-CIC are directly connected to the HTE — Consulting Technical Hour and the LPU in Consulting Engineering Services.
HTE represents equivalent consulting technical effort. LPU organizes services, reference units, and contracting criteria. The Service Order formalizes the demand by linking scope, deliverable, schedule, and acceptance.
Together, these elements create a governance structure:
| Element | Function |
| HTE | Represent equivalent consulting technical effort |
| LPU | Organize services, units, and contracting references |
| OS-LPU | Formalize a specific demand linked to the LPU |
| OS-CIC | Formalize an integrated engineering cycle |
| Deliverable-based measurement | Verify documented technical production |
| Technical acceptance | Validate the deliverable against defined criteria |
This structure is especially useful in Ongoing Consulting Engineering Services, where the client needs recurring support but not every demand has the same complexity.
What is OS-LPU?
OS-LPU is a Service Order used to activate an item previously defined in the LPU.
It is appropriate when the demand is specific, objective, and measurable by a reference unit. OS-LPU allows the client to request a defined deliverable without starting a new procurement process from scratch.
An OS-LPU can be used for demands such as:
- preliminary technical analysis;
- objective document review;
- simple comparison matrix;
- specific technical opinion;
- participation in a technical meeting with a formal record;
- acceptance checklist;
- preliminary proposal analysis;
- specific technical support for contracting;
- initial risk assessment.
The OS-LPU must have a bounded scope. If the demand requires many interdependent activities, multidisciplinary review, or broader responsibility, it probably should not be treated as an isolated item.
What an OS-LPU should contain
An OS-LPU must record minimum information to avoid ambiguity.
Recommended fields include:
- demand identification;
- applicable LPU item;
- technical objective;
- reference documents;
- adopted assumptions;
- included scope;
- exclusions and limitations;
- expected deliverable;
- schedule;
- person responsible for acceptance;
- measurement criterion;
- acceptance criterion;
- evidence record.
This record reduces dependence on memory or informal conversations and improves contract traceability.
What is OS-CIC?
OS-CIC is a Service Order linked to an Integrated Engineering Services Cycle.
It is appropriate when the demand cannot be adequately represented by a single LPU item or a simple sum of microactivities.
An OS-CIC can be used in cycles such as:
- technical due diligence;
- technical procurement;
- owner’s engineering;
- support for complex contracting;
- commissioning;
- technical acceptance;
- multidisciplinary review;
- technical diagnosis;
- detailed design;
- design coordination.
In these cases, the demand involves connected stages. There may be meetings, document analysis, evidence gathering, risk matrices, validation of assumptions, report preparation, technical review, and presentation of results.
OS-CIC organizes the cycle as a coherent technical unit.
Why not everything should be measured as an isolated item
Measuring every consulting activity as an isolated item can create distortions.
A complex demand may involve several meetings, reviews, analyses, and records. If each microactivity is measured separately, there is a risk of fragmentation, double counting, loss of context, and disputes over what is included in each item.
On the other hand, if the demand is treated only as an hour bank, the client may lose clarity over the deliverable and acceptance criterion.
OS-CIC seeks to balance these two issues. It recognizes that certain services need to be measured by cycle, with scope, stages, deliverables, and consolidated criteria.
OS-LPU vs. OS-CIC
The central difference lies in the nature of the demand.
| Criterion | OS-LPU | OS-CIC |
| Type of demand | Specific and bounded | Integrated and interdependent |
| Contracting basis | LPU item | Engineering cycle |
| Measurement | By item, unit, or specific deliverable | By stage, milestone, or set of deliverables |
| Complexity | Low to moderate | Moderate to high |
| Risk of fragmentation | Lower | Higher if treated as isolated items |
| Example | Specific technical opinion | Due diligence or technical procurement |
The choice between OS-LPU and OS-CIC should consider the actual scope, technical risk, number of interfaces, documentation needs, and responsibility involved.
Deliverable-based measurement
Both OS-LPU and OS-CIC should seek deliverable-based measurement whenever possible.
Deliverable-based measurement does not ignore technical effort. It recognizes that effort must produce a verifiable result.
Possible deliverables include:
- technical opinion;
- analysis report;
- risk matrix;
- comparison matrix;
- technical meeting record;
- acceptance checklist;
- measurement bulletin;
- due diligence report;
- action plan;
- commissioning documentation;
- technical memorandum or detailed design.
This model improves communication with procurement, legal, engineering, facilities, operations, and maintenance. It also strengthens technical acceptance in engineering projects because validation is based on documented criteria.
Document traceability
Document traceability makes it possible to reconstruct the technical history of a demand.
A good Service Order should make it possible to answer:
- who requested it;
- what technical problem needed to be solved;
- which documents were considered;
- which assumptions were adopted;
- which scope was approved;
- which deliverable was produced;
- which risks were identified;
- which acceptance criterion was used;
- when the demand was measured and accepted.
This traceability is relevant to private companies, industrial organizations, public bodies, and institutions that need to contract engineering services with accountability and documentation.
Practical example: technical proposal analysis
Imagine that an organization needs to compare three proposals for implementing a critical system.
If the need is only a preliminary review to identify apparent gaps, the demand can be handled as an OS-LPU.
If the need involves supplier meetings, a comparison matrix, risk analysis, technical bid leveling, a documented recommendation, and negotiation support, it may be more appropriate to structure an OS-CIC.
In this case, the demand is no longer merely a specific review and becomes an integrated contracting-support cycle.
The content on technical proposal analysis in engineering is directly connected to this process.
How A3A uses OS-LPU and OS-CIC
A3A uses OS-LPU and OS-CIC to organize consulting engineering demands with clear scope, measurement criteria, and document traceability.
This methodology connects to services and solutions such as:
- Ongoing Consulting Engineering Services;
- Detailed Design;
- Technical Due Diligence;
- Technical Procurement;
- Owner’s Engineering;
- EPCM;
- Design Coordination.
The objective is to prevent technical demands from being handled informally, without scope, a deliverable, or an acceptance criterion.
Recommended complementary content
To explore the methodology further, also see:
- Complete Guide to Consulting Engineering;
- HTE in Consulting Engineering;
- LPU in Consulting Engineering Services;
- Technical Proposal Analysis in Engineering;
- Risk Matrix in Engineering Projects;
- Technical Acceptance in Engineering Projects.
Conclusion
OS-LPU and OS-CIC are instruments for turning technical demands into service orders with scope, deliverables, measurement criteria, and traceability.
OS-LPU is appropriate for specific demands measurable by an LPU item. OS-CIC is appropriate for integrated engineering cycles when the demand involves several interdependent activities.
When properly applied, these structures reduce ambiguity, improve measurement, strengthen technical acceptance, and make consulting engineering contracting clearer and more defensible.
Talk to our Engineering Department
If your organization needs to structure consulting engineering demands through Service Orders, LPU, integrated cycles, or deliverable-based measurement, talk to A3A’s Engineering Department.
A3A supports private companies, industrial organizations, public bodies, and institutions in contracting consulting engineering with method, scope, technical governance, and document traceability.
Technical references
[1] A3A Consulting Engineering. Complete Guide to Consulting Engineering. Available at: https://a3aengenharia.com.br/conteudo/guias-tecnicos/guia-completo-sobre-engenharia-consultiva/.
[2] A3A Consulting Engineering. Consulting Engineering Contracting with Traceability, Governance, and Cost Engineering. Available at: https://a3aengenharia.com.br/conteudo/whitepapers/contratacao-engenharia-consultiva-governanca-rastreabilidade/.
[3] PMI. PMBOK Guide.
[4] AACE International. Recommended Practices for Cost Engineering.
Frequently asked questions
OS-LPU is a Service Order linked to an LPU — Unit Price List item. It is intended for specific, bounded, and measurable demands.
OS-CIC is a Service Order linked to an Integrated Engineering Services Cycle. It is intended for demands composed of several interdependent activities.
Use OS-LPU when the demand is objective, bounded, and measurable by an LPU item, such as a preliminary analysis, specific technical opinion, checklist, or document review.
Use OS-CIC when the demand involves connected stages, such as due diligence, technical procurement, owner’s engineering, commissioning, technical acceptance, or multidisciplinary review.
HTE represents consulting effort, LPU organizes items and reference units, OS-LPU formalizes specific demands, and OS-CIC formalizes integrated engineering cycles.
