1 / 10

MUNDAUS GROUP

MUNDAUS GROUP. PROPOSAL PREPERATION. Proposal Pipeline. Breaking Out Proposal Preparation. Deciding on approving to target a project is the first process in proposal management. The process of developing proposals is very in depth and there are various stringent requirements in every field.

berg
Download Presentation

MUNDAUS GROUP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. MUNDAUS GROUP PROPOSAL PREPERATION

  2. Proposal Pipeline

  3. Breaking Out Proposal Preparation • Deciding on approving to target a project is the first process in proposal management. • The process of developing proposals is very in depth and there are various stringent requirements in every field. • A simplified overview breaks down the process of preparing proposals.

  4. Filtering Responsibilities All proposal information is collected after filtering responsibilities – Define Roles. Data is collected and compiled.

  5. Standard Proposal Request Request for Proposal (RFP) RFPs provide detailed specifications of what the customer wants to buy and sometimes include directions for preparing the proposal, as well as evaluation criteria the customer will use to evaluate offers. Customers issue RFPs when their needs cannot be met with generally available products or services. RFIs are issues to qualify the vendors who are interested in providing service/products for specific requirements. Based on the response to RFI, a detailed RFP is issued to qualified vendors who the organization believes can provide desired services. Proposals in response to RFPs are seldom less than 10 pages and sometimes reach 1,000's of pages, without cost data. Generally Cost data is in a secondary volume for Pricing. Request for Quotation (RFQ) Customers issue RFQs when they want to buy large amounts of a commodity and price is not the only issue--for example, when availability or delivering or service are considerations. RFQs can be very detailed, so proposals written to RFQs can be lengthy but generally much shorter than an RFP-proposal. RFQ proposals consist primarily of cost data, with small narratives addressing customer issues, such as quality control. Request for Information (RFI) Sometimes before a customer issues an RFP or RFQ or IFB, the customer will issue a Request for Information (RFI). The purpose of the RFI is to gain "marketing intelligence" about what products, services, and vendors are available. RFIs are used to shape final RFPs, RFQs, and IFBs, so potential vendors take great care in responding to these requests, hoping to shape the eventual formal solicitation toward their products or services. Invitation for Bid (IFB) Customers issue IFBs when they are buying some service, such as construction. The requirements are detailed, but the primary consideration is price. For example, a customer provides architectural blueprints for contractors to bid on. These proposals can be lengthy but most of the length comes from cost-estimating data and detailed schedules .

  6. Data Input Based on the proposal type, various responsibilities for data input will be given to Members and Subcontractors for completion. Following the process pipeline all data is to be input into the database and validated for compilation by the Project Leader. Various inputs will include design work, cost estimation, methodology etc. Responsibilities are given on a contract by contract basis and will follow the proposal pipeline process.

  7. Defining Review Teams The goal of a Pink Team review is to ensure that the structure of the response is appropriate. The review focuses upon whether the win strategy is sound and whether the proposed technical and management approaches support this strategy. Pink Team The Red Team review tries to evaluate the persuasiveness of the proposal, i.e., how well the proposal clearly presents and sells the solution. Red Team reviews are undertaken when the proposal is essentially complete; suggested changes are incorporated in previous reviews. Red Teams reviews also try to mimic the customer’s evaluation process. Red Team The Gold Team review should be conducted in coordination with the Project Leader. The other participants should include the Board Members. This review team should concentrate primarily on last minute proposal compliance and quality. GoldTeam

  8. Proposal Review Process Implement Win Strategy Prepare Draft 2 Prepare Draft 1 Kickoff Review RFP Conduct Red Team Verbal Presentation Conduct Project Leader Develop Work Packages Conduct Pink Team Prepare Draft N Conduct Gold Team Prepare Final Draft Prepare for Kickoff Award • Final Edit • Final Review • Final Preparation • Final Approval • Annotated Outline • Assignments • Work Packages • Style Guide • Background • Briefing Attend Debrief • Red Team • Recovery • Decision to • Proceed • Pink Team • Recovery • Outline Frozen In Process Review Bid | No Bid Decision Orals DTL Edit Collect Lessons DTL Edit In Process Review Brainstorm and Research INTEGRATION PLANNING WRITING POLISHING PRODUCTION POST

  9. Standard Review Teaming Pink Team GoldTeam Red Team Develop Draft Update Proposal Finalize Proposal Project Leader In-Process Review BEGINS COMPILATION PROCESS SUBMIT TO CLIENT

  10. Defining Symbols Acceptance Input Data Files Validate Filter Web Data Base Proposal Review Award Acceptance Process Output

More Related