Charlotte County 2050
Comprehensive Plan System
Growth Management Department
UCF Project Manager
UCF Technical Consultant
UCF Business Process Analyst
Charlotte County Growth Management Department
Vision .............................................................................................................................. 3
Communications ............................................................................................................. 3
Stakeholder Analysis ...................................................................................................... 4
Expectations .................................................................................................................... 8
Contact Information ...................................................................................................... 13
Charlotte 2050 Comprehensive Plan
The Charlotte 2050 Comprehensive Plan project has as a Vision a “Long term
engagement of the citizenry in the development and execution of the plan”. Special
interests are currently the primary group that takes an interest in the plan based on
interest. This desired shift is to the overall the engagement of the citizenry.
1. There will be weekly update and nudge to review new items. It is an email with the
information to review, the timeline, and the information about who to send the
2. Charlotte County will hold the software
3. There will be a weekly SourceSafe upload
4. There will be a weekly Test upload, and test and deploy script
5. The test scripts will be uploaded into the Sage Wiki site for everyone to see
6. Charlotte County will have the last word about going from testing to production
7. There will be weekly production cycle
*Charlotte County will assign a server and domain for the software.
Stakeholder Interest Type * Commitment
- Plan maintenance, coordination, and facilitation
- Primary users of the Com plan
Growth Management Staff
- Enforcement, interpretation, and implementation P
- 33 staff
- Desire long term engagement of citizenry
- Users of plan (for decision making)
- Final arbitrator of plan P
- 5 County Commissioners
- Desire direct influence on the plan
- Personal interests in developing properties
- Seasonal population interest in level of service
- Direct interest in county growth
- Interest in parks, recreation and facilities
- Desire predictability and consistency of plan
- Interest in the process of planning and best
- Interest in organization and content of the plan
- Desire predictability and protections from plan S
- Have a high level of ownership in the overall
- Public Works
- Parks and Recreation
- True ownership of each department part of the
- Environmental Resources P
- Development of the plan and acting as experts for
- Economic Development
the details for portions of the plan
- Emergency Management
- Information Technology
- Review agency for plan
- Approval authority
State Agencies (DCA) - Early buy-in from DCA necessary P
- State comprehensive plan with goals are input to
the local plan
- Foundations of the plan are based in Federal law,
which is implemented in state law
Federal Government S
- Plan compliance must cover state and federal
- Very similar to BCC interests
Constitutional Offices - Growth management and planning issues based
- Clerk of Courts on plan
- Tax Collector - Population and resource allocation based on
- Property Appraiser plan. P
- Sheriff’s Office - Increased capability through planning process
- Supervisor of Elections (crime prevention as example)
- School Board - Prediction of revenues through impact fees
- Not directly involved in implementation
- Regional policies (environmental, economic,
etc.) have impact on surrounding counties
Neighboring Counties and - Land use typically moves to county boundaries,
cities which impacts neighbors
- Transportation networks are impacted regionally
- Have available traffic planning
- Non-legislative planning body
Regional Planning Councils
- Interest in regional planning S
- SW Florida RPC
- Desired acceptance of the plan and process
Cities: - City has an annexation interest
- Punta Gorda - Desire for compatible land uses and integrated S
recreation, emergency, and other services
- City utility service area is beyond the city limits
- Interest in all water uses
Water Management District - SFWMD is involved in low impact development
- SWFWMD standards S
- SFWMD - Need plan participation and acceptance of both
Regional Water Authorities - Interest in LOS and how to meet the LOS
- Peace/Manasota Water - Conservation by mandate (state/federal) as part
Management Authority of plan
- 18 Local Utilities - Regionalism and reservoir management
Local Businesses - Direct involvement with planning
- Via Chamber of Commerce - Economic Development
- Sierra Club
- Coastal Wildlife Club - Preservation of existing state
- Lemon Bay Conservancy - Conversion of existing lands to natural lands S
- 1000 Friends of Florida - Growth limitations
- Audubon Society
- Conservancy of SW
Federal and State
– Charlotte Harbor National
Estuary - Has Charlotte Harbor under federal preservation
- Babcock/Cecil Webb - Has impact on development, natural lands, and S
- Conservation Charlotte preservation
- Babcock Preserve
- Charlotte Harbor buffer
Tourism Department - Promotion of tourism S
- Hotel development
- Been appointed by the BCC to carry out specific
Citizen Advisory Groups P
Planning and Zoning Board - Under the legislation, P&Z actually is the body
(P&Z) responsible for preparation of the Comprehensive P
* Primary: P, Secondary: S
1. The comprehensive plan is a structured document that is organized hierarchically.
The hierarchical structure is maintained by having an embedded link in each system
element to a parent.
SEBaseID – PK of table
SEParentID – FK to SystemElementBaseID, points to parent
SESiblingOrder – A numerical order for the display of system elements.
2. The comprehensive plan will have a main table of contents. The plan will have the
capability of having different table of contents based on user desires or needs.
a. A user can select that they only desire to see elements of the plan relating
to natural resources. They can then filter the TOC to show only those
items that are tagged as dealing with natural resources.
An abstracted table system will handle the table of contents. This will consist of 2 tables;
TableofContents and TableofContentsElement. The TableOfContents table will be the
named table of contents for the document.
TableOfContentsID – PK of table, identity
TOCTitleText – Text name for the table of contents.
StructuredDocumentID – FK to the Structured Document ID defining the document.
TOCTypeCode – MAIN or CUSTOM table of contents.
CreatedByLID – Login ID of user creating TOC
CreatedDate – Datetime of date of creation
Each entry in the table of contents is represented by a TableOfContentsElement. These
must contain a pointer to the primary definition of the TOC and also to the element that is
TOCElementID – PK of table
TableOfContentsID – FK to the Table of Contents table
SystemElementBaseID – FK to the System Element
TOCParentID – FK to TOCElementID if not root element, allows TOC to have different
structure than the System elements.
TOCSiblingOrder – Defines the order of the siblings in the TOC
TOCTitleText – Display text of the TOC element.
TOCPrintBit – Bit field to include SE in printout of document.
CreatedByLID – Login ID of user creating TOC element
CreatedDate – Login ID of user creating element
3. The comprehensive plan must have a printable version.
Each system element will have a field as part of the SystemElement table called
IsPrintableBit. The table of contents will also have a print option that will
sequentially print all the TOC elements marked as printable. The logic requires for an
element to be printed only if it meets these conditions.
4. All text elements within the plan must be fully text searchable including basic
All ntext fields will be marked by SQL server as full-text indexed. Use of the SQL
server full text searching capability will be used by the program interface.
5. The users should have the ability to pull materials from the system to create a custom
interface that includes elements from the plan (in summary).
a. Create a single screen called “Urban Service Area” that allows the
management staff to put in bullets and video. (Per example given)
6. Security will have a single comprehensive plan manager who opens and closes and
locks the document elements.
Locked elements can not be edited. The document owner can lock the entire plan by
using an interface that uses the TOC to lock all the elements in the TOC. In this case the
system will parse through all the elements in the TOC and set the SEIsLocked to true for
the SystemElements. They can also lock individual elements separately through a
7. The elements making up the final approved version of the plan will be denoted as
a. The approved comp plan elements will be marked as approved and locked.
b. The users will still have the ability to upload elements, provide feedback,
etc., at all times.
Elements can be added to any element even though the parent element might be locked.
When elements are locked then they will appear as locked elements.
8. The system should have the ability to link all types of system elements; textual,
graphical, video, and map based.
a. Linkages can be created using a “Create Link” and then a select the
element or site that we create the linkage to.
Linkages will be made using the Bookmark table. A linkage is a special case of a
bookmark where “a from” and “to” element are both specified.
SEBookmarkID – PK of table
SEBaseElementID – FK to the bookmarked element
SEBaseElementLinkedID – FK to element in a linkage
BookmarkCommentText – Text representation of bookmark
BookmarkNotifyBit – T/F of whether to be notified on condition specified
BookmarkNotifyConditionCode – Condition to trigger notification
BookmarkPublicBit – T/F on linkage or bookmark made public
CreatedByLID – Login ID of Bookmark creator
CreatedDate – Date of creation
9. Authorized staff will have the ability to enter meta-tags into a list of available
metadata tags. Tags should have different levels; staff, public, etc. and all users
should be able to tag elements with their level of tagging.
All available meta-tags will be entered by an authorized staff member and held in the
MetaTagList table. This table will have a single unique field – MetaTagText.
Actual meta-tags will be stored in the MetaTag table. This table will have a pointer to the
system element being tagged.
MetatagID – PK of table
MetatagText – metatag from meta tag list, FK to list
SEBaseElementID – FK to element tagged.
MetatagTypeCode – Code designating type of meta tag
10. Auto-complete will be used in all fields where appropriate.
Standard part of AJAX interface design.
11. Staff will have a login, public will have an ability to create a login. People with
login will have access to features that require a login.
Users will have the ability to create a public login through the SAGE UMS.
12. Users with logins will have the ability to create bookmarks and personal notes.
See design above – personal notes are a field within the bookmarks.
13. Ability to tag and export elements for reports.
The TOC table allows for the creation of a document for print from any system elements.
Tagging is creating the TOC which will need an interface for a custom creation.
14. Ability to report on what elements have been and not been tagged and how many
Basic query of all system elements and counts of tags and bookmarks.
15. Ability to track logins and produce login stats of how many entries and time on
system users are logging.
16. All public feedback comments must be moderated.
All System Elements have a SEIsReleased that must be set to true to be available to the
public. An interface to set this bit must be developed and also a notification must be set
on all feedback items entered by users to the Charlotte County rep responsible for
releasing the feedback.
17. The system should have the ability to produce reports of public comments.
18. Include embedded help system within the system with instructions on how to use the
Embed SAGE help system.
19. Have the ability to tag elements for notification on changes and items. Also the ability
to be notified on meetings associated with an element.
This will be done through the bookmark.
Name Organization Phone E-mail
Jim Fendrick Charlotte County 941-764-4920 email@example.com
Tom Scott Charlotte County 941-764-4152 firstname.lastname@example.org
Jeff Ruggieri Charlotte County 941-745-1589 Jeff.Ruggieri@chatlottefl.com
Andy Sterms Charlotte County 941-764-4383 email@example.com
Inga Williams Charlotte County 941-7431242 firstname.lastname@example.org
Jeffrey Crimer Charlotte County 941-743-1901 email@example.com
Kevin Edwards Charlotte County 941-764-5507 firstname.lastname@example.org
Jeff Reese Charlotte County 941-764-5505 email@example.com
Andrew McCown Glatting Jackson 407-325-7355 firstname.lastname@example.org
Ron Eaglin UCF 407-497-9213 email@example.com
Karla Moore UCF 407-451-7658 firstname.lastname@example.org
Oscar Martinez UCF 407-823-4419 email@example.com