// Shared data model for Matthew Bunn's personal site // MBSE-focused positioning, real RMF/ATO work for Navy customers. const SITE_DATA = { name: "Matthew Bunn", role: "MBSE Systems Engineer", tagline: "Systems engineering, captured in models.", longTagline: "MBSE Systems Engineer at G2 Ops. SysML across requirements, architecture, and accreditation, supporting cleared Navy programs with an Active Secret clearance.", location: "Virginia", status: "Open to senior MBSE work", about: [ "MBSE Systems Engineer at G2 Ops. I work across the lifecycle in SysML and the Unified Architecture Framework, capturing requirements, modeling system architecture, and producing the artifacts downstream activities depend on. Diagrams are an output, not the source of truth.", "Recent work spans requirements generation and system modeling earlier in the V-model lifecycle, architecture authoring across complex multi-system Navy programs, and the model-based artifacts that support RMF accreditation packages across multiple cleared contracts.", "Came up the operational side: NMCI network engineering, COMSEC, and large-scale LAN/WAN, before moving into MBSE. That's why my models survive contact with the people who actually have to build, operate, and accredit the system.", "Open to MBSE and digital engineering roles across defense, private industry, or commercial, with an interest in system ownership across the lifecycle. Active Secret cleared. Security+, CCST, AZ-900, SysML v1.7.", ], now: { building: "MBSE artifacts across cleared Navy programs: requirements, architecture, and accreditation evidence in SysML", reading: "INCOSE Systems Engineering Handbook, 5th ed. · OMG SysML v2 spec · NIST SP 800-53 Rev 5", learning: "OMG OCSMP-MU certification (in progress); Cameo advanced patterns; SysML v2 transition; private-industry digital engineering practice", location: "Virginia", }, // Real project portfolio: RMF/ATO work foregrounded with concrete scope. projects: [ { id: "p01", code: "ATO-A", title: "Multi-System ATO: Architecture Artifacts", year: "2025–2026", tags: ["RMF", "ATO", "MBSE", "SysML", "Navy"], summary: "Model-based architecture artifact author for a cleared Navy ATO covering a multi-system program with deployments across several platforms. The model is the source of truth; downstream package artifacts regenerate from it.", detail: "Each subsystem has its own architecture view; deployments with shared design are combined into a single diagram, others get dedicated diagrams as configuration warrants. Updates flow from the model into the dependent artifacts rather than being re-authored by hand.", role: "MBSE Systems Engineer", stack: ["Cameo Systems Modeler", "SysML", "In-house MBSE tooling"], domain: "Navy", metrics: [ { v: "MULTI-SYSTEM", k: "SCOPE" }, { v: "MODEL-DRIVEN", k: "ARTIFACTS" }, { v: "COMBINED ATO", k: "PACKAGE" }, ], problem: "Document-centric ATO packages drift from the system the moment design changes. Hand-maintained artifacts across many subsystems multiply that drift and add cost to every revision.", approach: "Model the system once in SysML. Generate architecture views per subsystem; collapse deployments with shared design into a single view, split where they diverge. Tooling pulls model elements into ATO-package artifacts so a model edit propagates to every dependent view, system description, and report.", outcome: "Single source of truth for the architecture. Views, descriptions, and supporting artifacts regenerate from the model, shortening the change cycle for the security package.", artifacts: ["SysML architecture set", "Per-subsystem views", "System descriptions", "Architecture-package deliverables"], }, { id: "p02", code: "ATO-B", title: "Parallel-Track ATOs: Mission-Package Modeling", year: "2025–2026", tags: ["RMF", "ATO", "Mission Packages", "MBSE", "Navy"], summary: "Generating model-based architecture artifacts for a portfolio of distinct mission packages, each running its own ATO. Configuration variants warranting separate accreditation are modeled as first-class siblings rather than parameterized off a shared model.", detail: "Each package has dedicated architecture artifacts; some have subsystem-level views beneath. Where one package fielded operational variants different enough to need their own accreditation, those got dedicated models rather than being forced into a single parameterized one.", role: "MBSE Systems Engineer", stack: ["Cameo Systems Modeler", "SysML", "In-house MBSE tooling"], domain: "Navy", metrics: [ { v: "PORTFOLIO", k: "PACKAGES" }, { v: "PARALLEL", k: "ATO TIMELINES" }, { v: "VARIANT-AWARE", k: "MODELING" }, ], problem: "A portfolio of mission packages on parallel ATO timelines means parallel artifact streams. Hand-maintained packages diverge from each other and from the systems they describe, worse when one package fields multiple variants needing distinct accreditation.", approach: "Model each package; treat variants as first-class siblings with their own dedicated models when the differences warrant. Pull architecture views and system descriptions from the models for each package's ATO submission.", outcome: "Each ATO package has architecture artifacts traceable to a versioned model. Variant-specific accreditation is supported without conflating configurations.", artifacts: ["Per-package architecture views", "Variant models", "System descriptions", "Architecture deliverables"], }, { id: "p03", code: "REQS-ARCH", title: "Requirements & System Modeling: Connected Node and Pathway", year: "2025", tags: ["Requirements", "MBSE", "SysML", "Architecture", "Navy"], summary: "Generated requirements and modeled the architecture of a connected node and the end-to-end data pathway it depended on, working the front of the lifecycle in SysML and UAF.", detail: "Captured requirements directly against model elements. Modeled the node and its pathway as one connected system so requirements had something concrete to allocate against and the architecture had the requirements as constraints. Scope was reorganized away from the team during a program restructure; deliverables to that point stand as a reference pattern.", role: "MBSE Systems Engineer", stack: ["Cameo Systems Modeler", "SysML", "UAF", "Requirements management"], domain: "Navy", metrics: [ { v: "REQS+ARCH", k: "SCOPE" }, { v: "END-TO-END", k: "PATHWAY" }, { v: "FRONT OF V", k: "LIFECYCLE" }, ], problem: "Requirements and the system they depended on lived in separate documents. Nothing connected the node to the path it relied on, or to the requirements it had to satisfy.", approach: "Capture requirements against model elements. Model the node and its pathway as one connected system. Allocate requirements to architecture, surface gaps where allocation was missing.", outcome: "Connected requirement-to-architecture artifacts for the node and its pathway. Work was reassigned during a program shakeup; deliverables to that point are usable as a reference pattern for similar modeling.", artifacts: ["Requirements set", "System SysML model", "End-to-end pathway architecture"], }, ], // Network engineering roles retained as career history. Real, but not the // direction. Phrased to highlight the systems-engineering signal in them // (architecture, IA review, baseline management): the muscles MBSE uses. experience: [ { years: "May 2025 – Present", company: "G2 Ops, Inc.", role: "Systems Engineer · MBSE", note: "Used Model-Based Systems Engineering (MBSE) to drive system requirements, design, and validation across the Navy acquisition life-cycle. Developed complex system models in Cameo Systems Modeler using the SysML modeling language, ensuring seamless hardware/software integration to meet client-specific needs. Produced technical artifacts and reports supporting Navy engineering and certification activities in adherence to Unified Architecture Framework (UAF) standards and coordinated digital-engineering objectives and resources to meet quality and regulatory requirements." }, { years: "Dec 2024 – May 2025", company: "INflow Federal", role: "Network Engineer (NMCI)", note: "Designed and integrated network architectures for Navy shore-based networks as a core part of the NMCI program. Managed configuration baselines and upgrades for large-scale LAN/WAN environments supporting over 20,000 users. Conducted network design reviews with a focus on Information Assurance (IA) and cybersecurity controls, and provided high-level troubleshooting and maintenance for Cisco and Brocade network devices to ensure mission-critical uptime." }, { years: "Jun 2024 – Dec 2024", company: "INflow Federal", role: "Jr. Network Engineer (NMCI)", note: "Supported the NMCI program through the activation and configuration of network ports, ensuring optimal connectivity for Navy personnel. Installed and upgraded mission-critical hardware including routers, switches, and COMSEC/TACLANE devices. Resolved complex Layer 1–3 connectivity issues across global LAN/WAN infrastructures." }, { years: "Jul 2023 – Jun 2024", company: "G2 Ops, Inc.", role: "IT Support Technician", note: "Managed enterprise employee accounts and devices using Microsoft 365 Admin, Entra ID, and Intune. Maintained organizational security posture by implementing Azure policies and utilizing Tenable Nessus and Sophos EDR. Developed cybersecurity training and phishing simulations to mitigate social-engineering threats." }, ], education: [ { years: "Graduated Dec 2024", school: "Regent University", degree: "B.S. Cybersecurity, Virginia Beach, VA" }, ], volunteering: [ { years: "Aug 2021 – May 2023", org: "National Cybersecurity Student Association", role: "Treasurer, Regent University Student Chapter" }, ], certifications: [ "Active Secret Clearance", "CompTIA Security+", "Cisco CCST", "Microsoft AZ-900 (Azure Fundamentals)", "SysML v1.7 (Udemy, 2025)", ], // Skills lead with MBSE. RMF/ATO surfaced as its own discipline. skills: { "MBSE & Modeling": ["SysML", "UAF (project-applied)", "Cameo Systems Modeler (MagicDraw)", "Architecture Description", "Model-Based V&V"], "RMF & Accreditation": ["NIST SP 800-53", "Traditional RMF ATO", "Cyber Ready (cATO) familiarity", "Architecture artifacts for ATO packages", "Multi-system accreditation"], "Systems Engineering": ["Requirements Capture", "Architecture Development", "System Analysis", "Lifecycle Management", "Traceability", "Certification Artifacts"], "Process & Tooling": ["Jira", "FreshService", "Confluence-class wikis", "Digital Engineering", "Cisco Meraki Dashboard"], "Cleared Defense Context": ["Active Secret", "Navy acquisition", "NMCI familiarity", "COMSEC/TACLANE awareness"], "Background, Networks & IT": ["LAN/WAN Design", "Cisco / Brocade", "Aruba Wireless", "Microsoft 365 / Entra ID / Intune", "Tenable Nessus", "Sophos EDR"], }, writing: [ { date: "2021", title: "The Security Risks and Challenges of 5G Communications", kind: "publication", venue: "IGI Global", url: "https://www.igi-global.com/article/the-security-risks-and-challenges-of-5g-communications/281682", excerpt: "Peer-reviewed article on the cybersecurity attack surface introduced by 5G: spectrum, virtualization, supply chain, and edge." }, ], contact: { email: "matthew@matthew-b.com", phone: "757-270-6755", linkedin: "linkedin.com/in/matthew-bunn-e", }, }; window.SITE_DATA = SITE_DATA;