The DVP Test screen is a powerful administrative tool for creating and reporting the test requirements for all components, systems and homologation required by a Feature being developed, as well as providing two useful features in reducing admin and creating robust data.

Auto Referencing to Project Costs

The DVP functionality has been created to allow all Tests created to be automatically entered to the Cost Details for the Feature.

All Tests in the entry drop down have a cost allocated to them which along with the name of the person Responsible for the test and the Test Title is entered to the Feature Costs with the cost showing as 'Estimated'. This will remain as 'Estimated' whilst the Test Result is shown as Pending. When the Test is set to Pass or Fail, the cost in the Feature Costings will automatically update to an 'Actual Cost' indicating the test has been completed.

The 'Carry-Over' DVP Function

The DVP screen can also be used to reference existing Feature Sheets when 'carry-over' data is acceptable to satisfy the test requirements of a new Feature Sheet where the Engineer responsible can determine if any 'carry-over' tests are applicable. Carry-over referencing is described below in Carry-Over DVP Plans where it is explained how to use the function.

Access rights to the DVP functionality are granted for Engineering functions only to Add, Edit and Delete Tests and Test Reports as required.

Creating a New Test Report

By being in the Feature Sheet (referenced by the Feature Sheet Number on the screen under Number) you will be creating a DVP Test Plan linked to this feature sheet.

To start, click Add New Test and complete the form provided. As you will see, the system has been creeated to require minimum user input to create a test entry with various fields auto-filled with the most likely option for convenience.

Please note, all fields are mandatory for adding a DVP test.

Please familiarise yourself with the input requirements.

1. Component to be tested by name.
2. The quantity of parts to be tested.
3. The name of the Engineer responsible for the test (not the test technicican who will perform the testing).
4. From the drop down menu selec the test required.
5. Acceptance criteria is set to PASS by default, but can be changed to By Review, if required.
6. Enter test start date from automated calender.
7. Enter test finish date from automated calendar.
8. Test Results are set to Pending on the Entry screen as the testing has yet to take place. Should testing have been completed already and results are ready to be entered it is possible to set to PASS in this screen and the Edit screen. The Edit screen will also allow a test report to be added.
9. Test report number is set to TBC at the point of tests being created.
10. Notes is a Mandatory field and can be used during test creation or editing to add notes relative to the technician or for later reference. If no notes are required enter NA.

Submit the Test entry to the system and it will be added to the DVP Test Plan as a new line.

Editing, Updating and Deleting Test Results

All tests can have a test reported attached to the correct test line. This can be done in the Edit screen at the base of the form. It is possible to add a new test report AND reference an existing test report already saved to the Feature Sheet number (any other test already uploaded to this DVP test plan. This is useful when a single test report covers more than one test and prevents additional identical files being uploaded (taking up server space!).

To Delete a test, simply click delete and the system will confirm you wish to do this. Once the test has been deleed it has gone forever.

It is also handy to note that if more than one Test Report is being referenced by separate tests (sometimes done when one Test Report covers multiple tests), all test lines will need to be deleted before the report is removed from the system. This prevents a single line being able to delete uploaded Test Reports used on additional lines.

Carry-Over DVP Plans

The Carry-Over function is both useful and intuitive in trying to maintain traceability and can be used in various ways.

Before writing a New DVP Test Schedule it is possible to search by selecting Add/Change Ref DVP button. This will bring up a form with a single field showing ONLY existing Features with an 'original' Test Schedule. It will not display any existing Test Schedules where only a refernce has been made. An original test plan is defined as anything with data added to a the top level DVP Test Schedule. By doing this, the aim it so remove referencing existing Test Schedules that themselves were a reference of, but show no traceability. Whilst this in itself isn't an issue when looking directly as a certain Feature, it does leave big problems when trying to maintain breadcrumbs to solid datums.

When referencing an existing DVP Test Schedule, Engineers are advise to open a New Test Schedule above, and select from 'Tests' the very last option on the list "No Testing Required". This removes various fields, leaving only Responsible and Notes where the Engineer can make record why no testing is required.

All Reference DVP Test Schedules are shown in grey to provide easy visual differentiation from an original Test Schedule created.

Uploading Test Reports

It is possible to upload many formats of test report, but we would advise PDF file formats and JPG drawing formats for ease and simplicity and to aid speedy re-opening on Windows based PCs.

It is also not necessary to add a Report Number to the system as the Test Report will show this and is referenced with a single click, however we understand many Engineers will still want to include this.

General Information

Tests can only be added from those in the automated drop down menu (in the Add/Edit form). This has been done to ensuring data consistency further enhancing the reporting possibilities within the system.

It is also hoped to add additional robustness to engineering selections of tests required removing the need for Engineers to remember or have to reference old material to remind themselves what tests are available to them.