Issuu on Google+

Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Scope Provides the forum for an industry-wide set of design automation features and specifications to be created that will be available for software vendors to use when developing improved design automation software.The team  will support industry knowledge management clearinghouse efforts to avoid duplication of effort. .. Enables industry stakeholders and software vendors to work collaboratively to develop improved design automation technology for the capital projects industry.

Working Team The team members listed here contributed to the revision of this document and are active in one or more implementation projects. . For a list of current working team members refer to the FIATECH web site.

Aveva, Derek Middlemas Bechtel, Shikrant Dixit and Darya Nabavian (Team Co-Champion) Bentley Systems, Inc., Gordon McPhee CommonPoint, Ted Blackmon CH2M HILL, Rob Brawn (Team Champion) Fluor, Dan Slade Hatch, Peter Blake and Daryl Ofstie State of Wisconsin, Bill Napier Software Innovation, Tony Vander Valk US Army EDRC, Johnnie Shockley

Other Contributors The team also recognizes these individuals for their past contribution during the original development of this document.

Gordon McPhee , Bentley  Systems Mike Albert , Bechtel Mike Alianza , Intel Jack DeBrunner , The Procter and Gamble Company Keith Denton , Intergraph

1 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Tamer El-Diraby , University of Toronto Randy Fix , Fluor Tom Hannigan , Zachry Construction Corporation Patrick Holcomb , Intergraph John McQuary , Fluor Mike Pye , Fluor Ian Smith , Bentley Systems Earl Tipton , Jacobs Engineering Ray Williams , KBR

Vision The Vision statement describes what is wanted in the future.

Current and emerging capabilities in 3-D design, analytical modeling and simulation, intelligent systems and distributed information management offer the opportunity to create a truly integrated and automated project design environment. In this environment, all tools will work together as an interconnected system that provides all of the functionality needed to develop and validate detailed designs for every aspect of a project based on the design criteria. This integrated design environment will dramatically reduce the time and cost in moving from concept to construction execution through automation of complex design engineering tasks. It will also greatly reduce errors and liability through comprehensive, automated design optimization and verification. Optimization would include a variety of options including total installed cost, total lifecycle cost, plant output and facilities.. The vision of the automated design system of the future is shown in Figure 1 below. The system will enable design teams to interact with the customer and other stakeholders to assist in the conceptual design process, starting with the capturing of requirements and preferences for design, while automatically processing options in a mathematically accurate, scenario-based visualization environment (see Element 1: Scenario-based Project Planning ). Modeling and simulation tools linked to the automated design system will enable quantitative evaluation to assess the cost, performance, and risks of each option.

2 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Figure 1. The capability processes. thatautomated is seamlessly design integrated system with will provide both upstream a complete, and downstream end-to-end design project

Current Problem

The Current Problem statement describes the existing situation.

Today’s capital project designs are largely produced using computer-aided tools for discrete elements of the facility. The overall “final design” is comprised of a variety of packages of diversely formatted data ready for handoff to the procurement and construction execution functions. Although many aspects of the project effort, including design, analysis, and systems engineering, are performed using electronic tools, the individual tools are not integrated and often do not work well together. This results in inefficiency. The transfer of information is time-consuming, costly, error-prone, and highly dependent on the skills and experience of the design team. Project requirements and design data and information are often lost as the design deliverables pass from the designer to other entities in the project’s lifecycle.

Design tools and technology have advanced significantly in the capital projects industry over

3 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

the past decade. However, there are still significant opportunities to advance the state of the industry by increasing integration and interoperability of existing applications and creating other applications to meet new needs. Software vendors currently spend much time and effort determining the requirements for future software enhancements and data conversion. Each vendor attempts to provide the software suite that will meet the needs of its customer base, or partners with other selected vendors to provide additional capabilities. This often results in wasteful overlapping competition among vendors in areas that are not their core competencies.

The customer base reviews and tests vendor offerings, sometimes multiple times within the same company. The customer base also spends a significant amount of time providing input to software vendors regarding current products and desired features of new products, and frequently feels that their concerns are not heard or understood and their needs are not met. Again, this often results in time-consuming wasteful efforts on the part of these customers, time which could better be spent in value producing efforts for their companies.

Potential Benefits & Opportunities The automated design system of the future will enable the designer to produce detailed designs using multiple design and data software in automated processes that ensures the design will be consistent with all preferences and requirements. Working with established industry-wide product definition and data standards will enable designers to specify supplier-furnished materials, components, and products that designers can directly upload into the design basis, complete with geometry and associated specifications and performance models. Other features and benefits of the system that will be of value to down-stream participants and stakeholders include automated review for code compliance, data and visualizations/simulations for the contractor, and supplier submittals and collection of equipment data that automatically updates the project model and database. The system architecture and standards will enable interoperability with other stakeholders and participants to capture and enable use of information, decisions, and maintenance and operating parameters throughout the life of the project.

Stakeholder Specific Benefit Owner/Operators Full assurance that designs are in direct response to requirements and optim Architects Improved efficiency in translating concepts to buildable designs; enhanced a Designers/Engineers Improved capability and efficiency through built-in analytical and validation t Constructors Delivered contract documents will provide a complete and totally optimized Material/Equipment/Technology Clear, complete Suppliersand unambiguous definition of all materials, parts, products Design software vendors Vendors need to understand the market benefits associated with developing

4 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Potential Barriers & Challenges With any implementation there is generally some resistance to change. The capital projects arena is no exception. Examples of barriers to change might include: - Lack of proven case studies – Companies are nervous to invest until there is proven return on investment. Limited case studies and proprietary data make it difficult to predict a return on investment. - Contractual methods and legal responsibility – Traditional contracting practices and liability are counter to collaborative processes and lifecycle perspectives. - Protection of Intellectual Property – Concerns regarding protection of intellectual property and absence of industry standards make it difficult to share information in a secure and confidential manner. - Lack of a bridge between CAPEX (Capital Expense) and OPEX  (Operating Expense) goals and objectives inside the owner/operator company - Lifecycle goals are often seen as contrary to project goals. As one high-ranking CAPEX manager recently stated, “we are totally committed to the ideas and benefits of lifecycle asset approaches right up to the point where they interfere with project cost or schedule.” If this thinking is not overcome, the discrete products and systems will continue to innovate and incrementally improve but the overall lifecycle goals are not likely to be achieved. - Powerful and autonomous capital project managers - These managers are measured on individual project results: schedule and budget. They are usually averse to anything they do not understand and see new approaches simply as added project risk. Past experiences indicate that they are rarely open to innovations related to the project cycle itself. Reluctance to make necessary alterations to business and work practices - Many companies have set up systems that are “working” and once deemed functional tend to leave them in that state. Due to tremendous changes in technology, companies are using the opportunity of migration to new technology as the junction point to revamp work processes. Ongoing work processes should be challenged to adopt technology just as technology should adapt to work processes. - Design contractors with legacy systems – Work cannot stop to implement new systems so smooth migration from existing systems is a must. Vendors must balance between satisfying their existing customers while charting a course for the next generation of applications. Development and adoption of industry standards that enable or simplify plug and play solutions may be perceived as opening the door to competition. Meanwhile too often new or improved software tools and utilities may get passed over because of competing internal developed applications. - Determining how to share the risk and reward for lifecycle approaches – If Engineering, Procurement and Construction companies (EPCs) are forced to use tools they are not familiar with they may charge premium prices to cover the unknowns even though there may be direct benefits to them. In other situations, EPCs may be able to provide useful content that could save the owner money but since there is no incentive to provide the information and there is potential liability, the opportunity is abandoned. Similar situations also occur between

5 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

planning and design with construction activities.  This may need revision to include facility projects and address other project delivery methods such as Design-Bid-Build, Design/Build, Construction Manager (all variants), and the upcoming collaborative "alliance" model (one contract with Owner for all participants) - Currently, software vendors spend a significant amount of time researching product needs, and their customers may feel as if they are played against the requests from other customers. On the other hand, customers may resort to back room arm-twisting to force vendors to create new features in subsequent product releases to meet specific project needs which may be counterproductive in the long run. Clear and consistent industry requirements will both motivate and enable vendors to focus on building products that include the required features rather than trying to address the desires of individual users associated with the capital projects industry who usually focus on a narrow market or element of the project lifecycle (e.g., design, construction, equipment, or operations).

Goals The Goal statement describes what is expected to be achieved.

To expedite advancement of automated design vision to improve cost-efficiency, enhance the lifecycle value of the design work products, and enable interoperability among entities associated with a project's lifecycle, resulting in significant cost savings and/or profit.

The goal is to accelerate the development and deployment of an integrated suite of design advisors, automated design tools and processes in the capital projects arena that increase cost efficiency and improve project performance. Key issues include integration of detailed design with the other vision diagram elements; design reuse; design requirements integration and management; automated design advisors; and industry-specific modeling and simulation tools. This functional element will address automated design and the role it plays within the total project lifecycle, and will capture and provide industry feedback for integration into the Asset Lifecycle Information System (see Element #9 - Lifecycle Data Management and Information Integration ) to support total management of project performance.

Strategy for Achieving the Goal

6 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

The strategy statement describes how we see the goal being achieved.

The strategy for achieving the goal is composed of two basic parts: - Provide design automation software vendors with an industry-wide set of design automation features and specifications that are updated annually and the market incentive to rapidly develop products that incorporate those features. - Use existing or emerging clearinghouses to serve as a knowledge management resource for design automation. Value is gained by reducing redundant investigation of products and approaches, and by reducing the time spent searching for information. Industry will also gain the value of obtaining feedback from a diverse group of reviewers. Automation design experts and industry-wide stakeholders will come together; representing all aspects of capital projects in a forum where the design automation features of the capital projects industry can be developed in collaboration with companies that are likely to provide the tools to fulfill the vision of an automated design system. By having significant representation of customers throughout the supply chain working collaboratively toward a common objective, we expect to provide the impetus and incentives for software vendors to develop a new generation of automation tools and processes that will result in a quantum leap in design productivity and lifecycle value. This strategy will include utliziation of a Web-based knowledge management system, which will serve as a central location for industry to access, review and comment on the latest vendor software and associated automation features. The automated design working group will manage design-related content on the Web site, compile and evaluate information gathered, and combine that with their cumulative experience to develop details for the automated design plan. The automated design working group will obtain review and feedback from industry stakeholders, including software vendors.

The intent is to provide a single and concise voice from the capital projects industry that will motivate and provide incentives to the software industry to accelerate investment and development of software and processes that will enable the design automation vision to be realized. As with any technology-based solutions, we will need to periodically update and advance the design automation plan to shape the future of the technology and to keep advancing the value to the entire capital projects industry. The working group will provide a concise and unified voice for the capital projects industry consistent with lifecycle objectives and promote the benefits associated with the development of automation tools that provide the desired features to their industry and to their software vendors. Estimates of the market value and depth of such tools combined with the anticipated life expectancy, so that each vendor can calculate their own benefits, may accelerate vendors' adoption of the industry’s vision.

7 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

The following steps establish and maintain the organizational foundation that is needed prior to implementing the strategy described above. 1. Establish and charter the automated design working group –The details necessary to accurately convey the needs of the industry are not yet sufficient for a vendor to implement. Formation of an industry-led working group will help guide this process, provide input, and identify existing gaps. 2. Create the automated design plan - The working group will compile and evaluate the information gathered from vendors and industry through the clearinghouse and infuse their expertise to expand and enhance this plan. The plan will expand upon the existing focus areas listed below as well as identify other focus areas that should be pursued. The working group will identify, specify, and validate common features and capabilities necessary to advance automated design within our industry to achieve the vision, to identify barriers to success and to develop approaches to reduce or remove those barriers. 3. Review and update the automated design plan - Technology and industry requirements will change over time. The working group will annually evaluate, update and advance the automated design plan for the Roadmap to provide increased value to the industry and clear up-to-date targets for our software vendors. The working group will compile the information and communicate the updates to the primary software vendors and the industry at large.

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.

Key components of delivering the vision of a totally automated and integrated design for capital projects are design advisors, knowledge bases, rule bases, integration, and enhanced viewing and collaboration. Some of these components are far-reaching and include the application of technology from other industries or the development of new technologies, while others involve the enhancement of current approaches.

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.

8 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Project details can be viewed by downloading the PDF. 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 Elements) ( constraints, boundaries ), Urgency / Time line ( 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.

E2-FA1: Metrics for proof of concept and demonstration of capabilities - The metrics developed for proof of concept will be used to validate the approach, focus areas and projects proposed in the tactical plan and to build support for quicker adoption of technology. The working group will organize meetings with software vendors and user groups from industry to gain their input for the automated design plan. The meeting with vendors will provide them the opportunity to have their primary system architects present for interaction and direct feedback from an industry body, and to address implementation issues. After vendor and user feedback is obtained, the working group will finalize the automated design plan and will make it available to industry.

Projects:

E2-FA1-P1 Charrettes E2-FA1-P2 Contractual Delivery Issues

E2-FA2: Design Viewing - The Design Viewing focus area encompasses all viewing technology associated with design review systems. It is intended to take advantage of the advances made in virtual reality, holographic projection, immersive 3-D walkthroughs, collaboration tools, and redlining.

9 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Project:

E2-FA2-P1 Virtual Design and Validation Environment

E2-FA3: Integrated and Interoperable Design Systems - This focus area centers on those efforts required to communicate specific features and standards of an integrated/interoperable design platform. Results of this focus area will facilitate real-time data integration, data exchange between design systems, and the exchange of information with other elements of the FIATECH Capital Projects Technology Roadmap. It will also address standards to improve the data exchange mechanisms for design information.

Projects:

E2-FA3-P1 Distributed Simulation Environment E2-FA3-P2 Collaborative Requirements Definition E2-FA3-P3 Automated Abstraction E2-FA3-P4 Data Management E2-FA3-P5 Extend Collaborative Environment to Include Suppliers & Fabricators E2-FA3-P6 Exchange of Information from Design to Construction

E2-FA4: Intelligent Design Systems - This focus area centers on the creation and definition of rule-based systems, reusable designs, design advisors, and knowledge bases.

Projects:

E2-FA4-P1 Design Conventions, Standards and Rules E2-FA4-P2 Regulatory Compliance E2-FA4-P3 Architecture for Design Advisors

10 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

E2-FA4-P4 Automated Detailed Design Systems E2-FA4-P5 Automated Change Management E2-FA4-P6 Design/Reuse Capability E2-FA4-P7 Intelligent Capital Projects Design Models

E2-FA5: Create and maintain a design automation information clearinghouse - Under current practice, companies periodically conduct software reviews (sometimes at multiple locations within the same company). The working group will encourage these companies to share their findings, which will be included in the information clearinghouse. Similarly, since software vendors send out large quantities of marketing information, they will be encouraged to provide their relevant information for inclusion in the clearinghouse as well. Through this clearinghouse, industry will be able to easily access, review and evaluate vendor information as it relates to the overall design automation plan. Industry will also be encouraged to submit desired features to support the vision through the automation information clearinghouse.

Project:

E2-FA5-P1 Create and Maintain a Design Automation Information Clearinghouse

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). Preparation includes identifying funding, resourcing and project 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). Yr 1 Yr 2 Yr 3 Yr 4 Y4 5 Yr 6 Yr 7 E2-FA1: Metrics for proof of concept and demonstration of capabilities E2-FA1-P1Charrettes Q2-Q4

11 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

E2-FA1-P2 Contractual Delivery IssuesQ2-Q4 E2-FA2: Design Viewing E2-FA2-P1 Virtual Design and Validation Q4 Environment

Q1-Q4

E2-FA3: Integrated/Interoperable Design Systems E2-FA3-P1 Capital projects distributed simulation Q4 environment

Q1-Q4

E2-FA3-P2

Collaborative design environment Q2-Q4

Q1-Q4

E2-FA3-P3

Automated abstraction

E2-FA3-P4

Data management

E2-FA3-P5

Extended collaborative environment Q1-Q4

Q1

E2-FA3-P6

Handoff from design to construction Q2-Q4

Q1-Q4

Q3-Q4 Q2-Q4

Q1-Q4 Q1-Q4

E2-FA4: Intelligent Design Systems E2-FA4-P1 Design conventions, standards Q1-Q4 and rules E2-FA4-P2 Regulatory compliance Q2-Q4 E2-FA4-P3

Architecture for design advisors Q1-Q4

E2-FA4-P4

Automated detailed designQ1-Q4 systemsn

Q1-Q4 Q1-Q2

Q1

12 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

E2-FA4-P5 E2-FA4-P6

Automated change management Q3-Q4 Design/Reuse capability Q4

E2-FA4-P7

Integrity assessment based on design Q2-Q4

Q1-Q2

E2-FA4-P8

Intelligent capital projects designQ4 models

Q1-Q4

Q1-Q4

E2-FA5: Create and maintain a design automation information clearinghouse E2-FA5-P1 Create and maintain a design Populate automation and maintain information Populate clearinghouse and maintain

Case Studies To be developed.

Organizations Working in Focus Areas To be developed.

Existing Relevant Research Activities and Results To be developed.

Funding Sources To be developed.

Project Descriptions by Focus Area

13 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

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. Charrettes Project

Title

Charrettes

Objective / Deliverables (what result )

Objective: Deliverables: a) Promotional material

Purpose (why)

Sponsor charrettes

(modeled after B

/ Business Driver(s)

14 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Purpose: Business Drivers:

Speed development and deploymen Create incentives for software vendo

Ties / Dependencies / Overlaps (constraints, boundaries)

a) Compatibility with overall roadmap objectives b) Constraints with funding and sponsors

Urgency (when)

/ Timeline

Medium/Short

Process (how)

term

/ Activities

1) Identify focus areas 2) Seek sponsors 3) Develop instructions/guidelines 4) Review entries and make awards 5) Promote results

Resources (who)

15 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Individuals: Organizations:

FIATECH members, academia Universities, software vendors, indu

E2-FA1-P2 Contractual Delivery Issues Project

Title

Contractual Delivery Issues

Objective / Deliverables (what result )

Objective: Deliverables: a) Example contract terms and approaches b) Whitepaper outlining solutions

Purpose (why)

Identify

contractual issues that create

/ Business Driver(s)

Purpose: Business Drivers:

Address contract terms to improve v Contract terms and legal responsibi

Ties / Dependencies / Overlaps (constraints, boundaries)

a)

Legal constraints and sharing or responsibility/risk/reward

16 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

b)

Historical behavior

Urgency (when)

/ Timeline

High/short

Process (how)

term

/ Activities

1) Assemble team of industry representatives (owner, EPC, trades) 2) Brainstorm barriers and possible solutions 4) Submit solutions for broader review 5) Incorporate feedback 6) Publish results 7) Repeat process and work with other trades

Resources (who)

Individuals: Organizations: Estimated cost:

Representative of organizations belo Trades, EPCs, Owners $20K

E2-FA2: Design Viewing Projects: E2-FA2-P1 Virtual Design and Validation Environment

17 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Project

Title

Virtual Design and

Validation Environment

Objective / Deliverables (what result )

Objective: An  environment that allows users to in Deliverables: Detailed definition of desired viewing and validation capabilities (then software vendors provide prod

Purpose (why)

/ Business Driver(s)

Purpose: Business Drivers:

Enhanced communication and more Today, there are many disparate sy

Ties / Dependencies / Overlaps (constraints, boundaries)

a) Ties to design advisors and code conformance. b) Depends on design tools, simulation environment and technical framework for

Urgency

data exchange

/ Timeline

18 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

(when)

High/Medium

Process (how)

/ Activities

1) Assemble working group 2) Define and detail desired capabilities 3) Publish requirements 4) Create incentives for vendors 5) Review new products as they come to market 6) Enhance and update requirements

Resources (who)

Individuals: Organizations: Estimated cost:

FIATECH members, academia Software vendors, hardware vendor $40K

E2-FA3: Integrated and Interoperable Design Systems Projects: E2-FA3-P1: Distributed Simulation Environment Project

Title

19 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Distributed simulation

Environment

Objective / Deliverables (what result )

Objective: Deliverables: a) Exchange vehicle for front end and process data

Purpose (why)

Create an

Environment where it is po

/ Business Driver(s)

Purpose: Business Drivers:

Improved efficiency of work process Inefficiency of current work processes

Ties / Dependencies / Overlaps (constraints, boundaries)

a) 4.1 design conventions and standards b) 3.2 collaborative design environment c) 3.6 extend collaborative environment

Urgency (when)

Low/Long

/ Timeline

term

20 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Process (how)

/ Activities

1) Assemble working group 2) Define and detail desired capabilities 3) Publish requirements 4) Create incentives for vendors 5) Review new products as they come to market 6) Enhance and update requirements

Resources (who)

Individuals: Organizations:

FIATECH members, academia Software vendors, hardware vendor

E2-FA3-P2: Collaborative Requirements Definition Project

Title

Collaborative Requirements

Definition

Objective / Deliverables (what result )

Objective: Deliverables:

Define the types

of interaction, inform

21 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

a) b)

White paper defining requirements Identify current best practices for work-sharing in a global environment, and

Purpose (why)

define future requirem

/ Business Driver(s)

Purpose: Business Drivers: Improved work sharing in a global environment.

Deliverable to software providers for Design execution cost reduction thro

Ties / Dependencies / Overlaps (constraints, boundaries)

a) Ties with Element 1, Element 3, and Element 9 specific projects TBD. b) Providing incentive to software suppliers at the completion of this effort to incorporate requiremen c) Alignment in the industry around terms and definition associated with collaboration.

Urgency (when)

/ Timeline

Medium/Medium

Process (how)

1)

to long term

/ Activities

RFQ to consultant companies to define cost

22 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

2) 3) 4) 5)

Seek funding Identify team Execute study Follow-up with FIATECH membership and software suppliers

Resources (who)

Individuals: Organizations:

FIATECH members Owners, EPCs, Software suppliers,

E2-FA3-P3: Automated Abstraction Project

Title

Automated Abstraction

Objective / Deliverables (what result )

Objective: Create Deliverables: a) Specifications of required subsets and work process descriptions

Purpose (why)

capability to extract sub sets

/ Business Driver(s)

23 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Purpose: Business Drivers:

Improved Improved

flexibility in design with im efficiency in design.

Ties / Dependencies / Overlaps (constraints, boundaries)

a) 4.1 design conventions and standards b) 3.2 collaborative design environment c) 3.4 Data Management

Urgency (when)

/ Timeline

Low/Long

Process (how)

term

/ Activities

1) Assemble working group 2) Define and detail desired capabilities 3) Publish requirements 4) Create incentives for vendors 5) Review new products as they come to market 6) Enhance and update requirements

Resources (who)

24 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Individuals: Organizations:

FIATECH members, academia Software vendors, hardware vendor

E2-FA3-P4: Data Management Project

Title

Data Management

Objective / Deliverables (what result )

Objective: a) Specifications of such a system

Purpose (why)

To define a

systematic way to identif

/ Business Driver(s)

Purpose: Business Drivers:

Improved flexibility in EPCOM with i Improved efficiency in work processe

Ties / Dependencies / Overlaps (constraints, boundaries)

a)

4.1 design conventions and standards

25 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

b)

3.2 collaborative design environment

Urgency (when)

/ Timeline

Medium/Medium

Process (how)

/ Activities

1) 1) Assemble working group 2) Define and detail desired capabilities 3) Publish requirements 4) Create incentives for vendors 5) Review new products as they come to market 6) Enhance and update requirements

Resources (who)

Individuals: Organizations:

FIATECH members, academia Software vendors, hardware vendor

E2-FA3-P5: Extend Collaborative Environment to Include Suppliers & Fabricators Project

Title

26 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Extend Collaborative

Environment to Include Suppliers & Fabricators

Objective / Deliverables (what result )

Objective: Work with the trade associations and Deliverables: a) Detailed description of project(s) for team to focus on and the metrics or measurable goals to be o

Purpose (why)

/ Business Driver(s)

Purpose: Business Drivers:

Ensure inclusion of all appropriate s Provide a focused project to coalesc

Ties / Dependencies / Overlaps (constraints, boundaries)

a) Work on FA3-5 must have progressed to some “tipping point� where there is a minimum level of c b) A critical mass of vendors must have bought-in to the initiative. c) Owners need to supply prototype project(s) that are sufficiently compelling to suppliers to provide Element 8 FA1-P5

Urgency (when)

/ Timeline

27 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Medium/Medium

Process (how)

.

/ Activities

That team would comprise the appropriate stakeholders, and would know what

initial “functionality�

Resources (who)

Individuals: Organizations:

FIATECH members, academia, repr Universities, software vendors, associ

Exchange of Information from Design to Construction Project

Title

Exchange of Information from

Design to Construction

Objective / Deliverables (what result )

Objective: Identify and address barriers to auto Deliverables: a) Detailed listing by the construction industry of the requirements, needs, and preferences of the de b) Detailed description of the challenges and/or barriers to providing the above in an integrated and

28 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Purpose (why)

/ Business Driver(s)

Purpose: Business Drivers:

Enhance the timeliness, quality, con Enable better and quicker execution

Ties / Dependencies / Overlaps (constraints, boundaries)

 

Urgency (when)

High/Long

Process (how)

/ Timeline

term – appears to lie on the critical path for successful

integrated/interoperable design sys

/ Activities

1) Assemble team of industry representatives [academic, associations, owners, engineers, construct 2) Identify work already done to support this goal and by whom. 3) Develop a consensus on minimum requirements for “deliverables” by an engineering/design com 4) Provide results to team comprising FA 3-P5.

29 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Resources (who)

Individuals: Organizations: Estimated Cost:

FIATECH members who comprise t Major EPC firms, Universities, softw $25K

Intelligent Design Systems Projects: E2-FA4-P1: Standards for Sharing Design Conventions and Rules Project

Title

Standards for Sharing Design

Conventions and Rules

Objective / Deliverables (what result )

Objective: Create standards and best practices Deliverables: a) Definition of best practices b) Basic rules for design systems developed in a common language which can easily be customized c) Definition of standards necessary to build rule base

Purpose (why)

/ Business Driver(s)

30 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Purpose: Business Drivers:

Facilitate development and deploym There is a need for advanced rule b

Ties / Dependencies / Overlaps (constraints, boundaries)

a)

Element 9

Urgency (when)

/ Timeline

High/Medium

Process (how)

/ Activities

1) Assemble working group 2) Define requirements for rule base for Element 9 3) Assess and document best practices 4) Develop and document core rules 5) Distribute best practices and basic rules

Resources (who)

Individuals:

FIATECH

members, academia

31 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Organizations:

Software

vendors, Universities, EPC

Regulatory Compliance Project

Title

Regulatory Compliance

Objective / Deliverables (what result )

Objective: Deliverables: a) Definition of system requirements b) Examples of regulatory requirements

Purpose (why)

Define

requirements for intelligent de

/ Business Driver(s)

Purpose: Business Drivers:

Provide clear definitions of requeste There are often multiple sets of regu

Ties / Dependencies / Overlaps (constraints, boundaries)

a)

Ties to Element 9

32 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Urgency (when)

Low

/ Timeline

/ Long term

Process (how)

/ Activities

1) Assemble working group 2) Assess and define requirements for regulatory compliance 3) Distribute findings

Resources (who)

Individuals: Organizations:

FIATECH members, academia ICC, Software vendors, Universities

E2-FA4-P3 System Architecture for Design Advisors Project

Title

System

Architecture for Design Advisors

33 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Objective / Deliverables (what result )

Objective: Deliverables:

Purpose (why)

Define a common framework for the White paper defining standard appro

/ Business Driver(s)

Purpose: Business Drivers:

Simplify effort needed to incorporate Improved quality and consistency in

Ties / Dependencies / Overlaps (constraints, boundaries)

a) Ties with Element 8, Element 9 specific projects TBD; FA3-P2, FA3-P4, FA4-P4, FA4-P6. b) Providing incentive to software suppliers at the completion of this effort to incorporate requiremen

Urgency (when)

/ Timeline

Medium/Long

Process (how)

term

/ Activities

34 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

1) Assemble team of industry representatives from detail design engineering 2) Develop functional requirements and preferred behaviours 3) Execute study 4) Follow-up with FIATECH membership and software suppliers

firms and software vend

Resources (who)

Individuals: Organizations:

FIATECH members  EPCs, Software suppliers, and unive

E2-FA4-P4 Automated Detailed Design Systems Project

Title

Automated Detail Design

Systems

Objective / Deliverables (what result )

Objective: Deliverables:

Purpose (why)

Define how automated systems will White paper defining standards and

/ Business Driver(s)

35 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Purpose: Business Drivers:

Lower cost of detail design, improve Lowered cost for detail design in hig

Ties / Dependencies / Overlaps (constraints, boundaries)

a) Ties with Element 3, Element 8, Element 9 specific projects TBD; FA3-P2, FA3-P4, FA3-P6, FA3-P8 b) Providing incentive to software suppliers at the completion of this effort to incorporate requiremen

Urgency (when)

/ Timeline

High/Short

Process (how)

term

/ Activities

1) Identify team 2) Execute study 3) Follow-up with FIATECH membership and software suppliers

Resources (who)

Individuals Organizations:

: FIATECH members EPCs, Software suppliers

36 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

E2-FA4-P5 Automated Change Management Project

Title

Automated Change Management

Objective / Deliverables (what result )

Objective: Deliverables:

Purpose (why)

Identify and address approaches to White paper defining standards and

/ Business Driver(s)

Purpose: Business Drivers:

Improve upon gaps that exist within Improve ability of EPCs to meet sch

Ties / Dependencies / Overlaps (constraints, boundaries)

a) Ties with Element 3, Element 4, Element 9 specific projects TBD; FA3-P2, FA3-P4, FA3-P6, FA3-P8 b) Legal/regulatory community involvement around contract and scope definition.

37 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Urgency (when)

/ Timeline

Medium/Long

Process (how)

term

/ Activities

1) Identify team 2) Execute study 3) Follow-up with FIATECH membership and software suppliers

Resources (who)

Individuals: Organizations:

FIATECH members Owners, EPCs, Software supplier’s,

E2-FA4-P6: Design/Reuse Capability Project

Title

Design/Reuse Capability

Objective / Deliverables (what result )

38 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Objective: Deliverables: a) White paper defining functional requirements b) Proto-types of systems

Purpose (why)

Define

methodology and functional r

/ Business Driver(s)

Purpose: Business Drivers:

Deliverable to software providers for Design execution cost reduction thro

Ties / Dependencies / Overlaps (constraints, boundaries)

a) Ties with Element 1, Element 9 specific projects TBD. b) Providing incentive to software suppliers at the completion of this effort to incorporate requiremen c) Alignment in the industry around terms and definition associated with design reuse.

Urgency (when)

/ Timeline

Medium/Long

Process (how)

term

/ Activities

39 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

1) Form team 2) Develop functional description of system requirements 3) Solicit Universities for participation or use concept to design competitions 4) Seek funding 5) Develop proto-types 6) Document the results 7) Follow-up with FIATECH membership and software suppliers 8) Provide incentives to the software vendors to further develop the proto-type

for inclusion in existin

Resources (who)

Individuals: Organizations:

FIATECH members Owners, EPCs, Software supplier’s,

E2-FA4-P7 Intelligent Capital Projects Design Models Project

Intelligent

Title

Capital Projects Design Models

Objective / Deliverables (what result )

Objective: Deliverables:

Define the requirements of the incor White paper defining standards and

40 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Purpose (why)

/ Business Driver(s)

Purpose: Business Drivers:

Improved ability to accurately estima Improved use of project capital, redu

Ties / Dependencies / Overlaps (constraints, boundaries)

a) Ties with Element 1, Element 5, Element 9 specific projects TBD; FA3-P3, b) Providing incentive to software suppliers at the completion of this effort to

Urgency (when)

/ Timeline

Low/Long

Process (how)

FA3-P4, FA4-P4, FA4incorporate requiremen

term

/ Activities

1) Identify team 2) Execute study 3) Follow-up with FIATECH

membership and software suppliers

Resources (who)

41 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Individuals: Organizations:

FIATECH members Owners, EPCs, Software suppliers

E2-FA5: Create and Maintain a Design Automation Information Clearinghouse Projects: Populate a Design Automation Information Clearinghouse Project

Title

Populate a design

automation information clearinghouse

Objective / Deliverables (what result )

Objective: Deliverables:

Purpose (why)

Share  design automation information A populated  clearinghouse providing

/ Business Driver(s)

Purpose: Business Drivers:

Available and current design automa Reduce time spent searching for de

42 / 43


Element 2: Automated Design

Last Updated Tuesday, 28 July 2009 12:24

Ties / Dependencies / Overlaps (constraints, boundaries)

a)

Element 9 or possibly buildingSMART Alliance

Urgency (when)

provides the technical framework for the clearingho

/ Timeline

 

Process (how)

/ Activities

1) Prepare a specification of features and functionality desired for the design automation information 2) Develop a knowledge management approach to create a common template, populate and mainta 3) Prepare guidelines for evaluating information and vendor materials proposed for posting. The gui 4) Establish a research network tied to educational institutes, government branches, and private not 5) Identify potential funding sources for the creation and ongoing maintenance of the design automa 6) Create the clearinghouse, populate it and operate/maintain it.

Resources (who)

Individuals: Organizations:

(people who want to work on this proje buildingSMART Alliance and

43 / 43


http://fiatech.org/design