1 / 16

Bus 361

Bus 361. Chapter 4 Enterprise-wide Systems & Inter-enterprise Systems. Objectives. What is an enterprise-wide system How do they fit into e-bus strategy What are the key features How are inter-enterprise systems created Evaluate the structures for setting up the two systems

connor
Télécharger la présentation

Bus 361

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bus 361 Chapter 4 Enterprise-wide Systems & Inter-enterprise Systems

  2. Objectives • What is an enterprise-wide system • How do they fit into e-bus strategy • What are the key features • How are inter-enterprise systems created • Evaluate the structures for setting up the two systems • Explain why they are crucial to e-bus

  3. Enterprise-wide Systems • Info access to all who need it no matter where they are physically • Key concept is that all users have access to the same up-to-date information • Data collection with one piece of S/W to make organization, management & access easy. • ERP, SCM & CRM all examples • Middleware s/w that links 2 dif. programs

  4. ERP Systems • Switch from silo to shared • “Knowledge is power”?? • Developing the system requires analysis of all processes • Business Process Re-engineering • Vendors: Oracle, SAP, minor leagues – MSFT • Module based, drill down

  5. Characteristics • Client-server systems • Relationship database • Common field • 3 basic elements • Data • Processing (applications) • Output (display) • Where is the processing done? • Distributed processing systems • 2-tier (S & C) • 3-tier (S & C + dedicated processing servers) • Distributed data client servers

  6. Database Terminology • Database: is a collection of data that is organized in a specific way. The data is stored in a way that makes it easy to access using queries. • Table: A database can have multiple tables in it. All the data is stored in the tables. A table has a set of fields in it. These fields makes the design or the structure of the database. • Field: Each table has a set of fields (columns). • Data Type: Each field can have only one kind of data. That is called the Data Type of that field. This can be a string, an integer, a date, etc. When creating a table, you have to specify the kind of data that can be stored in that field. One field can be used to store a number, another for a string. Since every table has a number of fields, different types of data can be stored in a table. • Row: All the terms till now dealt with the structure - row refers to the data. It can also called a record. The collection of a set of values for all fields in one table is together called a row. • Primary Key: Primary key is a field that will uniquely identify each row in the table. The value of this field will be unique through the table. • Relation: There will be many cases when the data in one table can be related to the data in another table. This connection between two tables is called a relation. • Foreign Key: When there is a relation between 2 tables, these tables will be connected by inserting the primary key of one table into the corresponding row of the other table. The field used in such a way to connect the 2 tables is called the foreign key.

  7. Two other terms • Packaged Software (COTS) • Installed & then operated • Can be customized • Business Process Re-engineering • Redesigning how we do business • Necessary because of ERP • Can be how, who, what with or when • Resistance to change

  8. Implementing ERP • Hershey example of how not to do it • Timing • Capabilities • “Systems sizing” • “Stress testing” • Training

  9. Integrating ERP • Is the whole organization going ERP or .. • Interfaces • Modifying existing systems • Standardization makes integration easier • “Best of Breed” … existing might be better

  10. Oracle’s 6 Phases in Implementation • Definition & Team building • Operations Analysis • Solution Design • Build/code • Transition – training & checking • Production

  11. Back to the Middle(ware) • Middleware is seamless i.e. the user doesn’t know it is happening • Built in to the applications • Enterprise Application Integration • Using middleware to join applications • Planning, implementing & managing applications ability to share info between • Legacy systems & ERP

  12. MetaLanguage • a metalanguage is a language used to make statements about statements in another language • Words like …. Noun adjective • So XML is a “language” that can be read by humans and machines

  13. Collaborative & Inter-enterprise • Allow companies to interact • Customers • Suppliers • With other team members (LotusNotes) • Competitors (ethical issues)

  14. Managing them • Increasing scope -> Increasing complexity • Outsource • Create new separate entity • Management agreements with partners • Manage own part of the system

  15. What can go wrong? • Resistance • Sabotage • Timing • Resources • Delays

More Related