Category Archives: _Doc-Prep Guidance

TAD Section 4.3 — System Overview

1 Organization and Formatting

1.1 General (same as for other B-sheets; follow this link for easy reference)

1.2 Sheet-Specific — Making it All Fit

It’s a blank page; use it however you wish. Be sure to keep images and annotations large enough that they are easily read.

2 Content Presentation

There is no specific Page Input or Page Output textboxes/content to be addressed for this page(s).
Provide views of a graphical model that are appropriate for the type of design (physical, mechanical CAD, electrical CAD, etc.).
- Include more than one view (different viewing perspectives and/or of different subsystems) to assist the reader.
- The graphical modeling should fully describe your final system-level concept.
- Include descriptions of detail-level conceptual features and their functionality and manufacturability.
Graphics should be annotated labeling key components, subsystems, features.
Explicitly note system-level concept design decisions related to safety and manufacturability, pointing them out where possible on the graphics by way of annotations.
Brief, bullet-point text should be provided to explain the function of each part, its material composition, and the way it will be made (and who will make it) or where it will be purchased.

3 Examples of Great Work

Do a great job and be the first!

Updated September 09, 2022

TAD Section 4.2 — Supporting Engineering Summary

1 Organization and Formatting

1.1 General (same as for other B-sheets; follow this link for easy reference)

1.2 Sheet-Specific — Making it All Fit

It’s a blank page; use it however you wish. But, be sure to use it carefully to fit as much as you can while maintaining clarity and connectivity among the engineering results. You can have a second sheet if needed. Two pages is enough space, and one page is not significantly more space than needed (i.e., if you have a lot of excess space on a single page, you have likely fallen short, and the remedy is not just making the text and/or figures obnoxiously big to consume space).

2 Content Presentation

There is no specific Page Input or Page Output textboxes/content to be addressed for this page(s).
Summarize calculations and other technical/engineering work done to support your final system-level concept selection rationale/decisions (i.e., that the chosen final concept is indeed better than the others).
Put the details in Appendix C; only provide a thorough summary here (e.g., show here the methods used, the final results, and decisions made from each; all the inputs and intermediate steps and results between the inputs and final results are for Appendix C).

3 Examples of Great Work

Do a great job and be the first!

Updated September 09, 2022

TAD Section 4.1 — Pugh Analysis

1 Organization and Formatting

1.1 General (same as for other B-sheets; follow this link for easy reference)

1.2 Sheet-Specific — Making it All Fit

See the Page-Specific guidance for the System-Level Concept Evolution pages.

2 Content Presentation

Commence the page by populating the Page Input textbox. List any information that has evolved during the earlier rounds leading to this highly narrowed field of final candidate concepts.
Insert graphical renderings from the DP Manager Excel Use the copy table buttons on the Excel worksheet (typically the “Copy Table with Heading” button for use in the TAD). Include:
the round’s Pugh Analysis chart (below the Page Input textbox); and
the data table for the round’s best system-level concept.
In the pre-titled Notes textbox, provide conclusive reasoning for your concept assessment claims, referencing the supporting engineering summarized on the next page.
Complete the page by populating the Page Output textbox. In this case, the page output simply includes where this information is next used and for what and/or how it is used (“where next”).

3 Examples of Great Work

Do a great job and be the first!

_Excel_{is a registered trademark of Microsoft Corporation.}

Updated September 09, 2022

TAD Section 3 — System-Level Concept Evolution

1 Organization and Formatting

1.1 General (same as for other B-sheets; follow this link for easy reference)

1.2 Sheet-Specific — Making it All Fit

How you lay out the information on the sheet is up to you. The example provided is simply an example, but given that the Pugh Analysis chart and best system-level concept data sheet are consistently sized/shaped as shown, this layout may serve you well. Of course, as usual, the Page Input textbox should be at the top left and the Page Output textbox should be at the bottom right if at all possible.

2 Content Presentation

Commence the page by populating the Page Input textbox. In this case, the page input depends on which round you are in:
- If this is the first round, indicate highlights from the initial datum. Highlights include both favorable and unfavorable features.
- Otherwise, list any trends or signs that have evolved in earlier round(s) in regard to certain function-level concepts or combinations of them that tend to produce favorable results.
Insert graphical renderings from the DP Manager Excel workbook. Use the copy table buttons on the Excel worksheet (typically the “Copy Table with Heading” button for use in the TAD). Include:
- the round’s Pugh Analysis chart (below the Page Input textbox); and
- the data table for the round’s best system-level concept.
In the pre-titled Notes textbox, provide all relevant notes summarizing relative rationale with a focus on engineering requirements where the best concept fared better or worse than other concepts considered in this round.
Complete the page by populating the Page Output textbox. In this case, the page output includes two elements:
- a brief narrative of your reasons for the best-concept decision, based on the Pugh Analysis by describing the numbers (scoring based on +, =, −) and anything deeper than the numbers alone the factored into the decision (this is important to build credibility in regard to your decision abilities); and
- what was learned from this round that serves as guidance for the next round (this is really important as this is a thoughtful learning process, not a blind random process).

3 Examples of Great Work

Do a great job and be the first!

_Excel_{is a registered trademark of Microsoft Corporation.}

Updated September 09, 2022

TAD Section 2.3* — Information Gathering

* This is TAD Section 2.4 for “Failure-Resolution” Projects.

1 Organization and Formatting

1.1 General (same as for other B-sheets; follow this link for easy reference)

1.2 Sheet-Specific — Making it All Fit

How you lay out the information on the sheet is up to you. The example provided is simply an example. Of course, as usual, the Page Input textbox should be at the top left and the Page Output textbox should remain at the bottom, better yet at the bottom right if at all possible.

2 Content Presentation

There is no specific Page Input textbox/content needed for this page. Instead, the entirety of the “Data/Facts/Information” gathered is in a sense input from the sources you identify for each piece of information.
Use the pre-titled Function-Level Concepts — Data/Facts/Information box to generate a list of information gathered about all function-level concepts that will be satisfied by commercial off-the-shelf (COTS) components and/or subsystems. Also include results of trials that confirm, for any unconventional, uncertain concepts, that the concept will, in fact, provide the intended function. Formatting this information as a table instead of bullet points is an option to consider. In any case, group by function-level concept and for each indicate:
- The related main system function.
- A brief description of the representative item found in a catalog or other source, including identifying number.
- Relevant metrics such as but not limited to purchase price, weight, size, materials, and performance specs (such as but not limited to power/stall-torque/max-speed for a motor; generated force and travel distance for a linear actuator, pneumatic cylinder, etc.; sensitivity, voltage/current input and output, etc. for a sensor).
- Reference information so you or someone else can find the source of this information at a later date — do not put this in your references list, just put it here, and be specific, for example, the URL for the specific page for the specific item in an online catalog.
Insert a graphical rendering of the initial system-level datum from the DP Manager Excel workbook; that is, the datum to be used in the first-round of system-level concept assessment. Use the copy table buttons on the Excel worksheet (typically the “Copy Table with Heading” button for use in the TAD).
Complete the with the page by populating the Page Output textbox. In this case, the page output simply includes where this information is next used and for what and/or how it is used (“where next”).

3 Examples of Great Work

Do a great job and be the first!

_Excel_{is a registered trademark of Microsoft Corporation.}

Updated September 09, 2022

TAD Section 2.2* — Function-Level Concepting

* This is TAD Section 2.3 for “Failure-Resolution” Projects.

1 Organization and Formatting

1.1 General (same as for other B-sheets; follow this link for easy reference)

1.2 Sheet-Specific — Making it All Fit

How you lay out the information on the sheet is up to you. The example provided is simply an example. Depending on the relative size and aspect ratio of your function structure diagram, rearranging may be needed. Of course, as usual, the Page Input textbox should be at the top left and the Page Output textbox should remain at the bottom, better yet at the bottom right if at all possible.

2 Content Presentation

Commence the page by populating the Page Input In this case, the page input includes any special opportunities, such as for multi-functionality, or limitations, such as functional means you should steer away from either due to advise or requirement by your customer or related challenges you have uncovered.
Insert a graphical rendering of the morph chart from the DP Manager Excel workbook. Use the copy table buttons (in this case without the heading (“Copy Table Only”) for the TAD). As previously noted, (and the last reminder why to do it this way), the code that the button triggers places a good resolution picture graphic on the clipboard for then pasting into any other destination.
In the one or more Notes textboxes (configured as noted above), provide in bullet point lists descriptions elaborating on any function-level concept that is not obviously and completely described by its short title in the chart. Also, make note of any multi-functionality potentials you have conceived. Emphasize any concepts that come with uncertainty as to their ability to really provide the function desired (common when using commercial-off-the-shelf (COTS) items in unconventional and creative ways). Also emphasize concepts that are particularly exciting for what they will provide. Often, but not always, the former (uncertainty) and latter (exciting) are connected.
Complete the page by populating the Page Output textbox. In this case, the page output simply includes where this information is next used and for what and/or how it is used (“where next”).

3 Examples of Great Work

Do a great job and be the first!

_Excel_{is a registered trademark of Microsoft Corporation.}

Updated September 09, 2022

TAD Section 2.2* — Root-Cause Failure Analysis

* This is ONLY for “Failure-Resolution” Projects. | For Standard Projects skip to here.

1 Organization and Formatting

1.1 General (same as for other B-sheets; follow this link for easy reference)

1.1 Sheet-Specific — Making it All Fit

2 Content Presentation

Commence the page by populating the Page Input In this case, the page input is information describing the failure to be resolved.
Next, in the pre-titled Testing/Analysis Plan textbox, provide information on how you will systematically seek the root cause of the failure. Complement this textbox with graphics (typically) below it and to the upper right.
Next, in the pre-titled Page Output — Failure Cause Conclusion textbox, once determined, and this could be weeks down the road, provide a precise and concise yet complete/detailed description of the failure cause.
Complete the page by populating the pre-titled Page Output — Relevant Main Solution Functions Hopefully the textbox title tells you what to put here.

3 Examples of Great Work

Do a great job and be the first!

Updated September 21, 2022

TAD Section 2.1 — Main System Functions

1 Organization and Formatting

1.1 General (same as for other B-sheets; follow this link for easy reference)

1.2 Sheet-Specific — Making it All Fit

2 Content Presentation

Commence the sheet by populating the Page Input textbox. In this case, the page input is information from the use case(s). These page inputs (and outputs) being included on each page may seem redundant at this point, but they are important to keeping clear to the reader your thought-flow from one page to the next, noting further that connected pages are not always sequential. The key word there — your — is to realize that your audience reading this cannot read your mind in regard to the logical flow of thinking that resulted in your work-product presented on each sheet.
Begin with a single phrase or sentence that defines the overall system function. A pre-titled Overall System Function textbox is provided.
Next, in the pre-titled Function Structure Diagram box/frame, provide a function structure diagram drawn in the software of your choice then copied and pasted as a bitmap or other appropriate graphic format.
Insert graphical renderings of the functional recomposition table and House of Quality from the DP Manager Excel workbook. Like for the engineering requirements tables, you should first sort the table in a logical way; that is, use the button provided as doing so will invoke code that will assure no behind-the-scenes formulas (i.e., in hidden rows/columns) or formatting rules get messed up. Then use the copy table buttons on the Excel worksheet (typically the “Copy Table with Heading” button for use in the TAD). As previously noted, the code the button triggers places a good resolution picture graphic on the clipboard for then pasting into any other destination.
In the pre-titled Notes box, provide relevant clarifying notes about your function structure diagram, main system functions, and house of quality. Include information such as:
- Describe why your product/process is functionally broken down this way.
- Describe how the main system functions work together to create a system-level solution to the design problem.
- Provide reasons and examples for several relationships between the engineering requirements (the “Hows”) with the functions (the “Whats”) and correlations among functions (which indicate areas of extra challenge but also may indicate potential for multi-functional design elements).
- All clarifications should complement the information in the graphics/tables and not be a simple repetition of the information provided within the graphic/table.
Now, for each main system function, graphically “encircle” the elements in the function structure diagram that are grouped into that main system function. In some way indicate the main system function associated with each encirclement (e.g., color coding and/or leaders to main system function names and/or connections/leaders to the main system function table (though that could get messy), and/or your other creative ideas on how to communicate this). The objective is to make it clear where the main system functions fall within (and groupings of) the detail of the function structure diagram. It may be easier to do this in the software in which you created the function structure diagram, though there are drawing capabilities in Google Slides that are reasonably good for this purpose.
Complete the page by populating the Page Output textbox. In this case, the page output simply includes where this information is next used and for what and/or how it is used (“where next”).

3 Examples of Great Work

Do a great job and be the first!

_Excel_{is a registered trademark of Microsoft Corporation.}

Updated September 09, 2022

TAD Section 1.2 — Engineering Requirements

1 Organization and Formatting

1.1 General (same as for other B-sheets; follow this link for easy reference)

1.2 Sheet-Specific — Making it All Fit

How you lay out the information on the sheet is up to you. The example provided is simply an example. Depending on the relative sizes of tables, etc., rearranging may be needed. One exception, which hopefully is seen as logical, is that the Page Input textbox should be at the top left and the Page Output textbox should remain at the bottom, better yet at the bottom right if at all possible.

2 Content Presentation

Commence the sheet by populating the Page Input In this case, the page input are those sources that have provided information that is crafted into the engineering requirements and their quantification. List the party by party (e.g., customer, end-user) those that have a vested interest in defining requirements, and briefly state why. Some examples that should be included are (shown below as they may be written, but you should likely expand upon and/or be more specific than these examples):
- Customer contact (John Doe): he is responsible for the project and its eventual transition to the field.
- End-users (multiple): the people who will be using the solution have certain needs for its safe and efficient setup and use.
- Codes and standards (ASME XXXXXX): this code addresses xxxxxxxxx.
Insert graphical renderings of the engineering constraints and engineering objectives tables from the DP Manager Excel workbook. You should first sort each table in a logical way; that is, use the buttons provided as doing so will invoke code that will assure no behind-the-scenes formulas (i.e., in hidden rows/columns) or formatting rules get messed up. Then use the copy table buttons on the respective Excel worksheet (typically the “Copy Table with Heading” button for use in the TAD). The code the button triggers places a good resolution picture graphic on the clipboard for then pasting into any other destination.
For each set of requirements (constraints and objectives), there is a pre-titled End-User, Customer… Provide here what you heard from your sources and put in square brackets the one or more requirements it influenced. You may also include clarifications that complement the information in the respective table, not a repetition of information in the table. Note that “measurement descriptions” in the tables should (typically, 19 of 20 times) be sufficiently descriptive as concisely presented in the space provided in the table. The following should be clear to a reader:
- why an engineering requirement is a requirement, that is, why is it necessary.
- reasoning that supports its quantification (limits for constraints, target for objectives).
- any other relevant notes that support information summarized in the table.
Complete the page by populating the Page Output textbox. In this case, the page output is a brief description of where this information is next used and for what or how it is used (hint: many places, including functional decomposition and recomposition to main system functions, system-level concept assessment, and verification planning).

3 Examples of Great Work

Do a great job and be the first!

_Excel_{is a registered trademark of Microsoft Corporation.}

Updated September 09, 2022

TAD Section 1.1 — Use Cases

1 Organization and Formatting

1.1 General (same as for other B-sheets; follow this link for easy reference)

1.2 Sheet-Specific — Accommodating One or More End-User Cases

Three sheets are provided in the template with subtitles of End-User Case 1 (Short Name), End-User Case 2 (Short Name), and End-User Case 3 (Short Name).

If you have three end-user cases, you are all set.
If you have only two end-user cases, delete the third sheet of the three provided.
If you have only one end-user case:
- delete the second and third sheets of the three provided, AND
- delete the subtitle (text field) End-User Case 1 (Short Name) from the one remaining sheet.

2 Content Presentation

For each end-user use case (one sheet each):

If you have more than one end-user cases (i.e., the sheet subtitle has not been deleted as noted above), provide a short descriptive name in the sheet subtitle, replacing the text Short Name; for example: Machine Operator, Tool-Room Technician, Surgeon, and Surgical Technician.
Begin with a use-case flow diagram. A pre-titled Flow Diagram box/frame is provided. An example is included on the template.
In the pre-titled Description textbox, provide a concise but thorough textual description of the steps and their sequence, making liberal use of bullet-point and/or numbered lists and, only if necessary, short paragraphs (2-3 sentences, rather than long paragraphs).
Complete the page by populating the pre-titled Page Output In this case, the page output includes conclusions and where this information is next used (“where next”) and for what and/or how it is used (hint: engineering requirements; you need to say more than that though!). As noted, this concluding box is very important to help someone “reading this story” to follow the technical storyline — your logical flow of thought. The conclusions should succinctly indicate the needs and wants that evolve from the use case. The “where next” aspect should be a brief comment/description on where this information will next be used and how. This is important so your audience can follow the thinking path through your work product presented in this and the continuing sequence of pages. Many pages in the TAD have a Page Output textbox, again because its content is important for your reader to follow the flow of your thinking.

3 Examples of Great Work

Do a great job and be the first!

Updated September 09, 2022