Performance Measurement and Management IACT 418 IACT 918 Corporate Network Planning.

Slides:



Advertisements
Similar presentations
Managing Hardware and Software Assets
Advertisements

Capacity Planning For Products and Services
Capacity Planning For Products and Services
Capacity Planning IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
Chapter 1 Business Driven Technology
OPERATIONS The term production and operations tend to be interchangeable today the main feature of operations is that there is an input, process, output.
Unit 2 Manufacturing Operations Sections: 1.Manufacturing Industries and Products 2.Manufacturing Operations 3.Production Facilities 4.Product/Production.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. 5 Capacity Planning For Products and Services.
CAPACITY LOAD OUTPUT.
Theory of Constraints Part II: TOC Concepts
Operations Management
Network Design and Implementation
Chapter 14 Network Design and Implementation. 2 Network Analysis and Design Aspects of network analysis and design Understanding the requirements for.
Concepts in Enterprise Resource Planning Fourth Edition
Network Capacity Planning IACT 418 IACT 918 Corporate Network Planning.
Revision IACT 418 IACT 918 Corporate Network Planning.
Requirements Capture and Specification IACT424/924 Corporate Network Design and Implementation.
Chapter 1 Assuming the Role of the Systems Analyst
Security Management IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
Accounting Management IACT 918 April 2005 Glenn Bewsell/Gene Awyzio SITACS University of Wollongong.
Chapter 1 Assuming the Role of the Systems Analyst
IACT 901 Module 9 Establishing Technology Strategy - Scope & Purpose.
Security Management IACT 418/918 Autumn 2005 Gene Awyzio SITACS University of Wollongong.
Business Data Communications & Networking
Introduction to Systems Analysis and Design
Continual Improvement Ensuring the EMS is Effective! Internal Auditing, Corrective Actions & Management Review.
LAN/WAN Optimization Techniques. Agenda Current Traffic Current Traffic Equipment Inventory and Forecasted Growth Equipment Inventory and Forecasted Growth.
RF Drive Test (Testing) Engr. Mehran Mamonai. Introduction Every good RF design, after its implantation should be evaluated. There are few ways to do.
Maintenance Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill.
Chapter 8.  Network Management  Organization Management  Risk Assessment & Management  Service Management  Performance Management  Problem Management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management 1.
Section 11.1 Identify customer requirements Recommend appropriate network topologies Gather data about existing equipment and software Section 11.2 Demonstrate.
System Development Process Prof. Sujata Rao. 2Overview Systems development life cycle (SDLC) – Provides overall framework for managing system development.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Identifying Application Impacts on Network Design Designing and Supporting Computer.
Chapter 14 Information System Development
Manpower Planning.
Lecture 4 1 Introduction to Systems Planning Lecture 4 2 Objectives n Describe the strategic planning process n Explain the purpose of a mission statement.
Wide Area Networks. 2 Types of Traditional Telephone Circuits u Dial-Up Service (Any-to-Any) u Leased Lines u Point-to-point only u Cheaper for high volumes.
2  Mission Statement.  Company’s overall purpose and direction, products, services and values.  Goals.  That accomplish the mission. E.g. 5 year plan.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Identifying Application Impacts on Network Design Designing and Supporting.
Managing Travel for Planned Special Events: What, Why, & Benefits Walt Dunn, P.E. Dunn Engineering Associates, P.C. Talking Operations Seminar January.
Systems Analysis and Design
CHAPTER 13 Acquiring Information Systems and Applications.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 3 1 Software Size Estimation I Material adapted from: Disciplined.
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 2 Project Management Cycle.
Presentation made by 3D High School G.B. Bodoni.  What is it? Business Plan is a planning document that describe in detail the business project and allows.
Disciplined Software Engineering Lecture #3 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
Systems Analysis and Design in a Changing World, Fourth Edition
Maintenance Workload Forecasting
Concepts in Enterprise Resource Planning Fourth Edition
Introduction to IT investment decision-making Pertemuan 1-2 Matakuliah: A Strategi Investasi IT Tahun: 2009.
Capacity Planning Pertemuan 04
1 He Says vs. She Says Model Validation and Calibration Kevin Chang HNTB Corporation
Chapter 12 The Network Development Life Cycle
Network management Network management refers to the activities, methods, procedures, and tools that pertain to the operation, administration, maintenance,
MARKETING 3.01 Product/Service Management. Intro Who is responsible for the last product you bought? Did you know….. -It took over 3 years to develop.
Maintenance Management
Chapter 1 Assuming the Role of the Systems Analyst.
Economic Environment of Business Lecture Two: Legal structure and objectives of firms.
1 Block 3 Session 2 Continue.. & Session 3 Distribution systems, EDI and the organization: –Major developments over the last 30 years have been achieved.
Developing Information Systems
(Additional materials)
Capacity Planning For Products and Services
Capacity Planning For Products and Services
Systems Analysis and Design
Capacity Planning For Products and Services
Production and Operations Management
Capacity Planning For Products and Services
Presentation transcript:

Performance Measurement and Management IACT 418 IACT 918 Corporate Network Planning

Overview The performance of information technology is increasing rapidly and the need for transporting large amounts of data through a modern organisation is increasing with it Network managers are faced with the requirement to: Increase bandwidth to allow today's communications needs to be met, and allow for growth in those needs and Keep the costs down to a minimum

Overview This requires an engineering trade-off, which has to be made repeatedly So that we are not completely swamped with the size of the job, we have devised a procedure, which allows us to cope with it

Performance Management "... is a set of activities required to continuously evaluate the principal performance indicators of network operation, to verify how service levels are maintained, to identify actual and potential bottlenecks and to establish and report on trends for management decision making and planning.“ Terplan P 367

Performance Management The performance indicators are measured by the system Typical indicators are Availability Response time Throughput Utilisation Transmission volumes Errors etc

Performance Management Procedure The procedure is iterative, but we may identify four steps. Determining and quantifying current workload Projecting future workload Developing the network capacity plan Implementation

Determining and Quantifying Current Workload The information for this phase will be gathered by the network instrumentation The most important indicators of current workload are Volume of traffic Response time Lost messages Packets Utilisation Queueing theory (as a tool)

Determining and Quantifying Current Workload The number of trouble tickets will highlight areas where there are problems with reliability This information is needed for all elements in the region under consideration

Determining and Quantifying Current Workload We need to know (if we can) the breakdown of traffic between the main software applications This will become important if we intend to install new software which is expected to double the traffic of an existing, similar, application There will always be an overhead which cannot be allocated to any application in particular

Determining and Quantifying Current Workload All practical networks go through busy periods during a normal day Many networks have days of the week which are busier than others and seasonal periods such as the lead-up to Christmas The network needs to be designed to cope with the busiest times. So much of the important data will be the data for "busy hour"

Determining and Quantifying Current Workload Sometimes network connections are setup before Christmas and torn down after Christmas because of the extra traffic encountered at this time is so large as to make this an economic alternative (usually telecommunications carriers don’t like doing this but it happens)

Projecting Future Workload This depends on our ability to talk to others in the organisation The company's business plan may include buying a powerful new software package which will increase the load by 70% between some parts of the network Or it may be that we are about to increase our web usage because we are moving into e-commerce

Projecting Future Workload Other effects that change the amount of traffic on the network would be: Increasing sales Increasing personnel and payroll Opening or closing remote locations New operating systems

Projecting Future Workload It may be that some areas are more sensitive than others for the success of the overall business Most companies dealing with the public or a large number of customers would require that inquiries from potential customers received the best possible reception Companies dealing with a few large customers would already have well established relationships

Projecting Future Workload It has also been observed that the improved performance or attractiveness of a new application results in more traffic being generated, just because workers like it better As we look further into the future it becomes more and more difficult to predict what the demand will be This might lead us to plan for only a year in advance. But, if a little extra expense would give us a large increase in performance, we may be justified in taking a little extra risk

Developing the Network Capacity Plan We start with a knowledge of the present network and its traffic loads etc, and our prediction of the future demands of the organisation We will develop the network capacity plan in three steps, facilities, equipment and evaluation More in next weeks lecture

Response Management Response time at the customer level is a very important issue We need to break the response time up into at least Networking delay System response time Output response time Then we can see where the greatest scope for improvement lies