PDDE DQ Report

This report is intended for ICA CoC teams to use to identify data quality issues with Project Descriptor Data Elements.

Running the Report

Report Path

Folders
> Public Folder
> missouri_live_folder OR casperwy_live_folder
> Z-Admin
> Quarterly Project DQ Reports for ICA
> PDDE DQ Report

Recommended Export Format

Schedule to Microsoft Excel - Reports

Setting the Prompts

Prompt	Instructions
Select CoC Code(s):	You should use this prompt to run for the whole CoC.
Include Projects with Null CoC Code:	Leave as 'No' if running by CoC. Change to 'Yes' if running by single provider and want to check it even if it has a null CoC code.
Enter End Date PLUS 1 Day:	This prompt will default to 10/1/2022 - one day after the end of FY2022. Leave as is.
Enter Start Date:	This prompt will default to 10/1/2021 - the start of FY2022. Leave as is.
EDA Provider	If only one project is selected in the "Select Provider(s):" prompt above, select the same project here. If more than one project is selected in the "Select Provider(s):" prompt or if a reporting group has been selected in "Select Reporting Group:" prompt, then select one of the projects within the selected projects or reporting group.
Select Provider(s):	Select the project(s) for which you wish to run the report. Note: If this prompt is completed, the "Select Reporting Group" prompt must be left to "none selected" or left incomplete (blank).

What providers are pulled into the report?

Projects Included tab

If a CoC code is used in the prompt, the following providers will be pulled in:

All providers with that CoC code, and
Project type = ES, SH, TH, RRH, PSH, OPH

If the CoC code is left blank, the following providers will be pulled in:

Providers with any CoC code, and
Project type = ES, SH, TH, RRH, PSH, OPH

All other tabs

If a CoC code is used in the prompt, the following providers will be pulled in:

All providers with that CoC code, and
Has active operating start dates in the report period, and
Continuum project = Yes, and
Project type = ES, SH, TH, RRH, PSH, OPH

If a provider is selected in the prompt, that provider will be pulled in regardless of CoC code.

If 'Include Projects with Null CoC Code' = No, these projects do not have to have a CoC code.
If 'Include Projects with Null CoC Code' = Yes, these projects must have a CoC code.

General Notes

What is a continuum project?

From the Data Standards, a Continuum projects refers to a distinct unit of an organization, which may or may not be funded by HUD or the Federal Partners, whose primary purpose is to provide services and/or lodging for the homeless and is identified by the Continuum as part of its service system. For example, a project funded by the HUD's CoC Program may be referred to then as a “CoC Program-funded continuum project.”

Does my project need a project type?

All continuum projects should have a project type filled out. For non-continuum projects, you may need to rely on your knowledge of the related project, funder, and CoC policies.

Using the Report

This report has 10 tabs, each serving a specific purpose. It is recommended to work left-to-right through the tabs. Ensure all DQ flags are cleared, or an explanation is available for any remaining flags.

Projects Included

The table is intended to ensure that all projects will properly pull into the LSA. The LSA will pull all projects with Continuum = Yes.

Column	Explanation	DQ Flags and How to Correct Them
Provider	-	N/A
CoC Code	-	N/A
Project Type	-	Missing Add to HUD Standards tab in Provider Admin. Required for all Continuum=Yes projects.
Continuum Project	See above	Bold if No Add to HUD Standards tab in Provider Admin. Required for all Continuum=Yes projects. Missing Investigate to ensure this is correct. See above for notes on what is a Continuum Project.
Uses ServicePoint	-	Check that this is correct.
Operating Start Date	-	Missing Add to HUD Standards tab in Provider Admin
Operating End Date	-	Missing and the project has a ZZZ in the name, indicating it is closed Add to HUD Standards tab in Provider Admin. Note: Closed projects that were active at any point during the FY will be pulled into the LSA.
ICA SysAdmin	The ICA SysAdmin associated with that projects agency, if there is one.	N/A

Projects by Type

Shows all projects, organized by project type (Project Type column), with the count of valid funding sources, bed inventories, CoC code and Primary locations.

Column	Explanation	DQ Flags and How to Correct Them
Project Type	-	N/A
Provider	-	N/A
Funding Sources	Count of valid funding sources Valid = active in current FY based on start and end dates	No Valid Funding Source Add current funding source to Provider Admin. This will also flag if there is a funding source, but it's missing a start date. Check Provider Admin.
Bed Inventories	Count of valid bed inventory records Valid = active in current FY based on start and end dates	No Valid Inventory Add current bed inventory to Provider Admin. This will also flag if there is a bed inventory, but it's missing a start date. Check Provider Admin.
CoC Code	Count of valid CoC Code records Valid = active in current FY based on start and end dates	No Valid CoC Code Add current CoC Code to Provider Admin. This will also flag if there is a CoC Code, but it's missing a start date. Check Provider Admin.
Primary Location	Count of Provider Addresses	Missing Add address in Provider Profile > Location

Projects by Fund Source

Shows all projects grouped by fund source (section title). This tab is filtered to show ONLY grants that are active during the reporting period (FY).

Use this as a reference, but the real grant checking happens on the Funder.csv data tab.

Notes

# Active Funding Sources shows the count of active/valid funding sources for that project.
Funding Source Count refers to the number of funds per provider. The column Valid Fund Source shows which grants are valid for the reporting period and contribute to the Funding Source Count.
There are no flags on this tab.

Projects.csv

This table approximates the LSA export Project.csv. Data is pulled from Provider Admin > Profile > Standards Information.

Column	Explanation	DQ Flags and How to Correct Them
Provider	-	N/A
Operating Start Date	-	Missing Add to HUD Standards tab in Provider Admin
Operating End Date	-	Missing and the project has a ZZZ in the name, indicating it is closed Add to HUD Standards tab in Provider Admin. Note: Closed projects that were active at any point during the FY will be pulled into the LSA.
Continuum Project	See above	Value not Yes Note: When running for a CoC, only Continuum Project = Yes projects are pulled in.
Uses ServicePoint	-	No Projects will be pulled into LSA regardless of this field, but ensure it is correct for the project. Will cause LSA warning if marked no, but has client data, or marked yes and no client data.
Automatically Exit Back Date Mode	From Module Settings > ServicePoint Settings	For Missouri Missing for projects that Use ServicePoint This setting should be Yes for all projects using ServicePoint. Note- this is not specific to LSA, just general system functioning.
Project Type	-	Missing Add to HUD Standards tab in Provider Admin. Required for all Continuum=Yes projects.
Shelter Tracking	-	Project = ES and Method for Tracking is missing or not EE or NBN Add Method for Tracking (either EE or NBN) for all ES projects to HUD Standards tab in Provider Admin. Project NOT ES and Method for Tracking is filled out Remove. This is unnecessary.
Housing Type	-	Missing Add to HUD Standards tab in Provider Admin. Value present and not a HUD value HUD Values: Site-based - single site; Site-based clustered / multiple sites; Tenant-based - scattered site. Update to HUD Value.
Target Population	This is the 'Target Population' field. NOT the 'Target Population A (Optional).	Missing Add Method for Tracking (either EE or NBN) for all ES projects to HUD Standards tab in Provider Admin. Make sure this is filled out, even if it is N/A
Affiliated with Residential Project	-	Value not No Update to No. This should only be Yes for SSO projects, which are not included in the LSA
Project Identifier Provider Name	-	Any value Remove. You may need to toggle on the Affiliated with Residential Project to Yes to see this field and then delete the provider name. This should be null for all project types other than SSO, which is not included in the LSA. If this is (null), this is good.
Victim Service Provider?	-	Missing Add to HUD Standards tab in Provider Admin.

Organization.csv

This table approximates the LSA export Organization.csv. This shows the organizations associated with the providers that are pulled into Project.csv. This linkage is made through the Organization ID associated with the project-level provider.

Column	Explanation	DQ Flags and How to Correct Them
Organization	Level 2 Agency	N/A
VSP?	Level 2 Agency	Missing Add to HUD Standards tab in Provider Admin.
Continuum Project	See above	Yes Change to No. Organizations should NOT be marked Yes unless they collect client-level data.

Funder.csv

This table approximates the LSA export Funder.csv, showing all grants associated with the project.

This tab is filtered to show ONLY grants that are active during the reporting period (FY). These grants contribute to the Funding Source Count.

Use the Projects by Type tab to see projects without active grants. These will cause an error.

Data is pulled from Provider Admin > Profile > Standards Information > Federal Partner Program and Components.

Column	Explanation	DQ Flags and How to Correct Them
Provider	-	N/A
Project Type	-	N/A
Recordset ID	Back-end recordset ID for the grant subassessment record.	N/A
Federal Partner Program	-	N/A
Grant Identifier	-	N/A
Grant Start Date	-	Missing Add to funding source.
Grant End Date	-	N/A
Funding Source Count	Count of valid funding sources for that provider Valid = active in current FY based on start and end dates	N/A

Inventory.csv

This table approximates the LSA export Inventory.csv.

This tab is filtered to show ONLY inventories that are active during the reporting period (FY). These inventories contribute to the Inventory Count.

Use the Projects by Type tab to see projects without active bed inventories. These will cause an error.

Data is pulled from Provider Admin > Profile > Standards Information > Bed and Unit Inventory.

Column	Explanation	DQ Flags and How to Correct Them
Provider	-	N/A
Project Type	-	N/A
Recordset ID	Back-end recordset ID for the bed inventory subassessment record.	N/A
Inventory CoC Code	From the bed inventory subassessment record.	Missing when there is a recordset ID Add to inventory record. Does not match Prompt CoC (if used) Make sure Inventory CoC code matches Project CoC code.
Household Type	From the inventory subassessment record.	Missing when there is a recordset ID Add to inventory record.
Bed Type	From the inventory subassessment record.	Missing when Project is ES Add to inventory record. This is required for ES projects. Remove from inventory record. This should not be filled out for non-ES projects.
Availability	From the inventory subassessment record.	Missing when Project is ES Add to inventory record. This is required for ES projects. ddfgdf Remove from inventory record. This should not be filled out for non-ES projects.
Total Bed Inventory	From the inventory subassessment record.	Missing when there is a recordset ID Add to inventory record.
Unit Inventory	From the inventory subassessment record.	Missing when there is a recordset ID Add to inventory record.
Inventory Start Date	From the inventory subassessment record.	Missing when there is a recordset ID Add to inventory record. Inventory Start Date is earlier than Project Operating Start Date Update Inventory Start Date and/or project's Operating Start Date. Inventory Start Date should be on or after the Operating Start Date.
Inventory End Date	From the inventory subassessment record.	Missing when there is a recordset ID and Project has Operating End Date Add Inventory End Date. All inventories for projects with Operating End Dates should have Inventories with end dates. Inventory End Date is later than Project Operating End Date Update Inventory End Date and/or project's Operating End Date. Inventory End Date should be on or after the Operating End Date.
Inventory Count	Count of valid inventories for that provider Valid = active in current FY based on start and end dates	N/A
Dedicated beds	These fields are not in BusinessObjects. Use the LSA Airtable showing comparisons between HIC and HMIS BUI for discrepancies, or Reportwriter output for data dump.	N/A

Geography - CoC

This provides geography information for each project.

This tab shows all CoC codes associated with the project.

Data is pulled from Provider Admin > Profile > Standards Information > COC Code.

Note from Data Standards:
'Geocode,' 'Project ZIP code,' and 'Project Street Address' fields must reflect the location of the project's principal lodging site or, for multiple site projects, the area in which most of the project's clients are housed. Tenant-based scattered site projects and Victim Services Providers are only required to complete the geocode and ZIP code fields and may use mailing or administrative address information if they wish to complete the remainder of the address fields.
When there are multiple records of Continuum of Care Information because of a single project's association with different CoCs, the geocodes will differ. The geocode must be located within the CoC in the same record.

Column	Explanation	DQ Flags and How to Correct Them
Provider	-	N/A
Recordset ID	Back-end recordset ID for the bed inventory subassessment record.	N/A
CoC Code	From the inventory subassessment record.	Missing when there is a recordset ID Add to CoC record. Does not match Prompt CoC (if used) Make sure CoC code matches Project CoC code.
Geocode	-	Missing when there is a recordset ID Add to CoC record. Not 6 characters long Correct Geo Code - all Geo Codes are 6 digits long.
Postal Code	-	Missing when there is a recordset ID Add to CoC record. Not 5 characters long Check and correct Postal Code - Postal Codes should be 5 digits long. If it's the 5 digits and the 4 after, that's okay too.
Geography Type	-	Missing when there is a recordset ID Add to CoC record.
Start Date	-	Missing when there is a recordset ID Add to CoC record. Missing Start Date will cause the record to be invalid.
End Date	-	N/A
Valid CoC Code	X if the CoC Code record is valid. Valid = active in current FY based on start and end dates	Ensure valid CoC Code: Add one if missing entirely or ensure all elements are complete and correct, especially Start Date.
CoC Record Count	Count of valid CoC records for that provider Valid = active in current FY based on start and end dates	No Valid CoC Codes Ensure valid CoC Code: Add one if missing entirely or ensure all elements are complete and correct, especially Start Date.

Geography - CoC

This provides location (address) information for each project. .

Data is pulled from Provider Admin > Profile > Provider Profile > Location Information.

Column	Explanation	DQ Flags and How to Correct Them
Provider	-	N/A
Recordset ID	Back-end recordset ID for the bed inventory subassessment record.	N/A
Address Line 1	-	Missing and Housing Type is NOT Tenant-based - scattered site An address is required for all projects that are not tenant/scattered. Add to address record.
Address Line 2	-	N/A
City	-	Missing Add to address record.
Province	-	Missing Add to address record.
Zip Code	-	Missing Add to address record.
Location Count	Count of addresses for the provider.	N/A

Additional Information

This tab contains information about the report that can be utilized by ICA Reporting Team to determine whether the report was run properly by the user. If you seek assistance with this report from ICA Reporting Team, please be prepared to read/send information off of this tab to the individual who assists you.