Line 79: |
Line 79: |
| Furthermore, the workbook behaved in unexpected ways (halting, freezing or closing the workbook right in front of you) as the number of users increased. The idea will have to wait for the new tools in PHAC’s future. | | Furthermore, the workbook behaved in unexpected ways (halting, freezing or closing the workbook right in front of you) as the number of users increased. The idea will have to wait for the new tools in PHAC’s future. |
| | | |
− | I created an access database version of the repository to hold all of the “helpful” database solutions I came up with or for which I had been given a suggestion. That collection of unimplemented tools are planned for implementation on the timeline into the future that I leave with the final documentation. | + | I created an access database version of the repository to hold all of the “helpful” database solutions I came up with or for which I had been given a suggestion. That collection of unimplemented tools are planned for implementation on the timeline into the future that I leave with the final documentation. (Repository2.accdb) |
| | | |
− | As a very quick, Lean experiment, tried to embed a survey form as a watermark in an email. The idea was clever and worthy of testing in case it actually worked, but the outcome was wildly different for most receivers based on things I could not control, like the number of lines in a signature or the number of lines used by the list of addresses in the To:. Lesson learned: cheap shortcuts flirting with the edge of the envelope are simply too risky and so unlikely to work out that one ought not spend too much time on them. | + | As a very quick, Lean experiment, tried to embed a survey form as a watermark in an email. The idea was clever and worthy of testing in case it actually worked, but the outcome was wildly different for most receivers based on things I could not control, like the number of lines in a signature or the number of lines used by the list of addresses in the To:. Lesson learned: cheap shortcuts flirting with the edge of the envelope are simply too risky and so unlikely to work out that one ought not spend too much time on them. |
| | | |
− | Now, I began to build the CCDIC Planning System as an example of how the two planning world could co-exist as a PMR-BOP integrated system. My intention was to break the mindset of the old excel spreadsheet data gathering world. That data from any source could be collected and added to any of our reports without having to gather that new data when the PMR data is gathered. The data can be pre-existing or can be gathered later prior to the report generation. In this way CCDIC could expand its RBM reporting. | + | Now, I began to build the CCDIC Planning System as an example of how the two planning world could co-exist as a PMR-BOP integrated system. My intention was to break the mindset of the old excel spreadsheet data gathering world. That data from any source could be collected and added to any of our reports without having to gather that new data when the PMR data is gathered. The data can be pre-existing or can be gathered later prior to the report generation. In this way CCDIC could expand its RBM reporting. |
| | | |
| The response was good. Managers knew that things were missing and now they could bring those things into the reporting. So, by expanding the scope of the reporting, we able to meet some of our more sophisticated user stories like those from Audits and Evaluations. | | The response was good. Managers knew that things were missing and now they could bring those things into the reporting. So, by expanding the scope of the reporting, we able to meet some of our more sophisticated user stories like those from Audits and Evaluations. |
| | | |
− | Now, I needed to socialize the data models I had been capturing with the Team and introduce them to the common planning paradigm and the value of our local data to our work. I planned to deliver a new form built in Excel to demonstrate that a good user experience is possible in spreadsheets. The form was capable of sending the data it collected to any drive. | + | Now, I needed to socialize the data models I had been capturing with the Team and introduce them to the common planning paradigm and the value of our local data to our work. I planned to deliver a new form built in Excel to demonstrate that a good user experience is possible in spreadsheets. The form was capable of sending the data it collected to any drive. (Data Maodeling.xlsx, PPMG CCDIC planning tool.pptx) |
| | | |
| The transmission idea makes it possible for the data provider to transmit and the data gatherer to receive data in an asynchronous manner. This opens the door to continuous reporting and it effectively decouples data entry from collection. Data is entered when environmental conditions dictate, not to meet the timelines of the reporting authority. | | The transmission idea makes it possible for the data provider to transmit and the data gatherer to receive data in an asynchronous manner. This opens the door to continuous reporting and it effectively decouples data entry from collection. Data is entered when environmental conditions dictate, not to meet the timelines of the reporting authority. |
| | | |
− | I met with the TB Folks to plan the creation of a repository ( | + | I met with the TB Folks to plan the creation of a repository (Worksheet) capable of holding incoming indicator data for reports. Regrettably, the pandemic intervened. |
− | | |
− | Worksheet) capable of holding incoming indicator data for reports. Regrettably, the pandemic intervened. | |
| | | |
| February | | February |
| | | |
− | I gathered some information about the Departmental Plan approval process when I heard PPMG was not included at a critical stage. I created a process chart from the information I had gathered. The process was flawed by a discontinuity which the team had noticed. They were able to present the information to others in order to correct a process step. | + | I gathered some information about the Departmental Plan approval process when I heard PPMG was not included at a critical stage. I created a process chart from the information I had gathered. The process was flawed by a discontinuity which the team had noticed. They were able to present the information to others in order to correct a process step. (DP Approval Process.pptx) |
| | | |
| Any discussion of a process is improved by sharing a chart of that process. | | Any discussion of a process is improved by sharing a chart of that process. |
| | | |
− | I refined the PMR data input form to include editing records and added a professional services and resources data input sections. | + | I refined the PMR data input form to include editing records and added a professional services and resources data input sections. |
| | | |
| I had an important experience helping out in the effort to sort out financials records in order to enable the cuts requested. I imported spreadsheet data into a database in order to perform reporting that was difficult in Excel. I also explored the Power Pivot feature. My hopes that this Excel feature would be more stable than the standard pivot table tool, were undermined by our continuing negative experiences. A search on the net of Excel issues and power pivot help sites produced hundreds of stories from individuals like us, who felt the software was a bit shaky when you push it too far. The trouble is that you will lose work and repeatedly return to step one of your last backup of the data. This means that you must keep backups of each stage of your effort to develop the data. Analysts are able to build a path or strategy of data development in their minds, but are disappointed when Excel “lets them down” as they attempt to follow their strategy. This is one of the reasons groups move to SAS or other proven applications for this kind of sophisticated data manipulation. | | I had an important experience helping out in the effort to sort out financials records in order to enable the cuts requested. I imported spreadsheet data into a database in order to perform reporting that was difficult in Excel. I also explored the Power Pivot feature. My hopes that this Excel feature would be more stable than the standard pivot table tool, were undermined by our continuing negative experiences. A search on the net of Excel issues and power pivot help sites produced hundreds of stories from individuals like us, who felt the software was a bit shaky when you push it too far. The trouble is that you will lose work and repeatedly return to step one of your last backup of the data. This means that you must keep backups of each stage of your effort to develop the data. Analysts are able to build a path or strategy of data development in their minds, but are disappointed when Excel “lets them down” as they attempt to follow their strategy. This is one of the reasons groups move to SAS or other proven applications for this kind of sophisticated data manipulation. |
| | | |
− | I was asked to create a Publications SOP in a process diagram. During the data gathering process, I participated in several discussions about blending the Publications process tracking with the current RBM reporting. I explained what was possible. In an attempt to organically expand the scope of the current RBM, I planted the seeds the CCDIC data collection model. I explained that the content of RBM reports depend on the data in the collection not in the only form used to gather RBM data. People tend to created data concepts from the existing tools – like data input forms. A slide explaining the data model of the collection was enabling. Ideas for data inclusion in the RBM reporting were quickly incorporated into the plan: MRAP commitments, Publications etc. | + | I was asked to create a Publications SOP in a process diagram. During the data gathering process, I participated in several discussions about blending the Publications process tracking with the current RBM reporting. I explained what was possible. In an attempt to organically expand the scope of the current RBM, I planted the seeds the CCDIC data collection model. I explained that the content of RBM reports depend on the data in the collection not in the only form used to gather RBM data. People tend to created data concepts from the existing tools – like data input forms. A slide explaining the data model of the collection was enabling. Ideas for data inclusion in the RBM reporting were quickly incorporated into the plan: MRAP commitments, Publications etc.(Publications SOP.pptx) |
| | | |
| In the email study, I assessed the value of an attachments management user story. The concept was to drop attachments into a common repository in CCDIC rather than “attach” them to email or use common drive space with its confusing directory structure. The calculated impact on email volumes seemed impressive but I did not have estimates of the total volume of email in CCDIC. I created the beginnings of a database in the Access Repository for this purpose. | | In the email study, I assessed the value of an attachments management user story. The concept was to drop attachments into a common repository in CCDIC rather than “attach” them to email or use common drive space with its confusing directory structure. The calculated impact on email volumes seemed impressive but I did not have estimates of the total volume of email in CCDIC. I created the beginnings of a database in the Access Repository for this purpose. |
Line 115: |
Line 113: |
| March | | March |
| | | |
− | I built the Common Planning Dbs using related BOP and PMR tables as well as a PMR to publications relationship in order to demonstrate the data behaving as it was all in one “spreadsheet” so folks could begin to change their mindsets about the value of the data around us and witness new strategies towards data management. | + | I built the Common Planning Dbs using related BOP and PMR tables as well as a PMR to publications relationship in order to demonstrate the data behaving as it was all in one “spreadsheet” so folks could begin to change their mindsets about the value of the data around us and witness new strategies towards data management. (Repository2.accdb) |
| | | |
| It is from this old mindset that the concept of a “repository” came as the solution to the problems faced by the RBM system came. It would have the following characteristics: | | It is from this old mindset that the concept of a “repository” came as the solution to the problems faced by the RBM system came. It would have the following characteristics: |
Line 123: |
Line 121: |
| # A system that would lead to an easing of the tension between data producers and data gathers. | | # A system that would lead to an easing of the tension between data producers and data gathers. |
| | | |
− | The requirements are easy to elicit. However, it is the path to the solution which is in jeopardy. How do we get there? How do we improve once we do get there? Will improvements discovered by the BA be implemented? Will the improvements put in place survive? | + | The requirements are easy to elicit. An implementation strategy is straightforward. However, it is the path to the solution which is in jeopardy. How do we over come the expertise barrier? Will improvements discovered by the BA be implemented and/or survive? |
| | | |
− | The current situation is difficult to understand when working with only one section. PPMG. However, I had several outstanding pieces of empirical evidence from over a dozen solutions. | + | The current situation is difficult to prove when working with only one section. However, I had several outstanding pieces of empirical evidence from over a dozen solutions. |
| | | |
| 1) All of my solutions utilized Visual Basic | | 1) All of my solutions utilized Visual Basic |
Line 131: |
Line 129: |
| 2) Each of the solutions can be associated with higher levels of development in the maturity descriptions for systems: Integration, Harmonization, User Experience (UX) and Data Gathering/Transmission/ETL. | | 2) Each of the solutions can be associated with higher levels of development in the maturity descriptions for systems: Integration, Harmonization, User Experience (UX) and Data Gathering/Transmission/ETL. |
| | | |
− | These are not the immediate goals of system designers who start out in a modest way building an “out-of-the-box” system. Indeed, they are not achievable using “out-of-the-box” strategies. | + | These are not the immediate goals of system designers who start out in a modest way building an “out-of-the-box” system. truly, they are not achievable using “out-of-the-box” strategies. |
| | | |
| '''Out-of-the-Box''': Any functionality that comes shipped directly from the software vendor or can be configured easily (where “easily” means configured by a business, not IT user) with built-in workflow tools, templates, and/or best practices provided directly by the vendor | | '''Out-of-the-Box''': Any functionality that comes shipped directly from the software vendor or can be configured easily (where “easily” means configured by a business, not IT user) with built-in workflow tools, templates, and/or best practices provided directly by the vendor |