Buntop Brownfield Architecture & OT/IT Readiness Suite

BUNTOP BROWNFIELD INTEGRATION APPROACH

Buntop Brownfield Activity System Map

Explore how approved equipment interfaces, useful data models and network boundaries fit together. These fictional examples show the documents and checks a plant team can review before a pilot.

THEME 1: NON-INVASIVE EXTRACTION

Plan approved read-only telemetry access. Confirm controller load, operating limits and recovery steps with the plant team.

THEME 2: UNIFIED EDGE NAMESPACE

Transforms proprietary field tags into an ISA-95 standard semantic hierarchy using HighByte and report-by-exception MQTT Sparkplug B.

THEME 3: PURDUE & GXP HARDENING

Strict IEC 62443 conduits. Outbound-only TLS 1.3 pushes data to Layer 3.5 IDMZ without exposing Level 1/2 control networks to IT.

PILLAR 1 • L1/L2 Controlled Access

Non-Invasive Extraction

Read-only connection architecture preserving deterministic controller scans.

Read-Only Driver Configurations

Kepware / OPC-UA read-only channels. Zero remote writes to PLC memory.

Local Non-Volatile Edge Spooling

Example: local edge storage buffers telemetry. Capacity depends on data rate, retention settings and available storage.

Policy: Zero In-Flight PLC Rewrites

Refusal to touch active ladder logic or safety routines during discovery/pilots.

Trade-Off: Rejects open-ended ladder logic patching.

PILLAR 2 • L2/L3 Semantic Hub

Edge Contextualization

Transforming raw bits and registers into standardized ISA-95 models.

HighByte Semantic Modeling

Normalizes Allen-Bradley UDTs and Siemens DBs into unified namespaces.

MQTT Sparkplug B Transport

Report-by-exception transport can reduce repeated traffic. Measure the result against the site baseline.

Strict Interface Data Contracts

Explicit schema freeze protecting downstream historians, MES, and Power BI.

Trade-Off: Rejects brittle point-to-point SQL integrations.

PILLAR 3 • L3/L3.5 Purdue Hardening

Security & GxP Integrity

Example network boundaries and audit records for review by the site engineering and quality teams.

Dual-NIC Hardware Isolation

Physical segregation with Linux kernel ip_forward=0 and iptables DROP.

Outbound-Only TLS 1.3 Streams

Edge initiates connection to port 8883. Zero inbound listening ports in OT.

ALCOA+ Data Integrity Assurance

Timestamp and audit record design for quality review; compliance requires system-specific assessment and validation.

Trade-Off: Rejects inbound cloud-to-PLC command access.

Select an Operational Node Above to Inspect

READY

Operational Activity

Click any node above to inspect concrete engineering execution details.

Reinforcement Vector (Why it amplifies the system)

Examines how this practice reinforces other operational components.

Structural Trade-Off (What Buntop Refuses)

Highlights the common industry revenue stream Buntop deliberately turns down.

TECHNICAL SPECIFICATION STANDARD

Recommended Technical Schema Specifications

In brownfield OT/IT projects, ambiguity causes controller downtime and network loops. Buntop mandates two deterministic schemas: the 9-Field OT Interface Matrix (governing cross-boundary data contracts) and the 8-Field OT Network Risk Register (governing physical safeguards and observable site proof).

Schema 1: 9-Field OT Interface Matrix Specification

Captures every physical and logical path crossing Purdue network zones.

MANDATORY DATA CONTRACT

Field Name	Type & Constraints	Purdue Validation Rule	Plant Safeguard & Operational Purpose
Interface ID	String (e.g. IF-01)	Unique alphanumeric key	Provides deterministic traceability across electrical schematics, IT firewall tickets, and software tags.
Source Asset (Purdue Level)	String + Level [L1–L4]	Must designate originating tier	Identifies exact PLC or sensor generating data; prevents unmapped shadow devices on machine subnets.
Destination Asset (Purdue Level)	String + Level [L1–L4]	Designates receiving node	Restricts data movement to authorized consumers (e.g., OnLogic Edge IPC, HiveMQ Broker).
Physical Media / Port	Physical Port + Switch ID	Exact patch identifier	Prevents electricians from pulling the wrong patch lead or connecting unauthorized ports during maintenance.
Transport / Protocol	Layer 4 port + protocol	Approved protocol list	Specifies EtherNet/IP CIP (44818), S7comm (102), Modbus TCP (502), or MQTTS (8883) for firewall rules.
Access Type	Enum (Read-Only \| Read/Write)	Strict Read-Only default	Critical safeguard preventing accidental remote write commands, recipe changes, or remote machine cycles.
Payload & Scan Rate	Tag count + scan rate ms	Floor ≥ 1000 ms for L1	Prevents polling storms that trip motion loops or watchdog timers on running production machines.
Failure / Drop Behavior	Documented state transition	Fail-safe deterministic action	Ensures PLC runs unhindered if network or broker drops; triggers local NVMe/SQLite spooling.
Data Owner	Named engineer / role	Single accountable contact	Assigns accountable site controls or IT personnel for authorization, sign-off, and incident escalations.

Schema 2: 8-Field OT Network Risk Register Specification

Defines failure modes, engineering controls, residual scores, and physical verifications.

AUDIT PROOF STANDARD

Field Name	Metric / Standard	Description & Validation Rule
Risk ID	Sequential (RSK-01)	Standard tracking index for cross-referencing audit packages and site sign-offs.
Hazard / Failure Mode	Technical threat event	Concrete failure scenario (e.g., PLC CPU Overload, ARP Conflict, Dual-NIC Bridge Breach).
Affected Asset / Zone	Asset name + Purdue Level	Specifies the physical equipment or network zone vulnerable under IEC 62443 conduits.
Pre-Mitigation Score	P × I (1 to 25)	Probability (1–5) × Impact (1–5) prior to implementing engineering safeguards.
Preventative Control	Architectural safeguard	Concrete measure engineered into the pilot (e.g., dual-NIC isolation, 1000ms floor, Sparkplug B).
Contingency / Rollback	Immediate action protocol	Operational steps executed immediately if failure manifests on-site (e.g., physical patch disconnect).
Post-Mitigation Score	P × I (Target ≤ 5)	Residual risk calculated after safeguards are verified. Must achieve low or acceptable threshold.
Observable Verification	Measurable site test	Observable engineering method verifying control is functioning (e.g., Wireshark capture, Studio 5000 trace).

Sample OT Interface Matrix

PRODUCTION REFERENCE

Complete brownfield data contract across Rockwell, Siemens, HighByte, and Central MQTT Brokers.

Filter by Purdue Tier

Filter by Protocol

Search Keywords

ID	Source Asset (Purdue)	Destination Asset (Purdue)	Physical Media / Port	Transport / Protocol	Access Mode	Payload & Scan Rate	Failure Drop Behavior	Data Owner

Sample OT Network Risk Register

IEC 62443 CONDUIT PROOF

Populated failure modes, pre/post scores, safeguards, rollbacks, and observable verifications.

ID	Hazard / Failure Event	Zone	Pre	Engineering Safeguard / Control	Contingency / Rollback Plan	Post	Observable Verification

Sample Dual-NIC Network Separation Check

HARDWARE CONDUIT

Shows example commands and expected results for reviewing OT and IT separation. This page does not connect to equipment or inspect your network.

buntop@onlogic-edge:~#

SAMPLE RESULT: PASS

# 1. Checking Linux Kernel Packet Forwarding Flag (Must be 0)
root@onlogic-edge:~# sysctl net.ipv4.ip_forward net.ipv6.conf.all.forwarding
net.ipv4.ip_forward = 0
net.ipv6.conf.all.forwarding = 0

# 2. Inspecting Routing Table (Only 1 default gateway on eth1/DMZ)
root@onlogic-edge:~# ip route show
default via 10.10.20.1 dev eth1 proto static metric 100
10.10.20.0/24 dev eth1 proto kernel scope link src 10.10.20.50
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.50
[STATUS] No routing entry exists between eth0 (OT) and eth1 (DMZ). Cross-traffic blocked.

# 3. Checking Firewall FORWARD chain drop policy
root@onlogic-edge:~# iptables -L FORWARD -v -n
Chain FORWARD (policy DROP 0 packets, 0 bytes)
DROP all -- eth0 eth1 0.0.0.0/0 0.0.0.0/0
DROP all -- eth1 eth0 0.0.0.0/0 0.0.0.0/0

Example Configuration Script for Engineering Review

#!/usr/bin/env bash
# Buntop Automation - Dual-NIC Gateway Isolation Script
set -euo pipefail

# 1. Permanently disable kernel routing
cat << 'EOF' > /etc/sysctl.d/99-buntop-isolation.conf
net.ipv4.ip_forward = 0
net.ipv4.conf.all.forwarding = 0
net.ipv4.conf.default.forwarding = 0
net.ipv6.conf.all.forwarding = 0
net.ipv6.conf.default.forwarding = 0
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.all.accept_redirects = 0
net.ipv4.conf.all.rp_filter = 1
EOF
sysctl --system

# 2. Enforce strict firewall drop policies
iptables -P FORWARD DROP
ip6tables -P FORWARD DROP
iptables -A FORWARD -i eth0 -o eth1 -j DROP
iptables -A FORWARD -i eth1 -o eth0 -j DROP

echo "[SUCCESS] Buntop Dual-NIC Isolation Enforced."

Executive Handover Package

Sample engineering charter and draft sign-off dossier for Buntop Integrated Global Services LLC.

BUNTOP INTEGRATED GLOBAL SERVICES LLC

PLANT DATA ARCHITECTURE & MANUFACTURING INTEGRATION PRACTICE

Website: buntopautomation.com • United States / Project-based delivery

DOC ID: BNT-SAT-PLN-2026-X1

Date: November 2026

STATUS: SAMPLE — DRAFT FOR SITE REVIEW

1.0 Executive Architecture Charter

This fictional handover example outlines an edge-to-UNS pilot for site review. Actual interfaces, controller load, network controls, recovery and acceptance evidence must be agreed and tested with the plant team. This report is not a certification or authorization to implement.

2.0 OT Interface Matrix

ID	Source	Destination	Protocol	Access	Failure Behavior

3.0 OT Risk Mitigation & Contingency Measures

ID	Failure Vector	Residual	Engineering Safeguard

4.0 Stakeholder Authorization Signatures

Lead Controls Engineer

Plant Operations & Safety Sign-off

Sign: _______________________

Plant IT / OT Security Lead

Purdue Network & Firewall Validation

Sign: _______________________

Adewale Adeniran, M.S. ISE

Lead Architect, Buntop Integrated Global Services

Sign: _______________________

Explore a sample plant data architecture

BUNTOP AUTOMATION

Buntop Brownfield Activity System Map

Non-Invasive Extraction

Edge Contextualization

Security & GxP Integrity

Select an Operational Node Above to Inspect

Recommended Technical Schema Specifications

Schema 1: 9-Field OT Interface Matrix Specification

Schema 2: 8-Field OT Network Risk Register Specification

Sample OT Interface Matrix

Sample OT Network Risk Register

Sample Dual-NIC Network Separation Check

Example Configuration Script for Engineering Review

Executive Handover Package

1.0 Executive Architecture Charter

2.0 OT Interface Matrix

3.0 OT Risk Mitigation & Contingency Measures

4.0 Stakeholder Authorization Signatures