A documented framework, and an honest word for where each standard stands.
Forty-plus controlled documents across four tiers — policies, standards, procedures, and a quality manual that indexes them. It exists because a plant system, a flight controller and a battery pack cannot be held to whatever discipline the team remembers that week.
Read this before the table
We are aligned to and design to the standards below. We do not currently hold third-party certification against them, and we do not describe ourselves as certified.
The distinction matters, and vendors blur it constantly. Alignment means the framework is built to the standard's structure with a documented mapping — real, auditable work. Certification means an accredited body has examined us and issued a certificate. When that happens, this page will say so and name the certificate.
- Certified
- Audited by a third party, certificate held.
- Aligned
- Our framework is built and mapped to the standard's structure. Not third-party certified.
- Designed to
- Applied as engineering practice on the work it governs. Not a certification claim.
Which standard, where, and what it actually governs.
| Standard | Applies in | Status | What it governs here |
|---|---|---|---|
| ISO 9001Quality management systems | Group-wide | Aligned | Our quality manual is structured to the ISO 9001 clauses, with a documented clause-by-clause mapping. |
| AS9100Aerospace quality management | Vyovrinda | Aligned | Configuration management, risk, first-article inspection and counterfeit-part controls are built to the AS9100 additions. |
| ISO 27001Information security management | Group-wide | Aligned | Access control, cryptography, supplier and incident-management controls implemented; Kavacha enforces much of it in software. |
| IEC 62443Industrial automation & control security | Industrial · Smart Infrastructure | Designed to | Zone-and-conduit segmentation, secure remote access and the OT/IT boundary are designed to the 62443 model on every plant system. |
| DO-178C / DO-254Airborne software and hardware | Vyovrinda | Designed to | Requirements traceability, structural coverage and design-assurance-level practice applied to flight software and hardware. |
| ECSSEuropean space standards | Vyovrinda | Designed to | Materials selection, qualification-versus-acceptance testing and review gates follow ECSS practice for spacecraft subsystems. |
| IPC-2221 / IPC-A-610PCB design and assembly acceptability | Electronics | Designed to | Board design rules and assembly workmanship classes are specified per product class and inspected against them. |
| J-STD-001Soldered electrical assemblies | Electronics · Manufacturing | Designed to | Solder joint criteria and process controls applied to assembly, with class selected by the product's environment. |
| ANSI/ESD S20.20Electrostatic discharge control | Electronics · Manufacturing | Designed to | ESD-protected areas, grounding, packaging and periodic verification across handling and assembly. |
| MISRA CSafety-critical C guidelines | Embedded firmware | Designed to | Applied to flight and safety-related firmware, with deviations recorded and justified rather than silently taken. |
| ISA-18.2Alarm management | Industrial · Smart Infrastructure | Designed to | Alarms rationalised, prioritised and reviewed before an HMI is drawn — so operators can act on them. |
| SCOMETIndian export control | Vyovrinda · defence-adjacent | Designed to | A trade-compliance programme with classification, screening and a technology control plan. Classification decisions go to qualified counsel. |
Four tiers, each answering a different question.
Policies say what must be true. Standards say how engineering is done. Procedures are the executable steps. The quality manual indexes all of it.
Four tiers, narrowest at the top
Each tier answers a different question, and each one below implements the one above. The manual at the apex is the shortest document in the set — it exists to point at the others.
Policies
What the group requires — governance, delegation of authority, information security, export control, intellectual property. The layer that says what must be true.
- Company Policies
- Group Governance & DoA
- IP Governance
- Trade Compliance
Standards
How engineering is done — technical standards per stream, test standards, configuration and change management, and the risk, safety and reliability trio.
- Technical Standards
- Test Standards
- Configuration & Change Management
- Risk Management
- System Safety
- Reliability & FMEA
Procedures
The executable runbooks — branching and release, code review, board release to fab, bring-up, incoming inspection, calibration, non-conformance handling.
- Standard Operating Procedures
Quality Manual
The umbrella that names the quality system, maps it to the ISO 9001 clauses and indexes everything below it. The document we would hand an auditor first.
- Quality Manual
Five gates, and nothing passes one on assurance alone.
The same gates apply to a farm controller and a satellite subsystem. Only the depth of evidence changes.
- SRR
Requirements review
Requirements are agreed, testable and traced before design starts.
- PDR
Preliminary design review
Architecture, interfaces and budgets reviewed. Major risks identified and owned.
- CDR
Critical design review
Detailed design complete and reviewed. The design is frozen into a baseline.
- TRR
Test readiness review
Test procedures, rigs and acceptance criteria ready before testing begins.
- PRR
Production readiness review
Manufacturing data pack, processes and inspection proven before volume build.
And the four gates every engagement runs through.
- Gate 01
Understand the constraint
The shutdown window, the certification date, the power budget, the system nobody can switch off.
- Gate 02
Engineer to a spec
Requirements, interfaces and acceptance criteria agreed before build. Design reviews at defined gates.
- Gate 03
Prove it before it ships
FAT, environmental qualification, restore drills, load tests — evidence rather than assurance.
- Gate 04
Stay for day two
Commissioning, operator training, documentation and a support agreement that outlives the project.
What we can put in front of you.
A framework nobody can inspect is decoration. These are the artefacts a customer, an auditor or a partner can reasonably ask us for.
- The quality manual and its ISO 9001 clause mapping
- Technical and test standards for the streams in scope
- FAT and SAT packs, with signed check sheets
- Requirements traceability from requirement to verification result
- Configuration baselines and the change history against them
- Calibration records and non-conformance reports
- Supplier quality flow-down clauses
Where certification actually sits
Certification is a decision about cost and timing, not about whether the discipline exists. The framework was built first deliberately — certifying an organisation that has not written its standards down is an expensive way to produce a binder. If a contract requires a certificate, tell us which one and we will be straight with you about the timeline.
Ask us about a specific standardProcurement asking hard questions?
Send us the requirement. We will tell you what we can evidence today and what we cannot — before you write us into a bid.