Please enable JavaScript.
Coggle requires JavaScript to display documents.
WAYFINDING HQ DATABASE WEBSITE (leadership/users (SFO musuem rep (wants to…
WAYFINDING HQ DATABASE WEBSITE
Library (static, approved info)
design review process guidelines
ordinances and city law
sign index
GIS data
sign family
sign material
sign language
nomenclature standards
FAQ section
templates/resources/download-ables (login protected?)
map library
typography assets
CAD library of all signs
iconography assets
manufacturing data sheets
installation fact sheets
language translations
graphic templates
leadership/users
SFO musuem rep
wants to suggest art as wayfinding?
Guest experience rep
wants to comment/edit be a part of process
communications & marketing rep
wants to comment, ensure airport brand is maintained
IIM rep
owns GIS data, needs to update/add easily
Operations/Terminal Logistics rep
"police" of sorts, (boots on the ground) facilitates sign change & installation
IT rep
wants rapid change, smart systems, forward thinking
Planning and Environmental rep
forward thinking, trends, analysis, environmental, plan for 2029!
Traffic, Roadways, & Parking rep
wants to suggest additions
Reprographics rep
wants SPEED to update and make changes
REACH rep
wants to ensure standards are followed
ideology
principles
best practices
what we are not
Looking Ahead (sustain)
trends in wayfinding (could this be a blog?)
general plans for renovation (latest updates, whats coming next)
environmental challenges
specific plans for whats next (login protected?)
maps of focus areas
order of work to be done, calendar
questions
if a sign is in flux (design, review, etc), where will it live? Currently, we have a planning area and a library of approved info. Where might an "in process" sign live?
how long will City ID help us with this process of building a database? Until its up and running? Until we have a rough plan? Will we hire someone else?
Will everyone have the same level of permissions? I think so. This is an open access, open source sort of database. More private info to be exchanged internally
should this be an app for on the field updates? Does GIS have this capability already?
Should this whole website be a chapter under a "Design and Construction" handbook on the SFO site?
how much of this info is private and how much is public info? LAX has a very public sort of arrangement...
people want to comment, advise on the process. Should that only happen in the meetings, or should it be an option here, digitally?