RFP No. 283-24-0642 Attachment 1c Schedule of Deliverables.docx
DOCX document 35 KB Posted
- Attached to
- Grant & Contract Review Support "GCRS"
- Solicitation number
- 283-24-0642
About this file
This is a Schedule of Deliverables attachment to RFP No. 283-24-0642 for Grant & Contract Review Support services for the Substance Abuse and Mental Health Services Administration (SAMHSA). The schedule outlines 33 general requirements deliverables and specific task deliverables related to program management, contract technical support, honorarium payments, and transition activities.
Key deliverables include: IT Plan due 60 days after award; Privacy Threshold Analysis within 30 days; Information Security and Privacy training requirements within 30 days; System Authorization to Operate before system go-live; monthly vulnerability scan reports; Web Content Migration Plan within 60 days; monthly teleconference meetings and reports; technical writer support for peer review meetings (requiring 5-25 meetings with reports due within 10 days); and honorarium payment processing for contract reviewers within 10 business days after meetings. The contract includes optional tasks for additional grant honorarium support (10-50 applications) and increased contract technical support services. The bulk of work is expected between January and August annually, with February through June being peak periods.
View the file
Other files
Show all 23
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
RFP No. 283-24-0642 Attachment No. 1c
Schedule of Deliverables
General Requirements
| Item |
| Timeline |
| To |
| Section |
| 1 |
| Final Information Technology (IT) Plan |
| 60 calendar days after award. Review annually |
| DTM thru Contracting Officer's Representative (COR) |
| II |
| 2 |
| Meeting on systems or websites migration from third-party hosted service to SAMHSA |
| At least 60 calendars days or earlier before the planned migration date |
| DTM Infrastructure Team thru COR |
| V |
| 3 |
| IT and Web Cost Reports |
| Twice a year (July and November) |
| DTM Federal Information Technology Acquisition Reform Act (FITARA) Team thru COR |
| IV |
| 4 |
| IT Investment Factsheet |
| 90 calendar days after award and update annually |
| DTM FITARA Team thru COR |
| IV |
| 5 |
| Website Domain Registration |
| When registered and when requested |
| DTM FITARA Team thru COR |
| IV |
| 6 |
| Privacy Threshold Analysis (PTA) |
| 30 calendar days after award |
| Privacy and Chief Information Security Officer (CISO) and Info.Privacy@samhsa.hhs.gov thru COR |
| V |
| 7 |
| Entity, data type and relationship diagrams |
| No later than 30 calendar days after award |
| CISO and Info.Privacy@samhsa.hhs.gov thru COR |
| V |
| 8 |
| Draft system’s Privacy Impact Assessments (PIAs) if full PIAs is needed |
| No later than 45 calendar days after contract effective date (CED) |
| Privacy Officer and Info.Privacy@samhsa.hhs.gov thru COR |
| V |
| 9 |
| Encryption Key if applicable |
| When requested or at the end of the contract |
| Info.Privacy@samhsa.hhs.gov and COR |
| V |
| 10 |
| Information Security Awareness and Privacy training |
| Within 30 calendar days after CED and annually |
| COR |
| V |
| 11 |
| Security and Privacy Role-based Training |
| Within 30 calendar days after CED and annually |
| COR |
| V |
| 12 |
| Security and Privacy Training Records |
| Within 35 calendar days after CED and annually |
| COR |
| V |
| 13 |
| Read and sign Rules of Behavior |
| Within 35 calendar days after CED and annually |
| COR |
| V |
| 14 |
| Staff Roster |
| Within 30 calendar days after CED and 10 days when staffing changes |
| COR |
| V |
| 15 |
| Project Closeout/System Decommission meeting |
| At least 30 calendar days before project closeout/system decommission |
| DTM thru COR |
| V |
| 16 |
| Initiate security assessment and authorization (SA&A) process |
| No later than 30 calendar days after CED |
| CISO thru COR |
| V |
| 17 |
| System Authorization to Operate (ATO) |
| Before system goes live |
| CIO and CISO |
| V |
| 18 |
| Information System Security Plan (ISSP) (with supporting artifacts and documents listed on the ATO package and the Security Checklist.) |
| Part of ATO package, before system goes live |
| CISO and security email box infosecurity@samhsa.hhs.gov |
| V |
| 19 |
| E-Authentication Questionnaire (Risk Assessment) |
| Within 30 calendar days after CED |
| CISO and infosecurity@samhsa.hhs.gov. Template can be requested by emailing CISO and ISSO. |
| V |
| 20 |
| Privacy and security kickoff meeting |
| Within four (4) weeks of CED |
| COR and CISO |
| Work plan |
| 21 |
| Annual Penetration Testing Summary Report |
| Annually, anytime during a contract year |
| COR and DTM Security Team |
| V |
| 22 |
| Vulnerability scan reports for database, application, and operation system |
| Every 30 days after ATO is granted |
| Upload to SAMHSA Sharepoint Site directed by the SAMHSA Security team and COR |
| V |
| 23 |
| Vulnerability “Change Report” and Cloud Security Continuous Monitoring Reporting |
| Every 30 days after ATO is granted |
| Upload to SAMHSA Sharepoint Site directed by the SAMHSA Security team and COR |
| V |
| 24 |
| Permanent electronic records |
| 60 days prior to period of performance expiration |
| DTM Records Management Officer |
| XXXI 2. 3. |
| 25 |
| Records management training and provide Contractor Records Management Training Completion Memorandum |
| Within 30 days of contract award or new contract staff start date and then annually for the life of the contract. |
| COR |
XXXI 2. 11.
| 26 |
| Electronic Systems Questionnaire |
| Responses within 4 weeks after the CED and 30 days prior to modifications to system |
| DTM thru COR during the kickoff meeting |
| XXXI 2.12. |
| 27 |
| HHS Accessibility Checklist |
| Each content deliverables |
| COR |
| OC requirements I. G |
| 28 |
| Content Development and Management Plan |
| Within 60 days after CED |
| OC and DTM (including Records Officer) thru COR |
| OC requirements IV. A |
| 29 |
| Web Content Approval |
| No later than 3 weeks prior to the planned initial posting of document |
| COR |
| OC requirements IV. C |
| 30 |
| Web Content Migration Plan including a demo |
| Within 60 days after CED; demo within 30 days after CED |
| COR and DTM (including Records Officer) thru COR |
| OC requirements IV. D |
| 31 |
| Meeting on IT transition activities related to data, software, web content, and electronic records |
| Within 30 days after CED |
| COR, DTM, and OC |
| OC requirements IV. E |
| 32 |
| Reports of actual Web-related IT costs |
| Twice a year (July and November) |
| OC and DTM thru COR |
(could be combined with IT and Web Cost reports, see #3) OC requirements IV. F
| 33 |
| Transition Task |
| Schedule meeting with COR and DTM to discuss transition activities |
| COR and DTM |
| Transition Task |
Specific Requirements
| Task |
| Item |
| Quantity |
| Due Date |
Task 1: Program Management and Reporting Activities
| Task 1.1 |
| Kick-Off Meeting |
Kick-Off Meeting Summary Report
No later than (7) business days after Contract Effective Date (CED)
Within one (1) business day after meeting
| Task 1.2 |
| Draft Work Plan |
| 1 |
| Two (2) business days before the Contract kick-off meeting date |
| Task 1.3 |
| Final Work Plan |
Draft Work Plan for next year
Final Work Plan for next year
Within one (1) week after receipt of comments from the COR on the draft Work Plan
48 weeks after CED
Within two (2) week after COR comments
| Task 1.4 |
| Task 1.4: Monthly Teleconference Meeting |
Summary of Monthly Teleconference Meeting
At the end of each month
Within one (1) business day of meeting completion
Task 1.5
Monthly reports
Draft Annual Report
Final Annual Report
10th day after the end of the month
No later than three (3) weeks before the end of the year
No later than one (1) week after receipt of COR comments
Task 3: Contract Technical Support
| Task 3.2 |
| Provide Technical Writers for Peer Review Meetings |
Technical Review Summary Report Summary * Others
Writers’ fee
Writers’ Summary fee
Seven (7) business days after task received
Ten (10) calendar days after meeting 20 calendar days after meeting
Ten (10) business days after meeting
Ten (10) business days after COR acceptance of the final Summary
| Task 3.3 |
| Provide Technical Writers for Objective Review Meetings |
Technical Review Summary Report
Seven (7) business days after task received
Ten (10) business days after meeting
Ten (10) business days after COR acceptance of the final Summary
| Task 3.5 |
| Establish and Maintain Reviewer and Technical Writer Database |
| 1 |
| TBD |
Task 4: Honorarium Payments Support
| Task 4.1 |
| Contract Reviewer Honorarium payments |
| TBD |
| Ten (10) business days after meeting |
| Task 4.2 |
| Grant Honorarium Payment Support |
| TBD |
| Ten (10) business days after receipt of honorarium documents |
Task 5: Transition of Contract Specific Activities
Startup at the beginning of contract
Turnover at the end of contract
Implement a smooth transition Participate in meetings with previous contractor
Plans for transfer of project
Meetings with the new Contractor Five (5)
One (1)
Five (5) TBD – As director by CO
No later than two (2) months prior to completion of the final period of performance
TBD – As director by CO
Optional Task 6: Ability to increase Grants honorarium support for ten (10) applications
| Optional Task 6 |
| Ability to increase Grants honorarium support for ten (10) applications |
| 10 |
| Within ten (10) business days of receipt of honorarium documents |
Optional Task 7: Ability to increase Grants honorarium support for fifty (50) applications
| Optional Task 7 |
| Ability to increase Grants honorarium support for fifty (50) applications |
| 50 |
| Within ten (10) business days of receipt of honorarium documents |
Optional Task 9 – Ability to increase Contract Technical Support
| Optional Task 9 |
| Provide Technical Writers for Objective Review Meetings |
Technical Review Summary Report
Seven (7) business days after task received
Ten (10) business days after meeting
Ten (10) business days after COR acceptance of the final Summary
Optional Task 10 – Ability to hold an In-Person Contract Review Meeting
| Task 10.1 |
| Contract Reviewer Honorarium payments |
Reviewer travel
| 5 |
| Honoraria mailed within ten (10) business days following the close of the meeting |
Reimbursement checks for travel mailed by no later than 30 calendar days after receipt of Reviewers travel voucher
| Task 10.2 |
| Finalize Contract with Hotel for Lodging and Meeting Rooms for the Technical Merit Peer Review Committee Meetings |
| 1 |
| Within four (4) weeks of the Option Task Effective Date (OTED) |
| Task 10.4 |
| Provide Technical Writers for In-Person Review Meetings |
Technical Review Summary Report
Within seven (7) business days after receipt of the task
Ten (10) business days after meeting
Ten (10) business days after COR acceptance of the final Summary
File details come from the government source that posted it. Updated .