New Rules of Strategy Arthur Andersen Outlook, 1998, - PowerPoint PPT Presentation

About This Presentation
Title:

New Rules of Strategy Arthur Andersen Outlook, 1998,

Description:

Discuss the relationship between strategy, business ... High level map of info requirements; blueprint. Centralized: data. communications. Decentralized: ... – PowerPoint PPT presentation

Number of Views:293
Avg rating:3.0/5.0
Slides: 13
Provided by: CarolSa
Learn more at: https://www.ou.edu
Category:

less

Transcript and Presenter's Notes

Title: New Rules of Strategy Arthur Andersen Outlook, 1998,


1
New Rules of Strategy (Arthur Andersen Outlook,
1998, 1)
2
New Rules of Strategy (Arthur Andersen Outlook,
1998,01)
3
Architecture, Infrastructure ERP
  • Define application,bit, byte, client/server,
    coaxial cable, CPU, database,ERP, ethernet, fiber
    optic, gigabit (byte), hard drive, ISDN, kilobit
    (byte), LAN, WAN, megabit (byte), modem,
    operating system, protocol, RAM, SAP, server,
    thick client, thin client, WAN, TCO, legacy
    system
  • Distinguish architecture from infrastructure
  • Discuss the relationship between strategy,
    business requirements, architecture, and
    infrastructure
  • Discuss the applicability of evaluation criteria
    to architecture and infrastructure
  • Analyze infrastructure and architecture needs
    across hardware, software, data and networks
  • Advantages and disadvantages of ERPs

4
Strategy, Requirements, Architecture
Infrastructure
  • Strategy
  • Business Requirements
  • Architecture

  • Infrastructure

5
Information Architecture
  • High level map of info requirements blueprint
  • Centralized
  • data
  • communications
  • Decentralized
  • focus on organizational function
  • Translates strategy into infrastructure
  • Hard to define needs change

6
Information Infrastructure
  • Physical facilities, services, management
    supporting computing resources
  • hardware
  • software
  • networks communications
  • data
  • personnel

7
Evaluation Criteria Applicability
8
Meta Group Guidelines for Adaptable IT AI
  • Plan modular (independent and loosely coupled)
    vs. monolithic
  • Have clear boundaries between infrastructure
    components
  • With network architecture, provide access to all
    users when it makes sense to do so

9
Architecture Definitions - Client/server
  • Client - PC or workstation attached to a network
    which is used to access shared network resources
  • Server - machine that provides clients with
    services (i.e., sharing databases, software)
  • Thick client - full function stand-alone computer
    that is used either exclusively or occasionally
    as a client in a client/server architecture
  • Thin client - computer hardware designed to be
    used only as a client in a client/server
    architecture (Network PCs)

10
Definitions
  • Enterprise-wide system - distributed system that
    covers the entire organization
  • ERP - a large highly complex software program
    that integrates many business functions under a
    single application
  • Legacy system - older or mature IS (often 20-30
    years old)

11
ERP
  • No more fragments!
  • Streamlined operations
  • One system fits all?
  • Too centralized?
  • Big bucks
  • Growing need to integrate ERP applications within
    companies and across trading partners
  • middleware for 24/7 B2B applications (ERP
    databases and B2B applications)

12
Total Cost of Ownership
  • Popular when PC-based IT infrastructures began
    gaining popularity
  • TCO capital investments technical support
    administration training
  • Helps managers understand how infrastructure
    costs break down
  • Annual costs per user for each potential
    infrastructure choice
  • Shared vs. isolated
Write a Comment
User Comments (0)
About PowerShow.com