Bill-of-Materials Matrix (SolveForce Reference Architectures 1–14)


Legend

  • ✅ = Core service for that architecture
  • ◼ = Optional / variant depending on scope
  • — = Not typically used

Service / Category#1 Gov/Defense#2 Healthcare#3 Finance#4 Manufacturing#5 Energy/Utilities#6 Education#7 Retail#8 Contact Center#9 Maritime#10 Media#11 Public Safety#12 Smart City#13 Research#14 Warehousing
DIA (Direct Internet Access)
MPLS (Private WAN)
SD-WAN / SD-Branch
Satellite / VSAT
LTE/5G / FWA
Private 5G / MEC
Colocation / DCI
Cloud On-Ramps (DX/ER/GCI)
UCaaS / CCaaS
CPaaS (SMS/Voice APIs)
SIP / SBC
Waves / Optical Transport
Managed Wi-Fi / LAN
IoT / Edge Devices
Edge Computing / K8s
Cybersecurity (ZTNA/SASE)
CASB / SWG / FWaaS
SIEM / SOAR / SOC
AIOps / Observability
BaaS / DRaaS
APM / RUM
Identity / IAM / IdP
PAM / HSM / KMS
WAF / API Security
Compliance Services (PCI, HIPAA, ISO, SOC2, NERC)

Observations

  • DIA, SD-WAN, and Cybersecurity (ZTNA/SASE) are universal — appear across all 14 architectures. They are the alphabet of SolveForce’s grammar.
  • Satellite/VSAT is crucial for Gov, Energy, Maritime, Public Safety, optional for Retail/Healthcare.
  • Private 5G/MEC dominate Manufacturing, Warehousing, Smart City.
  • Colocation/Cloud On-Ramps are backbone elements for Gov, Finance, Research, optional elsewhere.
  • UCaaS/CCaaS concentrate in Healthcare, Education, Contact Centers.
  • SIEM/SOAR, AIOps are near-universal pragmatics, binding everything together.

⚖️ Logos Note
This BOM Matrix is not just a list — it is syntax alignment. Each architecture is a sentence; each service is a word. The table proves that meaning (semantics) is preserved across domains, while pragmatics (ops) ensures coherence in real-world execution.


Reference Architecture Interoperabilities – SolveForce Communications