Академический Документы
Профессиональный Документы
Культура Документы
INFORMATION
SYSTEMS IN THE
ENTERPRISE
This lecture is based on materials in Essentials of Management Information Systems by Laudon and Laudon 5/e and the summary slides available on their website. However, some material herein also represents the perspective of Gregory Rose of Washington State University. Where materials are taken verbatim from the Laudon and Laudon slides, they represent the views of the book and are copyrighted by the authors and the publisher. Where the sequence or content differ, the content is 1 considered the work of Gregory Rose with all copyrights reserved.
This lecture will cover the following perspectives about software: From the software developers perspective From the end users perspective (who is using and for what goal) From the business process perspective
2
These perspectives provide ways to view various subtypes of systems in business Why do you need to be aware of the various subtypes of systems?
For discussing your needs with different stakeholders For allocation of resources This is your catalog of what you could buy if you had all the resources in the World
3
From the software developers perspective Software is mostly a collection of software components assembled and reused as needed (like Lego blocks) Developers created these components to accumulate in the marketplace over time
Once only automated small subset of tasks Components now exist for just about any business function Now have components for sale individually at one extreme and bundled together as Inter4 organizational services at the other
From the software developers perspective (continued) Applications dont really exist except as a way to describe a set of software services
Sold based on marketing and sales Many services share components but are bundled and marketed differently based on user group and task Sales staff may end up selling multiple software systems that are actually 90%+ the same code to your firm. 5
From the end users perspective Different software helps different groups of users at different levels within business hierarchy Services are marketed based on
what level in the hierarchy user is located and what goal they are using the system for
6
Overview of Operational Level Systems: Produces routine answers. Nuts and bolts of the business.
Overview of Management Level Systems: Support monitoring, controlling, decision-making, and administration by middle management.
Overview of Strategic Level Systems: Information Systems that Support LongRange Planning of Senior Management.
10
A computerized system that performs and records daily routine transactions necessary to the conduct of the business Example: payroll system; production instructions11
Example: Weekly, monthly, and annual resource allocation. Not five year plans and not daily details, but something in between.
12
Management Information System (MIS) Some characteristics of MIS that make them differ from DSS (on next slide)
Structured and semi-structured decisions Output is often the kind that you need routinely each term (quarter, month, year) to evaluate how to proceed next (quarterly sales data for past 5 years) Generally, you can eyeball your decision
13
Top level (strategic level)Executive Support System (ESS): Inputs: Aggregate data. Internal and external Processing: Interactive and graphical simulations Outputs: Projections Users: Senior managers Example: 5-year operating plan. Answer question like what are long-term industry cost trends and how are we doing relative to them? Gets data from all internal IS plus external industry data bases 15
Top level management Designed to the individual Ties CEO to all levels Very expensive to keep up
16
INTERRELATIONSHIPS: -These systems can share data and be interconnected -TPS generally feed all other systems - MIS generally indicate when a DSS is needed and provide input for them to crunch - ESS take all internal data but usually only summary data from MIS and DSS level Output data from one is input data for others to process
17
When talking to sales staff with these terms, what matters here is (1) who is using the system and (2) what is their objective A single software package like Microsoft Office or even an application like Microsoft Excel could be classified as any or all of the following: DSS, TPS, MIS, or ESS (albeit, a trivial ESS, DSS, etc.) A service is provided by the CBIS is a solution. It is a DSS, etc., depending on what solution in the corporate hierarchy it serves.
Analogy: a BMW is either a luxury car or an expensive paper weight depending on what you use it for. But it 18 can be either or both.
(e.g., my old firm hired technologists and taught them about foodservice, or foodservice people and taught them about technologybut both skills were 20 needed for foodservice management software)
Google on a function and industry and see for yourself what is available
21
Not all business processes are contained within a single functional area Many business processes are cross-functional
Cross-Functional Business Processes Def: Transcend boundary between sales, marketing, manufacturing, and research and development (e.g., order fulfillment process)
22
Here you see that order fulfillment cuts across sales, accounting, and manufacturing and distribution
23
The largest business process is the entire business itself If goes across entire enterprise, is called an Enterprise System (ERP) If across multiple firms is interorganizational system (IOS). Eliminates media breaks! This way software has a single point of management to handle integration and settle disputes. Standardization of hardware, software, and data allows for easier maintenance Share data and avoid redundancy
24
25
That is the menu of what solutions are possible Also provides the categorization you need to use to discuss what you are looking to acquire Next up: discussions on how to decide which software to acquire given resources are finite
26