Petroleum software development sits at a unique intersection of deep engineering domain knowledge and advanced software engineering. When oil and gas companies and engineering firms look to outsource software development projects — whether building custom SCADA integrations, reservoir engineering tools, production optimization platforms, or laboratory data systems — finding a partner with genuine expertise in both dimensions is the critical challenge.
This guide outlines the key criteria for evaluating oil and gas software development partners, the red flags to watch for, and the questions that separate genuinely qualified vendors from generalist software shops that claim oil and gas experience.
Why General Software Development Firms Often Fail in Oil and Gas
Oil and gas engineering software is not simply “software that happens to be used in the oil industry.” It requires:
- Deep thermodynamic knowledge: Implementing an EOS, computing compressibility factors, or tracing a phase envelope requires graduate-level chemical engineering knowledge. A developer who has to look up what Peng-Robinson means cannot implement it correctly.
- Domain-specific data standards: OPC-UA/DA, Modbus, AGA report standards, PPDM data models, WITSML, and OSDU frameworks are specific to the industry. Integration with legacy SCADA systems requires knowledge of specific protocols and vendor quirks.
- Safety-critical mindset: Software that interfaces with SCADA control systems or provides data for production decisions must be developed with reliability and failure-mode thinking from the outset. A web developer’s attitude toward testing and error handling is inadequate for industrial control environments.
- Regulatory awareness: Pipeline measurement software must be consistent with AGA, ISO, and local regulatory requirements. EOS calculations for custody transfer may require validated software with documented test cases.
Key Criteria for Evaluating a Petroleum Software Partner
1. Technical Domain Expertise
The most important criterion is genuine engineering domain knowledge, not just software development capability. Evaluate this by:
- Asking specific technical questions about the domain relevant to your project (e.g., “How would you handle C7+ characterization for a gas condensate EOS?” or “What’s the difference between AGA8 and GERG-2008 for custody transfer?”). A qualified partner will answer clearly; a generalist will hedge or give vague responses.
- Reviewing the partner’s existing products or published work in the domain. KYCIS, for example, has developed DPCloud (a production dew point calculation service) and PVTz (a PVT laboratory processing system) — demonstrating the thermodynamic, SCADA, and laboratory domain knowledge relevant to most upstream and midstream software projects.
- Checking team qualifications — are there licensed professional engineers or PhD-level thermodynamicists on the technical team?
2. Relevant Project Track Record
Ask for specific examples of completed projects that are similar to yours in technical domain and integration environment. Relevant project types include:
- SCADA integration and real-time calculation services (TCP/OPC/REST interfaces with industrial control systems)
- PVT / reservoir engineering tools (EOS implementation, PVT data processing, simulation model preparation)
- Production data management and allocation systems
- Process simulation integration (Aspen, HYSYS, PIPESIM data exchange)
- Laboratory information management systems (LIMS) for petroleum testing
Be cautious of partners who claim broad oil and gas experience but can only point to business application development (CRM systems, field ticketing apps, mobile crew management tools) — these do not demonstrate the technical depth required for engineering software.
3. Software Architecture and Quality Practices
Industrial software must be reliable, maintainable, and testable. Ask about:
- Testing approach: Is there a comprehensive automated test suite? Are unit tests, integration tests, and performance benchmarks part of the standard development process?
- Performance requirements: Can they demonstrate that their software meets specified performance targets? (For SCADA calculation services, response time and throughput are contractually significant.)
- Deployment and licensing: How is software licensed and deployed in industrial environments? Do they have experience with air-gapped networks, license server alternatives, and Windows Service deployment?
- Documentation: Is engineering documentation (architecture design, API documentation, test reports) produced as a standard deliverable, not an afterthought?
4. Intellectual Property and Confidentiality
Oil and gas software development often involves access to proprietary reservoir data, production data, or commercially sensitive process information. Ensure:
- The development agreement clearly assigns IP ownership of custom-developed software to the client
- The partner has a clear confidentiality policy and NDA process for handling client data
- Development is performed on isolated, secure infrastructure — not shared cloud environments where client data could be commingled with other projects
- Any third-party components or libraries used in the software are clearly disclosed with their licensing terms
5. Communication and Project Management
Technical competence is necessary but not sufficient. Effective software development partnership requires:
- Clear communication in the client’s working language (English for most international oil and gas projects)
- Structured requirement specification process — the partner should help you articulate your requirements clearly, not just build whatever you describe
- Milestone-based delivery with demonstrable progress at each milestone
- Transparent issue escalation — problems should be surfaced early, not hidden until they become critical
Questions to Ask Potential Partners
- Can you describe a project where you implemented a thermodynamic calculation (EOS, phase equilibrium, or dew point calculation) integrated with a SCADA or industrial control system?
- What equations of state have you implemented? Can you explain the difference between PR78, SRK, and AGA8 for dew point calculation?
- How do you handle license management for software deployed in air-gapped industrial networks without internet access?
- What is your testing process for numerical accuracy in thermodynamic calculations?
- How do you manage IP ownership and confidentiality when working with client reservoir or production data?
- What documentation do you deliver as standard project deliverables (API documentation, design specifications, test reports)?
About KYCIS: Petroleum Software Development
KYCIS Inc. is a petroleum software company based in Edmonton, Alberta, with deep expertise in thermodynamic calculation systems, SCADA integration, and PVT data processing. Our products — DPCloud (real-time dew point calculation for SCADA) and PVTz (PVT laboratory data processing) — demonstrate the domain knowledge and software engineering quality that defines our contract development work.
We provide custom software development services for oil and gas companies requiring specialized engineering software: SCADA calculation engines, thermodynamic property libraries, reservoir data processing tools, and laboratory information systems. Our team combines petroleum engineering domain expertise with modern software development practices (.NET 10, REST APIs, cloud-ready architecture) to deliver industrial-grade software that meets the reliability and accuracy requirements of production environments.
If you are evaluating petroleum software development partners for an upcoming project, contact KYCIS to discuss your requirements. We are happy to answer specific technical questions about our capabilities and provide examples relevant to your project type.
Conclusion
Selecting the right petroleum software development partner requires evaluating both engineering domain expertise and software development capability — neither is sufficient alone. By applying the criteria and questions outlined in this guide, oil and gas companies can identify vendors with genuine oil and gas engineering depth, rather than generalist software firms that will need extensive technical direction throughout the project.
The best petroleum software partners are those who have already built production-deployed software in your technical domain — because they have already solved the hard problems you will encounter in your project.