67
edits
Changes
CCDIC Refining Strategic Data Management Initiative (view source)
Revision as of 10:31, 27 March 2020
, 10:31, 27 March 2020no edit summary
I extended my data modeling scope to include reports that use data provided by PPMG, any PPMG data submitted to planning or financial reporting authorities and any other data created by PPMG. (Section Planning Input Requirements.pptx, CCDIC Section Milestone Planning.xlsx)
I extended my data modeling scope to include reports that use data provided by PPMG, any PPMG data submitted to planning or financial reporting authorities and any other data created by PPMG. (Section Planning Input Requirements.pptx, CCDIC Section Milestone Planning.xlsx)
By this time, my intention was clear: integrate BOP and PRM planning in order to achieve time savings. If sufficient data were collected in PPMGs planning phase, it could have most, if not all, of the data on hand required by the BOP data gathering process. I felt that this time-saving incentive would also lead to a resolution of nomenclature issues as well. Further, it is sensible to provide data gatherers with requirements. I recommend that PPMG require that BOP activity names be selected soon enough to ensure none of the section and division planning processes are “negatively influenced”. (
By this time, my intention was clear: integrate BOP and PRM planning in order to achieve time savings. If sufficient data were collected in PPMGs planning phase, it could have most, if not all, of the data on hand required by the BOP data gathering process. I felt that this time-saving incentive would also lead to a resolution of nomenclature issues as well. Further, it is sensible to provide data gatherers with requirements. I recommend that PPMG require that BOP activity names be selected soon enough to ensure none of the section and division planning processes are “negatively influenced”. (Integration.pptx)
In addition, if PPMG preserved its inputs to the financial process in such a data collection, that un-aggregated data would be available to those investigating data shown in variance reports from a financial system incapable of providing the original un-aggregated inputs back to the area of concern when asking them to answer variance questions based on their inputs. Truly a “keep your receipts” kind of a situation. I called this data collection the CCDIC Planning System (now Repository2.accdb). Perhaps not all of the data contributes to nor is created by the planning process but, its availability enables solutions to many of the issues in our User Stories.
In addition, if PPMG preserved its inputs to the financial process in such a data collection, that un-aggregated data would be available to those investigating data shown in variance reports from a financial system incapable of providing the original un-aggregated inputs back to the area of concern when asking them to answer variance questions based on their inputs. Truly a “keep your receipts” kind of a situation. I called this data collection the CCDIC Planning System (now Repository2.accdb). Perhaps not all of the data contributes to nor is created by the planning process but, its availability enables solutions to many of the issues in our User Stories.
* The system in a state of paralysis and its value was being questioned
* The system in a state of paralysis and its value was being questioned
* The system was in that development phase in which the report outcomes were driving changes not the appearance or expected value of the reports.
* The system was in that development phase in which the report outcomes were driving changes not the appearance or expected value of the reports.
These are some of the symptoms of a System Maturity problem. Most of the systems in PHAC are DIY / Home grown systems built by arranging steps in applications like leggo pieces in order to create systems. At first, the system attracts attention based on its perceived potential. Then, the volunteer developers are asked to make some improvements to make the system meet business expectations. Some of those improvements are met, others stubbornly refuse solution. A backlog of changes begins to build. Soon, confidence in the system wanes and frustration builds. "How could we come so far so fast to only be stuck in the mud now? We have excellent people . . . how is this possible?"
I began to gather data to test this theory.
I experimented with code which could be used to import data sent in email directly into a database table. The code works nicely importing data as it arrives at the proposed CCDIC.DataInput@canada.ca address, but, needs to be refined for the various body content expected.
I experimented with code which could be used to import data sent in email directly into a database table. The code works nicely importing data as it arrives at the proposed CCDIC.DataInput@canada.ca address, but, needs to be refined for the various body content expected.