DADIMOS BUSINESS AND TECHNOLOGY

COLLEGE
HARDWARE AND NETWORKING SERVICE LEVEL – IV
Unit of Competence: : Build a small wireless LAN
Unit one: Confirm client and equipment requirements

Prepared By Instructor Tadesse.B

 Client and organizational requirements
 Network-accessible organizational data and mission-critical applications that are
essential to the organization's operations depend on network availability.
 To design a network that meets customers' needs, the organizational goals,
organizational constraints, technical goals, and technical constraints must be identified.
 This section describes the process of determining which applications, network services
already exist, and which ones are planned, along with associated organizational and
technical goals and constraints.
 Assessing the Scope of a Network Design Project
When assessing the scope of a network design, consider the following:
 Whether the design is for a new network or is a modification of an existing network.
 Whether the design is for an entire enterprise network, a subset of the network, or a
single segment or module..
 Whether the design addresses a single function or the network's entire functionality.
 Network Design Scope Assessment
Scope of Design Comments
Entire network The backbone at the central office needs to be redesigned. All branch offices' LANs will be
upgraded to Fast Ethernet technology.

Network layer Introduction of private IP addresses requires a new addressing plan. Certain LANs must
also be segmented. Routing must be redesigned to support the new addressing plan and to
provide greater reliability and redundancy.

Data link layer The central office backbone and some branch offices require redundant equipment and
redundant links are needed. The organization also requires a campus wireless radio
frequency (RF) site survey to determine mobility deployment options and equipment scope.

Scope of Design Comments

 Identify Required Information
 Determining requirements includes extracting initial requirements from the
customer and then refining these with other data that has been collected from the
organization.
Extracting Initial Requirements
 Initial design requirements are typically extracted from the Request for
Proposal (RFP) or Request for Information (RFI) documents that the customer issues.
 An RFP is a formal request to vendors for proposals that meet the requirements that the
document identifies.
 An RFI is typically a less formal document an organization issues to solicit ideas and
information from vendors about a specific project.
 The first step in the design process should be pre-documenting (sifting, processing,
reordering, translating, and so forth) the design requirements and reviewing them with the
customer for verification and approval, obtaining direct customer input, in either oral or
written form.
Gathering Network Requirements
 Planned Applications and Network Services
 The designer must determine which applications the customer is planning to use and the
importance of each of these applications.
Using a table helps organize and categorize the applications and services planned; the
table should contain the following information:
Planned application types: Include e-mail, groupware (tools that aid group work), voice
networking, web browsing, video on demand (VoD), databases, file sharing and transfer,
computer-aided manufacturing, and so forth.
Applications: Specific applications that will be used, such as Microsoft Internet Explorer,
Cisco Unified Meeting Place, and so forth.
Level of importance: The importance of the applications—whether critical, important, or
not important is noted.
Comments: Additional notes taken during the data-gathering process.
 Organizational Goals
 Every design project should begin by determining the organizational goals that are to be
achieved. The criteria for success must be determined, and the consequences of a failure
understood.
 Network designers are often eager to start by analyzing the technical goals before
considering the organizational goals and constraints. However, detailed attention to
organizational goals and constraints is important for a project's success. In discussions
about organizational goals, the designer obtains knowledge about the customer's
expectations of the design's positive outcomes for the organization. Both short- and long-
term goals should be identified.
 Organizational goals differ from organization to organization. The following
are some typical goals that commercial organizations might have:
 Increase the operation's generated revenue and profitability. A new design should reduce
costs in certain segments and propel growth in others. The network designer should discuss
with the customer any expectations about how the new network will influence revenues and
profits.
 Shorten development cycles and enhance productivity by improving internal data
availability and interdepartmental communications.
 Improve customer support and offer additional customer services that can expedite reaction
to customer needs and improve customer satisfaction.
 Open the organization's information infrastructure to all key stakeholders (prospects,
investors, customers, partners, suppliers, and employees), and build relationships and
information accessibility to a new level.
 Organizational Constraints
• When assessing organizational goals, it is important to analyze any organizational constraints
that might affect the network design.
 Typical constraints include the following:
 Budget: Reduced budgets or limited resources often force network designers to implement
an affordable solution rather than the best technical solution.
 Personnel: The availability of trained personnel within the organization might be a design
consideration. Organizations might not have enough trained personnel, or they might not
have enough personnel.
 Policies: Organizations have different policies about protocols, standards, vendors, and
applications; to design the network successfully, the designer must understand these policies.
 Schedule: The organization's executive management must discuss and approve the
project schedule to avoid possible disagreements about deadlines.
 Table 1-5 Corporation X's Organizational Constraints

Organizational Gathered Data (Current Situation) Comments

Constraint

Budget $650,000 Budget can be extended by a maximum of $78,000

Personnel Two engineers with college degrees and Cisco Certified Network Associate ( Plans to hire additional engineers for network
CCNA) certifications for network maintenance; one has Cisco Certified Network maintenance; need technical development plan for
Professional (CCNP) certification staff
Three engineers for various operating systems and applications maintenance

Policy Prefers a single vendor and standardized protocols Current equipment is Cisco; prefers to stay with
Cisco

Schedule Plans to introduce various new applications in the next nine months New applications that will be introduced shortly are
videoconferencing, groupware, and IP telephony
 Technical Goals
Technical Goals
• The technical goals of the project must also be determined before the design starts.
• Some sample questions the designer might ask to help determine technical goals include
the following:
 What infrastructure issues exist or will exist related to your applications rollouts?
 What skill sets does your technical staff need to acquire?
 Does your current network have any performance issues?
 Which portions of your network are considered mission-critical?
• The following list describes some common technical goals:
 Improve network performance: An increase in the number of users and the introduction of
new applications might degrade network performance, especially responsiveness and
throughput.
 Decrease expected downtime and related expenses: When a network failure occurs,
downtime must be minimal, and the network must respond quickly to minimize related
costs.
 Modernize outdated technologies: The emergence of new network technologies and
applications demands regular updates to and replacement of outdated equipment and
technologies.
 Improve scalability of the network: Networks must be designed to provide for upgrades
and future growth.
 Simplify network management: Simplify network management functions so that they are
easy to use and easily understood.
• Depicts the desired technical goals that were gathered for the sample
company
Technical Goals Importance Comments
Performance 2O Important in the central site, less important in branch offices
Security 15 The critical data transactions must be secure
Availability 25 Should be 99.9%
Adaptability (to new 1O
technologies)
Scalability 25 The network must be scalable
Good network design addresses constraints by identifying possible trade-offs, such
as the following:

 Existing equipment: The network design process is usually progressive; legacy equipment
must coexist with new equipment.
 Bandwidth availability: Insufficient bandwidth in parts of the network where the bandwidth
cannot be increased because of technical constraints must be resolved by other means.
 Application compatibility: If the new network is not being introduced at the same time as
new applications, the design must provide compatibility with old applications.
 Lack of qualified personnel: Lack of qualified personnel suggests that the designer must
consider the need for additional training; otherwise, certain features might have to be dropped.
 Technical Constraints for
Technical Constraints Gathered Data (Current Comments
Situation)

Existing equipment Coaxial cable The cabling must be replaced with twisted pair to the
desktop, and fiber optics for uplinks and in the core

Bandwidth availability 64-kbps WAN link Upgrade bandwidth; change to another service provider
because the current one does not have any other links to
offer

Application IP version 6 (IPv6)-based New network equipment must support IPv6

compatibility applications
 Assigning appropriate authority
 The importance of wireless network security cannot be understated. With the proliferation of
mobile devices and the popularity of public Wi-Fi hotspots, the potential for data breaches and
other cyber security threats has increased exponentially.
 While there are many different steps that can be taken to secure a wireless network, these 12
best practices are essential for ensuring that your data and devices are safe from malicious
actors
 Enabling Two-Factor Authentication (2FA)
 Two-factor authentication adds an extra layer of security to the login process. It requires users
to enter both a username and password, as well as a code that is generated by an authenticator
app. This makes it more difficult for someone to gain unauthorized access to the network.
Using A Strong Password
 Using a strong password is one of the most important best practices for wireless network
security. A strong password is at least eight characters long and includes a mix of upper- and
lower-case letters, numbers, and symbols. Passwords should be changed regularly to ensure
that they remain secure.
 Encrypting Data
 Encrypting data is another important best practice for wireless network security. Data encryption
scrambles data so that it can only be decrypted and read by authorized users. This helps to
protect sensitive information from being accessed by unauthorized individuals.
Disabling SSID Broadcast
 Disabling SSID broadcast is another best practice for wireless network security. When SSID
broadcast is enabled, it allows anyone within range of the wireless network to see the network's
name. You can disable SSID broadcast by accessing the wireless router's configuration page and
disabling the SSID broadcast feature.
Using MAC Filtering
 Using MAC filtering is another best practice for wireless network security. MAC addresses are
unique identifiers assigned to devices that connect to a network.
Enabling WPA3 Security
 Enabling WPA3 security is another best practice for wireless network security.
WPA3 is the most recent and most secure wireless security protocol. It provides
stronger protection than WPA2 and should be used whenever possible.
 Using A VPN
 Using a VPN is another best practice for wireless network security. A VPN encrypts all traffic between a
device and the VPN server, making it more difficult for someone to eavesdrop on the connection. This is
especially important when using public Wi-Fi networks, as they are often less secure than private ones.
Disabling Remote Administration
 Disabling remote administration is another best practice for wireless network security. When remote
administration is enabled, it allows anyone with the proper credentials to access the router's
configuration page and make changes to the network. This can be a security risk, as it allows
unauthorized individuals to potentially gain access to the network.
Changing the default password
 Changing the default password is another best practice for wireless network security. Many routers come
with a default password that is easy to guess. This can be a security risk, as it allows unauthorized
individuals to potentially gain access to the network..
Using a Firewall
• Using a firewall is another best practice for wireless network security. A firewall helps to
protect the network by blocking incoming traffic that is not authorized. This can be especially
important in preventing attacks from malware and other malicious software.
 Disabling UPnP
 Universal Plug and Play (UPnP) is a protocol that allows devices to automatically discover
and connect to each other. This can be a security risk, as it allows unauthorized devices to
potentially gain access to the network. To disable UPnP, access the wireless router's
configuration page and disable the feature. You can also disable UPnP on individual devices
by accessing the settings menu.
Disabling Unnecessary Services
 You often find that routers come with a number of unnecessary services enabled. These can
be a security risk, as they can provide potential attackers with information about the network.
To disable unnecessary services, access the wireless router's configuration page and disable
any services that are not needed. This will help to reduce the attack surface of the network.
Common unnecessary services include things like telnet, SSH, and HTTP.
 Wireless device technical requirements
 Requirements define what the wireless network must do, which provides the foundation for
the design. Requirements for a wireless network include needs, such as signal coverage in all
elevators and support for voice telephony.
 Leave the technical details, such as specific technologies (such as 2.4GHz vs. 5GHz
802.11n), components, and configuration settings to the designers after all requirements are
well-defined and agreed upon.
Before implementing a wireless network, consider the following types of
requirements
Applications. the wireless network must support user applications, so be sure to fully
define them in the requirements. This could be general office applications, such as web
browsing, email, and file transfer, or it could be wireless patient monitoring in a hospital or
voice telephony in a warehouse.
Environment.
 Provide a description of the environment where the wireless network will operate. For
buildings, include the floor plan, type construction, and possible locations for mounting
access points. For outdoor areas, include satellite images, aerial photographs, or drawings.
Walk through the areas to verify accuracy of these items.
Coverage areas.
 This describes where users will need access to the wireless network. They might only need
connectivity in their offices and conferences rooms, but they may also need connectivity
inside power utility rooms and the cafeteria. Also, carefully think about whether coverage is
needed in stairwells, elevators, and parking garages.
Client devices.
 You should specify the client devices (and existing client radios) to ensure the solution
accommodates them in the most effective manner.
 This provides a basis for deciding on the type of client radios to specify for other client
devices during the design and whether there is a need to support legacy devices (i.e.,
802.11b/g).
Existing infrastructure.
 Be certain to describe all existing applicable infrastructure. Identify locations and availability
of communications closets, switch types and available ports, PoE interfaces, fiber runs,
conduit, authentication servers, VPN ports, and operational support systems.
Security.
 Describe the sensitivity of the information that will traverse the wireless network. If possible,
cite existing corporate wireless security policies. You will likely need to require encryption and
authentication of all client devices. Be sure to give security requirements plenty of thought so
that you design a solution that will protect the company’s valuable resources
Funding.
 The requirements stage of a wireless network project is a good time to ask how much money is
available. If funding limits are known, then you will know how much there is to work with
when designing the system.
Schedules.
 Of course, a company will generally want the wireless network installed “yesterday,” but we
all know that is impossible. You will need to nail down a realistic completion date, though, and
plan accordingly.
 Identify components to be installed to meet the technical requirements
• Technical requirements are important because they describe how software should function and what
its behavior should be.
• This helps developers and users to understand the best way to use the software.
• A document of clearly defined specifications helps to create a project or software that has a proper
process for implementation.
• Developers and other technicians refer to this as technical requirement documentation.
• Technical requirements vary depending on the product or industry. However, there is no all-
encompassing list of technical requirements that apply to every project or development here is a
sample list of technical requirement examples:
Accessibility
Authentication and authorization
Availability
Information security
Maintainability
Performance
Privacy
Reliability
 Selecting appropriate position for access point
 Wireless Access Point (WAP) placement is an important aspect of setting up and maintaining
a wireless network. Proper placement of WAPs ensures good coverage, capacity, and
performance.
 Here are some best practices for WAP placement:
a) Conduct a site survey: Before installing any WAPs, conduct a Wireless site survey to
identify areas with poor coverage, high demand, and potential sources of interference. This
will help you to determine the optimal location for each WAP.
b) Use ceiling-mounted WAPs: Ceiling-mounted WAPs provide better coverage than wall-
mounted WAPs, as they can reach a wider area and provide more uniform coverage.
c) Place WAPs in the center of the coverage area: In general, WAPs should be placed in the
center of the area they are supposed to cover, as this will ensure good coverage for the
entire area.
d) Avoid physical obstructions: Physical obstructions such as walls, ceilings, and furniture
can interfere with wireless signals, so it’s important to avoid placing WAPs near these
types of obstructions.
E ) Use multiple WAPs: In large areas, it’s important to use multiple WAPs to ensure good
coverage and capacity. This will also help to reduce the risk of congestion and ensure that users
have a good experience.
F ) Use Power over Ethernet (PoE): PoE allows WAPs to receive power over the same cable
that carries the network data, making it easy to install them in a variety of locations.
G ) Use wireless planning tools: wireless planning tools can help to predict coverage,
capacity, and performance of wireless networks, by simulating the environment and giving you
an idea of how the wireless network will perform.
Access Point Placement Guidelines for Successful Installation
 In order to build a wireless network infrastructure, a company needs to consider the
placement of multiple access points around their campus. Access points connect to a wired
network and allow devices to connect to that network via the access point wirelessly. They
are the cornerstone of wireless networking; as such, knowing how to properly install them is
essential. Physical access point placement plays a huge part in this installation process.
 we have outlined five guidelines for you to follow when installing access points.

1. Place access points where Wi-Fi will be used the most

 The first rule of proper access point placement is to determine the locations where Wi-Fi
networks will be used the most.
2. Precise access point placement is key
 Access point placement is not just about picking the right general area to install a device.
3. Avoid coverage overlap whenever possible
 When designing your wireless infrastructure, you need to select the best access point
locations that will provide maximum coverage for your business.
4. Electronic devices
 Devices that emit electromagnetic signals, such as microwaves, are notorious for completely
blocking wireless signals.
5. Building materials
• The building materials of the structures your business operates in can cause varying degrees
of wireless signal interference or blockage.
 Cabling and power requirements
 Wireless cabling, also known as wireless connectivity or wireless networking, refers to the
transmission of data or information between devices without the need for physical cables or
wires. Instead, wireless communication technologies such as Wi-Fi, Bluetooth, or cellular
networks are used to establish connections.
• The specific power requirements can vary depending on the device and its intended use.
• Here are a few common examples
 Wireless Routers: Wireless routers, which provide Wi-Fi connectivity, are usually
powered by connecting them to a standard electrical outlet. They require a continuous power
source to function and transmit wireless signals.
 Wireless Access Points: Similar to routers, wireless access points are devices that
provide wireless connectivity in a specific area or location. They may be powered through
an electrical outlet or, in some cases, through Power over Ethernet (PoE) technology, which
allows both data and power to be transmitted over the same Ethernet cable
Wireless Cameras: Wireless security cameras or other types of wireless cameras may
be powered by batteries or by connecting them to an electrical outlet. Battery-powered
wireless cameras are often designed for flexibility and portability, while those connected to
an outlet can provide continuous power.

 Wireless Devices: Various wireless devices, such as smartphones, tablets, and laptops,
have built-in batteries that power their wireless capabilities. These devices need to be
periodically recharged to maintain their wireless functionality.
 Unit Two: Install and configure wireless access point
2.1. Selecting access point device
What is a wireless access point?
 A wireless access point is a device used to create a WLAN. Businesses in large offices or
buildings often use wireless access points. This device is connected to an internet hub, wired
router, or switch using an Ethernet cable. Then project the Wi-Fi signal to the designated
area. It is best to understand your business needs before you make a choice. Consider some
of the above, or ask an expert for recommendations.
 Router-switch–your professional IT provider.
Things to Consider
When choosing a wireless access point, keep the following points in mind.
Range
 The range that an AP can cover is an important parameter, and a WAP with a
larger coverage area is more beneficial.
Speed
 The rate at which information travels is also something we need to consider, usually measured
in bps (bits per second), kilobits, megabits, or gigabits. In general, if the exact 802.11n
protocol is supported, wireless AP speeds can reach 300Mbps or higher, six times faster than
802.11n. The WAP that supports the 802.11ac protocol can reach 1200Mbps.
Gain Antenna
 The antenna of the wireless AP is basically built-in, it is not external like the antenna of the
router. The antenna of the wireless AP is very important, it will directly affect the signal
strength and transmission range of the wireless AP. When buying a wireless AP, it is best to
choose one with a booster antenna.
Guest Access
 When people use their phones and computers over the Internet, security issues are not
expected. Modern systems have intelligent guest access systems that apply corporate security
policies.
No Hardware Controllers
• In the past, access points also required IT technicians with specialized knowledge to operate
from a computer. However, with the advancement of technology, these are no longer
necessary. The latest Wi-Fi 6 access points, for example, use software control in the network
and do not require an external controller. Software-based control has many benefits over
previous hardware-dependent access points.
Wi-Fi Technology
 Choose devices using MESH, MIMO and POE access point technologies based on your
business needs. MESH technology can be used in home and commercial equipment. POE
technology adopts low-power cabling technology and can transmit signals up to 100M.
Price
 It is not that the higher the price, the better the AP. Sometimes the high price will not only
increase the cost, but also cause waste of product function and performance. Too low a price
can tempt people to buy inferior or counterfeit products.
 Installing and configure access points
 Wireless devices (also known as access points) provide a secure, affordable, and easy-to-use
wireless LAN solution that combines mobility and flexibility with the enterprise-class
features required by networking professionals.
 When configured as an access point, the wireless device serves as the connection point
between wireless and wired networks or as the center point of a stand-alone wireless
network. In large installations, wireless users within radio range of an access point can roam
throughout a facility while maintaining seamless, uninterrupted access to the network.
 Here we are providing an example of how to configure a wireless access point (a DLink
access point, in this case). Please take the following technics:
1. Change the default admin password.
2. Change the default SSID to something of your choosing.
3. Enable encryption.
4. Disable the DHCP Server function, if your access point has this feature
5. Register the hardware (MAC) address of your wireless card.
The Wireless Access Point (WAP) is a networking devices that enables the capability for
wireless-capable devices to connect to a wired network. Introducing a WAP to your existing
wired network is instrumental to accommodating those devices only capable of wireless
connection
• Wireless Access Point
• Wireless devices (also known as access points) provide a secure, affordable, and easy-to-use
wireless LAN solution that combines mobility and flexibility with the enterprise-class features
required by networking professionals. When configured as an access point, the wireless device
serves as the connection point between wireless and wired networks or as the center point of a
stand-alone wireless network.
 Configure Services

 The Configure Services method is a place where you can register your dependent classes
with the built-in IoC container. After registering dependent class, it can be used anywhere in
the application. You just need to include it in the parameter of the constructor of a class
where you want to use it. The IoC container will inject it automatically.
 ASP.NET Core refers dependent class as a Service. So, whenever you read "Service" then
understand it as a class, which is going to be used in some other class.
What are Managed LAN Services?
• Managed LAN Services (MLS) is a term used to describe a service provided by a third
party service provider to manage a company’s local area network (LAN). This type of
service provides remote monitoring and maintenance of the company’s network
infrastructure.
• This type of service allows companies to reduce their IT costs and increase productivity. The
main advantage of MLS over other solutions is its ability to provide 24/7 support and
proactive monitoring. It also offers an easy way to access your network remotely.
A Local Area Network (LAN) is a high-speed communication system. It allows users
to share information and connect to other computers and peripherals. A LAN is usually
connected to a server via a router. Some types of LANs are wireless while others are wired.
 Your company may already have an existing LAN, or you might need to create one. You will
need to buy equipment such as switches, routers, and hubs. Depending on the size and type
of your network, you might also need to purchase servers, printers, fax machines, and
modems.
 If you want to use a managed LAN service, you should contact a local IT service provider
who specializes in these kinds of services.
Benefits of Using Managed LAN Services?
 Security: A managed LAN services provider can secure your network by
installing firewalls, intrusion detection/prevention systems, and other security
products.
 Network Monitoring: A managed LAN services company can monitor your
network 24 hours a day, seven days a week. It can alert you when there are
problems with your network.
 Improved Network Performance: managed LAN service providers usually offer faster
speeds than you could get from a public Internet access point. You won’t have to wait as long
to download large files.
 Cost Savings: Managed LAN service providers offer lower rates than you would pay for
similar services.
 Reliability: Most managed LAN service providers guarantee 99% uptime. If they fail to
deliver this level of reliability, they will reimburse you for the downtime.
 24-Hour Availability: Most managed LAN service providers offer 24-hour availability. If an
issue arises, they will resolve it immediately.
Testing access point for connection and security
When planning the testing of a WLAN, consider the following forms of testing:
 Signal coverage testing: Signal coverage testing determines where client devices are able to
satisfy coverage requirements. This testing may be part of performing a WLAN site survey or
done after the network is installed to determine the as-installed signal coverage
 Performance testing: Performance testing determines whether the WLAN can satisfy user
needs for using specific applications over the WLAN.
 In-motion testing: In-motion testing determines whether users can continue to make use of
applications while roaming throughout the coverage areas, especially when the roaming
requires handoffs between access points.
 Security vulnerability testing: Security vulnerability testing ensures that the WLAN
implements required security mechanisms and offers sufficient protection to unauthorized
access and passive monitoring.
 Acceptance/verification testing: After installing a WLAN, it is important to run a series of
acceptance/verification tests to ensure that the WLAN satisfies all requirements. This is
especially important if the organization is having a contractor install the WLAN.
 Simulation testing: In some cases, such as when implementing a very large WLAN, it may
be beneficial to simulate the behavior of the WLAN before actually installing it. This can
provide helpful feedback when designing the system, especially if the WLAN will have
critical performance requirements.
 Prototype testing: Prototype testing involves implementing an individual function of the
WLAN that is not well understood before deploying the complete system. For example, an
organization may not be very familiar with 802.1X authentication systems and may benefit by
implementing the 802.1X authentication in a lab environment with a limited number of test
client devices.
 Pilot testing: Before installing the WLAN across the entire organization, which may include
numerous buildings and different applications, it is strongly advisable to install the system in
a limited number of facilities (ideally one) and make that one work effectively first. After you
work out all the problems, you can install the WLAN at the remaining location without the
need for extensive rework because the problems will likely have been solved during the pilot
testing.
 Upgrading legacy equipment
The infinilink team designed and implemented an integrated management system that
provides visibility and control over the entire network infrastructure, reducing complexity
and fragmentation of the ICT system.
Upgrading the ICT system:
 The modernization of the system required the replacement of multiple hardware
and software elements, the integration of old equipment and the implementation
of new systems and applications. Very important was that the entire process was
carried out without interrupting ongoing operations, with minimal downtime.
 Outcome: reduce downtime, improve data management and increase
productivity.
 Implementation of new work processes and communications:
 Together with the client, we developed new processes that are compatible with
the existing system and easy to adopt by the client’s staff. The infinilink team
worked closely with client staff to ensure that the new processes optimized
efficiency and productivity of operations.
 Outcome: increase productivity, reduce errors and improve communication on
operations between staff members.
Training users on the new ICT system:
 The successful implementation of the new ICT system depended on the ability
of the client’s staff to use it. The infinilink team provided the client’s employees
with comprehensive training on the features and functionality of the new
system, as well as on-site support to ensure staff could use the system
confidently and effectively.
 Outcome: increase staff confidence, reduce errors and increase productivity.
  Consultancy to executive management on ICT system optimizations:
 Team has identified ICT areas affecting the client’s business processes that need
optimization. We provide concrete recommendations to the executive
management of the client company, leading to continuous improvement of
system performance and efficiency.
 Outcome: improve system performance, increase efficiency and reduce costs.
 Full ICT system responsibility for continuous support of business and
production processes:
 To support business and production processes, we ensure that the system is
always working optimally. We monitor system performance and take proactive
measures to prevent outages and ensure continuity of operations
Outcome: reducing downtime, improving system performance and increasing
productivity, with a positive effect on the quality of the client company’s
products.
The end of chapter 1 and 2

•