1 / 15

Workshop: EWB-USA PAPERWORK

Workshop: EWB-USA PAPERWORK . 16, February 2014. EWB-USA Cycle. Paperwork offer a systematic and official way for tracking the development of our programs Approve project feasibility by PM (Peter Waugh) Documentation Representative of our work and efforts

dunn
Download Presentation

Workshop: EWB-USA PAPERWORK

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. Workshop: EWB-USA PAPERWORK 16, February 2014

  2. EWB-USA Cycle • Paperwork offer a systematic and official way for tracking the development of our programs • Approve project feasibility by PM (Peter Waugh) • Documentation • Representative of our work and efforts • Reporting Process between the student chapter and national NGO • Submittal dates dependent on trip

  3. Program Development • Phase 1 - Establish community agreement, NGO partnership • Phase 2 – Water-filtration project • Phase 3 – Yagi Antenna • Phase 4 – Monitoring/Reflections 501 (B) 502 505 511 Pre: 521, 600/606 Post: 522, 506 Pre: 523, 524, 525, 600/606 Post: 526, 506 Pre: 527, 530 Post: 531

  4. Pillars of EwB projects • Engineering-related projects • Community-Driven! • Comply with the project process (paperwork/TAC) • Ensure health, safety, and welfare of users • Partnerships: Chapter + NGO + Community • Locally found materials & ease of monitoring • Sustainability, feasibility, & cost-effective • EDUCATION for independent use * These fundamental points require interdisciplinary work, efforts, and knowledge. Furthermore, paperwork serves as a basis for demonstrating that each is being satisfied to the best of our abilities.

  5. 523 – Alternative Analysis Report • The purpose of the alternatives analysis is to document the thought process that the chapter should go through to determine which alternative solution is best for a given situation.  There is sufficient information presented in this analysis to justify the choices made by the chapter for the project.  • i.e: if there are a number of different water sources that may be used for a water supply, the alternatives analysis would describe how the preferred source was chosen.  There is no prescribed methodology for carrying out this analysis.  Any method that the chapter finds useful can be used. • Deadline: 1 month before 524, 2 months before 525

  6. 524 – Preliminary Design Report • The 524 should present a complete design for the proposed implementation. The design, calculations, drawings and all other aspects of the design should be completed to the best ability of the chapter. The intent of this document is to allow the chapter the chance to receive feedback from the EWB-USA Projects Managers and modify the design as appropriate to incorporate those changes into the 525 Pre-Implementation Report submittal to the TAC • Deadline: 1 month before 525

  7. 525 – Pre-Implementation Report • This design document presents the final design of the project and the details of the proposed implementation trip. The document should be sufficiently detailed that someone with no background with the project would be able to use the document to construct all the proposed facilities. The project should be of the quality that would be sealed by a professional engineer for a project in the US. To allow time for review by EWB-USA Headquarters Staff, this report must be submitted in accordance with the deadlines posted on the EWB-USA website. Your trip will be postponed if your chapter does not meet the posted deadlines.

  8. TAC • Technical Advisory Committee of EWB-USA • Verifies the details of projects to ensure proper and successful implementation • Presentation to board of technical members • Comments and decisions to be granted permission for implementation • After reviewing 525 paperwork

  9. Source of “Know-How” • Instructions detailed by EWB-USA for writing • Template for each document • Transfer of knowledge between E-board/general members/Tech-groups • Notes and results from prototyping/assessment/on-site visits • Discussions with community leaders • Previously submitted paperwork • Practice & experience

  10. Expectations • Professional writing – “Graded” • Detailed/technical, but clear for average person • Representative of our chapter, projects, and efforts • Initiative and determination!

  11. Deadlines • Submittal deadlines are for an august trip, as we have done in the past few years • EWB-USA Deadline: Draft Deadline  EWB-BU Deadline • *Subject to change given progress

  12. 900 Series: PMEL

  13. Approach • Collaboration • Paperwork Workshop/transfer of knowledge • Work within tech groups and general meetings • Paperwork writing “parties” with food! • Working as a group to form drafts  editing • Use old paperwork as a guide • Ask QUESTIONS

  14. Getting Started • Sample paperwork review • Drive to Live (from draft to submission) • Start with collaboration on a google doc • Division of responsibilities • Plan for personal and official deadlines • Draft  editing  formatting • Questions!

More Related