Revisions to be Carried Forward into other City Protocol Work

January 2015

Comment reference: City Anatomy – Public Review Response

Comment # REVISION TO BE CARRIED FORWARD

#2 Create a “Referenced Standards” section in the Editor’s template for all CPA
documents.
#3 Identify a select set of terms defined in City Anatomy that are intended to become
part of the “Common Language” of City Protocol. Direct these terms to the Editor to
define in a CPA Glossary document.
#5, 6, 7 The CPTSC has decided to create a City Protocol Knowledge Base, utilizing a CMS
(Content Management System) tool. This system will refer to the formal CPA Library,
but it will also allow for content that is outside of the space of formal CP
Agreements.
The City Protocol knowledge base is proposed in order to (1) express dynamic cross-
linkages between CPA documents, (2) bring many cross-sector players to the City
Protocol table and begin to use a common language to describe the work they have
done or are doing, ie, the state-of-the-art, (3) provide input material for TAFT work,
(4) create a useful and collaboratively-created knowledge-base for cities and (5)
begin to shape and document a range of meanings for “CP-compliance”.
#9 Develop the City Aspirational Models language, and add it to the CP Glossary
#14, 38 Ranges of “CP-Compliance” need to be defined. This is a task for the CPTSC; its use
may become part of the City Protocol knowledge base.
#17 Create an “Audience” section in the Editor’s template for all CPA documents
#21 Define “Protocol” as we intend it (consult CPTSC for assistance), and add it to the
CPA Glossary.
#26 Consider doing the following: Drive the creation of one or more TAFTs whose
purpose is to identify key common areas of dysfunction and/or opportunity for each
area of City Anatomy, and develop that as a companion piece to City Anatomy.
#31 Subsystem interconnection needs to be addressed in the context of each specific
TAFT topic. Create an “Systems Interconnections” section in the Editor’s template
for all CPA documents
#32 Consider a comparison between the CA and the draft BSI Overview maturity model
#40 Suggest these “flow” dimensions be the topic of other TAFT work
#60 Create an online version of “City Anatomy” that allows people to zoom in on the
detail. Perhaps include a City Anatomy “map” which can be hot-linked to the City
Protocol Agreements library and CP knowledge base…….
#65 Create an “Evaluation” section in the Editor’s template for all CPA documents, which,
among other things, identifies KPIs from the City Protocol indicators pool.
#66 Evolve the “Smart City Framework”, in collaboration with City Protocol partner, the
Smart Cities Council whose work this framework builds on.
#66 The suggested “subject x subject x subject” analysis would be valuable in the context
of working with CP Member IESE’s work on City Indices.