Write 500 words proposal

https://www.cisco.com/c/dam/en_us/solutions/industries/government/wsca/docs/Packet_for_Bid.pdf

Proposals are a common part of pretty much any project that will ever happen. It is common that when a company wants something done, they will put out the RFP, and many companies will respond in part with their own designs. For example, in the past the US army was looking to refit a plane to become a flying aircraft carrier. Because of this, aircraft designers each proposed their own designs. These companies included Boeing and Lockheed Martin. They both proposed designs that were modifications on both the Boing 747 and the C17 respectively (I think). When the USA put out their RFP, it showed many of their requirements, such as ones related to fueling, as well as the ability to load and unload planes with ease. They also had to be able to perform repairs on the planes themselves while they were inside the main craft. To put it simply, the USA had requirements, and Boeing and Lockheed Martin both submitted proposals in return that met said requirements. Such proposals included models and diagrams, timeframes for project completion as well as costs. All these things are something that should always be in a proposal. The requirements you provided such as summaries, descriptions, introductions, purposes, as well as the plans, everything was shown. This is all information that is important, since we need money to work with proposals, facilities to make them, personnel to build them. Even in less professional environments, I've seen people write proposals in very similar ways, perhaps for small things in the workplace, a class, or even online groups. - Conclusion - Appendices For real-world examples, take a look at the RFP issued by the State of Utah and the proposal submitted in response by Cisco. While your own work on an RFP and proposal won't have the legalese you see see in these examples, I wanted you to see how these documents can work out in the world. To this end, what kind of work do you see these documents doing? Assess this work by using relevant information from the "Checklist for Developing Proposals and Progress Reports" (pp. 263-64), and previously discussed checklists, such as "The Qualities of Good Technical Writing" (p. 8), the "Style Checklist" (p. 76), and the "Document Design Checklist" (pp. 104). As the conversation among your group members continues, please add additional examples of RFPs and proposals. It can sometimes be difficult to find examples of proposals that were submitted to a specific RFP. If you can find such examples, that's great. If you can't you can provide stand-alone examples of each. For example: RFPs: Hawai'i Tourism Authority, Towson University, Center for Planning Excellence Proposals: Mercer, Goold Health Systems NOTE: It is not uncommon for recommendation reports to be labeled proposals. Oftentimes, such a proposal will propose a recommendation and hence why it might be labeled a proposal. However, we are interested in proposals that propose to do work that the proposal-submitting company/organization is then hired to implement. T\&D explain, "The starting point of projects is often a proposal. A proposal offers to provide a service or a product to a client or customer in exchange formoney. Usually, when a business enterprise orgovernment agency desiges to have some of work or research done, it wants thte best job for the best price. It will advertise the work it wants done and invite interested indivuals or organization to conect it. This document is usualy called a request for proposals (RFP) or a statement of work (SOW) (p. 236). In response to an RFP, an organization will submit a proposal in the hopes of being chosen to do the work proposed in the proposal. T\&D state on p. 241, Proposals generally include three main divisions: a summary, a main body, and attachments. The main body focuses on the three main parts of the proposals; the proposal's objectives ... methods for achieving objectives ..., and project cost ... Proposals vary, but you will see the following segments embedded in some way: - Project summary - Project description - Introduction - Rationale and significance - Plan of Work - Scope - Methods - Task breakdown - Problem analysis - Facilities and equipment - Personnel - Budget