The document summarizes a value engineering workshop held in November 2007 to examine the power and cooling system requirements and design solutions for the International Linear Collider (ILC) Main Linac. The workshop was facilitated by the US Army Corps of Engineers and included participants from various ILC collaborating institutions. The workshop followed the standard value engineering process, beginning with information gathering and functional analysis of the current design. Participants then engaged in speculation, evaluation and development of alternative solutions over the course of the three-day workshop before presenting recommendations. The document reviews the value engineering methodology and explains how applying it systematically can help optimize resources and reduce costs while maintaining performance for large projects like the ILC.
Many doubt it to be so, but Agile Development and supporting Agile software DOES have a place among Government Agencies. Tune in to see the successes and failures as the FBI attempted to utilize Agile Development practices
The document discusses applying agile principles to business intelligence (BI) projects. It provides an overview of agile BI and a maturity model for assessing teams on their ability to collaborate, manage technical architecture, and follow engineering practices that enable agility. The document recommends teams evaluate their current state in these areas and select an agile methodology to begin implementing agile BI practices through a kickoff and continuous inspection and adaptation process.
by Brad Appleton,
Presented August 2006 at Architecture & Design World 2006; Chicago, IL USA
Software Configuration Management Patterns for Agile Software Architectures.
Doing Architecture with Agile Teams IASA UK Summit 2013Chris F Carroll
This document discusses how software architecture can work with agile teams. It addresses methodological questions around how agile scales for enterprises, where architecture fits in the agile lifecycle, and how to address governance, risk, adoption and maturity concerns. Personal questions are discussed around how architects can effectively work with agile teams and add value. Technical questions cover defining agility as a quality attribute and what an agile architecture might look like. The document provides perspectives on these issues from experts in agile and architecture.
Right-sized Architecture: Integrity for Emerging DesignsTechWell
In agile projects, design ideally "emerges" over the course of development. However, if teams primarily focus on independent user stories, they risk losing sight of the product's vision and the integrity of well-thought-out architecture. Ken Kubo shares techniques he's used to improve the chances that a product's design will emerge into a cohesive and coherent architecture that serves its customers for many years. Join Ken to find out how you can incorporate contextual design principles and simple, visual techniques as part of his "A-Little-Before-Its-Time Design" framework. You can add these practices into your agile workflow to maintain a shared team understanding of your product's vision and the system's emerging design. Ken believes that you can only realize all the promises of agile development with a clearly and constantly communicated product vision and a set of architecture goals. Lack of these key principles leads to sub-optimizing system development-or much worse, failure.
WANTED: Seeking Single Agile Knowledge Development Tool-setBrad Appleton
by Brad Appleton,
Presented August 2009 at at Agile 2009 Conference; Chicago, IL USA
What tools and capabilities are necessary to apply Agile development concepts+practices (such as refactoring, TDD, CI, etc.) to all knowledge-artifacts? (not just source-code).
This was some thoughts for maturing our Agile SDLC with some specific notes on how to improve JIRA workflows. This was a discussion slide deck; it's very wordy
The document discusses several complex engineering project case studies and failures. It analyzes the root causes of failures including flawed assumptions, incomplete information, technological changes, and improper management of complex interactions within large systems. Traditional project management approaches are shown to be insufficient for complex projects with unknown unknowns. Systems thinking and considering projects as complex adaptive systems is presented as a better framework for managing complexity.
Many doubt it to be so, but Agile Development and supporting Agile software DOES have a place among Government Agencies. Tune in to see the successes and failures as the FBI attempted to utilize Agile Development practices
The document discusses applying agile principles to business intelligence (BI) projects. It provides an overview of agile BI and a maturity model for assessing teams on their ability to collaborate, manage technical architecture, and follow engineering practices that enable agility. The document recommends teams evaluate their current state in these areas and select an agile methodology to begin implementing agile BI practices through a kickoff and continuous inspection and adaptation process.
by Brad Appleton,
Presented August 2006 at Architecture & Design World 2006; Chicago, IL USA
Software Configuration Management Patterns for Agile Software Architectures.
Doing Architecture with Agile Teams IASA UK Summit 2013Chris F Carroll
This document discusses how software architecture can work with agile teams. It addresses methodological questions around how agile scales for enterprises, where architecture fits in the agile lifecycle, and how to address governance, risk, adoption and maturity concerns. Personal questions are discussed around how architects can effectively work with agile teams and add value. Technical questions cover defining agility as a quality attribute and what an agile architecture might look like. The document provides perspectives on these issues from experts in agile and architecture.
Right-sized Architecture: Integrity for Emerging DesignsTechWell
In agile projects, design ideally "emerges" over the course of development. However, if teams primarily focus on independent user stories, they risk losing sight of the product's vision and the integrity of well-thought-out architecture. Ken Kubo shares techniques he's used to improve the chances that a product's design will emerge into a cohesive and coherent architecture that serves its customers for many years. Join Ken to find out how you can incorporate contextual design principles and simple, visual techniques as part of his "A-Little-Before-Its-Time Design" framework. You can add these practices into your agile workflow to maintain a shared team understanding of your product's vision and the system's emerging design. Ken believes that you can only realize all the promises of agile development with a clearly and constantly communicated product vision and a set of architecture goals. Lack of these key principles leads to sub-optimizing system development-or much worse, failure.
WANTED: Seeking Single Agile Knowledge Development Tool-setBrad Appleton
by Brad Appleton,
Presented August 2009 at at Agile 2009 Conference; Chicago, IL USA
What tools and capabilities are necessary to apply Agile development concepts+practices (such as refactoring, TDD, CI, etc.) to all knowledge-artifacts? (not just source-code).
This was some thoughts for maturing our Agile SDLC with some specific notes on how to improve JIRA workflows. This was a discussion slide deck; it's very wordy
The document discusses several complex engineering project case studies and failures. It analyzes the root causes of failures including flawed assumptions, incomplete information, technological changes, and improper management of complex interactions within large systems. Traditional project management approaches are shown to be insufficient for complex projects with unknown unknowns. Systems thinking and considering projects as complex adaptive systems is presented as a better framework for managing complexity.
The document provides an overview of a workshop on Business Value Engineering. It discusses:
1) Business Value Engineering as an approach to continuously improve how teams deliver value to customers by looking at processes end-to-end and incrementally improving.
2) Attribution to thinkers like Peter Drucker, Taiichi Ohno, and others who have influenced the approach.
3) The workshop agenda covers defining business value, developing business value models, identifying metrics, and examining elements and theories of business value engineering.
The document provides definitions and context around business value engineering. It discusses business value engineering as a learning and incremental improvement approach focused on delivering more value to customers. The document then summarizes different approaches to business value engineering, comparing the more traditional Procter & Gamble approach of extensive customer research and marketing to the experimental approach used by Google of quickly prototyping and testing ideas.
This document summarizes a presentation given on the new CDM 2015 regulations in the UK. It outlines 10 key points speakers discussed: 1) Safety in the construction industry has improved significantly since 2007 but it remains dangerous; 2) The Principal Designer role mirrors the previous Principal Contractor role; 3) CDM regulations work alongside other health and safety laws; 4) Laws set a minimum standard and professionals should aim higher; 5) Client duties are significant; 6) Projects require integration and teamwork with the client's needs prioritized; 7) Health issues need repeated review; 8) Professionals must be competent and properly manage projects; 9) Training is available to demonstrate competence; 10) Registering demonstrates meeting defined health and
1: Value Analysis provides great turnaround in the operations of the businesses.
2: Use Value Analysis to analyze and understand the detail of cost for specific situations.
3: Use it to find a focus on key areas for innovation.
4: Use it in reverse (called Value Engineering) to identify specific solutions to detail problems.
Value analysis and value engineering (VAVE) is a systematic process to analyze products and services to reduce costs while maintaining or improving performance. It originated from General Electric during World War II and focuses on analyzing a product's functions. The value of a product is defined as its functionality divided by its cost. VAVE can be applied across industries to solve problems, expand markets, and reduce costs as part of a long-term business strategy. To learn VAVE, one should receive training, use analysis tools, and practice with experienced practitioners to generate ideas for cost savings and value improvements.
The document summarizes a case study of a value engineering project carried out at an Indian Railways electric locomotive shed to address the problem of gear in two halves (GITH) failures. The project identified issues with the design basis, pinion weight, and oil pump gear shaft as causing impact loading and GITH breakages. Solutions proposed changing the design basis to make the GITH the driving gear, reducing the pinion face width and weight using Teflon, and changing to an external threaded oil pump gear shaft with a castle nut to eliminate play. The project aimed to reduce locomotive downtime and maintenance costs by redesigning faulty components with standardized specifications.
This presentation is about Value Engineering and contains:
1.History of VE
2.Value Concept
3.What is Value Engineering?
4.Implementation of VE in our project
5.Principle and Purpose of VE
6.Case Study
7.Conclusion
This document provides an overview of value analysis. It defines value analysis as a systematic process that compares the function of a product required by customers against the lowest cost of meeting specified performance and reliability. The key steps of value analysis are to establish objectives, analyze the production process, decompose product characteristics, brainstorm alternatives, select the best alternative, and implement changes. Value analysis aims to provide better value to customers and improve competitive position by eliminating unnecessary costs.
Benchmark Electronics A team (EU headquarters in Almelo, The Netherlands) developped a CREATIVE WORKSHOP of 2-3 days. Electronic product development. Results: cost reduction, innovation, new invented products in just a few days. Look at the presentation! Call Bert Blom +31611024589 or Mail: bert.blom@bench.com
Cost Reduction of a product through Value Analysis & Value EngineeringQuEST Global
This document summarizes a value analysis and value engineering approach used by QuEST to reduce product costs for customers. It describes how VAVE systematically analyzes product functions to identify potential cost savings opportunities without compromising quality or performance. The approach involves understanding requirements, analyzing functions, generating alternative ideas, evaluating options, and developing value alternatives. An example project demonstrates how QuEST applied this process to reduce material costs for an industrial control product by over 25% while improving performance.
The document provides an overview of value engineering, including its definition, purpose, and methodology. It defines value engineering as a systematic process that focuses on improving functions at the lowest cost while maintaining quality. The methodology involves 6 steps: information gathering, functional analysis, creativity, evaluation, development, and reporting. It also provides an example case study comparing the use of middle barrettes versus concrete bored piles for constructing a general cargo berth project at a port. Using piles was found to potentially reduce costs without compromising quality or functionality.
Project Management For Good Procurement Practicestjcornish
The document discusses project management best practices for procurement. It covers understanding procurement in light of project management, developing user requirement specifications, vendor management, and quality-based selection of vendors. Key topics include the difference between direct and indirect procurement, engineering economics concepts, requirements gathering techniques, contract types, solicitation planning, vendor selection methods, and quality-based selection of consulting engineers.
Value analysis and value engineering are techniques used to identify unnecessary costs in products, processes, and services. Value analysis is traditionally used after development to analyze existing offerings, while value engineering is used during design and development stages. Both use a team approach and function analysis methodology to reliably deliver necessary functions at the lowest total cost over the lifecycle in order to maximize value for the customer. Larry Miles is considered the founder of these techniques which he developed at GE in the 1940s and which have since been widely adopted.
This document provides an overview of the RSMeans publication titled "Value Engineering in the Construction Industry". It includes a table of contents that outlines the various chapters in the book, which cover topics such as project budgeting, cost modeling, function analysis, life cycle costing, and case studies applying value engineering techniques. The document also provides brief descriptions of the content included in each chapter. It indicates that the book presents advances in value engineering since previous editions and includes an updated disk with additional value engineering tools and automated formats.
Value engineering is a technique used to improve projects, processes, products, or services by determining the best functional balance between cost, reliability, and performance. It aims to identify unnecessary costs that can be eliminated without compromising quality, performance, or customer satisfaction. A value engineering study is conducted systematically using an eight-step job plan involving information gathering, functional analysis, creative idea generation, evaluation, and implementation. The goal is to deliver necessary functions at the lowest cost through improvements to design, materials selection, production processes, maintenance, and other factors.
This document provides an overview of value engineering and value analysis. It begins with the course outcomes and introduces value engineering and value analysis, distinguishing between the two. It then covers the history, definitions, types of value, functions, the value engineering/analysis cycle and job plan, application, reasons for poor value, and the steps in value engineering/analysis. Key points addressed include the objective to achieve equivalent or better performance at lower cost while maintaining requirements.
This document discusses key concepts in systems development including the systems development lifecycle, strategic planning, architecture, methodologies, and project management. It provides an overview of traditional waterfall and alternative approaches like prototyping and rapid application development. It also covers risk assessment, end user development, and the tension between IT organizations and end users.
Managing complex projects requires an approach that embraces uncertainty. Traditional project management methods focused on planning and certainty are ill-suited for knowledge work which involves evolving requirements and technologies. Effective approaches gather consensus, prioritize based on business value and risk reduction, use short build and feedback cycles, provide results-oriented reporting, and respect and empower team members. Historical examples that successfully managed uncertainty, such as the Manhattan Project and Polaris missile project, demonstrate these principles.
Project management through the eye of the systems engineerevolve2013
1. Systems engineering (SE) takes an interdisciplinary approach to enable successful systems by focusing on customer needs, requirements documentation, and design while considering the full problem from start to finish.
2. SE was applied to two project examples to improve management. For the first project, a systems breakdown structure and failure modes analysis prioritized critical systems. For the second, a requirements validation process captured scientists' needs and resolved disconnects between requirements and design.
3. SE integrates management functions by providing requirements and criteria upfront to guide project execution and sequencing of management elements at critical points to maximize impact.
Half-day workshop on high-performance green building design for USGBC Nevada chapter, Las Vegas, 1/8/13, using case studies from Jerry Yudelson's new book, The World's Greenest Buildings: Promise vs Performance in Sustainable Design, published January 2013.
The document provides an overview of a workshop on Business Value Engineering. It discusses:
1) Business Value Engineering as an approach to continuously improve how teams deliver value to customers by looking at processes end-to-end and incrementally improving.
2) Attribution to thinkers like Peter Drucker, Taiichi Ohno, and others who have influenced the approach.
3) The workshop agenda covers defining business value, developing business value models, identifying metrics, and examining elements and theories of business value engineering.
The document provides definitions and context around business value engineering. It discusses business value engineering as a learning and incremental improvement approach focused on delivering more value to customers. The document then summarizes different approaches to business value engineering, comparing the more traditional Procter & Gamble approach of extensive customer research and marketing to the experimental approach used by Google of quickly prototyping and testing ideas.
This document summarizes a presentation given on the new CDM 2015 regulations in the UK. It outlines 10 key points speakers discussed: 1) Safety in the construction industry has improved significantly since 2007 but it remains dangerous; 2) The Principal Designer role mirrors the previous Principal Contractor role; 3) CDM regulations work alongside other health and safety laws; 4) Laws set a minimum standard and professionals should aim higher; 5) Client duties are significant; 6) Projects require integration and teamwork with the client's needs prioritized; 7) Health issues need repeated review; 8) Professionals must be competent and properly manage projects; 9) Training is available to demonstrate competence; 10) Registering demonstrates meeting defined health and
1: Value Analysis provides great turnaround in the operations of the businesses.
2: Use Value Analysis to analyze and understand the detail of cost for specific situations.
3: Use it to find a focus on key areas for innovation.
4: Use it in reverse (called Value Engineering) to identify specific solutions to detail problems.
Value analysis and value engineering (VAVE) is a systematic process to analyze products and services to reduce costs while maintaining or improving performance. It originated from General Electric during World War II and focuses on analyzing a product's functions. The value of a product is defined as its functionality divided by its cost. VAVE can be applied across industries to solve problems, expand markets, and reduce costs as part of a long-term business strategy. To learn VAVE, one should receive training, use analysis tools, and practice with experienced practitioners to generate ideas for cost savings and value improvements.
The document summarizes a case study of a value engineering project carried out at an Indian Railways electric locomotive shed to address the problem of gear in two halves (GITH) failures. The project identified issues with the design basis, pinion weight, and oil pump gear shaft as causing impact loading and GITH breakages. Solutions proposed changing the design basis to make the GITH the driving gear, reducing the pinion face width and weight using Teflon, and changing to an external threaded oil pump gear shaft with a castle nut to eliminate play. The project aimed to reduce locomotive downtime and maintenance costs by redesigning faulty components with standardized specifications.
This presentation is about Value Engineering and contains:
1.History of VE
2.Value Concept
3.What is Value Engineering?
4.Implementation of VE in our project
5.Principle and Purpose of VE
6.Case Study
7.Conclusion
This document provides an overview of value analysis. It defines value analysis as a systematic process that compares the function of a product required by customers against the lowest cost of meeting specified performance and reliability. The key steps of value analysis are to establish objectives, analyze the production process, decompose product characteristics, brainstorm alternatives, select the best alternative, and implement changes. Value analysis aims to provide better value to customers and improve competitive position by eliminating unnecessary costs.
Benchmark Electronics A team (EU headquarters in Almelo, The Netherlands) developped a CREATIVE WORKSHOP of 2-3 days. Electronic product development. Results: cost reduction, innovation, new invented products in just a few days. Look at the presentation! Call Bert Blom +31611024589 or Mail: bert.blom@bench.com
Cost Reduction of a product through Value Analysis & Value EngineeringQuEST Global
This document summarizes a value analysis and value engineering approach used by QuEST to reduce product costs for customers. It describes how VAVE systematically analyzes product functions to identify potential cost savings opportunities without compromising quality or performance. The approach involves understanding requirements, analyzing functions, generating alternative ideas, evaluating options, and developing value alternatives. An example project demonstrates how QuEST applied this process to reduce material costs for an industrial control product by over 25% while improving performance.
The document provides an overview of value engineering, including its definition, purpose, and methodology. It defines value engineering as a systematic process that focuses on improving functions at the lowest cost while maintaining quality. The methodology involves 6 steps: information gathering, functional analysis, creativity, evaluation, development, and reporting. It also provides an example case study comparing the use of middle barrettes versus concrete bored piles for constructing a general cargo berth project at a port. Using piles was found to potentially reduce costs without compromising quality or functionality.
Project Management For Good Procurement Practicestjcornish
The document discusses project management best practices for procurement. It covers understanding procurement in light of project management, developing user requirement specifications, vendor management, and quality-based selection of vendors. Key topics include the difference between direct and indirect procurement, engineering economics concepts, requirements gathering techniques, contract types, solicitation planning, vendor selection methods, and quality-based selection of consulting engineers.
Value analysis and value engineering are techniques used to identify unnecessary costs in products, processes, and services. Value analysis is traditionally used after development to analyze existing offerings, while value engineering is used during design and development stages. Both use a team approach and function analysis methodology to reliably deliver necessary functions at the lowest total cost over the lifecycle in order to maximize value for the customer. Larry Miles is considered the founder of these techniques which he developed at GE in the 1940s and which have since been widely adopted.
This document provides an overview of the RSMeans publication titled "Value Engineering in the Construction Industry". It includes a table of contents that outlines the various chapters in the book, which cover topics such as project budgeting, cost modeling, function analysis, life cycle costing, and case studies applying value engineering techniques. The document also provides brief descriptions of the content included in each chapter. It indicates that the book presents advances in value engineering since previous editions and includes an updated disk with additional value engineering tools and automated formats.
Value engineering is a technique used to improve projects, processes, products, or services by determining the best functional balance between cost, reliability, and performance. It aims to identify unnecessary costs that can be eliminated without compromising quality, performance, or customer satisfaction. A value engineering study is conducted systematically using an eight-step job plan involving information gathering, functional analysis, creative idea generation, evaluation, and implementation. The goal is to deliver necessary functions at the lowest cost through improvements to design, materials selection, production processes, maintenance, and other factors.
This document provides an overview of value engineering and value analysis. It begins with the course outcomes and introduces value engineering and value analysis, distinguishing between the two. It then covers the history, definitions, types of value, functions, the value engineering/analysis cycle and job plan, application, reasons for poor value, and the steps in value engineering/analysis. Key points addressed include the objective to achieve equivalent or better performance at lower cost while maintaining requirements.
This document discusses key concepts in systems development including the systems development lifecycle, strategic planning, architecture, methodologies, and project management. It provides an overview of traditional waterfall and alternative approaches like prototyping and rapid application development. It also covers risk assessment, end user development, and the tension between IT organizations and end users.
Managing complex projects requires an approach that embraces uncertainty. Traditional project management methods focused on planning and certainty are ill-suited for knowledge work which involves evolving requirements and technologies. Effective approaches gather consensus, prioritize based on business value and risk reduction, use short build and feedback cycles, provide results-oriented reporting, and respect and empower team members. Historical examples that successfully managed uncertainty, such as the Manhattan Project and Polaris missile project, demonstrate these principles.
Project management through the eye of the systems engineerevolve2013
1. Systems engineering (SE) takes an interdisciplinary approach to enable successful systems by focusing on customer needs, requirements documentation, and design while considering the full problem from start to finish.
2. SE was applied to two project examples to improve management. For the first project, a systems breakdown structure and failure modes analysis prioritized critical systems. For the second, a requirements validation process captured scientists' needs and resolved disconnects between requirements and design.
3. SE integrates management functions by providing requirements and criteria upfront to guide project execution and sequencing of management elements at critical points to maximize impact.
Half-day workshop on high-performance green building design for USGBC Nevada chapter, Las Vegas, 1/8/13, using case studies from Jerry Yudelson's new book, The World's Greenest Buildings: Promise vs Performance in Sustainable Design, published January 2013.
At our webinar, "Getting Started With MBSE: A Data-Driven Approach With Innoslate," Systems Engineer, Lilleigh Stevie, shared the foundation of MBSE that allows you to easily track your system through the entire lifecycle.
The document discusses the implementation of the M5 system at Orbotech to improve their customer support processes. Some key points:
- The project involved implementing 50 main business processes across operations, logistics, finance and more in the M5 system. It also integrated various other systems and included business intelligence capabilities.
- Challenges included the distributed nature of Orbotech's global operations, different working styles across divisions, and demands from customers.
- The implementation followed Orbotech's methodology and had a steering committee and dedicated project teams. It involved defining requirements, customizing the system, converting data, developing reports and training users.
- After two pilot phases, the system went live across major
Controlling Project Performance using PDM - PSQT2005 - Ben LindersBen Linders
• A hands-on model for control of product and process quality.
• Support of release risk decisions based on defect data.
• ODC and Test Matrices applied in different test phases.
• Usage of feedback to analyze data and come to actions.
• Using project data for a business case for improvement.
The document discusses various techniques for project estimation including three point estimation, Delphi method, planning poker, function point analysis, use case points, and PERT diagrams. It provides details on each technique including how they are conducted, their advantages and disadvantages, and when each is best applied. The key aspects that estimators need to consider for large scale projects are work partitioning challenges, increasing communication overhead with larger teams, and understanding how fast the project can realistically be completed based on its size.
Improve Product Design with High Quality RequirementsElizabeth Steiner
The webinar discussed improving product design through high quality requirements. It emphasized the importance of understanding stakeholders, determining real needs through concept of operations documents, writing specific but not overly specific requirements, including traceability, and using tools to automatically check requirements quality. The presenter demonstrated Innoslate's requirements management tools.
This document provides an overview of software engineering. It discusses what software engineering is, common software development process models like waterfall, spiral, agile development, and the Unified Software Development Process (USDP). The USDP follows an iterative approach with phases for inception, elaboration, construction, and transition. Each phase has milestones and the process involves iterations where requirements, design, coding, and testing are done to create executable increments.
The document discusses software engineering and the Unified Software Development Process (USDP). It describes the USDP which includes phases of inception, elaboration, construction, and transition. Each phase involves iterations where requirements, analysis, design, implementation, and testing are done. The goal of each iteration is to produce an executable increment that is tested and evaluated.
Exploratory Testing Kari Kakkonen BTD 2017Kari Kakkonen
My talk on Exploratory Testing basics and its future at Belgium Testing Days / BNTQB Test Summit 2017 https://btdconf.org/ bit of slides revamp included
Webinar Slides: Using Innoslate for Program Management SarahCraig7
Join us, October 6th @2pm EST to learn how to use Innoslate for Program Management as well as a live demonstration by Dr. Steven Dam on how Innoslate allows program managers to execute a variety of management processes.
The management processes covered include:
•project work planning (PWP)
•project tracking and control (PTC)
•project risk management (PRM)
•project quality management (PQM)
•project configuration management (PCM)
•project subcontractor management (PSM)
Listen to Dr. Dam as he explains the features in Innoslate that enable program managers to conduct model-based reviews, restrict reviewers, secure information, and enable collaboration with comment summaries. Understand the processes that separate information and how to create workflows for management processes.
Agile business analysis the changing role of business analysts in agile sof...Nari Kannan
The document discusses the changing role of business analysts in agile software development. It outlines some of the key principles of agile development, including an iterative approach and valuing working software over documentation. Traditional business analysis can cause problems for agile projects, such as being out of date or acting as a communication barrier. Effective agile business analysis requires skills like collaboration and adapting to changing requirements.
Value Engineering - PMPD Presentation_0.pptxPareshSwami2
The document provides an overview of value engineering for a project presentation. It defines value engineering, outlines when it should be conducted in a project, and describes the typical multi-step methodology. Conducting value engineering early in design allows greater opportunities for savings without impacting schedule. The goals are to maximize necessary functions at the lowest possible cost while maintaining quality, safety, and stakeholder satisfaction over the long term. Examples of value engineering alternatives are also presented.
Module 6 - Systems Planning bak.pptx.pdfMASantos15
This document provides an overview of systems planning. It discusses strategic planning, including conducting a SWOT analysis and developing a mission statement, goals, and objectives. It also covers factors to consider for information systems projects, such as internal and external influences. The document outlines the steps of a feasibility study, including assessing operational, technical, economic, and schedule feasibility. Finally, it discusses the preliminary investigation process for planning an information systems project, which involves understanding the problem, defining scope and constraints, fact-finding, feasibility evaluation, estimating time and costs, and presenting results to management.
Optimizing Post Remediation Groundwater Performance with Enhanced Microbiolog...Joshua Orris
Results of geophysics and pneumatic injection pilot tests during 2003 – 2007 yielded significant positive results for injection delivery design and contaminant mass treatment, resulting in permanent shut-down of an existing groundwater Pump & Treat system.
Accessible source areas were subsequently removed (2011) by soil excavation and treated with the placement of Emulsified Vegetable Oil EVO and zero-valent iron ZVI to accelerate treatment of impacted groundwater in overburden and weathered fractured bedrock. Post pilot test and post remediation groundwater monitoring has included analyses of CVOCs, organic fatty acids, dissolved gases and QuantArray® -Chlor to quantify key microorganisms (e.g., Dehalococcoides, Dehalobacter, etc.) and functional genes (e.g., vinyl chloride reductase, methane monooxygenase, etc.) to assess potential for reductive dechlorination and aerobic cometabolism of CVOCs.
In 2022, the first commercial application of MetaArray™ was performed at the site. MetaArray™ utilizes statistical analysis, such as principal component analysis and multivariate analysis to provide evidence that reductive dechlorination is active or even that it is slowing. This creates actionable data allowing users to save money by making important site management decisions earlier.
The results of the MetaArray™ analysis’ support vector machine (SVM) identified groundwater monitoring wells with a 80% confidence that were characterized as either Limited for Reductive Decholorination or had a High Reductive Reduction Dechlorination potential. The results of MetaArray™ will be used to further optimize the site’s post remediation monitoring program for monitored natural attenuation.
Presented by The Global Peatlands Assessment: Mapping, Policy, and Action at GLF Peatlands 2024 - The Global Peatlands Assessment: Mapping, Policy, and Action
Climate Change All over the World .pptxsairaanwer024
Climate change refers to significant and lasting changes in the average weather patterns over periods ranging from decades to millions of years. It encompasses both global warming driven by human emissions of greenhouse gases and the resulting large-scale shifts in weather patterns. While climate change is a natural phenomenon, human activities, particularly since the Industrial Revolution, have accelerated its pace and intensity
ENVIRONMENT~ Renewable Energy Sources and their future prospects.tiwarimanvi3129
This presentation is for us to know that how our Environment need Attention for protection of our natural resources which are depleted day by day that's why we need to take time and shift our attention to renewable energy sources instead of non-renewable sources which are better and Eco-friendly for our environment. these renewable energy sources are so helpful for our planet and for every living organism which depends on environment.
Improving the viability of probiotics by encapsulation methods for developmen...Open Access Research Paper
The popularity of functional foods among scientists and common people has been increasing day by day. Awareness and modernization make the consumer think better regarding food and nutrition. Now a day’s individual knows very well about the relation between food consumption and disease prevalence. Humans have a diversity of microbes in the gut that together form the gut microflora. Probiotics are the health-promoting live microbial cells improve host health through gut and brain connection and fighting against harmful bacteria. Bifidobacterium and Lactobacillus are the two bacterial genera which are considered to be probiotic. These good bacteria are facing challenges of viability. There are so many factors such as sensitivity to heat, pH, acidity, osmotic effect, mechanical shear, chemical components, freezing and storage time as well which affects the viability of probiotics in the dairy food matrix as well as in the gut. Multiple efforts have been done in the past and ongoing in present for these beneficial microbial population stability until their destination in the gut. One of a useful technique known as microencapsulation makes the probiotic effective in the diversified conditions and maintain these microbe’s community to the optimum level for achieving targeted benefits. Dairy products are found to be an ideal vehicle for probiotic incorporation. It has been seen that the encapsulated microbial cells show higher viability than the free cells in different processing and storage conditions as well as against bile salts in the gut. They make the food functional when incorporated, without affecting the product sensory characteristics.
Recycling and Disposal on SWM Raymond Einyu pptxRayLetai1
Increasing urbanization, rural–urban migration, rising standards of living, and rapid development associated with population growth have resulted in increased solid waste generation by industrial, domestic and other activities in Nairobi City. It has been noted in other contexts too that increasing population, changing consumption patterns, economic development, changing income, urbanization and industrialization all contribute to the increased generation of waste.
With the increasing urban population in Kenya, which is estimated to be growing at a rate higher than that of the country’s general population, waste generation and management is already a major challenge. The industrialization and urbanization process in the country, dominated by one major city – Nairobi, which has around four times the population of the next largest urban centre (Mombasa) – has witnessed an exponential increase in the generation of solid waste. It is projected that by 2030, about 50 per cent of the Kenyan population will be urban.
Aim:
A healthy, safe, secure and sustainable solid waste management system fit for a world – class city.
Improve and protect the public health of Nairobi residents and visitors.
Ecological health, diversity and productivity and maximize resource recovery through the participatory approach.
Goals:
Build awareness and capacity for source separation as essential components of sustainable waste management.
Build new environmentally sound infrastructure and systems for safe disposal of residual waste and replacing current dumpsites which should be commissioned.
Current solid waste management situation:
The status.
Solid waste generation rate is at 2240 tones / day
collection efficiently is at about 50%.
Actors i.e. city authorities, CBO’s , private firms and self-disposal
Current SWM Situation in Nairobi City:
Solid waste generation – collection – dumping
Good Practices:
• Separation – recycling – marketing.
• Open dumpsite dandora dump site through public education on source separation of waste, of which the situation can be reversed.
• Nairobi is one of the C40 cities in this respect , various actors in the solid waste management space have adopted a variety of technologies to reduce short lived climate pollutants including source separation , recycling , marketing of the recycled products.
• Through the network, it should expect to benefit from expertise of the different actors in the network in terms of applicable technologies and practices in reducing the short-lived climate pollutants.
Good practices:
Despite the dismal collection of solid waste in Nairobi city, there are practices and activities of informal actors (CBOs, CBO-SACCOs and yard shop operators) and other formal industrial actors on solid waste collection, recycling and waste reduction.
Practices and activities of these actor groups are viewed as innovations with the potential to change the way solid waste is handled.
CHALLENGES:
• Resource Allocation.
Microbial characterisation and identification, and potability of River Kuywa ...Open Access Research Paper
Water contamination is one of the major causes of water borne diseases worldwide. In Kenya, approximately 43% of people lack access to potable water due to human contamination. River Kuywa water is currently experiencing contamination due to human activities. Its water is widely used for domestic, agricultural, industrial and recreational purposes. This study aimed at characterizing bacteria and fungi in river Kuywa water. Water samples were randomly collected from four sites of the river: site A (Matisi), site B (Ngwelo), site C (Nzoia water pump) and site D (Chalicha), during the dry season (January-March 2018) and wet season (April-July 2018) and were transported to Maseno University Microbiology and plant pathology laboratory for analysis. The characterization and identification of bacteria and fungi were carried out using standard microbiological techniques. Nine bacterial genera and three fungi were identified from Kuywa river water. Clostridium spp., Staphylococcus spp., Enterobacter spp., Streptococcus spp., E. coli, Klebsiella spp., Shigella spp., Proteus spp. and Salmonella spp. Fungi were Fusarium oxysporum, Aspergillus flavus complex and Penicillium species. Wet season recorded highest bacterial and fungal counts (6.61-7.66 and 3.83-6.75cfu/ml) respectively. The results indicated that the river Kuywa water is polluted and therefore unsafe for human consumption before treatment. It is therefore recommended that the communities to ensure that they boil water especially for drinking.
Kinetic studies on malachite green dye adsorption from aqueous solutions by A...Open Access Research Paper
Water polluted by dyestuffs compounds is a global threat to health and the environment; accordingly, we prepared a green novel sorbent chemical and Physical system from an algae, chitosan and chitosan nanoparticle and impregnated with algae with chitosan nanocomposite for the sorption of Malachite green dye from water. The algae with chitosan nanocomposite by a simple method and used as a recyclable and effective adsorbent for the removal of malachite green dye from aqueous solutions. Algae, chitosan, chitosan nanoparticle and algae with chitosan nanocomposite were characterized using different physicochemical methods. The functional groups and chemical compounds found in algae, chitosan, chitosan algae, chitosan nanoparticle, and chitosan nanoparticle with algae were identified using FTIR, SEM, and TGADTA/DTG techniques. The optimal adsorption conditions, different dosages, pH and Temperature the amount of algae with chitosan nanocomposite were determined. At optimized conditions and the batch equilibrium studies more than 99% of the dye was removed. The adsorption process data matched well kinetics showed that the reaction order for dye varied with pseudo-first order and pseudo-second order. Furthermore, the maximum adsorption capacity of the algae with chitosan nanocomposite toward malachite green dye reached as high as 15.5mg/g, respectively. Finally, multiple times reusing of algae with chitosan nanocomposite and removing dye from a real wastewater has made it a promising and attractive option for further practical applications.
Epcon is One of the World's leading Manufacturing Companies.EpconLP
Epcon is One of the World's leading Manufacturing Companies. With over 4000 installations worldwide, EPCON has been pioneering new techniques since 1977 that have become industry standards now. Founded in 1977, Epcon has grown from a one-man operation to a global leader in developing and manufacturing innovative air pollution control technology and industrial heating equipment.
Evolving Lifecycles with High Resolution Site Characterization (HRSC) and 3-D...Joshua Orris
The incorporation of a 3DCSM and completion of HRSC provided a tool for enhanced, data-driven, decisions to support a change in remediation closure strategies. Currently, an approved pilot study has been obtained to shut-down the remediation systems (ISCO, P&T) and conduct a hydraulic study under non-pumping conditions. A separate micro-biological bench scale treatability study was competed that yielded positive results for an emerging innovative technology. As a result, a field pilot study has commenced with results expected in nine-twelve months. With the results of the hydraulic study, field pilot studies and an updated risk assessment leading site monitoring optimization cost lifecycle savings upwards of $15MM towards an alternatively evolved best available technology remediation closure strategy.
Evolving Lifecycles with High Resolution Site Characterization (HRSC) and 3-D...
Ve intro
1. June 5, 2008 ILC Conventional Facilities and Siting Workshop 1
History of the First ILC
Value Engineering
Workshop
2. June 5, 2008 ILC Conventional Facilities and 2
Value Engineering
• In November ‘07 a three day “Formal” Value
Engineering Workshop was held at Fermilab.
Charge
• Conduct a workshop that will
comprehensively examine the power and
cooling system requirements and design
solutions. Concentrating on the largest power
user, the Main Linac, examine all aspects of
the technical equipment and conventional
equipment as it relates to power and cooling.
3. June 5, 2008 ILC Conventional Facilities and 3
• Participants
US Corp of Engineers OVEST Team
Richard Lambert, Facilitator, Keith Ellmers, John Mathis
Main Linac and High level RF
Mike Neubauer (SLAC), Chris Jensen (Fermilab),
Shigeki Fukuda (KEK), Keith Jobe (SLAC)
Consultants :
Larry Hanson PE Burns and Mc Donnell, Robert Knoedler Hanson Engineering
Tracy Lundin Hanson, Venkat Kumar, University of Chicago
Javier Sevilla, SLAC
Conventional Facilities and Siting
Vic Kuchler, Marc Ross, Emil Huedem, Lee Hammond, Maurice Ball,
Tom Peterson, Tom Lackowski,
Observer: Bakul Banerjee
4. June 5, 2008 ILC Conventional Facilities and 4
Agenda
• Workshop Agenda:
• Tuesday Nov. 27, 2007 1:00 to 5:30
• 1:00 Information Phase
• Welcome and Introductions Tom Lackowski
• Opening remarks Vic Kuchler
• ILC Project Overview Marc Ross
• ILC Conventional Construction Tom Lackowski
• VM Process Overview Richard Lambert – OVEST
• Main Linac Equipment power and Mike Neubauer
• cooling Criteria
• 3:00-3:30 Coffee break
• 3:30-5:30 Function Analysis Phase
• Shaft 7 CF&S supplied Power and Cooling Emil Huedem
• HVAC Lee Hammond
• Power Tom Lackowski
• FAST Diagram Richard Lambert
• 5:30 Adjourn
• Wed. Nov. 28, 2007 9:00 to 5:30
• 9:00-10:30 Speculation Phase Richard Lambert
• 10:30-11:00 Coffee Break
• 12:30-1:30 Lunch
• 1:30-3:00 Speculation Phase Continued
• 3:00-3:30 Coffee Break
• 3:30-5:30 Speculation Phase Continued or Start Analysis Phase
• 5:30 Adjourn
• Thursday Nov. 29, 2007 9:00 to 5:30
• 9:00-10:30 Analysis Phase
• 10:30-11:00 Coffee Break
• 11:00 -12:30 Development Phase Planning
• 12:30-1:30 Lunch
• 1:30-3:00 Development Phase Planning Continued
• Presentation Phase Planning
• Workshop Close Out Tom Lackowski
• 3:00-3:30 Coffee Break
• 3:30-5:30 Development of EDR Work Packages
• 5:30 Adjourn
5. June 5, 2008 ILC Conventional Facilities and 5
• The following slides are from Richard
Lambert of the US Army Corp of Engineers.
• I will quickly run through these slides,
stopping at some of the key points.
• Summarize the experience.
• Provide some ideas for improvement.
6. June 5, 2008 ILC Conventional Facilities and Siting Workshop 6
Value Engineering
What is it?
7. June 5, 2008 ILC Conventional Facilities and 7
What Value Engineering Is Not!
• Cost Cutting
• Design Review
• Project Elimination
• Scope Reduction
• Quality Reduction
• Detailed Cost
Estimating
• Redesign
8. June 5, 2008 ILC Conventional Facilities and 8
What Value Engineering Is!
An organized study of FUNCTIONS to satisfy
the USER’S NEEDS with a QUALITY
PRODUCT at the LOWEST LIFE CYCLE COST
through APPLIED CREATIVITY
9. June 5, 2008 ILC Conventional Facilities and 9
Definition of Value Engineering
• Terms used to describe “Value Engineering”
– Value Methodology
• This is the “official” term used by SAVE International. It
describes the overall body of knowledge.
– Value Analysis
• This was the first term used when the process was
originally developed for manufacturing
– Value Engineering
• The term “engineering” was used to identify the process
as it is applied to design and construction
– Value Management
• This less commonly used term refers to its application to
business processes
10. June 5, 2008 ILC Conventional Facilities and 10
Definition of Value Engineering
• The value of a function is defined as the
relationship of cost to performance
Performancemax
Costmin
Valuemax
=
11. June 5, 2008 ILC Conventional Facilities and 11
Definition of Value Engineering
• “Good” Value is the lowest cost to reliably provide the
required function with essential performance.
• Value is always increased by decreasing costs while
maintaining essential performance.
• Value may also be increased if the customer needs, wants,
and is willing to pay for greater performance.
12. June 5, 2008 ILC Conventional Facilities and 12
Range of Application
• VE applies to everything because every
project or process has a function
• VE can be applied at any point of the
design or process
• VE is a problem solving technique
• VE can be used as a technique for
developing design criteria
13. June 5, 2008 ILC Conventional Facilities and 13
Reasons for Poor Value…
• Lack of and/or poor
coordination among
designers
• Failure to network
with customer – poor
definition of needs
and wants
• Design based on
habitual thinking or
mistaken beliefs
• Not enough time for
project formulation
and/or design
• Failure to utilize latest
technologies
• Negative attitudes
14. June 5, 2008 ILC Conventional Facilities and 14
More Reasons for Poor Value…
• Poor communication in developing project scope
• Lack of consensus among project stakeholders with regard to
project scope
• Outdated or inappropriate design standards
• Incorrect assumptions based on poor information
• Fixation with previous design concepts
• Honest wrong beliefs
15. June 5, 2008 ILC Conventional Facilities and 15
Common Misconceptions
• “VE is something we do all the time.”
– No it isn’t. VE requires the application of a specialized body of
knowledge at the right time with the right people.
• “VE degrades project performance.”
– If applied properly, its should maintain or improve project
performance.
• “VE is just another management fad.”
– VE was developed in 1943. It is required by federal and many state
laws. It has a professional society and maintains professional
standards and accreditation.
• “VE is really just cost cutting.”
– Really?
16. June 5, 2008 ILC Conventional Facilities and 16
VE vs. Cost Cutting/Reduction
• VE seeks to maintain or
improve performance while
reducing TOTAL costs.
• VE is a pre-planned allocation
of time and effort.
• VE is a highly structured
process using a formal
methodology.
• VE utilizes an objective, multi-
disciplined team and a trained
facilitator.
• VE provides an organized
follow-up, implementation and
reporting program.
• Cost reduction seeks to cut
INITIAL costs, often at the
expense of project quality.
• Cost reduction is usually a
reaction to budget overruns.
• Cost reduction is an informal
process.
• Cost reduction generally
involves only a few
management personnel.
• Cost reduction does not.
17. June 5, 2008 ILC Conventional Facilities and 17
Value Engineering Quality
Value Engineering is a tool/method to
enhance QUALITY
18. June 5, 2008 ILC Conventional Facilities and 18
Timing the VE Effort
Planning
Design
Development
Final Design /
Bid Documents
Construction
Project Life Cycle
$
Potential Value Engineering Cost Savings
Cost to
Change
Potential
Savings
19. June 5, 2008 ILC Conventional Facilities and 19
Some VE Study Objectives
• Performance Improvement
• Significant Cost Savings/Avoidance
• Optimization of Resources (Time & Money)
• Review (Technical, QA) – Optional Objective
• Coordination (In- House & Users)
• Transfer Innovative Technologies
• Have Fun!
20. June 5, 2008 ILC Conventional Facilities and 20
The Value Engineering Job Plan
• Provides a systematic
approach
• Divides the study into
distinct work elements
21. June 5, 2008 ILC Conventional Facilities and 21
Value Engineering Is:
Step 2 - Information
Step 3 – Function Analysis
Step 4 – Speculation/Creativity
Step 5 – Evaluation
Step 6 - Development
Step 7 – Presentation/Report
Step 1 – Preparation/Organization
Step 8 – Implementation & Audit
22. June 5, 2008 ILC Conventional Facilities and 22
Information Phase
Purposes
• To determine user needs
• To gather and tabulate information concerning the
item as presently designed
• To build team knowledge and understanding of the
project
• To completely understand the specific use of function
requirements of the item
• To visit the site (preferable)
• Process continues throughout remainder of the study
23. June 5, 2008 ILC Conventional Facilities and 23
Information Phase
Techniques
• Get all the facts from the best possible sources (e.g. design
team)
• Develop cost models
• Determine and evaluate the function(s) of the present design
• Prepare a FAST diagram
• Identify & define project Performance Criteria
• Develop project Performance Ratings
• Determine present design objectives & constraints
• What does the customer want?
USE GOOD HUMAN RELATIONS
24. June 5, 2008 ILC Conventional Facilities and 24
Why is Functional Analysis
Important?
• You can’t always get what you want!
• You can’t always get what you want!
• You can’t always get what you want!
• BUT – if you try, somehow you just might ,
from time to time, get what you need!
• Function Analysis defines user’s needs
through verb-noun pairings
25. June 5, 2008 ILC Conventional Facilities and 25
Function – The
• Specific purposes or intended use of an item (What is this?
What is it supposed to do? What else can it do?)
– Function is that which makes a product, process or project work or
sell.
– All cost is for function.
– Primary functions posses value and are required to make a product
work or sell.
– Secondary functions have no value and are present due to the
current design of the product.
• That characteristic that makes a product or service have
value
• Determine by considering the user’s actual needs
26. June 5, 2008 ILC Conventional Facilities and 26
FAST Diagram
Function Analysis System Technique
Verb-Noun
Function
Verb-Noun
Function
Verb-Noun
Function
Verb-Noun
Function
How Why
Generating a Function Picture
Scope Line
Scope Line
27. June 5, 2008 ILC Conventional Facilities and 27
The Purpose of a FAST Diagram is
• Show specific relationships of all
functions with respect to each other
• Deepen the understanding of the problem
to be solved
• Promote discussion and information
gathering – team building
• Support the process of creativity
28. June 5, 2008 ILC Conventional Facilities and 28
FAST Diagrams
Higher Order
Function
Primary
Function
Secondary
Function
Secondary
Function
Assumed
Function
Required
Secondary
Function
Design
Objective
“All The Time”
Function
HOW? WHY?
WHEN?
29. June 5, 2008 ILC Conventional Facilities and 29
Function Analysis
• Fuel Storage System
Steel
TankSacrificial
Anode
Excavation
&
Backfill
30. June 5, 2008 ILC Conventional Facilities and 30
Function Analysis
• Identify the functions
Store
FuelProtect
Tank Hide
Tank
31. June 5, 2008 ILC Conventional Facilities and 31
Function Analysis
• Identify the “scope”
Complete
Task
Perform
Work
Create
Energy
Dispense
Fuel
Store
Fuel
Obtain
Fuel
PrimaryPrimary
FunctionFunction
HOW? WHY?
32. June 5, 2008 ILC Conventional Facilities and 32
Function Analysis
• Identify the “scope”
Complete
Task
Perform
Work
Create
Energy
Dispense
Fuel
Store
Fuel
Obtain
Fuel
Tanks
Bins
Silos
Pools
Boxes
Sacks
PrimaryPrimary
FunctionFunction
HOW? WHY?
33. June 5, 2008 ILC Conventional Facilities and 33
Function Analysis
• Identify the “scope”
Complete
Task
Perform
Work
Create
Energy
Dispense
Fuel
Store
Fuel
Obtain
Fuel
PrimaryPrimary
FunctionFunction
HOW? WHY?
34. June 5, 2008 ILC Conventional Facilities and 34
Function Analysis
• Identify the “scope”
Manufacture
Purchase
Recycle
Trade
Generate
Mine
Complete
Task
Perform
Work
Create
Energy
Dispense
Fuel
Store
Fuel
Obtain
Fuel
PrimaryPrimary
FunctionFunction
HOW? WHY?
35. June 5, 2008 ILC Conventional Facilities and 35
Function Analysis
• Identify the “scope”
Complete
Task
Perform
Work
Create
Energy
Dispense
Fuel
Store
Fuel
Obtain
Fuel
PrimaryPrimary
FunctionFunction
HOW? WHY?
36. June 5, 2008 ILC Conventional Facilities and 36
Function Analysis
• Identify the “scope”
HOW? WHY?
Complete
Task
Perform
Work
Create
Energy
Dispense
Fuel
Store
Fuel
Obtain
Fuel
PrimaryPrimary
FunctionFunction
Pump
Pipeline
Conveyor
Siphon
Cable
Microwave
37. June 5, 2008 ILC Conventional Facilities and 37
Speculation Phase
Purposes
• To generate a large number of alternatives
that provide the item’s basic function(s)
without considering their practicality
38. June 5, 2008 ILC Conventional Facilities and 38
Speculation Phase
Techniques
• Use creative thinking
• No rules – no limits
• Forget about scope, speculate on the FUNCTION - not on
the item
• Don’t let regulations or people control your thinking
• If you don’t look for the second right answer, you won’t
find it
• Eliminate/simplify: modify and/or combine alternatives
• Think – get out of the comfort zone and enjoy it!
• Keep talking, keep generating, let the juices flow!
• Its about CHANGE!
USE GOOD HUMAN RELATIONS
39. June 5, 2008 ILC Conventional Facilities and 39
We’all’in’s never done it that
way before!!
Regulations
and
Guidelines
are sacred!
What will
my boss
think?
What if it doesn't work??
??
?
40. June 5, 2008 ILC Conventional Facilities and 40
Creativity
41. June 5, 2008 ILC Conventional Facilities and 41
Creativity
Brainstorming Rules & Objectives…
• Criticism/evaluation is prohibited (at this time)
• Free-wheeling is welcomed and encouraged – be
uninhibited and think as a child
• Be spontaneous – rapid fire ‘gut feels’
• Quantity is desired over quality – cover the walls
• Combine and add to ideas
• Build upon another person’s ideas
• How do others solve similar problems
• Record all ideas
42. June 5, 2008 ILC Conventional Facilities and 42
There Are No Dumb Ideas!
OK, so some of the ideas were dumb!
Which leads us to…….
43. June 5, 2008 ILC Conventional Facilities and 43
Analysis Phase
Purposes
• To evaluate, criticize, and rank alternatives
• Identify advantages and disadvantages as compared to the
baseline project
• Which alternatives offer the best combination of:
– Design-ability
– Construct-ability
– Operational ease
– Quality assurance
– Customer satisfaction
– And… low life-cycle cost
• To develop alternatives that offer the greatest increase in
value
44. June 5, 2008 ILC Conventional Facilities and 44
Analysis Phase
Techniques
• Prior experience
• Collective ‘Gut” feels
• Stakeholder input
• Use cost references
• Apply matrix techniques
– Define performance measures
– Weight and rank measures
– Evaluate alternatives
• Make sketches
• Consult experts
• Use your own judgment
USE GOOD HUMAN RELATIONS
45. June 5, 2008 ILC Conventional Facilities and 45
You gotta also consider…
Life Cycle Cost Analysis! (LCC)
• A definition…
“The systematic evaluation of alternative
designs and the comparison of their projected
development/design, construction,
operation/maintenance and disposal costs or
salvage value over a specified time period.”
46. June 5, 2008 ILC Conventional Facilities and 46
In other words, LCC is…
• Simply put… Consider all the costs!
• Total LCC = Initial Cost + Ownership Cost
+ Salvage value/disposal costs
• Deceptive… For example, security was
typically a minor cost, but can now be a
major consideration.
• LCC gives decision makers a complete
awareness of Big Picture
47. June 5, 2008 ILC Conventional Facilities and 47
Development Phase
Purposes
• To select the best alternative(s)
• To develop complete written and
oral proposals
48. June 5, 2008 ILC Conventional Facilities and 48
Development Phase
Techniques
• Recommend specifics, not generalities
• Make sure your report describes the disadvantages as well as the
advantages
• Gather convincing facts
– Assure technical adequacy
• Spend your client’s money as you would your own
– Complete order-of-magnitude cost estimate w/LCC
• Prepare Proposal
– Finalize FAST diagram for proposal
– Sell the idea through the justification
– You are selling something
uncomfortable to most people – CHANGE!
• Misteaks will cast doubt on your validity
USE GOOD HUMAN
RELATIONS
49. June 5, 2008 ILC Conventional Facilities and 49
Presentation Phase
Purposes
• To present value engineering study
proposal(s) to the decision makers/stake
holders
• To obtain approval/support
• To enhance potential implementation
50. June 5, 2008 ILC Conventional Facilities and 50
Presentation Phase
Techniques
• Again, you are selling CHANGE!
• Your enthusiasm will sell your proposal
• Use FAST diagram as a communication tool – Are
the most important functions satisfied?
• Be brief, pertinent and convincing
• Keep it simple
USE GOOD HUMAN RELATIONS
51. June 5, 2008 ILC Conventional Facilities and 51
Presentation Phase
Techniques
• Anticipate/remove road blocks – understand
their point of view
• Network with people and gain support
• BUT – you can’t please everybody
• AND – don’t overload the cart with too much
information
USE GOOD HUMAN RELATIONS
52. June 5, 2008 ILC Conventional Facilities and 52
How to find out more about
VE...
• A Value Engineering Professional Society
• Information about becoming a Certified Value
Specialist
• Professional journals, annual conference
• Web site lists local chapters
• Also lists VE consultants and specialists
53. June 5, 2008 ILC Conventional Facilities and 53
Important Links
• SAVE International
– www.value-eng.org
54. June 5, 2008 ILC Conventional Facilities and 54
Questions
Don’t be shy!
55. June 5, 2008 ILC Conventional Facilities and 55
Results of VE Workshop
• Our first VE study had
55 total Proposal that fit
into 20 groups
• Resources ran dry
before the proposals
could be evaluated.
56. June 5, 2008 ILC Conventional Facilities and 56
Proposal #12 Description
57. June 5, 2008 ILC Conventional Facilities and 57
Proposal #12 Description
58. June 5, 2008 ILC Conventional Facilities and 58
Cost Proposal Example
59. June 5, 2008 ILC Conventional Facilities and 59
Comments on Following VE Workshop
• The Formal VE process has the benefits over
informal continuous VE during the normal
design process.
– Various viewpoints provided.
– Fresh eyes
– Documentation
– Challenges the statue quo
• A workshop leader is needed to keep
movement in a productive direction.
Attending a workshop provides enough of a
understanding of the process to lead a
workshop.
60. June 5, 2008 ILC Conventional Facilities and 60
Comments on Following VE Workshop
• Planning is very important. Review the list or
participants with all of the stakeholders.
Having gaps in the needed technical
expertise is frustrating.
• Use both webex and video should be used for
those not attending in persons.
• Budget adequate resources.
• Preparation and Participation of project personnel
• Consultants (Industry or lab personnel not on the project)
– Time
– Travel and expenses
• Proposal Development
Editor's Notes
<number>
[Angie, click each at a time to uncover the reasons that it is scary to move outside the comfort zone box and into the realm of the unknown. Ask the students for other reasons.
“Don’t blame me boss, I did it the way we always did (and let our competitors get the contract).”
<number>
[Angie – say whatever you want]
<number>
It’s not rocket science, but often people forget to include the most obvious items. It’s about “cradle to grave” thinking.
<number>
[Angie – pass out the brochures if you get them in time]
Also, refer them to me if they want to want more information other than contacting the SAVE office.
Also, remember what I said about the initiative I am involved with at the Pittsburgh District. The students you are talking to could be prospective employees.