As the system generates VEOs only at time of export, it does not meet the following requirements for management of VEOs:

• verification of digital signatures within the system,
• ability to create ‘onion’ VEOs.
  

As the product generates VEOs at time of export only, it does not meet these requirements for management of VEOs

• verification of digital signatures within the system
• ability to create 'onion' VEOs

The product does not manage disposal of records through links with disposal authorities (as required by Specification 1), but instead manages disposal through the use of security rights.

Robert Marolda,
Regional Manager, Vic Government & SA
Email: robert.marolda@objective.com
Web: http://www.objective.com/

As WinVEO does not manage, store or control electronic records, it does not meet requirements for these metadata elements:

• M102 File Identifier - not guaranteed to be unique, as the value is entered manually
• M103 VERS Record Identifier - not guaranteed to be unique, as the value is entered manually

Therefore, WinVEO is compliant with VERS v1.2 Specification 2 when it is deployed as part of a full recordkeeping regime that includes registration and control of records.

As the system has been designed around specific requirements of Department of Justice, it does not meet requirements for the following metadata elements:

• M13 Agent Type – the system is configured to use only a sub-set of the required values.
• M33 Scheme Type – the system is configured to use a functional titling scheme, therefore subject and free-text titling schemes cannot be used.
• M69 Event Type – the system is configured to use only a sub-set of the required values.
• M90 Sentence – the system is configured to use only a sub-set of the required values.

The system does not meet requirements for these metadata elements:

• M69 Event Type - the system is configured to use only a sub-set of the required values.

None Noted