DJD (Development in Progress...)

Presentation

Mainly used for aircraft & military equipment the DJD is the document used to give an up to date justification of the specification given for the managed product. For example, if a device is said to be compliant to a standard, it has to be proven through a series of test. For each test, all the data are required (test methods, test description, test results, test report…). These information are originally managed in an Excel Sheet but two reason gives a good reason to include in a PLM system.
  • Change: on every validated change on the product the DJD has to be reviewed and updated. Each line has to be uptaded to either justify that the new version doesn’t affect the change results or a new test has to be launched. The PLM systems, with all its versioning mechanism make it easier to manage.
  • Information Reuse: many DJD can be done in the same company. It could be on very different systems but very often to make the same test using the same test methods. So it would help a lot to centralize these information.

Design

Grid

The main aim is to maintain a grid where all the requirements are validated by either test or justification. This grid should look like the following:
DJD Grid

DJD and test campaign data management

DJD Process

Data-Model

The Data Model to implement should be the following:

Data Model DJD

The DJD created is linked to a part (could be an assembly or even a product). Inside this DJD we have different lines each lines is detailing the analysis of a combination between a criteria or specification to test and the test type. In this line we need to be able to call the input documents (test methods generic/specific, spec detail, etc), and the outputs (test results, test reports,etc). The line can be linked to another part, when for example, after the creation of a new version, if we don't have to re-run a test, we will need to justify why but we will keep the test results and show that these test results and reports are related to a previous version. (In a STEP data-model, we would link it to the object Version).

Grid Behavior

How the grid should behave:
  1. Filling the grid
    1. In order to start filling the grid the part should be in a state where no change could be done. So where are sure to understand on which configuration we are doing the qualification
  2. Part new version
    1. The consequence of a new version for a part is that a new DJD should be created as a clone of the previous one but without the Test. For each item we need to tell if it requires a new test or a justification that the change in the part did not affect the last test. For a justification the last test item should be attached.

Grid Columns

Columns detail:
  1. Spec/Req: Name or Code identifying the Specification, standard or even a requirement for which we need to prove the compliancy of the product (Ex: Moisture)
  2. Spec/Req Doc: document or list of documents defining the previous Specification (ex: Spec_Product.pdf)
  3. Generic Test: Name of the test to proceed to prove compliancy (Ex: Moisture Test - MIL-STD-883G- 1004.7)
  4. Generic Test Doc: Document defining the test to execute to prove compliancy (Ex: MIL-STD-883G.pdf)
  5. Specific Test: name of the internal specifi test realized for the product to certify
  6. Justification Method: Test or Justify, explain for the concerned version of the product if a test as to be run or if the occured change doesn't need it.
  7. Test Setup: Document explaining the setup ofthe test
  8. Comments: comments for the test
  9. Justification: Justification explaining if a test doesn't have to be run again after a new version of the product
  10. Test Results: Document of the results of the test
  11. Test Report: Document reporting the conclusion of the test
  12. Result: Indicator giving a clear status on the test line. Should be reflected with color in the grid and in reports.

Technical Documentation

Implementation

ItemTypes

Grid

This is the Query for the DJD grid
<Item type="DJD_DJD_Item"  action="QP_PPGridsQuery"  initial_action="GetItemConfig"  select="related_id,sort_order">
    <source_id>{id}</source_id>
    <related_id>
     <Item type="DJD_Item"  select="id, name">
       <Relationships>
         <Item type="DJD_TestSpecRef" select="related_id,sort_order">
           <related_id>
             <Item type="Document" select="id, name" />         
           </related_id>
         </Item>
         <Item type="DJD_Ligne" select="related_id,sort_order">
           <related_id>
             <Item type="DJD_Essai" select="id, name" >
                  <Relationships>
                     <Item type="DJD_TestMethod" select="related_id,sort_order">
                       <related_id>
                          <Item type="Document" select="id, name" />
                       </related_id>
                    </Item>
                  </Relationships>
             </Item>         
           </related_id>     
           <Relationships>
             <Item type="DJD_Connect_Item_Study" select="related_id,sort_order">
               <related_id>
                 <Item type="DJD_Item_Study" select="id, name">
                   <Relationships>
                     <Item type="DJD_TestReport" select="related_id,sort_order">
                       <related_id>
                          <Item type="Document" select="id, name" />
                       </related_id>
                     </Item>
                     <Item type="DJD_TestResults" select="related_id,sort_order">
                       <related_id>
                          <Item type="Document" select="id, name" />
                       </related_id>
                     </Item>
                     <Item type="DJD_TestSetup" select="related_id,sort_order">
                       <related_id>
                          <Item type="Document" select="id, name" />
                       </related_id>
                     </Item>
                   </Relationships>
                 </Item>         
               </related_id>     
             </Item>
           </Relationships>    
         </Item>
       </Relationships>
     </Item>
   </related_id>
</Item>

Methods

Last edited Apr 28, 2010 at 9:39 AM by yoannmaingon, version 28

Comments

No comments yet.