Visores BIM visuales que todos puedan entender.
Grabación: https://www.lodplanner.com/planificacion-bim-espanol
Aprenda sobre la planificación fácil de BIM.
¿Qué es LOD?
Cómo crear un alcance BIM.
3. PLanes de ejecución BIM
que todos puedan entender.
PLAN
Episode 1 of 3:
● Plantillas reutilizables de la industria
● Crear PEB en línea
● Reducir administración y aumentar
adopción
5. Seguimiento
3
● Planificación de carta Gant en vivo
● Tablero Kanban con un simple
arrastrar y soltar
Líneas de tiempo más
integradas
6. Visual BIM scopes that even
Dave can understand.
SCOPE
● Everyone can understand the
who, what, when and WHY
● Visual scope agreement
Agenda de hoy:
1. Intro
2. Demos
3. Lo que sigue!
Q&A:
Escríbenos tus
preguntas!
7. BIM
es usado para:Marketing
Gestión de
Activos
Hospitales
Oficinas
Resorts
Residencial
Educación
Centros de datos
Infraesctructura
...
Análisis Estructural
Analisis
Humanos
Análisis solares
Cantidades de obra
Detección de
interferencias
Simulación 4D
Mixed Reality
Realidad Aumentada
Realidad Virtual
Logística
Diseños Detallados
Consecución del
proyecto
(Building Information Modeling)
7
10. +Cómo puede un número de LOD (NDI)
definir todo esto?!?
Geometía
● Simbolica?
● Generica?
● Detallada?
● Fabricación?
Presición
● 100mm / 5”?
● 50mm / 2”?
● 15mm / 5/8”?
● 5mm / 1/4”?
● 1mm / 1/16” ?
Elementos
● Demasiados?
● Muy pocos?
● Brechas en la comunicación?
● Superposició de
información?
Madurez
● Preliminar?
● Propuesto?
● Coordinado?
● As-built?
Propósito
● Cantidades / Estimación de
costos?
● Diseño
● Documentación?
● Coordinatción?
● Gestión de activos?
● VR?
Informacón
● IFC?
● Parametros de Software?
● Especificación de Equipos?
● Manual de propietario?
● Información de garantía?
11. Planeación Autoria Análisis Uso
ClashMEP
Not an exhaustive list
Herramientas de la industria AEC
Las herramientas de gestión de proyectos
tradicionales son ineficientes y
desconectadas
12. Y si hay una plataforma dedicada para esto?
Y si es en línea, con plantillas y es colaborativa?
14. +
● Es en línea y siempre actualizado
● Es visual
● Es colaborativo
● Combina contratos y especificaciones
● Puedes empezar con plantillas
● Está integrada con el módulo de seguimiento
● Es simple y hecha para NUESTRA industria!
● Y...
Y si?
17. +
1. De acuerdo en el “porqué”
2. Alcances de proyecto claramente
definidos
3. Aprovechando plantillas (LEAN)
4. Definiendo cuándo y cuánto
5. La “i” en BIM
6. Asignando quien es responsable
6 Demos: Alcances BIM Simples
de entender
18. ● Propósito del modelo
● Expectativas de modelado
● Alinear metas BIM
● Plan de ejecución BIM (BEP)
De acuerdo en el “porqué”1
19. Demo:
● Fases
● Etapas
● Proyectos entregables
● Usos BIM/Usos del modelo
1 De acuerdo en el “porqué”
20. ● Demasiado = sobre modelado
● Poco Claro = no cumplir con expectativas
Definiendo listas de alcance claros2
21. Demo:
● Biblioteca de elementos
● Arrastrar y soltar
● Estructura de folder
flexible
2 Definiendo listas de alcance claros
22. ● Consumos de tiempo
● Anticuado
● Copiar y pegar aumenta el riesgo
● Resultados inconsistentes
Gestionando plantillas3
24. ● Expectativas desalineadas
● Suposiciones
● Pérdida de información
● Impacto aguas abajo
Definiendo cuándo y cuánto4
25. Demo:
● Añadir grupos de elementos
requeridos
● Especificar elementos
necesarios para los Usos
BIM/Modelos
Definiendo cuándo y cuánto4
26. ● Gestionar requerimientos de
información
● Definir donde se requiere la
información
● Responsabilidad de la información
La “i” en BIM5
27. Demo:
● Información en bases
de da
● Listas de validación
automatizadas
● Notas y adjuntos
The “i” in BIM5
28. ● Responsabilidad del equipo
● Transferencias de alcance
● Contratos “Paraguas”
Quíen es responsable?6
29. Demo:
● Asignación de equipos
● Transferencias visuales de
alcance
● Imprimir contratos
individuales
Quíen es responsable?6
30. +
1. De acuerdo en el por qué
2. Definición clara de los alcances del
proyecto
3. Aprovechando plantillas(Lean)
4. Definir cuándo y cuánto
5. La “i” en BIM
6. Asignando a quien es responsable
RECAP
31. Planes de ejecución BIM que
todos puedan entender.
PLAN
Episode 1 of 3:
● Plantillas reutilizables de la industria
● Crear PEB en línea
● Reducir administración y aumentar
adopción
Hello Everyone!
Thanks for joining!
Today’s webinar we be speaking about the boring part of BIM
Not to worry - we at LOD Planner made BIM Planning fun!
There are man BIM uses through out a projects life cycle.
No matter the project type there is someone needing a BIM Model for Designing Purposes, Analysis, Clash Detection and Coordination, 4D Simulations in Construction and for Information purposes for Facities Management.
Our industry is similar to many others in that it needs tools for Planning, Authoring, Analysis and Use
We have some fantastic tools for Authoring+Analysis+Use
However unfortunately we are still forced to use these tools for planning our BIM
Not only are they disconnected from each other - they are also completely disconnected from all of our brilliant BIM ecosystem
We believe in an integrated workflow with openBIM standards - that can support connections to other tools
That’s why we created LOD Planner
So for a long time we asked ourselves why this was - why is there so much opportunity for miscommunication when it comes to BIM scoping
LOD Planner is dedicated for BIM, connects the function of all of these tools and provides us the opportunity to connect a contract-to-validation workflow between all parties
It was online
You could invite your team
You had templates
There was built in commenting
There was a built in approval workflow
It was live and could be archived along the way
It was simple and made for OUR industry!
A contract-to-validation workflow between all parties
Everyone has a different opinion on what BIM is.
1.misunderstanding, disagreement on the scope
Results - confusion (on what should be modelled, when, by whom) and blame (contractual challenges and huge risk for AECOs)
Text Option 1: Everyone has a different opinion on what BIM is and thus create misunderstanding, disagreement on the scope.
Text Option 2: Everyone has their own BIM Model use. Is this why we can’t get along?
Why we need visual scopes
What should be modeled
How should we structure our scope
What needs to be modeled and how much
When does it need to be modeled
Who is responsible
Model purpose is essential
Modeling expectations can sometimes be left undefined
Aligning BIM goals can be challenging
Phases (AIA?)
Stages (RIBA?)
Project Deliverables
AND BIM Uses/Model Uses
Model purpose is essential
Modeling expectations can sometimes be left undefined
Aligning BIM goals can be challenging
Phases (AIA?)
Stages (RIBA?)
Project Deliverables
AND BIM Uses/Model Uses
Too much scope = over modeling
Unclear scope = not meeting expectations
Built-in element library
Simple Drag n Drop
Flexible folder structure
Too much scope = over modeling
Unclear scope = not meeting expectations
Built-in element library
Simple Drag n Drop
Flexible folder structure
Copy/paste scopes increase risk
Difficult to continuously improve
Inconsistent
Using Global Classification folders
Company templates
Copy/paste scopes increase risk
Difficult to continuously improve
Inconsistent
Using Global Classification folders
Company templates
Misaligned scope expectations
Missing information for BIM / Model Uses
Downstream impacts
Quickly assign and populate scope grid
Clearly define when scope is required
Specify what elements are to be modeled
Misaligned scope expectations
Missing information for BIM / Model Uses
Downstream impacts
Quickly assign and populate scope grid
Clearly define when scope is required
Specify what elements are to be modeled
Challenges:
Managing information requirements
Defining where information is required
Responsibility of Information
Demo:
Information Requirements Library
Managing your project Information Requirements
Assigning exactly where information is needed
Automated Information Requirement Checklist
Assigning responsibility sometimes requires multiple contracts
Difficult to define when scope is handed over between teams
Difficult to hold teams accountable
Assigning responsibility sometimes requires multiple contracts
Difficult to define when scope is handed over between teams
Difficult to hold teams accountable
Why we need visual scopes
What should be modeled
How should we structure our scope
What needs to be modeled and how much
When does it need to be modeled
Who is responsible