Skip to content

Custom software development · Dammam

Custom Backend Systems & ERP for Dammam

We build custom backend systems and ERP modules for contractors, manufacturers and logistics operators working in and around Dammam and the wider Eastern Province: vendor and work-order portals, plant maintenance and asset-tracking systems, and HSE reporting dashboards. We work remotely from Ahmedabad, India, on Saudi hours. There is no QalbIT office in Dammam, and this page explains exactly what that changes.

Dammam’s business is plant uptime, vendor qualification and inspection paperwork. So this page stays with the systems an industrial contractor actually runs, and with what ZATCA and PDPL mean for a company that bills plants rather than shoppers.

  • 2018

    Building software since

  • 5.0

    Clutch rating

  • 50+

    Clients served

  • 4.9

    Google rating, 18 reviews

Get your free estimate

Three quick questions: scope, approach and a price range back within 48 hours. No sales call required first.

What do you need built?
When do you want to start?
Where should we send the estimate?

Answer all three questions above, then send.

NDA-friendly · IP yours from day one

Definition


What a remote software partner actually does for a Dammam company

QalbIT is a custom backend and ERP software development company working for Dammam contractors and manufacturers as a remote engineering partner. Two Saudi rules shape every build. ZATCA Phase 2 requires B2B tax invoices to be cleared by the Fatoora platform before the buyer receives them, and Wave 25 brings taxpayers above SAR 187,500 of VAT-subject revenue into scope by 1 February 2027. PDPL Article 29 governs workforce and vendor data leaving the Kingdom. Delivery is remote from Ahmedabad, India.

In the Eastern Province the software question usually starts at a plant gate, not in a boardroom. A crew is held at the gate because a certificate expired in someone’s inbox. A planner cannot tell which pump has slipped its service interval. An HSE lead is rebuilding an incident report from three message threads.

An integrator in Dammam or Al Khobar can sit in your planning office and attend the site induction. We cannot. What we can do is build the system those people use, from a written specification, and hand you the source code.

That trade-off decides more than price. It decides where workforce data is processed, who answers for the cross-border transfer, and how a cutover in a shutdown week is staffed.

We are the remote option. The rest of this page is written so you can tell whether that suits your operation before you call anyone.

At a glance

  • Core focus

    Vendor portals, maintenance systems, HSE and backend systems

  • Engagements

    Vendor portals · maintenance rebuilds · ERP extensions · HSE tools

  • Delivery

    From Ahmedabad, inside the Eastern Province Sunday–Thursday week

  • Saudi position

    No local entity. Processor outside the Kingdom under PDPL

Definition


Local systems integrator vs global consultancy vs remote engineering partner

Eastern Province buyers often meet all three in the same tender round. They differ most in who can stand on your site and who carries the data-transfer risk.

  • Local Eastern Province integrator

    Saudi-registered, able to put engineers through your site induction and onto the plant floor. The right pick when the job is hands-on: scanners at a gate, tablets during a turnaround, a cutover that needs people in the room.

  • Global consultancy

    Brought in when a group runs one ERP programme across several plants and wants a large, layered team with an in-Kingdom presence and a board-level sponsor.

  • Remote engineering partner

    A small senior team outside the Kingdom building one defined system, such as a vendor portal or a work-order module, on your working hours. With no Saudi entity, the PDPL transfer terms go into the contract up front.

QalbIT is the third. If your rollout needs people on site during a shutdown, we will tell you that before any contract is drafted.

Fit


When a remote partner is the right call for a Dammam business

Two honest lists. Most Dammam buyers recognise their project in one of them within a minute.

  • Hire a remote partner when

    • The system has edges you can draw: contractor pre-qualification, preventive-maintenance schedules, an asset register, permit-to-work tracking.
    • Your maintenance or HSE lead can make day-to-day calls, so a two-and-a-half-hour offset never holds a decision up.
    • You are replacing spreadsheets or extending an ERP you already run, not redesigning how the whole group operates.
    • You want the repository, the documentation and the next roadmap decision to stay with your company.
    • Workforce and vendor records can move under PDPL’s standard transfer safeguards, with health records kept in the Kingdom.
  • Hire locally instead when

    • The core of the system is health or biometric data, such as medical-fitness files or fingerprint gate access. PDPL treats both as sensitive, so keep that processing in the Kingdom.
    • An industrial anchor’s approved-vendor programme, or an Etimad tender, requires delivery by a Saudi-registered firm.
    • Every supervisor and crew lead needs training and support in Arabic, on site, not just an Arabic interface.
    • The go-live lands inside a plant shutdown and needs people on the ground for the whole window.
    • Your procurement policy only contracts with holders of a Saudi commercial registration.

When a project sits in the second list, we decline it. Building it remotely would waste your shutdown window, and with sensitive data it would put your PDPL position at risk.

Next step


Not sure whether to hire locally?

Send a short description of the system and the records it will hold, from vendor files to incident reports. We will tell you which list it falls in, including when a Dammam integrator is the better buy.

Comparison


Remote partner vs local integrator vs global consultancy

No rates here. Each row is a difference a Dammam contractor will feel during a build, and the rows where we come off worse are left in. Send us your scope and the records it holds, and we will fill this table in for your project.

How a remote engineering partner compares with an Eastern Province integrator and a global consultancy for plant and contractor systems
Local Eastern Province integratorGlobal consultancyQalbIT (remote partner)
Physical Dammam presenceYesUsuallyNo
Arabic-first deliveryYesVariesEnglish with your engineers, Arabic in screens and reports
PDPL position on workforce dataProcesses it inside the KingdomUsually processes it in-KingdomProcessor abroad, transfer terms in the contract
Where records are hostedIn the KingdomIn the Kingdom on requestSaudi hosting available, code written abroad
ZATCA clearance of B2B invoicesCommonCommonYes, including credit and debit notes
Working-week overlapFullFullFour of five days live, 2.5 hours apart
Maintenance and ERP system familiarityCommonVariesWorked from your interface documents
Shutdown and turnaround coverOn siteOn siteRemote only
Source code ownershipVariesVariesFull repository handed to you
Team size on your accountVariesLarge, layeredA few senior engineers, founder reachable
  • 01

    We left the losing rows in.

    On-site engineers, Arabic-first support and shutdown cover all favour a local firm. A Dammam buyer should weigh those before the build, not during a turnaround.

  • 02

    Plant-system familiarity is a spec question, not a location question.

    What matters is whether your maintenance or ERP system exposes a documented interface. Bring the interface documents, or the name of whoever holds them, to the scoping call.

  • 03

    Two and a half hours is a short gap.

    The Eastern Province runs on UTC+3 and Ahmedabad on UTC+5:30, so an 8am planning meeting in Dammam is 10:30 in our office, four days a week.

  • 04

    Vendor-programme eligibility is binary.

    If registration on an industrial anchor’s approved-vendor list requires an in-Kingdom commercial registration, that decides the vendor before quality does. Ask at the first call and you get a straight answer.

What we build


Custom software we build for Dammam companies

Built so that a work order raised in the field, the spare part it uses and the inspection that closes it share one record, instead of living in three files.

  • Vendor

    Vendor qualification and contractor portals

    Registration, document-expiry tracking, HSE certification and approval workflows for contractors bidding into or already working under an industrial anchor, without a spreadsheet holding the whole process together.

  • Maintenance

    Plant maintenance and asset-tracking systems

    Asset registers, preventive-maintenance schedules, work orders and downtime logs built around how your maintenance team actually moves through a facility.

  • ERP

    Industrial ERP and supply-chain modules

    Stores, inventory, procurement and progress billing as modules added one at a time, standalone or on top of the ERP you already run, with stock visible across every yard and material moving through the port. Shaped for a contractor or manufacturer, not adapted from retail.

  • HSE

    HSE reporting and compliance dashboards

    Incident logging, permit-to-work tracking and audit-ready reporting that replaces a paper trail nobody can search under deadline.

  • Backend

    Custom backends and APIs

    The services underneath: Laravel, Node.js and NestJS APIs that sync maintenance, stores and finance systems on a schedule, and retry cleanly when a site network drops.

  • CRM

    Custom CRM development

    Account plans, tender and RFQ tracking, and framework-agreement renewals for B2B sellers whose customers are plants, not consumers. An accepted quote hands over to invoicing without re-keying.

Cost


How much does custom software development cost in Dammam?

For a Dammam contractor or manufacturer, the price of custom software follows the scope of phase one, the systems it has to connect to and the compliance work inside it. Clearing B2B invoices with ZATCA, linking to a plant maintenance system and migrating asset history are each priced separately. We scope first, then fix the price of phase one.

We do not print a price list, because a figure quoted before we have seen your process would be a guess.

A single-yard vendor portal and an asset-management system covering several plants with three integrations are different projects, and any range wide enough to cover both tells you nothing.

Instead you get a scoping call, a written process map and a fixed price for phase one before you commit past discovery. The drivers below are the ones that move that price, so you can test any quote against them, ours included.

Try the software development cost calculator

What moves the number

  • Scope of phase one

    The biggest lever. A first phase that does vendor qualification and work orders well costs less, and earns more trust on site, than one that half-covers six modules.

  • Integration count and quality

    A maintenance system with a documented API is a few days of work. An older on-premise system that only exports files needs a middleware layer and nightly reconciliation.

  • ZATCA integration depth

    A contractor’s invoices are mostly B2B, so they need clearance, not just reporting. Progress claims, retention releases and credit notes each have to pass, which means CSID onboarding, XAdES signing and an unbroken hash chain.

  • Data protection architecture

    Crew rosters, medical-fitness files and incident reports carry different weight under PDPL. Deciding at design time what stays in the Kingdom costs little; moving it later costs a rebuild.

  • Arabic in the product

    Bilingual screens for supervisors and crew leads, right-to-left layouts, and Arabic permit and inspection reports that print correctly. Usually underestimated.

  • Data migration depth

    Moving vendor masters and open work orders is routine. Bringing across years of maintenance history, with every record tied to the right asset tag, is a project of its own.

How we work with Dammam teams


A delivery process built around a 2.5-hour offset

Being two and a half hours apart is easy. Shutdown calendars, shift handovers and site access rules are harder, so the plan is built around them.

  1. Discovery and process mapping

    Follow a work order, a vendor file or a permit from the moment it is raised to the moment it is closed, and note who touches it. Pick the system that hurts most for phase one and settle the data-protection profile for the whole build.

    A process map, a system roadmap, a phase-one estimate and the data-transfer position in writing.

    1–2 weeks

  2. Architecture and data design

    Design the data model around your asset hierarchy and vendor categories, then the screens and the interfaces to your maintenance, stores or ERP systems. Decide which records are hosted in the Kingdom.

    Signed-off data model, screen designs, interface plan and hosting decision.

    2–3 weeks

  3. Build phase one

    Weekly increments, demoed with your own asset tags, vendors and work orders. Demos are timed to your Sunday–Thursday week and kept away from planned shutdowns.

    Modules tested against real plant and contractor scenarios.

    6–14 weeks, scope-dependent

  4. Migration, training and parallel run

    Load vendor masters and open work orders, train planners and supervisors, and run old and new side by side until both show the same backlog.

    Go-live with reconciled records and supervisors who have used the system before day one.

    2–4 weeks

  5. Stabilise, extend, roll out next

    Fix what the first months of use show up, add the reports your HSE and maintenance leads ask for, then start the next system on the roadmap.

    A platform that grows with the operation, not a one-off delivery.

    Ongoing, month-to-month

Dammam works Sunday to Thursday on UTC+3, and our team is on UTC+5:30, so four of your five working days overlap ours in real time. Thursday afternoon and the weekend are covered by written updates. If a cutover falls in a shutdown week, the remote support hours are agreed before it starts.

Book a scoping call

Where we fit best


Dammam projects we take on

Four kinds of Dammam engagement suit a remote team. The ones that do not are in the fit section above.

  • First build

    Replacing spreadsheets with a real vendor system

    Contractors and manufacturers whose vendor files, work orders or maintenance logs live in spreadsheets and shared inboxes, and who want one system built properly the first time. For contractors, manufacturers and logistics operators.

  • Modernisation

    Rebuilding software you have outgrown

    An ageing desktop maintenance tool or early web portal rebuilt as a modern web application, with asset and vendor history carried across and supervisors moved over in stages. For plants and contractors on unsupported tools.

  • Compliance

    ZATCA and PDPL retrofit

    Bringing a contractor’s billing system to Fatoora clearance, and moving crew and vendor records to where PDPL needs them. A Wave 25 notification is often what starts it. For contractors billing B2B under Wave 25.

  • Integration

    Extending systems you already run

    Portals, mobile inspection apps and dashboards added on top of the ERP or maintenance system you already run, so field data reaches it without re-typing. For operators keeping their current ERP.

Industries


Sectors we build for in Dammam and the Eastern Province

The Eastern Province economy sits around energy and petrochemicals, and around the contractors, suppliers and hauliers that serve them. These are the sectors where our process work carries over.

  • Industrial contracting and plant services

    Vendor qualification, work-order management, permit-to-work and HSE reporting for oil and gas service companies and contractors serving refineries, petrochemical plants and industrial facilities, from Dammam up the coast to Jubail.

  • Manufacturing and processing

    Bills of materials, work orders, batch tracking and inventory for manufacturers supplying an industrial supply chain, where a missed component holds up a production line rather than just an order.

  • Logistics and port-adjacent operations

    Consignment tracking, warehouse allocation and dispatch planning for operators moving industrial and container cargo through King Abdulaziz Port and onward inland.

  • Trading and distribution

    Industrial distributors supplying spares, consumables and safety equipment to the region’s plants: stock across several warehouses, supplier reconciliation and B2B invoices cleared with ZATCA.

Next step


Your process is the reason the off-the-shelf tool doesn’t fit.

Packaged maintenance and vendor tools assume a generic plant. Tell us how your work orders, permits or vendor approvals really flow, and we will say whether the gap is worth a custom build.

Saudi compliance


Building software for Dammam: ZATCA, PDPL and data residency

ZATCA and PDPL apply in Dammam exactly as they do in the rest of the Kingdom. What changes is where they bite. For a contractor, it is B2B invoices that must be cleared before the client sees them, and HSE files that hold health data.

  1. ZATCA e-invoicing (Fatoora)

    Under Phase 2, your billing system connects to ZATCA’s Fatoora platform. A standard B2B or B2G tax invoice is cleared by Fatoora before it reaches your client; a simplified B2C invoice is reported after it is issued. Each one carries UBL 2.1 XML, a UUID, a cryptographic stamp and a QR code. ZATCA announced Wave 25 on 24 July 2026. It covers taxpayers with VAT-subject revenue above SAR 187,500 in any year from 2022 to 2025, half the SAR 375,000 threshold of Wave 24, and they must integrate by 1 February 2027. Most Dammam contractors invoice plants and other companies, so nearly every document they raise, progress claims and retention releases included, goes through clearance rather than reporting. The usual failure points: onboarding the cryptographic stamp identifier (CSID), XAdES signatures that do not validate, and a rejected clearance that breaks the previous-invoice-hash chain for every invoice after it. Sources: ZATCA, Wave 25 e-invoicing integration announcement, zatca.gov.sa.

    Phase 2 · Wave 25

  2. PDPL and cross-border data

    PDPL was issued by Royal Decree M/19, amended by Royal Decree M/148, and has been fully enforceable since 14 September 2024. It reaches organisations outside the Kingdom that process the personal data of people inside it, and that includes us. In a Dammam system that data is mostly crew rosters, Iqama and certification details, driver records and vendor contacts. Article 29 allows it to be transferred abroad under SDAIA’s approved safeguards, such as the Saudi Standard Contractual Clauses, with a risk assessment where the regulation requires one. You are the controller and we are the processor. The transfer needs a documented basis and a contract clause before the first record moves. Sources: Saudi Data & AI Authority, Personal Data Transfer Regulation v2.0 (August 2024), dgp.sdaia.gov.sa.

    Royal Decree M/19

  3. HSE records and sensitive data

    PDPL · sensitive data. An incident report that names an injured worker, a medical-fitness certificate in a contractor’s onboarding file and a fingerprint at a site gate are all sensitive data under PDPL: health data in the first two cases, biometric data in the third. They carry tighter rules than an ordinary contact record. So the design we recommend splits an HSE system in two. Permits, incident counts and corrective actions can be built and supported by a remote team, while the identifiable health and biometric records stay on servers in the Kingdom and our engineers work against masked copies. Which records count as sensitive is your legal team’s decision. We design the split once they have made it. Sources: Personal Data Protection Law and Implementing Regulation, dgp.sdaia.gov.sa · Saudi Data & AI Authority.

We build compliant output into the system from the start, rather than attaching a compliance add-on later. If a Wave 25 letter has set your deadline, the plan works backwards from 1 February 2027.

Working with us


Hiring a vendor outside the Kingdom: the honest version

Any vendor outside the Kingdom brings the same four risks to a Dammam contract. Here they are, in plain terms.

  • Data transfer

    You are the controller. Before crew or vendor records reach us, the transfer needs a lawful basis under Article 29 and documented safeguards. It is contract work, done once, before the build starts.

  • Sensitive data

    Medical-fitness files, injury reports and biometric gate data carry tighter rules. If your system holds them, plan for that processing inside the Kingdom, whoever writes the code.

  • Vendor-programme and government procurement

    Registration on an industrial anchor’s approved-vendor list, or an Etimad tender, commonly requires a Saudi commercial registration from the contracting party. We do not have one.

  • Physical presence

    Nobody from our team will attend your site induction or walk a unit with your maintenance planner. If a cutover needs hands on the plant, plan for a local partner, and we will say so at the scoping call.

  • Everything else

    Maintenance and ERP systems, accounting products, e-invoicing service providers, banking APIs, BI tools, and the handheld scanners used in stores and at gates.

    Integrations

None of these rules out a remote partner. They are reasons to settle the contract terms first, so nothing surprises you halfway through a build.

Tech stack


Technology we use for Dammam builds

Asset and vendor records outlast the people who first entered them. We pick proven technology that your own team, or the next vendor, can maintain.

  • Backend and business logic

    • Laravel (PHP 8.x) for work-order, vendor and stores modules that need a full audit trail.
    • NestJS (TypeScript) where many integrations and event flows meet, such as ERP or sensor feeds.
    • Queues and schedulers for nightly syncs, document-expiry alerts and permit reminders.
  • Frontend and usability

    • Next.js and React screens built for fast data entry by planners and storekeepers.
    • Arabic and English interfaces with correct right-to-left layout.
    • Role-based dashboards for supervisors, inspectors and plant managers.
    • Offline-capable mobile forms for inspections where site signal drops.
  • Data and integrations

    • PostgreSQL and MySQL with strict constraints, so asset, stock and billing records cannot drift apart.
    • ZATCA Fatoora clearance for B2B invoices, credit notes and debit notes.
    • Interfaces to maintenance, ERP and accounting systems through their documented APIs or file exports.
  • Security and residency

    • Permissions by role, site and contractor company, with every change logged.
    • Saudi-hosted servers for records that must stay in the Kingdom.
    • Automated backups, staged releases and alerts when a sync or a job fails.

Already running an ERP, a maintenance system, or spreadsheets and email? We extend what works before replacing anything, and the migration path is written into the plan.

Outcomes


What the project should actually change

No forecasts here. These are the changes the system should make on site and in the office, with the measure that would show each one.

What the project should actually change: what changes and how you would measure it
What changesHow you’d measure it
One record of every asset, vendor and open work orderGap between the system and a physical asset or stock count
Vendor documents stay valid without chasingContractors turned away at the gate for expired paperwork
Preventive maintenance happens on scheduleShare of planned work orders closed by their due date
Invoices and progress claims clear ZATCA first timeRejected clearances and hash-chain breaks per month
Permits and approvals are enforced by the systemShare of jobs with a complete permit and sign-off trail
Incidents are reported and closed on timeDays from incident to a closed corrective action
  • A note on sourcing

    A note on sourcing

    We do not quote downtime or cost savings for plants we have not measured, and we do not repeat the headline software-failure rates credited to analyst firms, which have no traceable primary source. Every figure on this page sits next to its source and date.

Why QalbIT


Why work with us

  1. Eight years building operational software

    Since 2018 we have delivered 120+ engagements across web, mobile and platform work, for 50+ clients. Clutch 5.0, Google 4.9, Upwork Top Rated. In the GCC we work today as the white-label engineering team behind a regional agency, and the Dammam offer rests on that same operational-systems experience.

  2. We say what we are

    No Dammam office, no local entity, no implied presence, and no claimed relationship with any named operator or anchor company. The compliance section above is there because losing a deal at the scoping call is better than failing an audit later.

  3. You own the code

    The repository, the documentation and the deployment scripts are yours. There is no licence or per-user fee, and nothing stops you moving maintenance to another team.

  4. Senior team, founder-led

    You talk to the senior engineers who write the code, and the founder is reachable. Questions do not pass through an account manager first.

  5. We’ll tell you to hire locally

    If your rollout needs people on site, for example a cutover during a planned shutdown, we say so on the first call and point you towards a local integrator.

The biggest difference has been their flexibility and solution-oriented approach. Rather than pointing out problems, they focus on solving them. I genuinely cannot recall hearing them say, ‘This cannot be done.’ No matter how many changes or updates we send their way, even after long working days, they consistently respond positively and find a way forward. What stands out most is that our relationship has evolved beyond a traditional client-supplier setup and feels more like a partnership. QalbIT takes genuine responsibility for the platform’s functionality, and when bugs are identified, they are addressed without hesitation.
Gabriell Summerland, CEO, Bluecircle

FAQs · Custom software development in Dammam


Frequently asked questions from Dammam teams

Asked by maintenance managers, HSE leads and contractor owners in the Eastern Province before they choose between a remote team and a local integrator.

Talk to the team
No. QalbIT has no office or legal entity anywhere in Saudi Arabia. Delivery runs remotely from Ahmedabad, India, on Dammam working hours. We say this plainly because implying a local presence creates a problem for both of us the first time it is checked.
Yes, with the data-protection position handled properly. Under PDPL you are the controller and we are the processor. Transferring personal data outside the Kingdom is permitted under Article 29 with approved safeguards, including Saudi Standard Contractual Clauses. That is contract work done once, before the build starts.
Yes. Phase 2 requires direct integration with the Fatoora platform: UBL 2.1 XML, UUID, cryptographic stamp and QR code, with standard invoices cleared before sending and simplified invoices reported afterwards.
Wave 25 covers VAT-subject revenue above SAR 187,500 in any of 2022 to 2025, with integration required by 1 February 2027. Treat the notification you received from ZATCA as authoritative for your own date, and confirm your status directly rather than relying on any article, this one included.
Dammam is UTC+3 and we are UTC+5:30: a two and a half hour offset. Your Sunday to Thursday week overlaps ours on four days out of five. Demos and decision calls are scheduled in your hours; Thursday afternoon through Saturday runs on written updates.
Your organisation, in full, in your own repository, once project payments are complete. No licence, no per-seat fee, no restriction on hiring another team afterwards.
Yes. Vendor registration, document tracking, approval workflows and work-order management are a recurring request from contractors and manufacturers around Dammam, and we build them around how your contractors and inspectors actually work rather than a generic ticketing template.
Yes. Inspection and HSE compliance tools are built as offline-first mobile apps for field teams, because signal drops on site and an inspection form that only works with a connection is not one that gets used. Records sync once a connection is back.
Yes. It is one of the most common integration jobs for industrial operators: maintenance, ERP and accounting systems that were bought separately and were never built to exchange data. We map the integration during architecture and say in writing what each side needs to expose.
Not directly, and we say so upfront. Vendor-registration programmes tied to a major industrial anchor commonly require a Saudi commercial registration from the contracting party, which we do not have. We can build the system a registered local partner then operates.
Yes. Asset-tracking, maintenance-scheduling and reporting across a plant or a multi-site operation is standard scope for us, with the schema, indexing and backup plan for that volume of asset records designed before the first one is written.
Three kinds. Integrators in Dammam and Al Khobar, who can put engineers on your plant floor. Global consultancies, usually for a group rolling one system out to many sites. And remote partners like QalbIT, building custom ERP modules for a single manufacturer from Ahmedabad, India, on Saudi hours. We have no office in Dammam. For a manufacturer we build bills of materials, work orders, batch tracking and stores, one module at a time, beside the ERP you already run or in place of a spreadsheet. An oil and gas service company gets the same approach, starting from work orders and progress billing instead.
We do not quote a figure before seeing the work. The price depends on how many sites and assets the system covers, which maintenance or ERP systems it connects to, whether technicians need an offline mobile app, and how much maintenance history comes across. Once phase one is scoped, its price is fixed in writing before work starts. A work-order module for one yard and planned maintenance across several plants are priced as different projects. ZATCA work only enters the scope if the same system also raises invoices.
We build the contractor’s side of it: a portal holding your company documents, certificates, HSE records and their expiry dates, and showing what is missing before a submission goes in. Registration itself happens in the anchor company’s own system. We have no relationship with Aramco, and we do not build or access its systems. Your staff still submit through the anchor’s own process; the portal makes sure the file they submit is complete and in date. Subcontractors can upload their own certificates into it, and every change is logged.
Yes, for most of it. Permit-to-work, incident logging, corrective actions and audit reports can be designed, built and supported from outside the Kingdom. Records that reveal a worker’s health or biometrics are different: PDPL treats them as sensitive data, so we recommend hosting those on servers inside Saudi Arabia. Our engineers then work from masked copies, never the identifiable originals. What a remote team cannot do is attend your site induction or train crews on the plant floor, so plan a local hand for the rollout.
Our current GCC delivery is a white-label engagement, so we cannot name the end client. We can share detailed case studies from comparable vendor-portal and maintenance-system builds in Europe and India, and we would rather tell you that than manufacture an Eastern Province reference.

Next step


Let’s scope the first system.

Show us how a work order, a spare part or a contractor’s paperwork moves through your operation now. We will map it, pick the one system that should come first, and put a phased estimate in writing. If a Dammam integrator is the better answer, we will say that instead. Most replies arrive within 24–48 hours and open with questions about your plant, not a brochure.