Data Acquisition Sprint
ABS, CBS, SNZ and STC
International Collaboration Workshop March 23 – 25 2015
Post-it notes transcribed (part 2)
1. Provider management
Relations (1st Pass)
What
Capture o/g information (event MI, preference
agreement, contact) to be used by:
 case management JIT,
 survey management + SFMP + future
sampling,
 channel (help desk, field)
Who
All four. SNZ: Saleforce
Why
Existing solution poor outcomes
Common tool - same problems to solve
COTS products look suitable but need clear
distinction of our statistical business
needs/integration of events
ABS - Provider focus
How
Model/terminology agreement
Shared requirements/outcomes
? Option: Market approach (SNZ) or Build own
(CBS)
When
SNZ - build new release Nov 15
ABS - PoC end 15
CBS - PoC by June 15
Share req's
(2nd pass)
What
Standalone component(s)
service
oriented
Goal is managing the relationship
- info
- events
- surveys
- mode prd
- contact details
- logical framework
- common criteria
Who:
CBS level
How:
Shared PoC approach
CBS: Siebal Exp. Microsol Dynamics - Just CRM
SNZ: Sales Force - case management
ABS: in house build transition. Procure/Pilot PM (relationship)
SC: ICOS, minimum - Product
2. QDT
What
Everything: questions flows, edits.
Not sample CD
(Capture change)
Bi-directional
Instrument design, dev, test, generate Inst.
Metadata driven, reuse (80:20)
Not programming
Standards based, simple efficient
Multi-modal & layouts
Who
All
Commercial e.g. collection, others (ABS, SC, CBS
In-house build
Consortium
Why
Group not perfect
Inefficient, costly, error prone, difficult - design
robust
Better chance of success
Pool resources, experience
Don't duplicate, timelines
Standalone collections
Scalability
Better solution
When
Plan
Analyse and Assess
Build/procurement
Imp. /Prod.
3 months
end 2015
by June 2016
1/1/2017
How
Several PoC approaches
Collaborative workshops
Plan, assess, and do
SMA + IT +PM
Example Q e.g. Labour F
Where
First deliverable: virtual meet again in 1 month
(possible side meets). ABS lead, then decide
Virtual sharepoint sprints G@G
Webex
3. Case management
"Run time" orchestration.
What to understand - logistical (data collection)
 not enterprise
What
Execute collection strategy
Case level - reporting unit
Responds to events
 auto
 manual
 time / process based
Future: know what want to collect from
provider (ask at once)
 proof for not collection based activity
Who
All lead
Tool
 workflow
 event based
CRM > PM > CASE < SAMPLE LIST
Why
Agile systems, efficiency and common quality
MIS based
 responsive design
Focus on provider
How
CBS - building tool
Same ?? model buy
 Concepts - BA? > together
 next level with defined user stories
Gaps - ABS 1 big system
 SNZ breed up [CRM, CASE< Channel]
All have experience - core business
When
BA activity based model by May 2015
CBS - paper walk through (next month)
STC - demo current system solution (next
month)
COTS tool - summer (June-August 15)
4. Channel
What
Capability to collect data by particular mode
Managed resources
Excludes case management
Who
ABS
CBS - lead? (Blaise for CAWI)
NZ
Why
Needed now by all
Pooling resources
Ongoing channel evolution
 critical mass
When
By channel separation
 CAWI, CAPI, CATI (PAPI)
 and offline and apps
Workload management?
 separate deliver
 optimisation
How
Needs program manager and investment
framework
Blaise 5 priorities (BCLUB) <- influence for
change
 governance, resources
 planning and delivery
Exchange priorities (before BCLUB)
Where
Virtual meetings
BCLUB
Co-design
 Split the work?
 ABS testing site
Shared resource with ABS
 Blaise
Workload Optimisation - Separate Deliverables
CATI
Queuing (intelligent)
Canada has multi-survey optimisation
Scheduling
CAPI
Mathematical for address
ABS has AWAT
Within and address need priority and provider
management info for multi- cases
CAWI
Server capacity
Prioritisation for multi cases single content
Share Algorithms + parameters, Process,
Systems?,
 collection strategy first
Why
5. Admin Data
What
All existing data. Not direct i.e. secondary
collect
Unstructured/Variable data
Different delivery methods
"Meta" administration ? Standardisation
XML: descriptions inside fils
Get from provider at set-up > changes?
Query/quality data when captured
 big data
 streamed data
 flexible
 scalable
 source agnostic
? Infrastructure to
 Capture metadata
 Receipt data
 Clean and validate
 Provider checks
Who
All four, investigation needed
Vendor > generic metadata? (Capture tool)
Decide examples
How
Sharing experiences
When
R&D
ABS has an urgent need. Approval for "SBR"
node project
ABS > 3 month touch base
Admin to focus on scenarios/examples
Tool idea
Capture metadata on data
Sim to collect - complete tool information
Structure
Attributes
Tables
Variables/definitions
Quality
Data profiling
To feed into our MAT and read incoming data
file for set up landing space in data store
Why
Complex > same for all
Repeated > control solution
Needs special infrastructure and VISION
Learn from industry
Addtional focus
How admin data reduces collection needs
Social/household