{"id":2041,"date":"2017-01-12T05:04:41","date_gmt":"2017-01-12T10:04:41","guid":{"rendered":"http:\/\/me.sites.mtu.edu\/meemscd\/?p=2041"},"modified":"2023-02-28T13:47:41","modified_gmt":"2023-02-28T18:47:41","slug":"dg-csr-pre-meeting-briefing-fr","status":"publish","type":"post","link":"https:\/\/me.sites.mtu.edu\/meemscd\/dg-csr-pre-meeting-briefing-fr\/","title":{"rendered":"Concept Selection Review (CSR) \u2014 Pre-meeting Briefing*"},"content":{"rendered":"<p style=\"text-align: center\"><span style=\"color: #ff0000\"><strong>* This is <em>ONLY<\/em> for \u201cFailure Resolution\u201d Projects. | For Standard Projects go <a href=\"http:\/\/me.sites.mtu.edu\/meemscd\/dg-csr-pre-meeting-briefing\/\">here<\/a>.<\/strong><\/span><\/p>\n<p>This one sheet serves three purposes:<\/p>\n<ul>\n<li>brief\/quick preparation for your audience prior to the meeting (\u201cpre-meeting briefing\u201d);<\/li>\n<li>a guide for the CSR meeting, for you and your audience members; and<\/li>\n<li>a take-away for your audience.<\/li>\n<\/ul>\n<h2>1\u00a0\u00a0\u00a0\u00a0 Organization and Formatting<\/h2>\n<ul>\n<li>There are four (4) sections that progress according to the numbers in their respective headings.<\/li>\n<li>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:\n<ol>\n<li>The first goes from top-left <strong>down<\/strong> to bottom-left then <strong>over and up<\/strong> to top-right and <strong>down<\/strong> to bottom-right (top-to-bottom then left-to-right, or \u201cTBLR\u201d).<\/li>\n<li>The second goes from top-left <strong>over<\/strong> to top-right then <strong>back over and down<\/strong> to bottom-left and <strong>over<\/strong> to bottom-right (left-to-right then top-to-bottom, or \u201cLRTB\u201d).<\/li>\n<\/ol>\n<\/li>\n<li>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 \u201cXxxxx\u201d.<\/li>\n<li>The top headings (left- and right-columns) are on the respective master layout (named \u201cPMB-TBLR\u201d or \u201cPMB-LRTB\u201d) 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. \u00a0<strong>Do <em>NOT<\/em> change the wording of any of the headings.<\/strong><\/li>\n<li>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.\n<ul>\n<li>It need not be jam packed; you are allowed\/encouraged to have your IRD content pages at hand to reference for details as needed.<\/li>\n<li>The content should be <strong>graphics-rich with minimal text<\/strong>. Aim for (<strong><em>minimum<\/em><\/strong>) 75% of the space consumed by graphics (with the exception of sections 3 and 4 which will likely, though not necessarily, be mainly text).<\/li>\n<li>But do not try to include all of your graphics relevant to the respective section. Be <strong><em>thoughtfully<\/em><\/strong> 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.<\/li>\n<li>Think of each of the four sections as a \u201cslide\u201d dominated by graphics with some bullet points to complement the graphics.<\/li>\n<\/ul>\n<\/li>\n<li>Regarding graphics:\n<ul>\n<li>Graphics include <strong><em>annotated<\/em><\/strong> 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.<\/li>\n<li>Graphics used here are copied and pasted from your other docs.<\/li>\n<li>Choose graphical elements of substance, not just to be present as a token non-textual element that is otherwise useless.<\/li>\n<li>Be sure to have figure and table numbers so your audience can follow you as you talk them through it.<\/li>\n<li><strong>Did you see \u201c<em>annotated<\/em>\u201d above?!<\/strong><\/li>\n<\/ul>\n<\/li>\n<li>Regarding text:\n<ul>\n<li>The bullet points serve three purposes:\n<ul>\n<li>guidance for your audience, leading them through the storyline and graphics both in the meeting and for <strong><em>quick<\/em><\/strong> pre-meeting preparation;<\/li>\n<li>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<\/li>\n<li>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).<\/li>\n<\/ul>\n<\/li>\n<li>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 <strong><em>single short<\/em><\/strong> sentence or phrase.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Again\u2026 more graphics, less text!<\/strong><\/li>\n<\/ul>\n<h2>2\u00a0\u00a0\u00a0\u00a0 Content Presentation<\/h2>\n<ul style=\"list-style-type: disc\">\n<li>Leading into each bullet-point list should be one short, complete sentence providing context for the list\/section.<\/li>\n<li>This one sheet serves three purposes:\n<ul style=\"list-style-type: circle\">\n<li>brief\/quick preparation for your audience prior to the meeting (\u201cpre-meeting briefing\u201d),<\/li>\n<li>a guide for the CSR meeting, for you and your audience members, and<\/li>\n<li>a hard-copy take-away for your audience.<\/li>\n<\/ul>\n<\/li>\n<li><span style=\"font-size: 1rem\">There are four areas you are covering <strong>(in this order)<\/strong>:<\/span>\n<ol>\n<li><span style=\"color: #339966\">Problem understanding (and definition in engineering terms; i.e., engineering requirements)<\/span><\/li>\n<li><span style=\"color: #339966\">Function-level design (specifically functional decomposition and any initial solution ideas)<\/span><\/li>\n<li><span style=\"color: #339966\">Root-cause failure analysis<\/span><\/li>\n<li>Next steps\u00a0(your plans toward successfully addressing the PCR metrics)<\/li>\n<\/ol>\n<\/li>\n<li>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:\n<ul style=\"list-style-type: circle\">\n<li>The top-left is a few key bullet points on what your project is, and perhaps what it isn\u2019t, then defined in engineering terms (your engineering requirements tables).<\/li>\n<li>The bottom-left is <strong><em>not<\/em><\/strong> your function-structure diagram; it is too much detail to be shown her at a readable size. It could be your main system function table and a few bullet points and\/or graphics highlighting some of your initial solution concepts\/ideas.<\/li>\n<li><span style=\"font-size: 1rem\">The top-right is for your plans, and more so details of any results (as graphical as possible) thus far in identifying the root cause of the failure and where those findings are taking you next.<\/span><\/li>\n<li>The bottom-right \u201cNext Steps\u201d region should be framed in regard to what you will be doing toward successfully meeting the four PCR metrics:\n<ol>\n<li>The chosen system-level concept has a good likelihood of meeting the engineering requirements as substantiated by preliminary\/feasibility engineering; i.e., the requirements <strong>could<\/strong> be met by your concept.<\/li>\n<li>A technically sound plan is in place, on a requirement-by-requirement basis, describing methods for detail-design engineering (so that your engineering requirements <strong>should<\/strong> be met by your design) and for prototype verification (showing that your engineering requirements <strong>are<\/strong> ultimately met by your physically realized solution).<\/li>\n<li>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.<\/li>\n<li>A financial plan is in place to complete the project within the allocated\/secured budget.<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<\/li>\n<li>This is not \u201cnew documentation,\u201d it is just a quick compilation of highlights pulled from other places in your documentation <strong>to prep others<\/strong>\u00a0for the meeting and, furthermore, assist you in leading the meeting before getting into the details of discussion.<\/li>\n<\/ul>\n<h2>3\u00a0\u00a0\u00a0\u00a0 Examples of Great Work<\/h2>\n<p>Failure resolution specific examples not yet available, but standard project examples are.<\/p>\n<h3><a href=\"https:\/\/drive.google.com\/file\/d\/1fGwXL1AtVjRPmCebWXUIP0jenmJF9DCf\/view?usp=sharing\">Example 1<\/a><\/h3>\n<h3><a href=\"https:\/\/drive.google.com\/file\/d\/1suz0uoyWksn3YxToAT-Ip1VuFlScVUmy\/view?usp=sharing\">Example 2<\/a><\/h3>\n<table>\n<tbody>\n<tr>\n<td>\u00a9 2017, William J. Endres<\/td>\n<td style=\"text-align: right\">Updated February 28, 2023<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p>* This is ONLY for \u201cFailure Resolution\u201d Projects. | For Standard Projects go here. This one sheet serves three purposes: brief\/quick preparation for your audience prior to the meeting (\u201cpre-meeting briefing\u201d); a guide for the CSR meeting, for you and your audience members; and a take-away for your audience. 1\u00a0\u00a0\u00a0\u00a0 Organization and Formatting There are [&hellip;]<\/p>\n","protected":false},"author":35,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,4],"tags":[],"_links":{"self":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/2041"}],"collection":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/users\/35"}],"replies":[{"embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/comments?post=2041"}],"version-history":[{"count":22,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/2041\/revisions"}],"predecessor-version":[{"id":2812,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/2041\/revisions\/2812"}],"wp:attachment":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/media?parent=2041"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/categories?post=2041"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/tags?post=2041"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}