 |
DuPage County Homeless
Continuum
Component #1 Action Plan |
|
| Component #1 - Needs Assessment - Fully functional CMIS | ||||||||||
| Objective: 1.1 Establish a universal criteria for needs assessment data entry by 2004. | ||||||||||
| Responsible Continuum Committee or Task Group: | Needs Assessment Committee - CMIS Users Group | |||||||||
|
Milestones and Action Steps
|
Timeline
|
Resources
|
||||||||
|
2004
|
2005
|
|||||||||
|
Q1
|
Q2
|
Q3
|
Q4
|
Q1
|
Q2
|
Q3
|
Q4
|
Partners
|
$$
|
|
| 1.1.1. CMIS users group to set sub-committee that represents major agencies. |
X
|
|
|
|
|
|
|
|
||
| 1.1.2. Define terms or fields needing definition. |
|
|
X
|
|
|
|
|
|
||
| 1.1.3. Agree upon definitions |
|
|
X
|
|
|
|
|
|
||
| 1.1.4. Report back to full CMIS Users Group. |
|
|
|
X
|
|
|
|
|
||
| 1.1.5. Publish glossary of terms for all agencies. |
|
|
|
X
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|||
| Total Cost | ||||||||||
| Component #1 - Needs Assessment - Fully functional CMIS | ||||||||||
| Objective: 1.2 By January 2005, all HUD funded agencies will be fully entering data into all required fields to the CMIS system. | ||||||||||
| Responsible Continuum Committee or Task Group: | Needs Assessment Committee - CMIS Users Group | |||||||||
|
Milestones and Action Steps
|
Timeline
|
Resources
|
||||||||
|
2004
|
2005
|
|||||||||
|
Q1
|
Q2
|
Q3
|
Q4
|
Q1
|
Q2
|
Q3
|
Q4
|
Partners
|
$$
|
|
| 1.2.1. Secure "going live date" for duPage Health Department participation in the CMIS. |
|
|
X
|
|
|
|
|
|
||
| 1.2.2. Assist Family Shelter Services in addressing barriers to participation in CMIS |
|
|
|
X
|
|
|
|
|
||
| 1.2.3. System Administrator will review agency data to assure full entry of required fields. Step in schedule |
|
|
|
|
X
|
|
|
|
||
| 1.2.4. Continued training is planned as system is updated and staff change. |
|
|
|
|
|
X
|
|
|
||
|
|
|
|
|
|||||||
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|||
| Total Cost | ||||||||||
| Component #1 - Needs Assessment - Fully functional CMIS | ||||||||||
| Objective: 1.3 By January 2006, all other relevant providers that support homeless populations will be invited to participate in the CMIS. | ||||||||||
| Responsible Continuum Committee or Task Group: | Needs Assessment Committee - CMIS Users Group | |||||||||
|
Milestones and Action Steps
|
Timeline
|
Resources
|
||||||||
|
2005
|
2006
|
|||||||||
|
Q1
|
Q2
|
Q3
|
Q4
|
Q1
|
Q2
|
Q3
|
Q4
|
Partners
|
$$
|
|
| 1.3.1. CMIS System Administrator prepares a list of agencies to invite. |
X
|
|
|
|
|
|
|
|
||
| 1.3.2. Send letter of invitation. |
|
X
|
|
|
|
|
|
|
||
| 1.3.3. Evaluate response. |
|
|
X
|
|
|
|
|
|
||
|
|
|
|
|
|||||||
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|||
| Total Cost | ||||||||||
| Component #1 - Needs Assessment - Fully functional CMIS | ||||||||||
| Objective: 1.4 Audit and analyze data in the system to ensure integrate and usage beginning in 2005. | ||||||||||
| Responsible Continuum Committee or Task Group: | Needs Assessment Committee - CMIS Users Group | |||||||||
|
Milestones and Action Steps
|
Timeline
|
Resources
|
||||||||
|
2005
|
2006
|
|||||||||
|
Q1
|
Q2
|
Q3
|
Q4
|
Q1
|
Q2
|
Q3
|
Q4
|
Partners
|
$$
|
|
| 1.4.1. Determine data fields to be audited for agencies and the system. |
X
|
|
|
|
|
|
|
|
||
| 1.4.2. Develop reports. |
X
|
|
|
|
|
|
|
|
||
| 1.4.3. Run audits. |
|
X
|
|
|
|
|
|
|
||
| 1.4.4. Summarize findings and report to CMIS. |
|
|
X
|
|
|
|
|
|
||
| 1.4.5. Develop plan for correction as needed. |
|
|
|
X
|
|
|
|
|
||
| 1.4.6. Implement corrective actions. |
|
|
|
|
X
|
|||||
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|||
| Total Cost | ||||||||||
| Component #1 - Needs Assessment - Fully functional CMIS | ||||||||||
| Objective: 1.5 By 2006, using the CMIS system, complete an annual "gaps analysis" for homeless services. | ||||||||||
| Responsible Continuum Committee or Task Group: | Needs Assessment Committee - CMIS Users Group | |||||||||
|
Milestones and Action Steps
|
Timeline
|
Resources
|
||||||||
|
2005
|
2006
|
|||||||||
|
Q1
|
Q2
|
Q3
|
Q4
|
Q1
|
Q2
|
Q3
|
Q4
|
Partners
|
$$
|
|
| 1.5.1. Meet with System Administrator, Peg, and Needs Chair to determine fields and reports required. |
X
|
|
|
|
|
|
|
|
Peg White Lijewski | |
| 1.5.2. Contract for development of custom report from Bowman System if needed. |
|
|
X
|
|
|
|
|
|
Bowman systems | $$ for development of reports if needed |
| 1.5.3. Run report and verify accuracy. |
|
|
|
|
X
|
|
|
|
||
| 1.5.4. Share with Needs Assessment Committee and Chairman's Forum for approval. |
|
|
|
|
|
|
X
|
|
||
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|||
| Total Cost | ||||||||||
| Component #1 - Needs Assessment - Fully functional CMIS | ||||||||||
| Objective: 1.6 By 2007, conduct a technology audit for all CMIS users . | ||||||||||
| Responsible Continuum Committee or Task Group: | Needs Assessment Committee - CMIS Users Group | |||||||||
|
Milestones and Action Steps
|
Timeline
|
Resources
|
||||||||
|
2006
|
2007
|
|||||||||
|
Q1
|
Q2
|
Q3
|
Q4
|
Q1
|
Q2
|
Q3
|
Q4
|
Partners
|
$$
|
|
| 1.6.1. Determine what is to be audited. |
|
|
|
|
|
|
|
|
||
| 1.6.2. Develop process for audit activities. |
|
|
X
|
|
|
|
|
|
||
| 1.6.3. Run audit. |
|
|
|
X
|
|
|
|
|
||
| 1.6.4. Prepare a report or findings and needs for update. |
|
|
|
|
X
|
|
|
|
||
|
|
|
|
|
|
X
|
|||||
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|||
| Total Cost | ||||||||||
Action Plan Index | Continuum Home
Last Updated May 10, 2005