Section Reviewer Page Date Original Comment Last Reply Author Last Reply Date Remediated Last Reply Text                                                                                        
(No Section Found) Klinger, Stephanie 2 5/22/2025 12:59 Required: If the documents list in the original revision history were not appropriately cited and modifications are needed, retain the original revision history and add what was changed in a new row in this table with the date and author. Michelle Newbold 6/8/2025 21:02 1 Remediated - Revision history is correct otherwise please clarify. 
(No Section Found) Klinger, Stephanie 7 5/22/2025 12:59 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. Michelle Newbold 6/8/2025 21:06 1 Document remediated in accordance with SEAS standards. 
Section Section 1 SYSTEM ARCHITECTURE AND HOSTING OPERATIONS Klinger, Stephanie 9 5/22/2025 13:00 Suggestion: Correct the typo. Michelle Newbold 6/8/2025 20:21 1 Corrected mater to master. 
Section Section 1 SYSTEM ARCHITECTURE AND HOSTING OPERATIONS Bandari, Naveen 9 5/23/2025 15:04 Please include core infrastructure components, such as server details, storage systems , data center details etc. Please call out in this section. Michelle Newbold 6/9/2025 10:05 1 6/9 Remediated w/ Naveen. 
Section Section 1 SYSTEM ARCHITECTURE AND HOSTING OPERATIONS McDaniel, Dan 9 5/21/2025 8:08 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.		 Michelle Newbold 6/9/2025 11:15 0 N/A
Section Section 1 SYSTEM ARCHITECTURE AND HOSTING OPERATIONS Klinger, Stephanie 12 5/22/2025 13:00 Required: UOC-295 and UOC-160 are not user story IDs. IV&V recommends the vendor review and update accordingly as they provided the ID for elaborated requirement. Patricka Coleman 6/10/2025 21:44 1 User Story IDs updated
Section Section 2 MONITORING DAILY OPERATIONS PERFORMANCE French, Shaun 13 5/26/2025 23:50 Required: More detail here please.  Is this the Agency’s DataDog, or UOC’s?  What metrics are tracked?  How are alerts logged and escalated? Michelle Newbold 6/11/2025 11:41 1 Via Michael Withrow: In the event that Docebo identifies a system issue - then UOC would be alerted via email and the problem and resolution would be captured on the Docebo Status website which tracks system health.

If UOC or the Agency identifies an issue then we would work through our own internal ticketing processes and the Learn hub system admin/owner would submit a ticket to Docebo and work with their support team to resolve the issue and update the UOC and Agency.
Section Section 2 MONITORING DAILY OPERATIONS PERFORMANCE McDaniel, Dan 16 5/21/2025 7:45 Required:  Please review 2.4 (and 2.3).  Are they required to exist even if “Not applicable”?  If they are N/A, what is the reason, and what is Exhibit 2-1 doing in 2.4?  It seems misplaced. Michelle Newbold 6/9/2025 11:17 1 6/9 Remediated with Dan. 
Section Section 2 MONITORING DAILY OPERATIONS PERFORMANCE Klinger, Stephanie 17 5/22/2025 13:01 Required: UOC-568 is not a user story ID. IV&V recommends the vendor review and update accordingly as they provided the ID for elaborated requirement. Patricka Coleman 6/7/2025 18:51 1 Update with correct User Story ID.
Section Section 1 OPERATIONAL PROCEDURES Klinger, Stephanie 18 5/22/2025 13:01 Clarification: Wouldn’t the reference be PD-14b as you are building on top of what was approved in PD-14a, which results being in the currently submitted version. Please advise. Patricka Coleman 6/7/2025 18:59 1 Updated
Section Section 1 OPERATIONAL PROCEDURES Klinger, Stephanie 18 5/22/2025 13:02 Clarification: Unclear where we are to find section 5.2 Monitoring Tools and Techniques, is it a different document than this? In addition the section 5.2 in this document states related to Minor Release Overview. Please advise and/or clarify in this section. Patricka Coleman 6/10/2025 21:31 1 Section updated to 2.2 
Section Section 1 OPERATIONAL PROCEDURES Klinger, Stephanie 18 5/22/2025 13:02 Clarification: Is this requirement applicable to Service Desk Release? If no, recommend updating this information to indicate as such since this deliverable is being reviewed for the Service Desk Release.  Patricka Coleman 6/7/2025 19:24 1 CCR-004 contract requirement for centralized mail is not in scope for FX Service Desk. However will be in scope for PSM.
Section Section 1 OPERATIONAL PROCEDURES Klinger, Stephanie 19 5/22/2025 13:02 Required: These user story IDs in exhibit 3-2 are incorrect and mismatched with the Story Title. IV&V recommends the vendor review and update accordingly as they provided the IDs for elaborated requirements. Michelle Newbold 6/6/2025 17:14 1 6/6 Reviewer must have JIRA access.  Request Sara E. to respond. 
Section Section 4 ROUTINE MAINTENANCE French, Shaun 20 5/26/2025 23:52 Required:  @Armstrong, William  Will, do you agree with this?  Should there be some mention of UOC vendor tracking, handling POAM, etc if corrective action by their SaaS vendor needed? Michelle Newbold 6/16/2025 12:07 0 Will delete 1st sentence in 4.2.  See text in yellow highlight for response to this item. 
Section Section 4 ROUTINE MAINTENANCE Bandari, Naveen 20 5/23/2025 15:10 Please include language on testing of patches and rollback plan process .Is there any automation process involved ? To auotomate patch management process where ever possible. Michelle Newbold 6/8/2025 21:44 1 Need to refer to Mike Withrow for explanation of Docebo.
Section Section 4 ROUTINE MAINTENANCE Klinger, Stephanie 21 5/22/2025 13:03 Required: These user story IDs in exhibit 4-1 are incorrect and mismatched with the Story Title. IV&V recommends the vendor review and update accordingly as they provided the IDs for elaborated requirements. Patricka Coleman 6/7/2025 19:15 1 User story IDs corrected
Section Section 5 RELEASE MANAGEMENT Klinger, Stephanie 23 5/22/2025 13:03 Suggestion: IV&V suggest adding the year for any of the dates in the Product updates to remove any ambiguity for readers. Patricka Coleman 6/10/2025 21:53 1 Updated
Section Section 5 RELEASE MANAGEMENT McDaniel, Dan 23 5/21/2025 7:49 ? Michelle Newbold 6/9/2025 11:18 1 6/9 Remediated with Dan. 
Count 18
Remediated 16 88.89%
Not Remediated 2 11.11%