Download
1 / 19
190 likes | 286 Views
Infrastructure Applications. Requirements for classes of applications. IT Drivers. Data Warehousing Enterprise Management SAP and others Supply chain management Electronic Commerce Business to business Electronic retail. Data Warehousing.
E N D
Infrastructure Applications Requirements for classes of applications
IT Drivers • Data Warehousing • Enterprise Management • SAP and others • Supply chain management • Electronic Commerce • Business to business • Electronic retail
Data Warehousing Building a database to support the decision making activities of a department or business unit
Data Warehouse A read-only database for decision analysis • Subject Oriented • Integrated • Time variant • Nonvolatile consisting of time stamped operational and external data.
Data Warehouse Architecture Enterprise Data Warehouse Data Marts Business Packages
Three Approaches • Classical Enterprise Warehouse Contains integrated operational data from all areas of the organization. • Data Mart Extracted and summarized data designed for departmental or EUC applications • Data Project Data for a specific application or analysis
Highly tuned Real time Data Detailed records Current values Accesses small amounts of data in a predictable manner Flexible access Consistent timing Summarized as appropriate Historical Access large amounts of data in unexpected ways Data Warehouse vsOperational Databases
Access Tailored access programs in user form, usually client-server • Specialist interfaces • General purpose GUI products (e.g. Access, PowerBuilder) • Custom access routines
ERP Reality • Complete systems can cost tens of millions of dollars • Implementation can take several years • Companies may lose flexibility
What is SAP?Systems Applications and Products in Data Processing • SAP is the leading global provider of client/server business application solutions • SAP is the number one vendor of standard business applications software • SAP is the fifth largest independent software supplier in the world
Electronic Commerce Interorganizational Systems: Business-to-business Electronic storefront
Market ExchangeInterorganizational Structure • Vertical integration Multiple activities in the same firm • Risk: range of expertise required • Selective sourcing Some outsourced activities • Risk: control of outsourcer • Virtual corporation Coordination of separate activities • Risk: loss of core competency
Questions • Do we benefit from electronic commerce? • Do we use information to add value to customers? • Are we managing the product/service channel? • Have we redesigned business with our partners to take advantage of technology and provide security • Do we have partners with shared vision and common purpose? • Do we have the right infrastructure?
External / Internal Hosting • Outside (Cheaper) • minimize bandwidth and hardware problems • use external experts • installed infrastructure • little additional staffing required • Inside (More Control) • dependent on third party reliability • possible single vendor software solutions • possible single vendor payment scheme
External / Internal Hosting • External better at storefronts but requires close integration with core business • Internal better at business to business but often creates a self-contained replicated system that can be outsourced
Payment • Credit Cards SET (Secure Electronic Transaction) with http • Electronic Checks Public/private key transactions with banks • Electronic Cash 3rd party software to create virtual cash • EDI/EFT Value added network using 3rd party. Common in business to business.
