FME 2015 and Beyond

CONNECT. TRANSFORM. AUTOMATE.
FME 2015 and Beyond
Dale Lutz, Don Murray

Safe Harbor Statement
Our discussion may include predictions, estimates or other
information that might be considered forward-looking. While
these forward-looking statements represent our current judgment
on what the future holds, they are subject to risks and
uncertainties that could cause actual results to differ materially.
You are cautioned not to place undue reliance on these forward-
looking statements, which reflect our opinions only as of the date
of this presentation. Please keep in mind that we are not
obligating ourselves to revise or publicly release the results of
any revision to these forward- looking statements in light of new
information or future events. Throughout today’s discussion, we
will attempt to present some important factors relating to our
business that may affect our predictions.

Connect.
Transform.
Automate.

IFC Writing Highlights
 Supports IFC2x3 and IFC4

 Create all types of IFC objects - walls, beams,
windows, doors, openings, spaces, …

 Full support for the property and quantity sets
defined in the IFC2x3 and IFC4 specifications

IFC Writing: Scenario 1
Rough DGN Floorplan -> IFC

Workbench Used to Enhance Geometry

Extruded BIM Model Viewed in Solibri

IFC Writing Scenario 2:
Read Building Footprints & Terrain

Extrude 3D Buildings with Roof Height

The “Slim BIM” is in Revit

Minecraft Example 1: Terrain

Minecraft Example 1: Source Data

Minecraft Example 1: Result

Minecraft Example 1 – Unobtainium
Currently writer does not “fill in” data underneath
 Produces hollow results

Example 2 – Sketchup -> Minecraft

Minecraft Example 2: Source Sketchup

Minecraft Example 2: Result

Add A Web Service

Add A Web Service
 In FME
Options Dialog
Specify How to
Connect To
Your Web
Service
 FME will ship
with some
preconfigured
web services

Add & Use A Named Connection
 When running the
workspace backend will
look up the authentication
information based on the
Named Connection.
 Only connection name
is stored in the
workspace.

Update Named Connection
 If connection information changes, no need to
open the workspace
 No passwords in workspaces!

FME Server Integration
 When publishing the workspace to FME Server map
the named connections used in the workspace to the
appropriate Named Connections on FME Server

File Storage Web Service Integration
 Select Named Connection to indicate where the file(s) are
located
 Dialogs will be written to support browsing to files or you
can type a URL
 At runtime, file(s) will be downloaded from or uploaded to
specified URL

PDFPageFormatter Transformer

Vote Early! Vote Often!
fme.ly/frank
en

Natural Feature Type Terminology

Modeless Transformer Parameters

Autohiding Docks

Guides & Grids: Demo

History Tree

Resizable Feature Types & Transformers

Today - FME Server Deployment
FME
FME Server Core
License
Server
Each Engine Machine
has license file pointing
to license server.
License Server file must
be updated each time
engines changes.
Engines connect to
License Server to get
license.
Engine communicates
with Server Core to do
work
Each Engine Machine
has file pointing to
FME Server Core
Big Support Headache
Inconveniencing users!!

New FME Server Deployment
FME
FME Server Core
License
Server
Say Goodbye to License
Server.
At connect time Engines
managed by Server Core
Each Engine now only
knows about Server
Core.
Simpler Deployment!
More Flexibility!

Benefit 1 – Burst Licensing
FME Server Jobs
License Server Time!
Any number of Engines.
Change number of engines
at any time.
Demand Peak

Benefit 2 - FME Desktop Workgroup
FME Desktop
Author and run
spatial data
transformation tasks
FME Workgroup Hub
Share Central
Workspace Repository
FME Server Core
Only
No Engines!!!

Benefit 3 – Cloud Management
FME Desktop
Author and run
spatial data
transformation tasks
FME Workgroup Hub
Share Central
Workspace Repository

FME Cloud Deployment
FME Cloud –Today
FME Server
Web Layer Queue
Database
•System
•Application
FME Engines
Everything on one instance

FME Cloud Deployment
FME Cloud – Future
FME Server
Web Layer
FME
Engines
ELB – Load Balancer
Amazon RDS
FME Server
Web Layer
FME
Engines
. . .
Amazon S3
Availability Zone 1 Availability Zone 2
ELB – Load Balancer
• Reliability
• Fault Tolerance
• Horizontal Scaling
RDS – Database
• Performance
• Fault Tolerance
• Scalability
AWS
Cloudwatch
SQS– Queue
• Reliability
• Scalability
S3– Shared Resources
• Reliability
• Scalability
• Performance
CloudWatch
• Reliability
• Scalability
• Performance

FME Cloud - Future
Multi-Region Support
Amazon Virtual Private Cloud

FME 2015 and Beyond

Recomendados

Recomendados

Mais conteúdo relacionado

Semelhante a FME 2015 and Beyond

Semelhante a FME 2015 and Beyond (20)

Mais de Safe Software

Mais de Safe Software (20)

Último

Último (20)

FME 2015 and Beyond