This document discusses Trimble's plans to build an Enterprise Platform as a Service (PaaS) framework using open source components. It provides an overview of Trimble as a global company experiencing sustained growth across various industries. The proposed Trimble PaaS (TPaaS) would provide core services like API management, identity management, and an enterprise service bus to enable building scalable solutions. WSO2 open source products are highlighted as fulfilling TPaaS requirements. High-level architecture diagrams depict how TPaaS would offer shared services to both Trimble and partner applications across industries in a scalable, containerized manner. Governance and future steps are also outlined.

1. Building an Enterprise PaaS framework using
Open Source Components
Prakash Iyer
Trimble Navigation Ltd.
Vice President, Software Architecture & Strategy

2. Trimble – Global company positioned to meet a global
market
Corporate Headquarters
Sunnyvale, California
10/29/2013

3. Trimble – Sustained growth
$2,250,000
$2,000,000
$1,750,000
$1,500,000
$1,250,000
$1,000,000
$750,000
$500,000
$250,000
$0
1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012
10/29/2013

4. A key concept is “franchise value” which requires a
subtle & holistic view of every aspect of our businesses
Agriculture
Heavy Civil Construction
10/29/2013
Cadastral & Geospatial
Building Construction
Transportation & Logistics

5. Emerging businesses provide us with potential growth
accelerators
Rail
Forestry
10/29/2013
Environmental &
Waste
Water Utilities
Field Service
Electric Utilities
Oil, Gas &
Chemical
Government
Mining

6. The competition and enterprise challenges require nuanced
resolution of the “entrepreneurship and collaboration”
apparent paradox
Divisions
Entrepreneurship:
- Speed
- Adaptability
- Accountability
- Focus
- Self interest
Growth & Breakout
Market Leadership
Corporate
Collaboration:
– Consistency
– Platforms
– Culture & skills
– Tools
– Common interest
Scalability &
Capability

7. Platform ?

8. Platform Challenges
•
•
•
•
•
Perceived value gap
Team autonomy – organizational challenges
Business value thinking
Traditional platform vs. product driven platform
Platform code and product ownership
– Who owns the shared components?
• Get the architecture right
– Ask the folks at Health and Human Services !!

9. Trimble Platform as a Service (TPaaS)
• Core services needed to build any modern Enterprise Application
• Provides an architectural framework to build loosely coupled SOA
(Service Oriented Architecture )apps
• Architecture to take advantage of the Cloud while building a service
platform that can run on private, public or behind the firewall
• TPaaS combines a development platform, computing resources,
deployment infrastructure and managed hosting services, so you can
reduce the cost, time and complexity of application development.
• Common services layer for building scalable solutions
• Can be offered as a service framework for Trimble dealers and
•
partners to host their applications
Company Confidential

10. What does TPaaS provide?
•
•
Core Services
– API Management
– Identity Management
– Enterprise Service Bus
– Business Process Service
– Complex Event Processor
– Business Rule Server
Cloud Container to host any Trimble service
– Act as a gateway to share any Trimble Service for wider reuse
• E.g. Reverse GeoCoding, Object Registry, Event Registry, etc can be hosted for
wider Trimble
– Scalable “One click” cloud deployment
– Service metering and charging for services
– Technology agnostic to host services (.Net, Java)
Company Confidential

11. Why Open Source ?
• Availability and ability to customize
• Portability and ownership
– Vendor lock-in?
•
•
•
•
Flexibility
Lower Cost & Support Ecosystem
Platform is not what our customers pay for
Watch for licensing model and who is behind it
Company Confidential

12. Why WSO2?
•
•
•
•
•
Comprehensive set of services
Support & Flexibility
Strategic alignment
Active Community
Track record of executing on a vision
Company Confidential

13. High Level Architecture View
•
Vertical Application
Vertical Application
Partner Apps
PaaS (Cloud Monitoring, Auto scaling, Service Metering)
Coarse
Market focused
Market focused
Market focused
Services(80/20 apps) Services(80/20 apps) Services(80/20 apps)
PaaS
Container
PaaS
Container
Trimble Shareable Services
Fine
Core platform services (API Mgr., ESB, Identity ,Complex Event processor, MDM, MAM etc. )
Infrastructure(AWS, Rackspace, VMware etc)
Company Confidential

14. TPaaS and Vertical Solutions
Trimble App-1
Trimble App-2
Trimble App-3
Partner App
Customer App
PaaS
Container
Infrastructure as as Service (e.g. AWS, Rackspace)
Core services
Service clusters from industries;
core services developed centrally
Ag. Services
Buildings services
Telematics services
Other Domain specific services
Geospatial services

15. TPaaS – Step 1
•
•
•
•
API Management
Identity Management
Enterprise Service Bus
Scalable and HA deployment
Company Confidential

16. API Manager
• All services will be published through API manager for consumption
by the Applications.
• Includes a Service Registry to govern services
• Manage service (API) versions and lifecycle (publish, deprecate,
retire).
• Manage subscriptions to services
• Apply security policies to services.
• Track service consumption and statistics.
• Enforce rate limiting and throttling policies
• Horizontally scalable.

17. API Manager Scalable Deployment
•
•
•
•
API manager components split
for a scalable architecture
Store/Publisher runs in a
different cluster as a web
application
API gateway nodes that handles
all the api traffic run in a separate
cluster
Management node runs
independent of these worker
nodes

18. Enterprise Service Bus
Virtualizes services for loose coupling
Declarative development with configuration.
Message mediation through Enterprise Integration Patterns
Routing based on header, content and rules.
Message transformation
Horizontal scaling via clustering with stateless server
architecture
• Low resource utilization
•
•
•
•
•
•

19. TPaaS Deployment
•
•
•
•
•
•
WSO2 LB on all other
layers
HA on WSO LB using AWS
ELB
Auto scaling using WSO
LB for all TPaaS layers
Puppet for Configuration
Management within
TPaaS
Monitoring setup
Alerting

20. Governance Model
• Trimble Model
–
–
–
–
–
–
–
–
Need a clear governance structure to involve all the stakeholders
Make one person to make the final decision when needed
Rolling deliverables
Find an evangelist in each team using the platform services
Keep the core team small and nimble to deliver core services
Make sure to have good support for Opensource components used
Everyone understands the vision and the value of the platform
Support from top and bottom layers of the organization

21. Road ahead and lessons learned
•
Simplify deployment model
–
–
•
Too many knobs to turn when you build a platform on an Opensource.
–
•
•
Integrating to an AppStore
Mobile PaaS – An important next step
–
•
Find ways to hide complexity
Bring config. management across environments under version control
Full Application life cycle management
–
•
Simplify PaaS deployment from installing in different locations
Use other tools where needed make the model simple
Managing and securing content, device and Application
Service discoverability and sharing model

22. Thank You
Prakash_iyer@Trimble.com