# PROCEDURE 

1.  **Introduction**

## 1.1 Purpose

The purpose of this document is to define the process followed to
implement virtual reality visualizations to meet customer requirements.

## 1.2 Scope

This process applies to all new projects to be implemented by personnel
in the Virtual Reality Laboratory (VRL).

## 2.0 References

**2.1 Referenced Procedures and other Documents**

> LMD-PR-005 Contracts Procedure

2.  **Forms**

> RDHFL Task Request Form, QF-TASK-01
>
> RDHFL Task Tracking Form, QF-TASK-02

3.  **Definitions and Acronyms**

> Team Lead -- The individual responsible for tracking all projects
> supported by RDHFL personnel. The Team Lead also handles laboratory
> resource allocation of hardware, software and personnel.
>
> Virtual Reality Programmer -- A senior computer programmer with
> experience in building 3-D models using the hardware and software
> resources in the VRL.
>
> RDHFL -- Research Development and Human Factors Laboratory
>
> VRL -- Virtual Reality Laboratory
>
> CAD -- Computer Aided Design
>
> HMD -- Head Mounted Display
>
> VCR -- Video Cassette Recorder

**3.0 Process Description**

1.  **Process Initiation**

> The process is initiated when a customer submits an RDHFL Task Request
> Form to the Team Lead. The Team Lead will meet with one or more VR
> programmers to determine if resources are available to take on the
> project. This includes making sure the VRL has the hardware and
> software to do the project and checking on VRL programmer availability
> based on other ongoing projects.
>
> If it is determined that the project can be completed to the
> satisfaction of the customer, the Team Lead will contact the customer
> to set up a meeting to discuss the project schedule and deliverables.
>
> If the project cannot be done, the Team Lead will contact the customer
> to discuss the reasons why. In some cases, the project could be
> resubmitted once changes are made to address the issues leading to the
> project being rejected.
>
> The customer should be contacted as soon as possible to acknowledge
> the task request form has been received. The Team Lead should make
> every effort to accept or reject the task request form in a timely
> manner.

2.  **Schedule work and receive data from customer.**

> The Team Lead and VRL programmers meet with the customer to start
> planning product realization. The Team Lead or VRL programmers fill
> out the Task Tracking Form. The form tracks:

-   What inputs the customer supplies such as blueprints or CAD drawings
    and what should be done with the inputs when the project is
    finished.

-   What hardware and software should be used during the course of the
    project.

-   What deliverables the VRL must provide.

-   When they must be finished and in what format, i.e. Videotape,
    electronic files or printouts.

> The Team Lead and VRL programmers review the requirements with the
> customer. The customer signs off on the requirements before work is
> started. An effort should be made to keep the Task Tracking form up to
> date at all times.
>
> Once the VRL programmers receive the customer's supplied inputs, the
> programmers check the supplied inputs for adequacy. If the supplies do
> not meet the needs of the programmers, the customer will be asked to
> supply better inputs. The inputs will be marked to indicate how the
> inputs are to be handled at the end of the project.

1.  **Build 3-D Model**

> The VRL programmer begins by adapting the customer's inputs to build a
> 3-D model of the data. In some cases, the programmer uses a digital
> camera to photograph objects for the model and creates textures out of
> the photographs.
>
> Some projects may require the purchase of new hardware or software
> using a purchase request. The VRL programmers may use some or all of
> the following hardware or software:
>
> Creator 3D Modeling
>
> Vega
>
> Jack Anthropomorphic Models
>
> 3D Goggles
>
> Head Mounted Display
>
> VCR Recorder
>
> Cameras
>
> Silicon Graphics Computers

2.  **Prototype**

> The VRL programmer builds a working prototype to meet the customer's
> requirements. The prototype adds features to the 3-D model such as
> stereoscopic viewing with 3D goggles, interactivity with the use of a
> glove, and real time walk through of the virtual environment. The
> programmer verifies the prototype meets customer requirements, and
> documents this review on the RDHFL Task Tracking form.

3.  **Review prototype with customer**

> The VRL programmer meets with the customer and presents the prototype.
> In most cases the customer asks for minor modifications to the
> prototype. These changes are recorded on the RDHFL Task Tracking form.
> The VRL programmer makes the changes and arranges another meeting.
> This process continues until the customer accepts/validates the
> prototype.

4.  **Process deliverables.**

> The VRL programmer creates the appropriate deliverable for the
> customer. This could include a videotape fly through presentation of
> the prototype, computer graphic files or printouts.

3.  **Process Control**

    1.  **Customer Requirements**

> The customer of this process requires that the project is completed on
> schedule and all deliverables are delivered to the customer in the
> proper format as agreed to in the Task Tracking Form.

2.  **Process Verification/Monitoring**

> The RDHFL Task Tracking form is employed throughout the process to
> monitor for control and conformance to customer requirements. The
> customer must sign the RDHFL Task Tracking form to indicate acceptance
> of the process realization plan. The customer must sign the form to
> indicate acceptance of the final deliverable.
>
> The Team Lead in ACB-840 writes weekly status reports to track
> progress during the project realization.

**5.0 Training**

> Off site training in the use of commercial off the shelf software and
> hardware is available to ACB-840 senior programmers as needed.

6.  **Records**

  --------- --------------------- --------------- -------------- --------------- -----------------
  **Seq**   **Record              **Doc \# (if    **Location**   **Retention**   **Disposition**
            Description**         applicable)**                                  

  1         RDHFL Task Request    QF-TASK-01      Project File   2 Years         Discard
            Form                                  Folder in                      
                                                  RDHFL                          

  2         RDHFL Task Tracking   QF-TASK-02      (See above)    2 Years         Discard
            Form                                                                 

  3         Weekly Status Report  N/A             RDHFL Computer 2 Years         Discard
                                                  Network                        

                                                                                 
  --------- --------------------- --------------- -------------- --------------- -----------------

## APPENDIX A: Revision History

+---------+----------+------------------------------------------------+
| R       | REVISION | DESCRIPTION OF CHANGE                          |
| EVISION |          |                                                |
|         | DATE     | (Administrative, Scope, Process, or New )      |
| NUMBER  |          |                                                |
+---------+----------+------------------------------------------------+
| 1       | 12/1/02  | Initial Release, entire document -- New        |
+---------+----------+------------------------------------------------+
| 2       | 5/22/03  | Minor changes to wording to clarify process -  |
|         |          | Admin                                          |
+---------+----------+------------------------------------------------+
| 3       | 12/12/03 | Added response time to customer for task       |
|         |          | request and need to keep task tracking up to   |
|         |          | date                                           |
+---------+----------+------------------------------------------------+
| 4       | 12/22/05 | Organizational changes due to the Technical    |
|         |          | Center Realignment.                            |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+
|         |          |                                                |
+---------+----------+------------------------------------------------+