Upload
others
View
2
Download
0
Embed Size (px)
Citation preview
Or, “Dude, where’s my stuff?”
Steve ShaferPrincipal Scientist, MS Research
m Research For WPI PPL Workshop, August 2007 1
Facility Maps for Emergency Responders
• Theme for the workshop is “no infrastructure”
• But almost everyone here has shown firefighter locations on a floorplan!– Hardware infrastructure v. IT infrastructure
• Where do those building maps come from?• “Tracking most useful in a big building”
– Big buildings almost always have IT infrastructure!
m Research Facility Map Framework – August 2007 2
Current Indoor Location Systems1. CAD drawing and Bitmap are universal
– Used for everything but no task semantics2. Single-purpose systems are siloed
– Custom-built for a single business purpose– No interoperability, no commoditization– An enterprise may have several of these
3. Research demonstration systems abound– Built by researchers as capability demos– No scalability, limited ability to replicate
m Research Facility Map Framework – August 2007 3
The Indoor Location Ecosystem People
Facility Map Framework – August 2007
Staff
Asset Manager Customer
Application Developer
Partner
CAD DataManager
Space Planner
Architect
Lab Manager
Location System
Integrator
Location System Vendor
Facility ManagerFacility System
Architect
Field Service
Emergency Responder
m Research 4
The Facility Map Framework• FMF is prototype for user-oriented facility
map standard for enterprises• Make it profitable for enterprise to create
facility map data model using FMF– Think ROI rather than Mandate– Money is the “gravity” of the business world
• Published interface allows data sharing• Tools for data authors in enterprise• SDK for application developers
m Research Facility Map Framework – August 2007 5
6
Environ-ment
Sensors
LocationSensors
AssetInfo &
Control
OwnLocationSources
OperationsServices
Facility Map FrameworkVision
MobileDevices
Facility MapFramework
Facility Map Framework – August 2007
CustomerWeb SitesDrawings
CAFMDBs
LOBApps
m Research
Integrated Command & Control
Enterprise OperationsDashboard and Applications
Responders’ Applications(Mobile & Dashboard)
7
DeviceControl
Services
Floorplans &Campus Maps
(incl. EmergencyPrep. Plans)
Locations ofPersonnel and
Assets
Standardization and integration through Facility Map Framework
Responders’Personnel &
Mobile AssetsLocation
Enterprise’sLocation System
Responders’Location SystemCAD Data Device Controllers
m Research Facility Map Framework – August 2007
Generic Applications for FMF• Based on survey at Microsoft 2005
– Asset Location– Asset Detail– Place Information System– Routing and Wayfinding– Incident Response– Map Overlay and Federation– Real-time Sensor Input– “2 ½ D” (extrusions + cross-sections in 3D)
• FMF is designed to do all of the abovem Research Facility Map Framework – August2007 8
Facility Map FrameworkKey InsightLocation Information Sources
CAD drawings
VISIO drawings
CAFM systems
Asset databases
Active Directory etc.
Location from WiFi etc.
RFID & NFC
GPS / Cell phone location
Presence detection
Location Applications
Wayfinding
Route planning
Signage
Space planning
On-site service
Equipment / asset layout
Device management
Incident response
Location-based services
Facility MapFramework
Facility Map Object ModelFMOM
All can fit the same relatively simple object
model
m Research Facility Map Framework – August 2007 9
FMOM
FMML encoding in XMLFM-SQL encoding in SQL Staff
FMEDMap Editor
FMANMap Manager
FMAPIC# APIFMAM
Asset Mapper
FMOWSWeb Service
SPI
Asset Manager / Field Service
Customers
EnterprisePortal
WebPortal
Developer /Integrator
PartnersCAD DataManager
Space Planner /Lab Manager FM-VISIO
Facility Map FrameworkComponents
FMUI
FMOPObject Proxy
Applications
m Research Facility Map Framework – August 2007 10
Map Manager(FMAN)
SOHOEnterprise
FMML MapRepository
FMML / FM-SQL /Web Map Portal
FMMLSnapshots
Real-TimeSensing
FMOWSProvider
Map Editor(FMED)
FM-VISIODrawings
Asset Databases
CAD / VISIODrawings
Facility Map FrameworkAuthoring and Deployment
m Research Facility Map Framework – August 2007 11
Approach and Philosophy• Object-Oriented Map (OOM) as Dashboard• Support for Authoring, Deployment, Applications• Integration via Least Common Denominator
– Common object model in UML, XML, SQL, C#, SOAP• Map-on-Map Composition
– Late binding “compose-on-use” with caching• Layered Articulation Points for Plug-Ins
– Map I/O, Rendering, Object proxies, Event handlers• Declarative Relationships & User Experience
– Full-featured “1-line” location-independent UX• API Allows Application Intervention in UX
– Also power tools for routing, geometry, lookup, etc.m Confidential Facility Map Framework – August 2007 12
How Enterprise Uses FMFWeb Service Shell
FMOPEnterprise OperationsDashboard and Applications
Facility Map API - FMAPI
Map User Interface - FMUI
Device Controllers
Web Service ShellFMOWS
Web Service ShellFMOWS
13
CAD Data Asset DatabaseReal-TimeLocation System Asset Database
Database Scanner
XML Data FileFMMLXML Data File
FMML
FMAPIFMED Map
Editor
m Research Facility Map Framework – August 2007
Issues Addressed by FMF• End-to-end integration• Interoperability of
location components• Extending existing
location resources• Federation across IT
jurisdiction boundaries• Map composition and
overlay• Aggregate namespace
• Route planning (also across maps)
• Real-time update• Location-independent
application design• Data authoring tools• Map management
and deployment tools• Developer API
– Full-featured map UIm Research Facility Map Framework – August 2007 14
Value Added by FMF• Allows integration of enterprise system with
responders’ system
• Supports full-featured dashboard application (real-time, routes, controls, etc.)
• Puts cost of enterprise data sources onto the enterprise (operations & business)
m Research Facility Map Framework – August 2007 15
Toward Online Emergency Preparedness Plans
Book #1 from a computing standards body:
“STANDARD DATA FORMAT FOR FACILITY MAPS”
How to represent generic things in facility map data files
Book #2 from the NFPA:
“STANDARD PRACTICES FOR ELECTRONIC EMERGENCY PLANS”
What to represent and how to embed it in the standard facility map data format in Book #1
m Confidential Facility Map Framework – August 2007 16
Challenges to FMF Vision• Enterprise and marketplace adoption• Ease of use by tactical command and
possibly by mobile devices• Security of sensitive enterprise data and
services• “Handoff problem”
– Responders naming enterprise data sources• FMF is a research project
– Indeterminate timeline!
m Research Facility Map Framework – August 2007 17
Additional Materials
m Research Facility Map Framework – August 2007 18
Facility Map Object Model / FMML
N0 1 2 3
m Research Facility Map Framework – August 2007 19
20
Layout Relationships in FMF
Campus
Building
Room
Rack
Template
AssetLocationsSensor
Georeference
Coplanar
Detail
Parallel
Containment
Cross-Section
Calibration
Replicate
Assets
Prototypes
Instance
Completion
Overlay
Refresh
“Exploded”
Insert
People
Association
m Research Facility Map Framework – August 2007
Application Layers
Applications MS OfficeWeb Sites Web Services
FMUI / ASP(?) FMOWS Server
Facility Map API (FMAPI)
FMML
FMOM Object Model Classes
AssetDatabases
Real-TimeSensing
Tracking &Events
Routing &Wayfinding
FM-SQL OtherProviders
FMOWSClient
Federation
FMML/FTP
FMUI – Rendering, UI Input, External Proxies
m Research Facility Map Framework – August 2007 21
Scenario: The Visiting Technician
• Vendor technician sees route by car & foot
• Map and route connect outdoors & indoors
• Credentials needed to enter building / lab
• Cross floors of building by elevator
• Lab room has detail map by lab manager
• Sensor system tell what is in each slot
• Front view presented to technician
• Computer racks have a generic template
Need to repair a device in a computer rack:
m Research Facility Map Framework – August 2007 22
Scenario: The Warehouse
• Fixed devices and warehouse zones in database
• Equipment and key personnel tracked by active RFID
• Inventory tracked by passive RFID
• All systems integrated on map display
• Map is dashboard for devices, personnel, equipment, inventory
• Linked to LOB software• Goods placement planning• Route planning and traffic control• Unexpected event and exception
detection• History log for analysis
Need to plan and monitor activities:
Reader 8Reader 8
Dock Door A
Status: OK
Gain
Receiving
m Research Facility Map Framework – August 2007 23
• Map is in standard format for use by responders
• Security devices may govern some doors
• Route crosses floors of building by stairs
• Victim may be able to indicate location (X)
• Building sensors, controls, resources are available [1] [2] [3] [4]
• Route around danger areas (red)
• Security videos of the scene can be viewed
• First responder’s location & facing are reported (A)
• Other responders’locations shown (B) (C)
Need to rescue a victim in a building:
Scenario: The First Responder
m Research Facility Map Framework – August 2007 24
The Indoor Location EcosystemArtifacts
Places ofInterest
Own LocationSources
CAD Data
MobileComputers
LocationSystemsCAFM System
PersonalCalendarsBuilding
ManagementCommunication
ApplicationsSpace
Assignments
EmergencyPlans
RoutePlans
LOBApplications Web Services
AssetRosters Operations
ApplicationsAssets /Devices Web Sites
m Research Facility Map Framework – August 2007 25
FMF Enterprise Value Proposition• Value is high due to integration & interop• Increases value of each siloed application• Development costs reduced through
published APIs and shared services• Maintenance costs reduced by data sharing• Cost of entry is low by building naturally
from existing CAD data and services– Target is “a buck a room” to create map data
m Research Facility Map Framework – August 2007 26
Design Criteria for FMF• Object model is application-independent and location-
independent• High level of built-in functionality (routing, render / UI, …)• Embrace existing drawings, data stores, and servers• Loadable unit is the file (= “map”) so OS can do the
heavy lifting• Anything in one file can be split into multiple files• Everything in object model is optional• Anything static can be dynamic• Layered articulation points (from C# to plug-in to web
service)• File size minimized by factoring out common elements• (future) Adherence to relevant industry standards
m Research Facility Map Framework – August 2007 27
Additional FMF Features• Name and ID Dictionaries
– Dictionary Delegation for conglomerates– “ItIs” for substitutions (e.g. GLN, URN)
• References to Map Objects– Self-describing through “map type” field
• Rendering by assigning Styles to objects– FMUI adds “dashboard” functionality to map
• Route Planning– Open Spaces, Transports, and Credentials
m Research Facility Map Framework – August 2007 28
Inputs and OutputsMap Providers
29
• FMML rw• FM-SQL rw• FM-VISIO r(w)• FMOWS r• FMML over FTP r• IAI IFC / aecXML r(w)• Bitmap image r• Excel / Text r(w)
Renderers• FMUI
– Windows Control– Windows Form– Windows Mobile
Form– Web page… ?
• SVG• Bitmap image• VISIO• XAML / WPF
FMAPI
m Research Facility Map Framework – August 2007
Facility Map FrameworkTechnology Roadmap
FMAN MapManager
FMML MapRepository
Web / FTPExternal
Map Portal
FMMLSnapshot
Real-Time Sensing
FMOWSProvider
FMEDMap Editor
Asset DatabasesCAD / VISIO Drawings / CAFM
FM-VISIODrawings
Own Location
Facility Map API
Facility Map Object Model
Ren
der
Rou
te
Find
Impo
rt
UI
Eve
nts
Con
trol
M1
M2
M3
M4
M5
M6
MS Atlas“Dogfood”
FMAM AssetMapper
m Research Facility Map Framework – August 2007 30