This document intends to provide new projects Maintenance and Inspection Engineering Contractors with the methodology for identifying Safety Critical Elements (SCE) and preparing the baseframe requirements for managing SCEs.

Company have defined the requirements to manage Asset Integrity. The objective is to ensure that the people, systems, processes & resources, which deliver integrity, are in place, in use and fit for purpose over the whole lifecycle of the assets.

To achieve this while considering the vast inventory of assets and activities the general principle is to concentrate management efforts on those elements being the most critical to safety, the objective being to minimize the risk of major accidents. These elements are designated as Safety Critical Elements (SCE).

This document provides guidance for the performance of a production availability study of oil and gas system(s). It deals with:

• The general methodology

• The data used in the study

• The availability modelling and calculations

• The reporting.

This document provides guidance for the performance of a Quantitative Risk Assessment (QRA) of oil and gas  operated installations. It is applicable to offshore or onshore fixed installations and makes allowance for their specific risks and context. The methodology can help for the performance of QRA of mobile installations, although, the risk categorisation may be different.

Managing quality means you understand the expectations of your customer in terms of quality and you put a plan in place to meet their expectations. It is hard to define product or service quality at a high-level because the term "quality” is vague and means different things to different people. You must take the time to define the lower-level characteristics of quality for each specific service or deliverable. If you want to ensure that a service or product meets the client’s expectations of quality, you have to understand the underlying characteristics of quality. For example:

Product Quality. The product is:

• Reliable
• ............................

Service Quality. The people are:

• Responsive
• ................................................

These characteristics are still vague, but now you have some direction that you can use to probe further for more details.

Contact us today to discuss how we can help you strengthen your project, portfolio and PMO processes

 А manager once told me that they could be a better manager if they had better people to manage.

Of course, good people managers can work with all kinds of people, and don't shy away from the challenge of working through difficulty. This is especially true when there is conflict on a project. You need to face the conflict and not ignore it. Ignoring it only makes the problem worse. The earlier you face it, the easier it will be to resolve.

Conflict can occur with your managers, your peers or your staff. Here are some examples of conflict you might experience on projects.

• Your boss is frustrated with progress and takes it out on you openly, in front of others in your team.
• Your colleague wants something from you that you can't provide, or can't do for them within the timeframe required so they get angry.
• Your staff think you're being unrealistic about timeframes, so they handle it badly by raising their voice and being obstructive.

When conflict occurs, take these steps:

1. Take a time out.
2. Defuse the situation. .
3. Identify the cause of the conflict.
4. Solve the problem.
5. Observe body language. 
6. Agree on a course of action - and follow-through.

You can utilize this process to turn a conflict into a team-building and learning opportunity.

Лучший способ внедрить в компанию систему СМК, это использовать уже документированный  апробированный сертифицированный комплект СМК.

1. В родственном или дружественном предприятии одолжить на время полную документированную копию СМК.

2. Изучить и сделать свою минимально необходимую по объему версию СМК для своего предприятия  (3 месяца).

3. Провести аудит сертифицирующим органом и получить сертификат ИСО.

Мы имеем опыт разработки и внедрения СМК в НИПИ, Инжиниринговые компании, Машэкспертные организации, Производственные Компании. Все системы СМК сертифицированы на ИСО 9001, 14001 серии и ПБ 18000.

Делайте бизнес с профессионалами. Пример оглавления руководства по качеству:

The term “Energy Assessment” refers to the methodology of collecting and analyzing available energy utilities related data in order to establish the “big picture” of the breakdown of energy consumption for a particular facility and identify componentbased- energy saving opportunities within the facility.

The purpose of this best practice document is to describe a methodology and introduce short cut tools by which quick assessment for energy efficiency improvement can be conducted faster, cheaper and better. Its scope include quick energy assessment methodology in a step-by-step manner, simple models for data representation, checklists for identifying areas for energy savings and short cut tools for creating and evaluating process initiatives for energy saving for common use in  plants.

Project management processes are defined by MPMM  as "the methods taken to complete a project". Put simply, they are the sets of activities that a Project Manager completes to initiate, plan, execute and close projects. Project Managers use processes to manage a project - whether these are personal processes or a common set of processes defined by your organization. You should periodically take a step back to refine your processes so that they become more and more effective over time. 

The process to improve your processes is not so hard. You can boil it down to three steps.

Step 1: Identify Your Current State Processes

Step 2: Identify Future State Improvements

Step 3: Implement Process Improvements

...................

Process improvement work takes time, diligence and patience to implement changes that help you to manage projects successfully every time.

Вопрос далеко не праздный, не только для отдельной личности, при принятии решения как избавиться (или излечиться?) от употребления алкоголя, но даже для официальной медицины.  Если это болезнь, то тогда после лечения, скажем в стационаре, человек должен выйти здоровым и свободным от болезни под именем алкоголизм. Здоровый человек же, может время от времени выпивать на праздники. А нет.... сразу обычно наступает запой. Вывод: или алкоголизм не болезнь, а если болезнь, то тогда методика лечения никуда не годная. Она выводит из запоя, восстанавливает нормальное функционирование организма и... все оставляет на кругах своя. АА говорит: Раз алкоголик, навсегда алкоголик.

Опыт говорит, что алкоголизм это отсутствие выбора у личности  более полезных шаблонов поведения достижения цели, которая выполняется пьяным поведением. У него есть только два шаблона: 1ый это поведение абсолютно трезвого человека и 2рй это поведение человека в запое .... промежуточных просто нет, так как в нем они и не присутствуют и не присутствовали никогда. Вывод? Нужно создать новые шаблоны поведения, интегрировать их в личность и алкоголик превращается в человека. способного выпить и спокойно остановиться. Т.е. он приобрел новые шаблоны поведения. позволяющими ему быть гибким  в разных обстоятельствах.

Алкоголь это деньги в казну. Но ответственность быть алкоголиком возложена на него самого.

Желающие могут избавиться от зависимости. Это просто, если понимание, что нужно добавить новое поведение.

One of the philosophies of the Agile model is the importance of building workable code in short sprints on an ongoing basis. There are a number of techniques that are ingrained in the Agile model that result in more straightforward and elegant code.

• Code as simply as possible. 

• Build for today.

• Code as flexibly as possible.

• Document the code. 

• Share ownership of the code.

• Refactor the code.

If you look at the total lifecycle of an application, only about small percentage of the cost and time is spent during the development project. The larger percentage is spent in the support and maintenance phase. If you build a good application, the code might run in production for ten years or more. Simple, straightforward and optimized code allows easier understanding, easier error fixes and easier enhancements over the entire lifecycle