Submitted By:- MANISH KUMAR(IMB2010022)

DILEEP KUMAR (IMB2010036)

TECHNICAL PROPOSAL

Overview

Proposals in generalTypical parts of a proposal

RFP Proposal Recommendation

Project Completion Report

Feasibility

Written offer to . . .. . . perform work, do research, or solve

problems. . . another person has—who says, “How do

I solve this problem of ‘Should I convert the Accounting Department from PC-compatible computers to Mac?’”

. . . proposal writer has—who says, “I have this problem of needing funding for my research project.”

Definition of Proposal

Directed toward Governmental agency or agencies

Agency has a need—Request for Proposal = RFP

FoundationAgency has a need: RFP

Company: InternalDepartment has a need: RFP

Definition, cont.

Solicited: Responds to an RFPFormal—complete with all the

parts (cover, title page, front and back matter)

Informal—typically an internal memo

UnsolicitedFormalInformal

Proposal Types (Generally)

.

Types

Proposal

Known to Reader

Unknown to Reader

Known to Reader

Unknown to Reader

Solicited Unsolicited

FORMAL/INFORMAL

Your proposal will persuade the reader that. . . you have a task analysis with

reasonable assignments. . . and a realistic schedule with

balanced work loads. . . you are qualified to work on the

problem. . . you have a risk management plan. . . the schedule shows that you can

complete the project on time

Rhetorical Situation

Format Front matter Introduction Body

I. Technical sectionII. Management sectionIII. Cost section

Conclusion Attachments (Appendix materials)

Typical Parts of a Proposal

I. Technical elements—the technical solution to the problem

II. Management—proving that you can do what you say you will do

III. Cost—how much the solution will cost

Typical Parts of the Proposal

Focus on client’s needsUnderstand the client’s . . .

. . . limitations. . . capabilities

Presents the problem(s)Does client know of problem?

Determines . . .. . . amount of background. . . technical detail

Technical Section

Technical detailsMust convince client of . . .

. . . your understanding of the problem

. . . the soundness of the technical solution

Provides a plan (tasks and schedule) for solving the problem

Technical Section, cont.

ContainsProject´s purpose/scope (limitations)Methods/procedures (steps) and

rationaleResources (physical, personnel,

literature, etc.)Task breakdown (what will be done)

and timetable (when will it be done)

Technical Section, cont.

ScheduleSteps and tasks to solve the problemTime each task will takeStart and end dates; relation to other

tasks, duration and dependenciesPersonnel working on the task

Currently availableNeed to hire (justify)

Technical Section, cont.

Technical proposal

.

The introduction of the Technical Proposal should provide an overview of the entire project.

It should include a description of the proposed project, including the details of the expected impact of the completed project on clinical investigators and their research team.

The role of end user community throughout the project, as well as in the implementation and evaluation components should be included.

1. Introduction

This section of the Technical Proposal should provide a well thought out and solid technical plan for applying informatics and information technology to your proposed project.

This section should include a description of the methodology that will be used to complete the project, specific plan for implementation, approach to inter-group collaboration; and best practices applied.

2. TECHNICAL APPROACH

This section of the Technical Proposal should include: the approach to overall project management, timelines, and deliverables.

This section should also include a staffing plan that clearly demonstrates the appropriate allocation of personnel who are specifically qualified to achieve the goals described in the proposal and their responsibilities for deliverables.

The approach and management of necessary interdisciplinary team members and components should be clearly articulated.

3. PROJECT MANAGEMENT AND STAFFING

This section of the Technical Proposal should document the qualifications of the Offeror and all proposed subcontractor and collaborator staff.

The qualifications of the stated subcontractors and collaborators should also be documented, including relevant past experience.

4. DOMAIN KNOWLEDGE AND EXPERIENCE

This section should include the plan for and commitment of the Offeror and all affiliated organizations to wide distribution and sharing of tools/results of the proposed project.

This should include clearly identifying and providing information for obtaining/purchasing any required components.

5. DATA AND SOFTWARE SHARING PLANS

Attach all required resume/biographical sketches.

6. RESUMES/BIOGRAPHICAL SKETCHES

THANK YOU

.