Enterprise Information System (EIS) - A Guide

Eis is a shortcut for 'enterprise information system' Rules in an EIS: - Who will receive access to the data? - How will they be able to access the data? - How should they use the data? - How will the data be protected from people who have no right to access it? - How will data p...

Eis is a shortcut for 'enterprise information system' Rules in an EIS: - Who will receive access to the data? - How will they be able to access the data? - How should they use the data? - How will the data be protected from people who have no right to access it? - How will data privacy be ensured? - Who will be responsible for ensuring data protection\ and privacy? - Now that we've talked about the rules of an EIS, let's turn to **protocols**. What are they?\ Protocols have two main meanings whenever computer networks are involved.\ Both types play a role in an EIS. The first type of protocol is simply a clearer, **step-by-step list of instructions on how the rules of the EIS are to be implemented**. Protocols dictate how a particular process or interaction should be carried out -- like a cooking recipe. They outline the sequence of steps, the format of messages, and the actions to be taken at each stage of the process. Let's assume that on the previous question of *"How will the valuable data be* *stored?"*, you decided to store all the data of your EIS on sheets of paper in folders. Bravissimo -- you've set a rule. To make sure that employees comply with the rule correctly, it would be helpful to have step-by-step instructions for how to store the data in the folders. What should be done first? Second? What risks should you watch out for? Who must you inform? Such instructions are protocols. Whenever computers are involved, the term "protocol" also has a second meaning. It refers to instructions that computers and other digital devices follow so that they can "talk to each other" (i.e. exchange data with each other) effectively. Whenever computers and servers exchange data with each other over the internet, they follow such protocols. In fact, even smaller devices like your printer, your mouse, and your keyboard follow protocols when exchanging data with your PC. If you've seen abbreviations like HTTP, FTP, TCP/IP: these are all examples of such protocols. More on that later. **WHO ARE THE HUMAN BEINGS IN AN ENTERPRISE INFORMATION SYSTEM?** As suppliers, users, and distributors of information, people play a central role in an EIS. 1. They play a role as stakeholder groups (e.g. customers, employees, suppliers, investors); 2. Every manager in an organization is a part of an EIS because their strategies and decisions are (hopefully!) data-driven. 3. Last, there are individual jobs that are specifically responsible for planning, designing, maintaining, and controlling an organization's Enterprise Information System.. Hardware in an EIS: **WHAT IS THE HARDWARE OF AN ENTERPRISE INFORMATION SYSTEM?** In general, **hardware** refers to any physical component or part of a device that can be seen and touched. If we go with this very broad definition, then that means that any physical object that collects, creates, uses and/or distributes data is part of an organization's EIS. However, not everybody agrees on this broad definition. In fact, some experts limit the hardware that is considered part of an EIS to the **digital devices (and components) that collect, create, use and/or distribute data**. For this reason, some people get into endless arguments about whether e.g. an oven or e.g. a car qualify as hardware in an EIS. After all, objects such as these DO need - and also create - data. But they aren't necessarily digital. In truth, though, this type of 'academic' discussion is transitional. Very soon -- through the Internet of Things -- nearly all physical objects in an organization will have a digital element, making the discussion obsolete. **WHAT IS A COMPUTER NETWORK?** If you work in an organization, the chances are high that the hardware of that organization's EIS will not consist of only one computer. It's more likely that your organization will have SEVERAL computers -- maybe thousands. The people that work on these computers (i.e. "**work stations**"): - must regularly share files with each other; - use many of the same devices (e.g. a printer, a physical firewall, a router through which to access the internet); - must access & update a lot of the same data (e.g. inventory data that is stored in a database); How can dozens -- or thousands -- of computers do all these things? One way would be to assign each work station an individual internet connection. Then it could simply connect to whatever device it needs. But most organizations prefer a different option. They set up a **private network**. Such a network **connects only the computers (and other digital devices) of the organization with each other**, allowing them to share data directly with each other instead of through a public internet connection. Organizations prefer private networks over the internet for the following reasons: **Security:** A company\'s network is more secure than the public internet because it allows the company to control who has access to its data and systems; **Reliability:** A company\'s network is more reliable than the public internet because it is usually designed to have \"plan B\" options in case the internet is down (or too slow for critical activities); **Performance:** A company\'s network can provide faster and more consistent network performance than the public internet. **Cost:** Companies can tailor their network infrastructure to meet their specific needs and avoid paying for unnecessary services or features; You have now familiarized yourself with many of the hardware components of a private network. There are a few extras that we won't cover in this beginner course, such as "**hubs**", **bridges**", and "**repeaters**". These are simply additional devices that provide many of the same functions we've already discussed here (though in faster or cheaper ways -- depending on the situation).