- In terms of the PIA project flow, this is the second step. It is directly linked to the requirement that institutions must identify all personal information associated with the business processes.
- The purpose of this step is to describe the personal information flows.
- To do this, work with your PIA team to develop detailed descriptions and analysis of the business processes, architecture and detailed data flows for the proposal.
![Note](/web/20071206203827im_/http://www.tbs-sct.gc.ca/pgol-pged/piatp-pfefvp/images/note.gif)
Always remember: there is no such thing as a stupid question! Ask questions and clarify your understanding at any point in the PIA process. If you don't understand, there is a strong likelihood that someone else is or will be in exactly the same situation.
- Understanding the PIA Guidelines document will help you complete this section.
![Note](/web/20071206203827im_/http://www.tbs-sct.gc.ca/pgol-pged/piatp-pfefvp/images/note.gif)
Your IT and systems resources are essential for this part of the Report.
![Note](/web/20071206203827im_/http://www.tbs-sct.gc.ca/pgol-pged/piatp-pfefvp/images/note.gif)
Charters,
Statements of Sensitivity (SOS), Threat and Risk Assessments (TRAs), data-sharing agreements and
Memorandums of Understanding (MOUs) can provide a lot of information.
![Note](/web/20071206203827im_/http://www.tbs-sct.gc.ca/pgol-pged/piatp-pfefvp/images/note.gif)
Map out all data flows.
![Note](/web/20071206203827im_/http://www.tbs-sct.gc.ca/pgol-pged/piatp-pfefvp/images/note.gif)
Data flows can take a long time to research and write. Give yourself enough time to do this properly. It is a crucial part of the Report. If you don't understand data flows, you're not likely to understand what you're dealing with.
Project Proposal
Data Flow Analysis - Business Flow Diagram & Description![Next Page](/web/20071206203827im_/http://www.tbs-sct.gc.ca/pgol-pged/piatp-pfefvp/images/right.gif)