FACEBOOK

BUSINESS PROCESS ASSESSMENT Facebook Prepared for Prepared by FACEBOOK, INC Autodesk Shaun Selha Kent Jaeger QA/QC Program Manager, Infrastructure Industry Sales Executive Construction Management [email protected] [email protected]

TABLE OF CONTENTS TABLE OF CONTENTS BPA SUMMARY DESIGN COLLABORATION MODEL COORDINATION Overview VDC Plan - PREPARE BIM 360 Glue - SHARE Navisworks - COLLABORATE BIMTrack - COORDINATE Cyclone - CAPTURE ReCap - CONFIRM Summary FIELD EXECUTION BIM 360 Field Execution Automated Reporting Custom Filters Equipment Categories and Types BIM 360 Plan Location breakdown structure Work breakdown structure Inspection workflow CLOSEOUT / TURNOVER Equipment Properties Import Equipment Sets From Model Move Properties from Original Equipment Sets to Set Tied to Model Export Properties to Revit Model Equipment Mapping to Separate Field Projects Large Model Viewer to Existing FM System Or Full Export to BIM 360 Ops Facebook WORKFLOW Overall

BPA SUMMARY FACEBOOK, INC is a social media and social networking web service company based in California. Its website was launched by Mark Zuckerberg, and others on February 4, 2004. Facebook is building a $1 billion data center in eastern Henrico County, just a few miles east of the Richmond International Airport. DPR Construction has been chosen as the general contractor for the nearly 1 million-square-foot facility. DPR is known for its portfolio of data center, medical and corporate campus projects. It has previously been tapped at least four times by Facebook to construct similar data centers in North Carolina, Oregon, Sweden, and its latest project in Fort Worth, Texas. Facebook and DPR has worked closely to develop its team, processes and workflows. Autodesk committed to providing a four step Business Process Assessment. This BPA will provide a better understanding of collaboration efforts, team communication and alignments. As well as a road map for greater project execution. AREAS OF REVIEW We have reviewed and summarized the results of our findings into four areas. Design Collaboration Model Coordination Field Execution Turnover In each area, we have noted workflows that we thought were on-target and items or workflows that are potential areas for additional value-add.

DESIGN COLLABORATION Facebook's design process was not a major focus of the BPA, but nonetheless holds potential to streamline communication and coordinate design intent. The current process includes a handover of the design model at 100% ConDocs to the GC/Subtrades to further detail/coordinate. This transition currently occurs offline in isolated data environments. Using BIM 360 Design, the process can be contained under one project environment allowing easier design review, change management (identification), and communication. Utilizing the approval workflow models can be approved to a specific model version to transition ownership. Subtrades can then reuse or reference design models as they move forward at greater LOD.

Value Description Design Review Design process reviewed by Owner, GC, subs to alieviate downstream issues. Vice versa during coordination (design team aware of modifications). First person Versioning + Change \"pin drop\" visualization to gain full context of relationships within space. Management Approval Design iteration and change management is captured through versioning/package FM Data sharing of model updates. Compare changes allows visualization of iterations on 2D Global Design Standard sheet or 3D view w/ color overlay to understand modifications between versions. Handover procedures from 100% CD to Construction to FM can be applied to specific model version (2D sheets + 3D Model Views included). At turnover, appropriate assets can have properties retrieved from Field Execution phases. Model becomes data rich and maintainable throughout facility life-cycle. Centralizing the models enables Facebook's intent to create a design standard. Future projects begin further along with coordinated design and best practices included.

MODEL COORDINATION Overview DPR Construction along with Facebook has developed a six part process utilizing Building Information Modeling with Virtual Design and Construction workflows to deliver collaborative and coordinated project. This process begins with a VDC plan and leverages a series of software solution to share, collaborate, coordinate, capture and confirm information throughout the project. VDC Plan - PREPARE The project team uses a detailed BIM Execution Plan that outlines the needs for the VDC team in connection with the Facebook projects requirements. BEST PRACTICES IN PLACE DESCRIPTION BIM Execution Plan Active use and continual dialog of the BIM Execution Plan through out the model coordination process.

BIM 360 Glue - SHARE The DPR and Facebook team utilizes BIM 360 Glue as a cloud storage solutions to aggregate project team models and link these models into Navisworks for collaboration purposes. However, many downstream benefit could be had by expanding the use of BIM 360 Glue further. BEST PRACTICES IN PLACE DESCRIPTION Cloud Storage Anywhere, anytime access and unlimited cloud storage of over Model Aggrigation 50 plus project model file types. Naming Conventions One-click publishing of models from Revit, AutoCAD and Equipment Sets with BIM 360 Field Navisworks for fast and efficient model uploads. Project teams should upload model as one would create selection sets in Navisworks. Increasing the ease of using both Glue and Navisworks clash tools. Equipment Sets allows you to use Glue model data for BIM 360 Field Integration. Navisworks - COLLABORATE The project team uses Navisworks to manage the collaboration process. Specific features used for this process include Sets for organization, Clash detective for tests and results, Viewpoints for sharing the clash results. BEST PRACTICES IN PLACE DESCRIPTION Selection and Search Sets You can and use sets of like objects. This makes it easier to review and analyze your model. Clash Detective The Clash Detective enables identification, inspection, and Viewpoints reporting of clashes in a project model. Viewpoints are snapshots of the model as it is displayed. Allowing for a clash review audit trail.

BIMTrack - COORDINATE Independent of the Facebook baseline requirements the DPR team utilizes a product BIMTrack, a web-based point solution to empower better coordination workflows. Including Clash coordination issue tracking and reporting. BEST PRACTICES IN PLACE DESCRIPTION Clash Issue Tracking The system builds a database of clash issues, assigns clashes to Clash Reporting teams and sets priorities. Unified Issue Management DPR creates a series of reports and dashboards monitor clash resolution and progress. Clash issue tracking system is disconnected from Facebooks issue management system, BIM 360 Field. Cyclone - CAPTURE The DPR and Facebook team utilizes reality capture processes to verify and validate existing conditions, construction progress and as-built conditions. BEST PRACTICES IN PLACE DESCRIPTION Scanning Various forms of scanning processes are implemented and Scheduling utilized through out the project team. Scan Registration Project team is utilizing BIM 360 Plan for better scanning task scheduling. Implemented automation to assist the registration process.

ReCap - CONFIRM Once the scanning processes are completed the team uses software solution ReCap and Navisworks to confirm the installation was installed as design and coordinated. BEST PRACTICES IN PLACE DESCRIPTION Installation Verification Use of scan data for as-built conditions and quality assurance. Summary The DPR and Facebook team has implemented a sophisticated Model Coordination process involving several different software solutions. The result is a collaborative coordination progression from clash detection to as- built model deliverables. To help improve this process the team could implement a new naming convention within the BIM execution plan that would enable the participating team members to uploaded models as the DPR coordinator organizes selection sets in Navisworks. This would ease the need for heavy set creation in Navisworks and allow all team members to the ability to utilize BIM 360 Glue as a more efficient, iterative collaboration tool. Leveraging Equipment Sets in BIM 360 Glue provides pass-through for model-based parametric information for use in the field for equipment tracking as well as handover to operation. Increasing the efficiency of populated FM data throughout the project lifecycle. DRP currently uses a system for categorizing clashes and issue tracking. This system stores its clash issues into a disconnected database. Facebook uses BIM 360 Field as the projects QA/QC and issues management system during construction. It is our suggestion a simple import and export of higher level clash issues, issue requiring field operation input also be copied into BIM 360 Field, to maintain the repository for record keeping.

FIELD EXECUTION BIM 360 Field Execution The equipment is being well tracked in Field, checklists are being completed at a rapid rate, and there is an impressive set of metrics being used to give feedback to the team. FM has given their input on the properties being tracked but for the complexity of the equipment the properties listed seems light compared to that of other owners. One of the biggest gaps/asks we discovered is related to bringing the model into the equipment tracking and ensuring that FM has a model they can accept with the data they need upon, or even before, turnover. BEST PRACTICES IN PLACE DESCRIPTION Checklisting Checklists are being used extensively and are well tracked. Metrics Metrics are well thought out and tracked using APIs. Reporting Reporting is Extensive. Reporting should be scheduled to run automatically to the right individuals when possible. Auto emailed Issue, Checklist, and Equipment Filtering csv's could be setup to integrate directly with PowerBI. Equipment Categories Filtering could be more robust to provide users data that is most useful, and reducing syncing - saving time and room on iPads. Looking at the Solutions matrix and what is in the RVA-1 project. You may consider adding additional categories to efficiently enter, filter and report on the data.

AUTOMATED REPORTING Upon review of the project in BIM 360 Field, it is recommended that additional filters be added to both this project and the project template. Ensure that reporting and tie in's to Power BI are as automated as possible. Reports in BIM 360 can be scheduled to run daily, weekly, or on the first of the month. Most are available as csv or pdfs and they come from a consistent email with a consistent title making it easy to create rules. These automated emails out of BIM 360 Field could be ran through a rule and Microsoft Flow in saving the attachment which is then linked to Power BI. You could also call the PowerBI API with Flow to automate the refresh. Remember that you can schedule company wide csv reports for issues and checklists, filter it by project, and do all projects under Facebook's account in one step. CUSTOM FILTERS Issue and checklist filters can assist different roles and responsibilities on the project by ensuring users have what they need efficiently both in time and device memory. For example, having a filter for safety specific items ensures that those managing safety can focus on their issues and checklists. Though safety is not tracked in this project, this same example can be used for multiple roles and focus items. More info on customizing filters can be found here. As data increases through the duration of the project, these more specific filters also assist with managing the amount of data being downloaded to the iPads. The team may even consider either deleting or limiting the access to \"All Issues\" or \"All Checklists\" filters to specific user types to prevent future issues with memory use on iPads.

Equipment filters have been added for electrical and mechanical equipment. This will assist but the team (and template creator) may consider additional more specific filters such as further breakdown of type of equipment, when the equipment was delivered, status, whether it has open checklists or issues, etc. EQUIPMENT CATEGORIES AND TYPES Another thing that came up on the solutions matrix was \"System identification to all for linking of multiple piece of equipment to the same system (i.e. CHW System has CH, CHWP, CWP, CT, etc.…). Categories on this project seem under-utilized. With only 5 in place there are over 50 types of equipment per category. I would use the examples listed above to add categories or I would split it by trade. For example, in mechanical you will have foreman split by plumbing and air and maybe even further on a job of this magnitude. Consider how work is divided and tracked.

A couple additional equipment related notes. Consider making changes like adding categories and custom properties that are specific per type on the template prior to copying another project as these changes will then roll over to the next project. And categories can be a consideration or variable by which you create a filter.

BIM 360 Plan The project has a well thought out plan with great Contractor involvement. Suggestions revolve around driving consistency across projects and modifying the inspection workflow to ensure that, as the number inspections increase, it is clear who is going to be performing the inspection and ensuring they are not overbooked. This will further ensure that inspections can be completed as requested, with the right resources, ensuring fieldwork can proceed in a timely manner with proper inspections complete. BEST PRACTICES IN PLACE DESCRIPTION Inspection Tracking Meeting every day is ensuring with the speed of the project that everyone is on top of their inspections and committing to their Contractor Involvement activities. We have suggested small tweaks to ensure that all inspections are being closed out. Project has great input and use by the General Contractor and Subcontractors. Ensuring subcontractors maintain scheduling inspections as required by the Project Documents will assist in ensuring the inspections are properly scheduled without overlap allowing work to proceed as intended.

Team Collaboration The project showed great team collaboration and the LBS, WBS Standardization communication using Plan was aspiring. Inspection Workflow In the efforts to drive consistency, Facebook should consider providing common Location Breakdown, common Task Naming, and a typical Work Breakdown Structure to use as the Project Specific Setup (PSS). We suggest making a few simple adjustments to the Inspection Workflow below. In the efforts to drive consistency, Facebook should consider providing common Location Breakdown, common Task Naming, and a typical Work Breakdown Structure to use as the Project Specific Setup (PSS). If the project is non-typical, the Facebook Project Team should work with the General Contractor's Superintendent to develop the PSS using the Facebook Project Naming Structure. LOCATION BREAKDOWN STRUCTURE We suggest developing a Location Breakdown Structure that can be used over all projects and moving Equipment into the LBS. This will help track the delivery, installation, start up and commissioning of the equipment. WORK BREAKDOWN STRUCTURE Consider using WBS for Inspections Types and Deliveries Types. This will make it easier to identify the type of inspection being requested because you will be able to sort by inspection type and responsible inspector.

INSPECTION WORKFLOW The inspection workflow is well thought out and has great participation. We suggest making a few simple adjustments to create an Inspection Workflow that uses a Customer-Supplier process. Step 1 Create an Task Activity Committing to be ready 48 hours in advance of needing the Inspection. Must have - Status, Description, Finish Date, Location Step 2 The Requesting Contractor will create an Inspection Activity requesting an inspection from the responsible inspector. Must Have - Date, Time/Who Requested the inspection, Location, Inspection Type (WBS) and Responsible Inspector. Very Important to link the Previous Handoffs.

Step 3 By 12pm the day before the inspection is needed, the Requesting Contractor should change his activity status from committed to complete letting the responsible inspector know they are ready. Step 4 By 3pm the day before the inspection is needed, the Responsible Inspector should change his status

from Open to Committed acknowledging he is available for the time to perform the inspection. Step 5 After the inspection has been performed and Passed, the Responsible Inspector should change is status to complete

CLOSEOUT/TURNOVER BEST PRACTICES IN PLACE DESCRIPTION Guiding Documentation The first big step towards having an efficient turn-over process is a Guiding Document detailing expectations from FacOps Input on Properties the contractor. FacOps has given the team a list of equipment properties that have been added to the project and template. Turnover Approvals The same turnover process listed above in Design Extent of Equipment Properties Collaboration could be executed during Turnover to ensure that the process is smooth, efficient, and results in a correct master model. Equipment Properties specific to FacOps are lighter than we typically find for customers of this size and sophistication. Export of Properties to Model We have included a workflow on bringing in the Revit model to link equipment and populate the model with properties for FM. This model and data can be exported directly to BIM360 Ops or you could use the large model viewer to tie it back to Facebook's current FM system. Follow-Up Required on dividing up the model and equipment.

Equipment Properties Prior to having a fully coordinated model, there is a need to begin tracking checklists, issues, and other QAQC and commissioning workflows. Be sure to follow these key points when setting up the equipment. Ensure custom properties in template and project are up to date. Use sample template to import equipment. This equipment could come from the equipment schedule. Import the template. Proceed as doing now throughout the project doing checklists, issues, and adding equipment properties. Import Equipment Sets From Model Equipment sets will be mapped to the coordinated model that hosts all equipment. This links the equipment to the model and will provide the transfer of the data entered in Field to the model. This workflow is as designed and information on how to complete this step can be found here.

We are suggesting that this be done at the end of the project but could be done earlier if the model contains the needed equipment and the benefits exist.

Move Properties from Original Equipment Sets to Set Tied to Model This video shows how the equipment properties that have been entered in early on in the project (before their is a fully coordinated model can be moved to the equipment that has been mapped to the Revit model. Though the video shows all properties moving over, commissioning based properties that are not needed for FacOps can be left out of the transfer. Note: Checklists and issues won't move over. However, the video also shows how the new equipment brought in from the model can be tied to the existing equipment that holds the issues and checklists. The older equipment can be filtered to no longer show in the equipment list but yet is still accessible via the linked equipment. Note: This linking can also be used for equipment and their subcomponents as requested on the Solution Comparison Matrix.

Export Properties to Revit Model This video shows how equipment properties that have been entered in during construction in BIM 360 Field can be pulled into a Revit model that is published to Docs.

Equipment Mapping to Separate Field Projects This video shows how to map equipment from one BIM 360 Glue project to two (or possibly more) Field projects.

Large Model Viewer to Existing FM System This Revit Model will be stored in BIM 360 Docs as the single source of truth for the handover model. This can then be progressed in Docs through the Handover approval process using the Review feature. This model, which can now be maintained during updates and smaller projects, can be pulled into and kept updated in Facebook's existing FM system using the LMV API. Or Full Export to BIM 360 Ops Equipment Properties could also go to BIM 360 Ops. Just enter the code in Field for the appropriate BIM 360 Ops account and all properties, attachments, and equipment linked to the model will move over. Here is a video showing this step.

Facebook WORKFLOW Overall