Judy Windle Sunflower Systems How to Clean Up Your Property Data: From Plan to Execution.

Slides:



Advertisements
Similar presentations
SHOW ME THE MONEY BUDGETING 101.
Advertisements

Internal Controls Becoming Compliant. Design & Implementation of Internal Controls. Design: Need to show that a framework is in place to establish internal.
Department Spotlight: The Operating Room (OR) Data Problem As much as 40 percent of a hospital’s budget goes to OR expenses, specifically, the cost of.
How to Document A Business Management System
Performance Appraisal System Update
Performance Appraisal in the Public Sector
Chapter 4 IDENTIFYING RISKS AND CONTROLS IN BUSINESS PROCESSES
Software Project Transition Planning
Unit 8: Tests, Training, and Exercises Unit Introduction and Overview Unit objectives:  Define and explain the terms tests, training, and exercises. 
Job Order Costing Systems
Project Management Session 7
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems Introduction to Hewlett Packard (HP) Application Lifecycle Management.
19 Costing Systems: Process Costing Principles of Accounting 12e
Chapter 4 IDENTIFYING RISKS AND CONTROLS IN BUSINESS PROCESSES.
Asset management guidelines
Troy Eversen | 19 May 2015 Data Integrity Workshop.
UNLV Data Governance Executive Sponsors Meeting Office of Institutional Analysis and Planning August 29, 2006.
000000_1 Confidential and proprietary information of Ingram Micro Inc. — Do not distribute or duplicate without Ingram Micro's express written permission.
Improving Data Quality Best practices for entering and maintaining data.
Guidelines 4-6 Developing a file plan for government agencies Tuvalu Government Filing Manual Funafuti, Tuvalu June 2013 There are three guidelines in.
Office of the Under Secretary of Defense (Comptroller) Physical Inventory Best Practices 1 Briefing for Joint Physical Inventory Working Group September.
Professional Development Plan Externship Contact Hours Tracking.
Agenda 1. Definition and Purpose of Data Governance
Integrated Capability Maturity Model (CMMI)
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Unit 5:Elements of A Viable COOP Capability (cont.)  Define and explain the terms tests, training, and exercises (TT&E)  Explain the importance of a.
Data Integrity Soup to Nuts Skip Adolph, CPPM, CF Judy Windle, CPPS.
MEASUREMENT PLAN SOFTWARE MEASUREMENT & ANALYSIS Team Assignment 15
Imaging, Document Management and the Future Nick Zinser Northeastern University Jim Slattery The College Board MASFAA Conference 2002.
- 1 - Roadmap to Re-aligning the Customer Master with Oracle's TCA Northern California OAUG March 7, 2005.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
Information Systems Security Operational Control for Information Security.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
C6 Databases. 2 Traditional file environment Data Redundancy and Inconsistency: –Data redundancy: The presence of duplicate data in multiple data files.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Analyzing Systems Using Data Dictionaries Systems Analysis and Design, 8e Kendall.
Webinar for FY 2011 i3 Grantees February 9, 2012 Fiscal Oversight of i3 Grants Erin McHughJames Evans, CPA, CGFM, CGMA Office of Innovation and Improvement.
5-1 Lesson 5 | Common Issues & Challenges. Describe how RSAs address project schedule (time), project cost, and agency liability concerns. Explain the.
Subcommittee on Design New Strategies for Cost Estimating Research on Cost Estimating and Management NCHRP Project 8-49 Annual Meeting Orlando, Florida.
© British Telecommunications plc Senior Engineer Review Field, Plan and Build.
Michael Campe U.S. Army Aviation and Missile Command NDIA TID Technical Information Division Symposium Royal Sonesta Hotel, New Orleans, LA August 2003.
Information System Project Management Lecture three Chapter one
Safety Management System Implementation Michael Niels Thorsen Moscow 15 September 2005.
Adjustments and the Ten-Column Work Sheet Making Accounting Relevant Financial data must be communicated properly before it can be used effectively. Making.
Networked Systems Survivability CERT ® Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA © 2002 Carnegie.
Digital recordkeeping strategy for mobile work processes Joel Smith HPRM System Administrator.
Metadata By N.Gopinath AP/CSE Metadata and it’s role in the lifecycle. The collection, maintenance, and deployment of metadata Metadata and tool integration.
Financial Management and Budgeting The Details. What Is a Budget? A useful tool for keeping track of funds. A useful tool for keeping track of funds.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
MOD Form 3 Register of Supply Action. Purpose: –Used by both supported and the supporting unit. Supporting units use it as a voucher register for a Stock.
Prepared By: Razif Razali 1 TMK 264: COMPUTER SECURITY CHAPTER SIX : ADMINISTERING SECURITY.
IT-465 Introduction to Lean part Two. IT-465 Lean Manufacturing2 Introduction Waste Walks and Spaghetti Charts Outcomes Understand what a waste walk is.
Preparation Plan. Objectives Describe the role and importance of a preparation plan. Describe the key contents of a preparation plan. Identify and discuss.
Information Resource Stewardship A suggested approach for managing the critical information assets of the organization.
Adjustments and the Ten-Column Work Sheet Making Accounting Relevant Financial data must be communicated properly before it can be used effectively. Making.
Leadership Guide for Strategic Information Management Leadership Guide for Strategic Information Management for State DOTs NCHRP Project Information.
6 th Annual Focus Users’ Conference 6 th Annual Focus Users’ Conference ERP Fixed Assets ERP Fixed Assets Presented by: Will Brock ERP Programmer PowerPoint.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
The Project Management Process Groups
Welcome. Contents: 1.Organization’s Policies & Procedure 2.Internal Controls 3.Manager’s Financial Role 4.Procurement Process 5.Monthly Financial Report.
EECS David C. Chan1 Computer Security Management Session 1 How IT Affects Risks and Assurance.
Chapter 11 Project Management.
Each Storyboard should consist of 5 slides:
Overview – Guide to Developing Safety Improvement Plan
PEFA 2016 Slides selected from the training materials of the PEFA secretariat.
Overview – Guide to Developing Safety Improvement Plan
Project Initiatives Identified by the CIA Project
PEFA 2016 Slides selected from the training materials of the PEFA secretariat.
Project Management Chapter 11.
Capital Assets Through the Eyes of an Auditor
Each Storyboard should consist of 5 slides:
Presentation transcript:

Judy Windle Sunflower Systems How to Clean Up Your Property Data: From Plan to Execution

Purpose To describe how to address data cleanup challenges To present steps required to effectively plan and clean up property data To review an Asset Catalog example To describe how to maintain clean, consistent data

Overview Understand how to achieve the following cleanup steps:  Address the challenge  Create a plan  Execute and Manage  Maintain policies and procedures Keeping data accurate, consistent and reportable is the key to success!!

Address the Challenge Begin with the following suggested questions:  Is there one, centralized office driving polices, procedures and guidance on how to manage and track property?  Do the property managers and custodians understand the importance of entering clean, precise data into a property management system? Are they motivated?  What are the weaknesses of your property management system?

Address the Challenge “If you take care of the small things, the big things will take care of themselves.” Lets focus on the weaknesses… Step 1: Recognize the need for data cleanup Step 2: Understand the importance of a cleanup effort Step 3: Identify the cause behind the inconsistencies

Create a Plan Step 1: Assign one, centralized office or person to lead the cleanup effort Step 2: Establish uniform naming conventions  This will drive consistency and accuracy Step 3: Develop training and education processes  Train and re-train users on how to use the system properly  Educate users on the new or updated naming conventions  Plan weekly, for example, meetings with system users to discuss concerns, questions, ideas, etc.

Create a Plan cont. Step 4: Prepare to analyze the data  Assign resources  Understand the amount of data you may have to clean up  Plan how to organize the data Step 5: Define the scope  Determine the number of users that need to be trained on the system and educated on the new naming conventions  Decide what problem area (s) you want to focus on (if not all)  Define a timeframe

Create a Plan cont. Step 6: Document…Document…Document  Document the following:  The centralized office or person leading the effort  Naming convention (s) or guidance (e.g. ASTM standards)  Training and education processes and manuals Determine where the manuals can be found Determine who will train and what users (in general) Training schedules Weekly meeting platform

Create a Plan cont.  Document cont.  Scope involved to implement the cleanup Why conduct a cleanup effort What problem areas and how much [data] The amount of time expected Anticipated risks and assumptions  Approach Who is carrying out the effort How to analyze the data How to execute the cleanup process  Maintenance Strategy How to keep data intact Who will update all of the above

Execute: The Cleanup Step 1: Complete all steps in the “Create a Plan” phase Step 2: Once the plan is documented, start to train and educate users as the cleanup effort begins Step 3: Analyze the data  If limited resources are available, focus on one problem area at a time  Assuming a technical resource is available, multiple queries should be run organizing data into categories (e.g. asset catalog, accountability, locations, etc.)

Execute: The Cleanup cont. Step 4: Execute the cleanup  Once all categories are organized and broken down into elements or levels, it is time to clean up  Key steps to follow:  Eliminate duplicate entries  Correct misspellings  Adjust entries to reflect new naming convention  Map asset records to correct entries

Execute: The Cleanup cont. Step 5: Wrap up!  Re-run all queries  Review categories along with each level  Make adjustments and correct discrepancies  Repeat until desired outcome is achieved

Asset Catalog  Cleanup category example: Asset Catalog  What is an asset catalog? The metadata below are suggestions and are not limited to the following:  Core data elements: Manufacturer Model Number Model Name Description

Asset Catalog  Additional data elements to consider: Federal Supply Classification (FSC) Part number Stock Number Unit of measure

Asset Catalog Asset Catalog Cleanup  Manufacturer :  Eliminate all duplicates and correct misspelled manufacturers  Map all assets to the correct manufacturer HEWLETT PACKARD HEWLETT-PACKARD HP HEWLETT PACKERD HEWLET PAC HPC HPACKARD HEWLETT PACKHARD

Asset Catalog Asset Catalog Cleanup  Model Number/Name:  Eliminate all duplicate entries specific to each manufacturer  Correct inaccurate entries to follow the naming convention

Asset Catalog Asset Catalog Cleanup  Model Number/Name cont.:  Decide if the model number column or field should include the model name (e.g. Latitude E4310 or E4310)  Model name can be included in a additional field or column  Map all assets reflecting eliminated models to the correct models

Asset Catalog Asset Catalog Cleanup  Description:  Eliminate all duplicates, misspellings and “like” entries  Decide if the common denominator should be labeled first  Map assets to the correct description  Federal Supply Classification (FSC)  Correct all FSC discrepancies  In general, the same descriptions should have the same FSCs

Maintain  Lessons learned  Knowledge transfer  Continue to train system users  Continue to educate and enforce naming conventions  Consider list of value data fields  Continue to host weekly meetings  Run queries on an annual basis (for example)

Summary Understand the BIG picture Balance structure, flexibility and usability of the system Property data should be…  Descriptive  Standard  Reportable Review  Address the Challenge  Create a Plan  Execute and Manage  Maintain

Questions/Comments ???