| Section |
Reviewer |
Page |
Date |
Original Comment |
Last Reply Author |
Last Reply Date |
Remediated |
Last Reply Text |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Section Section 1 SYSTEM OVERVIEW |
Klinger, Stephanie |
6 |
5/22/2025 13:20 |
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. |
Mike Collins |
6/2/2025 10:39 |
1 |
I think I got them all |
|
| Section Section 2 ROLES AND
RESPONSIBILITIES |
McDaniel, Dan |
9 |
5/21/2025 12:46 |
Style: Fonts on this page should
match. |
Michelle Newbold |
6/9/2025 10:57 |
1 |
6/9 Remediated with Dan. |
|
| Section Section 2 ROLES AND
RESPONSIBILITIES |
McDaniel, Dan |
9 |
5/21/2025 12:52 |
Required: “Intended” is not an
appropriate adjective for a role (repeated twice
more below). |
Michelle Newbold |
6/9/2025 11:00 |
1 |
6/9 Remediated with Dan. |
|
| Section Section 2 ROLES AND
RESPONSIBILITIES |
McDaniel, Dan |
9 |
5/21/2025 12:48 |
Clarification: By “allows full
access,” does this mean can read a folder, view a
file, make changes? Clerical options
such as file editing should not be permitted to Admins. Please be precise so the limits of the role
are known. |
Michelle Newbold |
6/9/2025 11:01 |
1 |
6/9 Remediated with Dan. |
|
| Section Section 3 STANDARD OPERATING
PROCEDURES |
French, Shaun |
10 |
5/26/2025 23:57 |
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. |
Mike Collins |
6/2/2025 10:40 |
0 |
N/A |
|
| Section Section 3 STANDARD OPERATING
PROCEDURES |
French, Shaun |
10 |
5/26/2025 23:58 |
Required: We need to know what reports are
available, not what can be done. Also
the previous sentence mentions a variety of tools are readily available.
Please list and describe them and their usages. |
Mike Collins |
5/29/2025 15:52 |
1 |
I narrowed it down to the one tool.
Power BI is tricky, please let me know how to reword the “SLM requirements”
piece (that lists all the reports which are available). Or I could just name
some of the reports? - Thanks |
| Section Section 3 STANDARD OPERATING
PROCEDURES |
French, Shaun |
12 |
5/26/2025 23:59 |
Required: How are these dashboards being made
available to the Agency? |
Mike Collins |
5/29/2025 15:57 |
1 |
Clarified user vs admin notification
methods. |
|
| Section Section 3 STANDARD OPERATING
PROCEDURES |
French, Shaun |
12 |
5/26/2025 23:59 |
Required: How are these being made available
to the Agency? |
Mike Collins |
6/2/2025 10:40 |
1 |
Discussed ways power users and
admins can access data system usage |
|
| Section Section 3 STANDARD OPERATING
PROCEDURES |
French, Shaun |
12 |
5/27/2025 |
Required: Where is the frequency and detail of
this described? |
Mike Collins |
6/2/2025 10:41 |
1 |
Replaced automated backups with the
more descriptive “continuous incremental backups” |
|
| Section Section 3 STANDARD OPERATING
PROCEDURES |
French, Shaun |
13 |
5/27/2025 0:02 |
Required: This describes recovery from an
outage, but how do you deal with other forms of disaster? Network outages affecting a specific data
center (can you force switch region?), cyberattack, randomware, etc. |
Mike Collins |
6/2/2025 10:53 |
1 |
I added some more information,
specifically more info about how the failovers work and a summary of data
breach prevention |
|
| Section Section 4 SECURITY AND DATA
PROCEDURES |
French, Shaun |
14 |
5/27/2025 0:03 |
Required: This is not accurate. |
Mike Collins |
5/29/2025 16:09 |
1 |
Updated, trimmed it down a bit to
avoid saying anything it shouldn’t. |
|
| Section Section 4 SECURITY AND DATA
PROCEDURES |
French, Shaun |
14 |
5/27/2025 0:06 |
Required: This whole section reads
like marketing material from DataVerse. Please rewrite for the appropriate
audience. |
Mike Collins |
5/29/2025 16:15 |
1 |
Trimmed the fat and only put in
things specifically used by UOC |
|
| Section Section 4 SECURITY AND DATA
PROCEDURES |
French, Shaun |
15 |
5/27/2025 0:04 |
Required: How do you anticipate the Agency
will be using DataVerse to create comprehensive business solutions? |
Mike Collins |
5/29/2025 16:15 |
0 |
Good question. Deleted. |
|
| Section Section 4 SECURITY AND DATA
PROCEDURES |
French, Shaun |
15 |
5/27/2025 0:05 |
Required: How will this be made available to
the Agency? |
Mike Collins |
5/29/2025 16:17 |
1 |
I deleted it, pretty much a repeat
of the earlier monitoring tools description. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Count |
14 |
|
|
|
|
|
|
|
|
| Remediated |
12 |
85.71% |
|
|
|
|
|
|
|
| Not Remediated |
2 |
14.29% |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|