Update on Selective Editing and Implications for Staff Skills International Trade Conference September 2008 Ken Smart

Background Review of Trade Editing – 2004 Threshold Editing introduced – 2005 Requirement for Selective Editing…

SE methodology in Overseas Trade The suspicion function compares a record to a distribution of values in historical clean data (boundaries are supplied as parameters). The further from the standard deviation, the higher the suspicion value given to the record. The impact function estimates the likely end value if the record was edited and weights this against the published total it feeds into. The higher the weight, the higher the impact value given to the record. The score function combines the suspicion and impact into one number. The higher the number, the more benefit from editing it. The score is added to the actual record, and is used to rank it in a virtual queue.

Background – cont …the plan was: Construct, test and implement Selective Editing – planned for early 2007… …what happened: Developed this year and put into production 21 August 2008!

raw datafix fatal errorsassign errors & warningsauto edits score records rank based on score (virtual queue) present to editors in rank order does the line item have a quantity & history historic benchmarks stored in sybase table parameter settings held in web based user interface noyes apply threshold not presented for editing present to editors in rank order below $5000 above rank based on $ value (virtual queue) Selective editing Threshold editing Selective editing system flow

SE features - editor entry screen Select to receive imports, exports or both Select to receive records from errors queue, selective editing queue, threshold editing queue or all queues Enter date range to receive records for

SE features - web based user interface Manage parameter settings Turn on/off individual warnings View archived parameter sets

Benefits we’re expecting to see over time… Productivity gains - reduction in the number of edits Quality gains - targeted editing Improves error identification & management System improvements by fine tuning of parameters

Selective editing in production… Some aspects (e.g. ‘park’ function) we weren’t able to build but the system has been built so that components can be added Many components built generically – other areas within Stats NZ already interested in the system Many insignificant entries still being edited but time will tell where ‘score’ significance cut off point is Statistical methods staff still ‘tuning the system’ (monitoring parameters) Kept some warnings – ranked by $ value Editors no longer directed to source of possible error…

Identifying errors using selective editing Previously editors were directed to the possible error by specific warnings – now they have to look at the entry as a whole The big difference - editors need to be able to identify how an entry may be faulty Still just as important that editors are able to decide which entries to spend time on Multiple demands on their decision making

Selective editing now and in the future We have a new editing system, which should focus editing where it counts and make time available for better quality editing But… How do we address the changing demands on our editors? How do we continue to measure the effectiveness of the SE processes?

Over to you… What skillsets do you look for in trade editors (and what editing skills become more important with selective editing)? Have you focussed training on any particular areas (for either procedural or technological developments)? How much checking do you do on editors productivity/decision making? What sort of system reporting tools do you use (to make sure the system is performing)?