01
Drafting
Drawing production and re-issue to your title blocks and numbering, from markups, models or vendor data. The steadiest volume we absorb.
Engineering support centre · Kazakhstan
We do not run your project.
We do not run your project.
We carry the work inside it.
Drafting, models, calculations and document control, staffed by our engineers and delivered under your contract, your standards and your name.
Call-off · subcontract · work package
Your contract. Your schedule. Your client. What we add is capacity, not another company between you and the work.
The problem
Work arrives in peaks. Headcount does not.
- A campaign lands and the drawing office is already full.
- Hiring for a peak leaves you carrying the cost after it passes.
- Progress needs to be visible while there is still time to act on it.
What we do about it
A centre that scales with the workload.
- Engineers assigned to your scope and released when the peak is over.
- Your standards, your templates, your numbering from the first drawing.
- The state of every document visible while the work is still running.
What we do
Seven kinds of work, all inside your project
Each one is a scope you can hand over on its own, or a part of a larger package we carry for you.
02
3D and BIM modelling
A model kept alive rather than delivered once: drawings, schedules and take-offs come out of it as the design moves.
03
Calculations
Sizing, strength, loads and supports in the scope we carry, written up so your engineer can check the working rather than repeat it.
04
Document control
Routes, revisions, comment rounds, statuses and transmittals — the register kept current instead of reconstructed at handover.
05
Material coordination
Take-offs reconciled with the model, the drawings and purchase data, with changes reported between revisions instead of found on site.
06
Consulting
CFD, finite element analysis, fitness-for-service and failure investigation, ordered as a separate task when a decision needs a number.
07
Digitalisation
Data entry, parsing of existing documents and registers, and manual input where every entry needs a person's check.
Boundaries
What stays with you
The contract with your client. The tender. Design authority and the signature on the issue. Responsibility for the project as a whole. We take the scope, never the role.
How it works
Three steps from a scope to a delivered package
01
You send the scope
The type of work, the standards you issue to, the volume and the deadline. A markup, a drawing list or a register is enough to start the conversation.
02
We come back with a team and a plan
Who would lead it, how many engineers it takes, how the work is checked before it reaches you, and what the acceptance of each deliverable looks like.
03
Work runs visibly and comes back in your format
Revisions, comments and statuses are recorded as the work happens. The handover pack is assembled along the way, so closing a package is a check, not an excavation.
Ways in
Four contract shapes, one relationship
Call-off
Framework agreed once, work released when you need it. Rates and terms already settled when the peak arrives.
Subcontract
We sit under your contract with the end client and deliver a defined part of the design or documentation.
Dedicated team
A named group working only on your project, inside your process and your reporting, scaled to the load.
Work package
A bounded deliverable list with acceptance criteria, priced and delivered as one package.
Delivery environment
Progress you can see while the work is still running.
We run our scope on the easykawa platform, so the state of the work is visible while there is still time to act on it. If you would rather we work entirely inside your systems, we do that instead.
One place for documents
Drawings, calculations, registers and correspondence live together, each with its revision history attached.
Traceable comment rounds
Who asked for the change, who made it and which revision it landed in — recorded as it happens.
Status without a status meeting
What is in progress, what waits on your comment, what is ready to issue. Visible, not reported.
Handover as you go
The transmittal pack builds itself along the work, so package closure is a verification step.
Your format at the boundary
Whatever we use internally, what reaches you carries your numbering, templates and structure.
Decisions stay in the record
Decisions and history stay in the project record when an engineer rolls off it.
Who works with us
Three positions in the same project
EPC contractors
Absorb a peak without permanent hires. Packages released on call-off and closed when the campaign ends.
Asset owners and operators
A local engineering resource in Kazakhstan for your projects and in-country requirements, under your contractor or directly under you.
Design institutes
Subcontracted volume: our engineers work inside your process and your standards, and the output returns in your format.
Objections first
The questions that decide this
Do you compete with us for the contract?
No. We do not bid for projects. The tender and the contract stay with you. We carry a scope inside the project you have won.
Whose name goes on the issued documents?
Yours. Design authority and the signature stay with you. We deliver in your templates and your numbering, ready to be issued under your name.
How do we start without committing to a large scope?
With one bounded work package: a drawing set, a model, a document register or a data clean-up, with an agreed deliverable list and acceptance criteria. If it goes well, the next package is a conversation and not a negotiation.
Do we have to use your platform?
No. We use easykawa to keep our own work traceable. If you prefer us to work entirely inside your systems, we do that instead, and the platform stops being part of the discussion.
What happens to confidentiality and project data?
Work happens under your confidentiality terms. Client names and project details do not appear in our material without written permission, which is why the examples on this site name the engineering problem and not the operator.
How do you handle our standards and our software?
Engineers are trained on your standards and templates before they touch your documents, and the environment is agreed at the start of the package. Tell us what you issue to and we will tell you plainly whether we work in it today.
What if the quality is not there?
Work is reviewed inside our team before it reaches you, and the acceptance criteria are agreed before the package starts. Rework terms are agreed in the contract.
What if the volume disappears?
That is the point of a centre rather than a hire. The team scales down with the workload, the project record stays complete, and the same engineers can return for the next campaign.
Next step
Send us a scope, not a meeting request
Tell us the type of work, the standards, the volume and the deadline. You get back a staffing plan and an honest answer about whether we are the right centre for it.
- Start with one package, not a framework
- Acceptance criteria agreed before work starts
- We do not bid for projects