12.07.2015 Views

Manufacturing Readiness Level (MRL) Deskbook

Manufacturing Readiness Level (MRL) Deskbook

Manufacturing Readiness Level (MRL) Deskbook

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

It is also important for the program/project office to set expectations for teammembers early in the process. The following are some of the key areas to be covered:• Initial schedule• Format and timing of reporting their results to the team• Standards of behavior at the contractor’s facility• Security clearances or nondisclosure agreements• Personal preparation• The need for a detailed understanding of their assigned area and the role ofshop floor observations and off-line discussions with contractor personnel• Responsibilities after the on-site review4.5 ORIENT CONTRACTORS BEING ASSESSEDThe leader of the assessment (either the government program/project office orthe prime contractor) should orient the contractor(s) to be assessed before theassessment occurs. This orientation may involve including contractor personnel inplanning meetings as well as providing the contractor with an orientation package thatincludes:• The <strong>MRL</strong> definitions and threads• Directions to additional materials on http://www.dodmrl.com/• Self-assessment questions• An indication of technologies or processes of special interest that should beincluded in the self assessmentFor on-site assessments, the orientation package should also include:• The questions the assessment team will use• A strawman agenda for the assessment visit• Evidence to be provided at the onsite visit (e.g., process maps, proposedmanufacturing plan, process capability data, yield data, technologydevelopment plans, risk reduction plans, value stream analysis, etc.)• High-interest areas where shop floor visits and/or discussions with contractorexperts will be desired4-7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!