Attach 7 - Resource Allocation Schedules.xlsx
XLSX spreadsheet 18 KB Posted
- Solicitation number
- DPHHS-RFP-2024-0497KH
- Issued by
- Montana
About this file
The file is an Excel-based Resource Allocation Schedule attachment for the Montana Access to Quality Childcare System (MAQCS) Rebid, prepared for the Department of Public Health and Human Services (DPHHS). The document provides detailed instructions for offerors to complete two critical schedules: Schedule A for Full Time Equivalents (FTEs) and Schedule B for total resource hours across project phases including Initiation/Requirements, Design/Build/Configuration, Testing, Deployment/Implementation/Certification, and Operations. The schedules require contractors to comprehensively document staffing plans, with separate submissions required for prime contractors and subcontractors, and include a wide range of potential resource types such as Project Managers, Security Leads, System Architects, Developers, and Database Administrators.
The resource allocation instructions specify precise qualifications for resource positions, with Senior (Sr.) positions requiring either a four-year degree in a related field and five years of experience, or seven years of experience without a degree. All other positions must have a minimum of four years of related experience. While the current attachment shows zero entries for FTEs and hours, it serves as a template for potential contractors to detail their proposed workforce allocation across different project phases for the Montana childcare system database implementation. The document emphasizes flexibility, noting that the listed resource types are not exhaustive and encouraging offerors to add necessary roles to successfully deliver the project's scope of work.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| CCUBS Rows per table11.29.23.xlsx | XLSX spreadsheet | |
| Output_Inventory_MAQCS.xlsx | XLSX spreadsheet | |
| Project_Management_Deliverables_MAQCS.xlsx | XLSX spreadsheet | |
| Attach 8 - Technology Matrix.xlsx | XLSX spreadsheet | |
| Acronyms_Definitions_and_Terms_MAQCS.xlsx | XLSX spreadsheet | |
| CCUBS_Production_Calendar_2023_MAQCS.pdf | ||
| CCUBS_ERD_Tables_MAQCS.pdf | ||
| Section_5_Cost_Sheet.xlsx | XLSX spreadsheet | |
| 1200452-event.pdf | ||
| Attach 9 -Baseline Technical Requirements.xlsx | XLSX spreadsheet | |
| CCUBS_Data_Dictonary_MAQCS.xlsx | XLSX spreadsheet |
Show all 11
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
Attachment 7 - Instructions Attachment 7 - Instructions
| List of Schedules | |
| Schedule | Title |
| Schedule A | Number of Full Time Equivalents (FTE) |
| Schedule B | Number of Hours |
| Instructions: Offerors must complete both Resource Allocation Schedules. These schedules serve as the representation of Offeror's plan for staffing the project by resource type. Offeror should include additional information as necessary to explain the Offeror's resource allocation. If the Offeror has one or more subcontractors, the Offeror must submit a Schedule A and Schedule B with a comprehensive total for all FTE and hours representing the effort of the prime contractor and all subcontractor work in total. In addition, a separate Schedule A and Schedule B for each contractor (prime contractor and subcontractor) must be submitted. |
All schedules must be completed in full at the time of submittal. The resource types listed in the schedule are not exhaustive, nor should the Contractor assume that DPHHS is requesting resources from each category. Add resource types necessary to successfully deliver the scope of work.
Schedule A: This schedule details the number of full time equivalents the Offeror plans to allocate to the project by phase and by resource type.
Schedule B: This schedule details the number of resource hours the Offeror plans to allocate to the project by phase and by resource type.
page &P of &N
Sch A - FTEs by Phase
| Schedule A - Number of Full Time Equivalents (FTE) | |||
| Resource Type | Phase | ||
| Initiation / | |||
| Requirements | Design, Build, Config | Testing | Deployment / |
| Implementation / Certification | Operations | Total Resource FTE by Resource Type for all phases | |
| Project Manager | |||
| Contract Manager | |||
| Integration Lead | |||
| Security Lead | |||
| Security Analyst | |||
| Architecture Lead | |||
| System Architect | |||
| Sr. System Architect | |||
| Configuration Lead | |||
| Configuration Specialist | |||
| Sr. Configuration Specialist | |||
| Infrastructure Lead | |||
| Infrastructure Analyst | |||
| Developer | |||
| Sr. Developer | |||
| Database Lead | |||
| Database Administrator | |||
| Database Analyst | |||
| Sr. Database Administrator | |||
| Testing Lead | |||
| Tester | |||
| Technical Writer | |||
| Sr. Data Scientist | |||
| Data Scientist | |||
| System Analyst | |||
| Sr. System Analyst | |||
| Business Analyst | |||
| Sr. Business Analyst | |||
| Certification Lead | |||
| Training Lead | |||
| Trainer |
| Average Resource FTE Per Phase | ||||||
| Total Resources FTE Per Phase | 0 | 0 | 0 | 0 | 0 | 0 |
| The resource types listed are not exhaustive, nor should the Contractor assume that DPHHS is requesting resources from each category. Use any resource type listed above and/or add resource types necessary to successfully deliver the scope of work. |
Senior (Sr.) Positions are defined by a combination of education and experience and shall have a four year degree in a related field, and at least five (5) years of experience. In lieu of a four year degree, seven (7) years of experience is expected. All other positions must have a minimum of four (4) years of related experience. Please map your resource positions based on years of experience and educational requirements to the following generally named resource positions.
Sch B Total Hrs by Phase
| Schedule B - Number of Hours | |||
| Resource Type | Phase | ||
| Initiation / | |||
| Requirements | Design, Build, Config | Testing | Deployment / |
| Implementation / Certification | Operations | Total Resource Hrs. by Resource Type for All Phases | |
| Project Manager | |||
| Contract Manager | |||
| Integration Lead | |||
| Security Lead | |||
| Security Analyst | |||
| Architecture Lead | |||
| System Architect | |||
| Sr. System Architect | |||
| Configuration Lead | |||
| Configuration Specialist | |||
| Sr. Configuration Specialist | |||
| Infrastructure Lead | |||
| Infrastructure Analyst | |||
| Developer | |||
| Sr. Developer | |||
| Database Lead | |||
| Database Administrator | |||
| Database Analyst | |||
| Sr. Database Administrator | |||
| Testing Lead | |||
| Tester | |||
| Technical Writer | |||
| Sr. Data Scientist | |||
| Data Scientist | |||
| System Analyst | |||
| Sr. System Analyst | |||
| Business Analyst | |||
| Sr. Business Analyst | |||
| Certification Lead | |||
| Training Lead | |||
| Trainer |
| Total Resource Hrs. Per Phase | 0 | 0 | 0 | 0 | 0 | 0 |
| The resource types listed are not exhaustive, nor should the Contractor assume that DPHHS is requesting resources from each category. Use any resource type listed above and/or add resource types necessary to successfully deliver the scope of work. |
Senior (Sr.) Positions are defined by a combination of education and experience and shall have a four year degree in a related field, and at least five (5) years of experience. In lieu of a four year degree, seven (7) years of experience is expected. All other positions must have a minimum of four (4) years of related experience. Please map your resource positions based on years of experience and educational requirements to the following generally named resource positions.
File details come from the government source that posted it. Updated .