PL 003.pdf
PDF 325 KB Posted
- Attached to
- Pharmacy Benefit Services (PBS)
- Solicitation number
- 5400029905
- Issued by
- Richland County, South Carolina
About this file
This is a Project Status Report template for the Delivery of Automated Systems for Healthcare (DASH) Program, a state and local healthcare technology implementation project. The document serves as a standardized weekly reporting mechanism to track project progress across multiple critical areas including project management, contract deliverables, scheduling, resource allocation, system development lifecycle requirements, functional design, configuration and development, testing and software quality assurance, data conversion, data management, implementation and deployment, training, and organizational change management. The report utilizes a traffic light health indicator system (Green for "On Target," Yellow for "At Risk," and Red for "In Jeopardy") to provide visual project status across each functional area, with specific criteria defined for each color rating based on deliverable timeliness, schedule performance indices, resource availability, task delays, risk mitigation status, and issue severity levels.
The report template includes structured sections for documenting action items by completion status, change requests in process with approval dates, approved and pending deliverables, inbox items for change requests and risks, open and closed issues categorized by severity and priority, open and closed risks with response strategies, and detailed project area updates covering activities completed during the reporting week and planned activities for the following two weeks. The template accommodates both vendor and state comments and activities across all project components, enabling collaborative tracking between the implementing vendor and state stakeholders. While the document provides no specific pricing information, incumbent details, funding sources, or contract term information, it establishes the governance and reporting framework necessary for managing a complex healthcare system implementation project requiring coordination across multiple functional disciplines and stakeholder groups.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| ATTM 021.pdf | ||
| ATTM 022.pdf | ||
| ATTM 024(a).docx | DOCX document | |
| ATTM 016.pdf | ||
| ATTM 014.pdf | ||
| ATTM 005.docx | DOCX document | |
| ATTM 006.docx | DOCX document | |
| ATTM 008.xlsx | XLSX spreadsheet | |
| PL 001.docx | DOCX document | |
| ATTM 009.xlsx | XLSX spreadsheet | |
| ATTM 017.pdf | ||
| ATTM 024(b).xlsx | XLSX spreadsheet | |
| ATTM 018.pdf | ||
| PL 002.pdf | ||
| ATTM 003.docx | DOCX document | |
| ATTM 013.xlsx | XLSX spreadsheet | |
| ATTM 019.pdf | ||
| ATTM 011.pdf | ||
| ATTM 015.pdf | ||
| ATTM 023.xlsx | XLSX spreadsheet | |
| ATTM 010.docx | DOCX document | |
| ATTM 026.docx | DOCX document | |
| ATTM 020.pdf | ||
| ATTM 007.docx | DOCX document | |
| Solicitation 5400029905.docx | DOCX document | |
| ATTM 025.docx | DOCX document | |
| ATTM 012.xlsx | XLSX spreadsheet | |
| ATTM 004.docx | DOCX document | |
| ATTM 001.docx | DOCX document | |
| ATTM 002.docx | DOCX document |
Show all 30
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
Delivery of Automated Systems for Healthcare (DASH) Program
[project acronym] Project Status Report
Submitted by:
Fill in Project Manager Names
Week Ending:
PL 003
[acronym] Project Status Report
V5.0 Page 1 of 11
PROJECT HEALTH INDICATORS
Evaluated Area Current Period
Trending
Comments
Project Management Contract Deliverables Vendor Comments:
State Comments:
Schedule Vendor Comments:
State Comments:
Resources Vendor Comments:
State Comments:
SDLC
Requirements Vendor Comments:
State Comments:
Functional/Design Vendor Comments:
State Comments:
Configuration/Development Vendor Comments:
State Comments:
Test/Software Quality Vendor Comments:
State Comments:
Data Conversion Design Vendor Comments:
State Comments:
Data Management Vendor Comments:
State Comments:
Implementation (Deployment)/Training
Planning Vendor Comments:
State Comments:
Organizational Change Management Planning Vendor Comments:
State Comments:
V5.0 Page 2 of 11
Health Indicator Criteria
Joint Weekly Status Report
On Target Criteria At Risk Criteria In Jeopardy Criteria
G
Y
R
Contract Deliverables
No contract deliverables are currently late for submission, resubmission, or sign-off
Contract deliverable(s) are late for submission, resubmission, or sign-off, but critical path is not impacted
Contract deliverable(s) are late for submission, resubmission, or sign-off and critical path is impacted
Schedule • SPI is ≥ 0.95; and
• Critical path is late by ≤5 working days
• SPI is ≥ 0.9 and ≤ 0.94; or
• Critical path is late by < 15 and > 5 days
• SPI is < 0.9; or
• Critical path tasks is by
> 15 working days
Resources • Planned resources are assigned; and
• Resource levels are sufficient to finish the project under the current schedule and scope
• Work is delayed up to 15 working days due to lack of resources; and
• Resource levels are sufficient to finish the project under the current schedule and scope
Work is delayed more than 3 weeks in 1 or more areas due to lack of resource(s)
SDLC
Requirements • No tasks are late by more than 5 working days; and
• Monitored risks may exist in this area, and mitigation is planned or in progress
• No tasks are more than 15 working days late; and
• All related, monitored risks have mitigation planned or plan is in progress
• One or more tasks are late by more than 15 working days; or
• Monitored risks exist in this area without mitigation plans; or
• Open high severity issues exist
Functional/ Design • No tasks are late by more than 5 working days; and
• Monitored risks may exist in
• All related, monitored risks have mitigation planned or plan is in progress
• One or more tasks are late by more than 15 working days; or
• Monitored risks exist in this area without mitigation plans; or
• Open high severity Issues exist
Configuration/Deve lopment
• No tasks are late by more than 5 working days; and
• Monitored risks may exist in this area, and mitigation is planned or in progress
• No tasks are more than 15 working days late; and
• All related, monitored risks have mitigation planned or plan is in progress
• One or more tasks are late by more than 15 working days; or
• Monitored risks exist in this area without mitigation plans; or issues exist
V5.0 Page 3 of 11
On Target Criteria At Risk Criteria In Jeopardy Criteria
G
Y
R
Test/Software Quality
• No tasks are late by more than 5 working days; and
• Monitored risks may exist in this area, and mitigation is planned or in progress; and
• No severity 1 (showstopper) bugs exist
• All related, monitored risks have mitigation planned or plan is in progress; or
• No more than 1 severity 1 bug exists
• One or more tasks are late by more than 15 working days; or
• Monitored risks exist in this area without mitigation plans; or
• Open high severity issues exist; or
• More than one severity 1 bug exists
Data Conversion
Design • No tasks are late by more than 5 working days; and
• Monitored risks may exist in
• All related, monitored risks have mitigation planned or plan is in progress
• One or more tasks are late by more than 15 working days; or
• Monitored risks exist in this area without mitigation plans; or
• Open high severity issues exist
Data Management • No tasks are late by more than 5 working days; and
• Monitored risks may exist in
• All related, monitored risks have mitigation planned or plan is in progress
• One or more tasks are late by more than 15 working days; or
• Monitored risks exist in this area without mitigation plans; or
• Open high severity issues exist
Implementation (Deployment)/Training
• No tasks are late by more than 5 working days; and
• Monitored risks may exist in
• All related, monitored risks have mitigation planned or plan is in progress
• One or more tasks are late by more than 15 working days; or
• Monitored risks exist in this area without mitigation plans; or
• Open high severity issues exist
ORGANIZATIONAL CHANGE MANAGEMENT
• No tasks are late by more than 5 working days; and
• Monitored risks may exist in
• All related, monitored risks have mitigation planned or plan is in progress
• One or more tasks are late by more than 15 working days; or
• Monitored risks exist in this area without mitigation plans; or issues exist
V5.0 Page 4 of 11
Trending column indicators:
= No change from previous reporting period
= Positive change from previous reporting period
= Negative change from previous reporting period
ACTION ITEMS
Action Items by Status
[Insert statistics table]
Completed Action Items
[Insert list of completed action items]
Overdue Action Items
[Insert list of overdue action items]
Action Items Due in the Next 2 Weeks
[Insert list of action items due in the next 2 weeks]
CHANGE REQUESTS
[See Change Management Plan for Additional Details on Change Request Metrics]
Change Requests In-Process
[Insert Data Only from “Status Report In-Process Change Request” View] ID Title Change
Request Owner
Status Approval Date
Deferred Until Date
Closure Date
V5.0 Page 5 of 11
DELIVERABLES
Approved Deliverables [Insert table of approved Deliverables]
Deliverables in Review
[Insert table of Deliverables in Review; include on-schedule indicator]
Deliverables Due to the State in the Next 2 Weeks
[Insert table of deliverables due to the State in the next 2 weeks]
Deliverables Due to Vendor in the Next 2 Weeks
[Insert table of deliverables due to the Vendor in the next 2 weeks]
INBOX ITEMS FOR THIS REPORTING PERIOD
[Insert statistics and list of InBox items; the InBox is the entrance point for change requests, risks, issues, and deliverables]
ID Title State Created Notes Submitter
ISSUES
[See Issue Plan for Additional Details on Issue Metrics]
Issues by Severity and Priority
[Insert Data Only from Pivot Table]
V5.0 Page 6 of 11
Open Issues*
[Insert Data Only from “Status Report Open Issues” View]
ID Issue Title Issue Severity
Issue Priority
Issue Owner Issue Status
Issue Resolution
Date
* Excludes Closed and Rejected Status
Issues Closed Since Last Report*
[Insert Data Only from “Status Report Closed Issues” View] ID Issue Title Issue
Severity Issue
Priority Issue Owner Issue
Status Issue
Closure
* Includes Closed and Rejected Status with Issue Closure Date since last report
RISKS
[See Risk Plan for Additional Details on Risk Metrics]
Risks by Priority and Status
Open Issues Severity
High Medium Low Grand Total
Pr io rit y High 4 4
Medium 1 1 2
Low
Grand Total 5 1 6
Open Risks Priority
V5.0 Page 7 of 11
[Insert Data Only from Pivot Table]
Open Risks*
[Insert Data Only from “Status Report Open Risks” View]
ID Risk Title Risk Owner Risk Priority
Risk Response Strategy
Risk Trigger
Risk Status
* Excludes Closed and Rejected Status
Risks Closed Since Last Report*
[Insert Data Only from “Status Report Closed Risks” View] ID Risk Title Risk Owner Risk
Priority Risk
Response Strategy
Risk Closure Date
Closure Reason
* Includes Closed and Rejected Status with Risk Closure Date since last report
PROJECT AREA UPDATES
This section includes the Vendor and State activities worked during the status week, the activities planned for the next two weeks, metrics for the ongoing work, and items of importance or interest for the project team.
High Medium Low Grand Total
St at us
Assigned 1 1
Draft 1 1
Monitoring 1 1
Pending Approval 1 1
Planning 1 1
Grand Total 1 2 2 5
V5.0 Page 8 of 11
PMO
Vendor Activities during the Week
Vendor Activities Planned for Next Two Weeks
Vendor Metrics and/or Additional Information
State Activities during the Week
State Activities Planned for Next Two Weeks
State Metrics and/or Additional Information
QUALITY ASSURANCE
Vendor Activities during the Week
Vendor Activities Planned for Next Two Weeks
Vendor Metrics and/or Additional Information
State Activities during the Week
State Activities Planned for Next Two Weeks
State Metrics and/or Additional Information
Infrastructure (Hardware and Software)
Vendor Activities during the Week
Vendor Activities Planned for Next Two Weeks
Vendor Metrics and/or Additional Information
V5.0 Page 9 of 11
State Activities during the Week
State Activities Planned for Next Two Weeks
State Metrics and/or Additional Information
REQUIREMENTS AND DESIGN
Vendor Activities Planned for Next Two Weeks
Vendor Metrics and/or Additional Information
State Activities during the Week
State Activities Planned for Next Two Weeks
State Metrics and Additional Information
Configuration/Development
Vendor Activities Planned for Next Two Weeks
Vendor Metrics and/or Additional Information
State Activities during the Week
State Activities Planned for Next Two Weeks
V5.0 Page 10 of 11
TEST/SOFTWARE QUALITY
Vendor Activities during the Week
Vendor Activities Planned for Next Two Weeks
Vendor Metrics and/or Additional Information
State Activities during the Week
State Activities Planned for Next Two Weeks
DATA CONVERSION
Vendor Activities Planned for Next Two Weeks
Vendor Metrics and/or Additional Information
State Activities during the Week
State Activities Planned for Next Two Weeks
ORGANIZATIONAL CHANGE MANAGEMENT
State Activities during the Week
State Activities Planned for Next Two Weeks
V5.0 Page 11 of 11
IMPLEMENTATION (DEPLOYMENT)/TRAINING
Vendor Activities Planned for Next Two Weeks
Vendor Metrics and/or Additional Information
State Activities during the Week
State Activities Planned for Next Two Weeks
FEDERAL CERTIFICATION
Vendor Activities Planned for Next Two Weeks
Vendor Metrics and/or Additional Information
State Activities during the Week
State Activities Planned for Next Two Weeks
| PROJECT HEALTH INDICATORS |
| ACTION ITEMS |
| CHANGE REQUESTS |
| DELIVERABLES |
| INBOX ITEMS FOR THIS REPORTING PERIOD |
| ISSUES |
| RISKS |
| PROJECT AREA UPDATES |
File details come from the government source that posted it. Updated .