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

This one sheet serves three purposes:

• brief/quick preparation for your audience prior to the meeting (“pre-meeting briefing”);
• a guide for the CSR meeting, for you and your audience members; and
• a take-away for your audience.

1     Organization and Formatting

• There are four (4) sections that progress according to the numbers in their respective headings.
• There are two layouts from which you can choose based on how you think apportioning the space between sections 2 and 3 works best for you:
  1. The first goes from top-left down to bottom-left then over and up to top-right and down to bottom-right (top-to-bottom then left-to-right, or “TBLR”).
  2. The second goes from top-left over to top-right then back over and down to bottom-left and over to bottom-right (left-to-right then top-to-bottom, or “LRTB”).
• Each section on the sheet has, below its heading, a text field with a prompt for a short sentence to provide context (replace that prompt with yours) followed by a bullet-list starter “Xxxxx”.
• The top headings (left- and right-columns) are on the respective master layout (named “PMB-TBLR” or “PMB-LRTB”) and should not be moved. The other two headings may be moved up or down (hold the shift key down to maintain vertical alignment) to redistribute space as it better serves you.  Do NOT change the wording of any of the headings.
• Remember, like the PUR PMB, this is highlights, what will prep your audience before the meeting and that you will use to lead the discussion at the start of the meeting.
  • It need not be jam packed; you are allowed/encouraged to have your IRD content pages at hand to reference for details as needed.
  • The content should be graphics-rich with minimal text. Aim for (minimum) 75% of the space consumed by graphics (with the exception of sections 3 and 4 which will likely, though not necessarily, be mainly text).
  • But do not try to include all of your graphics relevant to the respective section. Be thoughtfully selective; you can have your IRDs to reference as noted, and the graphics on the PMB must be large enough to see any important feature on the graphic.
  • Think of each of the four sections as a “slide” dominated by graphics with some bullet points to complement the graphics.
• Regarding graphics:
  • Graphics include annotated CAD, illustrations, plots, and photos as well as tables. Yes, annotate plots as needed (often but not all of the time) to point out what is of particular interest.
  • Graphics used here are copied and pasted from your other docs.
  • Choose graphical elements of substance, not just to be present as a token non-textual element that is otherwise useless.
  • Be sure to have figure and table numbers so your audience can follow you as you talk them through it.
  • Did you see “annotated” above?!
• Regarding text:
  • The bullet points serve three purposes:
    • guidance for your audience, leading them through the storyline and graphics both in the meeting and for quick pre-meeting preparation;
    • cues for you during the meeting, reminding you not what specifically to say (use your spoken words for that), but what generally to talk about; and
    • refreshers for your audience, reminding them afterwards what you talked about and jogging their memory about some of the details of what they heard you say (your spoken words).
  • These bullet points are short, to-the-point, not copied from your TAD since they are to be so limited and short compared to your more extensive bullet points in the TAD. Each should be no more than a single short sentence or phrase.
• Again… more graphics, less text!

2     Content Presentation

• Leading into each bullet-point list should be one short, complete sentence providing context for the list/section.
• There are four areas you are covering (in this order):
  1. Problem understanding (and definition in engineering terms; i.e., engineering requirements)
  2. Function-level design
  3. System-level design
  4. Next steps (your plans toward successfully addressing the PCR metrics)
• The three green-text areas are the focus for the content on this sheet, as indicated by the headings on the larger regions on the template. Some additional guidance follows:
  • The top-left is a few key bullet points on what your project is, and perhaps what it isn’t, then defined in engineering terms (your engineering requirements tables).
  • The bottom-left is not your function-structure diagram; it is too much detail to be shown here at a readable size. Full morph charts are typically too big to be shown here at a readable size.  It could include any or all of the following:
    • your main system function table and a few bullet points;
    • graphics highlighting some of the function-level concepts/ideas that are most exciting/intriguing/interesting; and/or
    • graphics highlighting some of the function-level concepts/ideas that are uncertain at this point as to their ability to truly meet the respective functional need; to create space for this you may need to omit the main system function table in which case you could convey main system functions in a more spatially efficient way.
  • The top-right is your DP Manager round-1 Pugh chart and the DP Manager data sheet for you round-1 winner.
  • The bottom-right “Next Steps” region should be framed in regard to what you will be doing toward successfully meeting the four PCR metrics:
    1. The chosen system-level concept has a good likelihood of meeting the engineering requirements as substantiated by preliminary/feasibility engineering; i.e., the requirements could be met by your concept.
    2. A technically sound plan is in place, on a requirement-by-requirement basis, describing methods for detail-design engineering (so that your engineering requirements should be met by your design) and for prototype verification (showing that your engineering requirements are ultimately met by your physically realized solution).
    3. A detailed and realistic work-plan is in place for completing the detail-design work, procuring materials and components, fabricating the prototype, and testing/refining the prototype.
    4. A financial plan is in place to complete the project within the allocated/secured budget.
• This is not “new documentation,” it is just a quick compilation of highlights pulled from other places in your documentation to prep others for the meeting and, furthermore, assist you in leading the meeting before getting into the details of discussion.

3     Examples of Great Work

Example 1

Example 2