Management of Information System fiche

MIS FICHE

Data, Information and Knowledge

Data = undefined material, information = meaningful data, knowledge = associated with a person or entity

Information Technology

Range: Hardware (computer, tablets), software (applications, data base), network (modem, routers)

Infrastructure = need to be organize with business process and employees needed to operate and support the IS Infra

Function IT = enable achievement of individual tasks

Network IT = facilitate interaction between stakeholders

Enterprise IT = enable business processes between organization

2-tier architecture

Client/server with an application between the two, integrating a functional use such as sales management or procurement

Multi-tier architecture

3 Tier :

• Server Layer (Database with Relation Data Base Management Systems)
• Application server (Application logics, makes the calculations)
• Client Layer (SAP User graphic interface)

[pic 1]

Pros :

• Agility: Implement and Deploy new applications and satisfy users demand in a reactive manner
• Scalability: benefit from additional computing resources
• Security: application layer provides additional security
• Independence: enables IT departments to act on one tier without impacting the others

Cloud Case

2 ways of storing data:

• Cloud computing, never using your own server but using internet servers
• Traditional data centers, own servers in a certain room of the firm

A few dimensions: On-premise environment, infrastructure, platform, software

Private Cloud, Public cloud, Hybrid

NDPL – pharmaceutical industry in India

Traditional IS pros:

• Avoid manual errors and duplication efforts
• Increase the number of orders taken
• Efficiency, communication
• Stock management
• Sales growth

Traditional IS cons:

• Expensive
• Upgrade are necessary
• Security needed
• Diverse suppliers

Cloud pros:

• Reduce costs, not need to invest a lot in IT
• Focus on core business
• Access to the cloud anywhere
• Scalability
• Allows NDPL to expand

Cloud cons:

• Connectivity problem +accountability
• Limited experience to provide a good cloud for pharmaceutical companies
• Latency and Network shutdowns
• While not using the cloud, you become less dependent on your server provider’s errors and bugs

ERP System Architecture / Client/Server System

Enterprise Resource Planning. Architecture that supports the connection between the database, processing and presentation is called Client/Server architecture

Client (Front-end) <-> Network (Transmission of data) <-> Server (back end)

Big Amount of data stored in warehouses

Client: Process that makes service requests to a server

Server: Process that responds with the requested service to a client

Thin client: Has minimal processing responsibilities (the server does the majority of the work)

Fat client: Takes on a larger load of processing

Middleware orchestrating the communication over the network, can run different operating systems

Components of ERP System:

• Presentation Logic (Client): User input, Data output, Rendering the user interface
• Processing Logic (Application Server): Business transactions and rues, communicating with storage logic, Managing and balancing load, Input/Output processing
• Storage Logic (Database Server): DBMS, Data storage, Data retrieval, Physical storage device

N-Tier approach

The three logic components can be distributed across multiple tiers of an n-tier client and server systems. Application partitioning: Programs that are distributed onto clients and servers as needed to maximize performance and data security. Between Web Server and Application Server for example

3 Tier for ERP Systems

• Database Tier: Master Data (about customers, vendors, materials…), Transactional Data, primary key that is a field that uniquely identifies each row in a table
• Business Tier: Perform tasks such as managing the resources, distributing the transactions, organize all communication, maintain the data integrity
• Presentation Tier: rendering program for the client screen (mobile, PC…)

Database connectivity and Middleware

Database connectivity: Mechanism that orchestrates the connecting and the communication to a source of data (relational database) over a network through an application. Middleware is the glue that binds all client server applications

...