|
2 | 2 | title: Welcome
|
3 | 3 | ---
|
4 | 4 |
|
5 |
| -# |
6 | 5 |
|
7 | 6 | <p align="center">
|
8 | 7 | <img width="500" src="https://raw.githubusercontent.com/BHoM/documentation/main/Images/logos/BHoM_Logo.png">
|
9 | 8 | </p>
|
10 | 9 |
|
11 | 10 | <br/><br/>
|
12 | 11 |
|
13 |
| -### So - what exactly is the BHoM? |
| 12 | +### What is BHoM? |
14 | 13 |
|
15 |
| -The **BHoM** (**Buildings and Habitats object Model**) is a collaborative computational development project for the built environment. |
16 |
| -BHoM aims to standardise the data and functionality that AEC domain experts use to design across all disciplines. |
| 14 | +The **BHoM** (**Buildings and Habitats object Model**) is a framework for AEC, a collection of _schemas_, _functions_ and _schema conversions_. |
17 | 15 |
|
18 |
| -BHoM is a collection of _schemas_, _functionality_ and _conversions_. |
19 |
| -BHoM aims to standardise the _data_, and the functionality that operates on it, in the belief that this provides great opportunities for efficiency, for collaboration and most of all, to improve the way we work. |
| 16 | +The BHoM schema -- called BHoM Object Model -- contains definitions for any kind of AEC concept: |
| 17 | +from physical concepts (e.g. columns, floors, etc.) to theoretical concepts (structural forces, light, etc.). |
20 | 18 |
|
21 |
| -### BHoM tries to avoid common pitfalls of other AEC frameworks |
22 |
| -BHoM does not attempt to standardise exact processes, because these must be flexible. |
23 |
| -BHoM does not aim to be an holistic software solution to replace established software used and loved by people. |
24 |
| -BHoM is not designed as a data-sharing platform, like Speckle or BIM360; although it can be used in synergy with them, BHoM attempts to unify the "shape" of the data, and the functionality that can operate on it, rather than how the data is shared. |
| 19 | +Further, BHoM offers several functions that can operate on the BHoM objects. For example, you can derive calculations or quantities from given objects, like the total weight of a set of BHoM columns. |
25 | 20 |
|
| 21 | +The objects and functions are software-agnostic, and you can access it from command line, or from specific software, like Grasshopper, Excel, Revit, etc. |
| 22 | + |
| 23 | +To export/import from the BHoM format to other software, BHoM offers several _adapters_ that can convert to/from BHoM, so you can export/import from e.g. Autodesk Robot, Revit, Grasshopper, etc. |
| 24 | + |
| 25 | +In short, BHoM aims to standardise the _data_ and the functionality that operates on data, in an open-source way. |
| 26 | + |
| 27 | +### BHoM VS other AEC frameworks |
| 28 | + |
| 29 | +BHoM focuses on defining _concepts_ without a focus on a particular software or graphical interface. |
| 30 | +BHoM is transdisciplinary, software-agnostic and office/region/country-invariant. |
| 31 | + |
| 32 | + |
| 33 | +<img width="1136" height="610" alt="image" src="https://github.com/user-attachments/assets/4d636b3d-30fd-45c2-90b8-fbdded6f8ff6" /> |
26 | 34 |
|
27 |
| -### An agnostic framework |
28 |
| -BHoM is crafted as transdisciplinary, software-agnostic and office/region/country-invariant, and therefore would be nothing without our active community and wide range of contributors. |
29 | 35 |
|
30 | 36 | ### Embracing open-source
|
31 |
| -The whole **BHoM** project uses an open-source model for project architecture, co-creation and planning. So explore, experiment and contribute to both the source code and the wiki. Sharing and building our code together in this open-source type approach means we can feed off and pool our disparate knowledge, experience and expertise towards a common goal – better design. |
| 37 | +The whole **BHoM** project uses an open-source model for project architecture, co-creation and planning. |
| 38 | + |
| 39 | +So explore, experiment and contribute to both the source code and the wiki. |
| 40 | + |
| 41 | +Sharing and building our code together in this open-source type approach means we can feed off and pool our disparate knowledge, experience and expertise towards a common goal – better design. |
0 commit comments