Any data..! Any where..! Any time..! Linking Process and Content in a Distributed Spatial Production...
20
Any data..! Any where..! Any time..! Linking Process and Content in Linking Process and Content in a a Distributed Spatial Production Distributed Spatial Production System System Pierre Lafond HydraSpace Solutions Inc www.hydraspace.com
-
Upload
buck-johns -
Category
Documents
-
view
214 -
download
1
Transcript of Any data..! Any where..! Any time..! Linking Process and Content in a Distributed Spatial Production...
Any data..!
Any where..!Any time..!
Linking Process and Content in a Linking Process and Content in a Distributed Spatial Production System Distributed Spatial Production System
Pierre LafondHydraSpace Solutions Inc
www.hydraspace.com
HydraSpace“Linking People and Information”
Why Metacontent?Why Metacontent?Users separate from Information!Users separate from Information!
Why Metacontent?Why Metacontent?Users separate from Information!Users separate from Information!
time - viewing historical data at some point in the future
space - physically separated or having limited proximal access to the data and data collectors
subject area - not being a specialist in the information domain that the data represents
HydraSpace“Linking People and Information”
A Hierarchical view ofA Hierarchical view of meta-content Needs meta-content Needs
ManagingHarmonization, Integration, Creation, Preservation, Retention, Disposal
FindingTime, Place,
Theme, Focus
AssessingRelevance, Quality, Cost,
Timeliness, Concepts, Methods, Sources,
UsingClassifications, Questionnaires, Codebooks,
Dictionaries, Database Schemas, Record Layouts
HydraSpace“Linking People and Information”
The Components The Components of Metacontentof Metacontent
Database
Metadata
(databaseschema)
Controls&
Guides
Meta-information
(repository &web documents)
Describes fitnessfor use
Metacontent are facts that describes both database organization and the data's fitness for
use.
linked&
Referenced
HydraSpace“Linking People and Information”
Metacontent - Fitness for useMetacontent - Fitness for use Metacontent - Fitness for useMetacontent - Fitness for use
content, ownership, collection and processing methods, lineage, resolution, accuracy, spatial location and extent, temporal location and extent
HydraSpace“Linking People and Information”
Levels of MetacontentLevels of Metacontent
Static Static metacontentmetacontent
Ownership,Lineage, Resolution, Accuracy, Spatial location and extent, Temporal location and extent
Dynamic Dynamic metacontentmetacontent
Collection and processing methods,
what was done
what is being done
ProspectiveProspective metacontentmetacontent
what is planned to be done
HydraSpace“Linking People and Information”
Metacontent Management Metacontent Management through the Business Life cyclethrough the Business Life cycle
Planning
Marketing
External collection
Data Acquisition
Production
Distribution
Product Data Management
CUSTOMER
Static and Dynamic Static and Dynamic MetacontentMetacontent
Prospective Prospective MetacontentMetacontent
Survey/ internal
collection
HydraSpace“Linking People and Information”
Static metacontent Recording facts about data during acquisition
Evolution of Metacontent Evolution of Metacontent ManagementManagement
Dynamic metacontent Manually logging process steps executed on datasets Process steps automatically logged by system as they
are being executed System-monitored standard processes
Prospective metacontent Planned and actual processes managed together
Process ManagementProcess Management
HydraSpace“Linking People and Information”
Why Process Management?Why Process Management?(other than for metacontent)(other than for metacontent)
Quality Project planning and monitoring Repeatability Version control Quality assurance Intergroup coordination
Isolating user tasks from complexity of integrating many computer programs
loading datasets discovering feature links
Ability to better identify impact of new or updated source data on products
Ability to reduce time to market from source acquisition to product
HydraSpace“Linking People and Information”
The Concept of SessionThe Concept of Session
A session is a set of activities carried out A session is a set of activities carried out over a period of time and over a period of time and covering a covering a specified geographic areaspecified geographic area, which will , which will produce a new or updated spatial dataset. produce a new or updated spatial dataset.
A session layer is a common mechanism by A session layer is a common mechanism by which users perform activities to acquire, which users perform activities to acquire, integrate and make use of spatial data.integrate and make use of spatial data.
HydraSpace“Linking People and Information”
Process Manager ComponentsProcess Manager Components
Basic Session Operations
Process configuration
Source acquisition session operations
Product maintenance session operations
Source integration session operations
Workflow
Process tracking and reporting
SESSION CORE
Task Manager and Scheduler
HydraSpace“Linking People and Information”
Automated Task ManagerAutomated Task Manager
Allows users to deal with a user task interface instead of computer programs at the command line
Example: Commands required to be run to extract data for validation:
execute cwodi.dropwindow('check3');
execute cwodi.createwindow('check3','halifax',-65.597,42.665,-63.59,44.67);
cwco userid=pierre/xxxx table=halifax window_name=check3 mdffile=check3co.mdf rangecols=pro_depth
hhsort.exe hhsort.con check3sort.mdf check3co.mdf
Users only need to specify the user task they want to do and the parameters for this task
Tasks can be re-configured at any point to take advantage of upgrades, without the user needing to know new syntax
Task manager generates metacontent
HydraSpace“Linking People and Information”
Distributed process architectureDistributed process architecture
Remote collaboration handled through standard distributed database architecture and networking
St John’sSt John’s
OttawaOttawa MontrealMontreal
HalifaxHalifax
Validation hydrographerSurvey hydrographer
Production Quality Control Cartographer
HydraSpace“Linking People and Information”
Case Study Case Study Canadian Hydrographic ServiceCanadian Hydrographic Service
Their challenges: Distributed organization in four offices More powerful data acquisition systems - large volumes More types of products - adoption of IHO S-57 standard New ENC update distribution method Fewer staff - less budget
HydraSpace“Linking People and Information”
Attacking the problemAttacking the problem
Data acquisition
In-house survey
3rd party survey
Other documents/sources
Data validation and integration
Chart production
Data ManagementProcess Management
Oracle
CubeStor
HHViewer
CarisCaris Object Manager
Custom utilities
HydraSpace“Linking People and Information”
CHS ProgressionCHS Progression
Specific process management tool for production
S57 Object andProduct
Repository
Dataset versioning Product Configuration
Process Tracking andMonitoring
Data Archival
Security
HydraSpace“Linking People and Information”
CHS Progression (cont’d)CHS Progression (cont’d)
More generic process management model defined for data acquisition and validation
Basic Session Operations
Process configuration
Source acquisition session operations
Source integration session operations
Workflow
Process tracking and reporting
SESSION CORE
Task Manager and Scheduler
HydraSpace“Linking People and Information”
CHS Progression (cont’d)CHS Progression (cont’d)
Implement generic model for all operations Allow vizualisation of all projects graphically
Product maintenance session operations
Basic Session Operations
Process configuration
Source acquisition session operations
Source integration session operations
Workflow
Process tracking and reporting
SESSION CORE
Task Manager and Scheduler
HydraSpace“Linking People and Information”
Keys to effective process management in Keys to effective process management in spatial data warehousing and productionspatial data warehousing and production
Define standard processes Define user tasks executed by a series of automated
tools Plan work sessions (projects) Log user tasks as they are carried out System-generated metacontent as automated user
tasks are executed Monitor and control standard processes Location independence - distributed architecture
HydraSpace“Linking People and Information”
Questions?Questions?
Pierre [email protected]
Henry [email protected]
www.holonics.ca
