Upcoming Webinars
Access the latest trends and insights shaping the profession—free for members.
.png)
 (1).jpg)
_1.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.png)
.jpg)
.jpg)
.jpg)
Document
ART - Award - Public Bid Opening via Webcasting 2011
Year Created: 2011
DOCUMENT
RFP - Risk Management Information System 2004
- YEAR CREATED: 2004
- ENTITY TYPE: County
- TYPE OF DOCUMENT: RFP - Request for Proposals
- Management
- Technology
The document outlines the requirements and format for submitting a proposal for a project. The document includes various sections such as an introduction and executive summary, company profile, organizational structure and key staff resumes, experience and reference summary, overview and technical capabilities of the application, project schedule with milestones, physical data model, SDLC adherence, specification checklist, miscellaneous information, and price proposal and worksheet.
The introduction and executive summary section requires a concise summary of the proposal, including conclusions, assumptions, and recommendations. The company profile section asks for information about the company's history, primary business, contact details, years of experience in claims management software, ownership type, financial statement, and licensing status.
The organizational structure and key staff resumes section requires a description of the proposed project team and resumes of the project manager, technical team lead, and other key staff. The experience and reference summary section asks for a summary of relevant experience and references, including project details, client information, contract period, products/services provided, contract amount, and status.
The overview and technical capabilities of the application section requires an overview of the application and a detailed discussion of its technical capabilities, including system requirements, operating system requirements, functionality, adherence to open system standards, system architecture, and database requirements. The training requirements and offerings section asks for details about the training options, audience, training environment, and sample session agendas.
The support/enhancements section requires the vendor to specify technical support and maintenance services, including remote support, support staff ratio, warranty coverage, sharing of enhancements, product upgrades/enhancements developed in the past three years, testing policies, and future plans for the proposed solution.
Additionally, the document now mentions the need to identify modifications, perform modifications, install the proposed solution, train users and administrators, and move the solution to production. These tasks should be included in the project schedule with milestones, showing their significance in the overall project timeline.