Question: Develop a proposal for the project Food processing plant construction Your company is invited to bid for a new food processing plant in Manitoba/Canada. As
Develop a proposal for the project Food processing plant construction
Your company is invited to bid for a new food processing plant in Manitoba/Canada. As part of the bid, you must include the following in the scope of work:
Registration and Permitting requirements:
All proposals for new construction must be reviewed for compliance by a Health Officer before construction starts.
Any person(s) constructing, a food processing establishment must first register the proposed food processing establishment with Manitoba Agriculture, Food and Rural
Initiatives on the approved form.
All plans and specifications and other information pertinent to review and approving the application must be submitted with the registration.
All food processing establishments require a Food Handling Establishment Permit prior to operating
1. Proposal Report
*Executive Summary: Provide an executive summary (overview) of the proposed project. Ensure a standard and transparent format for review by the sponsor and other executives. This document should be kept at a reasonable level of detail. This is an executive summary that describes how this project came about, who is involved, and the purpose of the project.].
* Project Background: Background information enables all parties to have a shared understanding of the proposed project and allows effective prioritization against other initiatives based on the strategic direction of the company's overall strategy.
* Project Scope: Describe how the objectives of the project will be achieved. It may be that the proposed project is part of a larger undertaking. If this is the case, then this section should describe how the proposed project fits into the broader undertaking and related projects that are planned for the future. Project scope defines the boundaries of a project. Think of the scope as an imaginary box that will enclose all the project elements/activities. It not only defines what you are doing (what goes into the box), but it sets limits for what will not be done as part of the project (what doesn't fit in the box). Scope answers questions including what will be done, what won't be done, and what the result will look like. The proposed scope should define the high-level boundaries of the project. If approved, the project team will be able to further define and plan the project and develop the Project Charter and other Phases deliverables. Identify what is NOT included in the project scope.
*High-Level Requirements: Describe the high-level requirements for the project. In other words, high level requirement means describing the high-level required functionalities for the project. For example, a few examples of the high level requirements for an IT project could be: Ability to allow both internal and external users to access the application without downloading any software. Ability to interface with the existing data warehouse application. Ability to incorporate automated routing and notifications based on business rules.
*Deliverables: Deliverables are tangible or intangible products or services produced as a result of the project that is intended to be delivered to a customer. A deliverable could be a report, a document, a software product, a server upgrade or any other building block of an overall project.
* Affected Parties: List stakeholders which will impact or will be impacted by the project.
* Risk Identification and Response: Identify the risks in your project and rank each risk (High, Medium, Low) based on the probability and impact. Identify the risk response plan and the contingency plan for each risk item that is ranked High or Medium.
*Implementation Plan: Describe how you plan to implement the project (i.e., how do you operationalize your plan?). For example, will all parts of the project be rolled out at once or will it be executed in phases? What will be included in each phase?
*Schedule and Budget: Use Microsoft Project Software and develop project schedule and baseline
2 List all the tasks in the project
3. Project start date
4. Duration for all the tasks
5. Precedence for all the tasks (you should create a network diagram to identify precedence for each task
Statutory Holidays must be entered into the project calendar for the duration of the project. -
6. Resource sheet must be filled in
Resources must be assigned for each task
Set your project as a "baseline"
Reference: GUIDELINE FOR THE DESIGN, CONSTRUCTION AND RECONSTRUCTION OF A FOOD PROCESSING ESTABLISHMENT (n.d.). Retrieved from: https://www.gov.mb.ca/agriculture/food-safety/regulating-food/pubs/cfs06s04a.pdf
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
