My WebLink
|
Help
|
About
|
Sign Out
11
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2021
>
072021
>
11
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/15/2021 12:25:09 PM
Creation date
7/15/2021 12:25:05 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
7/20/2021
DESTRUCT DATE
15Y
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
28
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
We will start this Task with a half-hour phone interview with the OSD's GIS Analyst to understand the GIS <br /> in its current state and the processes handled by the GIS Department. Following the phone call, should we <br /> have additional question,we will try to follow up via email or may require an additional phone call depending <br /> on what is found. <br /> GHD's review of the OSD's GIS will include: <br /> — An evaluation of the existing GIS Data Model including features, objects, fields, domains and <br /> relationships(overall data standards) <br /> — A review of available metadata <br /> — A review of any network utilities and their connectivity <br /> — Naming conventions <br /> — QA/QC standards <br /> — Mobile/Field GIS standards <br /> — Application standards <br /> — Data collection standards <br /> — Data storage(i.e.,what should be in a central database and what could be stored locally/shared network <br /> location like project-specific data) <br /> — Comparison of the GIS data structure to the MaintStar asset table data structure to identify gaps <br /> Subtask 3.2: Schema Recommendations for Asset Management and CMMS <br /> GHD has a long history with asset management, and as such,we have taken advantage of that knowledge <br /> and combined it with our GIS schema for alignment. This is most advantageous when utilizing the GIS in <br /> CMMS/EAMS or importing the data into Decision Support Systems as the Asset Management Framework <br /> already exists on the asset. The GIS review performed in subtask 3.1 will provide the foundation from which <br /> we can build our GIS schema recommendations for Asset Management. In addition, we will provide other <br /> schema recommendations that may be related to: <br /> — Nameplate data/Attributes—i.e.: Specification templates <br /> — Hierarchy(Parent/Child relationships) <br /> — Standardized naming conventions <br /> — Criticality <br /> — Asset types/Asset classes <br /> — Closing data structure gaps between GIS and the MaintStar asset table data structure <br /> Upon completion of subtasks 3.1 and 3.2,we will prepare a Summary of Findings and Schema <br /> Recommendations technical memo. <br /> Optional Task 3: City Roles and Responsibilities <br /> — Site access to or a copy of the OSD's most recent Geodatabase(x-ray is fine) <br /> — Half hour meeting time with the GIS Analyst to discuss overall GIS structure and process, more time <br /> may be asked if we have follow-up questions <br /> Optional Task 3: Deliverables <br /> — Conduct a half-hour phone meeting with the GIS Analyst to gain an overall understanding of the GIS in <br /> its current state and the overall processes that occur in that Department <br /> — Preparation of a Summary of Findings and Schema Recommendations Technical Memo based on our <br /> discoveries from subtasks 3.1 and 3.2 <br /> The Power of Commitment <br /> 11227916 I Proposal for Workflow Development&Integration into MaintStar CMMS Scope Update and Fee 5 <br />
The URL can be used to link to this page
Your browser does not support the video tag.