system integrator best practices

20
Presentation for Best Practices for Systems Integrators… Its all about Project Management 3/13/2013 Presenter: Ken Kutchek VP Operations

Upload: marcia-gadbois

Post on 14-Nov-2014

1.894 views

Category:

Documents


2 download

DESCRIPTION

Ken Kutchek of Patti Engineering offers best practices for project management for systems integrators.

TRANSCRIPT

Page 1: System Integrator Best Practices

Presentation for

Best Practices for Systems Integrators…

Its all about Project Management

3/13/2013Presenter:Ken KutchekVP Operations

Page 2: System Integrator Best Practices

Patti Engineering Overview

• Control System Integrator• Established in 1991• Offices in Detroit MI and Austin TX• 47 Employees, 32 Engineers, 3 PEs (lic. in MI and TX)• InduSoft Certified Integrator • Experience with multiple H/W & S/W Products• We are NOT a “Me Too” Company• CSIA Certified (Control System Integrator Association)• Control Engineering 2013 System Integrator of the Year

Page 3: System Integrator Best Practices

Key Markets

• Automotive • Distribution (Material Handling & Sortation)• Factory Automation / Robotics• Process Control• MES

Page 4: System Integrator Best Practices

CSIA Certification

Integrator complies with CSIA’s Best Practices

• General Management• Human Resources Management• Financial Management• Marketing and Sales Management• Project Management• System Development Lifecycle• Quality Assurance Management• Service and Support

An audit is required every three years

Reduce the project risk and increase the probability of success!

Page 5: System Integrator Best Practices

Project Management Best Practices

• Project Initiation– Project Management Plan

– Choosing team members

– Internal kickoff meeting  

– Customer kickoff meeting

• Development– Functional Specification

– Software Design/Development

– Factory Acceptance Test (FAT)

– Changes / Additions

• Installation– Install / Testing / Verification

– Training / User Manual

• Completion– Project Closeout

– Project Review / Evaluation

Page 6: System Integrator Best Practices

Project Management Plan

A goal without a plan… is a wish !!

Page 7: System Integrator Best Practices

Project Management Plan

Plan of Execution– Scope of work / Requirements

– Hardware / Software technologies

– Team

– Training

– Budget

– Schedule

– Risks (technology, staffing, schedule, requirements, startup issues)

– Communications

– Quality– Closure

Page 8: System Integrator Best Practices

Project Management Plan

“A little pessimism is just good planning”

Page 9: System Integrator Best Practices

Choosing Project Team

Choose a Lead Engineer/Project Manager and project team based the following items :

– Customer – industry, their plant/operation

– Customer - specific application

– Technologies being used (PLC’s, Servers, databases)

– Project size– Schedule

Page 10: System Integrator Best Practices

Internal Kickoff Meeting

Salesperson, Engineering Manager, Lead Engineer/Project Manager, and engineering team meet to review and discuss the project.

– Customer, plant/operation, specific application

– Proposal (Scope of Work, Customer Responsibilities)

– Hardware / software requirements

– Project team members and responsibilities

– Budgeted hours

– Schedule

– Project risks and expectations – schedule, software development, installation, testing)

Meeting minutes taken and distributed afterward

Page 11: System Integrator Best Practices

Customer Kickoff Meeting

Lead Engineer/Project Manager and Engineering Manager meet with the Customer to review and discuss the project.

– Project team members (Customer and Integrator)

– Scope of work

– Requirements

– Hardware / software requirements

– Schedule

– Testing/Verification

– Risks

Meeting minutes taken and distributed afterward

Page 12: System Integrator Best Practices

Functional Specification

Purpose - Thoroughly define / explain function, features, and operation

Outcome - Understanding and agreement between integrator and customer

• Customer Requirements

• System Requirements

• System Overview

• Screen Layout / Content

• All operator interactions with the system

• All interfaces with other systems or equipment

• Included Reports

• System administration, security

• System limitations

• Customer responsibilities

• Review Functional Spec with customer • Customer must sign off

Page 13: System Integrator Best Practices

Software Design / Development

• Functional Spec becomes road map to design

• Open Issues List - Log all questions, required information, clarifications

assign responsibilities

• Task List - Breakdown the Software design into individual tasks

assign responsibilities, set expected completion

• User Friendly / Intuitive Design

• (KISS) Keep It Simple Stupid

• Design Standards

• Design Reviews

Page 14: System Integrator Best Practices

Factory Acceptance Test (FAT)

Thorough and systematic testing/verification is critical !!

•Provides formal testing to verify the functionality and operation

•It is really just one big checklist

•Deserves same attention as requirements and designs.

•Begin developing early….as soon as the requirements are approved.

•Some method (e.g. matrix) should be used to ensure all requirements have been mapped to one or more test protocols.

•Start using FAT during office testing, finish during onsite testing

•Customer should be involved

Page 15: System Integrator Best Practices

Changes / Additions

Scope Creep is bad for the Integrator … and the Customer too.

Scope Creep is the kind of thing that accumulates so slowly and subtly that you don't realize it's happening until it's too late.

•Design change requests. Is it within the scope ?

•Change Orders

•When a Change Order is accepted by the customer

– Update Project Management Plan

– Update Functional Spec

– Update Factory Acceptance Test

Page 16: System Integrator Best Practices

Install / Testing / Verification

Thorough and systematic testing/verification is critical !!

•Complete the Factory Acceptance Test•Log all issues on Project Task List •Provide “Stand-by support” for the agreed amount of time•Complete all Task List items•Remote access for future support and changes

Any item not tested or resolved onsite can cost 10x when addressed as a warranty issue later

Page 17: System Integrator Best Practices

Training / User Manual

Critical to “perceived” system functionality, customer satisfaction

– System Overview

– System Operation

– Start-up and Shutdown procedures

– Operator interaction procedures

– Supervisor interaction procedures

– Administrator interaction procedures

– Explain each type of screen

– List and explain all Fault Messages and Status Messages

– Troubleshooting Guide

Page 18: System Integrator Best Practices

Project Completion

Closeout is critical to wrapping up project and getting buyoff.

Project Completion Checklist - thorough and organized completion

Verify the following items are complete…• Customer is satisfied

• All deliverables have been given to customer

• All Open Issues List Items resolved

• All Task List Items complete

• Factory Acceptance Test complete

• Final software has been backed-up

Page 19: System Integrator Best Practices

Project Review / Evaluation

•What went well ?•What did go well ?

•Rate and Comment on the following– Customer Satisfaction

– Initiation

– Development

– Installation/Testing

– Project management

– Schedule

– Budget

– Closeout

– Proposal Evaluation

Page 20: System Integrator Best Practices

Thank You !

IndusoftBest Practices for Systems Integrators…

Its all about Project Management