Page 1

Capit al Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

October 2004

3925 West Braker Lane (R4500) Austin, TX 78759 www.fiatech.org ď›™2004 FIATECH


Capit al Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

G. ABSTRACT FIATECH is a non-profit consortium that focuses on the fast-track development and deployment of technologies to improve substantially how capital projects and facilities are designed, engineered, constructed, and maintained. FIATECH develops new technologies and adapts existing technologies from our industry, as well as others, while working with the standards community to accelerate the development of industry-wide standards and guidelines for capital projects. This publication, Capital Projects Technology Roadmap, was developed through a cooperative effort, with input and support from many contributing individuals and organizations, as referenced below. This report is freely available to the public; however, no copies may be made or distributed and no modifications made without prior written permission from FIATECH. To obtain permission for this or other FIATECH publications, contact FIATECH at www.fiatech.org or 512-232-9600.

Copyright Š 2004 by FIATECH. All Rights Reserved.

ď›™2004 FIATECH

October 2004, Element 1


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

Scenario-based Project Planning Element 1 Tactical Plan for the Capital Projects Technology Roadmap Table of Contents SCENARIO -BASED PROJECT PLANNING ......................................................................................................................5 SCOPE............................................................................................................................................................................................ 5 W ORKING TEAM.......................................................................................................................................................................... 5 VISION........................................................................................................................................................................................... 5 CURRENT PROBLEM .................................................................................................................................................................... 6 POTENTIAL BENEFITS AND OPPORTUNITIES............................................................................................................................ 7 POTENTIAL BARRIERS AND CHALLENGES............................................................................................................................... 7 GOALS........................................................................................................................................................................................... 9 STRATEGY FOR A CHIEVING THE GOAL.................................................................................................................................... 9 FOCUS A REAS AND PROJECTS................................................................................................................................................. 11 SEVEN-YEAR TIMELINE ........................................................................................................................................................... 13 CASE STUDIES............................................................................................................................................................................ 14 ORGANIZATIONS W ORKING IN FOCUS A REAS...................................................................................................................... 15 EXISTING RELEVANT RESEARCH A CTIVITIES AND RESULTS............................................................................................. 15 FUNDING SOURCES ................................................................................................................................................................... 15 PROJECT DESCRIPTIONS BY FOCUS A REA ............................................................................................................................. 16 E1-FA1: Work Process Mapping.....................................................................................................................................17 E1-FA1-P1 Map the Decision Process.............................................................................................................................. 17

E1-FA2: Industry Tool Survey..........................................................................................................................................18 E1-FA2-P1 Product and Process Survey and Analysis..................................................................................................... 18

E1-FA3: Reference Data Requirements..........................................................................................................................20 E1-FA3-P1 Industry Costing Reference Data................................................................................................................... 20 E1-FA3-P2 Lifecycle Cost Reference Data...................................................................................................................... 21 E1-FA3-P3 Industry Schedule and Quality Reference Data............................................................................................. 22 E1-FA3-P4 Reference Information Model ....................................................................................................................... 23

E1-FA4: Functional Requirements..................................................................................................................................24 E1-FA4-P1 Develop Working Agreements As Required................................................................................................. 24 E1-FA4-P2 Functional Requirements for Project Risk Assessment................................................................................. 25 E1-FA4-P3 Functional Requirements for the User Interface............................................................................................ 26 E1-FA4-P4 Functional Requirements for Modeling & Simulation .................................................................................. 28 E1-FA4-P5 Define “Grouping” Functionality for Analysis and Output........................................................................... 29 E1-FA4-P6 Functional Requirements for Automated Scheduling and Facility Project Definition.................................. 30 E1-FA4-P7 Define Interfaces with Other Tools ............................................................................................................... 31 E1-FA4-P8 Next -generation Product Specifications ........................................................................................................ 32

E1-FA5: Data Model Requirements................................................................................................................................33 E1-FA5-P1 Data Modeling - Integration with Existing Data Sources.............................................................................. 33 E1-FA5-P2 Define the Data Model for SbPP Data in ALIS............................................................................................. 34 E1-FA5-P3 Define the SBPP Reference Data Model....................................................................................................... 35 E1-FA5-P4 Create the Tools and Database Development Multi-Generation Plan........................................................... 36

E1-FA6: Design & Develop Next Generation Tools and Database...........................................................................37 E1-FA6-P1 Write Software Application(s) and Create and Populate Database(s)........................................................... 37 E1-FA6-P2 Create and Populate the SbPP Reference Model........................................................................................... 38 E1-FA6-P3 Beta Test the SbPP Reference Model and ALIS Using the SbPP Application............................................. 39 E1-FA6-P4 Implementation Plan...................................................................................................................................... 40

2004 FIATECH

October 2004, Element 1, Table of Contents


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

ď›™2004 FIATECH

October 2004, Element 1, Table of Contents


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

Scenario-based Project Planning Element 1 Tactical Plan for the Capital Projects Technology Roadmap SCOPE Provides a comprehensive, collaborative project planning system that captures and analyzes front end data (including business case, scientific data, what-if scenarios, requirements and conceptual design, customer needs, budget and scheduling, and feedback from operations and maintenance) to assist the planning team as well as to provide the initial data capture to be used throughout the lifecycle of the facility.

WORKING TEAM The team members listed here have contributed to the content of this document during its development. For a list of current working team members refer to the FIATECH web site. Jehu Burton, DuPont (Team Co-champion) Sylvia Rappenecker, The Dow Chemical Company (Team Co-champion) Godfried Augenbroe , Georgia Institute of Technology Gary Chanko, Fluor Ben Fergus , CH2M Hill Dr. Martin Fischer, Stanford University, CIFE David Hammond, Office of Civil Engineering, U.S. Coast Guard Frank Miller, Rohm and Haas Mark Mummert, Rohm and Haas

VISION The Vision statement describes what is wanted in the future. The future project planning system will provide interactive evaluation of project alternatives, enabling creation of conceptual designs and project plans that best meet the needs of all stakeholders. This collaborative planning environment will provide full awareness of the impacts of decisions on costs, schedules, and lifecycle performance. The system will provide the initial input to a comprehensive project plan and specifications, ultimately captured in an Asset Lifecycle Information System, to guide subsequent project designs and support downstream project functions. The Asset Lifecycle Information System is a foundation of the future state vision, serving as the repository for all design and planning information and the interface for all systems and applications. Work Processes: Project teams will interact with customers and other stakeholders to review various options and to develop and refine a set of project requirements and plans. Options will be evaluated using a rich suite of modeling and simulation (M&S) tools that enable rapid real-time exploration of different scenarios to arrive at optimum decisions both within the context of a project, and within the context of a facility lifecycle . Project decisions will provide the conceptual basis for the detailed design. Scenarios can be reevaluated at project milestones or at critical decision junctures to validate and/or modify the planning for subsequent project phases.

ď›™2004 FIATECH

October 2004, Element 1, Page 5


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

The project planning team will interface with the design team to iterate conceptual designs, using modeling and simulation tools that permit planners and stakeholders to view and concur on such project areas as functionality, aesthetics, layouts, flow sheets, and construction strategies. Technology Enablers: The M&S tools are a suite of powerful assessment and planning tools, linked to the Asset Lifecycle Information System and to external information sources that will enable project teams to quickly capture, iterate, and determine optimum solutions based on accurate and complete data. The M&S tools will enable financial risk assessment as well as consideration of options related to the capital facility, such as what to build, where to build and how to build. Various scenarios can be evaluated assessing the impact of risk and business factors such as 1) site selection, 2) technology selection, 3) current and future capacity needs, and 4) facilities operation and maintenance strategies. Although the project planning system will not model scenarios involving “pure” business decisions (e.g., market assessments of business needs and trends, determination of market share, venture modeling, own versus buy decisions, etc.), the model will illuminate the cost and schedule impact of alternative project execution strategies and decisions. The planning environment will encompass conceptual designs for review and selection, requirements, objectives, technical and business issues, and analysis of options. Captured knowledge from previous projects and links to business systems will determine availability and prevailing pricing of labor, materials, and equipment. This will provide accurate cost and schedule estimates to support project financial decisions and facilitate authorization to proceed to the design phase. These inputs will include accurate market forecasts and full knowledge of regulatory, technical, demographic, and other factors. The suite of M&S tools will also interface with external databases to capture regulatory requirements, codes and standards and to correlate them to the design requirements. It will automatically generate an initial work breakdown structure and other key elements of the project management toolset to provide a framework for costing, scheduling, and workflow tasking. Model-based risk assessment tools will enable planners to explore physical and financial risk scenarios to make informed decisions that balance cost drivers against risk factors.

CURRENT PROBLEM The Current Problem statement describes the existing situation. There have been many technology advances in engineering design, construction, and facility operations; however, project planning has remained a very intuitive process with little technology automation. Project planning is carried out by project engineers who may or may not have the experience needed to understand all of the project variables and their complex inter-relationships. Many times, project requirements must be extracted from business teams by project team members who may not know the right questions to ask and are unable to analyze and identify project alternatives to meet the requirements. There is little or no automated scenario modeling and simulation capability available to the decision makers, leading to sub-optimized project plans. Many projects follow a tight timeline forcing inexperienced team members to make “seat-of-the-pants” decisions with little or no data. Many senior project professionals have experience-based rules-of-thumb that are not well documented or readily accessible by others. Some of the variables addressed in the decision-making process are unique to specific projects, may need to be weighted differently, and may have over-riding or dominating factors.

2004 FIATECH

October 2004, Element 1, Page 6


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

Future project success is dependent on early identification of all the risk factors and development of suitable contingency plans. There are currently available no expert systems capable of capturing current project successes and failures and translating that knowledge into improved project strategies.

POTENTIAL BENEFITS AND OPPORTUNITIES The benefits of scenario-based project planning (SbPP) include elimination of costly errors up-front, agreement among all stakeholders, compression of the timeline from requirements to full design specifications, and the ability to explore numerous options quickly, prior to selecting a project execution strategy. These features will result in better, safer, more secure facilities delivered faster and at less cost. Specific benefits to the stakeholders are cited in Table 1 below.

Table 1. Benefits of Scenario-based Project Planning for Industry Stakeholders Stakeholder Owner/Operators Architects Designers/Engineers Constructors Material/Equipment/ Technology Suppliers

Specific Benefits Rapid and complete agreement on what will be designed, built, and operated – reduces cost, risk, and project cycle time. Considers views of all stakeholders. Close integration and alignment with the engineers, contractors, and owners to eliminate misinterpretation and optimize facility requirements and features. Accurate and complete electronic definition of project requirements – reduces design time, eliminates ambiguities, and reduces technical ris k. Provides a voice in the early phases to assure “constructability”, reduce risks, and eliminate unnecessary challenges – reduces build time and cost. Enables early start on long lead items, more cost-competitive solutions through clear specification of requirements, and early mitigation of technical and schedule risks.

NOTE: There will be a need to benchmark the potential benefits shown in Table 1 – if we succeed in creating the vision, what will it be worth? We need to connect performance in the Roadmap Elements to standard improvement metrics in the industry, such as IPA or CII Benchmarking. This will most likely become a separate FIATECH project.

POTENTIAL BARRIERS AND CHALLENGES Scenario-based project planning involves the iteration of many variables with complex relationships. Modeling these relationships will be difficult because the importance of individual variables will be unique to specific projects and will vary across projects. One of the challenges in scenario based project planning is to be able to understand and incorporate complex interrelationships of variables to achieve the best decision in alignment with values and strategies such as sustainable development. As stated by the International Institute for Sustainable Development, related to business strategies “the aim is to seek win-win situations which can achieve environmental quality, increase wealth, and enhance competitive advantage... In the pursuit of economic, environmental and community benefits, management considers the long-term interests and needs of the stakeholders.” One goal of scenario based project planning is to enable stakeholders to maximize the “win-win situations” that will enhance the sustainability of projects and the surrounding community. Variables to consider in scenario-based project planning include the following (recognizing that weighting factors and level of importance for each variable will depend on specific business needs of each project):

2004 FIATECH

October 2004, Element 1, Page 7


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

A. Site selection 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12.

Market location Raw material sources Logistics availability - incoming and outbound Political and social climate Environmental impact - water effluent, air emissions, social factors Personnel hazards - explosion potential, toxic releases Tax incentives Governmental permitting - national and local, building, sewers, highways, railroads, navigation, navigable waters, aircraft, environmental Staffing - labor pool, skill level Site soils, groundwater, and geology Infrastructure - available services - electrical power, telephone, water, railroad, highways Cost of services – energy costs, construction and operating labor

B. Facility Technology 1. Is the technology state-of-the-art? 2. Is it competitive - world class manufacturing 3. Alternatives - waste treatment and disposal requirements, energy consumption C. Project Strategy 1. 2. 3. 4. 5.

Front end loading Production design Construction - stick built versus modular construction Contracting - lump-sum, cost-plus-percentage-of-cost, incentive? Project information strategy (collaboration, work flow, document management)

D. Sourcing/Procurement 1. 2. 3. 4. 5. 6.

Engineered equipment Field material Field labor Raw materials Domestic versus import requirements Contract services

E. Schedule 1. Start up timing 2. Rate of capacity attainment F. Project Budget 1. Capital and non-cap 2. Cash flow requirements/limits G. Risk assessment and Contingency Planning/Exit Strategy 1. 2. 3. 4. 5.

Process / Structure technology Logistics – how to transport product? Economic risk (project economics, market assumptions still true) Environmental risk Contractual risk

H. Information Asset

2004 FIATECH

October 2004, Element 1, Page 8


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

1. Content requirements for information handoff 2. Format requirements for information handoff (documents, databases, paper, etc.) 3. Timing and availability of the information deliverable (during, after) I. Business requirement flexibility 1. Capacity flexibility 2. Product flexibility 3. Quality flexibility

GOALS The Goal statement describes what is expected to be achieved. From a technological standpoint, the goal is to achieve a fully automated project planning and conceptual design environment. From an operational viewpoint, the goal is to provide a level of automation and human interaction that best serves all the stakeholders by providing the ability to review project planning options and scenarios quickly and interactively, resulting in the highest value business-based project plan. All of the data and information generated in this phase of the project is part of an Asset Lifecycle Information System (described in Element #9 – Lifecycle Data Management and Information Integration). This system is the interface for all project operations, applications, and information flows and must be maintained and validated throughout the lifecycle of the project.

STRATEGY FOR ACHIEVING THE GOAL The strategy statement describes how we see the goal being achieved. The figure below represents the emerging model for the scenario-based planning process in the overall capital project value chain. We believe execution of scenario based planning includes three very highlevel phases: Define Requirements, Evaluate Alternatives, and Make Decisions. Each phase is described with the high-level attributes that characterize the ideal process state. The figure also indicates gaps in the execution and performance of this work process relative to today's state of the art. It identifies some potential information technology enablers which will help close the gaps. We recognize that work process improvements may also be needed to close the gaps; these will be added to the chart as they are identified.

Scenario-based Project Planning Steps: Major attributes of the ideal state for this Roadmap element:

2004 FIATECH

Define Requirements Evaluate Alternatives Collaborate, Speed, Concise Data collection, Right level of quantitative Creation of options, data, Analysis of options, Clear definition of Negotiation, requirements – ranges, Dependency analysis, Sound set of business Iterative, requirements, Requirements finalized Fact-based, Leverage global broad-spectrum knowledge Current Activity

Make Decisions Scenarios processed with all stakeholders, Decision documented, Visible, Leverage-able into future

October 2004, Element 1, Page 9


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

Scenario-based Project Planning Steps: Previous or current projects:

Define Requirements

Problem space:

Complexity, Data unavailable, Requirements not fully expressed, Reliance on tacit knowledge

Evaluate Alternatives

Make Decisions

Gaps

Technologies that may enable the ideal state:

Don’t understand require ments, Less analysis done, No automation, Silo flow, Have to “extract requirements”, Knowledge unavailable Technology Enablers Business intelligence, Data mining, Knowledge mgmt and Scenario modeling, collaboration, “Process recording – of the Integration of information, thought process”, Digitized best practices – Simulation, requirements questions – Digitized best practice – “interrogatory”, options Workflow Organization and Process Enablers

Intuition-based decision, Unclear accountability, Lack of clarity, Lack of scenarios, Decision questioned

Visualization, Knowledge mgmt, Document mgmt.

Organizations and processes that may enable the ideal state:

As practitioners, when we evaluate the current state of our processes against the ideal state, we can see real gaps in our capabilities. Closing these gaps in capability will drive tangible value in the capital project value chain. These are the future state capabilities that we wish to achieve and the value to be realized. We believe these future state capabilities can be achieved through the application of organization, process, and technology enablers. Our strategy addresses how the gaps may be closed and the future state capabilities achieved in order to realize the vision of a fully integrated and automated project planning process for capital projects. The strategy provides the framework in which projects may be chartered to leverage organizational, process, and information technology enablers to close the gaps. The specific steps of the strategy are described below. Note that projects addressing combinations of these elements may be in progress concurrently, to maximize progress. •

Engage Stakeholders: Establish a methodology for engaging a broad participation and feedback with stakeholder groups in the industry (e.g., owner/operators, EPCs, project planning consultants, software providers, etc.). Identify subject matter experts with deep expertise in scenario-based project planning, simulation and modelin g of business and work processes.

Leverage Industry Knowledge: Assemble a list of the existing resources (tools and work processes) that are widely used in the industry today. Assess degree of utilization and applicability of these resources in achieving the vision.

Identify Emerging Technology and Directions : Identify emerging tools and technology platforms for modeling / simulating scenario-based project plans.

2004 FIATECH

October 2004, Element 1, Page 10


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

Evaluate and Develop: Evaluate both existing resources and emerging tools and technologies, and develop specifications for technologies and tools that must be developed to fulfill the requirements of scenario-based project planning.

Manage for Value: Explore all three gap segments described above to better understand the value impact on the work process for each segment, and to deliver a set of prioritized opportunities in these areas:

o Transform the requirements definition process o Accelerate the delivery of viable alternatives with high efficiency o Drive quality decision-making and lower risk Govern Project Portfolio: Establish an opportunity portfolio management methodology for project prioritization, chartering and resourcing.

Drive Change: Demonstrate and implement organizational, work process, and technology solutions, track experiences, and establish key performance metrics.

Measure Performance: Establish mappings between identified gaps and industry project execution benchmarking metrics (e.g., IPA and CII). Identify any new metrics needed and establish methodologies for tracking. Start tracking well before implementation of improvement projects in order to obtain a solid base of data reflecting the current state.

We will implement the above strategies by chartering and executing projects. We have begun to develop a project portfolio in several major Focus Areas. Emerging focus areas and projects are described in the following sections.

FOCUS AREAS AND PROJECTS The focus area section describes what we are going to focus on, and specific projects are proposed within each focus area. Focus Areas are the broad description of what this Roadmap element is going to do. Each focus area will be addressed through several projects, conducted over time. The project titles are linked to the detailed project descriptions provided in a later section of the document. E1-FA1: Work Process Mapping Identify and document the SBPP process by which project planning decisions are made, and the broad information inputs and outputs required to support those decisions. Projects: E1-FA1-P1 Map the Decision Process E1-FA2: Industry Tool Survey Using the SBPP Work Process Map, identify the Reference Data and Tools available in the industry today to support the SBPP process. Projects: E1-FA2-P1 Product and Process Survey and Analysis

2004 FIATECH

October 2004, Element 1, Page 11


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA3: Reference Data Requirements Identify and document the Reference Data requirements for delivering next-generation SBPP capability. Projects: E1-FA3-P1 Industry Costing Reference Data E1-FA3-P2 Lifecycle Cost Reference Data E1-FA3-P3 Industry Schedule and Quality Reference Data E1-FA3-P4 Reference Information Model E1-FA4: Functional Requirements Identify and document the functional requirements necessary to support input, output and analysis activities in the next-generation SBPP tools. Projects: E1-FA4-P1 Develop Working Agreements As Required E1-FA4-P2 Functional Requirements for Project Risk Assessment E1-FA4-P3 Functional Requirements for the User Interface E1-FA4-P4 Functional Requirements for Modeling & Simulation E1-FA4-P5 Define “Grouping” Functionality for Analysis and Output E1-FA4-P6 Functional Requirements for Automated Scheduling and Facility Project Definition E1-FA4-P7 Define Interfaces with Other Tools E1-FA4-P8 Next-generation Product Specifications E1-FA5: Data Model Requirements Identify and document the data model requirements necessary to support the functional requirements identified in FA3, for the next-generation SBPP tools. Include definition of data exchange, validation, interfaces, for the data held in ALIS, and for any external Reference Data. Projects: E1-FA5-P1 Data Modeling - Integration with Existing Data Sources E1-FA5-P2 Define the Data Model for SbPP Data in ALIS E1-FA5-P3 Define the SBPP Reference Data Model E1-FA5-P4 Create the Tools and Database Development Multi-Generation Plan

2004 FIATECH

October 2004, Element 1, Page 12


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA6: Design & Develop Next Generation Tools and Database Complete the application system design, and the database schema for the next-generation SBPP tools. Develop, test, and deliver the tools and reference database. Projects: E1-FA6-P1 Write Software Application(s) and Create and Populate Database(s) E1-FA6-P2 Create and Populate the SbPP Reference Model E1-FA6-P3 Beta Test the SbPP Reference Model and ALIS Using the SbPP Application E1-FA6-P4 Implementation Plan

SEVEN-YEAR TIMELINE A timeline is proposed for the projects within this tactical plan. Assumptions used for the seven-year timeline shown below: 1. Preparation for each project will take about 3 months (1 quarter). Project preparation includes identifying funding, resourcing and set-up. Preparation time is included in the following timelines. 2. Project teams will form and disband for each project (unless the team wishes to continue to do another project). 3. The "X" is placed in the year of the most intensive work, although there may be opportunities to start some phases earlier or to run some projects in parallel for a while.

Yr 1

Yr 2

Yr 3

Yr 4

Yr 5

Yr 6

Yr 7

E1-FA1: Work Process Mapping E1-FA1-P1

Map the Decision Process

X

E1-FA2: Industry Tool Survey E1-FA2-P1

Product and process survey and analysis

X

E1-FA3: Reference Data Requirements E1-FA3-P1

Industry Costing Reference Data

X

E1-FA3-P2

Lifecycle Cost Reference Data

X

E1-FA3-P3

Industry Schedule and Quality Reference Data

X

E1-FA3-P4

Reference Information Model

X

E1-FA4: Functional Requirements E1-FA4-P1 E1-FA4-P2 E1-FA4-P3 E1-FA4-P4 E1-FA4-P5 E1-FA4-P6

Develop working agreements as required Functional Requirements for Project Risk Assessment Functional Requirements for the User Interface Functional Requirements for Modeling & Simulation Define “Grouping” Functionality for analysis and output Functional Requirements for Automated scheduling and facility project definition

2004 FIATECH

X X X X X X

October 2004, Element 1, Page 13


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

Yr 1

Yr 2

Yr 3

E1-FA4-P7

Define Interfaces with other tools

X

E1-FA4-P8

Next-generation product specifications

X

E1-FA5: Data Model Requirements Data Modeling - Integration with existing data E1-FA5-P1 sources E1-FA5-P2 Define the Data Model for SbPP data in ALIS E1-FA5-P3

Define the SBPP Reference Data Model

Create the Tools & Database Development E1-FA5-P4 Multi-Generation Plan E1-FA6: Design & Develop Next Generation Tools and Database Write Software Application(s) and create and E1-FA6-P1 populate database(s) E1-FA6-P2 Create and populate the SbPP Reference Model E1-FA6-P3 E1-FA6-P4

Beta Test the SbPP Reference Model and ALIS Using the SbPP application Implementation plan

Yr 4

Yr 5

Yr 6

Yr 7

X X X X

X X X X

CASE STUDIES •

DuPont, one of the world’s most diverse manufactures, applies a discipline called front-end loading (FEL) to maximize efficiencies in its capital projects. While this has nothing to do with moving dirt, it does have everything to do with assuring a solid foundation from inception for every project. First, a Business Objectives Letter is used to create alignment between business goals and project obje ctives. This describes the business objectives for the project, what the business expects of the project team, and the criteria/principles that the team will follow in developing the project. Gatekeeping Reviews at the end of each stage of FEL evaluate adherence to capital effectiveness best practices and business objectives. This is a prerequisite to going on to the next stage of the project, and gives the team an opportunity to review and gain buy-in with the project sponsors and business leaders. These discussions also enable all the stakeholders to interact to assure project success. Process Hazards Screening Reviews are held to identify potential acute hazards and concerns, and to recommend any broad scope changes that could significantly reduce the hazards. This step also determines if detailed hazards reviews are needed. The review includes assessment of occupational health and toxicity issues, initial hazards classifications per standards, and identific ation of critical components, equipment, and systems. – Contributed by Judith W. Passwaters, DuPont Company

The CII has created tools based on industry Best Practices that are excellent guides for project definition and planning including areas related to constructability. Other best practices focus on teambuilding and partnering. The PDRI – the Project Definition Rating Index for Building Projects – and the PDRI-I for Industrial Projects offer comprehensive checklists that support scope evaluation and identification of areas for improvement.

The Patriot missile system that first saw action in Desert Storm in the early ‘90s started life as a program called SAM-D in the 1960s – a staggering 30-year development span. Aggressive efforts by industry and government both changed the defense business model and leveraged new technologies to radically reduce time-to-market. The results have been amazing: the winning prototype of the new, radically advanced Joint Strike Fighter (JSF) aircraft started the design phase in 1998 and began first flights only 2 years later in a “same as production” configuration which will begin rolling off the assembly line in 2004-05.

2004 FIATECH

October 2004, Element 1, Page 14


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

The electronics industry has responded with the “fast turnaround fab” – a facility designed to produce for a limited time span, based on the most current technology, and then be changed out or decommissioned.

Bechtel is one of the world's largest engineerin g and construction firms, with over $14.5 billion in new business booked in Financial Year 2000. Reductions in delivery time and plant construction costs are key factors in their success. To accomplish this, Bechtel init iated a process in the early 1990s of standardizing power plant designs. There are less than 10 standard designs, each of which includes a set of process drawings and physical models along with associated performance and cost data. These standard designs are stored ele ctronically, enabling rapid modification and configuration to a specific customer requirement. This process significantly reduced the delivery time and cost of power plants over the past decade including Egypt’s first privately owned power plant, Sidi Krir, completed within budget and ahead of schedule in December 2001. – Thomas Ulrich, “Bringing Power to the People,” Bechtel Briefs, April 2001. www.bechtel.com/pdf/brief0401.pdf

Lack of industry standards has long impeded management of the planning stages of capital projects. The National Institute of Standards and Technology (NIST) is the most visible champion for Research and Development (R&D) that supports this need and is working towards product data standards and integrated information systems to enable more efficient project planning. A major thrust in this area is the Construction Integration and Automation Technology (CONSIAT) program, which is aimed at significantly reducing cycle time and lifecycle cost through integration and automation of project information.

Another notable NIST activity is PlantSTEP, being developed through a consortium of EPCOM companies and suppliers. The primary focus is to develop and implement data exchange standards based on ISO 10303 (International Standards Organization). This effort is coordinated with related activities such as PIEBASE (Process Industries Executives for Achieving Business Advantage Using Standards for Data Exchange), a global organization for process industry consortia and companies.

The International Alliance for Interoperability (IAI) is developing Industry Foundation Classes (IFCs) as a basis for information sharing in engineering, construction, architecture, and facilities management. IFC project models define individual buildings for which compliant applications can exchange information accurately. Current activities include advances in XML standards to enable seamless flow of text-based information via the web; development of IFCs to support code compliance applic ations during design; and IFCs related to cost estimating and scheduling.

ORGANIZATIONS WORKING IN FOCUS AREAS To be developed.

EXISTING RELEVANT RESEARCH ACTIVITIES AND RESULTS To be developed.

FUNDING SOURCES To be developed.

2004 FIATECH

October 2004, Element 1, Page 15


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

PROJECT DESCRIPTIONS BY FOCUS AREA Projects are described below within each of the Focus Areas. The project template applied to each project includes: Project Title, Objectives / Deliverables (what result), Purpose / Business Driver(s) (why), Ties / Dependencies / Overlaps (with other projects or Roadmap elements) (constraints, boundaries), Urgency / Timeline (when), Process / Activities (how), and Resources (who). Each project will be more fully defined as time progresses. At this point the project descriptions should indicate what the project will do in sufficient detail to get potential participants interested and to understand the timing and dependencies between projects. Timing or scheduling of these projects is presented in the section, the Seven-year Timeline. Many of these projects in Roadmap Element 9 may need to be conducted concurrently, as sub-projects of one larger project.

ď›™2004 FIATECH

October 2004, Element 1, Page 16


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA1: Work Process Mapping Projects: E1-FA1-P1 Map the Decision Process Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Map the Decision Process Objective: Describe/map the decisions making process including participants, timing, milestone, inputs and outputs (deliverables). Deliverables: a) Work Process Map for the SBPP activity Purpose: Improve productivity of scenario-based project planning Business Drivers: a) No predecessors to this project. b) This project is the predecessor to all other projects in the SBPP Roadmap Element.

1.

2. 3. 4.

5. 6. Resources (who, where)

2004 FIATECH

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). Staff and initiate the project. Identify the high-level steps in the SbPP process. Identify the decisions made in each step of the process, and the information flows (inputs and outputs) of each step. Include the information/knowledge needed by each participant in the decision making process and the source including business and client requirements for the facility, and prioritization of those wants. Re-engineer and streamline the work process to create a “next -generation” work process. Document and publish the results.

Individuals: (people who want to work on this project) Organizations: (organizations working this topic already)

October 2004, Element 1, Page 17


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA2: Industry Tool Survey Projects: E1-FA2-P1 Product and Process Survey and Analysis Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why)

Ties / Dependencies / Overlaps (constraints, boundaries)

Urgency / Timeline (when)

2004 FIATECH

Product and process survey and analysis Objective: Identify and evaluate decision modeling products for use in making decisions identified by Focus Area 1 with project-specific knowledge of the variables listed within the Potential Barriers and Challenges section. Deliverables: a) Report of the available models and relevant published research including a recommendation on further work needed to complete the objectives of this project. b) A procedure for evaluating the commercially available decision modeling software products c) A list of candidate products proposed for evaluation and testing d) Report of the testing results compared to the evaluation criteria including recommendations and a path forward. Purpose: To identify and evaluate commercially available decision modeling products that are capable of analyzing the particular complex nature of facilities and the interrelated variables. A second purpose of the evaluation is to decide if commercially-available models are adequate to meet our objectives or if additional development of decision models for this type of situation is needed. Business Drivers: Identifying commercially available tools is the first step in a cost benefit analysis to decide if purchasing an existing tool is preferred over researching and developing a new tool. a) Scenario-based Project Planning (SbPP) Focus Area (FA) #1 will define SbPP decisions that need to be made. The decision modeling products will be evaluated with respect to their capability to address these decisions. b) Having the variables listed within the “Potential Barriers and Challenges” section will enable this project to proceed once the types of decisions are known from FA1. c) Project #2 in this Focus Area relies on the results of this project. d) Cost and risk are significant factors in the decision making process. Therefore, the results of SbPP FA4–tools for cost-based evaluation of project alternatives, and SbPP FA5–tools for risk-based evaluation of project alternatives will facilitate use of the decision models, but the results are not required for completion of this project or Focus Area. e) SbPP FA4-1–Interaction with Asset Lifecycle Information System includes storing relationships between project variables. The tools used in this Focus Area will facilitate capturing the relationships among these variables and are expected to output these relationships to the Asset Lifecycle Information System. This project can commence once the types of decisions to be made are known from Focus Area 1. This project is estimated to be completed within 6 months.

October 2004, Element 1, Page 18


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

Project Title Process / Activities (how)

Resources (who, where)

ď›™2004 FIATECH

Product and process survey and analysis 1. Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Identify published research on evaluations of existing commercial decision modeling products, published processes and comparative studies for analyzing complex interrelated system variables. 4. Search for expertise that could be applied to the capital projects industry while casting a broad net to look for research related to making decisions in complex systems. 5. Compile a summary report of the available models and relevant published research including a recommendation on further work needed to complete the objectives of this project. 6. Develop a procedure for evaluating the commercially available decision modeling software that includes use of the software to be evaluated. 7. Identify and survey the available commercial software and prepare a list of candidates for evaluation and testing. 8. Establish evaluation criteria for the decision modeling software. 9. Evaluate the decision modeling software and recommend leading candidates for testing. 10. Test the recommended decision modeling software. 11. Prepare a report of the testing results compared to the evaluation criteria including recommendations and a path forward. Make specific recommendations regarding the need and priority for Project #2 that would prepare a product specification for the next generation decision modeling software with enhanced features to better meet the needs of the capital projects industry. Note: A listing of decision science organizations and decision modeling software is presented at groups.msn.com/DecisionModeling/yourwebpage1.msnw and from the Decision System Laboratory of the University of Pittsburgh at www.sis.pitt.edu/~dsl/software.htm. An example of a comparative analysis is the Trade-Off Analysis Planning and Procedures Guidebook prepared for the U.S. Army Institute for Water Resources Decision Methodologies Division, April 2002 IWR 02-R-2 at www.iwr.usace.army.mil/iwr/pdf/tradeoff.pdf Individuals: (people who want to work on this project) Organizations: (organizations working this topic already)

October 2004, Element 1, Page 19


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA3: Reference Data Requirements Projects: E1-FA3-P1 Industry Costing Reference Data Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

ď›™2004 FIATECH

Industry Costing Reference Data Objective: Perform an industry survey to determine availability of license-able costing databases, availability of services for refreshing the cost data with current industry experience, and applicability of these costing databases to the types of facilities we are targeting (e.g., buildings, civil works, harbors, airports, process plants, power plants, platforms, pipelines, etc.). Deliverables: Based on findings, either identify best-in-class data sets, or document why the industry has failed to produce such a data set, and outline the high-level requirements of the data set. Purpose: Identify existing capabilities in the industry. Business Drivers: Avoid duplication of effort, leverage existing capability, and understand capability gaps. This project is a pre-requisite for the others in this Focus Area.

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Identify key subject matter experts (including planners, estimators, project definition subject matter experts) 4. Determine data requirements in our industry. 5. Survey reference data offerings in the industry. 6. Map available reference data to industry data requirements. 7. Report gaps and recommendations. Individuals: (people who want to work on this project) TBD Organizations: (organizations working this topic already) TBD

October 2004, Element 1, Page 20


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA3-P2 Lifecycle Cost Reference Data Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

2004 FIATECH

Lifecycle Cost Reference Data Objective: Identify metrics for lifecycle costs which are broadly applicable in various segments of the facilities project industry (e.g., buildings, civil works, harbors, airports, process plants, power plants, platforms, pipelines, etc.). Establish statistical relationship between key project cost factors (e.g., project cycle time, constructability, equipment reliability, material availability, logistics, etc.), and these lifecycle cost metrics. Deliverables: Purpose: Business Drivers: Identify key variables and interrelationships for scenario modeling. a) From SBPP FA1 “Identify Decisions”, determine the decisions to be made, in order to determine the types of metrics needed. b) From SBPP FA4-1 “Industry Costing Reference Data”, determine which metrics are already supported by data available to the industry.

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Gather requirements from SBPP FA1. 4. Gather available data from SBPP FA4-1. 5. Identify ideal metrics, based on what is necessary for decision support, and what is feasible in the industry. 6. Identify those metrics which are, or can be, aggregated across companies, and those that must stay within a company. 7. Propose tools and work processes which can be applied to gather both the “public” and “private” metrics. 8. Propose analysis methods and tools to assess the metrics. 9. Report results. Individuals: (people who want to work on this project) TBD Organizations: (organizations working this topic already) TBD

October 2004, Element 1, Page 21


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA3-P3 Industry Schedule and Quality Reference Data Project Title Objectives / Deliverables (what result)

Industry Schedule and Quality Reference Data Objective: Perform an industry survey to determine availability of license-able reference databases, availability of services for refreshing the reference data with current industry experience, and applicability of these reference databases to the types of facilities we are targeting (e.g., buildings, civil works, harbors, airports, process plants, power plants, platforms, pipelines, etc.). Deliverables: Based on findings, either identify best-in-class data sets, or document why the industry has failed to produce such a data set, and outline the high-level requirements of the data set.

Purpose / Business Driver(s) (why)

Purpose: Identify existing capabilities in the industry. Business Drivers: Avoid duplication of effort, leverage existing capability, and understand capability gaps.

Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

ď›™2004 FIATECH

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Identify key subject matter experts (including planners, estimators, project definition subject matter experts) 4. Determine data requirements in our industry. 5. Survey reference data offerings in the industry. 6. Map available reference data to industry data requirements. 7. Report gaps and recommendations. Individuals: (people who want to work on this project) TBD Organizations: (organizations working this topic already) TBD

October 2004, Element 1, Page 22


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA3-P4 Reference Information Model Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

ď›™2004 FIATECH

Reference Information Model Objective: Develop and validate functional description of the reference information model including data needed, data obtained from costing, project management and reporting systems, functionality and decision support required from the model. Deliverables: Purpose: Business Drivers: Capture and re-use of integrated current and historical costing information provides stronger basis for project planning decision-making. a) This project is a pre-curser to completing the planning data design in ALIS (Roadmap Element 9)

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Map current data linkages between available tools and data repositories. 4. Identify necessary ties between technical design data, and planning reference data. 5. Identify necessary ties between procurement & logistics data, and planning cost, schedule and quality data. 6. Identify necessary ties between other operational and performance data and the planning reference data. 7. Perform gap analysis. 8. Document data definitions, relationships, and versioning requirements, for the costing data to be stored. 9. Report recommendations, and communicate to ALIS design team and to the relevant industry software and data providers. Individuals: (people who want to work on this project) TBD Organizations: (organizations working this topic already) TBD

October 2004, Element 1, Page 23


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA4: Functional Requirements Projects: E1-FA4-P1 Develop Working Agreements As Required Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why)

Develop working agreements as required Objective: To create the working relationships and legal agreements between software vendors and practitioners which will be the basis of the team that will work to develop next -generation product specifications for decision modeling software to better address the needs of the capital projects industry and gain the endorsement of software vendors to develop products to meet the enhanced specifications. Deliverables: a) List of cooperating vendors b) List of “review” vendors c) List of other participants and stakeholders (e.g., research teams, consortia, academia, engineering firms, etc.) d) Legal agreements, or documented working relationships as needed with all parties Purpose: To leverage existing tools available in the capital projects industry. Business Drivers: To work collaboratively with software vendors to develop product specifications that will be of mutual value and benefit.

Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

2004 FIATECH

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Obtain candidate list from Industry Survey performed earlier. 4. Draft charter for “contributing” and “reviewing” vendor agreements. 5. Present proposals to the vendors, and solicit involvement. 6. Finalize agreements with the selected vendors. Individuals: (people who want to work on this project) Organizations: (organizations working this topic already)

October 2004, Element 1, Page 24


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA4-P2 Functional Requirements for Project Risk Assessment Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries)

Functional Requirements for Project Risk Assessment Objective: Document the functional requirements to automatically identify, represent, characterize, and incorporate potential risk information into the project management system, to analyze the risk factors, to model the project outcomes, and to generate reports for project planning purposes. Deliverables: a) SbPP Functional Requirements document. Purpose: Improve productivity of scenario-based project planning Business Drivers:

Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

ď›™2004 FIATECH

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Identify facility project risk factors (including impacts on Cost, Schedule and Quality), and the interdependencies between them. 4. Describe functional requirements for the next -generation SBPP capability. Examples include: a. Ability to collect information about project execution and perform realtime risk assessments based on new factors (e.g., terrorist threats, supplier failures, regulatory changes, geopolitical crises, and other factors outside the control of the project) b. Ability to provide appropriate alerts upon changes in the risk status and actions that threaten progress against the baseline plan. 5. Identify any complex interactions between multiple risk factors to deliver a unified risk assessment and recommendations for mitigation. 6. Identify and document the facility project risk factors, and a decision tree showing how the factors are evaluated in the planning process. 7. Update the functionality gap analysis spreadsheet to reflect the next -generation capabilities. 8. Document and publish the functional requirements regarding risk. Individuals: (people who want to work on this project) Organizations: (organizations working this topic already)

October 2004, Element 1, Page 25


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA4-P3 Functional Requirements for the User Interface Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries)

Urgency / Timeline (when)

2004 FIATECH

Functional Requirements for the User Interface Objective: Define the end-user functionality needed in terms of user interface, analysis and alerts, inputs and outputs. User interface: 1. Define the processes and user interface to support data entry to define project events and scope, select the applicable variables, and assign variable weights. 2. Define the processes and user interface to support configuration of a wide variety of inputs and outputs including Reports, Queries, Charts, Graphs, Imports and Exports. 3. Identify the interactions with SbPP data for which 3D and 4D models are appropriate interaction methods, and define the functionality need for such interactions. Analysis: 4. Define mechanisms to alert the SbPP team to changes in project decisions (design, sourcing, construction, business, operations, etc.) that impact project alternatives. Alerts: a. Identify case studies that illustrate: • the need alert the SbPP team to changes in decisions • the impact of not alerting the SbPP team to changes in decisions • the types of decisions to which the SbPP needs to receive updates • the speed and level of accuracy necessary to alert the SbPP team b. identify the data and modeling and simulation tools for each type of decision to support automated alerts to the SbPP team when changes in these decisions occur. c. specify the mechanisms and interfaces necessary to support such automated alerts. d. implement and test these mechanisms based on the specifications and test cases. Deliverables: a) User Interface specification b) Relevant process descriptions c) Prototype implementing the User Interface Purpose: Define a clear, easy-to-learn data entry process for SbPP. Business Drivers: Ensure that the SbPP data model and data set are populated and deployed consistently and efficiently regardless of the particular user. a) Modeling and simulation tools b) Asset Lifecycle Information System and SbPP data model c) Existing information sources d) Automated scheduling and requirements definition tool e) Other User Interfaces specified in E1-FA6 A first cut at this is urgent, since definition of an appropriate User Interface provides significant guidance and input into the design of the entire SbPP method and related processes, tools, and data

October 2004, Element 1, Page 26


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

Project Title Process / Activities (how)

Resources (who, where)

ď›™2004 FIATECH

Functional Requirements for the User Interface 1. Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Identify case studies that illustrate current User Interfaces and data needs for SbPP and support the specification of a desirable User Interface 4. Define criteria for a good User Interface based on the case studies and the related stakeholders and users of SbPP 5. Develop and test the User Interface Individuals: (people who want to work on this project) Organizations: (organizations working this topic already)

October 2004, Element 1, Page 27


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA4-P4 Functional Requirements for Modeling & Simulation Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why)

Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

ď›™2004 FIATECH

Functional Requirements for Modeling & Simulation Objective: Define functional requirements for modeling and simulation tools. Deliverables: a) Modeling and simulation requirements. b) Requirements for the design system, financial system, scheduling system. c) Requirements for external sources (regulatory agencies, subcontractors, sources of supplies. Purpose: Support accurate and complete planning and analysis of all important aspects of a capital project. Business Drivers: Maximize the use of fact-based and model-based methods for scenario development and project planning. a) Accuracy and timeliness of output required b) Available modeling and simulation tools and methods c) Asset Lifecycle Information System (ALIS) (Roadmap Element 9)

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Lis t important stakeholders and collect their requirements (needs) for information about a scenario so that they can make a decision on a proposed project plan 4. Establish the existing and desired modeling and simulation methods to generate the outputs described in activity 1 5. Define the inputs required to generate the outputs with the methods described in activity 2 6. Develop the requirements for modeling and simulation based on this stakeholder, input/output, and methods analysis Individuals: (people who want to work on this project) Organizations: (organizations working this topic already)

October 2004, Element 1, Page 28


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA4-P5 Define “Grouping” Functionality for Analysis and Output Project Title Objectives / Deliverables (what result)

Define “Grouping” Functionality for analysis and output Objective: Define data objects and relationships needed to support analysis and output, in the areas of cost estimating, cost tracking, cost forecasting, and storage of both estimated and actual costs. Groupings include operations and maintenance objects related to functional units, systems which perform a single function, objects covered by a single supplier strategy, etc. Example 1: It should be possible to group active pumps, hot-spare installed pumps, cold-spare pumps in the spare-parts warehouse, and common spare parts and maintenance materials for a group of pumps. Example 2: It should be possible to group all the equipment, steel, concrete, wiring, etc., associated with the air-conditioning system, so that you can test the costs of window units versus central air, across a single project, and across the lifecycle of the facility. Prioritization of project characteristics unique to the project. Deliverables:

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Purpose: Business Drivers:

Resources (who, where)

2004 FIATECH

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. Individuals: (people who want to work on this project) Organizations: (organizations working this topic already)

October 2004, Element 1, Page 29


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA4-P6 Functional Requirements for Automated Scheduling and Facility Project Definition Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

2004 FIATECH

Functional Requirements for Automated scheduling and facility project definition Objective: Define the functional requirements to support integration and automation of the facility project requirements definition process, including: • Project scope definition • Project risk components and evaluation • Detailed baseline schedule • Work breakdown structure • Early-stage material and labor cost estimates • Bill of materials (should this be included?) with links to the Asset Lifecycle Information System. Deliverables: a) Functional Requirements document b) Use case scenarios illustrating use of the functionality Purpose: Automate key steps in SbPP to the extent possible. Business Drivers: Reduce the time required to carry out SbPP and increase the consistency in applying SbPP methods across companies and the industry. a) Modeling and simulation tools b) Asset Lifecycle Information System c) Existing information sources d) Performance requirements for SbPP

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. identify case studies that illustrate the performance requirements of an automated scheduling and requirements definition tool; these case studies will also help validate and test the developed tool and support the training of professionals in using the tool 4. Design the functional requirements 5. Document and publish the functional requirements and use case scenarios Individuals: (people who want to work on this project) Organizations: (organizations working this topic already)

October 2004, Element 1, Page 30


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA4-P7 Define Interfaces with Other Tools Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

ď›™2004 FIATECH

Define Interfaces with other tools Objective: Definition of requirements for interfaces (including data exchange and validation) with other design, construction, and procurement software tools. Deliverables: Identification of shared data and data relationships between the SbPP functionality and all other facility creation/modification functionality. Purpose: Business Drivers:

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Integration Definition 4. Data Modeling 5. Define development coordination plans with the other automated tool efforts. Individuals: IT Database Implementation Skills, Process Modeling Skills, Process Subject Matter Experts, Consult: Project Decision Makers Organizations: (organizations working this topic already) TBD

October 2004, Element 1, Page 31


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA4-P8 Next-generation Product Specifications Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why)

Ties / Dependencies / Overlaps (constraints, boundaries)

Next -generation product specifications. Objective: In cooperation with the software vendors, to develop next -generation product specifications for decision modeling software to better address the needs of the capital projects industry and gain the endorsement of software vendors to develop products to meet the enhanced specifications. Deliverables: a) Workshop notes. b) Product specifications for decision modeling software. Purpose: To develop a decision modeling software specification that when fulfilled, enhances the usefulness and value for the capital projects industry. Business Drivers: To work collaboratively with software vendors to develop product specifications that will be of mutual value and benefit. a) Project #1 in this Focus Area (E1-FA4-P1) will make a recommendation regarding the need for and priority for this project. If the team from Project #1 recommends this project, they are to include specific recommendations for enhancements to existing decision modeling software. b) Cost and risk are significant factors in the decision making process. Therefore, the results of SbPP FA4 – Tools for cost-based evaluation of project alternatives and SbPP FA5 – Tools for risk-based evaluation of project alternatives may identify features and enhancements desired for the decision modeling products. c) SBPP project E1-FA4-P1: Interaction with Asset Lifecycle Information System project (Roadmap Element 9) includes storing relationships between project variables. The results from FA4 when combined with the results from Project #1 of this Focus Area may indicate enhancements to the data storage and retrieval for the decision modeling products.

Urgency / Timeline (when)

The need for this project depends on the results from Project #1 in this Focus Area. This project can commence once the recommendations from Project #1 are endorsed and this project is funded. This project is estimated to be completed within 6 months.

Process / Activities (how)

1.

Resources (who, where)

2004 FIATECH

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Conduct workshops to discuss the desired enhancements and to specify features for the next generation decision modeling products. 4. Prepare a product specification for decision modeling software. Individuals: (people who want to work on this project) Organizations: (organizations working this topic already)

October 2004, Element 1, Page 32


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA5: Data Model Requirements Projects: E1-FA5-P1 Data Modeling - Integration with Existing Data Sources Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Data Modeling - Integration with existing data sources Objective: Determine relevant public and private information sources; determine the role these information sources play in SbPP Deliverables: a) Criteria to determine relevance of information sources b) List of relevant private information sources c) List of relevant public information sources d) List of missing, but desired public or private information sources to support SbPP e) Description of role of public and private information sources in SbPP f) Definition of a process to keep information sources up to date Purpose: Maximize the use of existing and available information sources for SbPP. Business Drivers: Leverage existing information sources to improve costeffectiveness and timeliness of SbPP a) Information needed by modeling and simulation tools

1.

2. 3.

4. 5.

Resources (who, where)

ď›™2004 FIATECH

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). Staff and initiate the project. Study the modeling and simulation tools to determine necessary information sources and to determine the criteria to assess the relevance of a particular information source. Survey companies to identify information sources they use today and to understand how they maintain these information sources. Survey information providers to identify information sources they already have and information sources they plan to have, and to understand the process they use to keep the information up to date.

Individuals: (people who want to work on this project) TBD Organizations: (organizations working this topic already) TBD

October 2004, Element 1, Page 33


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA5-P2 Define the Data Model for SbPP Data in ALIS Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

ď›™2004 FIATECH

Define the Data Model for SbPP data in ALIS Objective: After refinement of the list of variables to be considered in scenario based project planning, work with ALI S data architecture team to design the SBPP portions of the data, including data and variables, relationships, rules, validation, internal and external data, versioning, time sensitive data, etc. Identify the information that is specific to project and plant, and segregate from the information that belongs in the Reference Data repository. Deliverables: Purpose: Business Drivers:

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Classification, matrix and hierarchical. Individuals: (people who want to work on this project) TBD Organizations: (organizations working this topic already) TBD

October 2004, Element 1, Page 34


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA5-P3 Define the SBPP Reference Data Model Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

ď›™2004 FIATECH

Define the SBPP Reference Data Model Objective: Defines the data model to support the project investment decision. Deliverables: a) Data Model (<= three layers) b) Process Model Purpose: Create the data model that supports the process of scenario based planning. Business Drivers: Understand all of the data required to perform scenario based project planning and the decisions it must support. a) Scenario based planning process b) Tools and techniques

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Decision Map 4. Data definition 5. Data Modeling Individuals: Data Modeling Skills, Process Modeling Skills, Process Subject Matter Experts, Consult: Tool Experts, Project Decision Makers Organizations: (organizations working this topic already) TBD

October 2004, Element 1, Page 35


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA5-P4 Create the Tools and Database Development Multi-Generation Plan Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries)

Create the Tools and Database Development Multi-Generation Plan Objective: Defines the time sequenced order software and database development activities. Deliverables: a) Data model build-out over time b) Capability build-out over time c) Interfaces coordinated with other parallel efforts. Purpose: Understand the priority order of building the tools. Business Drivers: Bring capability to the industry in multiple generations. a) Scenario based planning process b) Tools and techniques

Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

ď&#x203A;&#x2122;2004 FIATECH

1.

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Capability Prioritization 4. Data Model Layering 5. Time -phased Roadmapping Individuals: Data Modeling Skills, Process Subject Matter Experts, Pro ject Decision Makers Organizations: (organizations working this topic already) TBD

October 2004, Element 1, Page 36


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA6: Design & Develop Next Generation Tools and Database Projects: E1-FA6-P1 Write Software Application(s) and Create and Populate Database(s) Project Title Objectives / Deliverables (what result)

Write Software Application(s) and create and populate database(s) Objective: Using the software vendor relationships formed, and the functional specifications documented, in Focus Area FA3 “Functional Requirements”, and following the development Roadmap defined in FA5-4, develop the next -generation software tools. Deliverables:

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Purpose: Business Drivers:

Resources (who, where)

Individuals: IT Database Implementation Skills, Process Modeling Skills, Process Subject Matter Experts, Consult: Project Decision Makers Organizations: (organizations working this topic already)

2004 FIATECH

a) b) c) d) e) f) g)

Charter the team. Identify industry communication venues for communicating requirements. Do detailed system design and database schema design Develop the tools. Perform proof-of-concept. Outline implementation recommendations. Publish results, and prepare to support marketing rollouts by vendors.

October 2004, Element 1, Page 37


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA6-P2 Create and Populate the SbPP Reference Model Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries)

Create and populate the SbPP Reference Model Objective: Create the phase 1 data base to support the project investment decision and pilot in the field. Deliverables: a) Working data model b) Working process model Purpose: Create the data base that supports the process of scenario based planning and use it in a pilot. Business Drivers: Deliver phase 1 data capability a) Scenario based planning process b) Tools and techniques

Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

ď&#x203A;&#x2122;2004 FIATECH

1) Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2) Staff and initiate the project. 3) Pilot Scope 4) Project Development 5) Pilot / Proof of Concept Individuals: IT Database Implementation Skills, Process Modeling Skills, Process Subject Matter Experts, Consult: Project Decision Makers Organizations: (organizations working this topic already)TBD

October 2004, Element 1, Page 38


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA6-P3 Beta Test the SbPP Reference Model and ALIS Using the SbPP Application Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why)

Beta Test the SbPP Reference Model and ALIS Using the SbPP application Objective: To test the delivered functionality and databases in a controlled environment, and to obtain broader industry feedback on the design and delivery of the software and databases. Deliverables: a) Test environment accessible to broad set of industry participants b) Collection of Reference Data c) Planning data for a project, recorded in ALIS Purpose: Quality assurance, validation of functionality. Business Drivers:

Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

1.

Resources (who, where)

ď&#x203A;&#x2122;2004 FIATECH

Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2. Staff and initiate the project. 3. Create test platform 4. Conference room pilot to validate data and software design in Industry 1,2,3 5. Improve as indicated 6. Field test and pilot 7. Project Development in Industry 1, 2, 3 8. Pilot / Proof of Concept in Industry 1,2,3 Individuals: IT Database Implementation Skills, Process Modeling Skills, Process Subject Matter Experts, Consult: Project Decision Makers Organizations: TBD

October 2004, Element 1, Page 39


Capital Projects Technology Roadmap Element 1 Tactical Plan, Scenario-based Project Planning

E1-FA6-P4 Implementation Plan Project Title Objectives / Deliverables (what result)

Purpose / Business Driver(s) (why) Ties / Dependencies / Overlaps (constraints, boundaries) Urgency / Timeline (when) Process / Activities (how)

Resources (who, where)

ď&#x203A;&#x2122;2004 FIATECH

Implementation plan Objective: Develop and implement rollout plans, data migration plans, value proposition communications, marketing efforts, requests for early adopters, support and training processes, feedback processes, etc., in order to implement the SbPP software, reference data, and data model widely across the industry. Deliverables: See above Purpose: Implement the tools. Business Drivers: Realize the benefits of a highly interoperable scenario based project planning capability.

1) Define the necessary Roadmap project control plans, including charter, schedule and project plan, resourcing plan (in terms of skill sets and work hours), communication plan, financial plan, etc.). 2) Staff and initiate the project. 3) Work with software vendors to create demonstrations and marketing materials. 4) Work with industry and vendors to demonstrate implementation techniques. 5) Identify and support early adopters, and learn from their experiences. 6) Communicate the value proposition broadly. Individuals: (people who want to work on this project) TBD Organizations: (organizations working this topic already) TBD

October 2004, Element 1, Page 40

http://fiatech.org/images/stories/techroadmap/deliverables/oct2004/CPTR_E1_ScenarioPlanning_Download  

http://fiatech.org/images/stories/techroadmap/deliverables/oct2004/CPTR_E1_ScenarioPlanning_Download_Oct2004.pdf

Advertisement