The Scenario: Different Ecology databases, tracking many of the same facilities, are being linked together into the Facility/Site Identification System (F/S System). As part of the linking process, someone is trying to enter a new or ‘candidate’ facility in the F/S System. The Data Migration Engine (DME) first does its work and finds a possible match with an existing facility already in the system (in ‘production’). There’s a discrepancy between the candidate’s name (or some other ID data element) and the name in the production system. By most accounts (name, location, lat/long, facility address, mailing address, etc.), they look to be the same facility. Assuming they are the same facility…
The Goal:
The Protocol: Who does the sleuthing? The person initially trying to enter the new record is to do the sleuthing. This person is assumed to be working with a ‘candidate’ record (within the DME), trying to match it with a facility record already found in the F/S System (production). This person will take the lead in reconciling that particular record. This data discrepancy detective will be referred to as the ‘reconciler’. The reconciler must be well versed in the F/S System’s naming/address standards before beginning the following process. Contact Ecology’s current Database Administrator for more about these standards, if necessary.
It will be the responsibility of the others contacted by the reconciler to search for a more recent document from the same facility (within their own respective files). If found, the others must reply right away (phone or e-mail) and provide a copy of the document (item in question) to the reconciler as soon as possible, again, only if it is more recent that the one cited by the reconciler.
***(How much time should be allowed for this step? A day? A week? More?)***
The most recent document from the participating programs will be determined by the reconciler, and will be considered the most accurate source to be used for the F/S System. The program holding the most recent document will be responsible for updating the appropriate information in the F/S System as soon as possible. Make sure to notify the other programs of any changes made, as described in steps 2, 5, and 6. The reconciler will update their own candidate record accordingly.
If an ID data discrepancy still exists . . . it will likely be due to two or more inconsistent documents from the same facility, from approximately the same time (dates may not match exactly). So, at the reconciler’s discretion . . . (otherwise, the most recent date rule will apply.)
Explain the discrepancy (cite conflicting documents) to the facility contact and ask how they want to resolve it -–exactly. The facility has the final word on their name. We will shorten the facility name only if it is too long to fit, and then only by abbreviations already noted within Ecology’s standards, if possible. Ecology’s mailing address standards will be applied unless there’s an agreed upon (and documented) reason not to by the Resolution Group.
While speaking with the facility contact, read the proposed resolution back, confirming the spelling/numbers in question. Keep a written record of the conversation and resolved item as it should be in the F/S System. This must include: (a) the contact person’s name; (b) contact person’s position in the facility; (c) your (reconciler’s) name; and (d) the date. It will be the reconciler’s responsibility to update the F/S System as soon as possible, if the change is based on such a call to the facility.
In Summary . . . the key to the success of this process will be clear and timely communication within the Resolution Group. Many discrepancies are expected. Data discrepancies are not to be taken as a reflection on any individual or program. Teamwork is critical here. Resolution is based on documents from, or contact with, the facility/company in question. Personal judgment should be avoided. Questions, which will surely arise, should be addressed first by this protocol and secondly by the Resolution Group, as a team. The entire group will be responsible for testing, using, and improving this protocol!
|
TCP |
||
|
SWRO |
Tara Davis |
(360) 407-6240 |
|
NWRO |
Gayle Garbush |
(425) 649-4426 |
|
ERO |
Roque Nalley |
(509) 625-5193 |
|
CRO |
Debra Kroon |
(509) 454-7842 |
|
HQ |
Gail Jaskar |
(360) 407-7225 |
|
HQ (UST) |
Lisa Shriver |
(360) 407-7023 |
|
AIR QUALITY |
||
|
ALL |
Sally Otterson |
(360) 407-6806 |
|
ERO |
Lori Rodrequez |
(509) 456-2719 |
|
CRO |
Chrissie Phelps |
(509) 454-7898 |
|
HWTR |
||
|
ALL |
Sheri Dotson |
(360) 407-7555 |
|
TRI |
Idell Hansen |
(360) 407-6727 |
|
WATER QUALITY |
||
|
SWRO |
Carey Cholski |
(360) 407-6280 |
|
NWRO |
Tricia Miller |
(425) 649-7201 |
|
ERO |
Cynthia Wall |
(509) 456-6310 |
|
CRO |
Joe Ortiz |
(509) 457-7148 |
|
WATER RESOURCES |
||
|
HQ (DAMS) |
Doug Johnson |
(360) 407-6623 |
|
HQ (DAMS) |
Dave Cummings |
(360) 407-6620 |