ch15_final
合集下载
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
15-4
Software Standards and the Next Inflection Point
FIGURE 15-1: Software standards and the next inflection point
15-5
Four Phases Proprietary
Until the early 80s Mostly mainframe computers accessed through key punches and dumb terminals Little communication between systems with few options such as private networks or physical media.
Eventually created a large user base and a large market for applications Communication standards developed mostly for local networks
Ethernet and IBM token ring
Uniform access capability anytime and anywhere Standard way to track products in order to provide participants with the information they need to perform efficiently Uniform Code Council
15-11
System Architecture
Encompasses the way the components are configured Components imply:
Databases, interface devices, communications
Two main categories:
a form of distributed processing some processes are performed centrally for many users while others are performed locally on a user’s PC
15-15
Client/Server Architecture
Service Oriented Architecture (SOA)
15-3
15.2 IT Standards
High level of standards evolving due to following reasons:
Market forces Standards reduce cost of system development and maintenance. Interconnectivity Connecting different systems and work across networks has pushed the development of standards New software models Internet has produced the need for software that has new development and deployment characteristics. Economies of scale Standards reduce the price of system components, development, integration, and maintenance.
15-13
Legacy System Architecture
FIGURE 15-2: Legacy system architecture
15-14
Client/Server Architecture
Systems take advantage of the PC’s computing power and friendly graphic interface. PC is typically called the “client” Main processor is the “server.” Client/server computing
Created the bar code system, Universal Product Code (UPC), in 1973 Scanning and recording information about products Automatic data capture interfaces, bar-code readers and radio frequency (RF) tags RF tags used to locate items, particularly in large warehouses. Together with GPS capabilities, enables tracking of tagged cargo while in shipment. RFID tag a replacement for the RF tag
Interface/presentation devices Communications Databases System architecture
15-10
Interface Devices
Common devirs, voice mail, terminals, Internet devices, barcode scanners, PDA
15-8
Four Phases Collaboration
Next phase of standards
Currently being developed Addresses collaboration Supporting technology built around SOA and BPM technologies Has further increased the importance of ERP systems
15-6
Four Phases Stand Alone
IBM PC software and hardware introduced the first standard platform called Wintel
Microsoft Windows and Intel standard
Missing link in communications provided by the internet Expanded the connection across organizations and beyond the local network Forms of communication enabled:
Local PC browser processes the HTML (hypertext markup language) pages and Java applets (i.e., small applications) These are retrieved from servers Evolving towards a Web-centric model where the client is a Web browser connected to a Web server.
Legacy system architecture Client/Server architecture
15-12
Legacy System Architecture
Evolved as departmental solutions using mainframe or minicomputers that were accessed through “dumb” terminals Company’s main systems for special applications such as word processing or spreadsheets. PCs Connecting PCs by means of local area networks (LANs) LANs extended across companies with wide area networks (WANs)
Chapter 15
Technology Standards
McGraw-Hill/Irwin
Copyright © 2008 by The McGraw-Hill Companies, Inc. All rights reserved.
15.1 Introduction
Technology standards are important in supply chain management Review
Electronic mail File and information transfer Electronic commerce from shopping, bidding, and exchanges Shipment tracking Extended collaboration between companies on joint forecasts, transportation and other activities.
Legacy systems replaced by client/server-based enterprise resource planning (ERP) systems ERP Systems:
Year 2000 fears
1st generation systems: finance and human resource applications Subsequent: Manufacturing and distribution More recent: Adding supply chain capabilities
Most current system design use this architecture Variations in:
Sophistication and price of the client Number and type of servers Other design parameters
For business networks private networks were mostly used for file transfers
Electronic data interchange (EDI)
Client/server was developed
15-7
Four Phases Connected
IT related standards New technology platforms Evolving technology standards
15-2
New Developments
Radio Frequency Identification Devices (RFID) Consolidation of market to a few players New approaches to system design
15-9
15.3 IT Infrastructure
Critical in the success or failure of any system implementation Forms the base for data collection, transactions, system access, and communications. Infrastructure components:
Software Standards and the Next Inflection Point
FIGURE 15-1: Software standards and the next inflection point
15-5
Four Phases Proprietary
Until the early 80s Mostly mainframe computers accessed through key punches and dumb terminals Little communication between systems with few options such as private networks or physical media.
Eventually created a large user base and a large market for applications Communication standards developed mostly for local networks
Ethernet and IBM token ring
Uniform access capability anytime and anywhere Standard way to track products in order to provide participants with the information they need to perform efficiently Uniform Code Council
15-11
System Architecture
Encompasses the way the components are configured Components imply:
Databases, interface devices, communications
Two main categories:
a form of distributed processing some processes are performed centrally for many users while others are performed locally on a user’s PC
15-15
Client/Server Architecture
Service Oriented Architecture (SOA)
15-3
15.2 IT Standards
High level of standards evolving due to following reasons:
Market forces Standards reduce cost of system development and maintenance. Interconnectivity Connecting different systems and work across networks has pushed the development of standards New software models Internet has produced the need for software that has new development and deployment characteristics. Economies of scale Standards reduce the price of system components, development, integration, and maintenance.
15-13
Legacy System Architecture
FIGURE 15-2: Legacy system architecture
15-14
Client/Server Architecture
Systems take advantage of the PC’s computing power and friendly graphic interface. PC is typically called the “client” Main processor is the “server.” Client/server computing
Created the bar code system, Universal Product Code (UPC), in 1973 Scanning and recording information about products Automatic data capture interfaces, bar-code readers and radio frequency (RF) tags RF tags used to locate items, particularly in large warehouses. Together with GPS capabilities, enables tracking of tagged cargo while in shipment. RFID tag a replacement for the RF tag
Interface/presentation devices Communications Databases System architecture
15-10
Interface Devices
Common devirs, voice mail, terminals, Internet devices, barcode scanners, PDA
15-8
Four Phases Collaboration
Next phase of standards
Currently being developed Addresses collaboration Supporting technology built around SOA and BPM technologies Has further increased the importance of ERP systems
15-6
Four Phases Stand Alone
IBM PC software and hardware introduced the first standard platform called Wintel
Microsoft Windows and Intel standard
Missing link in communications provided by the internet Expanded the connection across organizations and beyond the local network Forms of communication enabled:
Local PC browser processes the HTML (hypertext markup language) pages and Java applets (i.e., small applications) These are retrieved from servers Evolving towards a Web-centric model where the client is a Web browser connected to a Web server.
Legacy system architecture Client/Server architecture
15-12
Legacy System Architecture
Evolved as departmental solutions using mainframe or minicomputers that were accessed through “dumb” terminals Company’s main systems for special applications such as word processing or spreadsheets. PCs Connecting PCs by means of local area networks (LANs) LANs extended across companies with wide area networks (WANs)
Chapter 15
Technology Standards
McGraw-Hill/Irwin
Copyright © 2008 by The McGraw-Hill Companies, Inc. All rights reserved.
15.1 Introduction
Technology standards are important in supply chain management Review
Electronic mail File and information transfer Electronic commerce from shopping, bidding, and exchanges Shipment tracking Extended collaboration between companies on joint forecasts, transportation and other activities.
Legacy systems replaced by client/server-based enterprise resource planning (ERP) systems ERP Systems:
Year 2000 fears
1st generation systems: finance and human resource applications Subsequent: Manufacturing and distribution More recent: Adding supply chain capabilities
Most current system design use this architecture Variations in:
Sophistication and price of the client Number and type of servers Other design parameters
For business networks private networks were mostly used for file transfers
Electronic data interchange (EDI)
Client/server was developed
15-7
Four Phases Connected
IT related standards New technology platforms Evolving technology standards
15-2
New Developments
Radio Frequency Identification Devices (RFID) Consolidation of market to a few players New approaches to system design
15-9
15.3 IT Infrastructure
Critical in the success or failure of any system implementation Forms the base for data collection, transactions, system access, and communications. Infrastructure components: