sns-network-solutions/businesses/sns-technology-group/networking/01-networking.md
Samuel James d04c611c7f organize: move all businesses into their group directories
- 00-sns-holding → 00-holdings (shorter name)
- 01-networking → sns-technology-group/networking/
- 02-digital → sns-technology-group/secure/
- 03-support → sns-technology-group/support/
- indian-food-truck-legacy merged into indian-food-truck
- warehouse-property → warehouse, rental-property → rental
- Remove empty placeholder LLC dirs
- Update READMEs with correct paths
2026-08-12 07:33:31 -05:00

3.9 KiB
Raw Permalink Blame History

01 · SNS Networking — Scaffold / Research / TODO

Status: Business #1 — ACTIVE · Tagline: The Connected Foundation Entity: SNS Networking LLC (operating subsidiary of SnS Network Solutions Holdings LLC) Liability tier: High (physical/on-site + cyber E&O) Signature accent: Signal Blue #1E6FFF Formal brief: ../../divisions/sns-networking.md

Consolidates: former Infrastructure + Secure + Systems divisions into one entity. If it touches the network, protects the network, or runs on-prem compute — it's Networking.

Scope

Physical networking & cabling

  • Structured cabling (Cat6/6A, fiber) and certification
  • Enterprise networking (Cisco, MikroTik, Ubiquiti) — routing, switching, VLANs
  • Wireless design, site surveys, Wi-Fi deployment
  • Rack build-outs, patch panels, cable management, labeling
  • Network documentation: IP schemes, rack diagrams, cable maps

Security (physical + cyber)

  • IP cameras (design, install, NVR/VMS), access control, alarms
  • Firewalls/UTM, VPN, network segmentation
  • Security audits, hardening, monitoring, incident response
  • Awareness training

On-prem systems

  • Linux server design, deployment, administration
  • Virtualization (Proxmox, KVM) and containers
  • Self-hosted infrastructure (identity, files, backups)
  • Storage, NAS/SAN, disaster-recovery design
  • Ansible automation for repeatable builds

Boundary Rules

  • Build, don't maintain. Project/build work lives here. Recurring managed contracts (SLAs, monthly monitoring, helpdesk) belong to SNS Support.
  • Not cloud. Off-prem compute (AWS, Azure, hosted) belongs to SNS Digital.
  • Not software/web. Custom apps, websites, and hosting belong to SNS Digital.

Working Documents (carried from former Infrastructure)

TODO → Launch

  • Confirm name availability: SNS Networking LLC (or retain SNS Infrastructure LLC and file assumed name)
  • Form LLC on INBiz (owner: Holdings LLC) · EIN · operating agreement
  • Business bank account (separate from Holdings)
  • Insurance: general liability + cyber E&O + workers' comp (field/low-voltage class)
  • Confirm Indiana low-voltage / alarm / security licensing requirements
  • Secure the ~$6580k loan runway (personal guarantee likely)
  • Hire the builder-operator; set up Field Nation / Work Market for labor
  • Vendor accounts (Graybar, ADI, Wesco/Anixter) + Fluke certifier
  • Finalize combined logo/branding for the consolidated entity

TODO → Security Service Line (formerly SNS Secure)

  • Confirm Indiana alarm/security licensing — blocker for physical security work
  • Decide launch shape: physical-first, cyber-first, or both
  • Pick core product lines (cameras, access control, firewall/UTM vendors)
  • Draft pricing + service packages (project vs. monitoring handoff to Support)

TODO → Systems Service Line (formerly SNS Systems)

  • Define standard reference builds (hypervisor, backup, identity, monitoring)
  • Build the Ansible baseline / IaC repo
  • Pricing: project builds vs. handoff-to-Support maintenance

Milestones

Track build milestones here once the operator is onboarded and the plan is live.

  • Licensing flag: Indiana may require a state license to sell/install/monitor burglar/fire/electronic security, access control, and CCTV — verify before physical security work.
  • Store formation docs, EIN letter, operating agreement, licenses, and insurance policies in docs/ when this splits into its own repo.