Logbook Webpage

8/8/2019 Logbook Webpage

http://slidepdf.com/reader/full/logbook-webpage 1/22

CommunicationLogbook / Website

Monday 27 September 2010



The Design Process

Laws of Physics

Economics

Legal

Conceive Idea /

Concept

@ 30,000 ft

The Ground @ 0 ft ASL

Product

Recognize Need

Define Problem

Concept 3Concept 2

Concept 1

Constraints:

Detailed Design

Build / Test

Implement / Operate

Iterate



Communication throughout …

Selling the Idea. [Promotion]

Customer solicitation / patents / marketplace. [Data collection]

Team-based design. [Information control and distribution]

Detailed records of what was done. [Logbook]

Formal documentation. [Reports, simulations, models]

Present progress. [Interim Reviews]

Product launch / Design Fair. [Website, Tradeshow]

Communication is both Receiving and Broadcasting.



Communication includes …Strategy:

Analyze the situation (target audience).

Structure:

Logical, persuasive arguments.

Concise, crisp, precise, and clear language.

Cross-disciplinary / Cross-cultural communication.

Written Communication:

Coherence and flow.

Correct spelling, punctuation, and grammar.

Document formatting.

Informal, formal memos, reports, etc.



Communication includes …Electronic / Multimedia Communication:

Powerpoint (or equivalent)

Graphical Communication:

Sketching and engineering graphics.

Construction of tables, graphs, charts, etc.

Read technical drawings and renderings.

Norms for e-mail, voicemail, videoconferencing

Electronic styles (Google docs, website, etc.)

Oral Presentation:

Appropriate language, style, timing and flow.

Nonverbal (gesture, eye contact, poise).

Answering questions effectively.



The Engineering LogbookPersonal / professional reference documenting project

evolution and learning.

Protects intellectual property, bound so that pages cannot be

inserted / removed.

Written in ink, dated, and fill consecutive pages.

In the event of an investigation, it will be reviewed by the

professional regulatory bodies and / or by the courts.



The Logbook



The Engineering Logbook

Bound Notebook.

Write in ink.

Carry journal everywhere.

Paste / staple in items collected.

Date all journal entries.Two witnesses sign and date new ideas.

Write in the journal daily.



General Expectations

5-6 pages of thoughtful entries per week supporting the design process

Log of planning, communications, team meetings, lecture notes (~ 20% entries)

Project learning and product development (~ 70% of entries)

Review of individual / team / product performance (~ 10% of entries)

Organization / format for easy re-reading / reuse (self, team, mentor, instructor)



Industry ExpectationsRecord the date on each page. Start each day on a new page.

Label each entry and record this in a table of contents (reserve 3-4 front pages)

Use ink, do not erase, delete entries by drawing single line through them.

Do not remove pages, do not skip pages.

Avoid backfilling. If a new idea comes, write it in and refer back to original date.

Include everything …

Sketches / doodling

Class notes

Meeting notesHalf-baked ideas

Work in progress

Vendor notes

Sources of ideas

Design reviews

Design processProject reflections

Customer needs / requirements

Project objectives

Action itemsMath calculations

Design alternatives

Research findings

Evaluation of data / results

Decision criteria

Rationale for decisionsProfessional development



Logbook Prompts:A meeting:

What were the main outcomes of the meeting?

Was the meeting productive, why?

What are your personal action items before the next meeting?

Is the team heading in the correct direction?

Brainstorming:

Which ideas seem most feasible, and why?

Are there enough good ideas?

How could better ideas be developed based on this session?

Engineering Analysis:

What were the governing equations?

What are the most important findings?

What do the results mean and how should they be applied?

Visualization (sketching or CAD):

What are the major features / discoveries and why are these significant?

What was learned about the problem or solution possibilities?

What problems were resolved and what still needs to be addressed?How does this piece integrate with the whole?



Logbook Prompts:Internet search:

What key information was found?

How does it help achieve the project objectives?

Are there other sources that should be pursued?

What new questions were generated?



Project Website

Each group will maintain their own website.

We will create links from the department home page.Links will be under the “Industry” tab.

All teams will use Kompozer.

User Guide: www.kompozer.net/Community

Use template from University of Idaho:

http://seniordesign.engr.uidaho.edu/first_semester_docs/web-template.zip

Upload: SSH Secure File Transfer http://www.ucalgary.ca/it/software/ssh/windows/install

Project Advisors / Customers will monitor your progress.



Kompozer Interface



SSH Secure File Transfer



After Clicking Quick Connect



Browser type Interface



Local – Your Computer Remote – UofC Server



Disconnect when Done



Course Roadmap

Team Assignments (this week)

Project Definition Document (PDD) - reportAssigned 29 Sep 10

Due 8 Oct 10

Conceptual Design Document (CDD) - reportAssigned 6 Oct 10

Due 22 Oct 10

Preliminary Design Review (PDR) - presentation3 Nov 10 [1PM – 5PM]

Peer Review and Logbooks



Course Roadmap - 2

Critical Design Review (CDR) - presentation

8 Dec 10 [1PM – 5PM]

Peer Review and LogbooksFall Final Report (FFR) - report

Due 10 Dec 10

Interim Review #1 (IR1) – presentation, informal2 Feb 11 [1PM – 5PM]

Interim Review #2 (IR2) – presentation, informal

2 Mar 11 [1PM – 5PM]Peer Review and Logbooks

Winter Project Review (WPR) – presentation

6 Apr 11 [1PM – 5PM]Peer Review and Logbooks



Course Roadmap - 3

Winter Design Fair (WDF) - tradeshow

TBD ~ Early Apr 11

Project Final Report (PFR) - report

Due 15 Apr 11

Logbook Webpage

Documents

Transcript of Logbook Webpage