|
|
| Line 10: |
Line 10: |
| | == What is Client Access Infrastructure ? == | | == What is Client Access Infrastructure ? == |
| | This is a set of principles, guidelines, and rules used by an organization to direct the process of acquiring, building, modifying and interfacing with IT resources throughout the enterprise. | | This is a set of principles, guidelines, and rules used by an organization to direct the process of acquiring, building, modifying and interfacing with IT resources throughout the enterprise. |
| − |
| |
| − | ==== The resources can include: ====
| |
| − | * Cable Systems for interconnecting equipment
| |
| − | * Equipment
| |
| − | * How much disk space and other 400 resources we need
| |
| − | ** [[BPCS]] sizing questionairre
| |
| − | * How connect PCs to 400
| |
| − | ** spend $150 per PC and PC printer to connect to twinax and know next to nothing when something goes wrong or spend much more $ on a better quality interface
| |
| − | ** network PCs to a PC-based server then network the PC server to the 400
| |
| − | ** mix and match IBM and 3rd party solutions
| |
| − | * Software
| |
| − | * Communications protocols
| |
| − | * Remote site support
| |
| − | * How we connect thru ma bell
| |
| − | * Application development
| |
| − | * Methodology
| |
| − | * Data base systems
| |
| − | * Shared pool of documentation
| |
| − | * Security
| |
| − | * IT Organizational structure
| |
| − | * IT professional skills
| |
| − | ** GUI software updates
| |
| − | ** Relational data base concepts
| |
| − | ** SQL
| |
| − | ** Network management
| |
| − | ** Integrate new technologies with base software applications such as [[BPCS]]
| |
| − | *** e-mail
| |
| − | *** fax
| |
| − | *** EDI
| |
| − | *** bar coding & data collection
| |
| − | *** Internet access
| |
| − | **** re-think security where before it was Ok to assume 99% users trustworthy, now we have a world of hackers and malware out there
| |
| − | * Help Desk services
| |
| − |
| |
| − | ==== What [[ERP]] Version is best? ====
| |
| − | ===== [[BPCS]] Choices =====
| |
| − | Decisions decisions
| |
| − | * [[Mixed Mode]] or full Client Server?
| |
| − | ** Fat and Thin Clients
| |
| − | ** Mixed Mode
| |
| − | *** Client Server for which applications
| |
| − | **** Accounting
| |
| − | **** Customer Service
| |
| − | **** Supply Chain
| |
| − | *** [[Green Screen]] for everything else
| |
| − | *** Need Netsoft Router
| |
| − | ** Full Client Server
| |
| − | *** Fat Client for which applications
| |
| − | **** Accounting
| |
| − | **** Customer Service
| |
| − | **** Supply Chain
| |
| − | *** Thin Client for everything else
| |
| − | *** Need TCP/IP
| |
| − | ** UserVision has some Windows minimum requirements
| |
| − | * Client setup
| |
| − | ** 16 bit or 32 bit
| |
| − | ** What versions of Microsoft Windows
| |
| − | ** Are SSA minimums appropriate?
| |
| − | * Network
| |
| − | ** Ethernet or Token Ring if Client Server
| |
| − | ** Twinax r IBM Cabling System for Mixed Mode
| |
| − | ** Examine Network Segmentation Growth Constraints
| |
| − | ** Network Management
| |
| − | *** Wireless opens another door into Security hassles
| |
| − | * Network OS - Windows NT follow-on or Netware?
| |
| − | * Network Server - BPCS FSIOP or separate server?
| |
| − | * Different 3rd party support vendors are more attuned to different mixtures of solutions
| |
| − | ** If you go with one mixture, and use a tech support place whose expertise is in a different mixture, expect problems down the road
| |
| − |
| |
| − | === What is Client / Server ? ===
| |
| − | Client / Server computing is the splitting of an application into tasks that are performed on separate computers, one of which is a programmable workstation.
| |
| − | * Client is the computing resource that is USING some resource provided by a Server.
| |
| − | * Server is the computing resource that is PROVIDING some resource to Clients.
| |
| − | * There can be a linkage or hierarchy of multiple Clients of Servers, in which the Clients are in turn Servers to other Clients.
| |
| − | ==== Client/Server Computing is NOT ====
| |
| − | * It is NOT some specific software.
| |
| − | * It is NOT some specific hardware.
| |
| − | * It is NOT a solution for all applications.
| |
| − | == Sane Planning ==
| |
| − | * Project Organization, as with any other conversion
| |
| − | ** Define Objectives, Schedule (a moving target)
| |
| − | ** Management Approval, Budget Commitment
| |
| − | ** Team Membership
| |
| − | *** Key IT leadership
| |
| − | *** Application Design management
| |
| − | *** IT Operations Support management
| |
| − | *** Consultants
| |
| − | ** Set hierarchy ... team leader
| |
| − | * Assess exisitng infrastructure inventory
| |
| − | * Four layers
| |
| − | ** Logical Architecture
| |
| − | *** What MIS does to support the business
| |
| − | *** What the users need
| |
| − | *** Business vision
| |
| − | ** Physical Architecture
| |
| − | *** Site specific
| |
| − | *** technologies that define or limit what we can do
| |
| − | ** Enabling Technologies
| |
| − | *** Operating Systems
| |
| − | *** Middleware
| |
| − | *** Systems and Network management
| |
| − | *** Security
| |
| − | *** Configuration
| |
| − | *** Trouble-shooting
| |
| − | *** Performance
| |
| − | ** Support
| |
| − | *** What it takes to meet regulatory constraints
| |
| − | *** Planning
| |
| − | *** Development
| |
| − | *** Different kinds of support
| |
| − | **** Hardware
| |
| − | **** Network
| |
| − | **** Application
| |
| − | **** Training new users
| |
| − | **** Skill sets ... same person
| |
| − | ***** AS/400 and PC and telecom
| |
| − | **** Documenting
| |
| − | * Design
| |
| − | ** Diagrams that make sense to everyone
| |
| − | ** Testing
| |
| − | * Implementation
| |
