Order Form No. 01 & Technical Onboarding Intake

Facility Subscription Order Form

Strata Plant Health & Strata Carbon Assurance Deployment Schedule
JIL Sovereign Technologies, Inc. (Trade Name: Strata Carbon Assurance)
JIL Sovereign Technologies, Inc.
Governed by Master Subscription Agreement
1. Customer & Authorized Facility Identification
Customer Legal Entity Name:  
Billing & Corporate HQ Address:  
Authorized Facility Name & Site ID: e.g., TX-MIDLOTHIAN-01 -
Facility Physical Address (County/State):  
EPA GHGRP Facility ID (if applicable):  
TX RRC / EPA Class VI Permit No. (if appl.):  
Facility record name: [As named in the order]
2. Product Selection & Monthly Facility Pricing
Select Product Tier Included Capabilities & Retention Monthly Fee
[   ] Product 01: Strata Plant Health
(Standalone Operations)
Read-only AVEVA PI DMZ connector, sensor drift and calibration alerts, and an operational log. Agreed in the order
not published here
[   ] Product 02: Carbon Auditing
(Standalone Compliance)
Draft workpaper packet and retention for the evidence record. Any clearing fee is agreed in the order and is not published here. Agreed in the order
not published here
[   ] Unified Health + Carbon Suite
(Recommended Enterprise)
Plant health plus the draft workpaper packet. Any clearing fee is agreed in the order and is not published here. Agreed in the order
not published here
3. Facility Technical, Treasury & Verifier Contacts
Role Name & Title Email & Direct Phone
Plant Manager / Operations Lead    
Plant OT / AVEVA PI Administrator    
Treasury / Settlement Approver    
Independent CPA / PE Reviewer    
4. Order Form Execution
PROVIDER: JIL SOVEREIGN TECHNOLOGIES, INC. (TRADE NAME: STRATA CARBON ASSURANCE) CUSTOMER: [CUSTOMER LEGAL ENTITY NAME]
By: ________________________________________ By: ________________________________________
Name / Title: Jeffrey A. Mendonca, Chairman & CEO Name / Title: ________________________________
Date: ______________________________________ Date: ______________________________________
OT/IT Security & CISO Architecture Brief

Purdue Level 3.5 Zero-Write Security Architecture

Read-Only AVEVA PI DMZ Extraction, mTLS Authentication & Multi-Tenant AWS Isolation
SOC 2 Scoped (In Progress)
Johanson Group LLP
0 Inbound Firewall Ports
0 Ports
Inbound Firewall Rules
Strata cloud never initiates connections into your plant DMZ or OT network.
HTTP GET
Strictly Read-Only PI API
Service account SVC_STRATA_RO is explicitly denied Write/Create rights.
X.509 mTLS
Per-Plant Client Certs
Terminated at AWS ALB Trust Store; revocable per facility in < 1 second.
72-Hour
Local SQLite WAL Spool
Survives facility WAN outages with zero loss of 1-minute telemetry samples.
1. Purdue Enterprise Reference Architecture Isolation Diagram
PURDUE LEVEL 0-2 (Field Sensors, PLCs, DCS, SCADA Control Loops) └── [PHYSICALLY & LOGICALLY AIR-GAPPED FROM STRATA] -- Zero Strata hardware, zero PLC writes PURDUE LEVEL 3 (Plant Operations & AVEVA PI System Historian) └── AVEVA PI Data Archive & PI Asset Framework (Strata_Compliance_Facility_Template) ▲ Internal HTTPS GET /piwebapi/streamsets/{webId}/value (Kerberos / Read-Only SVC_STRATA_RO) | PURDUE LEVEL 3.5 (Customer OT/IT DMZ Utility VM) └── Containerized Strata PI DMZ Agent (strata_pi_dmz_agent_aws.py) + 72h SQLite WAL Spool │ Outbound TCP 443 ONLY (TLS 1.3 + Per-Facility X.509 Client Certificate mTLS) ▼ PURDUE LEVEL 4/5 (Strata production control plane) ├── Client-certificate check, then the live and backfill queues ├── PostgreSQL 16 (isolated, FORCE ROW LEVEL SECURITY, NOBYPASSRLS) └── Object-lock archive (COMPLIANCE mode, 15-year retention through 2041)
2. Plant IT / OT CISO Verification Checklist
Security Control Domain Verifiable Implementation Guarantee
Network Firewall Posture Requires solely a single outbound firewall allow rule on TCP 443 from the DMZ utility VM to ingest.stratacarbonassurance.com. Zero inbound ports opened.
PI Historian Access Control SVC_STRATA_RO is granted strictly Read permissions on the target facility AF element tree and mapped PI Points. PI Data Archive audit logs confirm zero write calls.
Cryptography & Key Management TLS 1.3 in transit; AES-256 at rest with per-tenant encryption keys. Evidence anchor transactions are signed inside FIPS 140-3 Level 3 HSMs (ECC_SECG_P256K1).
Cross-Tenant Isolation PostgreSQL FORCE ROW LEVEL SECURITY bound to transaction-scoped SET LOCAL app.current_tenant_id prevents cross-tenant data access even under connection pooling.
SOC 2 SOC 2 is in progress with Johanson Group LLP. No report has been issued.