IAM at PMV: Past, Present, Future & Lessons Learned - staging.files ...

IAM at PMV:Past, Present, Future &Lessons LearnedMo MofradGary Toshp o r t m e t r o v a n c o u v e r.c o m

PMV’s IAM History• Start: 2009• Port-owned asset definition and identification• A two year process• Lessons• Background data: ownership, drawings, inspections,photos, etc.• Scope definition: What matters to your Port?• Docks, Roads, Buildings, Services, less/more?• Relax, data will always be missing; 80/20 rule• Fixed Asset Ledger: useful but beware, new assetsvs. upgradesp o r t m e t r o v a n c o u v e r.c o m

PMV’s IAM History• 730 assets in 14 asset classes• Data recorded in Excel for eventual database• Lesson: Consult departments for their data needs• Baseline inspection performed for each asset• Inspected in-person or by ‘table-top’ Q&A• Lesson: Consistency• Five-year plan for in-depth inspections• Based: age, inspection history and critical nature.• Lesson: Review after inspections, alter as requiredp o r t m e t r o v a n c o u v e r.c o m

PMV’s IAM History• Functional Requirements for IAM software• What affected departments need, should and wantto see from AM software• Lesson: Google• 98% of PMV assets in GIS• Searchable by unique Asset ID• To come: Baseline condition rating (VG, G, F, P, VP)• Lesson: Goal attained? show it off.• IAM Directive• Draft completed• For program success, AM cannot be optional.p o r t m e t r o v a n c o u v e r.c o m

PMV’s IAM Present & Future• Gap Analysis• Issue: Asset information sharing within PMV• Multiple dept’s acquire/maintain/divest assets• Goal: Identify information gaps and recommendnew processes between key departments whoacquire/maintain/divest infrastructure assets• GIS-centered IAM Software• Existing asset locations (macro)• Deficiency/Issue locations within the asset (micro)• Hyperlinked drill-down for as-built drawings, photos,report details, etc.• Location referencing for consistent future inspectionsp o r t m e t r o v a n c o u v e r.c o m