Section Reviewer Page Date Original Comment Last Reply Author Last Reply Date Remediated Last Reply Text                                        
Section Section 2 ROLES AND RESPONSIBILITIES McDaniel, Dan 5 5/21/2025 12:37 Critical:  So far, the FX Report roles have not been defined officially in Prod, so this may be premature, but (1) this role is not in the preliminary documentation as an RBAC role and (2) there is an internal conflict of duties when an administrator can both actively alter data (by publication, e.g.) and change user roles.  Luke Barry 6/12/2025 12:46 1 I agree. Admin is not an RBAC role.
Section Section 3 STANDARD OPERATING PROCEDURES French, Shaun 6 5/23/2025 7:50 Required: What are the automated processes, where are they listed? Luke Barry 6/12/2025 12:55 1 The automated processes are referring to auto-refreshing the reports on the app. The list of processes is the list of report names.
Section Section 3 STANDARD OPERATING PROCEDURES Sidana, Parampreet 6 5/22/2025 15:54 Required - Log capturing and monitoring is not mentioned? Luke Barry 6/12/2025 13:01 1 Correct, log capturing is not a PBI process.
Section Section 3 STANDARD OPERATING PROCEDURES Klinger, Stephanie 6 5/22/2025 13:50 Required: Please review this document and add first references with acronyms as per the FX Program Style and Writing Guide, Section 2.5, where Appendix C provides common examples. Luke Barry 6/12/2025 13:04 1 I updated the document.
Section Section 3 STANDARD OPERATING PROCEDURES French, Shaun 7 5/23/2025 7:51 Deliverable Reviewers self-classify their comments (Add type, listed below, as first word in comment, in both comment tracker and Word documents):
Critical: The resolution of these comments, including clarifications, is essential and must be completed to approve deliverable. Discussion with the vendor is likely required to resolve. Required: (Documentation/corrections/formats) The resolution of these comments, including clarifications, is important and necessary to approve the deliverable. Conditional approval to move forward - project tasks dependent upon the approval on this artifact can commence. This artifact will be eligible for payment upon final approval. Suggestion: The resolution of these comments is not necessary for the approval of the deliverable.
Clarification: The resolution of this comment is dependent on discussion between Deliverable Reviewer and vendor. Vendor to reach out to the Deliverable Reviewer to discuss further PRIOR to remediation and resubmission. Vendor to update comment(s) with discussion notes.		 Luke Barry 6/12/2025 13:06 1 N/A
Section Section 3 STANDARD OPERATING PROCEDURES French, Shaun 7 5/23/2025 7:35 Required: Define regularly planned. Luke Barry 6/12/2025 13:07 1 I am flexible on the cadence. Perhaps a factor will be how much training is needed, probably more in the beginning.
Section Section 3 STANDARD OPERATING PROCEDURES French, Shaun 7 5/23/2025 7:37 Required: how often? Luke Barry 6/12/2025 13:09 1 I am flexible on the cadence. Perhaps a factor will be how much training is needed, probably more in the beginning.
Section Section 3 STANDARD OPERATING PROCEDURES French, Shaun 7 5/23/2025 7:37 Required: How/where/what tools will this be? Luke Barry 6/12/2025 13:12 1 Office hour meetings and forums occur here in MS Word and on Teams. There are SLMs detailing the ad hoc reporting request process. There will be training sessions.
Section Section 3 STANDARD OPERATING PROCEDURES French, Shaun 7 5/23/2025 7:38 Required: Where are the details?  There’s nothing in this section. Luke Barry 6/12/2025 13:22 1 The data analyst team will  follow contractual obligations to respond to ad hoc requests for reporting.
Section Section 3 STANDARD OPERATING PROCEDURES McDaniel, Dan 7 5/21/2025 15:49 Suggestion:  Would these typically be reported in the Service Desk / ServiceNow systems?  Suggestion is to add to the sentence: “...on reporting-specific issues submitted for correction in Service Desk.”  The reason is that “incident response” (as title suggests) is used by disaster reporting protocols to mitigate threats to the network, hardware, etc. Michelle Newbold 6/9/2025 11:27 1 6/9 Remediated with Dan. 
Section Section 3 STANDARD OPERATING PROCEDURES French, Shaun 7 5/23/2025 7:39 Required:  This section is empty of meaning.  This needs detail of the approach to change management, not an explanation of the benefits of change management. Luke Barry 6/12/2025 13:26 1 The detail is in the explanation. We will work with the stakeholders to develop the change management plan so requests are logged and implemented in an efficient manner.   
Section Section 3 STANDARD OPERATING PROCEDURES French, Shaun 7 5/23/2025 7:41 Required:  Where are the details around how DR and continuity of reporting solutions then?  The main O&M manual refers here. Luke Barry 6/12/2025 13:27 1 Disaster recovery of the data is handled by development, not the reporting team. 
Section Section 4 SECURITY AND DATA PROCEDURES French, Shaun 9 5/23/2025 7:43 Required:  This section is too general.  Where are these steps described and enumerated?  What audits are done, what validation checks are done?  When in the process do they occur?  What ETL processes are done and what is the general data flow?  Which “SQL data warehouse”? Luke Barry 6/12/2025 13:32 1 Data flows from Genesys and Dynamics and ETL occurs to get the data into SQL. The reporting team connects PBI to the UOC SQL data warehouse. The reporting team does not handle the audit logs and documentation of the ETL. 
Section Section 4 SECURITY AND DATA PROCEDURES French, Shaun 9 5/23/2025 7:42 Required:  Agree. Where is this well-documented? Luke Barry 6/12/2025 13:33 1 Audit logs are captured from ETL code handled by development.
Section Section 4 SECURITY AND DATA PROCEDURES French, Shaun 9 5/23/2025 7:44 Required;  Agreed they should.  But do they?  We need details on how you meet this. Luke Barry 6/12/2025 13:36 1 See RBAC roles documentation for the full description of limiting access based on RBAC role. 
Section Section 4 SECURITY AND DATA PROCEDURES French, Shaun 9 5/23/2025 7:46 Required:  What relevance to this project is this?  This section needs to be written for this project, and not generalized from other sources. Luke Barry 6/12/2025 13:38 1 This section is relevant to data privacy laws regarding data and healthcare.
Section Section 4 SECURITY AND DATA PROCEDURES French, Shaun 9 5/23/2025 7:47 Required: Which techniques of this type do you implement and how are they used? Luke Barry 6/12/2025 14:03 1 This would be used where possible. They are used to keep PII data anonymous.
Section Section 4 SECURITY AND DATA PROCEDURES Klinger, Stephanie 9 5/22/2025 13:51 Required: Please review spelling and grammar (including spacing) in this document using the FX Program Style and Writing Guide to make any necessary changes (e.g., grammar, spelling, a vs an, hyphen usage). Luke Barry 6/12/2025 14:05 1 Corrected.
Section Section 4 SECURITY AND DATA PROCEDURES French, Shaun 9 5/23/2025 7:47 Required: How is this education handled, and is it enforce-mandatory before access is granted? Luke Barry 6/12/2025 14:07 1 The analysts have all taken enforce-mandatory training to handle sensitive data.
Section Section 4 SECURITY AND DATA PROCEDURES French, Shaun 10 5/23/2025 7:48 Required: Elaborate please. Luke Barry 6/12/2025 14:11 0 I don't have any further information at this time. Version control exists in PBI with a Microsoft product called Fabric. The AHS research into the utility of Fabric is at the infancy stages.
Section Section 4 SECURITY AND DATA PROCEDURES French, Shaun 10 5/23/2025 7:49 Required: This feels inappropriate for a final deliverable.  Luke Barry 6/12/2025 14:13 0 I am fine with removing this piece of information and instead stating that version control does exist for UOC.
Section Section 4 SECURITY AND DATA PROCEDURES Sidana, Parampreet 10 5/22/2025 15:57 Clarification - Is fabric going to be a new tool introduced? Why it cant be done with existing version control tools?
When the talks will be completed to have verstion control method? Is it going to be new method, which is not existing in FX curently? How will it be different and align with current FX RM standards?		 Luke Barry 6/12/2025 14:13 0 I don't have any further information at this time. Version control exists in PBI with a Microsoft product called Fabric. The AHS research into the utility of Fabric is at the infancy stages.
Count 22
Remediated 19 86.36%
Not Remediated 3 13.64%