FME 2015 and Beyond

3,018
-1

Published on

A look at what's in store for FME 2015 and the future of FME.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
3,018
On Slideshare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
50
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

FME 2015 and Beyond

  1. 1. CONNECT. TRANSFORM. AUTOMATE. FME 2015 and Beyond Dale Lutz, Don Murray
  2. 2. 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.
  3. 3. The Future
  4. 4. CONNECT. TRANSFORM. AUTOMATE. Connect. Transform. Automate.
  5. 5. CONNECT. TRANSFORM. AUTOMATE.
  6. 6. CONNECT. TRANSFORM. AUTOMATE.
  7. 7. CONNECT. TRANSFORM. AUTOMATE.
  8. 8. CONNECT. TRANSFORM. AUTOMATE.
  9. 9. CONNECT. TRANSFORM. AUTOMATE.
  10. 10. IFC Writing
  11. 11. IFC Writing Highlights  Supports IFC2x3 and IFC4 CONNECT. TRANSFORM. AUTOMATE.
  12. 12. IFC Writing Highlights  Create all types of IFC objects - walls, beams, windows, doors, openings, spaces, … CONNECT. TRANSFORM. AUTOMATE.
  13. 13. IFC Writing Highlights  Full support for the property and quantity sets defined in the IFC2x3 and IFC4 specifications CONNECT. TRANSFORM. AUTOMATE.
  14. 14. IFC Writing: Scenario 1 Rough DGN Floorplan -> IFC CONNECT. TRANSFORM. AUTOMATE.
  15. 15. IFC Writing: Scenario 1 Workbench Used to Enhance Geometry CONNECT. TRANSFORM. AUTOMATE.
  16. 16. IFC Writing: Scenario 1 Extruded BIM Model Viewed in Solibri CONNECT. TRANSFORM. AUTOMATE.
  17. 17. IFC Writing Scenario 2: Read Building Footprints & Terrain CONNECT. TRANSFORM. AUTOMATE.
  18. 18. IFC Writing Scenario 2: Read Building Footprints & Terrain CONNECT. TRANSFORM. AUTOMATE.
  19. 19. IFC Writing Scenario 2: Extrude 3D Buildings with Roof Height CONNECT. TRANSFORM. AUTOMATE.
  20. 20. IFC Writing Scenario 2: The “Slim BIM” is in Revit CONNECT. TRANSFORM. AUTOMATE.
  21. 21. Minecraft Example 1: Terrain CONNECT. TRANSFORM. AUTOMATE.
  22. 22. Minecraft Example 1: Source Data CONNECT. TRANSFORM. AUTOMATE.
  23. 23. Minecraft Example 1: Result CONNECT. TRANSFORM. AUTOMATE.
  24. 24. Minecraft Example 1: Result CONNECT. TRANSFORM. AUTOMATE.
  25. 25. Minecraft Example 1 – Unobtainium Currently writer does not “fill in” data underneath  Produces hollow results CONNECT. TRANSFORM. AUTOMATE.
  26. 26. Example 2 – Sketchup -> Minecraft CONNECT. TRANSFORM. AUTOMATE.
  27. 27. Example 2 – Sketchup -> Minecraft CONNECT. TRANSFORM. AUTOMATE.
  28. 28. Minecraft Example 2: Source Sketchup CONNECT. TRANSFORM. AUTOMATE.
  29. 29. Minecraft Example 2: Result CONNECT. TRANSFORM. AUTOMATE.
  30. 30. Minecraft Example 2: Result CONNECT. TRANSFORM. AUTOMATE.
  31. 31. Web Services
  32. 32. Add A Web Service CONNECT. TRANSFORM. AUTOMATE.
  33. 33. Add A Web Service  In FME Options Dialog Specify How to Connect To Your Web Service  FME will ship with some preconfigured web services CONNECT. TRANSFORM. AUTOMATE.
  34. 34. 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. CONNECT. TRANSFORM. AUTOMATE.
  35. 35. Update Named Connection  If connection information changes, no need to open the workspace  No passwords in workspaces! CONNECT. TRANSFORM. AUTOMATE.
  36. 36. 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 CONNECT. TRANSFORM. AUTOMATE.
  37. 37. Web Filesystems
  38. 38. 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 CONNECT. TRANSFORM. AUTOMATE.
  39. 39. CONNECT. TRANSFORM. AUTOMATE. Connect. Transform. Automate.
  40. 40. PDFPageFormatter Transformer CONNECT. TRANSFORM. AUTOMATE.
  41. 41. PDFPageFormatter Transformer CONNECT. TRANSFORM. AUTOMATE.
  42. 42. Vote Early! Vote Often! fme.ly/frank en
  43. 43. Natural Feature Type Terminology CONNECT. TRANSFORM. AUTOMATE.
  44. 44. Natural Feature Type Terminology CONNECT. TRANSFORM. AUTOMATE.
  45. 45. Modeless Transformer Parameters CONNECT. TRANSFORM. AUTOMATE.
  46. 46. Modeless Transformer Parameters CONNECT. TRANSFORM. AUTOMATE.
  47. 47. Autohiding Docks CONNECT. TRANSFORM. AUTOMATE.
  48. 48. Guides & Grids: Demo CONNECT. TRANSFORM. AUTOMATE.
  49. 49. History Tree CONNECT. TRANSFORM. AUTOMATE.
  50. 50. History Tree CONNECT. TRANSFORM. AUTOMATE.
  51. 51. Resizable Feature Types & Transformers CONNECT. TRANSFORM. AUTOMATE.
  52. 52. Vote Early! Vote Often! fme.ly/frank en
  53. 53. CONNECT. TRANSFORM. AUTOMATE. Connect. Transform. Automate.
  54. 54. Tighter Cloud Integration
  55. 55. FME Server: Today
  56. 56. FME Server: Tomorrow
  57. 57. FME Server: Tomorrow
  58. 58. FME Server: Tomorrow
  59. 59. FME Server: Tomorrow
  60. 60. 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!!
  61. 61. 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!
  62. 62. Benefit 1 – Burst Licensing FME Server Jobs License Server Time! Any number of Engines. Change number of engines at any time. Demand Peak
  63. 63. 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!!!
  64. 64. Benefit 3 – Cloud Management FME Desktop Author and run spatial data transformation tasks FME Workgroup Hub Share Central Workspace Repository
  65. 65. FME Cloud Deployment FME Cloud –Today FME Server Web Layer Queue Database •System •Application FME Engines Everything on one instance
  66. 66. FME Cloud Today
  67. 67. FME Cloud Tomorrow Leverage
  68. 68. FME Cloud: Tomorrow
  69. 69. 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
  70. 70. FME Cloud - Future Multi-Region Support Amazon Virtual Private Cloud
  71. 71. Thank You

×