OUTAGE MANAGEMENT. OUTAGE APPROACH/PHILOSOPHY A) Time based / machine operating hours based concept related to OEM recommendations - More expensive than.

Slides:



Advertisements
Similar presentations
Project Management.
Advertisements

Project management.
MONITORING OF SUBGRANTEES
Fiscal Monitoring: Ensuring Accountability of Your Sub-Grantees
Gas Plant Operation and Maintenance Overview Presented by Geoff Vail.
Project management Information systems for management1 Project Management.
Software Quality Assurance Plan
Work Breakdown Structures
1 SW Project Management (Planning & Tracking) Dr. Atef Z Ghalwash Faculty of Computers & Information Helwan University.
Monitoring and Information Systems
Jump to first page Dr. Henry Deng Assistant Professor MIS Department UNLV IS 488 Information Technology Project Management.
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
XII- COST CONTROL, MONITORING & ACCOUNTING
Energy Audit- a small introduction A presentation by Pune Power Development Pvt. Ltd.
Process Engineer’s Role in Project Management Dr Abdullah Malik.
Chapter 3 : Managing the Information Systems Project.
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
S/W Project Management
Client Logo LEAN ENTERPRISE Implementation Workshop.
Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.
1 Chapter 5 Project management. 2 Project management : Is Organizing, planning and scheduling software projects.
Project Post-Mortem University of California Berkeley Extension Copyright © 2008 Patrick McDermott From an AutoContent Wizard 10/27/2007.
Mechanical Integrity Written Procedures. Lesson Objectives  Describe Required Written Procedures for Establishing an MI Program  List Acceptable Sources.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
SacProNet An Overview of Project Management Techniques.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Objectives 4 Understand the basic concepts of project planning and control 4 Explain PERT and Timeline (Gantt) charts.
Glen Fields - Final Project Presentation. What Sets CSI Apart... GBA 573 Consultants Company Background Located in San Diego, CA 5 Engineering Consultants.
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
Pre-Project Components
Jump to first page Dr. Henry Deng Assistant Professor MIS Department UNLV IS 488 Information Technology Project Management.
Produced by: Towards a Rational Cost Model Presenter: Tom Lenahan Tom Lenahan Limited.
1 Project management. 2 Topics covered Management activities Project planning Project scheduling Risk management.
University of Minnesota Internal\External Sales “The Internal Sales Review Process” An Overview of What Happens During the Review.
Lesson 1: Examining Professional Project Management Topic 1A: Identify Project Management Processes.
SOLUTION What kind of plan do we need? How will we know if the work is on track to be done? How quickly can we get this done? How long will this work take.
Chap 4. Project Management - Organising, planning and scheduling
Copyright 2009 John Wiley & Sons, Inc. Chapter 10 Monitoring and Information Systems.
Financial Management and Budgeting The Details. What Is a Budget? A useful tool for keeping track of funds. A useful tool for keeping track of funds.
1 PROJECT MONITORING & CONTROL. 2 Project Monitoring and Control Why do we monitor? What do we monitor? When to we monitor? How do we monitor?
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Checking and Corrective Action EPA Regions 9 & 10 and The Federal Network for Sustainability 2005.
Project Management Processes for a Project
Report Performance Monitor & Control Risk Administer Procurement MONITORING & CONTROLLING PROCESS.
Ch7: Project Monitoring and Control  To reduce differences between plan and actual in the 3D space of T/C/P.  Best utilization of organization’s primary.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
Project Management Information System What?? Objective: –Record & report relevant information and status of various components of project –Highlight the.
SOFTWARE PROJECT MANAGEMENT
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
Copyright 2015 John Wiley & Sons, Inc. Chapter 10 Monitoring and Information Systems.
Copyright 2009 John Wiley & Sons, Inc. Chapter 11 Project Control.
B U D I L U H U R U N I V E R S I T Y POST GRADUATE PROGRAM MAGISTER ILMU KOMPUTER (M.Kom) IS PROJECT MANAGEMENT.
CHAPTER 2 SYSTEM PLANNING DFC4013 System Analysis & Design.
Project Management PTM721S
Why LPA’s? LPA’s can provide low cost system for finding problems and making improvements in Safety, Quality, Delivery, Cost and Morale when used effectively.
Project Planning and Implementation
[Project Name] Post-Mortem
PROJECT NAME POST-MORTEM
Monitoring and Information Systems
[Project Name] Post-Mortem Presentation Template
Project Name Post-Mortem
Why LPA’s? LPA’s can provide low cost system for finding problems and making improvements in Safety, Quality, Delivery, Cost and Morale when used effectively.
PSS verification and validation
Chapter 11 Project Control.
Why LPA’s? LPA’s can provide low cost system for finding problems and making improvements in Safety, Quality, Delivery, Cost and Morale when used effectively.
Risk Management NDS Forum June 23rd 2010.
Management of Change GROUP HSE RULE (CR-GR-HSE-302)
Presentation transcript:

OUTAGE MANAGEMENT

OUTAGE APPROACH/PHILOSOPHY A) Time based / machine operating hours based concept related to OEM recommendations - More expensive than condition based approach - Frequent disassembly / assembly, at times, detrimental to the equipment - Loss of generation, cost of overhauling - Risk of damage through human performance error B)Condition based overhaul concept - More logical being mix of OEM recommendation and technical evaluation of operating data - Longer hours of operation / extra generation benefit, better up-keep of machine due to regular online data assessment / evaluation - Need addressing of Insurance/Regulatory issues, if any.

OUTAGE GOALS & OBJECTIVES Will be performed in strict adherence to schedule and in the shortest time as possible without compensating quality of work, personal safety and integrity of equipment and environment. Ensuring proper documentation on daily basis of work completed with necessary disassembly/assembly records, record of deviations, if any, from the planned work, budget expended and deviations from EHS related issues, if any. Final report enumerating the details of work performed, milestones targeted/achieved, total expenditure, lessons learnt including corrective steps for the next outage. Post outage, equipment performance data analysis

OUTAGE SCOPE Scope of Work - Preparation of Detailed scope of work covering OEM recommendations, past inspection recommendations and inputs from Plant Operation section and various other disciplines. - Identification of key activities concerning plant performance Outage Duration - Outage time frame in line with available resources. - Mile stone dates for completion of key activities ( hold/control point to avoid outage over-run with additional augmentation of resources). - Contingency plan to cover over-run. Outage Budget - Budget estimation for the planned activities. - Contingency plan viz. a viz. Financial impact of each day over-run of the outage.

PRE - 0UTAGE READINESS REVIEW CONTROL MECHANISM Detailed work scope prepared and vetted by all concerned sections. Bar chart integrating all vital activities with critical parts identification. Manpower requirement addition to internal resources identified and addressed. Material status. Status of impending contracts. Safety Plan, including confined work space requirements, working at heights and in restricted plant areas. On site support needs – scaffolding, insulation, temporary power, tooling, equipment, labour force break area accommodations etc. Status of pre-outage work. Contingency plans, inspection plans and resources. Lessons learnt from the previous outages and incorporation in the current outage plan.

PRE-OUTAGE PREPARATORY WORK  Review of available spares/spares on order viz.a viz. requirement as per scheduled activities.  Review of available specialized consumables and items on order, especially “Shelf-Life” related items.  Review of specialized equipment specific T&P.  Confirmation of mandatory testing requirement compliance on tools, tackles and lifting devices.  Calibration compliance confirmation on measuring instruments.  Review of on-site support needs – scaffolding, insulation, temporary power, tooling, special equipment, labor force safety and welfare requirements.  Safety plan  Review of pre-outage operating parameters.

PRE-OUTAGE PREPARATORY W0RK.... Cont’d  Review of specific maintenance related issues need to be addressed during unit shutdown.  Review of online machine performance data – vibration, oil temperatures, expansion (absolute / differential)  Review of changed operating parameters needing specific attention

OUTAGE CONTROL – IMPLEMENTATION PHASE Daily progress review. Identification of bottle necks likely to hinder scheduled completion Necessary assistance to the execution team to address concerns – OEM/Consultant related and other issues Ensure strict compliance of EHS related issues – no compromise on working personnel safety Review of inspection/fact finding reports Liaison with OEM in case of serious findings in the inspection report Weekly review of actual outage expenses vs budgeted expenses Commissioning team progress review to ensure timely start up of the unit

POST OUTAGE - MONITORING Compilation of meaningful outage report Performance Analysis Actual vs budgeted outage expenses Identification of Key Players with necessary recognition/rewards Lessons learnt Key issues to be considered/addressed during next outage

KEY ISSUES  Effective / Realistic activities planning schedule  Pre–outage planning schedule  Outage readiness review process  Effective pre-outage activities completion  Critical path tracking process  Realistic amendment of planned scope of work following disassembly inspection and fact finding report.  Milestones progress review process – resources augmentation to achieve targeted schedule  EHS compliance  Post overhaul performance improvement  Budgeted vs actual expenses  Lessons learnt.