support@amerinets.com San Jose, CA · Bay Area & US Remote
408.714.8151 24/7 SLA-ready
AMERINETS
Request SOW →
Industrial facility
Home/Projects
Project Profiles

Five engagements. Real outcomes. Anonymized.

Codename-styled case studies covering semiconductor manufacturing, healthcare, public education, specialty chemicals, and mid-market SaaS. Identities and identifying details withheld under standard confidentiality terms. Full references available after mutual NDA.

Jump to case study
01Project Atlas 02Project Beacon 03Project Cedar 04Project Delta 05Project Echo
Case 01 · Manufacturing Project Atlas Semiconductor manufacturing environment

Project Atlas — Multi-Site Data Center Fabric Refresh

Global Semiconductor & Technology Manufacturer · Multi-site corporate and manufacturing infrastructure
Industry Semiconductor Mfg
Environment 3 sites · US / CA / MX
Duration 14 weeks
Engagement Senior-led delivery · C2C
The Scope
  • Support 24/7 research lab and manufacturing uptime across 3 production sites
  • Modernize data center core fabrics ahead of a new product line rollout
  • Enforce strict network segmentation between research, manufacturing, and corporate
  • Maintain cross-border MPLS WAN SLA compliance throughout the engagement
The Challenges
  • Cutover had to occur within a single weekend maintenance window per site
  • Production lines had zero tolerance for unplanned downtime — a single misstep cost the client measurable yield
  • Cross-border configuration drift had to be normalized without affecting live traffic
  • Compliance audit window was scheduled 6 weeks after cutover — documentation had to be audit-ready on day one
The Delivery
  • Deployed redundant Cisco Nexus 9K vPC server switch topologies across all 3 data centers
  • Palo Alto firewall clusters with synchronized cross-site policy and HA failover
  • Cisco ISE 802.1X NAC for endpoint enforcement in research lab networks
  • Standardized configuration templates rolled out across all sites, with per-site overrides only where required
The Outcome
  • 3-site cutover completed within a single weekend window with zero unplanned downtime
  • Cross-border MPLS WAN SLA maintained throughout the 14-week engagement
  • Full audit-ready documentation package delivered to client on completion
  • Standardized configuration baseline inherited by internal network team for ongoing operations
Outcome
  • Zero unplanned downtime during a 3-site production cutover
  • Audit-ready documentation delivered within 6 weeks of cutover
  • Configuration baseline adopted as the internal standard
What Made It Work
  • Pre-staged configurations validated in a lab environment against realistic topology emulations before touching production — no production device saw an untested change
  • Rollback plan tested, not theorized — every change had a rehearsed exit path with explicit rollback triggers
  • Direct engagement with the client's on-site network leads at each site for tribal knowledge that wasn't in the documentation
Tech Stack
Cisco Nexus 9K vPC Palo Alto NGFW Cisco ISE 802.1X MPLS WAN BGP VRF
Case 02 · Healthcare Project Beacon Healthcare clinical environment

Project Beacon — Clinical Network Segmentation & 802.1X Rollout

Regional Healthcare System · 8 facilities across clinical and administrative networks
Industry Healthcare
Environment 8 facilities · 2,400+ endpoints
Duration 10 weeks
Engagement Senior-led delivery
The Scope
  • Segment clinical networks from administrative networks across 8 facilities
  • Roll out 802.1X authentication across wired and wireless endpoints
  • Establish posture assessment for medical, administrative, and personal devices
  • Prepare documentation package for upcoming HIPAA-adjacent compliance audit
The Challenges
  • Mixed-OS medical devices with limited or no 802.1X supplicant support — couldn't be enforced
  • Existing switch infrastructure was a mix of EOL and current — phased rollout required
  • Wireless coverage for clinical areas had to be maintained during cutover (life-safety dependency)
  • Audit window was 10 weeks out — no room for rework or extended timelines
The Delivery
  • Cisco ISE 802.1X phased rollout starting with admin networks, then clinical
  • MAB (MAC Authentication Bypass) fallback profile for legacy medical devices
  • Dedicated VLAN and ACL structure for medical device traffic with documented exception list
  • Posture assessment policy with remediation workflows for non-compliant endpoints
  • Wireless re-design for clinical coverage gaps, with coverage validation site survey
The Outcome
  • 802.1X enforcement active on 2,100+ endpoints at engagement close
  • Medical device network fully isolated with documented exception list and quarterly review process
  • Audit documentation accepted with no revision requests
  • Wireless coverage complaints in clinical areas reduced to near zero
Outcome
  • 802.1X enforced across 2,100+ endpoints with zero clinical workflow disruption
  • HIPAA-adjacent audit documentation accepted with no revision requests
  • Clinical wireless coverage complaints resolved through re-design
What Made It Work
  • Started with a full device discovery to identify what would and wouldn't support 802.1X — guided the entire rollout plan and the MAB fallback policy
  • Built an exception register up front, not as an afterthought — the auditor could see the rationale for every non-802.1X device
  • Coordinated cutover windows with the clinical engineering team, not just IT — the people who understood which devices were actually life-safety
Tech Stack
Cisco Catalyst 9300 Cisco Catalyst 9200 Cisco ISE 802.1X Cisco WLC Meraki MR MAB Fallback VLAN Segmentation
Case 03 · Public Sector Project Cedar Public education technology environment

Project Cedar — Multi-Site Network Discovery & EOL Refresh

Regional Public Education & Municipal Infrastructure · Distributed municipal buildings and school campuses
Industry Public Sector / Education
Environment 40+ sites · 12,000+ users
Duration 6 months
Engagement Senior-led delivery · public-sector procurement
The Scope
  • Resolve undocumented legacy network closets across 40+ sites
  • Replace aging EOL switches with standardized platforms
  • Establish campus-wide wireless coverage with central management
  • Deliver audit-ready documentation package for state-level compliance review
The Challenges
  • Many closets had no documentation going back 5+ years — physical inventory was the only starting point
  • Site access was constrained to specific maintenance windows during school breaks
  • Standardized templates had to work for both elementary and high school traffic patterns
  • State compliance audit was scheduled — no slip allowed
The Delivery
  • Full physical and logical network discovery across all 40+ sites, with photo documentation per closet
  • Detailed Visio L2/L3 topologies, rack elevations, and port-level documentation
  • 3-Tier Cisco Catalyst 9500/9300/9200 deployment with templated configurations
  • Meraki cloud-managed switching for smaller sites, MX firewalls, and centrally-managed APs
  • Standardized configuration templates intentionally easy for an internal team to maintain after the engagement ended
The Outcome
  • Documentation package passed state compliance audit on first submission
  • Standardized templates reduced per-site deployment time by 60%
  • Wireless coverage gap reports from schools dropped to near zero
  • Standardized configuration baseline inherited by internal IT for ongoing operations
Outcome
  • State-level compliance audit passed on first submission with zero revision requests
  • 60% reduction in per-site deployment time through templated configurations
  • 40+ sites documented to Visio standard from undocumented baseline
What Made It Work
  • Treated documentation as a deliverable from day one, not an afterthought — every closet visit produced a photo set, a port map, and a topology delta
  • Built configuration templates that were deliberately easy for an internal team to maintain after the engagement ended, not over-engineered for senior engineers
  • Spent time with the facilities team to understand the actual physical access constraints before scheduling cutovers
Tech Stack
Cisco Catalyst 9500 Cisco Catalyst 9300 Cisco Catalyst 9200 Meraki MS Meraki MX Meraki MR Microsoft Visio 3-Tier Architecture
Case 04 · Industrial Project Delta Industrial chemical processing facility

Project Delta — ICS / SCADA Isolation on a Global MPLS Backbone

Global Specialty Chemical Manufacturing Corporation · International multi-plant with corporate administration
Industry Specialty Chemical Mfg
Environment 6 plants · 4 countries
Duration 8 months
Engagement Senior-led delivery · global IT/OT coordination
The Scope
  • Isolate industrial control systems (ICS / SCADA) from standard enterprise traffic
  • Maintain unified global routing across international sites
  • Preserve manufacturing operations through all configuration changes
  • Deliver consistent architecture blueprint for global IT and OT operations
The Challenges
  • Plant operations ran 24/7 — no maintenance windows for the manufacturing floor
  • IT and OT had historically operated as separate organizations with different priorities, success metrics, and change windows
  • Configuration changes had to be coordinated across multiple time zones
  • Regulatory environment required documented change control for any plant-floor touch
The Delivery
  • Global 3-Tier Cisco routing and switching architecture over MPLS backbone
  • VRF segmentation to isolate IT, OT, and guest traffic on shared infrastructure
  • HSRP default gateway redundancy across the distribution layer at every site
  • Cisco ASA firewalls with consistent policy template rolled out globally
  • Recorded architecture walkthroughs and runbooks for the internal network team
The Outcome
  • SCADA traffic isolated from enterprise traffic with zero impact on plant operations
  • IT and OT network operations now operate from a single architectural blueprint across all international sites
  • Regulatory change control documentation passed review on first submission across all six plants
  • Handoff to internal network team with recorded architecture walkthroughs and runbooks
Outcome
  • SCADA / OT traffic isolated from enterprise traffic with zero plant-floor impact across 6 sites
  • Unified architectural blueprint for global IT and OT operations
  • Regulatory change control documentation passed on first submission
What Made It Work
  • Treated IT and OT stakeholders as separate customers with separate success criteria — separate status reports, separate change windows, separate escalation paths
  • Pre-staged every configuration in a lab that emulated the MPLS topology before shipping to the field
  • Used a "smallest possible change" approach for plant-floor work — every modification was a contained, reversible unit with explicit blast radius
Tech Stack
Cisco 3-Tier MPLS WAN VRF HSRP Cisco ASA BGP OSPF ICS / SCADA
Case 05 · SaaS / Mid-Market Project Echo Modern technology office environment

Project Echo — HQ Network Refresh & Hybrid Cloud Cutover

Mid-Market SaaS Company · Single headquarters, four floors, hybrid cloud with AWS Direct Connect
Industry SaaS / Technology
Environment 1 HQ · 280 employees · 4 floors
Duration 6 weeks
Engagement Senior-led delivery
The Scope
  • Refresh the cramped main IDF that had grown organically over 5 years
  • Standardize on a single switching and wireless platform across the building
  • Maintain 99.99% uptime during the cutover — no impact to AWS-backed production
  • Clean handoff to the internal IT team with operational documentation
The Challenges
  • Main IDF was at physical capacity — structured cabling audit was the first task, not the last
  • Hybrid cloud dependency (AWS Direct Connect) meant a single routing misstep could take down production for paying customers
  • Internal IT team had limited network depth — the handoff had to be intentionally clear and operationally simple
  • The business was growing — the new design had to accommodate 50% headcount growth without another refresh
The Delivery
  • Structured cabling audit and full rack rebuild with proper cable management and labeling
  • Meraki MS switching stack with templated configurations across all 4 floors
  • Meraki MX for perimeter firewall and AWS Direct Connect routing
  • Meraki MR wireless with full coverage validation site survey across the building
  • Standardized runbooks for the most common operational scenarios, written for the internal team
The Outcome
  • Cutover completed over a single weekend with zero production impact
  • 99.99% uptime maintained during and after the engagement
  • 50% headcount growth accommodated without further infrastructure investment
  • Internal IT team trained on the new platform with documented runbooks
Outcome
  • Single-weekend cutover with zero impact to AWS-backed production
  • 50% headcount growth accommodated without infrastructure change
  • Internal IT team operating independently with documented runbooks
What Made It Work
  • Treated the structured cabling audit as a hard prerequisite — not optional, not deferred, not bundled into the cutover
  • Templated every configuration so the internal team could clone and modify rather than designing from scratch on every change
  • Did the cutover in a single maintenance window with a documented, rehearsed rollback plan — not "we'll figure it out if it breaks"
Tech Stack
Meraki MS Meraki MX Meraki MR AWS Direct Connect BGP Structured Cabling
References & Verification

References available on request.

Direct contact information for past engagement leads is provided after a mutual NDA is in place and during active proposal discussions. Specific codename-to-client mapping is held under signed confidentiality and is not shared.

Engagement References

Direct contact information for past engagement leads, available on request during active proposal discussions and after mutual NDA execution.

Confidentiality Held

Codename-to-client mapping is held under signed confidentiality. Identities are protected regardless of the prospect relationship or engagement outcome.

Detailed Case Materials

Visio topologies, runbooks, configuration templates, and post-engagement documentation can be reviewed under NDA for due diligence.

Have an engagement that resembles one of these?

If your environment looks like Project Atlas, Beacon, Cedar, Delta, or Echo — or sits in a similar operational posture — let's discuss what a comparable engagement would look like.

Start an Inquiry →