A COTS Approach to Implementing Forest Management Systems · A COTS Approach to Implementing Forest...
Transcript of A COTS Approach to Implementing Forest Management Systems · A COTS Approach to Implementing Forest...
A COTS Approach to Implementing Forest Management Systems
Mark Williams, Esri Scot McQueen, GeoEngineers
Topics
1. Introducing the COTS Approach 2. The Role of GIS in Forestry 3. GIS As Infrastructure 4. COTS Technology Elements for Enterprise GIS 5. A Process for a COTS Based Approach 6. Summary 7. Questions / Discussion
Introducing the COTS Approach
What is the COTS Approach?
• Maximizing commercial off the shelf software in a GIS system
• System meets business goals by leveraging COTS - Configures and extends COTS - Avoids developing software
• Immediate capability… continually improving via COTS release cycles
• Users engaged early and often to iteratively improve system
Approaches to Building an Enterprise GIS A spectrum of system implementation patterns
Custom System Built with custom code
Component System
Using stand alone COTS components with
significant development
COTS System
Configured with minimal development
Comparing Approaches
Custom
Custom built to meet business goals
Emphasis on software development
Design based on detailed functional requirements
Considerable development time / effort
Static system
COTS Components
Custom system, using some COTS elements
Emphasis on component-based software
development
Design based on detailed functional requirements
Reduced development time / effort
Some capability evolves with COTS releases
COTS system
Orchestrates COTS to meet business goals
Emphasis on workflows and configuration
Design based on business goals and COTS
capability
Minimized development time / effort
Evolving system with COTS releases
COTS System follows standard system development lifecycles, but activities are different than traditional developmental systems
COTS VS Traditional Delivery Model
Planning REQ Design DEV Test Implement
Planning REQ Design DEV Test Implement
Accelerated Delivery
Traditional Approach
COTS Approach
Configuration Users Exercise System
Users Exercise System
Demos for Users
Configurable COTS Components
ESRI Production Mapping
QA\QC Rules
Feature Templates
Metadata Rules
Map Templates
ArcGIS Workflow Manager
Workflows Application Integration
Task Assistant Manager
GIS Professionals
ArcGIS Server Workflow Manager
ArcGIS Mobile ArcGIS Web APIs
Management Services
Execution Services
Tasking Services
Mapping Services
Non-GIS Users
Field Users
Production
Silver light
Java Script Flex Android Windows iOS
ArcGIS Desktop ArcGIS Server
A Different Way of Thinking
• Challenges common procurement models - Requirements focused on business goals vice detailed
feature functions - Select COTS that best meets business goals and
implement “with the grain” for best results - Schedule linked to COTS release cycles
• Asks users to consider new business processes - New workflows based on COTS strengths (usually better)
- People resist change - Organizations resist change
• Avoid temptation to overly customize - Best intentions of many people often push systems
towards customization
ArcGIS System Concept The backbone of a COTS based enterprise system…
• …with flexibility to support wide range of user roles
Cloud Services
Enterprise Services
Local
• Discover • Create • Manage • Visualize • Analyze • Collaborate
Rich Client
Mobile
ArcGIS
Web Browser
Enterprise GIS System Pattern @ ArcGIS 10 Power to configure how content is produced, shared, and used
Authoritative Content
Producers Basemaps
& ArcGIS.com
Map & Data Products
Services (Maps, Analysis)
Field Edits & Partner Input
Configurable & shared • workflows • production tools • business rules
The Role of GIS in Forestry
Timber
Alaska
Tree Heights
Germany
Wetlands
Minnesota
Change Detection
Kenya
CO2 Sequestration
Kansas
Stream Classification
Ontario, Canada
Vegetation
Indonesia
Biomass
California
Resources Inventory
Logistics / Scheduling
Bavaria, Germany
Resource Assessment
Nevada, USA
Wildfire Assessment
Oregon, USA
Treatment Scheduling
Road Design Wildfire Risk Salvage Analysis Route Planning
Sao Paulo, Brazil
France California, USA Bavaria, Germany Colorado, USA
Tactical Planning
Field Observations
California, USA
Fire Simulation
USA
Workforce Scheduling
Virginia, USA
Timber Stack Logistics
Restocking Planning Timber Cruise Plans Stream Crossings Public Safety
Oregon, USA
Kenya Florida, USA Ontario, Canada Kinglake, Australia
Field Operations
Property Valuation
Kansas, USA
Easements
Washington, USA
Tenure Management
Latvia
Legal Surveys
Property Management Property Research Priority Lands Land Use
Oregon, USA
Maryland, USA Brazil Quinault Indian Nation Korea
Land Administration
Harvest Planning
Scotland, Great Britain
Carbon Accounting
Australia
Road Density
Borneo, Indonesia
Visual Impact Studies
Climate Change Cash Flow Analysis Public Consultation Strategic Planning
Utah
North America Scotland, Great Britain Scotland, Great Britain Alaska, USA
Sustainable Forest Management
GIS As Infrastructure
ArcGIS Supports Multiple Implementation Patterns . . . Reaching Everybody
Server
Workgroups
• Shared Database
• Fixed Applications
• Transactions
Federated
Organizations
• Shared Services
• Integration
• Collaboration
Desktop
Individuals
• Ad Hoc Projects
• Analysis/Modeling
• Mapping
Cloud / Web GIS
Desktop Mobile Web
Enterprise
Device
Pervasive
Enabling the Forestry Enterprise
The Four GIS Business Functions
Examples of Required Business Solutions
Technology Approach
COTS Technology Elements for Enterprise GIS
Data Maintenance Dissemination Geodata Management
A COTS approach for Enterprise GIS
Production Management
Production Geodatabase
Publication Geodatabase
Web Services Web Services
Geodatabase Design
• Emphasize end-user capabilities - Define detailed information products - Build to deliver
• Embrace federated compilation and maintenance - Be realistic, prioritize compilation capabilities - Leverage data content provided by the enterprise - Integrate content at the service level, not RDBMS
• Design for COTS usability - Leverage geodatabase concepts (FCs, subtypes, etc) - Balance tradeoffs for maintenance and dissemination
Geodata Management
Geodatabase Versions
Connected Replicas
Disconnected Replicas
Check Out Replicas
Production Geodatabase
Publication Geodatabase
One-Way Replica
•Read-Write Access •Tuned for Editing •Authoritative Content
•Read-Only Access •Tuned for Services •Approved Content
•Ideal for outsourcing work •XML-based transfer •Two-way exchange
•File-based GDB •In-house or Outsourced •One-time exchange
•Workgroups •Two-way exchange
•Direct editing •Basis for replication
Data Maintenance
• Model new and existing processes - Integrate GIS and non-GIS - Standardize and streamline - Continually evolve workflows
• Configure a common rule-base - Feature templates - Map templates - Quality Control rules
Data Maintenance
ESRI Production Mapping
QA\QC Rules
Feature Templates
Metadata Rules
Map Templates
ArcGIS Workflow Manager
Workflows Application Integration
Task Assistant Manager
GIS Professionals
ArcGIS Server Workflow Manager
ArcGIS Mobile ArcGIS Web APIs
Management Services
Execution Services
Tasking Services
Mapping Services
Non-GIS Users
Field Users
Production
Silver light
Java Script Flex Android Windows iOS
ArcGIS Desktop ArcGIS Server
Data Maintenance
ESRI Production Mapping
QA\QC Rules
Feature Templates
Metadata Rules
Map Templates
ArcGIS Workflow Manager
Workflows Application Integration
Task Assistant Manager
GIS Professionals
ArcGIS Server Workflow Manager
ArcGIS Mobile ArcGIS Web APIs
Management Services
Execution Services
Tasking Services
Mapping Services
Non-GIS Users
Field Users
Production
Silver light
Java Script Flex Android Windows iOS
ArcGIS Desktop ArcGIS Server
Content Dissemination
• Deliver diverse information products - Visualization - Analysis - Geodata
• Enable search & discovery - Standards-based (OGC) - ArcGIS.com
• Support internal and external users - Web services (connected) - Traditional media (disconnected)
Connected
Publication
ArcGIS Server & GeoPortal Extension Search & Discovery
Geoprocessing Services
OGC Services
Map Services
Geodata Services
ArcGIS Server Web APIs JavaScript
API Silverlight
API Flex API
Many Users
Many Applications
Content Dissemination
Disconnected
Distributed Publication
Node
Production Management
• Provide transparency - Task and manage production - Provide status and reporting
• Utilize role-based functionality - Targeted user experience - Keep it simple
• Extend the reach of GIS workflows - Simple, web-based access - Enable non-GIS users
Production Management
Production
ArcGIS Server Web APIs JavaScript
API Silverlight
API Flex API
Managers & Executives
ArcGIS Server Mapping Services
ArcGIS Server Workflow Manager Reporting Services
Management Services
Tasking Services
Execution Services
Web Applications
ArcGIS.com
Data Maintenance
Dissemination (Connected/Disconnected)
A Complete System for Enterprise GIS
Production Management
Geodata Management
Reporting
Execution
Tasking
Management
Non-GIS Users
GIS Users
Web Apps
Field Users
Generate Products
Visualize
Analyze
Search & Discover
Access Data
Many Users
Many Apps
Multiple Options
A Process for a COTS Based Approach
COTS Impacts to System Development Process
Planning REQ Design DEV Test Implement
Planning REQ Design DEV Test Implement
Accelerated Delivery
Traditional Approach
COTS Approach
Configuration Users Exercise System
Users Exercise System
Demos for Users
Enterprise GIS Planning and Implementation
Central Data
Repository
Enterprise Planning
Enterprise Geodatabase
Design
GIS Integration with Existing
Systems
User/Enterprise Access to GIS (Web Portal)
Enterprise GIS Framework
Long Term Support Strategy
GIS Maintenance
(Data, Applications)
Enterprise Planning,
Development
Staffing, Roles &
Responsibilities
IT/Systems Integration
Budget &Funding Mechanisms
GROW SYSTEM STRENGTHEN SUPPORT
The COTS Approach - Planning
Planning REQ Design DEV Test Implement
Accelerated Delivery
Configuration Users Exercise System
Demos for Users
Planning
• Focus on business objectives and goals • What are you trying to accomplish?
- Improving productivity
- Increasing revenue
- Reducing cost
- Supporting regulatory requirements
• All system requirements and technical decisions should consider business goals
4
Remember you are trying to solve a business problem not engineer a new software module
Planning
• Plan project using multiple phases/iterations • Plan for heavy user interaction and validation of
capabilities • Allows for integrating new COTS releases • Provides an opportunity for intermittent training
4
Phases or iterations should focus on completing a use case or scenario
4
• Implement base COTS release
• Data Model – first release
• Workflows - initial configuration
• Usage Patterns – Identify
• User Roles – Define • Architecture - establish
initial infrastructure
Phase 1: Out of Box Phase 2:
Refine Phase 3: Finalize • Implement incremental
COTS Release • Data Model – modify
based on input • Workflows – elaborate
and create new • Usage Patterns - refine • Architecture - Integrate
with other systems
• Implement Final COTS Deployment Release
• Data Model - finalize • Workflows - finalize
workflows • Architecture – plan for
system implementation • Training – develop plan
COTS Based Phased Planning
Continuous Learning & Improvement
The COTS Approach - Requirements
Planning REQ Design DEV Test Implement
Accelerated Delivery
Configuration Users Exercise System
Demos for Users
Requirements
• Focus on the “what” NOT the “how” • Embrace the change – do not modify COTS
technology to support an inefficient process • Keep it simple
4
Users COTS Demos
Traditional COTS
Business Workflows
Land Sales Summary Reports
As Is
Fina
nce
Tax
Le
gal
ENR
& O
ther
Le
ases
Fo
rest
ry &
O
ps S
uppo
rt R
eal
Esta
te
Evaluate Property Profile
Evaluate Asset Profile
Improve
Evaluate Disposition Options
Negotiate Deal
Final Contract Estab. Escrow Record Deal Manage 1031
Excel Pipeline and Summary Reports Excel Reports
Man
ual C
olla
bora
tion
GIS
Map System
Identify Property
Identify Property
Excel
Approve & Finalize Deal
Man
ual C
olla
bora
tion
Man
ual C
olla
bora
tion
Legl desc, Paper
Current Owner? Acq’rd From? Encumbered?
Excel Lists
Tax Status? BIG Impact?
GIS, Excel
Timber NPV? Harvest Schd? Environment Concern?
Access
Minerals Val? Active Lease? Hunt Club?
Man
ual C
olla
bora
tion
Excel Lists
Tax Compliant?
Excel?
Ledger Transactions Cost Accounting
Excel Lists
Transfer Ownership
Terms Sheet
Draft Contract Earnest Money
Man
ual
Man
ual C
olla
bora
tion
Excel Templates
Ledger Trans. Financial Trans.
??
Update System
Excel Lists
Titles
Update System
Update System
Minerals
Update System
Forestry
Update System
Business Workflows Used to define solutions
On-line Lists
Land Sales Summary Reports
As Is
Fina
nce
Tax
Le
gal
ENR
& O
ther
Le
ases
Fo
rest
ry &
O
ps S
uppo
rt R
eal
Esta
te
Evaluate Property Profile
Evaluate Asset Profile
Improve
Evaluate Disposition Options
Negotiate Deal
Final Contract Estab. Escrow Record Deal Manage 1031
On-line Pipeline and Summary Reports On-line Reports
Inte
grat
ed D
atab
ase
GIS
GIS
Identify Property
Identify Property
Excel AFD
Approve & Finalize Deal
Inte
grat
ed D
atab
ase
On-
line
Che
cklis
ts
??, Paper
Acq’rd From? Encumbered?
On-line Lists
Tax Status? BIG Impact?
GIS
Timber NPV? Harvest Schd? Environment Concern?
Minerals, Access
Minerals Val? Active Lease? Hunt Club?
Inte
grat
ed D
atab
ase
On-line Lists
Tax Compliant?
Lawson Financials
Ledger Transactions Cost Accounting
On-line Lists
Transfer Ownership
Terms Sheet
Draft Contract Earnest Money
Man
ual
On-
line
Not
ifica
tion
On-line Templates
Ledger Trans. Financial Trans.
Update System
Update System
Update System
Minerals?
Update System
GIS
Update System
The COTS Approach - Design
Planning REQ Design DEV Test Implement
Accelerated Delivery
Configuration Users Exercise System
Demos for Users
Design
• Short focused interactive design sessions • Heavy use of prototyping and lab environment • End users along with COTS experts
- Defining user roles - Defining workflows - Identifying efficiencies - Understanding end user access
• Consider future COTS releases
4
Design should emphasize delivering immediate capabilities
COTS Design/Configuration Process
Configure
•Build base workflows •Streamline COTS usage
•Obtain user feedback
Design
•Configuration Team focuses on workflows
•User role definition •Usage patterns
Prototype
•COTS experts fully engaged with users
•Review existing COTS tools
The COTS Approach – Develop/Configuration
Planning REQ Design DEV Test Implement
Accelerated Delivery
Configuration Users Exercise System
Demos for Users
Develop
• Based on user input and feedback • Targeted to configuration not customization • 90% configuration 10% (or less) development
5
Users
Roles & Usage
Configuration Team
COTS Products
Data Model Workflows
The COTS Approach – Test
Planning REQ Design DEV Test Implement
Accelerated Delivery
Configuration Users Exercise System
Demos for Users
Test
• Frequent user validation • Multiple user groups to verify usage patterns • Prioritize user feedback – leverage phases • Use validation as training opportunity
5
Real time feedback to Configuration Team
Use/Exercises Feedback Training Refine
Users Configuration
Team
The COTS Approach – Implementation
Planning REQ Design DEV Test Implement
Accelerated Delivery
Configuration Users Exercise System
Demos for Users
Implementation
• Understand you are changing process not just technology
• Leverage COTS training • Data flow patterns • IT Specifications • Security considerations • Administration
- Who? What? Skills?
• Don’t forget about the data!
5
COTS Based Phased Implementation
Migrate to new data
model
Capacity Planning
Migrate Data for AOI
Implement Base
Architecture
Verify Security Model
Training Users
Pilot
Deployment Phase 1
Deployment Phase 2
Execute Workforce Training
Complete Data
Migration
Refine Operational Procedures
Expand to Other Users
Implement Incremental
COTS Release
Expand Workforce Training
Ramp Data Migration
Refine Operational Procedures
Other Workgroup
Users
Configure Workflows
Summary
Benefits of a COTS Approach
• Minimized cost to implement • Shorter schedule – immediate exercising by users • Reduced risk (technology proven by user-base) • Lowered maintenance costs • Evolves with future COTS functionality • Wider range of qualified people to use and maintain
system
Summary
• COTS configuration is a more efficient way to approach system development
• The COTS Approach redefines system development process, with focus on mission instead of building software
• ArcGIS 10 provides a platform for configuration and rapid development – making the COTS Approach viable for many systems
Questions
Contact Us: - Mark Williams, [email protected] - Scot McQueen, [email protected]
More Info:
- COTS Approach ArcNews article (Winter 2011) - http://www.esri.com/news/arcnews/winter1011articles/the-cots-approach.html
- COTS Approach white paper (Jan 2011) - http://www.esri.com/library/whitepapers/pdfs/cots-based-approach-
enterprise.pdf