Computer networking has evolved from a discipline primarily concerned with connecting computers into a critical engineering foundation for modern business, industrial automation, cloud computing, artificial intelligence, ecommerce, and digital infrastructure.

Organizations depend on networks to operate point-of-sale systems, accounting applications, enterprise resource planning platforms, cloud services, industrial controllers, customer-facing websites, databases, and distributed applications. Network performance, security, availability, and scalability therefore have direct consequences for business productivity, customer satisfaction, operational continuity, and profitability.

However, traditional network administration frequently emphasizes the configuration of individual routers, switches, firewalls, and wireless access points. Although these skills are essential, they do not constitute a complete systems engineering methodology.

A more comprehensive approach must integrate:

1. Computer networking theory: Network architecture, protocols, internetworking, and distributed systems.
2. CCNA practical competencies: Switching, routing, addressing, network services, security, and troubleshooting.
3. Systems-oriented networking literature: Particularly Larry Peterson and Bruce Davie's Computer Networks: A Systems Approach.
4. TCP/IP internetworking literature: Particularly Douglas Comer's Internetworking with TCP/IP series.
5. Network simulation: ns-3 discrete-event simulation for controlled experimentation and performance analysis.
6. Model-Based Systems Engineering (MBSE): Requirements engineering, system architecture, interface modelling, traceability, and verification.
7. Network operations: Deployment, cybersecurity, monitoring, maintenance, and continuous improvement.

This paper proposes an integrated Network Systems Engineering framework that connects theoretical knowledge to practical implementation and operational management.

Research White Paper-Network Systems Engineering: Integrating CCNA, Computer Networks: A Systems Approach, TCP/IP Internetworking, ns-3 Simulation, and Model-Based Systems Engineering

A Strategic Framework for Network Architecture, Simulation, Verification, Deployment, and SME Digital Transformation

Prepared for: IAS-Research.com | KeenComputer.com | KeenDirect.com
Author: KEENCOMPUTER-IASR-KEENDIRECT
Date: November 2026
Research focus: Computer Networking, Network Systems Engineering, CCNA, TCP/IP, ns-3, MBSE, Network Security, and SME Digital Transformation

Executive Summary

Computer networking has evolved from a discipline primarily concerned with connecting computers into a critical engineering foundation for modern business, industrial automation, cloud computing, artificial intelligence, ecommerce, and digital infrastructure.

Organizations depend on networks to operate point-of-sale systems, accounting applications, enterprise resource planning platforms, cloud services, industrial controllers, customer-facing websites, databases, and distributed applications. Network performance, security, availability, and scalability therefore have direct consequences for business productivity, customer satisfaction, operational continuity, and profitability.

However, traditional network administration frequently emphasizes the configuration of individual routers, switches, firewalls, and wireless access points. Although these skills are essential, they do not constitute a complete systems engineering methodology.

A more comprehensive approach must integrate:

1. Computer networking theory: Network architecture, protocols, internetworking, and distributed systems.
2. CCNA practical competencies: Switching, routing, addressing, network services, security, and troubleshooting.
3. Systems-oriented networking literature: Particularly Larry Peterson and Bruce Davie's Computer Networks: A Systems Approach.
4. TCP/IP internetworking literature: Particularly Douglas Comer's Internetworking with TCP/IP series.
5. Network simulation: ns-3 discrete-event simulation for controlled experimentation and performance analysis.
6. Model-Based Systems Engineering (MBSE): Requirements engineering, system architecture, interface modelling, traceability, and verification.
7. Network operations: Deployment, cybersecurity, monitoring, maintenance, and continuous improvement.

This paper proposes an integrated Network Systems Engineering framework that connects theoretical knowledge to practical implementation and operational management.

It also establishes a strategic business model for three complementary organizations:

• IAS-Research.com: Research, engineering consulting, systems architecture, MBSE, ns-3 simulation, technical feasibility studies, and innovation.
• KeenComputer.com: Network implementation, cybersecurity, infrastructure modernization, monitoring, maintenance, and managed IT services.
• KeenDirect.com: Commercialization of network equipment, standardized network packages, technology products, and ecommerce distribution.

The central proposition is that networking should be treated as an engineered business system rather than a collection of independently configured devices.

The proposed methodology follows this lifecycle:

Understand → Specify → Architect → Model → Simulate → Implement → Verify → Operate → Improve.

This framework can be applied to SMEs, restaurants, professional offices, educational institutions, industrial facilities, engineering organizations, and AI infrastructure environments.

1. Introduction: Computer Networking as Systems Engineering

1.1 The changing role of computer networks

Computer networks are now essential operational infrastructure.

A small business may depend on a single network for:

• Internet connectivity.
• Accounting and financial applications.
• Point-of-sale terminals.
• Customer Wi-Fi.
• Employee workstations.
• Printers and document management.
• Cloud storage and backup.
• Business websites and ecommerce.
• Security cameras and access control.
• Remote administration.

Larger organizations may additionally require:

• Multiple interconnected locations.
• Data-centre infrastructure.
• Industrial control networks.
• Virtualized computing.
• Cloud and hybrid-cloud connectivity.
• High-availability services.
• Network automation.
• Security operations and compliance monitoring.

The increasing dependence on network infrastructure creates a corresponding engineering responsibility.

A poorly designed network can cause operational interruptions, security vulnerabilities, slow applications, unreliable communications, and unnecessary expenditure.

A well-designed network should support the organization's business objectives while maintaining appropriate security, performance, availability, scalability, and lifecycle cost.

1.2 From device configuration to systems engineering

Traditional network administration often begins with a device:

• Configure a router.
• Configure a switch.
• Create VLANs.
• Assign IP addresses.
• Configure wireless access.
• Establish internet connectivity.

Systems engineering begins with a different question:

What must the complete network system accomplish for its users and business processes?

The answer requires understanding:

• Stakeholder needs.
• Applications and services.
• Network users and devices.
• Communication requirements.
• Security boundaries.
• Performance expectations.
• Failure conditions.
• Recovery requirements.
• Operational responsibilities.
• Budget and lifecycle constraints.

The network is then designed as an integrated system.

This distinction is fundamental. A router can be configured correctly while the overall network remains poorly designed. For example, a business may have functioning internet connectivity but no meaningful separation between guest Wi-Fi, administrative systems, payment terminals, and internal servers.

1.3 Research objectives

This paper has the following objectives:

1. Establish the theoretical foundations of computer networking using recognized textbooks.
2. Integrate Peterson and Davie's systems approach with Comer's TCP/IP internetworking literature.
3. Connect networking theory to CCNA practical competencies.
4. Introduce ns-3 as a network simulation and research platform.
5. Apply MBSE and SysML to network requirements, architecture, and verification.
6. Develop an integrated methodology for network design and implementation.
7. Identify applied research opportunities.
8. Define the strategic roles of IAS-Research, KeenComputer, and KeenDirect.
9. Propose commercially viable network engineering services for SMEs.

2. Foundational Literature: Computer Networks as a Systems Discipline

A professional network engineer needs to understand both the architectural principles and the detailed operation of network protocols.

Two important textbook traditions provide this foundation:

• The systems-oriented approach of Peterson and Davie.
• The protocol and internetworking approach of Douglas Comer.

These works complement practical networking certifications and simulation-based engineering.

2.1 Peterson and Davie: Computer Networks: A Systems Approach

Larry L. Peterson and Bruce S. Davie's Computer Networks: A Systems Approach is an important reference for understanding networks as interconnected systems.

The sixth edition, published in 2021, provides an architectural and engineering perspective on computer networks.

The online textbook is available at:

https://book.systemsapproach.org/

Its central contribution is the explanation of networking through architecture, design decisions, implementation concepts, and performance trade-offs.

Important subject areas include:

• Network architecture.
• Layering and end-to-end communication.
• Packet switching.
• Link technologies.
• Internetworking.
• Routing.
• Congestion control.
• Resource allocation.
• Wireless and mobile networking.
• Network security.
• Network performance.

2.1.1 Why the systems approach matters

Consider a business experiencing slow access to a cloud accounting application.

A device-oriented approach might begin by replacing the router or increasing internet bandwidth.

A systems approach investigates the entire communication path:

1. Is the client connected through a reliable physical or wireless link?
2. Is the Ethernet switching infrastructure operating correctly?
3. Is the correct VLAN and IP configuration applied?
4. Is DNS resolution functioning?
5. Is routing operating correctly?
6. Is TCP experiencing retransmissions?
7. Is WAN congestion occurring?
8. Is the remote application responding slowly?
9. Is the firewall inspecting or delaying traffic?
10. Is the problem isolated to one user, one application, or the entire network?

This approach prevents premature equipment replacement and encourages evidence-based engineering decisions.

2.1.2 Architectural trade-offs

Peterson and Davie's systems perspective is particularly valuable when evaluating:

• Centralized versus distributed network services.
• Redundant versus single-path architectures.
• Different routing strategies.
• Network segmentation.
• End-to-end performance.
• Congestion and resource allocation.
• Security and operational complexity.

A network design must balance technical performance against implementation cost, maintenance requirements, and business priorities.

2.2 Douglas Comer: Internetworking with TCP/IP

Douglas E. Comer provides a complementary foundation through his Internetworking with TCP/IP series.

Internetworking with TCP/IP, Volume One: Principles, Protocols, and Architecture, sixth edition, published in 2014, is a major reference for understanding the TCP/IP architecture.

The book addresses:

• Protocol layering.
• Internet architecture.
• IPv4 and IPv6.
• Internet Protocol.
• TCP and UDP.
• Addressing.
• Routing.
• Packet formats.
• Network services.
• Internetwork communication.

2.2.1 Why Comer is important

Peterson and Davie provide a systems-level understanding of networking. Comer develops the engineer's understanding of the protocols that make internetworking possible.

For example, consider communication between a workstation and a remote web server.

The engineer must understand:

1. How the workstation obtains its IP configuration.
2. How the hostname is resolved through DNS.
3. How the local network determines the next-hop address.
4. How IP packets are constructed and forwarded.
5. How routers select forwarding paths.
6. How TCP establishes communication.
7. How reliability and retransmission work.
8. How the application exchanges data.

This knowledge is essential for diagnosing complex network failures.

2.3 Comer's implementation and application volumes

The additional volumes extend the conceptual foundation into implementation and application development.

Book	Primary emphasis	Engineering relevance
Comer, Volume I	Principles, protocols, and architecture	TCP/IP and internetwork design
Comer and Stevens, Volume II	Design, implementation, and internals	Protocol implementation and networking systems
Comer and Stevens, Volume III	Client-server programming and applications	Distributed applications and network programming
Comer, The Internet Book	Internet architecture and operation	Broader understanding of Internet services

Volumes II and III are classic implementation-oriented references. Their editions should be identified accurately when used in academic work; they should not be assumed to represent current protocol specifications.

Douglas Comer's networking publications can be reviewed through Purdue University:

https://www.cs.purdue.edu/homes/comer/netbooks.html

2.4 The Internet Book

Douglas Comer's The Internet Book, fifth edition, 2018, provides a broader explanation of the Internet and its technologies.

It is useful for understanding how individual networks, communication protocols, Internet services, and applications fit into the larger Internet environment.

For business and systems engineers, this perspective helps connect technical network design to the services that organizations consume and provide.

2.5 Integrating the literature with practical engineering

The textbooks can be mapped to the wider engineering workflow.

Knowledge source	Main question	Practical result
Peterson and Davie	How should a network system be architected?	Architecture and design decisions
Comer, Volume I	How do TCP/IP protocols operate?	Protocol understanding and troubleshooting
Comer, Volume II	How are network components implemented?	Implementation-level knowledge
Comer, Volume III	How do networked applications communicate?	Client-server application understanding
The Internet Book	How does the Internet function as a whole?	Internet architecture literacy
CCNA	How are practical networks configured?	Operational network skills
ns-3	How will a network behave under specified conditions?	Simulation and experimental results
MBSE	How are requirements and architecture managed?	Traceable engineering models

The combined reading and practical programme should develop engineers who understand the complete path from requirements and architecture to protocols, simulation, implementation, and operations.

3. CCNA: Practical Networking Competencies

The Cisco Certified Network Associate (CCNA) programme provides a practical foundation in networking technologies.

CCNA-aligned knowledge is relevant to the configuration, operation, and troubleshooting of enterprise networks.

It should be treated as one component of a broader systems engineering education.

3.1 Network fundamentals

Core subjects include:

• Network topologies.
• OSI and TCP/IP models.
• Ethernet.
• IPv4 and IPv6.
• Subnetting.
• Network addressing.
• Switching and routing fundamentals.
• Wireless networking.
• Physical and logical network components.

3.2 Network access

Important topics include:

• Ethernet switching.
• VLAN configuration.
• Trunking.
• Spanning Tree Protocol.
• EtherChannel.
• Wireless LAN architecture.
• Access-layer design.

These concepts are essential when designing networks for multiple departments, customer groups, or business functions.

3.3 IP connectivity

The engineer should understand:

• Static routing.
• Dynamic routing.
• Routing tables.
• Packet forwarding.
• OSPF fundamentals.
• Default routes.
• Routing behaviour during network changes.

Routing knowledge becomes particularly important when connecting multiple buildings, branch offices, cloud environments, and remote sites.

3.4 IP services

Important services include:

• DHCP.
• DNS.
• NAT.
• NTP.
• SNMP.
• Syslog.
• QoS fundamentals.

These services support network configuration, communication, monitoring, and operational management.

3.5 Security fundamentals

CCNA-aligned security concepts include:

• Device hardening.
• Secure management.
• Access control lists.
• Port security.
• Authentication.
• Authorization.
• VPN fundamentals.
• Network segmentation.
• Basic security monitoring.

These skills should be supplemented with a broader cybersecurity programme, including identity management, endpoint security, vulnerability management, incident response, and secure architecture.

3.6 Automation and programmability

Modern networking increasingly requires software-oriented skills.

Important topics include:

• REST APIs.
• JSON.
• Network automation.
• Configuration management.
• Controller-based networking.
• Programmability.
• Infrastructure documentation.

This creates a natural connection between networking, software engineering, DevOps, and AI-assisted operations.

3.7 CCNA as an engineering foundation

CCNA provides practical configuration and troubleshooting knowledge. However, a complete network systems engineer also needs:

• Protocol-level understanding.
• Requirements engineering.
• Architectural modelling.
• Simulation.
• Verification.
• Security analysis.
• Lifecycle management.

The combination is more valuable than certification knowledge alone.

4. Network Architecture and TCP/IP Protocol Engineering

4.1 Layered networking architecture

The OSI and TCP/IP models provide conceptual frameworks for understanding communication between systems.

The TCP/IP model can be summarized as follows.

Layer	Representative technologies	Engineering responsibility
Application	HTTP, HTTPS, DNS, DHCP, SSH, email, APIs	Application communication
Transport	TCP, UDP	End-to-end transport
Internet	IPv4, IPv6, ICMP, routing	Addressing and packet forwarding
Network access	Ethernet, Wi-Fi, physical media	Local connectivity and transmission

The engineer must understand how the layers interact.

For example, an application failure may be caused by:

• A physical cable problem.
• Wireless interference.
• An incorrect VLAN.
• An addressing error.
• DNS failure.
• Routing problems.
• TCP retransmissions.
• Firewall policy.
• Server overload.

A systems-oriented troubleshooting process investigates the complete communication path.

4.2 Internetworking

Internetworking allows independent networks to communicate through common protocols and routing mechanisms.

Important subjects include:

• IP addressing.
• Subnetting.
• Routing.
• Packet forwarding.
• Address resolution.
• Transport protocols.
• Network services.
• Security boundaries.

Comer's TCP/IP literature provides a strong foundation for understanding these mechanisms.

4.3 Protocol and service reference

Protocol or service	Function	Example engineering concern
Ethernet	Local communication	Link reliability and switching
ARP	IPv4 address resolution	Local next-hop discovery
IPv6 Neighbor Discovery	IPv6 local communication support	Address resolution and neighbour management
IPv4 / IPv6	Logical addressing and forwarding	Addressing and routing correctness
ICMP	Network control and diagnostics	Reachability and error reporting
TCP	Reliable transport	Retransmission, flow control, congestion
UDP	Connectionless transport	Loss-sensitive and latency-sensitive traffic
DNS	Name resolution	Application access and resolution delays
DHCP	Dynamic address configuration	Client network configuration
OSPF	Dynamic routing	Route selection and network recovery
SNMP	Network monitoring and management	Device status and performance
Syslog	Event reporting	Fault investigation and auditing

NAT, VPNs, firewalls, and QoS add further architectural and operational considerations.

Not every service is represented by a complete native protocol model in ns-3. The engineer must identify which functions can be simulated directly, which require additional models, and which should be abstracted.

4.4 Network design principles

A professional network architecture should address:

Modularity: Separate network functions into manageable logical and physical components.

Scalability: Allow additional users, devices, services, and locations.

Resilience: Provide appropriate redundancy and tested recovery procedures.

Security: Apply least privilege, segmentation, access controls, and secure management.

Manageability: Maintain documentation, configuration baselines, and monitoring.

Performance: Evaluate throughput, latency, jitter, packet loss, and application response.

Economics: Balance lifecycle cost against business requirements and risk.

5. ns-3: Network Simulation and Experimental Engineering

5.1 Introduction to ns-3

ns-3 is an open-source discrete-event network simulator used in networking research, education, and experimentation.

Official website:

https://www.nsnam.org/

Documentation:

https://www.nsnam.org/documentation/

ns-3 allows researchers to construct network topologies, configure communication links, generate traffic, model network conditions, and collect performance measurements.

It is particularly useful for evaluating design alternatives under controlled experimental conditions.

5.2 Why network simulation matters

A physical network testbed can be expensive and time-consuming to construct.

Simulation provides an opportunity to investigate network behaviour before equipment is purchased or deployed.

Questions include:

• How much bandwidth is required?
• What happens when a WAN link fails?
• How does congestion affect application traffic?
• How does traffic load influence delay?
• How does TCP behave under packet loss?
• How do different network topologies compare?
• What happens when the number of wireless users increases?
• How does a network respond to changes in link capacity?

Simulation does not automatically predict real-world performance. Its accuracy depends on the validity of the models, assumptions, configurations, and experimental design.

5.3 Proposed ns-3 experiments

Experiment	Research objective	Measurements
Point-to-point network	Establish baseline communication	Throughput, delay, packet loss
Star topology	Evaluate centralized connectivity	Link utilization and bottlenecks
Multi-router network	Study routing behaviour	Forwarding and route changes
TCP versus UDP	Compare transport behaviour	Throughput, loss, delay
Congestion study	Evaluate traffic contention	Queue length, delay, drops
Wireless network	Examine wireless conditions	Throughput, delivery ratio, delay
Link failure	Study resilience	Recovery and interruption
Traffic prioritization	Evaluate QoS approaches	Delay and jitter by traffic class

Each experiment should specify:

1. Research question.
2. Hypothesis.
3. Network topology.
4. Protocol and application models.
5. Simulation parameters.
6. Traffic patterns.
7. Measurement methods.
8. Number of runs and random seeds.
9. Results.
10. Limitations.

5.4 Example SME network simulation

Consider a small business with:

• One WAN connection.
• One edge router.
• One firewall.
• Two managed switches.
• Three VLANs.
• One wireless access point.
• Business workstations.
• POS devices.
• Guest devices.

A conceptual architecture is:

Internet / WAN | Edge Router | Firewall | Managed Switch | +--------------+--------------+ | | | VLAN 10 VLAN 20 VLAN 30 Office POS Guest Wi-Fi | | | Workstations Terminals Guest Devices Printers POS Server Internet Access

A simulation can examine traffic flows, link utilization, delay, packet loss, congestion, and selected failure scenarios.

The physical network implementation must separately verify the actual switch configuration, firewall rules, wireless isolation, and device behaviour.

5.5 ns-3 experiment workflow

A typical workflow includes:

1. Define the research objective.
2. Create simulation nodes.
3. Establish network links.
4. Configure link capacity and delay.
5. Assign IP addresses.
6. Configure routing.
7. Generate TCP or UDP application traffic.
8. Introduce controlled changes in traffic load or network conditions.
9. Capture packet traces.
10. Collect flow statistics.
11. Analyze performance.
12. Repeat experiments under different parameter settings.
13. Document limitations and conclusions.

5.6 Network performance metrics

Throughput

[
Throughput=\frac{\text{Successfully delivered bits}}{\text{Measurement interval}}
]

Packet loss ratio

[
PLR=\frac{\text{Packets sent}-\text{Packets received}}
{\text{Packets sent}}\times100%
]

Average one-way delay

[
D_{avg}=\frac{1}{N}\sum_{i=1}^{N}
(t_{receive,i}-t_{send,i})
]

Jitter

Jitter represents variation in packet delay. The exact calculation must be defined consistently for each experiment.

Additional measurements may include:

• Queue length.
• Retransmission count.
• Link utilization.
• Packet delivery ratio.
• Route convergence behaviour.
• Application-level response time.

5.7 Simulation limitations

ns-3 should be used with a clear understanding of its modelling boundaries.

It is not a complete replacement for:

• Physical network equipment.
• Vendor configuration testing.
• Hardware-specific performance testing.
• Security penetration testing.
• Wireless site surveys.
• Application performance monitoring.

A sound methodology compares simulation results with physical laboratory measurements wherever practical.

6. Model-Based Systems Engineering for Computer Networks

6.1 Why MBSE is important

Model-Based Systems Engineering provides a structured approach to requirements, architecture, interfaces, behaviour, and verification.

In conventional network projects, documentation may consist of disconnected spreadsheets, topology drawings, configuration files, and operational notes.

MBSE seeks to establish traceability among:

• Stakeholder needs.
• System requirements.
• Architecture.
• Components.
• Interfaces.
• Behaviour.
• Verification.
• Validation.

This is particularly valuable when a network supports business-critical applications.

6.2 Network engineering through MBSE

The proposed workflow is:

Stage 1 — Stakeholder needs

Identify business objectives, user groups, applications, risk, and operational priorities.

Stage 2 — Requirements engineering

Define measurable performance, security, capacity, availability, and service requirements.

Stage 3 — Architecture development

Define network topology, logical segmentation, routing, WAN, security boundaries, and service interfaces.

Stage 4 — Detailed design

Specify addressing, VLANs, equipment roles, configuration policies, and monitoring.

Stage 5 — Simulation and analysis

Use ns-3 to evaluate selected traffic, capacity, and failure scenarios.

Stage 6 — Verification

Develop test cases and acceptance criteria linked to requirements.

Stage 7 — Deployment and operations

Implement the network, verify the configuration, monitor performance, and maintain the engineering baseline.

6.3 SysML modelling

The Systems Modeling Language (SysML) provides modelling constructs that can support network systems engineering.

Useful model types include:

SysML model	Network application
Requirements diagram	Performance, availability, capacity, and security requirements
Use-case diagram	Network user and system interactions
Block Definition Diagram	Routers, switches, firewalls, servers, and services
Internal Block Diagram	Interfaces, connections, and communication paths
Activity diagram	Provisioning and troubleshooting workflows
Sequence diagram	Client-server and network service interactions
Parametric diagram	Capacity, traffic, delay, and performance constraints

Tools such as Sparx Systems Enterprise Architect can be used to support modelling and requirements traceability.

6.4 Example network requirements

ID	Requirement	Design element	Verification
NET-001	Guest devices must not access POS systems	VLAN and firewall policies	Segmentation test
NET-002	Business traffic must meet specified capacity requirements	WAN and traffic design	Load test and simulation
NET-003	Network faults must generate alerts	Monitoring platform	Alert injection test
NET-004	Critical services must recover from specified failures	Resilience architecture	Failover test
NET-005	Administrative access must be restricted	Management network and access controls	Access-control test
NET-006	Network configurations must be documented	Configuration management	Documentation audit

Requirements should be measurable, testable, and traceable to architecture and verification evidence.

6.5 MBSE and network digital twins

A network digital twin can maintain a digital representation of the actual network.

It may combine:

• Logical topology.
• Physical topology.
• IP addressing.
• Device inventory.
• VLAN configuration.
• Routing relationships.
• Security policies.
• Requirements.
• Monitoring data.
• Simulation models.

The objective is not simply to create a diagram. It is to maintain a useful relationship between the real network and its engineering model.

7. Integrating Networking Theory, CCNA, ns-3, and MBSE

The most important contribution of this paper is the integration of these disciplines into a unified engineering methodology.

Engineering stage	Foundation	Deliverable
Understand the network	Peterson and Davie	Systems architecture knowledge
Understand protocols	Comer TCP/IP	Protocol and internetworking model
Configure and troubleshoot	CCNA	Practical implementation
Evaluate behaviour	ns-3	Simulation and performance results
Formalize the design	MBSE and SysML	Requirements and architecture models
Validate implementation	Test engineering	Verification and acceptance report
Operate and improve	Network management	Monitoring and lifecycle service

7.1 Engineering feedback loop

The lifecycle should be iterative.

Requirements drive architecture.

Architecture drives simulation and implementation.

Simulation identifies potential weaknesses.

Physical testing validates modelling assumptions.

Operational monitoring identifies real-world problems.

Operational findings update requirements, models, and design decisions.

This feedback loop creates a more disciplined engineering process than isolated network installation and maintenance.

8. Applied Network Engineering Use Cases

8.1 SME restaurant network

Restaurants may operate:

• Multiple Wi-Fi networks.
• POS terminals.
• Accounting computers.
• Kitchen printers.
• Guest wireless devices.
• Security cameras.
• Business management systems.
• Internet-connected payment services.

The network should separate critical business systems from guest devices and other less-trusted endpoints.

A proposed architecture may include:

Segment	Devices	Security objective
VLAN 10	Administration and accounting	Protect business information
VLAN 20	POS and payment systems	Restrict access to payment-related infrastructure
VLAN 30	Guest Wi-Fi	Isolate customer devices
VLAN 40	Cameras and IoT	Restrict device communication
VLAN 99	Network management	Restrict administrative access

The actual segmentation and compliance scope must be determined by the business environment and applicable payment requirements.

Engineering considerations

• Managed Ethernet switches.
• Appropriate 24-port D-Link switches where justified.
• Router and firewall configuration.
• Bridged WAN access where supported and properly secured.
• Wireless access-point placement.
• VLAN and firewall policy.
• WAN resilience.
• Monitoring and alerting.
• Backup and recovery.

Research opportunity

Use ns-3 to investigate traffic contention, latency, and failure scenarios. Then validate the proposed architecture on physical equipment.

KeenComputer can implement the design, while IAS-Research can provide the architecture and simulation methodology.

8.2 Professional services SME

Accounting, legal, medical, and consulting organizations depend on reliable access to:

• Cloud applications.
• Document management.
• Email.
• Video conferencing.
• Customer relationship management.
• Accounting systems.
• Business websites.

Their networks should address:

• Identity and access management.
• Secure remote access.
• Endpoint security.
• Network segmentation.
• Backup and recovery.
• Secure wireless.
• Monitoring.
• Business continuity.

8.3 Industrial and engineering networks

Industrial environments introduce additional concerns:

• Operational technology segmentation.
• Industrial Ethernet.
• Supervisory control and data acquisition.
• Remote monitoring.
• Availability.
• Time-sensitive communication.
• Safety and operational constraints.

Enterprise IT and operational technology should be separated according to risk and system requirements.

Network design should consider the relevant industrial cybersecurity standards and the operational consequences of communication failures.

8.4 Data-centre and AI infrastructure

AI workloads introduce significant network requirements.

Research subjects include:

• East-west and north-south traffic.
• Storage and compute communication.
• Network bottlenecks.
• Throughput and latency.
• Traffic prioritization.
• Network segmentation.
• Workload isolation.
• Monitoring and observability.

The network architecture should be evaluated against actual workload requirements rather than relying only on theoretical bandwidth estimates.

9. Strategic Role of IAS-Research.com, KeenComputer.com, and KeenDirect.com

The three organizations can operate as complementary parts of a research-to-commercialization ecosystem.

9.1 IAS-Research: Research, innovation, and systems engineering

IAS-Research should lead the research, architecture, modelling, and engineering advisory activities.

Potential services include:

1. Network systems engineering studies.
2. Network architecture development.
3. MBSE and SysML modelling.
4. ns-3 simulation.
5. Capacity and performance studies.
6. Network resilience analysis.
7. TCP/IP and protocol research.
8. Industrial and enterprise network design.
9. Cybersecurity architecture.
10. Technical feasibility studies.
11. Research publications and white papers.
12. Proof-of-concept development.

IAS-Research can differentiate itself from conventional IT service providers by offering research-led engineering.

Instead of recommending equipment immediately, IAS-Research can define the requirements, compare architectures, evaluate performance, and document the engineering rationale.

Strategic positioning

IAS-Research: Engineering intelligence for complex technology decisions.

9.2 KeenComputer: Implementation and managed network services

KeenComputer should translate architecture and engineering recommendations into operational customer solutions.

Potential services include:

Service	Customer benefit
SME network health assessment	Identify security and performance weaknesses
LAN/WAN design	Establish a documented network architecture
Router and switch configuration	Improve reliability and maintainability
VLAN and firewall implementation	Separate business systems
Wi-Fi modernization	Improve wireless performance and security
Network monitoring	Detect problems earlier
Backup and recovery	Reduce operational disruption
Managed network operations	Provide ongoing maintenance and support

Proposed initial commercial offer

SME Network Health Assessment — CAD $199

A limited-scope assessment could include:

• Router and firewall review.
• Switch configuration review.
• VLAN and wireless security review.
• Basic WAN connectivity assessment.
• Backup and monitoring review.
• Identification of operational risks.
• Prioritized recommendations.
• A concise improvement roadmap.

The offer should clearly define its scope, exclusions, access requirements, and whether on-site work is included.

Strategic positioning

KeenComputer: Engineered IT solutions for business reliability and growth.

9.3 KeenDirect: Product commercialization and ecommerce

KeenDirect can serve as the commercial channel for network equipment and standardized solutions.

Potential categories include:

• Managed Ethernet switches.
• Routers and firewalls.
• Wireless access points.
• Network cabling.
• Network adapters.
• UPS systems.
• Monitoring solutions.
• Network security products.
• Small-business network kits.

The strongest proposition is not simply to sell hardware.

KeenDirect can package products with engineering knowledge, implementation options, documentation, and continuing support.

Example: Restaurant network package

A packaged offering could contain:

1. Managed 24-port switch.
2. Firewall/router.
3. Wireless access points.
4. VLAN architecture.
5. Configuration guidance.
6. Network documentation.
7. Installation options.
8. Acceptance testing.
9. Optional monitoring and managed services.

This model creates a stronger commercial proposition than selling individual devices.

Strategic positioning

KeenDirect: Technology products and engineered solutions for business customers.

10. Flagship Joint Initiative: SME Network Digital Twin

A major opportunity is to develop an SME Network Digital Twin methodology jointly between IAS-Research and KeenComputer.

10.1 Concept

A network digital twin is a maintained digital representation of a real network.

It may contain:

• Network topology.
• Device inventory.
• IP addressing.
• VLANs.
• Routing relationships.
• Security policies.
• Network requirements.
• Interfaces.
• Monitoring data.
• Simulation models.
• Verification records.

Its purpose is to provide a structured engineering view of the network and its operational condition.

10.2 Proposed architecture

The digital twin methodology can integrate four components.

Physical network

Routers, switches, firewalls, access points, servers, and connected devices.

Network data collection

SNMP, Syslog, configuration exports, monitoring data, and available flow records.

MBSE model

Requirements, system architecture, interfaces, dependencies, and verification.

ns-3 simulation

Selected traffic, capacity, congestion, and failure scenarios.

The combined information supports engineering decisions concerning:

• Capacity.
• Security.
• Resilience.
• Upgrades.
• Performance.
• Operational cost.

10.3 Research questions

The initiative can investigate:

1. Can MBSE improve traceability of SME network requirements?
2. Can ns-3 identify performance and resilience weaknesses before deployment?
3. How closely do simulated results match physical network measurements?
4. Can monitoring and configuration data maintain an accurate network model?
5. Can AI-assisted analysis improve troubleshooting and documentation?
6. Can the methodology be implemented economically for small businesses?

10.4 Proposed proof of concept

Develop a reference SME network containing:

• One WAN connection.
• One edge router/firewall.
• Two managed switches.
• Three VLANs.
• One wireless access point.
• Business workstations.
• Network printers.
• Guest devices.
• A monitoring server.

The project should deliver:

• Stakeholder requirements.
• IP addressing plan.
• VLAN plan.
• Network topology.
• SysML diagrams.
• ns-3 simulation model.
• Physical lab implementation.
• Performance measurements.
• Fault-injection test results.
• Configuration documentation.
• Final engineering report.

The comparison between simulation and physical results will be particularly valuable.

It can help establish which simulation assumptions are appropriate for SME network design.

11. AI-Assisted Network Engineering

Artificial intelligence provides an additional research and commercialization opportunity.

Large Language Models and Retrieval-Augmented Generation can support network documentation, troubleshooting assistance, and technical knowledge retrieval.

11.1 Potential applications

• Search network equipment manuals.
• Interpret configuration documentation.
• Explain monitoring alerts.
• Retrieve historical incident records.
• Assist with troubleshooting.
• Generate change documentation.
• Explain protocol behaviour.
• Map operational findings to requirements.
• Produce draft network assessment reports.

11.2 Proposed architecture

An AI-assisted network engineering platform could combine:

• Network documentation repository.
• Vendor manuals.
• Configuration records.
• Syslog and monitoring data.
• RAG knowledge retrieval.
• LLM-based reasoning assistance.
• Human-reviewed engineering workflows.

The system should not autonomously make high-impact network changes without appropriate review and authorization.

Configuration changes must be tested, access-controlled, documented, and managed through formal change procedures.

11.3 Strategic value

IAS-Research can investigate the architecture and technical feasibility.

KeenComputer can integrate the platform into managed IT operations.

KeenDirect can commercialize compatible software, monitoring products, and implementation packages.

This creates an opportunity to combine network engineering with the wider AI research and software engineering capabilities of the organizations.

12. Implementation Roadmap

A 12-month programme can establish the technical foundation and initial commercial offerings.

Period	IAS-Research	KeenComputer	KeenDirect
Months 1–2	Review literature; define MBSE methodology	Build CCNA-aligned lab	Identify equipment categories
Months 3–4	Develop ns-3 experiment library	Develop standard assessment procedure	Design network equipment bundles
Months 5–6	Develop SME network architectures	Implement pilot networks	Publish initial packages
Months 7–8	Compare simulation and physical results	Establish monitoring and support processes	Expand product catalogue
Months 9–10	Develop digital twin proof of concept	Refine implementation methodology	Improve ecommerce integration
Months 11–12	Publish research and technical report	Launch repeatable managed service	Expand network product offerings

12.1 Technical performance indicators

Potential KPIs include:

• Network availability.
• Throughput.
• Latency.
• Jitter.
• Packet loss.
• Mean Time to Detect.
• Mean Time to Repair.
• Backup success.
• Recovery test success.
• Security configuration compliance.

12.2 Business performance indicators

Potential business KPIs include:

• SME assessments completed.
• Assessment-to-project conversion rate.
• Recurring managed-service revenue.
• Customer retention.
• Average project delivery time.
• Support cost per customer.
• Product bundle sales.
• Customer satisfaction.
• Documented operational improvements.

Targets should be defined after establishing baseline measurements.

13. Risks and Engineering Limitations

Risk	Potential impact	Mitigation
Incorrect simulation assumptions	Misleading conclusions	Validate against physical measurements
Incomplete requirements	Poor architecture	Apply stakeholder and requirements analysis
Treating CCNA as complete systems engineering	Architectural gaps	Supplement with theory, MBSE, and verification
Inadequate network segmentation	Security exposure	Define and test security boundaries
Overly complex SME designs	High operating cost	Match architecture to business needs
Vendor-specific behaviour	Simulation mismatch	Document equipment assumptions and test physically
Incomplete documentation	Difficult maintenance	Maintain configuration baselines
Uncontrolled configuration changes	Operational disruption	Apply change management and rollback procedures
Poor monitoring	Delayed fault detection	Establish measurable operational monitoring

Simulation should not be presented as proof that a physical implementation will work under all conditions.

Physical testing, configuration validation, security assessment, and operational monitoring remain essential.

14. Research and Academic Opportunities

The combined methodology provides several opportunities for applied research and technical publication.

14.1 Network performance and congestion

Study how traffic patterns, link capacity, queue sizes, transport protocols, and packet loss influence end-to-end performance.

14.2 Resilient SME network architecture

Investigate the trade-offs between single-WAN and dual-WAN architectures, redundant switching, alternative routing, and failover strategies.

14.3 MBSE for enterprise networking

Develop reusable SysML modelling patterns for:

• Network requirements.
• Logical architecture.
• Physical architecture.
• Interfaces.
• Security boundaries.
• Verification.

14.4 Simulation-to-implementation validation

Compare ns-3 results against physical measurements.

Research should examine:

• Throughput.
• Delay.
• Packet loss.
• Congestion.
• Recovery behaviour.
• Model limitations.

14.5 AI-assisted network operations

Investigate RAG and LLM systems for network documentation, troubleshooting, knowledge retrieval, and operational decision support.

14.6 Network digital twins for SMEs

Develop a methodology that is affordable and maintainable for small organizations.

The goal should be a practical digital representation that improves engineering decisions without requiring the extensive infrastructure associated with large telecommunications or industrial digital twin platforms.

15. Commercialization Strategy

The technical framework should lead to repeatable products and services.

15.1 Proposed service portfolio

Offering	Lead organization	Revenue model
SME Network Health Assessment	KeenComputer	Fixed-price assessment
Network Architecture and MBSE Study	IAS-Research	Engineering consulting
ns-3 Network Simulation Study	IAS-Research	Project-based research
Network Modernization	KeenComputer	Implementation project
Managed Network Operations	KeenComputer	Monthly recurring service
SME Network Equipment Packages	KeenDirect	Product sales
Network Digital Twin	IAS-Research + KeenComputer	Engineering and recurring service
AI Network Operations Assistant	IAS-Research + KeenComputer	Project and subscription opportunities

15.2 Target customer groups

The initial market can include:

• Restaurants.
• Retail stores.
• Accounting firms.
• Legal offices.
• Medical and professional clinics.
• Educational institutions.
• Small manufacturing businesses.
• Engineering consulting firms.
• Multi-location SMEs.

15.3 Positioning in the Winnipeg market

For the Winnipeg SME market, KeenComputer can focus on practical business outcomes:

• More reliable internet and network connectivity.
• Better separation of business and guest devices.
• Secure remote access.
• Improved backup and recovery.
• Better monitoring.
• Lower operational disruption.
• Documented infrastructure.
• Predictable IT support.

The offering should avoid overwhelming business owners with a catalogue of protocols and devices.

Instead, communicate the business problem, its operational consequences, the engineering solution, the expected deliverables, and the next step.

16. Strategic Recommendations

The strongest strategy is to position IAS-Research, KeenComputer, and KeenDirect as an integrated engineering and commercialization ecosystem.

16.1 Build a common technical identity

The shared theme should be:

Network Systems Engineering for Business Reliability, Security, and Digital Transformation.

This creates a coherent connection among research, implementation, and ecommerce.

16.2 Develop a reference network architecture

Begin with a practical SME network reference design.

It should contain:

• Logical and physical network diagrams.
• IP addressing plan.
• VLAN architecture.
• Firewall policy.
• WAN design.
• Wireless design.
• Monitoring architecture.
• Backup and recovery requirements.
• SysML diagrams.
• ns-3 experiments.
• Physical verification procedures.

16.3 Establish an engineering demonstration laboratory

The lab should combine:

• CCNA-aligned router and switch exercises.
• Managed Ethernet switches.
• Wireless access points.
• Linux servers.
• Firewall infrastructure.
• Network monitoring.
• ns-3 simulation.
• SysML modelling tools.
• Packet analysis and troubleshooting.

A Linux-based environment can support much of the simulation, documentation, automation, and monitoring work.

16.4 Publish research and practical implementation material

IAS-Research can publish:

• Network architecture white papers.
• ns-3 simulation studies.
• MBSE network design methodologies.
• SME network digital twin research.
• Network security architecture papers.
• AI-assisted network operations studies.

KeenComputer can publish:

• Customer-oriented implementation guides.
• Network modernization case studies.
• Security assessment packages.
• Monitoring and managed-service offerings.

KeenDirect can publish:

• Equipment packages.
• Network product comparisons.
• Installation bundles.
• Small-business networking solutions.

16.5 Develop the first commercial project

The first project should be an SME Network Engineering Reference Implementation.

It should combine:

1. Requirements analysis.
2. Systems architecture.
3. TCP/IP design.
4. CCNA-aligned configuration.
5. ns-3 simulation.
6. MBSE documentation.
7. Physical implementation.
8. Verification and acceptance.
9. Operational monitoring.
10. Commercial packaging.

This one project can generate a research publication, an implementation methodology, a demonstration laboratory, a customer case study, and a commercially reusable network solution.

17. Conclusion

Computer networking should be treated as a complete systems engineering discipline.

Peterson and Davie's Computer Networks: A Systems Approach establishes the architectural and systems perspective.

Douglas Comer's Internetworking with TCP/IP series provides the protocol, implementation, and application foundations.

CCNA supplies practical network configuration and troubleshooting skills.

ns-3 enables controlled network simulation and performance experimentation.

MBSE provides requirements management, architecture definition, traceability, and verification.

Together, these disciplines create a comprehensive engineering methodology:

Understand → Specify → Architect → Model → Simulate → Implement → Verify → Operate → Improve.

The strategic opportunity for IAS-Research, KeenComputer, and KeenDirect is to connect these stages into a coherent research-to-commercialization model.

IAS-Research develops the knowledge, architecture, simulation methods, and engineering recommendations.

KeenComputer converts these recommendations into secure, reliable, operational networks and managed services.

KeenDirect commercializes the associated equipment, standardized solutions, and technology packages.

For SMEs, the business value is clear: computer networks should not merely provide connectivity. They should support operational continuity, security, productivity, customer service, and sustainable business growth.

The long-term opportunity is to develop an affordable and repeatable Network Systems Engineering methodology that brings advanced engineering practices—traditionally associated with telecommunications, aerospace, industrial systems, and large enterprises—to the SME market.

18. References and Further Reading

18.1 Core computer networking textbooks

1. Peterson, L. L., and Davie, B. S. Computer Networks: A Systems Approach. 6th edition. Morgan Kaufmann, 2021.
   Online textbook: https://book.systemsapproach.org/
2. Comer, D. E. Internetworking with TCP/IP, Volume One: Principles, Protocols, and Architecture. 6th edition. Pearson, 2014.
3. Comer, D. E., and Stevens, D. L. Internetworking with TCP/IP, Volume Two: Design, Implementation, and Internals. Classic implementation reference.
4. Comer, D. E., and Stevens, D. L. Internetworking with TCP/IP, Volume Three: Client-Server Programming and Applications. Classic application-programming reference.
5. Comer, D. E. The Internet Book. 5th edition. CRC Press, 2018.
6. Kurose, J. F., and Ross, K. W. Computer Networking: A Top-Down Approach. Pearson.
7. Tanenbaum, A. S., and Wetherall, D. J. Computer Networks. Pearson.
8. Stallings, W. Data and Computer Communications. Pearson.

18.2 Network simulation and research

9. ns-3 Project. Official website and documentation.
   https://www.nsnam.org/
10. ns-3 Project. Model library and documentation.
    https://www.nsnam.org/documentation/
11. IEEE. IEEE Communications Surveys & Tutorials.
12. IEEE. IEEE Transactions on Network and Service Management.
13. IEEE. IEEE/ACM Transactions on Networking.

18.3 Systems engineering and MBSE

14. Object Management Group. Systems Modeling Language (SysML).
    https://www.omg.org/spec/SysML/
15. INCOSE. Systems Engineering Handbook. International Council on Systems Engineering.
16. ISO/IEC/IEEE 15288. Systems and Software Engineering — System Life Cycle Processes.
17. Sparx Systems. Enterprise Architect documentation.
    https://sparxsystems.com/

18.4 Practical networking and standards

18. Cisco. CCNA certification information.
    https://www.cisco.com/site/us/en/learn/training-certifications/certifications/enterprise/ccna/index.html
19. Cisco Networking Academy.
    https://www.netacad.com/
20. IETF. RFC Editor — Internet protocol specifications.
    https://www.rfc-editor.org/
21. NIST. Cybersecurity Framework.
    https://www.nist.gov/cyberframework
22. NIST. Computer Security Resource Center.
    https://csrc.nist.gov/

Final Strategic Proposition

IAS-Research + KeenComputer + KeenDirect: From Network Theory to Engineered Business Solutions.

The immediate priority should be to develop a documented SME network reference architecture, simulate its principal traffic and failure scenarios using ns-3, model its requirements and interfaces using SysML, and implement the design in a physical laboratory.

The resulting work can become:

• An IAS-Research technical publication.
• A KeenComputer network assessment and implementation package.
• A KeenDirect equipment and network solution bundle.
• A repeatable SME network modernization methodology.
• A foundation for future network digital twin and AI-assisted operations research.

The competitive advantage is not simply knowing how to configure a network. It is knowing how to engineer, evaluate, secure, implement, and continuously improve the complete network system.

Add a sharper research methodologyCreate a concrete SME reference architecture