 |
| Quick View | | javascript:CoveoShowQuickViewForListItem('{ListId}', {ItemId}) | 0x0 | 0x0 | List | 101 | 2147483647 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
| Quick View | | javascript:CoveoShowQuickViewForListItem('{ListId}', {ItemId}) | 0x0 | 0x0 | List | 101 | 2147483647 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
| Quick View | | javascript:CoveoShowQuickViewForListItem('{ListId}', {ItemId}) | 0x0 | 0x0 | List | 101 | 2147483647 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
 |
|
|
|
|
|
|
|
10/17/2008
The second ALM panel discussion of day 1 at the forum asked identified the key AIM challenges that need to be addressed in operating, reporting, maintaining, and improving lifecycle processes. Panelists included John Cusimano of Siemens Energy and Automation, Tom Hannigan of Zachry, Magnus Pousette of ABB Reliability Services, Jim Simpson of Petro Canada, Ian Gordon of Silcar, and Pradeep Nair of IBM Tivoli. Sid Snitkin served as moderator.
Tom Hannigan had some interesting insights to share on the gulf between design and operations. Tom stated, “I want to give voice to all those maintenance technicians and superintendents who say the four words -- what were they thinking?” He gave the example of a new power plant, which experienced cracks in its 36 inch diameter steam lines. The pipes were 18 inches from the floor, the height of the room was 74 inches, which gave 30 inches of clearance and no way of getting access to the pipes. Great time and expense was spent creating a large opening in the roof, bringing in a crane, etc. This is evidence of the need to make sure systemically that there is a process within the gate system that makes sure that operations and maintenance requirements have been built in, not just design requirements. A lot of software vendors are working on sophisticated systems in the design phase that, with little effort, could have modules added that would address the issue of maintainability of the plant and assets. Modules that ask you questions and force you down a thought process.
Jim Simpson noted that if a design engineer built an airplane, it probably wouldn’t have wheels on it, which perhaps is a bit harsh to the world of design engineers, but it does exemplify the issues that need to be addressed. Simpson stated that one way to drive more operations and maintenance concerns in to the design process would be to have design engineers spend a week in a plant to understand the true realities of what they are designing.
Pradeep noted that IBM Tivoli looks closely at internal communications between operations and maintenance. Why is it that we still have these silos and islands of information that still exist in the enterprise. There needs to be a common standard to send information across the enterprise in a common format that allows people to share best practice information between industries and among industries.
Can somebody come up with a definition of what information is required? According to Tom Hannigan, there is a broad set of categories in operations and maintenance that can be developed, like energy consumption, accessibility, safety issues. You can look at a pump or piping or valve system and look at the safety, accessibility and energy consumption issues that need to be addressed. The engineering and design software vendors can help with that. They can put in modules that force design people to look at these issues. According to John Cusimano, the real weak point is the equipment vendors and the procedures that are purchased and installed. According to Ian Gordon, there isn’t much optimization around the value chain either. It is an opportunity that is immense and this is where AIM can be really useful.
Who should be collecting the information that is needed for asset management? Information is coming from a variety of systems – the DCS, CMMS, data historians, and many other sources. Each system has a different piece of information about that asset. Cusimano stated the availability of a central information database would enable owner operators to have a better change of managing asset information more effectively. 10/15/2008Sid Snitkin Sets the Tone with ARC Defintion for ALM Excellence
ARC's Asset Lifecycle Management Forum in Houston is in full swing now. With about 250 attendees, Day 1 started with a keynote presentation from ARC Vice President Sid Snitkin that answered the questions "What is asset information, what is good asset information, what makes asset information excellence, and what is that worth?"
In ARC’s definition, asset information answers any reasonable question, about any asset, from any stakeholder in the asset lifecycle management program in a way that suits their needs and helps them execute their ALM tasks. Asset information falls into several categories, with the two primary groupings of reference data and activity records. Asset information is essentially the “virtual asset” in the trinity of physical, human and virtual assets that humans need to understand, analyze, and improve the physical plant. But who uses this asset information? Where is it created? Where does it reside across the asset lifecycle? That depends on who has a stake in these processes. EPCs, automation suppliers, and service providers all need access to this data and have a hand in creating it. The information can reside across multiple facets of the lifecycle, but in most cases the people that really need it don’t always get it. Asset information reaches a level of excellence only when it is complete, accurate, consistent, accessible, and timely.
Asset information management (AIM) excellence provides an environment of operational readiness, where plant startup happens flawlessly and the people that need asset information have access to the right information right away. AIM excellence can quickly pay for itself. According to a NIST study, AIM excellence can provide a 1.3 percent savings in installed cost. According to the same study, during operations the payback is 2.8 percent of the value of total assets and a 30 percent improvement in maintenance efficiency. For all the details, you can download Sid's report on Asset Lifecycle Management here.
Dow Looks into the Eye of the ALM Storm
Jerry Gipson of Dow was next on the agenda. In addition to being one of the biggest chemical companies in the world, Dow is also one of the biggest EPCs in the world. But how does Dow prepare for the challenges that a large scale chemical manufacturer faces? Jerry used the analogy of preparing for an impending storm. Could be a physical storm as we saw here in Houston not too long ago, or it could be the recent tumult in financial markets or the everyday challenges faced in plant design and construction. Safety is also critical to Dow, which has a safety culture that has successfully and steadily driven down incidents such as injury, illness, and accidents over the past several years.
Dow has a build and modify facility work process (B&MF) for its projects that asks the central question, “Are we designing for what we want to accomplish with this asset?” One key way that Dow determines this is to drive more collaboration and more shared intent with the IT department. Dow also ensures that engineering data supports ALM, and Jerry acknowledged that the FIATECH organization is bringing the company together and is driving a shared understanding and associated shared outcomes. According to Jerry, “If we look at the aftermath of the storm, we can see its exposed flaws. What can we do to execute the next time to avoid some of these flaws?” To Dow, ALM is delivery of sustainability.”
PetroCanada Looks for ALM Operational Readiness in the Canadian Oil Sands
Jim Simpson of Petro Canada discussed how his company is developing business processes and systems that will be used in new Fort Hills oil sands project. Fort Hills is an integrated mining project and is a world scale open pit mine. They use a large bitumen extraction plant to separate bitumen from sand and produce 140 thousand barrels per day of synthetic crude. With a staff of 2,000 in the far north, a lack of local resource, and high turnover, the overall demographics mean that the staff for PetroCanada will be increasingly younger and less experienced. The tough operating conditions including extreme low temperatures and abrasive oil sands add to the operating challenges.
This means that PetroCanada needs to establish key strategies and develop and state their end state targets. The company also had to develop a risk managed plan to reach their goal, which meant implementing simplified and standardized processes. They needed to automate as much as possible and make that automation scalable, repeatable, and shorten the learning curve.
This means developing processes and systems in advance of the business need. These processes and systems are developed in four phases, starting with the basics and adding on more complexities over time. Each phase is approximately one year. Asset information is an early target, and is recognized as a priority early in the program. O&M information needs to be delivered to the end user at their fingertips in multiple formats. But who is the end user? They include engineers, IT folks, operators, maintenance folks, etc. Handover programs are not enough. Project and vendor information does not equal O&M information. Recommended does not equal accepted or optimized. Recommended procedures and processes need review and revision. In the delivery stage, according to Jim, “some assembly is required”, including preparing the data, preparing documents, assembling and connecting them all together, and then delivering them to end users.
This process must be repeated as required to stay current. Jim’s advice to EPCs was to keep delivering accurate information. There is still a lot of work to do on the part of the owner operator after the information is received. Early delivery of selected information to the owner operator can reduce risk and shorten time to startup. Owner operators will always need to transform, supplement, structure and deliver information to meet their specific requirements for safe reliable operation. In many cases, the effort to do this is not well understood and vastly underestimated.
First Panel Discussion: Answering the Big Questions
The first panel discussion of the morning was moderated by Richard Jackson of FIATECH. Jim Humphries of Fluor, Jerry Gipson, Craig Llewellyn of Emerson Process Management, Scott Hillman of Honeywell, and Blair Wheeler of AspenTech all sat on the panel. The overarching discussion revolved around the questions of what the vision of ALM should be, what are the benefits and challenges and what is needed to attain that vision. Jim Humphries noted that most people are using stage gate processes such as Front End Loading (FEL) 1, 2, and 3, but there is no clear definition of what is required in those stages. No clear definition of the inputs. What is the IT infrastructure? How do you go about building it into a standard process? Processes are facilitated by a set of integrated tools that are built for purpose. There are a lot of generic tools, but they are not optimized for the needs of capital project execution. Owner Operators (O/Os), EPCs, and suppliers need a common view of what those stage gate processes are and can then develop common processes and tools.
Jerry Gipson talked about the need to automate workflow. Manual transfers, data conversions -- all contribute to the current state of being. Can we marry the design build with the operate maintain? There need to be common data models or common subsets of data models. Craig Llewellyn noted that about a third of Emerson’s business is on the Capex side. Establishing an asset management strategy in the FEED phase is becoming increasingly important to Emerson customers. Looking at the individual assets, finding out what information is needed and who needs it, and working that in the early phases of the project to ensure successful startup has become a key priority.
According to Scott Hillman, optimizing during the first year of operation is a key component of Honeywell’s strategy, which it calls Integrated Main Automation Contractor (I-MAC). The idea is to get the owner operator to a state of full operational readiness. Traditional MAC has focused on one dimension of project excellence, but from a business standpoint you need to have a three dimensional approach, which includes project excellence, operational and business readiness (how do they work with owners and EPCs to have everything ready so they are ready to operate fully on day one), and the third dimension of asset lifecycle sustainability.
Blair noted the similarities between AspenTech’s and Honeywell’s approach to providing customers with operational readiness, stating that upfront design is the shortest period in the lifecycle of the asset. Once you turn a plant on, however, you run it for 50 years. The most important decisions are made up front. AspenTech works closely with EPCs and vendors in the early stages. From their perspective it really comes down to the data. It is an issue of consistency, like having two watches each with different times. Owner operators need to normalize the data that is underlying the actual asset as it goes through the lifecycle. Blair stated that AspenTech’s Master Data Model normalizes this.
Jim Humphries of Fluor stated that there is a reasonable consistency of tools that are available today, but when you get down to issues of information needed to operate and maintain the plant there is very little consistency from one project to another. Jim did acknowledge that they (Fluor) are starting to drive the requirements of ISO 15926 into their project requirements.
Humphries also pointed out that within Fluor they have an organization that manages lifecycle design support information. Next? Companies still have a long way to go before they can intelligently address the issue of lifecycle cost. How many engineers really know how to develop a lifecycle cost analysis? Owner operators need more of that kind of support. Jim also proposed that a consortium of ARC, FIATECH, and CII may be able to define what deliverables need to come out of stage gate processes such as FEL 1-3 as they relate to the AIM and ALM processes. Problem is there is no model that is currently accepted across the manufacturing industry. 10/2/2008
- What AIM information is needed to support O/O efforts to identify and overcome key plant production bottlenecks?
- What is required to ensure that models used during process design are kept accurate enough to support analysis during operations?
- How should this be integrated with real-time data collection on asset use and plant performance?
- Who should be responsible for these activities?
- How could/should these modeling efforts be integrated with other efforts like ISO 15926?
- What impact does Strategic Partnerships have on an owner/operators AIM Program?
- What benefits can one get from reusable information, reusable procedures, etc. related to standardized equipment?
- What AIM information about operating facilities and projects should O/O share with their partners?
- Who should manage information content for standard equipment? Who should provide the information systems to store and disseminate the information?
- What changes if any are needed to support the partnership?
- Who pays for what?
- What is the best data management strategy for integrating AIM across all lifecycle stages, all asset stakeholders, etc.?
- What data is kept where and who should be responsible for collecting, managing and distributing this information to everyone else?
- What is the role of information & business process standards in this strategy? Which standards should be used?
- What is the role of on-line asset health monitoring information within the overall AIM strategy?
- What information needs to be tracked and saved? Who should do this and who needs access to this information?
- How should this information be integrated with other Maintenance & Reliability solutions?
- When/How should outside experts be given access to this information? What other information should they have access to? How should their recommendations/actions be integrated with the O/Os overall AIM strategy?
- How should this information be linked with Plant Design solutions and the associated Design & Build information
- What role should AIM play in the development, monitoring and continuous improvement of maintenance strategies? What requirements does this place on the corporation's AIM strategy?
- What role should standards play in the AIM strategy to facilitate benchmarking of maintenance strategy performance across different facilities within a corporation? What about benchmarking external to the corporation - i.e. industry orgs, etc.?
- What AIM info do Operators really need? When do they need it? How do they need it presented? What is the best way for them to access it? What kinds of devices need to be supported? Who should do this?
- What AIM info do Maintenance & Reliability personnel really need? When do they need it? How do they need it presented? What is the best way for them to access it? What kinds of devices need to be supported?Who should do this?
- The value of 3D models in Greenfield Plant Design - when is the investment justified?
- The value of 3D Models in Brownfield Plant Upgrades - when is the investment in a design model justified? When/How should Laser Scanning be used?
- The value of 3D models for O&M - what are the benefits? What kind of model is required?
- What are the tradeoffs in maintenance of Design 3D models?
- What info is needed for Operational Readiness - Plant Design info, Vendor info, O&M Procedures, BOMs, etc.?
- When is it needed? How can this best be supported during Plant Design?
- Continuous vs. One-shot info handover - what are the benefits/challenges?
- Who should collect, structure and transforms the information needed for O&M, but not for Plant Design&Build?
| Quick View | | javascript:CoveoShowQuickViewForListItem('{ListId}', {ItemId}) | 0x0 | 0x0 | List | 101 | 2147483647 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /Domains/ALM/ALM_Blog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /Domains/ALM/ALM_Blog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
|
|
|
|
|