Forge - DevCon 2017, Darmstadt Germany: HFDM - What, why & how?

© Autodesk, Inc. 2017
HFDM - What, Why and How ?
Arno Zinke
Cloud Platforms
October, 2017

High Frequency Data Management

Quantum | Fusion
Forge HFDM
Data at the Center!

Forge HFDM
Data at the Center!
Opened to you!
Early next year

Miami Aquarium: Shark Tank

Temporary wooden form as can be seen on the slide

© Autodesk, Inc. 2017 ©CW Keller & Associates, Inc.
Manufactured

Architect
Bulding Design
Formwork
Detailed Design
Woodwork
Manufacture Data
Shoring
Design

Architect
Bulding Design
This file is huge!
Formwork
Detailed Design
Woodwork
Manufacture Data
Shoring
Design

Architect
Bulding Design
Formwork
Detailed Design
Woodwork
Manufacture Data
Shoring
Design
I don’t want my full design
to be available to Keller!

Formwork
Detailed Design
Woodwork
Manufacture Data
Shoring
Design
Architect
Bulding Design
I need to write a Revit plugin
or manually copy it!

Formwork
Detailed Design
Woodwork
Manufacture Data
Shoring
Design
Architect
Bulding Design

Formwork
Detailed Design
Woodwork
Manufacture Data
Shoring
Design
Architect
Bulding Design
I need to write a Fusion plugin
or manually import it!

Formwork
Detailed Design
Woodwork
Manufacture Data
Shoring
Design
Architect
Bulding Design
We can't manufacture this!

We can't manufacture this!
Formwork
Detailed Design
Woodwork
Manufacture Data
Shoring
Design
Architect
Bulding Design

Formwork
Detailed Design
Woodwork
Manufacture Data
Shoring
Design
Architect
Bulding Design
What has actually changed?

2 Years Later

What are the relationships between all these files?
2 Years Later
? ?
?

What did the project look like 6 months ago?
2 Years Later

History and Relationships
● What are the relationships between all these design files?
● Can I go back in time to look at an older version?
Granular data access
● Why do I need send complete files?
○ The next in line only needs a small part.
○ I made only a small change.
● I don’t want to share my IP
Data Management Needs
Internal collaboration
● Design exploration
● Collaborative design
Custom workflows
● Autodesk does not always have to right functionality.
● I don’t want to write a plugin for every possible CAD application.

Use Forge HFDM
to manage your data

http://boredomtherapy.com/wp-content/uploads/2015/04/02-fake-animal-hybrids.jpg

○ Generic branch and merge
○ Real-time
○ Offline mode
What is Forge HFDM?
Secure and efficient HF
cloud data store
Collaboratively change data Granular Access Control
○ Communicate and store HF Changes
○ Full and fine grained history
○ GDPR, SOC compliant
○ Users own certain parts of the data
○ Clients can subscribe to parts of the data
○ Owners can restrict access to their data
Service that allows:

What is Forge HFDM?
JavaScript, C++, C#

Drawing Application Example
○ Allows to draw shapes on a canvas.
○ Make modifications to these shapes.
○ Automatically saves to cloud storage.
Application that:
Cloud Storage

Naive Way:
Send full datamodel

Storing Full Views (naive way)

Shapes:
Circle_1:
Type: circle
center: (x: 2, y: 2)
radius: 2
color: “blue”

Shapes:
Circle_1:
Type: circle
radius: 2
color: “blue”
Rect_1:
Type: rectangle
width: 2
height: 3
color: “blue”

Shapes:
Circle_1:
Type: circle
radius: 2
color: “blue”
Rect_1:
Type: rectangle
width: 2
height: 3
color: “red”

Shapes:
Circle_1:
Type: circle
radius: 2
color: “blue”
Rect_1:
Type: rectangle
width: 3
height: 3
color: “red”

Storing and sending full datamodels is inefficient
Client StorageFiles

In the use of network bandwidth
Client StorageFiles

With regards to memory consumption
Client StorageFiles

Common “solution”: no history
Client StorageFiles

Sending and Storing Changes
Forge HFDM Way

Storing Changes (HFDM way)

Add:
type: circle
id: circle-1
radius: 2
color: “turquoise”

Add:
Type: rect
id: rect-1
width: 2
Height: 3
color: “blue”

Modify:
id: rect-1
color: “red”

Modify:
id: rect-1
width: 3

Modify:
id: rect-1
Center:
x: 5

Is efficient
● bandwidth: we send only what has changed
● storage: circle data is stored only once
And we can reconstruct the full history
of the data.
Storing Changes (HFDM way) Cloud Storage

High Frequency Data Streams and Persistency
Upload File
Update File
Upload File Upload File
Update File Update File
Low frequency file handling

Upload File
Update File
Upload File Upload File
Update File Update File
Low frequency file handling
change change change change change change change change
Incremental high frequency changes
High Frequency Data Streams and Persistency

Fine Grained History

Grained History

Asynchronous Collaboration

Branching

Branching
Branch

Merging
Branch Merge

3 Options to resolve conflicts
● Standard Operational Transformation (OT)
● Automatic custom conflict resolution functionality
● Custom conflict resolution with user intervention
Three options:

Branching and Merging Allows :
Design exploration
By creating multiple branches
Asynchronous collaboration
By merging changes of two branches
Client
Client
Changes

Real-time Collaboration

Real-time collaboration allows :
● Multiple collaborators
Manipulating the branches simultaneously
● Continuous merging
Of the local and global branches
Client
Client
Changes

Granular Access Control

● A client can choose
which data to fetch
● A user owns
certain parts of the data
● Owner can control
user access
Granular access
Changes
Client
Forge HFDM
Client
All data Circles only

Client types

Reactive, Distributed Clients
Forge
HFDM
Changes

Reactive, Distributed Clients and Services
Forge
HFDM
Changes

Interoperability: data schema’s
{
typeid: 'example:colored_point-1.0.0',
properties: [
{ id: 'position', properties: [
{ id: 'x', typeid: 'Float32' },
{ id: 'y', typeid: 'Float32' },
{ id: 'z', typeid: 'Float32' }
]},
{ id: 'color', properties: [
{ id: 'r', typeid: 'Float32' },
{ id: 'g', typeid: 'Float32' },
{ id: 'b', typeid: 'Float32' }
]}
]
}

What are the relationships between all these files?
? ?
?

Bring the Data to the Center
Players store data in HFDM
Shoring
FormworkArchitect
Woodwork
Forge HFDM

Dealing with Large Models
Only changes are communicated
Players only subscribe to the data they need.
Shoring
FormworkArchitect
Woodwork
Forge HFDM

Read-Only
IP Issues
Access Control: Read, Write, Read / Write
To the part of the data that needs to be shared
Shoring
FormworkArchitect

IP Issues
Access Control: to Read, Write, Read / Write
To the part of the data that needs to be shared
Formwork
Read-Only
Shoring Woodwork

Custom Workflow
Write microservices in any language
Interoperable through open data schemas that can run anywhere.
Shoring
Architect
Woodwork
Formwork

Data at the center with Forge HFDM

HFDM is a Key Technology
Ubiquitous
● Available client libraries: JavaScript, C++, C#
● Interfaces with Autodesk core products and services
HFDM enables connected
applications and collaborative workflows
● Directly access Revit, Inventor or Fusion data from anywhere, even in the browser
● Build custom end-to-end workflows through a common data interface

HFDM: Working with a Shared State

▪ HFDM works best with reactive, data-centric applications
▪ Applications react to data model changes

▪ HFDM works best with reactive, data-centric applications
▪ Applications react to data model changes
▪ Data model changes drive the business logic of an applications

Cloud HFDM
● A simple HFDM-based browser application that renders shapes
Rendering App
Working with a Shared State
A Simple Example

Cloud HFDM
State (data model in local HFDM)
Rendering App
A Simple Example

Canvas RenderingBusiness Objects (code)
A Simple Example
Cloud HFDM Rendering App

Canvas Rendering
● Fetch an existing commit (PropertySet data state) from HFDM
Business Objects (code)
{
Circle: center = (2.0,3.0) color = “red”
Circle: ...
Triangle: ...
Rectangle: ...
}
A Simple Example

● Instantiate and bind business objects to state
CircleRenderObject
CircleRenderObject
TriangleRenderObject
RectangleRenderObject
{
Circle: ...
Triangle: ...
Rectangle: ...
}
A Simple Example

CircleRenderObject
CircleRenderObject
Canvas Rendering
● Canvas gets updated
{
Circle: ...
Triangle: ...
Rectangle: ...
}
A Simple Example

{
Circle: center = (2.0,3.0) color = “blue”
Circle: ...
Triangle: ...
Rectangle: ...
}
State (data model in local HFDM) Canvas RenderingBusiness Objects (code)
● Data state mutation by application: circle color change in state
CircleRenderObject
CircleRenderObject
A Simple Example

CircleRenderObject
CircleRenderObject
Canvas Rendering
● Business object gets informed about this change and canvas gets updated
{
Circle: ...
Triangle: ...
Rectangle: ...
}
A Simple Example

● Change gets written to HFDM
CircleRenderObject
CircleRenderObject
{
Circle: ...
Triangle: ...
Rectangle: ...
}
A Simple Example

● A Forge console app that prints the state (shape types)
TextObject
TextObject
TextObject
TextObject
{
Circle: ...
Triangle: ...
Rectangle: ...
}
Cloud HFDM Console App
Circle
Circle
Triangle
Rectangle
Console
A Different Application

● Apps and services share the same state, enabling real-time collaboration
Circle
Circle
Triangle
Rectangle
{
Circle: center = (2.0,3.0) color =
“blue”
Circle: ...
Triangle: ...
Rectangle: ...
}
State(data)
{
Circle: center = (2.0,3.0) color =
“blue”
Circle: ...
Triangle: ...
Rectangle: ...
}
State(data)
Data-Centric Collaboration

Forge HFDM
Powering the future of Autodesk!

Autodesk and the Autodesk logo are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders.
Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document.
© 2017 Autodesk. All rights reserved.

Forge - DevCon 2017, Darmstadt Germany: HFDM - What, why & how?

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Forge - DevCon 2017, Darmstadt Germany: HFDM - What, why & how?

Similaire à Forge - DevCon 2017, Darmstadt Germany: HFDM - What, why & how? (20)

Plus de Autodesk

Plus de Autodesk (9)

Dernier

Dernier (20)

Forge - DevCon 2017, Darmstadt Germany: HFDM - What, why & how?