Abstract:
A computer-aided method for managing a part shipping apparatus development project including a plurality of predetermined processes or procedures is provided. The method includes receiving information about the part and storing a first set of data which identifies the part in at least one database. The method further includes filling out a first electronic work initiation request form including a plurality of fields and stored in the at least one database wherein one of the fields specifies work to be performed with respect to apparatus for shipping the part. A second set of data is stored which identifies the apparatus in the at least one database. Production materials are created which allow the building of production apparatus for shipping the part based on the second set of data.

Description:
BACKGROUND OF THE INVENTION  
       [0001]     1. Field of the Invention  
         [0002]     The present invention relates to computer-aided methods of managing development projects and, in particular, to computer-aided methods for managing a part shipping apparatus development project.  
         [0003]     2. Background Art  
         [0004]     The shipping and assembly of a multi-component product, such as an automobile, typically involves the simultaneous activities of many business groups. For example, one group may be responsible for the powertrain components of a vehicle, another group for the electrical system, another group for the body structure, another for the interior, another for the exterior, another group for the chassis, etc.  
         [0005]     Apparatus for shipping such components or parts to one or more locations for assembly may include dunnage as well as containers such as racks.  
         [0006]     The design and engineering of such apparatus can often be as complex as the components or parts which are containerized by the containers. The ability to timely communicate among the designers and engineers of the containers, the suppliers of the parts, any pre-production container builders and the assembler is very important, especially when changes are made to the parts or containers during the container development project.  
         [0007]     U.S. Pat. No. 5,761,063 discloses a design and engineering project management system comprising a computer including a microprocessor, program memory, data storage memory, one or more displays, logic for identifying overall product objectives and group objectives relating to each of one or more subsystems or components of the overall product and displaying the overall objective and group objectives in a plurality of graphic windows which are quickly retrieved by the system operator, thereby integrating the diverse interests and activities of the groups into a comprehensive system design and implementation program. The system also preferably includes logic for identifying one or more strategies for achieving group objectives and presenting the strategies in a graphic form which allows for quick comparison of competing strategies. The system also preferably includes logic for quantitatively measuring progress toward each group&#39;s stated objectives and providing a plurality of graphic displays indicating each group&#39;s, and the entire project&#39;s toward its objectives.  
         [0008]     U.S. Pat. No. 4,875,162 to Ferriter et al. discloses a method for interfacing a project management tool with a conceptual design tool used for building and modifying the structure of a product such as a lawnmower. In operation, the project management tool interface prompts a user to define various items concerning the product structure. This design data is put into a database and, a hierarchical tree of the structure is generated on a computer screen. The user may then access this information from manufacturing data gathered by the conceptual design tool. The data accessed is formatted in a file of the project management tool and then imported into the project management tool. This data can then be modified by the project management tool and can be reformatted for export to the conceptual design tool so as to allow the design process to continue with updated project data.  
       SUMMARY OF THE INVENTION  
       [0009]     An object of the present invention is to provide an improved computer-aided method of managing development projects and, in particular, to computer-aided methods for managing a part shipping apparatus development project.  
         [0010]     In carrying out the above object and other objects of the present invention, a computer-aided method for managing a part shipping apparatus development project including a plurality of predetermined processes or procedures is provided. The method includes receiving information about the part and storing a first set of data which identifies the part in at least one database. The method further includes filling out a first electronic work initiation request form including a plurality of fields and stored in the at least one database wherein one of the fields specifies work to be performed with respect to apparatus for shipping the part. A second set of data is stored which identifies the apparatus in the at least one database. Production materials are created which allow the building of production apparatus for shipping the part based on the second set of data.  
         [0011]     The project may include a build process or procedure, and the method may further include filling out an electronic release form stored in the at least one database to release a builder to perform at least one build function during the build process or procedure.  
         [0012]     A first article container may be built during the build process or procedure, and the method may further include inspecting the first article container and recording results of the inspection.  
         [0013]     The method may further include filling out a field order change form stored in the at least one database to identify, approve and implement a field order change to the apparatus.  
         [0014]     The method may further include filling out a second electronic work initiation request form including a plurality of fields and stored in the at least one database wherein one of the fields specifies the field order change.  
         [0015]     The work to be performed may be apparatus design work and the form may be a design form for requesting work to design the apparatus.  
         [0016]     The work to be performed may be apparatus build work and the form may be a build form for requesting work to build the apparatus.  
         [0017]     One of the fields of the form may specify a deviation from one of the predetermined processes or procedures.  
         [0018]     One of the fields of the form may specify status of the form.  
         [0019]     The at least one build function may include building a prototype of the apparatus and the method may further include reviewing the prototype and recording results of the review in the at least one database.  
         [0020]     The step of receiving may include the step of receiving math data which represents the part.  
         [0021]     The apparatus may include a rack.  
         [0022]     A plurality of parts may be shipped and the second set of data may identify orientation of the parts in the rack.  
         [0023]     The apparatus may include dunnage, a standard container, or an expendable container.  
         [0024]     The method may further include modifying the second set of data to obtain a revised second set of data which identifies the apparatus, and the step of creating production materials may be based on the revised second set of data.  
         [0025]     A plurality of parts may be shipped and the second set of data may identify density of the parts to be shipped with the apparatus.  
         [0026]     The second set of data may identify a supplier to supply the apparatus.  
         [0027]     The part may be a vehicle part.  
         [0028]     The at least one data base may include a relational database.  
         [0029]     The second set of data may also identify a transportation mode for the container and may identify part load and unload information with respect to the apparatus.  
         [0030]     The project may include a container development process or procedure and the method may further include conducting at least one pre-concept phase activity and recording the results of the at least one pre-concept phase activity in the at least one database.  
         [0031]     The project may include a rack development process or procedure and the method may further include conducting at least one concept phase activity and recording the results of the at least one concept phase activity in the at least one database.  
         [0032]     The method may further include conducting at least one design for manufacture activity and recording the results of the at least one design for manufacture activity in the at least one database The method may further include conducting at least one prototype draw activity and recording the results of the at least one prototype draw activity in the at least one database.  
         [0033]     The method may include monitoring the build process or procedure and collecting and recording information on any changes to be made to the apparatus during the build process or procedure in the at least one database.  
         [0034]     The method may include filling out an electronic requisition form including a plurality of fields and stored in the at least one database to conduct purchasing activities.  
         [0035]     The method may further include filling out an electronic shipping request form including a plurality of fields and stored in the at least one database to ship product or materials.  
         [0036]     The project may include a rack development process or procedure and the method may further include conducting at least one density study activity and recording the results of the at least one density study activity in the at least one database.  
         [0037]     The above object and other objects, features, and advantages of the present invention are readily apparent from the following detailed description of the best mode for carrying out the invention when taken in connection with the accompanying drawings. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0038]      FIG. 1  is a block diagram of a computer network-implemented system for carrying out many of the method steps of the present invention;  
         [0039]      FIG. 2  is a block diagram flow chart of one embodiment of a project control process or method of the present invention;  
         [0040]      FIG. 3  is a block diagram flow chart of a container/dunnage development process of the project control process;  
         [0041]      FIG. 4  is a block diagram flow chart of a prototype build process of the project control process;  
         [0042]      FIGS. 5   a  and  5   b  are block diagram flow charts of a procedure for testing packaging of the project control process;  
         [0043]      FIGS. 6   a  and  6   b  are block diagram flow charts of a process to conduct initiate/manage build phase activities of the project control process;  
         [0044]      FIG. 7  is a block diagram flow chart of a process to conduct final build print phase activities of the project control process;  
         [0045]      FIG. 8  is a block diagram flow chart of a process for containerizing C/E/F items of the container development process;  
         [0046]      FIG. 9  is a block diagram flow chart of a process to conduct pre-concept phase activities of the container development process;  
         [0047]      FIG. 10  is a block diagram flow chart of a process for containerizing B-items of the container development process;  
         [0048]      FIG. 11  is a block diagram flow chart of a process to conduct density study activities of the container development process;  
         [0049]      FIG. 12  is a block diagram flow chart of a process to conduct concept phase activities of the container development process;  
         [0050]      FIG. 13  is a checklist used at a meeting to obtain information about parts, containers, suppliers, transportation mode, load/unload instructions, etc. which information is used to populate at least one database of the present invention;  
         [0051]      FIG. 14  is a block diagram flow chart of a process to conduct design-for-manufacturing (DFM) phase activities of the container development process;  
         [0052]      FIG. 15  is a block diagram flow chart of a process to conduct prototype draw phase activities of the container development process;  
         [0053]      FIGS. 16   a,    16   b  and  16   c  are block diagram flow charts of a process for requesting/scheduling/tracking work initiation from a container design group and/or a container prototype source;  
         [0054]      FIG. 17  is a block diagram flow chart of a process for acquiring math data which represents a part to be containerized;  
         [0055]      FIGS. 18   a  and  18   b  are block diagram flow charts of a process for verifying the math data;  
         [0056]      FIG. 19  is a block diagram flow chart of a process for design/in-house prototype build line-up;  
         [0057]      FIGS. 20   a  and  20   b  are block diagram flow charts of a process for in-process inspection of designs;  
         [0058]      FIG. 21  is a block diagram flow chart of a process to select and evaluate suppliers;  
         [0059]      FIGS. 22   a  and  22   b  are block diagram flow charts of a process to conduct purchasing activities;  
         [0060]      FIG. 23  is a block diagram flow chart of a process for releasing suppliers to perform build functions;  
         [0061]      FIGS. 24   a  and  24   b  are block diagram flow charts of a process to package, load and ship product or materials via a commercial carrier;  
         [0062]      FIG. 25  is a block diagram flow chart of a process to organize, store and protect product from the receiving process and to release and ship product;  
         [0063]      FIGS. 26   a  and  26   b  are block diagram flow charts of a process to receive, inspect, identify and control product and material prior to transferring to the warehouse process of  FIG. 25  or engineering;  
         [0064]      FIG. 27  is a block diagram flow chart of a process to segregate, contain and control product and material found to be damaged/non-conforming;  
         [0065]      FIG. 28  is a block diagram flow chart of a process to conduct 1 st  article activities;  
         [0066]      FIG. 29  is a block diagram flow chart of a process for preparing to perform a 1 st  article inspection;  
         [0067]      FIGS. 30   a ,  30   b  and  30   c  are block diagram flow charts of a process to conduct 1 st  article inspection;  
         [0068]      FIG. 31  is a block diagram flow chart of a process for reviewing a prototype container/dunnage;  
         [0069]      FIG. 32  is a block diagram flow chart of a process to conduct release-for-production-design phase activities;  
         [0070]      FIGS. 33   a  and  33   b  are block diagram flow charts of a process for identifying, approving and implementing field order changes (FOC);  
         [0071]      FIG. 34  is a screen shot of a containers window which contains container information and an image of the container; standard instructions for loading and unloading the container are also provided;  
         [0072]      FIG. 35  is a screen shot of a WIRFs window and a particular, overlapping, WIRF window which depicts a work initiation request form (WIRF);  
         [0073]      FIG. 36  is a screen shot of an MRFs window and a particular, overlapping, MRF (i.e., Management Release Form) depicting a MRF form;  
         [0074]      FIG. 37  is a screen shot of an FOCs window and a particular, overlapping, field order change (i.e., FOC) window depicting a FOC form;  
         [0075]      FIG. 38  is a screen shot of a meeting minutes window and a particular, overlapping, job-related meeting minutes window depicting a meeting minutes form;  
         [0076]      FIG. 39  is a screen shot of an in-house requisitions window and a particular, overlapping, in-house purchase requisition window depicting an in-house requisition form; and  
         [0077]      FIG. 40  is a screen shot of a customer purchase requisitions window and a particular, overlapping, customer purchase requisitions window depicting a customer requisition form. 
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0078]     Referring now to the drawing figures, there is shown in  FIG. 1 , in block diagram form, a computer network-implemented system for carrying out the computer-aided method of the present invention. A computer network, generally indicated at  10 , includes a server computer  12  having one or more databases, such as relational databases. The network  10  also includes a number of client computers  13   a  through  13   n . Typically, the computers  12  and  13   a - 13   n  are located at the user premises  11 .  
         [0079]     A customer  14  of containers/dunnage is typically in communication with the user premises  11  which is also typically in communication with a builder  15  of material handling equipment such as the container and/or dunnage.  
         [0080]      FIG. 2  generally illustrates a project control process of one embodiment of the present invention. Typically, engineers and managers are responsible for the process of  FIG. 2 .  
         [0081]     At block  20 , initially a contract review is held. At block  21 , a kick-off meeting is held. At block  22 , a job in an operations database is created. At block  23 , a project engineer is assigned.  
         [0082]     At block  24   a , determine if container development required. If yes, at block  24   b,  implement a container development process of  FIG. 3 . If no, at block  25   a,  determine if a prototype build is required. If yes, at block  25   b,  implement a prototype build process of  FIG. 4 . If no, at block  26   a , determine if testing required. If yes, at block  26   b , implement a testing procedure of  FIGS. 5   a  and  5   b.  If no, at block  27   a,  determine if production management is required. If yes, at block  27   b,  implement a initiate/manage build procedure of  FIGS. 6   a  and  6   b . If no, at block  28   a , determine if final build prints are required. If yes, at block  28   b,  implement a final build prints procedure of  FIG. 7 . If no, at block  29 , the data/documents are delivered to the customer.  
         [0083]      FIG. 3  illustrates the container development process which is typically entered from the project control process of  FIG. 2 . At block  30   a , the container type is identified. If a standard or expendable container is identified, at block  30   b , implement a C/E/F item development process of  FIG. 8  and then return to project control of  FIG. 2 .  
         [0084]     If a rack or B-item is identified, at block  31   a , determine if a pre-concept process is required. If yes, at block  31   b , implement a pre-concept process of  FIG. 9 . If no, at block  32   a , determine if the container is a rack or B-item (i.e., dunnage). If a B-item, at block  32   b , implement a B-item development process of  FIG. 10 . Then, go back to the project control of  FIG. 2 .  
         [0085]     If a rack, at block  33   a , determine if a density study is required. If yes, at block  33   b,  implement a density study process of  FIG. 11 . If no, at block  34   a,  determine if a concept process is required. If yes, at block  34   b , implement a concept process of  FIG. 12 . If no, at block  35   a , determine if a design for manufacture (DFM) process is required. If yes, at block  35   b , implement a DFM process of  FIG. 14 . If no, at block  36   a , determine if a prototype draw process is required. If yes, at block  36   b , implement a prototype draw process of  FIG. 15 . If no, return to the project control of  FIG. 2 .  
         [0086]      FIG. 4  illustrates in detail the prototype build process noted in  FIG. 2 .  
         [0087]     At block  40   a , determine if the prototype is in-house or customer purchased. If customer purchased, at block  40   b , implement an appropriate customer pre-requisition process (i.e., see  FIG. 40 ). If in-house, at block  41 , implement a purchase requisition process of  FIGS. 22   a  and  22   b  (also  FIG. 39 ).  
         [0088]     At block  42 , implement an MRF process of  FIG. 23 .  
         [0089]     At block  43 , a project engineer sends a copy of prints to a fabricator.  
         [0090]     At block  44 , implement WIRF process, if required (in-house prototype) of  FIGS. 16   a  and  16   b.    
         [0091]     At block  45 , determine if it is a new prototype or a modification of an existing prototype. If it is a modification, at block  46 , implement a shipping process of  FIG. 24 . Then, or if the answer to block  45  is “new,” at block  47 , a fabricator builds the prototype.  
         [0092]     At block  48 , implement 1 st  article (i.e., pre-production) process of  FIG. 28 .  
         [0093]     At block  49 , implement a prototype review process of  FIG. 31 . Then go back to process control of  FIG. 2 .  
         [0094]      FIG. 5   a  illustrates the testing procedure of  FIG. 2 . At block  50 , a project engineer and a core team determine test criteria. At block  51 , determine if a purchase requisition required. If no, go immediately to block  54   a . If yes, at block  52   a , determine if it is an in-house or customer purchased item. If customer purchased, at block  52   b , implement an appropriate customer pre-requisition process (see  FIG. 40 ).  
         [0095]     If purchased in-house, at block  53 , implement the purchase requisition process of  FIGS. 22   a  and  22   b  (see also  FIG. 39 ).  
         [0096]     At block  54   a , determine if a container is available. If not, at block  54   b , a container is requested and then the process goes back to block  50 . If yes, at block  55   a , determine if current level parts are available. If not, at block  55   b , determine if a deviation to the process is approved. If not, at block  55   c , a request for parts is made and the process goes back to block  50 . If yes, at block  56 , a test is scheduled.  
         [0097]     At block  57 , a meeting notice is sent to the project engineer, the OEM representative, the customer representative, the assembly plant representative, and others, as required. Then, the testing procedure continues as indicated in  FIG. 5   b  which further illustrates the testing procedure.  
         [0098]     At block  58 , determine if the container/parts are to be shipped. If not, go directly to block  50   a ′. If yes, at block  59 , implement a shipping procedure of  FIG. 24 .  
         [0099]     At block  50   a ′, determine if part level matches the container design part level. If not, at block  50   b ′, determine if a deviation is approved. If not, at block  50   c ′, implement a request for parts and go back to block  50 . If yes, at block  51   a ′, determine if parts are in acceptable condition. If no, at block  51   b ′, determine if a deviation is approved. If not, at block  51   c ′, implement a request for parts and go back to block  50 . If yes, at block  52 ′, implement a run test.  
         [0100]     At block  53 ′, a review of parts and containers for damage is conducted.  
         [0101]     At block  54   a ′, determine if the test results are approved. If not, at block  54   b ′, document test results and distribute meeting minutes. Also, put meeting minutes in the database (see  FIG. 38 ). Then, at block  54   c ′, implement the container development procedure (i.e.,  FIG. 3 ).  
         [0102]     If the test results are approved, at block  55 ′, document the test results and distribute meeting minutes (also  FIG. 28 ). Then, go back to process control of  FIG. 2 .  
         [0103]      FIG. 6   a  illustrates the initiate/manage build process of  FIG. 2 . At block  60   a , determine if prints are updated to latest design/build level. If not, at block  60   b , determine if updates to the prints are required to initiate build. If yes, at block  60   c , implement a release for production process of  FIG. 32 .  
         [0104]     At block  61   a , determine if all FOCs (i.e., field order changes) are closed. If not, at block  61   b , determine if a FOC closure is required to initiate build. If yes, at block  61   c , implement the FOC process of  FIG. 33 . If no, at block  61   d , implement document deviation and approval.  
         [0105]     At block  62   a , determine if a purchase requisition is required. If yes, at block  62   b , implement the purchasing process of  FIGS. 22   a  and  22   b . If no, at block  63 , implement the MRF process of  FIG. 23 .  
         [0106]     At block  64   a , determine if 1 st  article (i.e., pre-production) container/dunnage is required. If no, go to block  65  of  FIG. 6   b . If yes, at block  64   b , the project engineer sends a copy of the prints to a fabricator. At block  64   c , the fabricator builds the 1 st  article container/dunnage. At block  64   d , implement the 1 st  article process of  FIG. 28 . Then, at block  64   e , implement the MRF process of  FIG. 23  and then go to block  65  of  FIG. 6   b  which further illustrates the initiate/manage build process.  
         [0107]     At block  65 , the project engineer tracks production and provides status reports, as required. At block  66   a , determine if a problem has occurred during production. If yes, at block  66   b , determine if containment is required. If not, at block  66   c , the customer is informed. At block  66   d , correction of manufacturing/production process and fleet, as required, is directed and at block  66   e,  implement a business system report process.  
         [0108]     If the answer to block  66   b  is yes, at block  66   f , production is stopped, at block  66   g,  the customer is informed and at block  66   h,  identify and quarantine all effected product at all locations.  
         [0109]     At block  66   i,  correction of manufacturing/production process and fleet as required, is directed using the appropriate MRF, FOC, and WIRF processes, as required. Then, at block  66   j,  implement a business system report process.  
         [0110]     At block  66   k,  determine if 1 st  article (i.e., pre-production) container/dunnage is required. If yes, at block  66   l , implement the 1 st  article process of  FIG. 28 . If no, at block  66   m,  determine if an MRF is required. If no, go directly to block  65 . If yes, at block  66   n,  implement the MRF process of  FIG. 23  then go to block  65 .  
         [0111]     At block  67 , the project engineer gathers information on any changes made during production, including marked-up prints, FOCs, and any other documentation. At block  68   a , determine if updates to prints required. If no, go back to the process control of  FIG. 2 . If yes, at block  68   b , implement the WIRF process of  FIGS. 16   a  and  16   b.    
         [0112]      FIG. 7  illustrates the final build prints process of  FIG. 2 . At block  70 , the project engineer obtains all changes from previous print level, supporting documents, open FOCs and any other information, as required. At block  71 , implement the WIRF process of  FIGS. 16   a  and  16   b . At block  72 , customer sign-off, if required, is obtained. Then, the process control of  FIG. 2  is returned to.  
         [0113]      FIG. 8  illustrates the C/E/F item development process of  FIG. 3 . At block  80 , contact the OEM to explain OEM &amp; in-house program requirements and responsibilities (per customer contract). At block  81   a , determine if the container is a carryover or new. If new, at block  81   b , obtain part information and discuss OEM&#39;s packaging design process. At block  81   c , develop preliminary package information (container and density) during pre-production reviews.  
         [0114]     If the answer to block  81   a  is “carry over,” at block  82 , obtain preliminary pack information (container and density). At block  83 , verify and document preliminary pack and supplier information. At block  84 , update all necessary databases with preliminary pack information. At block  85 , determine if the container is standard or an expendable package. If expendable, go directly to block  87 . If standard, at block  86   a , determine if OEM support pre-production with current container fleet. If no, at block  86   b , implement the initiate/manage build process of  FIGS. 6   a  and  6   b . If yes, at block  87 , conduct pre-production validations, as required. At block  88   a , determine if approved. If not, at block  88   b , determine if non-compliant. If non-compliant, at block  88   c , inform OEM of non-compliance and obtain written verification of future compliance. Then go back to block  87 . If the answer to block  88   b  is “no,” at block  88   d,  update databases per revised packaging proposal and go to block  81   c . If the answer to block  88   a  is “yes,” go to the process of  FIG. 3 .  
         [0115]      FIG. 9  illustrates the pre-concept phase of  FIG. 3 . At block  90 , the project engineer obtains process requirements from the core team. At block  91 , determine if a WIRF is required. If no, go directly to block  93 . If yes, at block  92 , implement the WIRF process of  FIGS. 16   a ,  16   b  and  16   c.    
         [0116]     At block  93 , determine if a meeting is required. If no, go directly to the process of  FIG. 3 . If yes, at block  94 , the project engineer holds a pre-concept meeting. At block  95 , obtain customer sign-off, if required. At block  96 , the project engineer records/distributes meeting minutes (see  FIG. 38 ).  
         [0117]      FIG. 10  illustrates the B-item development process of  FIG. 3 . At block  100 , contact the OEM to explain OEM and in-house program requirements and responsibilities (per customer contract). At block  101   a , determine if carryover or existing dunnage will accommodate the part. If no, at block  101   b , obtain part, part information, and OEM and plant requirements for package design. At block  101   c , develop a design per customer contract and go back to the process of  FIG. 3 .  
         [0118]     If the answer to block  101   a  is yes, at block  102 , document verification needed that dunnage will accommodate the part.  
         [0119]     At block  103 , update all necessary databases with pack information (see  FIG. 38 ). At block  104   a , determine if the OEM can support pre-production. If no, at block  104   b , implement the initiate/manage build process of  FIGS. 6   a  and  6   b . If yes, at block  105 , conduct pre-production buy-off, as required. At block  106   a , determine if approved. If yes, go back to the process of  FIG. 3 . If no, at block  106   b , determine if minor or major changes are required. If minor, at block  106   c , rework the container design and go back to block  105 . If major, go to block  101   c.    
         [0120]      FIG. 11  illustrates the density study process of  FIG. 3 .  
         [0121]     At block  110 , the project engineer obtains process requirements from the core team. At block  111 , determine if a WIRF is required. If no, go directly to block  113 . If yes, at block  112 , implement the WIRF process of  FIGS. 16   a  and  16   b.    
         [0122]     At block  113 , determine if a meeting is required. If no, go back to the process of  FIG. 3 . If yes, at block  114 , the project engineer holds a density study meeting. At block  115 , obtain customer sign-off, if required. At block  116 , the project engineer records/distributes meeting minutes (see  FIG. 38 ).  
         [0123]      FIG. 12  illustrates the concept phase process of  FIG. 3 . At block  120 , the project engineer obtains process requirements from the core team. At block  121 , determine if a WIRF is required. If no, go directly to block  123 . If yes, at block  122 , implement the WIRF process of  FIGS. 16   a  and  16   b.    
         [0124]     At block  123 , determine if a meeting is required. If no, go directly to block  127 . If yes, at block  124 , the project engineer holds a concept meeting to review the concept and other items on the meeting checklist of  FIG. 13 , which is completed. The information on the checklist is used to populate the database.  
         [0125]     At block  125 , obtain customer sign-off, if required. At block  126 , the project engineer completes/distributes meeting minutes (see  FIG. 38 ).  
         [0126]     At block  127 , the project engineer updates the operations database, as required. Then the process returns to the procedure of  FIG. 3 .  
         [0127]      FIG. 13  illustrates the previously mentioned concept meeting checklist.  
         [0128]      FIG. 14  illustrates the design for manufacturing (DFM) phase of  FIG. 3 . At block  140 , implement WIRF process of  FIGS. 16   a  and  16   b . At block  141 , a meeting is scheduled, as required, with the project engineer, the build advocate, the dunnage advocate, the customer representative or others, as required. At block  142 , the project engineer holds the DFM meeting. At block  143 , obtain customer sign-off, if required. At block  144 , the project engineer records/distributes meeting minutes (see  FIG. 38 ) and then returns to  FIG. 3 .  
         [0129]      FIG. 15  illustrates the prototype draw process of  FIG. 3 . At block  150 , the project engineer obtains design directives from core team and/or previous development stages. At block  151 , implement the WIRF process of  FIGS. 16   a  and  16   b . At block  152 , determine if a meeting is required. If no, go directly to block  156 . If yes, at block  153 , the project engineer holds a prototype draw meeting. At block  154 , obtain customer sign-off, if required. At block  155 , the project engineer completes/distributes meeting minutes (see  FIG. 38 ).  
         [0130]     At block  156 , the project engineer updates the operations database, as required ( FIG. 38 ). Then, return is made to the process of  FIG. 3 .  
         [0131]      FIGS. 16   a ,  16   b  and  16   c  illustrate the work initiation request form (WIRF) process. At block  160 , create a WIRF per on-line information. At block  161   a , determine if work is to be done in-house or elsewhere. If elsewhere, at block  161   b , specify external work source in the “other” field of the WIRF form ( FIG. 35 ).  
         [0132]     If in-house, at block  162   a , determine if a purchase order number is available. If not, at block  162   b , determine if a deviation is approved. If not, at block  162   c,  wait for purchase order from customer and return to block  160 .  
         [0133]     If yes, go to block  163 . If the purchase order number is available, at block  163 , input the purchase order number. At block  164 , assign the process. At block  165 , specify work to be done. At block  166 , WIRF status on its form (i.e.,  FIG. 35 ) is set to RFD.  
         [0134]      FIGS. 16   b  and  16   c  further illustrate the work initiation request form (WIRF) process. At block  167   a,  determine if the WIRF is a design WIRF. If no, go to block  168   a . If yes, at block  167   b,  determine if latest level math data required. If yes, at block  167   c , implement the math data acquisition process of  FIG. 17 . If no, at block  167   d,  determine if a deviation is approved.  
         [0135]     If yes, at block  167   e,  specify deviation on the WIRF (i.e.,  FIG. 35 ). If no, at block  167   f , wait for math data to become available. At block  167   g , implement the math data acquisition process of  FIG. 17 .  
         [0136]     At block  168   a , determine if part(s) are required. If no, go to block  169 . If yes, at block  168   b , determine if part(s) available. If yes, go to block  169 .  
         [0137]     If no, at block  168   c , determine if a deviation is approved. If yes, at block  168   d,  specify no part(s) on the WIRF (i.e.,  FIG. 35 ). If no, at block  168   e,  get part(s) and go back to block  168   a.    
         [0138]     At block  169 , implement the design prototype build line-up procedure of  FIG. 19 . At block  160 ′, work completed per WIRF (see  FIG. 35 ). At block  161   a ′, determine if design or in-house prototype build. If in-house prototype build, at block  161   b ′, implement the 1 st  article process of  FIG. 28 . If design, at block  161   c ′, implement an in-process inspection—design of  FIGS. 20   a  and  20   b.    
         [0139]     Then, at block  162   a ′, determine if the purchase order is authorized. If it is, go to block  163 ′. If no, at block  162   b ′, determine if a deviation is approved. If yes, go to block  163 ′. If no, at block  162   c ′, wait for a purchase order from the customer and then return to block  162   a′.    
         [0140]     At block  163 ′, complete transmittal form. At block  164   a ′, implement a ship prototype process of  FIG. 24  if a prototype is built in-house.  
         [0141]     At block  164   b ′, distribute prints if a design.  
         [0142]     At block  165 ′, invoice the customer for the work performed and return to the process of  FIG. 2 .  
         [0143]      FIG. 17  illustrates the math data acquisition process. At block  170 , ECA (i.e., engineering change analyst) pulls list of WIRFs with RFD status to start the acquisition of data. At block  171   a , determine if data acquisition complete. If not, at block  171   b , ECA sets to RFD 2  if first attempt fails. At block  171   c , re-attempt download. At block  171   d , determine if the data acquisition is complete. If complete, go back to block  171   a . If not, at block  171   e , the ECA sets to RFD 3  if the second attempt fails. At block  171   f , re-attempt download.  
         [0144]     At block  171   g,  determine if this is the third attempt and failure of acquisition. If no, go back to block  171   a . If yes, at block  171   h , the ECA places the WIRF on hold. At block  171   i,  the ECA notifies the project engineer. At block  171   j,  the engineer resolves the data availability issue.  
         [0145]     At block  171   k,  the engineer changes the WIRF status to RFD and return is made to block  170 .  
         [0146]     At block  172 , produce an output tree of data acquired and forward to the project engineer, including date acquired. At block  173 , the ECA places data in appropriate location for either in-house design or outside design transfer. At block  174 , the ECA changes the status of the WIRF to SW 2  alerting the designer and the engineer that data is available to begin work or transfer to outside design source.  
         [0147]     At block  175 , implement the math data validation process of  FIGS. 18   a  and  18   b . Then return to the WIRF process of  FIGS. 16   a  and  16   b.    
         [0148]      FIGS. 18   a  and  18   b  illustrate the math data validation process. At block  180   a , determine if an in-house or an outside design source is to be used. If outside, at block  180   b , prepare math data per instructions on the WIRF for transfer to an outside design source. At block  180   c , transfer the data. At block  180   d,  document all data sent and forward to project engineer, including date of transfer and list of items transferred.  
         [0149]     At block  181 , the project engineer forwards math data output tree to the design supervisor. At block  182 , the design source verifies receipt of all components to data output tree within two business days. At block  183   a , determine if all components are received. If no, at block  183   b , the design source notifies the design supervisor and the project engineer via e-mail. At block  183   c , the project engineer changes the WIRF status to RFD and return is made to the process of  FIG. 17 .  
         [0150]     If all components are received, at block  184 , the design source cleans and assembles math data and the process enters block  185  of  FIG. 18   b , which further illustrates the math data validation process.  
         [0151]     At block  185 , the design source creates a 3-D electronic image of the complete math data. At block  186 , the design source forwards the image to the project engineer for verification within three business days of verification of all components being received. At block  187 , the project engineer reviews the electronic image within two business days of receipt of image. At block  188 , project engineer confirms approval or rejection via e-mail to creator of the image and the design supervisor. At block  189   a , determine if the electronic image is approved. If yes, return to the process of  FIG. 17 . If no, at block  189   b , the project engineer places the WIRF on hold. At block  189   c , the project engineer resolves the data issue. At block  189   d , the project engineer changes the WIRF status to RFD and return is made to the process of  FIG. 17 .  
         [0152]      FIG. 19  illustrates design/prototype build line-up process from the process of  FIGS. 16   a  and  16   b.    
         [0153]     At block  190 , line-up preparation: project engineer gathers required information to support requested action on WIRF, referencing the line-up checklist. At block  191 , schedule a meeting. At block  192 , hold meeting: all pertinent information to be exchanged and reviewed. Use line-up checklist to confirm minimum requirements. At block  193   a , determine if the designer/fabricator have the information they need to proceed. If yes, return to the process of  FIGS. 16   a  and  16   b . If no, at block  193   b , the designer/fabricator and the project engineer determine missing information. At block  193   c , the project engineer acquires missing information and block  190  is re-entered.  
         [0154]      FIG. 20   a  illustrates the in process inspection—design process entered from the WIRF process of  FIGS. 16   a  and  16   b . At block  200 , determine what phase of design. If pre-concept/density study/overlay, at block  201   a , the design supervisor checks the work. If concept/DFM/proto draw/build prints/revisions, at block  201   b , the checker checks the work, referencing design checklist, if required. From block  201   a , at block  202   a , determine if there are any errors.  
         [0155]     From block  201   b , at block  202   b , determine if there are any errors.  
         [0156]     From block  202   a , if there are no errors, at block  203   a , the design supervisor signs and dates drawings with red pen and forwards a copy to the project engineer.  
         [0157]     From either block  202   a  or block  202   b , if there are errors, at block  203   b , errors are marked up with red pen, correct items are highlighted with yellow.  
         [0158]     From block  202   b , if there are no errors, at block  203   c , the prints are signed and dated with red pen and given to the release manager. At block  203   d , the release manager reviews the prints. At block  203   e , determine if there are any errors. If there are errors, at block  203   f , the release manager documents the errors. At block  203   g , the release manager reviews the errors with the design supervisor. At block  203   h,  the design supervisor returns the prints to the designer for correction. At block  203   i,  the designer corrects the errors and highlights the corrections with a green pen.  
         [0159]     If there are no errors as determined at block  203   e , at block  203   j , determine if approved. If no, return to the process of  FIG. 3 . If yes, at block  203   k,  the release manager signs and dates the drawings with a red pen and gives to the project engineer and the process continues to block  206   a  of  FIG. 20   b.    
         [0160]     At block  204   a , the design supervisor files the drawing package in a design job folder and the process continues to block  206   a.    
         [0161]     At block  204   b , the designer corrects the errors and highlights corrections with a green pen. At block  205 , determine what phase the design is in. If in the pre-concept/density study/overlay phase, go to block  201   a . If in the concept/DFM/proto draw/build prints/revisions phase, go to block  201   b.    
         [0162]      FIG. 20   b  further illustrates the in process inspection—design process. At block  206   a , determine if project engineer approved. If not, at block  206   b , the project engineer reviews with the design supervisor. At block  206   c , determine if changes are required. If yes, design responsible at block  206   d , the designer corrects the errors and highlights corrections with a green pen. At block  206   e,  determine what phase the design is in. If pre-concept/density study/overlay, go to block  201   a . If concept/DFM/proto draw/build prints/revisions, go to block  201   b . If yes, project engineer responsible at block  206   c , go to WIRF process of  FIGS. 16   a - 16   c.    
         [0163]     Coming from block  206   a , if yes, concept/DFM/proto draw/build prints/revisions at block  207 , the project engineer signs the drawings with a red pen. At block  208   a , obtain customer sign-off, if required. At block  208   b , the project engineer returns the drawings to the design supervisor. Coming from block  206   a , if yes and the phase is pre-concept/density study/overlay phase, at block  209 , the design supervisor files the drawing package in a design job folder and return is made to the WIRF process of  FIGS. 16   a  and  16   b.    
         [0164]      FIG. 21  illustrates a supplier selection and evaluation process. At block  210 , establish supplier selection criteria, including items such as: quality performance status, pricing competitiveness, minority status, invoicing criteria, and QMS registration status. At block  211 , determine the type of services that need to be purchased. At block  212 , develop a list of approved suppliers. At block  213   a , determine if the supplier is used directly for our customers. If no, at block  213   b , non-customer suppliers are flagged in the database as non-quality trackable. At block  213   c , use ad hoc price/delivery performance.  
         [0165]     If yes, at block  214   a , determine if there are any issues. If no, at block  214   b , review supplier annually. At block  214   c , send out supplier self assessment survey annually in July if they have not attained a quality certificate such as ISO9000 or QS9000 or if their quality certificate expires in the past year. At block  214   d,  data generated by survey responses are accumulated and analyzed at the end of September. At block  214   e,  update list as required and return to block  214   a.    
         [0166]     If there are issues, coming from block  214   a , at block  215   a , determine whether to put supplier on probation. If no, at block  215   b , remove supplier from list. If yes, at block  216 , flag in operations. At block  217 , go to a business system report process. Then go back to block  214   a.    
         [0167]      FIG. 22   a  illustrates the purchasing process after a need to purchase has been identified.  
         [0168]     At block  220 , the requisitioner receives quote(s), or gathers blanket order information. At block  221 , the requisitioner fills out on-line requisition form in operations database (i.e.,  FIGS. 39 and 40 ).  
         [0169]     At block  222 , submit requisition and quote/blanket order information to analyst for approval. At block  223 , analyst reviews, prepares, and approves, referencing checklist. This is documented with a signature on the purchase requisition form. At block  224   a , determine if requisition is approved. If no, at block  224   b , determine if changes are required. If yes, at block  224   c , requisition incorrectly prepared (RIP) form is filled out and returned to the requisitioner for correction or clarification. At block  224   d , the requisitioner is notified of the rejection and block  221  is re-entered.  
         [0170]     If changes are not required from block  224   b , at block  224   e , cancel the requisition and at block  224   f  notify the requisitioner of the cancellation.  
         [0171]     If the purchase requisition is approved at block  224   a , at block  225 , the purchase order requisition is reviewed by management, as necessary, referencing checklist. At block  226 , determine if approved. If not, go to block  224   b.    
         [0172]     If approved, at block  227 , accounts payable generates purchase order through integrated accounting package with copy forwarded to the requisitioner and faxed to vendor. The block  228  of  FIG. 22   b  is entered, which further illustrates the purchasing process.  
         [0173]     At block  228 , documentation confirming the transmission is maintained by accounts payable. At block  229 , the vendor invoice arrives. At block  220 ′, accounts payable enters invoice information into the invoice log. At block  221 ′, the invoice is forwarded to the requisitioner for approval. At block  222   a ′, determine if approved. If not, at block  222   b ′, requisitioner resolves discrepancy and return to block  221 ′.  
         [0174]     If yes, at block  223 ′, the invoice is forwarded to the analyst for approval, if required. At block  224   a ′, determine if approved. If not, at block  224   b ′, the analyst contacts the requisitioner for resolution and return to block  223 ′. If yes, at block  225 ′, the invoice is forwarded to the controller for approval, if required. At block  226   a ′, determine if approved. If not, at block  226   b ′, the controller contacts the requisitioner for resolution and return to block  225 ′.  
         [0175]     If yes, at block  227 ′, the controller forwards the invoice to accounts payable for entry into the integrated accounting package. At block  228 ′, update invoice log with approved/received back date.  
         [0176]     At block  229 ′, accounts payable records purchase order quantity received through integrated accounting package. At block  220 ″, accounts payable pays the invoice.  
         [0177]      FIG. 23  illustrates the management release form (MRF) process after it has been determined that a supplier is required to take action. At block  230 , the project engineer or designee fills out the MRF per on-line information in the database (i.e.,  FIG. 36 ). At block  231   a , determine if customer approval required. If no, at block  231   b,  document why customer approval is not required and go to block  235 . If yes, at block  232 , the MRF is submitted to the customer for authorization. At block  233   a , determine if customer approved. If no, at block  233   b , determine if the MRF revision is requested. If yes, go to block  230 . If no, at block  233   c , the MRF is rejected, cancelled and closed.  
         [0178]     If the customer approved the MRF, at block  234 , the customer signs the MRF and returns it. At block  235 , the project engineer or designee forwards the signed MRF to the supplier. At block  236 , the supplier fills in the MRF, signs and returns the MRF confirming action to be taken. At block  237 , the project engineer or designee updates the system and the database with a date that the fabricator acknowledges.  
         [0179]     At block  238 , the project engineer or designee files signed MRF in a project file.  
         [0180]      FIGS. 24   a  and  24   b  illustrate a shipping process for shipping product and/or materials via a commercial carrier after a need to ship has been identified.  
         [0181]     At block  240 , a requestor fills out shipping request form in the database and forwards it to a shipping clerk. At block  241   a,  determine if funds are available. If no, at block  241   b , acquire funds and return to block  241   a . If yes, at block  242 , review the shipping request form for accuracy. At block  243 , verify ship date. At block  244   a , determine if the request is accurate. If not, at block  244   b , contact requestor for any other information needed and return to block  242 . If accurate, at block  245 , determine and contact shipping company. At block  246   a , determine if internal or external shipment. If external, at block  246   b , process assigned to external carrier. At block  246   c , file the paperwork.  
         [0182]     If internal, at block  247 , fill out bill of lading. At block  248   a , determine if customs paperwork required. If yes, at block  248   b , complete customs paperwork.  
         [0183]     After block  248   b  and if paperwork is not requited, at block  249 , the shipping clerk inputs carrier name and bill of lading number onto shipping request form in the database. At block  240 ′, determine packaging requirements and package as required. At block  241 ′, stage item for shipping. At block  242   a ′, determine if truck has arrived. If no, at block  242   b ′, hold item in staging area and return to block  242   a′.    
         [0184]     If the truck has arrived, at block  243 ′, load the truck. At block  244 ′, shipping company signs bill of lading. At block  245 ′, the shipping clerk or designee signs carrier&#39;s paperwork, if required. At block  246 ′, file the paperwork and go to the inventory control process of  FIG. 25 .  
         [0185]      FIG. 25  illustrates a warehouse/inventory control process. At block  250 , and coming from either the shipping process of  FIG. 24  or a disposal process, remove items from inventory control database.  
         [0186]     Coming from a receiving process of  FIGS. 26   a  and  26   b , at block  251 , add item to the database and obtain inventory number. At block  252 , fill out inventory tag, apply to item, and record number on shipper. At block  253 , review inventory regularly. At block  254   a , determine if there are any non-conforming items. If yes, at block  254   b , remove non-conforming product from inventory.  
         [0187]     At block  254   c , implement non-conforming product process of  FIG. 27 .  
         [0188]     If no and coming from block  254   a , at block  255   a , determine if inventory counts match database counts. If no, at block  255   b , implement a business system report process. If yes, at block  256   a , determine if too much inventory is on hand. If yes, at block  256   b , send out notification requesting reduction. If no, return to block  253 .  
         [0189]      FIGS. 26   a  and  26   b  illustrate a receiving process to receive, inspect, identify and control product or material prior to transferring to the warehouse process of  FIG. 25  or engineering.  
         [0190]     At block  260 , inspect a hand-carried shipment for damage/non-conformance. At block  261 , review paperwork of an item which has arrived via truck. At block  262 , inspect shipment on truck for non-conformance, i.e., damage, qty. At block  263   a , determine if shipment is damaged/non-conforming. If yes, at block  263   b , implement non-conforming product process of  FIG. 27 . At block  264   a , determine if truck or hand-carried item. If hand-carried, at block  264   b , verify number of packages. If truck, at block  264   c , unload the truck. At block  265 , sign shipper&#39;s paperwork, if required. At block  266 , notify addressee of arrival.  
         [0191]     At block  267 , addressee verifies shipment to packaging slip, if required. At block  268   a , determine if item is customer/vendor sample. If yes, at block  268   b , shipping clerk or designee puts “reference only” tag on item. If no, at block  269   a , determine if truck or hand carried. If truck, at block  269   b , stamp paperwork with receiving stamp and fill in information. If hand-carried, at block  260   a ′, determine if item tagged is non-conforming. If yes, at block  260   b ′, segregate item. At block  260   c ′, obtain decision on item (dispose, return, etc.). If no, at block  261   a ′, determine where to house shipment. If hold, at block  261   b ′, place paperwork in hold folder. At block  261   c ′, determine disposition. If dispose, go directly to block  261   e ′. If ship, at block  261   d ′, implement shipping process of  FIG. 24 .  
         [0192]     At block  261   e ′, implement disposal process.  
         [0193]     At block  261   f ′, put items in stock room if office supplies.  
         [0194]     At block  262 ′, file paperwork if inventory and go to the process of  FIG. 25 .  
         [0195]      FIG. 27  illustrates a non-conforming product process to receive, inspect, identify and control product and material prior to transferring to the warehouse process of  FIG. 25  or engineering.  
         [0196]     At block  270 , notify responsible employee of damage status after visually damaged/non-conforming goods arrive or are found.  
         [0197]     At block  271 , responsible employee assess item to determine status and action to be taken. At block  272 , determine if item is damaged/non-conforming. If no, return to process if required. If yes, at block  273   a , determine if product is customer supplied. If yes, at block  273   b , inform the customer and to go to block  274  to document damage/non-conformance. If product is not customer-supplied, go to block  274 .  
         [0198]     At block  275 , determine whether to tag item non-conforming. If no, return to process if required. If yes, at block  276 , fill out and apply non-conforming tag to item.  
         [0199]     At block  277   a , determine if business system report should be issued. If no, at block  277   b , appropriate action is taken with damaged item and return to process if required. If yes, at block  278 , implement business system report process and return to process if required.  
         [0200]      FIG. 28  illustrates the 1 st  article (pre-production) process after the supplier has informed the user that the container is ready for 1 st  article inspection. At block  280 , 1 st  article preparation process of  FIG. 29  starts.  
         [0201]     At block  281 , schedule 1 st  article inspection.  
         [0202]     At block  282 , sign out/obtain 1 st  article measurement equipment, as required.  
         [0203]     At block  283 , perform 1 st  article inspection of  FIGS. 30   a  and  30   b.    
         [0204]     At block  284   a , determine if product is approved. If no, at block  284   b , rework product. If yes, at block  285 , file 1 st  article paperwork in job file and return to the main process.  
         [0205]      FIG. 29  illustrates the 1 st  article preparation process entered from the process of  FIG. 28 .  
         [0206]     At block  290   a , determine if drawings are available. If not, at block  290   b , determine if a deviation is approved. If not, at block  290   c , request drawings of containers. If yes, at block  291   a , determine if current level parts are available. If not, at block  291   b , determine if a deviation is approved. If not, at block  291   c , request parts. If deviation is approved, at block  292   a , determine if other information is required. If required, at block  292   b , gather other supporting information such as, but not limited to, meeting minutes, MRF(s), FOC(s), and functional critical rack dimensions from the database. If no other information is required, at block  293   a , determine if line-up is required. If required, at block  293   b , line-up designee, giving them as much supporting information about the container as possible. Include any data gathered during prior steps. Items to be considered may include, but are not limited to, outstanding changes, core team contacts, prior concerns, fabricator issues, critical characteristics of the container, experience on previous containers for the commodity, part characteristics, and customer performance expectations. If line-up is not required, return to the process of  FIG. 28 .  
         [0207]      FIGS. 30   a ,  30   b  and  30   c  illustrate a 1 st  article inspection process after a production container has been obtained. At block  300 , inspect welds on container, reference 1 st  article checklist. At block  301   a , determine if approved. If not, at block  301   b , determine if a deviation is approved. If no, at block  301   c , the supplier is to rework the container. If a deviation is approved, at block  302   a , determine if fixtures/tooling are available.  
         [0208]     If dunnage is inspected, this is the first block in that process. If not available, at block  302   b , determine if a deviation is approved.  
         [0209]     If not, at block  302   c , request fixtures/tooling. If approved, at block  303 , inspect fixtures/tooling, reference 1 st  article checklist. At block  304 , perform dimensional inspection. If prototype container/dunnage is inspected, this is the first block in that process. At block  305   a , determine if approved. If not approved and it&#39;s a design/build issue, at block  305   b , document and correct. If not approved and it&#39;s a build error, at block  305   c , determine if a deviation is approved. If not, at block  305   d,  the supplier is to rework.  
         [0210]      FIGS. 30   b  and  30   c  further illustrate the 1 st  article inspection process. If approved, at block  306   a , determine if part fit is required. If no, at block  306   b , determine if per customer request. If yes, at block  306   c , determine if deviation approved. If no, at block  306   d , request parts. If approved, go to block  301 ′ of  FIG. 30   b . Also, go to block  301 ′ if its not per the customer request.  
         [0211]     If part fit is required, at block  307   a , determine if part level matches container/dunnage design part level. If yes, go to block  308   a  of  FIG. 30   c . If no, at block  307   b , determine if a deviation is approved. If yes, go to block  308   a . If no, at block  307   c , request new parts and return to the process of  FIG. 29 .  
         [0212]     At block  308   a , determine if the parts are in an acceptable condition. If no, at block  308   b , determine if a deviation is approved. If no, at block  308   c , request new parts and return to the process of  FIG. 29 .  
         [0213]     If yes, at block  309 , perform part fit in container/dunnage, reference 1 st  article checklist. At block  300   a ′, determine if approved. If not, at block  300   b ′, determine if a deviation is approved. If no, at block  300   c ′, reject the 1 st  article and return to the process of  FIG. 28 .  
         [0214]     If a deviation is approved, at block  301 ′, perform other inspections and gather certifications as required, referencing 1 st  article checklist. At block  302   a ′, determine if approved. If no, at block  302   b ′, determine if a deviation is approved. If no, at block  302   c ′, reject the 1 st  article and return to the process of  FIG. 28 .  
         [0215]     If a deviation is approved, at block  303 ′, complete the 1 st  article checklist and return to the process of  FIG. 28 .  
         [0216]      FIG. 31  illustrates a prototype review process reached from the process of block  310  ( FIG. 4 ).  
         [0217]     At block  311   a , determine if parts available. If no, at block  311   b , determine if a deviation is approved. If no, at block  311   c,  acquire parts and return to block  311   a.  If yes, at block  312 , schedule proto review meeting, including project engineer, OEM supplier representative, assembly plant representative, in-house customer representative, and others, as required. At block  313 , conduct prototype container/dunnage review. At block  314   a , determine whether to approve prototype. If no, at block  314   b , document meeting results and distribute meeting minutes (see database meeting minutes). At block  314   c , determine if changes are required.  
         [0218]     If no, at block  314   d , implement container development process of  FIG. 3 .  
         [0219]     If yes, at block  314   e , implement field order change process of  FIG. 33 . At block  314   f  , implement WIRF process of  FIGS. 16   a  and  16   b , if required (design changes and/or in-house prototype changes). At block  314   g,  determine whether to review prototype changes. If yes, go to block  311   a.  If no, return to process of  FIG. 4 .  
         [0220]     At block  315  and coming from block  314   a , document meeting results and distribute meeting minutes (also database).  
         [0221]      FIG. 32  illustrates release for production process coming from the initiate/manage build process  320  (i.e.,  FIGS. 6   a  and  6   b ).  
         [0222]     At block  321 , the project engineer obtains all changes from previous print level, supporting documents, open FOCs and any other information, as required. At block  322 , implement the WIRF process of  FIGS. 16   a  and  16   b . At block  323 , obtain customer sign-off, if required and at block  324 , return to the initiate/manage build process of  FIGS. 6   a  and  6   b.    
         [0223]      FIGS. 33   a  and  33   b  illustrate a field order change (FOC) process after a field change has been identified. At block  330 , fill out FOC form per on-line information (see  FIG. 37 ). At block  331   a , FOC is identified as either “cost” or “no cost.” If “cost,” at block  331   b,  quote is requested from supplier.  
         [0224]     At block  331   c , supplier returns quote. At block  331   d , the FOC is updated with cost information. At block  331   e,  verify funds are available. At block  332 , the FOC form is submitted to customer for authorization. At block  333 , determine if customer approval required. If no, go to block  336 . If yes, at block  334   a , determine is customer approved. If no, at block  334   b , determine if FOC revisions are requested. If yes, at block  334   c , return to author. If no, at block  334   d , the FOC is rejected, cancelled and closed.  
         [0225]     Coming from block  334   a , if yes, at block  335 , the customer signs and returns the FOC form to the author. At block  336 , the FOC is implemented. At this point, entry into the process from the process of  FIGS. 6   a  and  6   b  is possible.  
         [0226]     At block  337   a , determine if it&#39;s a cost FOC. If yes, at block  337   b , determine if in-house or customer purchased item. If customer, at block  337   c , go to appropriate customer pre-requisition process. If in-house, at block  337   d,  go to the process of  FIGS. 22   a  and  22   b.    
         [0227]     Coming from block  337   a , if no, at block  338 , determine if WIRF is required. If no, go to block  330 ′.  
         [0228]     If yes, at block  339 , implement WIRF process of  FIGS. 16   a  and  16   b . At block  330 ′, the project engineer updates appropriate flags in system (i.e., database).  
         [0229]     At block  331 ′, the project engineer files the signed FOC form and supporting documentation in project file and return to the process, if required.  
         [0230]      FIG. 34  is a screen shot of an electronic container form which is filled out with data which describes a container, an image of which is also shown. Instructions for loading and unloading the container are also provided on the form. The container form is located in the relational database in the computer  12 .  
         [0231]      FIG. 35  is a screen shot of a pair of windows, one of which lists a number of WIRFs (i.e., work initiation request forms) and the overlying window illustrating a particular, filled-out WIRF. The form is also located in the relational database.  
         [0232]      FIG. 36  is a screen shot of a pair of windows, one of which lists a number of MRFs (i.e., management release forms) and the overlying window illustrating a particular, filled-out MRF. As with the other forms, the MRFs are also located in the database in the computer  12 .  
         [0233]      FIG. 37  is a screen shot of a pair of windows, one of which lists a number of field order changes (i.e., FOCs) and the overlying window illustrating a particular field order change form located within the database.  
         [0234]      FIG. 38  is a screen shot of a pair of windows, one of which lists a number of meeting minutes and the overlying window illustrates a form filled-out with minutes from a particular meeting.  
         [0235]      FIG. 39  is a screen shot of a pair of windows, one of which lists a number of in-house requisitions and the overlying window illustrates a form filled-out with information which facilitates the purchase of a particular item.  
         [0236]      FIG. 40  is a screen shot, similar to the screen shot of  FIG. 39 , but which illustrates customer purchase requisition information.  
         [0237]     While embodiments of the invention have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention.