Certificate of Achievement Stuart Westbrook Schneider Electric Data Center Certified Associate Exam
•
1 like•802 views
This Certificate of Achievement is awarded to Susan Hartman for successfully completing the Data Center Certified Associate Exam on September 25, 2015. The exam certifies that she possesses the basic knowledge necessary to participate on teams that design or upgrade the critical physical layer of the Data Center.
Report
Share
Report
Share
Download to read offline
Recommended
Failure Mode Effects & Criticality Analysis 2-Day Workshop by Tetrahedron
The Failure Mode Effects and Criticality Analysis is a reliability evaluation/design technique which examines the potential failure modes within a system and its equipment, in order to determine the effects on equipment and system performance.
ChronicCareIQ Summer Internship Presentation
The document outlines an agenda for an internship presentation on software testing and UX design. It covers maintaining quality through various testing methods, exploring automation tools, and getting feedback to plan future improvements. The presentation discusses the current testing process, proposes a new dashboard wireframe, and takes questions on prototyping and next steps.
Building a Project Charter with Matt Hansen at StatStuff
A review of how to compile the various Define Phase tools for building a project charter for a typical Six Sigma DMAIC project.
Project Pre-Assessment Using a Min/Max Analysis with Matt Hansen at StatStuff
A review of why it’s important to do a project pre-assessment and how to do it using a Min/Max Analysis.
Essential building blocks of a lean and efficient test process
Lean and efficient test process framework (TestSmart)
1.Provide quality gates across the Application Lifecycle to prevent the problems faced currently
2.Incrementally builds the missing requirements and test cases
3.Improved defect containment resulting in increased customer satisfaction
4.Reduces overheads and consequently cycle time
Haricharan Reddy(Netbackup)_resume
Haricharan Reddy D is seeking a position that provides challenging work and growth. He has 3 years of experience as a Veritas Netbackup Administrator at Capgemini, where he is responsible for resolving incidents, configuring backups, and troubleshooting errors. He has experience with Netbackup versions 7.5 and 7.6, and has also worked with technologies like EMC Networker, Arcserve, and TSM. He holds a Bachelor's degree in Computer Science and certifications in EMC storage management.
The DMAIC Roadmap (Levels 1 & 2) with Matt Hansen at StatStuff
A high-level roadmap through the DMAIC methodology that navigates the user through the various tools and concepts for leading a Six Sigma project.
Lean and Six Sigma Project Methodologies by Matt Hansen at StatStuff (S03)
This document introduces five project methodologies - Lean, DMAIC, DMADV, DFSS, and PMI - and provides guidance on when each is appropriate to use. It explains the differences between efficiency and effectiveness, and how the methodologies focus on one or the other. A decision tree is presented to help determine which methodology to apply based on whether the project involves a new or existing process/output and is focused on effectiveness or efficiency. Readers are prompted to analyze past projects and potential future ones to practice applying the framework.
Recommended
Failure Mode Effects & Criticality Analysis 2-Day Workshop by Tetrahedron
The Failure Mode Effects and Criticality Analysis is a reliability evaluation/design technique which examines the potential failure modes within a system and its equipment, in order to determine the effects on equipment and system performance.
ChronicCareIQ Summer Internship Presentation
The document outlines an agenda for an internship presentation on software testing and UX design. It covers maintaining quality through various testing methods, exploring automation tools, and getting feedback to plan future improvements. The presentation discusses the current testing process, proposes a new dashboard wireframe, and takes questions on prototyping and next steps.
Building a Project Charter with Matt Hansen at StatStuff
A review of how to compile the various Define Phase tools for building a project charter for a typical Six Sigma DMAIC project.
Project Pre-Assessment Using a Min/Max Analysis with Matt Hansen at StatStuff
A review of why it’s important to do a project pre-assessment and how to do it using a Min/Max Analysis.
Essential building blocks of a lean and efficient test process
Lean and efficient test process framework (TestSmart)
1.Provide quality gates across the Application Lifecycle to prevent the problems faced currently
2.Incrementally builds the missing requirements and test cases
3.Improved defect containment resulting in increased customer satisfaction
4.Reduces overheads and consequently cycle time
Haricharan Reddy(Netbackup)_resume
Haricharan Reddy D is seeking a position that provides challenging work and growth. He has 3 years of experience as a Veritas Netbackup Administrator at Capgemini, where he is responsible for resolving incidents, configuring backups, and troubleshooting errors. He has experience with Netbackup versions 7.5 and 7.6, and has also worked with technologies like EMC Networker, Arcserve, and TSM. He holds a Bachelor's degree in Computer Science and certifications in EMC storage management.
The DMAIC Roadmap (Levels 1 & 2) with Matt Hansen at StatStuff
A high-level roadmap through the DMAIC methodology that navigates the user through the various tools and concepts for leading a Six Sigma project.
Lean and Six Sigma Project Methodologies by Matt Hansen at StatStuff (S03)
This document introduces five project methodologies - Lean, DMAIC, DMADV, DFSS, and PMI - and provides guidance on when each is appropriate to use. It explains the differences between efficiency and effectiveness, and how the methodologies focus on one or the other. A decision tree is presented to help determine which methodology to apply based on whether the project involves a new or existing process/output and is focused on effectiveness or efficiency. Readers are prompted to analyze past projects and potential future ones to practice applying the framework.
teamwork board.3.6.2014 final
This document describes the implementation of TEAMwork boards in the pediatric intensive care unit (PICU) at a children's hospital. The TEAMwork boards were developed to foster frequent problem solving and timely resolution of issues using a visual tool with red, yellow, and green sections. An example problem around critical medication IV drips was presented, showing the current state challenges and proposed future state improvements. Survey results found the boards had a positive impact and staff felt their ideas were considered. The boards promoted continuous improvement and engagement. Keys to their success included encouraging idea submission and feedback, and recognizing contributions.
Compiling Operational Definitions with Matt Hansen at StatStuff
Operational definitions are lists of definitions for key terms and acronyms used in a particular business area or project. They help unify discussion for teams, prevent confusion, and allow new people to quickly understand processes. To compile operational definitions, listen for unique terms used by the team, ask subject matter experts for definitions, and update the list throughout the project. While not required for small projects, operational definitions are especially helpful for newcomers to an area. Definitions can be included as an appendix or tracked separately and shared with team members.
Documenting a New Process with SOPs
A review of the necessity and how to build standard operating procedures (SOPs) when making changes to a process.
Problem Resolution Using DMAIC with Matt Hansen at StatStuff
A review of how the DMAIC methodology follows the typical steps we follow when trying to resolve a problem.
Erp 20090521
The white paper discusses best practices for implementing an ERP system. It recommends (1) understanding the strategic importance of the implementation process, (2) building an appropriate implementation team of mid-level managers, and (3) setting a realistic plan and timeline supported by backfilling employee responsibilities. Straying from proven implementation methods risks failure and increased costs to fix issues later.
Managing Test Environments
Test environments are important for project success and require upfront organization and proactive management to minimize downtime. Ensuring test environments are stable, maintainable, accurate and accessible can save significant costs by reducing defects, maintaining project schedules, and maximizing development and testing time. Key questions to address include what the environment will be used for, its technical structure, who will access it, and how many environments are needed to minimize downtime.
The case for continuous delivery
The document discusses the benefits of adopting continuous delivery (CD) principles for software development. It outlines how CD can (1) create a repeatable, reliable release process that automates tasks, (2) empower teams through shared responsibility and increased collaboration, and (3) provide business value through faster feedback, consistent processes, and lower costs. While initial costs may increase for training and new tools, CD can ultimately shift costs from releases to other activities and deliver software faster. The document provides a sample deployment pipeline and maturity model, and discusses managing expectations for change when adopting CD practices.
Define Phase Roadmap (Level 3) with Matt Hansen at StatStuff
A detailed roadmap through the Define phase of the DMAIC methodology that navigates the user through the various tools and concepts for leading a Six Sigma project.
Tyrone Mitchell resume update
Tyrone Mitchell is seeking a management consultant position where he can utilize his over 8 years of experience in operations, program management, analysis, team building and strategic planning. He has a Master's degree in Management Information Systems and a Bachelor's degree in Business Management. Mitchell has extensive experience managing IT projects and teams in both the private and public sectors. He currently works as a Lead IT Professor and Cisco Certified Academy Instructor where he teaches various IT courses and certifications.
Enterprise DevOps, Sergey Baranov @ AgileKitchen
This document discusses implementing DevOps practices in an enterprise environment. Some key challenges with enterprise environments include monolithic systems, static environments, lengthy approval gates, and waterfall processes that are manual and error-prone. The document proposes adopting practices like infrastructure as code, continuous delivery pipelines, automated policies, and breaking down knowledge silos. It suggests roles like Dev and Ops teams, reliability engineers, process masters, and service masters. The goal is to maximize business outcomes by increasing speed, sales, and profitability while minimizing costs. The document outlines processes for business strategy, marketing, administration, planning, requirements, development, deployment, operations, customer service, and end of life. It emphasizes that DevOps is a process of continuous improvement
Failure elimination made_simple_article_1_bk
Preventive maintenance programs that rely solely on time-based tasks are often ineffective and result in high equipment failure rates. Research shows over 80% of failures are not related to age or use. To improve reliability, the author migrated to a proactive approach focusing on asset health monitoring to determine maintenance needs. This approach identifies specific failure modes and uses predictive technologies to catch issues early. The result is significantly reduced failures and improved reliability, availability, and cost savings. Sharing successes from pilot programs encourages management support to roll out the approach for all critical assets.
Ford
The 8D problem solving process is a structured approach to continuously improve quality that was popularized by Ford Motor Company. It consists of 8 disciplines: 1) assemble a cross-functional team, 2) define the problem, 3) implement interim containment actions, 4) identify and verify the root cause, 5) choose and verify permanent corrective actions, 6) implement and validate the corrective actions, 7) prevent recurrence, and 8) recognize the efforts of the team. The process aims to eliminate root causes and prevent their reoccurrences.
More Related Content
What's hot
teamwork board.3.6.2014 final
This document describes the implementation of TEAMwork boards in the pediatric intensive care unit (PICU) at a children's hospital. The TEAMwork boards were developed to foster frequent problem solving and timely resolution of issues using a visual tool with red, yellow, and green sections. An example problem around critical medication IV drips was presented, showing the current state challenges and proposed future state improvements. Survey results found the boards had a positive impact and staff felt their ideas were considered. The boards promoted continuous improvement and engagement. Keys to their success included encouraging idea submission and feedback, and recognizing contributions.
Compiling Operational Definitions with Matt Hansen at StatStuff
Operational definitions are lists of definitions for key terms and acronyms used in a particular business area or project. They help unify discussion for teams, prevent confusion, and allow new people to quickly understand processes. To compile operational definitions, listen for unique terms used by the team, ask subject matter experts for definitions, and update the list throughout the project. While not required for small projects, operational definitions are especially helpful for newcomers to an area. Definitions can be included as an appendix or tracked separately and shared with team members.
Documenting a New Process with SOPs
A review of the necessity and how to build standard operating procedures (SOPs) when making changes to a process.
Problem Resolution Using DMAIC with Matt Hansen at StatStuff
A review of how the DMAIC methodology follows the typical steps we follow when trying to resolve a problem.
Erp 20090521
The white paper discusses best practices for implementing an ERP system. It recommends (1) understanding the strategic importance of the implementation process, (2) building an appropriate implementation team of mid-level managers, and (3) setting a realistic plan and timeline supported by backfilling employee responsibilities. Straying from proven implementation methods risks failure and increased costs to fix issues later.
Managing Test Environments
Test environments are important for project success and require upfront organization and proactive management to minimize downtime. Ensuring test environments are stable, maintainable, accurate and accessible can save significant costs by reducing defects, maintaining project schedules, and maximizing development and testing time. Key questions to address include what the environment will be used for, its technical structure, who will access it, and how many environments are needed to minimize downtime.
The case for continuous delivery
The document discusses the benefits of adopting continuous delivery (CD) principles for software development. It outlines how CD can (1) create a repeatable, reliable release process that automates tasks, (2) empower teams through shared responsibility and increased collaboration, and (3) provide business value through faster feedback, consistent processes, and lower costs. While initial costs may increase for training and new tools, CD can ultimately shift costs from releases to other activities and deliver software faster. The document provides a sample deployment pipeline and maturity model, and discusses managing expectations for change when adopting CD practices.
Define Phase Roadmap (Level 3) with Matt Hansen at StatStuff
A detailed roadmap through the Define phase of the DMAIC methodology that navigates the user through the various tools and concepts for leading a Six Sigma project.
Tyrone Mitchell resume update
Tyrone Mitchell is seeking a management consultant position where he can utilize his over 8 years of experience in operations, program management, analysis, team building and strategic planning. He has a Master's degree in Management Information Systems and a Bachelor's degree in Business Management. Mitchell has extensive experience managing IT projects and teams in both the private and public sectors. He currently works as a Lead IT Professor and Cisco Certified Academy Instructor where he teaches various IT courses and certifications.
Enterprise DevOps, Sergey Baranov @ AgileKitchen
This document discusses implementing DevOps practices in an enterprise environment. Some key challenges with enterprise environments include monolithic systems, static environments, lengthy approval gates, and waterfall processes that are manual and error-prone. The document proposes adopting practices like infrastructure as code, continuous delivery pipelines, automated policies, and breaking down knowledge silos. It suggests roles like Dev and Ops teams, reliability engineers, process masters, and service masters. The goal is to maximize business outcomes by increasing speed, sales, and profitability while minimizing costs. The document outlines processes for business strategy, marketing, administration, planning, requirements, development, deployment, operations, customer service, and end of life. It emphasizes that DevOps is a process of continuous improvement
Failure elimination made_simple_article_1_bk
Preventive maintenance programs that rely solely on time-based tasks are often ineffective and result in high equipment failure rates. Research shows over 80% of failures are not related to age or use. To improve reliability, the author migrated to a proactive approach focusing on asset health monitoring to determine maintenance needs. This approach identifies specific failure modes and uses predictive technologies to catch issues early. The result is significantly reduced failures and improved reliability, availability, and cost savings. Sharing successes from pilot programs encourages management support to roll out the approach for all critical assets.
Ford
The 8D problem solving process is a structured approach to continuously improve quality that was popularized by Ford Motor Company. It consists of 8 disciplines: 1) assemble a cross-functional team, 2) define the problem, 3) implement interim containment actions, 4) identify and verify the root cause, 5) choose and verify permanent corrective actions, 6) implement and validate the corrective actions, 7) prevent recurrence, and 8) recognize the efforts of the team. The process aims to eliminate root causes and prevent their reoccurrences.
What's hot (12)
Compiling Operational Definitions with Matt Hansen at StatStuff
Compiling Operational Definitions with Matt Hansen at StatStuff
Problem Resolution Using DMAIC with Matt Hansen at StatStuff
Problem Resolution Using DMAIC with Matt Hansen at StatStuff
Define Phase Roadmap (Level 3) with Matt Hansen at StatStuff
Define Phase Roadmap (Level 3) with Matt Hansen at StatStuff
Certificate of Achievement Stuart Westbrook Schneider Electric Data Center Certified Associate Exam
- 1. Certificate of Achievement This Certificate is Awarded to: For the successful completion of: Serial Number Susan Hartman, Manager, Global Customer Education Data Center Certified Associate Exam Associates possess the basic knowledge necessary to participate on teams that design or upgrade the critical physical layer of the Data Center. Date 25 Sep 2015714341e1834bf40ec7a5cecaa36d6fee Stuart Westbrook Powered by TCPDF (www.tcpdf.org)