Laserfiche WebLink
Work management, Computerized <br />Maintenance Management System <br />(CMMS) <br />Performance measurement and <br />reporting <br />As -is asset characterization sheets <br />describing each asset the City manages. <br />Information will describe the asset, asset <br />custodian, current life -cycle management <br />practices, known deficiencies, systems <br />used for managing the assets, listing of <br />reference documents (CIP, master plans, <br />etc.), and other pertinent data <br />EAM opportunity areas and applications <br />Needs assessment participants <br />Deliverable <br />Aggregate PWA Needs Assessment Report <br />(MS Word, PDF) <br />PWA asset inventory data (MS Word, PDF) <br />Task 3. Enterprise Asset Management <br />System Design <br />Based on our current understanding of the <br />City's IT infrastructure (Le,, supporting GIS), we <br />assume the technology infrastructure currently <br />deployed in support of asset management is <br />not sufficient to support enterprise -level EAMS <br />implementation. One of the key strategic <br />initiatives will be to address this gap based <br />on our assessment of the system hardware, <br />software, data repository, necessary resources, <br />training, and governance required for sustained <br />operations. <br />V. Develop Conceptual EAMS Database <br />Design — Psomas will develop a conceptual <br />design of the EAMS data repository based <br />on industry best practices and available <br />templates. The conceptual database <br />design will define relationships between <br />data and systems for the envisioned <br />EAM. Components of the design will <br />include asset registry, asset condition data <br />(CCTV, inspection records, etc.), strategic <br />prioritization, criticality, consequence of <br />failure, future demand, work management <br />and work history, fiscal tracking, CIP, staff <br />qualifications and training, service requests <br />and complaints, and level of service goals <br />and trends. <br />The design will be presented graphically <br />and supplemented with a succinct <br />narrative to explain the components and <br />their importance. Information systems are <br />referenced as it is expected that the EAM <br />will integrate with some existing systems <br />and data stores. <br />3.2. Develop EAMS Technology <br />Recommendations — Psomas will identify <br />technology recommendations to address <br />the following categories requested in <br />the RFP. Increasingly, EAM offerings <br />are moving to cloud hosted services <br />that present IT configuration alternatives <br />that have minimal impact on the City IT <br />infrastructure. We will present alternative <br />configurations considering both hosted <br />services and on premise installation of EAM <br />solutions, <br />• il' infrastructure configuration <br />• EAMS server requirements <br />• EAMS data repository and maintenance <br />policies <br />• Mobile data management and mobile <br />equipment alternatives for field workforce <br />enablement <br />• EAMS governance, operations, and <br />technical support <br />4.3. Develop EAM System Design Document- <br />Psomas will compile the design and <br />recommendations to produce the system <br />design document. <br />Dolivviahlu; <br />Conceptual database design (MS Visio, PDF) <br />EAMS System Design Document <br />(MS Word, PDF) <br />Task 4. Implementation Plan and <br />Final Presentation <br />The implementation plan will incorporate <br />strategic initiatives and expand on the plan to <br />define implementation "projects," sequences, <br />aggregate resource needs and costs by year, <br />i's O M AS <br />251 -72 <br />