CWDS / Child Welfare Digital Services
CWDS Quarterly UpdateJune 2019
Agenda
• Introductions
• Kevin Gaines
• CWS-CARES Development Approach
• Becky Stilling
• County Perspective
• Wendy Christian
• Product Blueprinting & Domain Modeling
• Andrea Hollen
• Resource Family Approval (RFA) “Deep Dive”
• Jeff Dent
CWDS / 2
CWS-CARES
Development
Approach
CWDS / 3
Becky Stilling
Things to know about the
Acceleration Strategy
What is it?
A strategy that evaluates a
number of areas to
determine the best options
(technically and
economically) in order to
accelerate the delivery of
CWS-CARES.
Why are we doing it?
The project’s current approach
to product delivery has lagged
compared to expectations.
These specific areas are worthy
of reconsideration because they
effect all areas of future
development.
What does it mean
for me?
We are still in the evaluation
and analysis phase and no
decisions have been made
regarding next steps. We are
assessing all potential impacts
and planning for them
proactively. Findings from this
work will inform future
development planning.
CWDS / 4
Key Components of the Acceleration Strategy
Product Blueprinting & Domain ModelingA Product Blueprint is a high-level flow diagram that takes into account Federal/state
reporting requirements and captures the end-to-end process in each core digital service area.
A Domain Model describes how core child welfare concepts relate to each other and
specifies the business flows and rules governing their interactions.
Legacy Integration & SynchronizationCan CWS-CARES co-exist with legacy systems in a technically feasible, predictable,
repeatable and cost-effective way or not?
CWDS / 5
Key Components of the Acceleration Strategy
Platform-as-a-Service (PaaS) Proof of Concept (POC)A two-phase process for vendors to build and demonstrate a working application on a
commercial PaaS based on realistic scenarios (from the Product Blueprint).
Platform Market ResearchWorkshops and demonstrations with additional vendors to further understand limits and
capabilities in addition to costs and licensing. This will assist the project in identifying gaps;
understand how configuration and customization, in combination, might close those gaps and
assess the associated trade-offs and economic impacts.
CWDS / 6
CARES Development Approach
• CWDS will have an enterprise architecture that includes a PaaS, State Managed
Data Infrastructure (SDI) and potentially, some special purpose commercial
products or custom developed capabilities
• The PaaS will house the CARES application
• The SDI will support data exchange & analytics
• We will continue to:
• Directly involve County partners, utilizing user-centered research & design
• Configure/develop the PaaS in an agile, iterative way
• Maintain and support the features currently in production until they can be fully replaced or
incorporated into the new platform
• Plan & build one thing at a time
• Over the next six months:
• Determine which of the two market leaders (Salesforce or Dynamics) are best for CARES
• Procure the selected platform and the services of a PaaS systems integrator
• Plan for maintenance & operation of the County Sandbox Environment
• Further develop Product Blueprint CWDS / 7
County Perspective
CWDS / 8
Wendy Christian
Product
Blueprinting &
Domain Modeling
CWDS / 9
Andrea Hollen
Blueprint
Product Blueprint• Product Vision
• Shows the full extent of the work CARES must support
• Reflects the needs of all users, including data consumers and community partners
• Affords a to-be perspective, emphasizing decisions, program events and outcomes
• Provides the starting point for a more rigorous delivery methodology suited to a
highly-regulated, safety-critical, data-intensive system
• Aspects• To-be administrative workflow, partitioned into Product Building Blocks, each with
a Value Hypothesis
• Worker and child/family pain points, with associated improvement opportunities -
based on careful research and service design thinking
• Shared services
o Domain concepts (e.g. Person, Relationship, Household)
o Product features (e.g. Search, Match, Schedule, Upload Content)
• Integration (data exchange) pointsCWDS / 10
CWDS / 11
Product Blueprint - Case Management Example
Value Hypothesis - CFT Example
CWDS / 12
Share of children exiting to safe and stable reunification
Timeliness of initial and subsequent CFT meetings
Fidelity to CFT model
Permanency Outcomes
Length of stay for children exiting to reunification
Time to organize and schedule CFT meetings
Effort to identify potential CFT members
Practice VariablesProcess Variables
Product features - CFT reminders by situation (e.g. IHBS, SMHS, STRTP)
- Metric Time to first CFT from day brought into custody
Product features (metrics) Length of stay by entry cohort, by permanency outcome, by subgroup (e.g. race/ethnicity, age stratum, neighborhood, strengths and needs at entry)
Product features Calendaring tool that helps schedule and locate meeting in accordance with family needs/preferences
Product features Picture of family relationships over time that highlights natural supports
Product features Tools that simplify capturing attendance, strengths, needs, goals, plans
Domain Model• Shared Vocabulary
• Precisely captures human services concepts and the relationships among them
• Accommodates context-specific variations
(e.g. program-specific definitions of ‘Household’)
• Foundation for Data Quality Monitoring, CQI, Program Evaluation
and Data Exchange
• Includes a “registry” (set of master indices) to help prevent and resolve duplicates
• Shows coverage of data elements and populations required for Federal/State
compliance reporting
• Shows coverage of the “numerators and denominators” needed to build and track
Value Hypothesis metrics
• Represents events, event histories and pathways as first class system concepts
CWDS / 13
Domain Model - Case Management Example
CWDS / 14
RFA “Deep Dive”
CWDS / 15
Jeff Dent
CWDS / 16
CWDS / 17
Detail Design ActivitiesProduct blueprint showing Building Block 1 and 2 for RFA
Application acceptance and start of review
CWDS / 18
Level 2 flow for Scenario 1, 2, 3 and 4 based off Building Block 1 and 2
CWDS / 19
Example research items coming out of level 2 and 3 flow
Example outcomes, opportunities, pain points coming out of level 2 and 3 flow
CWDS / 20
CWDS / 21
Level 3 for Scenario 1 Gather applicant and address info
CWDS / 22
Example deep dive design document for Scenario 1
SCENARIO EPIC USER STORY/TASK ASSIG NED TO Link t o t he ar t ifact s
All Level 2 flow Story 1 - Create level 2 flow and identify metrics pain points, opportunities, outcomes, research questions and domain model Team Level 2 Flow Diagram
Outcomes, Metrics, Paint points, opportunities, questions
Story 2 - Group Research Questions by Category Team Research Questions
Story 3 - Create high level Domain Model PO and Team High Level domain model
Create EPICS and stories for backlog PO and Team This document and Jira
Manage Mast er Infor mat ion for t r aining Level 3 flow Story 4 - Design - Prepare level 3 flow
Acceptance Criteria:1) Level 3 workflow with participants, events, and business rule call outs2) Document metrics, pain points, opportunities
Team Level 3 Flow
Story 5 - Research – Conduct SME researchAcceptance Criteria: -1) Gather findings ??
SME/Researchers/BA Research QuestionsQuestion - continue discussion on how to bring answers to research questions in design document
Story 6 - Research – Conduct county research
Acceptance Criteria: -
Gather findings ??
SME/Researchers/BA Research Questions
Question - continue discussion on how to bring answers to research questions in design document
Story 7 - Research – Conduct Policy researchAcceptance Criteria: -
Gather findings??
SME/Researchers/BA Research QuestionsQuestion - continue discussion on how to bring answers to research questions in design document
CWDS / 23
Example deep dive design document
Deep Dive Summary• Provide a detailed visual flow for “to be” CARES capabilities.
• Ensure user research/feedback is incorporated into the blueprint artifacts
• Define opportunities for automation and process improvements
• ICPM (i.e. Team based, collaboration & integration, outcomes-based)
• CQI
• Account for program goals and metrics for each building block
• Establish sound business rules to ensure policy/program compliance and increase data quality
• Provide a repeatable framework for development and configuration efforts.
CWDS / 24
Questions & Answers
CWDS / 25
CWS-CARES Resources
Executive Leadership Team
CDSS - Kevin Gaines:
OSI - Becky Stilling:
CWDA - Wendy Christian:
v
CWDS.CA.GOV
Communications:Heather [email protected]@cwds.ca.gov
Service Desk:
Implementation:[email protected]
CWDS / 26