Asset Management Database Clause Samples
Asset Management Database. (1) The Town will provide the Contractor with a list of Residential Service Units that includes the parcel folio number, address, and number of Residential Service Units on each parcel. Contractor shall use this list to develop and maintain an asset management database through which Contractor shall be responsible for reporting and tracking the movement of all Carts used for Residential Collection Service, including deliveries, removals, exchanges, repairs, warranty recovery, and any other information necessary to manage Cart assets, subject to Town approval. The database shall also specify the route for each Residential Service Unit and shall be in a format that is searchable by the Administrator. The initial database must be populated and transmitted to the Administrator in accordance with the approved Transition Plan. All database adjustments must be made within forty-eight (48) hours of physical inventory exchange and completion of work order. If a Cart is swapped out, data for the Cart removed and the Cart replaced is to be provided. Data fields shall include, but not be limited to the following:
(a) Work order number, date, and status
(b) Residential Service Unit name/ID and address
(c) Parcel folio number (as provided by the Town)
(d) For each Cart at each Residential Service Unit, the type (Solid Waste or Recycling), size, serial number, and RFID chip identifier (as applicable)
(e) Routes on which the Residential Service Unit is serviced
(2) Contractor shall provide the Administrator with an updated copy of the asset management database monthly, as well as access upon request.
Asset Management Database.
1) The City will provide the Contractor with a list of Residential Customers that includes the parcel folio number, address, and number of Dwelling Units on each parcel. Contractor shall use this list to develop and maintain an asset management database through which Contractor shall be responsible for reporting and tracking the movement of all Carts used for Residential Collection Service, including deliveries, removals, repairs, replacements, warranty recovery, and any other information necessary to manage Cart assets, subject to City approval. The database shall also specify the route for each Residential Customer and shall be in a format that is searchable by the Administrator. The initial database must be populated and transmitted to the Administrator in accordance with the approved Transition Plan. All database adjustments must be made within forty-eight (48) hours of physical inventory change and completion of work order. Data fields shall include, but not be limited to the following:
(a) Work order number, date, and status
(b) Residential Customer name/ID and address (c) Parcel folio number (as provided by the City)
Asset Management Database. Collect physical and historical tank information • Determine database software and best uses • Compile data into asset management database • Evaluate tank data 🌢 Risk Assessment • Develop criteria for risk assessment • Determine tank probability of failure and consequence of failure • Evaluate risk for tanks • Prioritize tanks improvements �� Regulatory Requirements • Review regulatory requirements for tankage • Confirm tanks meet regulatory requirements • Recommend improvements to meet or exceed requirements 🌢 Computerized Maintenance Management System (CMMS) • Review City’s CMMS and reporting for tanks • Coordinate/incorporate existing and new data from the Storage Tank Engineering services in the City’s CMMS • Assist with improvements to City’s CMMS and reporting 🌢 Standard Operating Procedures (SOP)s • Review/evaluate existing tank SOPs • Update existing tank SOPs • Create new tank SOPs 🌢 Standard Specifications • Review/evaluate existing tank specifications • Update existing tank standard specifications for tank maintenance and repair • Develop new tank standard specifications 🌢 Spill Prevention, Control and Countermeasure (SPCC) • Review/evaluate existing fuel tank SPCC documents • Update existing fuel tank SPCC protocol documents • Develop new fuel tank SPCC documents 🌢 Recommend and complete needed survey 🌢 Recommend and complete needed geotechnical investigations and materials testing 🌢 Recommended and design needed tank improvements including structural, electrical/I&I, painting/coatings, civil and other tank improvements �� Prepare design drawings and technical specifications for recommended/needed tank improvements 🌢 Assist with bidding for recommended/needed improvements 🌢 Provide construction administration, oversight, Engineer of Record and inspection services for recommended/needed tank improvements 🌢 Determine probable construction cost for tank projects 🌢 Recommend and forecast annual budgets for tank projects 🌢 Develop a STAMP which may include any or all reports, standard documents, specific documents, evaluations, assessments, cost and budget information and recommendations developed through this project 🌢 Update the STAMP annually with progress from the previous year 🌢 Follow guidelines set by ASTM’s Standard Practice of Hydraulic leak testing ASTM E1003-13 (EO7.08)
Asset Management Database. (a) The Asset Management Database must be up to date at all times and may be examined by the Crown at any time upon reasonable notice.
(b) In accordance with clause 37, the Crown may conduct an audit of the Equipment and the Asset Management Database at any time upon reasonable notice to the Contractor.
Asset Management Database. A database that is hosted and maintained by Xerox to facilitate the XPS Services and record anrodvpide reporting on Managed Device activities.
Asset Management Database. ESI will establish or provide access to a database of spare equipment and their statuses for major assets (e.g. CCTV cameras). ESI should continue identifying all spare equipment on vehicles and in warehouses, making swapped equipment easy to track and identify. If an asset database is not previously available, once the database is set up, C/CAG should have access to view the asset information in real- time. The database does not need to be set up when the PMP is submitted, but the PMP should detail the process to establishing the database.