BB IP HOLDING CO PTY LTD

Public coded portfolio

The engineering code is the public identity. Only broad functional and maturity boundaries are stated here. Detailed working methods and private project naming remain controlled unless separately published.

A/B/C/D retain domain ownership. E-01 through E-06 are disclosed as a small shared-kernel direction used by several domain systems rather than as a parallel catalogue of end-user products.

CodePublic propositionMaturity
A-01Field evidence and operations platform with offline-capable evidence capture and reconciliation.Implemented / hardening
A-02Structured machinery diagnostics linking symptoms, candidate causes, tests and evidence-backed technical knowledge.Implemented / extending
A-02.RIReliability/failure-intelligence extension using accumulated diagnostic, work and sensing evidence.System architecture
A-03Quality-gated field positioning, alignment and re-entry guidance.Working hardware/software candidate
A-04Physical tag and machine-readable reference workflows linked to safety and field evidence.Working standalone/integration candidate
A-05Structured mechanic/workshop work execution covering preparation, work evidence, verification and closeout.Working software / active development
A-05.CFGControlled configuration/change direction in which machine changes become verified work outcomes.System architecture
A-06Unified operational management surface for coded asset, work, fault, safety and abnormal-state context.Concept / architecture direction
B-01Machine-state research using vibrational observations and human-confirmed labels.Experimental R&D
B-02Compact downhole sensing and durable data-logging platform.Engineering prototype
B-03Non-magnetic downhole trajectory research with optional formation-coupled communications.Concept / gated R&D
C-01Rig-specific calibrated operator decision support around drilling controls and machine loading.Working decision-support tool
C-01.HARMeasured compressor/booster load-sharing and balancing decision-support branch.Working algorithm / field-tool direction
C-02Evidence-governance system for traceable exploration and technical decision packs.Implemented governance concept
C-03Multi-temporal public-data analysis for transparent evidence of exploration activity or intent.Concept / prototype direction
C-04Evidence-grounded engineering-assistance direction using coded state, evidence and technical references.Concept / architecture direction
C-05Cost/performance-intelligence direction linking technical events to economic outcomes.Concept / architecture direction
C-06Simulation/what-if direction for comparing proposed technical or operating changes.Concept / architecture direction
D-01Directional acoustic and pressure-reference leak-diagnostic concept.Build-ready concept
D-02Layered competency-evidence architecture separating general, site and task-specific evidence.Concept
D-02.AUTHAuthority/competency integration direction separating capability evidence from present operational authority.System architecture
D-03Research direction for drilling-coupled electrical-field observations.Parked concept
D-04Hydraulic connection, fitting-resolution and hose-routing engineering-tool family.Working software / engineering-tool family
D-04.COMPBroader component-compatibility direction covering typed parts, equivalents, supersessions and bounded substitutions.System architecture
E-01Shared canonical asset identity and hierarchy across organisations, sites, rigs, systems and components.Kernel direction
E-02Shared durable chronological event history for observations, work, state changes, measurements and approvals.Kernel direction
E-03Shared edge/integration boundary for industrial protocols, files, OEM/partner APIs and external systems.Kernel direction
E-04Shared rule, gate, approval, state-transition and verification semantics across applications.Kernel direction
E-05Shared technical-knowledge substrate linking controlled references, procedures, schematics and failure knowledge.Kernel direction
E-06Shared schemas, event contracts, APIs and extension interfaces for authorised modules.Kernel direction

The later architecture codes recorded in the current disclosure are architecture/development directions as at 3 October 2026 unless a stronger maturity statement is shown. Inclusion records chronology and functional boundaries; it does not by itself determine ownership, inventorship, contractual entitlement, certification or production readiness.

Controlled source commitment

The controlled 3 October 2026 source underlying the current architecture append is retained privately and is not distributed by this website.

56a993f0243ca19b4669445a44019937e4346dd5f8e2fbe6c0c038a250c1fa37