Submission information
Submission Number: 13264
Submission ID: 63728
Submission UUID: 6b1eecdd-5a28-42fb-a4c2-08615ca8b615
Submission URI: /form/vendor-performance-evaluation
Created: Thu, 01/19/2023 - 18:10
Completed: Thu, 01/19/2023 - 18:10
Changed: Thu, 02/09/2023 - 14:49
Remote IP address: (unknown)
Submitted by: admin
Language: English
Is draft: No
Current page: webform_submission_import
Webform: Vendor Performance Evaluation
Locked: Yes
On the plus side:
• Ryan Thady did a great job. He is smart, professional and experienced. His CAD skills were superb. He was one of the best team members we’ve ever had on a VE study.
• Kasi is diligent and very willing to please.
• To learn the process, Benesh brought along Mike Gorman, who is new to the firm. Mike is very knowledgeable in transportation projects, specifically traffic and is working towards his CVS in Value Engineering.
On the minus side:
• Benesch staff is capable of managing engineering work; however, there were serious concerns about facilitation and management of the team during the study. Some of the following ideas may help tighten up the process:
o The team needs to know why they’re there. Explain the purpose of the VE study at the start. What VE is – what VE isn’t.
o Set daily goals. Each day should start with a list of milestones that need to be met at day’s end. Milestones should be detailed and specific – hourly if needed.
o Set rules and constraints – define what is and what is NOT on the table. If conversation slips off topic, put those issues on the parking lot to be dealt with later. Reassess as needed during the study.
o Stay on task and focused.
Bottom line: Each team member has regular work they are NOT doing in order to participate in the VE study. Their time must be productively and efficiently used. This can only be done with good time management and facilitation skills.
• Kasi stepped out of the room to work directly with the MnDOT Bridge Engineer. This was important work, but left the group leaderless. The rest of the team needed clear direction about what to do next. Kasi’s main task was to facilitate – the detail bridge engineering work should have been secondary. This might have been managed with good delegation to one of the other Benesch team members.
• Ideas don’t have to be specific. Focus less on the number of ideas and more on the content of the ideas.
eg, two ideas were:
Re-align T.H. 7 to the south (to build new bridge off-line of existing)
Re-align T.H. 7 to the north (to build new bridge off-line of existing)
Effectively, these are the same idea. Having a large number of ideas is great, but the sheer number adds more work and time later when they must be pared down into recommendations.
• Doug West seldom contributed and appeared to have only one task – prepare the PowerPoint presentation. Unfortunately, his skills as a construction expert were never used and even worse, he seemed to have little knowledge about PowerPoint.
QA/QC Final report
Details matter. The QMP looked great on paper, but was not implemented well. It took several iterations to get the final report error free. Simple things like TH100 appeared as TH10 or TH1000.