BPA Sample Document - V9

Sample DocumentTechnical Process AssessmentTuesday, March 27, 2017

Business Process Assessment FormAUTODESK AND PARTNER INFORMATIONDate: 3.28.2017 Autodesk Rep: Michael Counte Autodesk TS: AP Percowyzc TBD Reseller AE: TBDReseller: TBD Reseller Rep:COMPANY INFORMATIONCompany Name: RevCore Construction Location: Detroit, MI Primary Contact: Brandon LaCourciere Industry: Mech. Sub - Contractor Opportunity ID: 00012345Website: www.RevCore.comPROCESS PRE-PLANPrimary Business UnitsObjective /Goals Should be summary Statements, Link to notes for complex responsesTeam Name: Mechanical Team Contact: David MarksObjective/Goals: Improve external Team Collaboration Eliminate Version Mistakes (Out of Date Information)Notes: Pre-Meeting One Note – Mechanical TeamTeam Name: VDC Group Contact: Karen Jacobs Allow Non-Navisworks users to visualize Clashes / IssuesObjective/Goals: Accelerate the Clash Resolution ProcessNotes Pre-Meeting One Note – VDC GroupTeam Name: IT Department Contact: AL CulbersonObjective/Goals: Unified platform that manages data from secure cloud Active Directory (SSO)Notes: Pre-Meeting One Note – IT DepartmentTeam Name: Executive Management Contact: Ben HarperObjective/Goals: Reduction in Point Solutions (PlanGrid, BlueBeam, etc.) Workload Management SolutionNotes: Pre-Meeting One Note – Executive ManagementTeam Name: Field Commissioning Team Contact: Mike HilbertObjective/Goals: Real-Time Sync with Design Staff Integration with Layout SolutionNotes: Pre-Meeting One Note – Field Commissioning Team Contact:1Team Name:Objective/Goals:Notes:Team Name: Contact:Objective/Goals:Notes: AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 1

Business Process Assessment Discovery ResultsProcess Assessment OverviewTable of Contents Objective /Goals Should be summary Statements, Link to notes for complex responses Section 1 Project Setup Pg. 3 RevCore Existing Workflow: Project Setup Pg. 4 Autodesk Workflow: Project Setup Pg. 5 Assessment Data: Project Setup Pg. 6 Workflow Summary: Project Setup Section 2 Project Configuration Pg. 7 RevCore Existing Workflow: Project Configuration Pg. 8 Autodesk Workflow: Project Configuration Pg. 9 Assessment Data: Project Configuration Pg. 10 Workflow Summary: Project Configuration Section 3 Project Communication Pg. 11 RevCore Existing Workflow: Project Communication Pg. 12 Autodesk Workflow: Project Communication Pg. 13 Assessment Data: Project Communication Pg. 14 Workflow Summary: Project Communication Section 5 Summary Pg. 19 RevCore BPA SummaryAUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 2

Existing Workflow: Project SetupPros Robust custom markup tags Cons  Opportunity to embed properties into Revit  No connection from estimating to design  Geometry  Drawing sets must be manually uploaded into Ability to customize connection from 3rd  party solutions data store  Manual Process for updating data with Oracle provides single source of truth for all data contract documents (documents are lost, misplaced, etc)  No way to directly tie revised Revit models to updated/versioned sheet sets in the field  No centralized project administration (for all solutions) AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 3

Autodesk Workflow: Project SetupPros Issue Management workflows aligned to Cons equipment commissioning processes   Breadth of custom markup tools and stamps  Module for aligning field based tasks to  Company XYZ workflows  No shared location structure  Customizable reports and dashboard for field  No centralized project administration (for all  activities solutions) Daily report module allowing field foreman  No method to track assembly status to capture safety, environmental, and labor details for each day on the jobsite  No base reporting on field productivity Markup on 2D sheets and 3D Models AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 4

Assessment Data: Project Setups the design shared across disciplines?Workflow ContributorsTeam Name: Mechanical Team Contact: David MarksComments: “We could leverage these maps for future On-Boarding.”Team Name: Plumbing Team Contact: Blake LindseyComments: “Sometimes it feels like we are operating like different companies.”Team Name: Autodesk Contact: Dustin GallingerComments: Still waiting for additional data on the Project File SharingTeam Name: Autodesk Contact: AP PercowyczComments:Supporting Data: Project Setups the design shared across disciplines?Project Assets On a typical project, how often is the design shared across disciplines? Bi-Weekly Weekly Monthly Rarely Never AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 5

Workflow Summary: Project Setup Autodesk Includes YES / NO / PartialWorkflow Comparison YES / NO / Partial YES / NO / Partial<Client Name> Essential Pros Autodesk Resolves  Robust custom markup tags YES / NO / Partial  Ability to customize connection to Egnyte YES / NO / Partial  Ability to customize connection from 3rd party solutions YES / NO / Partial <Client Name> Includes<Client Name> Primary Cons YES / NO / Partial  No connection from estimating to design  No method to track assembly status YES / NO / Partial  No localized backup YES / NO / PartialAutodesk Primary Pros <Client Name> Includes  Markup on 2D sheets and 3D Models YES / NO / Partial  Issue Management workflows aligned to equipment commissioning YES / NO / Partial processes YES / NO / Partial  Customizable reports and dashboard for field activitiesAutodesk Primary Cons  Breadth of custom markup tools and stamps  No Android support  No shared location structureProject Setup Product Seats Training AmountExisting Workflow 30% BIM 360 Field 45 YES $$$ 16 NO $$$Autodesk Workflow BIM 360 Team 6 YES $$$ 80% Collaboration For Revit 9 YES $$$Comments: 112 YES $$$ Recap AEC CollectionsLinks 6http://www.autodesk.comhttp://learnbim360.autodesk.com AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE

Existing Workflow: Project Configuration SD to CDPros External Teams not required to learn adsk Cons Design Build learn Internal Processes  Design Team prefers SketchUp Modeling  Significant time required to develop Project Existing Servers Manage Data FTP Sites and Invite Partners.  Corporate Standards In-Place  Ability to Track Project Status  Incoming Talent Prefers Revit   Remote Access requires VPN   Difficult to manage standards across Silos  Data Tracking based off Manual Info  Changes Require Two Model Adjustments  Version Control is very Difficult  Customer Presentations take significant time and the information is difficult to share. AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 7

Autodesk Workflow: Project Configuration SD to CDPros Promote adsk Design Build as BIM Enabled Cons Appeal to Larger Candidate base for Hiring  Access Data from any Location. No FTP Site  Significant Training Required  required or expensive hardware  Additional Staffing Required  Corporate Stand. embedded in Application  New Standards required for Remote access Change Management is trackable in 2D & 3D  Version control is a Core feature of Docs that will impact External Partners  Customers have access to User Friendly 3D  Data Lives in the Cloud  Models based of Published Progress.  Design Team needs to divest from SKP.  Document Change is Bi-Directional  AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 8

Assessment Data: Project Setups the design shared across disciplines?Workflow ContributorsTeam Name: Process Piping Contact: David GarretComments: “We need to reduce the Siloed Workflows”Team Name: Executive Management Contact: Karen DavidsonComments: “I need on-demand visibility of the project Data”Team Name: Autodesk Contact: AP PercowyczComments:Team Name: Contact:Comments:Supporting Data: Project Setups the design shared across disciplines?Project Assets With interdisciplinary projects in mind, how would you describe adsk typical project structure? adsk Design | Build has an integrated design process with well-structured design meetings, project teams with clearly defined roles and responsibilities, and scheduled coordination efforts. adsk Design | Build has project-by-project processes and standards that vary depending on who is running the project and how tight of a deadline there is. adsk Design | Build tk1sc has no project organization structure AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 9

Workflow Summary: Project Setup Autodesk Includes YES / NO / PartialWorkflow Comparison YES / NO / Partial YES / NO / Partial<Client Name> Essential Pros Autodesk Resolves  Robust custom markup tags YES / NO / Partial  Ability to customize connection to Egnyte YES / NO / Partial  Ability to customize connection from 3rd party solutions YES / NO / Partial <Client Name> Includes<Client Name> Primary Cons YES / NO / Partial  No connection from estimating to design  No method to track assembly status YES / NO / Partial  No localized backup YES / NO / PartialAutodesk Primary Pros <Client Name> Includes  Markup on 2D sheets and 3D Models YES / NO / Partial  Issue Management workflows aligned to equipment commissioning YES / NO / Partial processes YES / NO / Partial  Customizable reports and dashboard for field activitiesAutodesk Primary Cons  Breadth of custom markup tools and stamps  No Android support  No shared location structureProject Setup Product Seats Training AmountExisting Workflow 50% BIM 360 Field 45 YES $$$ 16 NO $$$Autodesk Workflow BIM 360 Team 6 YES $$$ 90% Collaboration For Revit 9 YES $$$Comments: 112 YES $$$ Recap AEC Collectionshttp://www.autodesk.com 10http://learnbim360.autodesk.com AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE

Existing Workflow: Project CommunicationPros External Teams not required to learn adsk Cons Design Build learn Internal Processes  Design Team prefers SketchUp Modeling  Significant time required to develop Project Existing Servers Manage Data FTP Sites and Invite Partners.  Corporate Standards In-Place  Ability to Track Project Status  Incoming Talent Prefers Revit   Remote Access requires VPN   Difficult to manage standards across Silos  Data Tracking based off Manual Info  Changes Require Two Model Adjustments  Version Control is very Difficult AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 11

Autodesk Workflow: Project CommunicationPros External Teams not required to learn adsk Cons Design Build learn Internal Processes  Design Team prefers SketchUp Modeling  Significant time required to develop Project Existing Servers Manage Data FTP Sites and Invite Partners.  Corporate Standards In-Place  Ability to Track Project Status  Incoming Talent Prefers Revit   Remote Access requires VPN   Difficult to manage standards across Silos  Data Tracking based off Manual Info  Changes Require Two Model Adjustments  Version Control is very Difficult AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 12

Assessment Data: Project Setups the design shared across disciplines?Workflow ContributorsTeam Name: BIM Task Force Contact: Kenny ArnattComments: “We work within Industries that share data among our peers not managers”Team Name: IT Department Contact: AL CulbersonComments: Still look for an Active Directory SolutionTeam Name: AP Percowycz Contact: (459)-000-0000Comments:Team Name: Bugs McGee Contact: (459)-000-0000Comments: Please contact my cell during the week: (888)-455-0000Supporting Data: Project Setups the design shared across disciplines?Project Assets I understand the needs of the other disciplines involved in the project:I receive adequate information from outside consultants to make informed design decisions: AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 13

Workflow Summary: Project Setup Autodesk Includes YES / NO / PartialWorkflow Comparison YES / NO / Partial YES / NO / Partial<Client Name> Essential Pros Autodesk Resolves  Robust custom markup tags YES / NO / Partial  Ability to customize connection to Egnyte YES / NO / Partial  Ability to customize connection from 3rd party solutions YES / NO / Partial <Client Name> Includes<Client Name> Primary Cons YES / NO / Partial  No connection from estimating to design  No method to track assembly status YES / NO / Partial  No localized backup YES / NO / PartialAutodesk Primary Pros <Client Name> Includes  Markup on 2D sheets and 3D Models YES / NO / Partial  Issue Management workflows aligned to equipment commissioning YES / NO / Partial processes YES / NO / Partial  Customizable reports and dashboard for field activitiesAutodesk Primary Cons  Breadth of custom markup tools and stamps  No Android support  No shared location structureProject Setup Product Seats Training AmountExisting Workflow 60% BIM 360 Field 45 YES $$$ 16 NO $$$Autodesk Workflow BIM 360 Team 6 YES $$$ 70% Collaboration For Revit 9 YES $$$Comments: 112 YES $$$ Recap AEC CollectionsLinks 14http://www.autodesk.comhttp://learnbim360.autodesk.com AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE

AUTODESK CONFIDENTIAL – FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE 15