Release UV RFP Part 2 Encl 3 CDRL and DIDs.pdf

1982
Protected Mobility Act
Capability Project

Utility Vehicle –
Medium/Light
Information
Request for Proposal

Part Tw
Official o
Statement of Requirements
the

Appendix 3
under

Contract Data Requirements List
and
Data Item
Released
Descriptions

1982
Act
Information
Part 1 - Contract Data
Requirements List (CDRL)
Official
the
under
Released

P a g e 4 | 119

Explanatory Note
1.
The Contract Data Requirements List (CDRL) at Part 1 of this document lists the
Contract Data items and defines the schedule for each Contract Data item delivery.
2.
The supporting Data Item Descriptions (DIDs) are at Part 2 of this document. The DIDs
specify the format, content, preparation and delivery requirements for each of the Contract
Data items. Clause 7 of the draft Acquisition Contract defines the requirements for the
provision of Contract Data under the Contract once it is established.
3.
There are three uses for Contract Data items:
a.
Proposal Evaluation. One of the DIDs (DID PROJ-1.11) solicits information that
1982
will be used for the RFP evaluation only. Although there may be clarification of
the content and some of the information may be subsequently agreed for transfer
to other Contract Data items (e.g., Plans), the update or redelivery of this data
Act
deliverable is not part of any subsequent contract arrangement, and it will not be
included in Annex C of the Contract when it is signed.
b.
Contract Baseline Documents. There are two types of Contract Data items that
establish the Contract baseline.
(1)
those in the first category subsequently become part of the Acquisition
Contract (i.e., are draft Annexes to the Contract). These are the Detailed
Specification (DID PROJ-1.8), the Statement of Work (DID PROJ-1.9) and
the Government Furnished Materiel List (DID ILS-5.1); and
Information
(2)
the second category are DIDs that specify plans that define how the
Acquisition Contract would be managed and performed. Once these are
Accepted by the Crown, then they may only be varied by the process
defined in clause 7.2 of the Acquisition Contract.
Official
Both categories are submitted as part of the Proposal in ‘draft’ form and are
assessed during the evaluation of Proposals. These Contract Data items may be
subsequently negotiated further with the preferred Respondent. The term
“DRAFT at
the
Proposal” is used for the initial draft delivery date and means that the
data product is expected to be substantially complete (albeit subject to any
negotiation). An example from another product or a brief summary is acceptable
if “EXAMPLE at Proposal” is stated. The CDRL and applicable DID will define
when later versions of that Contract Data item must be provided as part of
subsequent Acquisition Contract performance.
under
c.
Contract Data Deliverables. Some Contract Data items will be delivered by the
successful Contractor once under contract (e.g., Monthly Reports). Some are
marked “EXAMPLE at Proposal” and the examples wil  be used to evaluate
Proposals. Some are marked “INFO ONLY for Proposal” and these Contract Data
items are not required as part of the Proposal submission. These DIDs are
included in the CDRL to assist the Respondent to assess and estimate the price
of the work under the Acquisition Contract for supplying these future deliverables.
Released
The CDRL and DIDs are subsequently included in Annex C of the Contract and
will be updated to remove the Proposal-only DIDs.
4.
Where a hard copy(s) is stipulated, the hard copies are only required as part of the final
deliverable. Only an electronic version is required at Proposal.
5.
Where the description “Contractor” is used in the DIDs, this also means:
a.
the “Respondent” for the purposes of the Proposal submissions; and

P a g e  5 | 119

b.
the “Preferred Respondent” during contract negotiations.
6.
Where the term “the Contract” is used in the CDRL and DIDs, this means the
Acquisition Contract.

1982
Act
Information
Official
the
under
Released

P a g e 6 | 119

link to page 16 link to page 16 link to page 18 link to page 20 link to page 22 link to page 22 link to page 24 link to page 26 link to page 26 link to page 28 link to page 28 Table: Contract Data Requirements List (CDRL)
1982
DID number
Deliverable
Initial draft
Date by which Contract Data item must
Updated version delivery date
delivery date
have been Accepted by Crown
DID PROJ-1.1
Project Management
DRAFT at Proposal
Contract Execution Date of Acquisition
As required, in accordance with
Act
Plan
Contract
clause 15.1 of the Contract
DID PROJ-1.2
Project Schedule
DRAFT at Proposal
Contract Execution Date of Acquisition
As required
(outline of major
Contract
tasks and
milestones)
DID PROJ-1.3
Project Quality Plan
DRAFT at Shortlist
Contract Execution Date of Acquisition
As required
/ Negotiations
Contract
DID PROJ-1.4
Risk Management
DRAFT at Shortlist
Contract Execution Date of Acquisition
As required
Plan
/ Negotiations
Contract
Information
DID PROJ-1.5
Security Plan
DRAFT at Shortlist
Contract Execution Date of Acquisition
As required
/ Negotiations
Contract
DID PROJ-1.6
Monthly Progress
INFO ONLY for
First report within five Business Days after the

Reports
Proposal
end of the first full calendar month after the
Contract Execution Date of the Acquisition
Official
Draft to be provided  Contract.
by 15th of first full
Thereafter, monthly within five Business Days
calendar month
of each month end.
the
DID PROJ-1.7
Meetings and Reviews
INFO ONLY for
Agenda: Two Business Days prior to relevant

Documentation
Proposal
Meeting or Review.
Minutes: Final after 10 Business Days.
Agenda: Draft 10
Business Days
under
prior to relevant
Meeting or Review.
Minutes: Draft five
Business Days
after relevant
Meeting or Review
Released

P a g e  7 | 119

link to page 31 link to page 33 link to page 35 link to page 35 link to page 35 link to page 38 link to page 38 link to page 41 link to page 41 link to page 44 link to page 44 link to page 46 link to page 46 link to page 46 link to page 48 link to page 48 link to page 50 link to page 50 link to page 51 link to page 51 DID number
Deliverable
Initial draft
Date by which Contract Data item must
Updated version delivery date
delivery date
have been Accepted by Crown
1982
DID PROJ-1.8
Detailed Specification
DRAFT at Proposal
Converted to form part of the Contract
As required, utilising the Contract
Technical Specification at Annex B, prior to
Change process, per clause 15.5 of
Contract Execution Date of Acquisition
the Contract.
Contract
Act
DID PROJ-1.9
Statement of Work
DRAFT at Proposal
Converted to form the Contract Statement of
As required, utilising the Contract
Work at Annex A, prior to Contract Execution
Change process
Date of Acquisition Contract
DID PROJ-1.10
Verification Cross
DRAFT at Shortlist
Contract Execution Date of Acquisition
As required
Reference Index
/ Negotiations
Contract
(VCRI)
DID PROJ-1.11
C4I Integration
FINAL at Proposal
N/A
N/A
Proposal
Information
DID ECP-2.1
Systems Engineering
DRAFT at Shortlist
Contract Execution Date of Acquisition
As required
Plan
/ Negotiations
Contract
Proposal
DID ECP-2.2
Configuration
DRAFT at Shortlist
Contract Execution Date of Acquisition
As required
Management Plan
/ Negotiations
Contract
Official
DID ECP-2.3
Electromagnetic
EXAMPLE at
Contract Execution Date of Acquisition
As required
Environmental Effects
Proposal
Contract
Control Plan
the
DID ECP-2.4
TEMPEST Control
EXAMPLE at
Contract Execution Date of Acquisition
As required
Plan
Proposal
Contract
DID ENG-3.1
Engineering Drawing
EXAMPLE at
For each variant, two months after Final
As required
Index
Proposal
Design Review of that variant
DID ENG-3.2
Engineering Drawing
EXAMPLE at
For each variant, two months prior to first
As required
under
Package
Proposal and
vehicle of that variant delivery in New Zealand
confirmation of
whether 3D dataset
and/or
manufacturing
drawings will be
provided.
Released

P a g e  8 | 119

link to page 53 link to page 54 link to page 54 link to page 56 link to page 56 link to page 57 link to page 57 link to page 58 link to page 59 link to page 59 link to page 60 link to page 60 link to page 62 link to page 62 link to page 63 link to page 63 link to page 65 DID number
Deliverable
Initial draft
Date by which Contract Data item must
Updated version delivery date
delivery date
have been Accepted by Crown
1982
DID ENG-3.3
Circuit Diagrams
EXAMPLE at
For each variant, two months after Final
As required
Proposal
Design Review of that variant
DID ENG-3.4
Equipment Layout
EXAMPLE at
For each variant, two months prior to first
As required
Act
Diagrams
Proposal
vehicle of that variant delivery in New Zealand
DID ENG-3.5
Communication
EXAMPLE at
For each variant, two months after Final
As required
System Schematic
Proposal
Design Review of that variant
DID ENG-3.6
Complete Equipment
INFO ONLY for
For each variant, two months prior to first
As required
Schedule Illustrations
Proposal
vehicle of that variant delivery in New Zealand
Two months after
confirmation of
CES (via
Provisioning
Information
Conference)
DID ENG-3.7
Configuration Records
EXAMPLE at
For each vehicle, at Acceptance of that vehicle
As required
Proposal
DID ENG-3.8
Antenna Compatibility
EXAMPLE at
For each variant, two months after Final
As required following any
Analysis
Proposal
Design Review of that variant
subsequently agreed design change
Official
DID ENG-3.9
Failure Mode, Effects
EXAMPLE at
Three months after Final Design Review of the
As required following any
and Criticality Analysis
Proposal
last variant
subsequently agreed design change
the
DID ENG-3.10
Weight, Balance and
EXAMPLE at
For each variant, three months after the Final
As required following any
Stability Analysis
Proposal
Design Review for that variant
subsequently agreed design change
DID ENG-3.11
Safety Assessment
EXAMPLE at
Three months after Final Design Review of the
As required
Report
Proposal.
last variant
under
Final draft two
months before first
of each variant
delivery.
DID TEST-4.1
Master Test Plan
DRAFT at Shortlist
Contract Execution Date of Acquisition
As required
/ Negotiations
Contract
Released

P a g e 9 | 119

link to page 69 link to page 71 link to page 73 link to page 75 link to page 75 link to page 77 link to page 77 link to page 77 link to page 79 link to page 79 link to page 80 link to page 80 DID number
Deliverable
Initial draft
Date by which Contract Data item must
Updated version delivery date
delivery date
have been Accepted by Crown
1982
DID TEST-4.2
Test Plans
INFO ONLY for
Relevant Test Programme Commencement
As required
Proposal
-20 Business Days
Relevant Test
Act
Programme -60
Business Days
DID TEST-4.3
Test Procedures
INFO ONLY for
Relevant Test -5 Business Days
As required
Proposal
Relevant Test
Programme -20
Business Days
DID TEST-4.4
Test Reports
INFO ONLY for
Relevant Test +10 Business Days
As required
Information
Proposal
Draft to be provided
as part of DID
TEST-4.2 (Test
Plans)
DID TEST-4.5
Official
Electrical Load Test
EXAMPLE at
Relevant Test Programme Commencement
As required
Plan
Proposal
-20 Business Days
DID TEST-4.6
Electromagnetic
EXAMPLE at
Relevant Test Programme Commencement        As required
the
Environmental Effects
Proposal
-20 Business Days
Test Plan
DID TEST-4.7
Roll Over Protection
INFO ONLY at
For each variant, one month after Final Design
As required
Structure Report
Proposal
Review of that variant
under
Draft to be provided
five Business Days
before Preliminary
Design Review of
each variant
DID TEST-4.8
Cyber Vulnerability
If Contractor has
For each variant, one month after Final Design
As required
Report
this information,
Review of that variant
Released

P a g e  10 | 119

link to page 83 link to page 83 link to page 85 link to page 90 link to page 90 link to page 90 link to page 92 link to page 92 link to page 92 link to page 94 link to page 94 link to page 94 link to page 96 link to page 96 link to page 96 link to page 97 DID number
Deliverable
Initial draft
Date by which Contract Data item must
Updated version delivery date
delivery date
have been Accepted by Crown
EXAMPLE at
1982
Proposal
DID ILS-5.1
Government Furnished  DRAFT at Proposal
Agreed GFM included in Annex J (GFM List) of  As required, utilising the Contract
Materiel List
Contract
Change process
Act
DID ILS-5.2
Codification
EXAMPLE at
Already codified items: NSN provided in
On order of any new items of
Proposal
Complete Support Equipment Price Catalogue
equipment
in Annex E of Contract.
Items not already codified: Two months after
relevant Crown Provisioning Notice.
DID ILS-5.3
Manufacturers
DRAFT at Proposal
One month prior to the relevant Provisioning
As required – see clause 6 of the
Recommended Spares
Conference
Contract
List
Information
DID ILS-5.4
Recommended
DRAFT at Proposal
One month prior to the relevant Provisioning
As required – see clause 6 of the
Support and Test
Conference
Contract
Equipment List
DID ILS-5.5
Packaging Handling
INFO ONLY for
Final Provisioning Conference
As required
Storage and
Proposal
Transportation Data
Official
Two months after
Contract Execution
Date of Acquisition
the
Contract
DID ILS-5.6
Human Machine
INFO ONLY for
For each variant, one month after Final Design
As required
Interface Analysis
Proposal
Review of that variant
Report
Draft:  for each
variant, five
under
Business Days
before the Final
Design Review of
that variant.
DID ILS-5.7
Facilities Data
If Contractor has
Four months after Contract Execution Date of
As required
this information,
Acquisition Contract
EXAMPLE at
Proposal
Released

P a g e  11 | 119

link to page 99 link to page 99 link to page 100 link to page 100 link to page 100 link to page 101 link to page 101 link to page 104 link to page 106 link to page 106 link to page 107 link to page 107 link to page 108 link to page 108 DID number
Deliverable
Initial draft
Date by which Contract Data item must
Updated version delivery date
delivery date
have been Accepted by Crown
1982
DID ILS-5.8
Material Safety Data
EXAMPLE at
For each variant, three months after Final
As required
Sheets
Proposal
Design Review of that variant
DID ILS-5.9
Reliability, Availability
EXAMPLE at
For each variant, three months after Final
As required
Act
and Maintainability
Proposal
Design Review of that variant
Data
DID ILS-5.10
Pass Through
EXAMPLE at
For each variant, one month after Final Design
As required
Warranty Information
Proposal
Review of that variant
DID PUB-6.1
Operator Manuals
EXAMPLES at
Four months after completion of respective
As required
Proposal
training course
Draft: Two months
prior to start of the
relevant training
Information
course
DID PUB-6.2
Equipment
EXAMPLES at
Four months after completion of respective
As required
maintenance manuals
Proposal
training course
Draft: Two months
prior to start of the
Official
relevant training
course
DID PUB-6.3
Support and Test
EXAMPLES at
Four months after completion of respective
As required
the
Equipment Manuals
Proposal
training course
Draft: Two months
prior to start of the
relevant training
under
course
DID PUB-6.4
Illustrated Parts
EXAMPLES at
For each variant, two months before delivery of As required
Catalogue
Proposal
first vehicle of that variant
Draft: Two months
after initial
Provisioning
Conference
Released

P a g e 12 | 119

link to page 113 link to page 113 link to page 113 link to page 115 link to page 117 link to page 119 link to page 119 DID number
Deliverable
Initial draft
Date by which Contract Data item must
Updated version delivery date
delivery date
have been Accepted by Crown
1982
DID PUB-6.5
Tie Down Scheme for
If Contractor has
For each variant, two months before delivery of  As required
Maritime, Air and Rail
this information,
first vehicle of that variant
Transportation
EXAMPLE at
Proposal
Act
DID TRA-7.1
Training Plan
DRAFT at Shortlist
Contract Execution Date of Acquisition
As required
/ Negotiations
Contract
DID TRA-7.2
Training Package
INFO ONLY for
20 Business Days prior to commencement of
As required
Proposal
the first training course
90 Business Days
prior to
commencement of
the first training
Information
course
DID TRA-7.3
Pre-Course
INFO ONLY for
Two months after completion of each training
As required
Information
Proposal
course (as part of DID TRA-7.2)
Four months prior
to commencement
Official
of each relevant
training course  the
under
Released

P a g e  13 | 119

1982
Act
Information
Part 2 - Data Item Descriptions

Official
the
under
Released

P a g e 14 | 119

1982
Act
Information
Section 1 – Project Plans

Official
the
under
Released

P a g e 15 | 119

DID PROJ-1.1 – Project Management Plan
REFERENCE NUMBER
TITLE:
DID PROJ-1.1
PROJECT MANAGEMENT PLAN
DESCRIPTION/PURPOSE:
The Project Management Plan describes how the Contractor will organise, plan and control
the Project.
1982
ISSUE DATE:
Act
Draft: Proposal.
Final: Contract Execution Date of Acquisition Contract.
FORMAT
1.
The Project Management Plan may be in the Contractor’s layout.
2.
The Project Management Plan shall be written in English.
Information
3.
The Project Management Plan shall be delivered in an electronic format capable of
being read, copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The Project Management Plan shall describe how the Contractor intends to organise,
plan and control the Project.
the
5.
The Project Management Plan shall show the interrelationship between the
management plans used to control the Project and describe the mechanism(s) by which the
Contractor proposes to ensure that the various plans are consistent.
6.
The Project Management Plan shall:
under
a.
provide a detailed description of the Contractor’s Project organisation;
b.
document, at a summary level, the process and techniques used to coordinate
and manage the entire Project, with specific reference to other management
plans (as applicable);
c.
describe organisational relationships and responsibilities within the Contractor’s
Released
organisation including how the Contractor maintains a safe and healthy working
environment for its employees and on-site Crown personnel;
d.
describe the process for the selection and management of Major Subcontractors,
including the following:
(1)
identity of each Major Subcontractor;
(2)
tasks and responsibilities of each Major Subcontractor;
(3)
city location of each Major Subcontractor’s facilities; and

P a g e 16 | 119

(4)
management of the Contractor to Major Subcontractor relationships;
e.
identify the locations where the equipment deliverables will be positioned for all
work in support of the Contract, including manufacture, test and evaluation; and
f.
identify key personnel who will be assigned to the Project, with a description of
their:
(1)
responsibilities for this Project and for any other customers;
(2)
level of authority relating to the Project;
(3)
qualifications and experience; and
1982
(4)
fluency in English.
Act
7.
As a minimum, key personnel shall be identified for the following areas of
responsibility:
a.
Contract Management – management of the Contractor to Crown relationship,
the primary point of contact with the Crown in relation to contract matters
b.
Project Management – overall day-to-day management of the Project and
delivery of contracted outputs in accordance with the contracted schedule
c.
Engineering/Design – managing all non-recurring engineering and new design
Information
d.
Testing – management of testing programme relating to all contract deliverables
e.
Through Life Support – management of the establishment of through life support
arrangements
Official
8.
The Project Management Plan shall identify:
a.
any related documents used for reference and provide links or copies of each
the
such related document if not already provided to the Crown; and
b.
other plans or documents that expand upon this Plan in greater detail.
QUANTITY
under
9.
The Contractor shall provide one electronic copy.

Released

P a g e 17 | 119

DID PROJ-1.2 – Project Schedule
REFERENCE NUMBER
TITLE:
DID PROJ-1.2
PROJECT SCHEDULE
DESCRIPTION/PURPOSE:
The Project Schedule describes the Contractor’s plan for the Project timeline, and how the
activities to be undertaken by the Contractor are identified as definable events and how they
1982
are sequenced. It is updated monthly to reflect actual progress.
ISSUE DATE:
Act
Draft: Proposal (outline of major tasks and significant milestones, sufficient to show critical
path).
Final: Contract Execution Date of Acquisition Contract.
FORMAT
1.
The Project Schedule may be in the Contractor’s layout.
Information
2.
The Project Schedule shall be written in English.
3.
The Project Schedule shall be delivered in the format of one electronic copy in
Microsoft® Project, compatible with version 2016.
Official
CONTENT
4.
For the Proposal submission, the draft Project Schedule must be to a level of detail
the
sufficient for the Crown to gain an understanding of the Contractor’s proposed schedule, and
must include a clear critical path.
5.
The final Project Schedule is as agreed during negotiation of the Contract and is the
initial baseline for the delivery of the Utility Vehicles and associated Contract Deliverables.
under
6.
The Project Schedule shall be a portrayal of the tasks, durations, dependencies, linked
activities, resources, floats and constraints associated with the Contractor’s performance of
the Contract.
7.
The Project Schedule shall include all applicable definable events and tasks
throughout the entire scope of the Project from Contract Execution Date of the Acquisition
Contract to Acceptance by the Crown of the last Contract Deliverable under the Acquisition
Released
Contract, excluding any follow-on through life support arrangements that may be offered or
applicable.
8.
The Project Schedule shall depict key events as milestones, such as:
a.
all Systems Requirements Reviews (SRR), if any;
b.
all Preliminary Design Reviews (PDR), if applicable;
c.
all Critical Design Reviews (CDR), if applicable and if any;

P a g e 18 | 119

d.
all Final Design Reviews (FDR), if applicable;
e.
ordering of major material;
f.
receipt of major material;
g.
manufacture/fabrication/assembly/integration;
h.
ILS reviews, including Provisioning Conferences;
i.
test and evaluation milestones including, if applicable, Factory Acceptance Tests
(FAT) and Test Readiness Reviews (TRR);
1982
j.
delivery of all Systems and associated other Contract Deliverables;
k.
delivery of Support Equipment;
Act
l.
delivery of training courses;
m.
delivery and commissioning of training devices, if any;
n.
delivery of all other Contract Deliverables;
o.
Acceptance of all Systems and associated other Contract Deliverables;
p.
Acceptance of all Support Equipment;
Information
q.
Acceptance of training courses;
r.
Acceptance of Training Devices, if applicable;
s.
Acceptance of all other Contract Deliverables;
Official
t.
all Milestones specified in the proposed Schedule of Payments; and
the
u.
other major events or internal sign-off steps that the Contractor may select that
represent the accomplishment of critical technical and management steps
towards completion of the Contract Deliverables.
9.
The delivery location for all physical Contract Deliverables (excluding documentation,
under
training courses and any training devices) will be in Trentham Military Camp, Upper Hutt,
New Zealand.
10.  For the Proposal submission, the Contractor shall use 11 June 2024 as the indicative
Contract Execution Date of the Acquisition Contract to baseline the entire schedule.
11.  The Project Schedule shall include the tasks and milestones required from Major
Subcontractors, with each Major Subcontractor clearly identified.
Released
12.  Project Schedule tasks shall have unique identifiers.
QUANTITY
13.  The Contractor shall provide one electronic copy.

P a g e  19 | 119

DID PROJ-1.3 – Project Quality Plan
REFERENCE NUMBER
TITLE:
DID PROJ-1.3
PROJECT QUALITY PLAN
DESCRIPTION/PURPOSE:
The Project Quality Plan describes the Contractor’s, and the Contractor’s proposed Major
Subcontractor’s, quality processes.
1982
ISSUE DATE:
Act
Draft: at Shortlist / Negotiations.
Final: Contract Execution Date of Acquisition Contract.
FORMAT
1.
The Project Quality Plan may be in the Contractor’s layout.
2.
The Project Quality Plan shall be written in English.
Information
3.
The Project Quality Plan shall be delivered in an electronic format capable of being
read, copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The Project Quality Plan shall include, for the Contractor and Major Subcontractors:
a.
a description, with supporting evidence, of its quality system, organisation and
the
certification;
b.
a description of the organisational responsibilities for the quality control
obligations under the Contract;
under
c.
for the Contractor specifically, a description of the process by which the particular
provisions of the Contract relating to quality will flow down to Major
Subcontractors including indicative dates of audits and the organisation carrying
out the audit, for example the Contractor or any third-party;
d.
a description of the review or corrective process; and
e.
details of the key duty holders for quality.
Released
5.
The Project Quality Plan shall provide details of all planned inspections and
witness/hold points relating to the activities relevant to the Contract undertaken by the
Contractor and Major Subcontractors (as applicable).
6.
The Project Quality Plan shall describe the Contractor’s Material Review Board and
Tool Control programmes (as applicable).
7.
The Project Quality Plan shall demonstrate that the Contractor and its Major
Subcontractors have in place appropriate quality processes, which meet international

P a g e 20 | 119

standards relating to System manufacturing, engineering, maintenance and modification (as
applicable).
8.
The Project Quality Plan shall identify:
a.
any related documents used for reference, and provide links to them or copies of
the same where the Crown does not already have copies of such referenced
documents; and
b.
other plans or documents that explain the Project Quality Plan in greater detail.
QUANTITY
1982
9.
The Contractor shall provide one electronic copy.

Act
Information
Official
the
under
Released

P a g e 21 | 119

DID PROJ-1.4 – Risk Management Plan
REFERENCE NUMBER
TITLE:
DID PROJ-1.4
RISK MANAGEMENT PLAN
DESCRIPTION/PURPOSE:
The Risk Management Plan describes how the Contractor will plan, control and manage
risks associated with the Contract.
1982
ISSUE DATE:
Act
Draft: at Shortlist / Negotiations.
Final: Contract Execution Date of Acquisition Contract.
FORMAT
1.
The Risk Management Plan may be in the Contractor’s layout.
2.
The Risk Management Plan shall be written in English.
Information
3.
The Risk Management Plan shall be delivered in an electronic format capable of being
read, copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The Risk Management Plan shall include, as a minimum:
a.
a description of the Contractor’s approach to risk management on the Project;
the
b.
a description of steps in the Contractor’s risk management process;
c.
allocation of risk management responsibilities; and
under
d.
an initial risk register based on:
(1)
a risk assessment of the Project, identifying high-level risks, including risks
associated with Major Subcontractors;
(2)
a priority for each risk based on likelihood and impact;
(3)
a risk treatment action plan, showing the position responsible for taking
action; and
Released
(4)
specific assessment of logistics risks related to support from sub-
contractors and vendors and shipping deliverables to New Zealand.
5.
The Risk Management Plan shall describe the level of visibility and input that will be
provided to the Crown throughout the Project (e.g., Crown participation in Risk Reviews,
Crown ability to nominate risks, etc.).

P a g e  22 | 119

6.
The Risk Management Plan shall identify any related documents used for reference
and provide links to them or copies of the same where the Crown does not already have
copies of such referenced documents.
QUANTITY
7.
The Contractor shall provide one electronic copy.

1982
Act
Information
Official
the
under
Released

P a g e 23 | 119

DID PROJ-1.5 – Security Plan
REFERENCE NUMBER
TITLE:
DID PROJ-1.5
SECURITY PLAN
DESCRIPTION/PURPOSE:
The Security Plan describes the procedures for managing, handling, processing and
controlling sensitive and classified material.
1982
ISSUE DATE:
Act
Draft: at Shortlist / Negotiations.
Final: Contract Execution Date of Acquisition Contract.
FORMAT
1.
The Security Plan may be in the Contractor’s format.
2.
The Security Plan shall be written in English.
Information
3.
The Security Plan shall be delivered in an electronic format capable of being read,
copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
Material Security
4.
For sensitive and classified equipment and material the Security Plan shall identify the
the
following:
a.
the security classification system used;
b.
the authority chain, including any delegated and sub-delegated responsibilities;
under
c.
storage and handling procedures for information, documentation and equipment;
d.
procedures used by the Contractor and Major Subcontractors, for the security
vetting of personnel that will have access to sensitive and classified material;
e.
procedures used by the Contractor and Major Subcontractors, for the security
accreditation of project work areas that will be used for the processing and
storage of sensitive and classified material;
Released
f.
procedures used by the Contractor and Major Subcontractors for the audit of their
security measures and procedures and base of last audit;
g.
procedures in the event of compromise;
h.
destruction requirements for:

P a g e 24 | 119

(1)
any paper or other material on which there is writing or on which there are
marks, figures, symbols or perforations having a meaning for persons or
machines qualified or able to interpret them;
(2)
any disk, tape, software, database and any other article or material from
which sound, images, writing or messages are capable of being reproduced
with or without the aid of any other article or device;
(3)
any survey, sketch, plan, drawing, certificate of title and any other
certificate or record used for any conveyance for security purposes; and
(4)
any information kept by means of any mechanical, electronic or other
device.
1982
Physical Security
Act
5.
The Security Plan shall describe:
a.
the security measures and procedures to control and record access to secure
areas;
b.
the security clearances required by Crown, and Major Subcontractor personnel;
c.
the procedures used by the Contractor and Major Subcontractors, for the security
vetting of personnel that will have access to secure areas;
Information
d.
the procedures used by the Contractor and Major Subcontractors, for the security
accreditation of project work areas that will be used for the processing and
storage of sensitive and classified material; and
e.
the procedures and approvals for handling Cyryptographic Controlled items (CCI)
including the Communications Security (ComSec) accounts that will hold CCI at
Official
the required locations for integration design and testing. Note for Respondents:
This may be included in the C4I Integration Proposal (DID PROJ-1.11) for the
Proposal but will be included in the Security Plan if agreed for the Acquisition
the
Contract.
6.
The Security Plan shall identify:
a.
any related documents used for reference and provide links to them or copies of
under
the same where the Crown does not already have copies of such referenced
documents; and
b.
other plans or documents that explain the Security Plan in greater detail.
Defence Security Requirements
7.
The Contractor will be required to gain accreditation with NZDF under the Defence
Released
Industry Security Programme once a Contract is approved, or have equivalent accreditation
that is recognised by the NZDF. Information about the Defence Industry Security Programme
is available at www.nzdf.mil.nz/what-we-do/dss/security/disp-faq.htm
https://www.nzdf.mil.nz/nzdf/working-with-us/defence-industry-security-programme/.  The
Contractor shall explain in the Security Plan how this will be managed.
QUANTITY
8.
The Contractor shall provide one electronic copy.

P a g e  25 | 119

DID PROJ-1.6 – Monthly Progress Reports
REFERENCE NUMBER
TITLE:
DID PROJ-1.6
MONTHLY PROGRESS REPORTS
DESCRIPTION/PURPOSE:
The Monthly Progress Reports describe the means by which Project status is reported, and
potential problems are highlighted, to the Crown.
1982
ISSUE DATE:
Act
Final: Monthly (on a calendar month basis), within five Business Days of each month end,
commencing once the first full calendar month after Contract Execution Date has passed.
FORMAT
1.
The Monthly Progress Reports may be in the Contractor’s layout.
2.
The Monthly Progress Reports shall be written in English.
Information
3.
The Monthly Progress Reports shall be delivered in an electronic format capable of
being read, copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
4.
Each Monthly Progress Report shall include the following information at a minimum:
Official
a.
executive summary of the status of significant issues;
the
b.
updates to the project schedule showing actual progress against forecast
progress;
c.
a summary of significant work activities in the period from the last report to the
current report;
under
d.
a report on significant problems experienced and potential problems that may
arise that could affect cost, quality or schedule. The report shall include a
description of the problems, the impact on the Project to date, and the
Contractor’s proposed remedial actions;
e.
a summary of action items requiring either Contractor or Crown action;
Released
f.
Contract Change Proposals being prepared, submitted or received;
g.
requests for deviation submitted or responses received;
h.
status reporting on the development and delivery of the items to be delivered
under the Contract;
i.
status reporting on the New Zealand Industry Programme, where applicable;
j.
an update of the Project risk register detailing any changes in the status of
identified risks or any new risks; and

P a g e 26 | 119

k.
a description of forecast project activity for the next two months and anticipated
Crown commitment.
5.
The Monthly Progress Report shall reference the tasks and milestones in DID PROJ-
1.2 (Project Schedule).
6.
The Monthly Progress Report shall reference other agreed Contract Data Items as
required.
QUANTITY
7.
The Contractor shall provide one electronic copy each month.

1982
Act
Information
Official
the
under
Released

P a g e 27 | 119

DID PROJ-1.7 – Meetings and Reviews
Documentation
REFERENCE NUMBER
TITLE:
DID PROJ-1.7
MEETINGS AND REVIEWS DOCUMENTATION
DESCRIPTION/PURPOSE:
1982
The Meetings and Reviews Documentation describes the documents that will be provided
by the Contractor for all meetings and reviews held during the Project.
Act
ISSUE DATE:
Agenda: 10 Business Days prior to relevant Meeting or Review.
Minutes: Draft at five Business Days after the relevant Meeting or Review, Final at 10
Business Days after the relevant Meeting or Review.
Action Item Register: Updated five Business Days prior to the relevant Meeting or Review
and at other times, as requested by the Crown.
Information
FORMAT
1.
The Meetings and Reviews Documentation may be in the Contractor’s format.
2.
The Meetings and Reviews Documentation shall be written in English.
Official
3.
The Meetings and Reviews Documentation shall be delivered in an electronic format
capable of being edited, read, copied, searched and printed by the Crown using Microsoft
the
Word™.
CONTENT
4.
The Meetings and Reviews Documentation shall, as a minimum, include the
under
documentation listed below.
Agenda
5.
The Contractor shall, for each proposed meeting, conference or review, produce a
separate draft Agenda.
6.
The draft Agenda shall as, a minimum, include:
Released
a.
the purpose of the meeting/review;
b.
the date and time of the proposed meeting/review;
c.
the location of meeting/review;
d.
the proposed list of attendees – Contractor and Crown;
e.
the list of meeting/review topics, arranged in order of presentation;
f.
the requested input and participation by the Crown; and

P a g e 28 | 119

g.
the allotted time for each topic.
7.
Should the Crown require changes to the draft Agenda, the Contractor shall amend the
Agenda accordingly and reissue it to all parties as soon as reasonably practicable and in any
event at least one Business Day before the meeting.
Minutes
8.
The Contractor shall, for each proposed meeting, conference or review, produce
Minutes.
9.
The draft Minutes shall be produced for each meeting, conference or review within five
Business Days of the event, and provided to the Crown for agreement that they are a true
1982
and accurate record of the meeting, conference or review.
10.  The final Minutes shall be updated for each meeting, conference or review and passed
Act
to the Crown within 10 Business Days of the event.
11.  For Project meetings the Minutes shall, as a minimum, include:
a.
a copy of the agenda;
b.
a list of attendees;
c.
a summary of meeting topics;
Information
d.
a record of the discussions;
e.
a record of any decisions; and
f.
a record of Action Items with the party responsible and an agreed timeline for
resolution of such Action Items.
Official
12.  For technical reviews/conferences the Minutes shall, to the extent that it is applicable
to document the actual review, include:
the
a.
a copy of the agenda;
b.
a list of attendees;
under
c.
a description (Technical Review Item);
d.
source Material, including paper copies of presentation material;
e.
supporting handouts and reports;
f.
a record of Action Items and responsibilities; and
g.
individuals assigned responsibility for each Action Item with the associated
Released
resolution dates.
Action Item Register
13.  The Contractor shall maintain an Action Item Register to provide an ongoing register of
all Action Items from each meeting, conference or review. The Action Item Register shall, as
a minimum, include:
a.
a unique Action Item identification number and subject;
b.
an issue date and closure/target date for each Action Item;

P a g e  29 | 119

c.
a summary of action to perform; and
d.
the person responsible for completing the Action Item.
QUANTITY
14. The Contractor shall provide one electronic copy of each item.

1982
Act
Information
Official
the
under
Released

P a g e 30 | 119

DID PROJ-1.8 – Detailed Specification
REFERENCE NUMBER
TITLE:
DID PROJ-1.8
DETAILED SPECIFICATION
DESCRIPTION/PURPOSE:
The Detailed Specification describes the design, configuration, manufacturing and
performance requirements of the Contract Deliverables provided under the Acquisition 1982
Contract. The successful Respondent’s Detailed Specification, as updated during contract
negotiations, will subsequently form part of the Technical Specification in Annex B of the
Contract.
Act
The Technical Specification will consist of two parts. The agreed requirements from the
Statement of Requirements will become Part 1 of the Technical Specification at Annex B of
the Contract. The final, agreed, response to this DID will be Part 2 of the Technical
Specification at Annex B of the Contract.
ISSUE DATE:
Draft: Proposal.
Information
Final: During negotiation of the Acquisition Contract, to be converted into part of the
Contract Technical Specification prior to Contract Execution Date.
FORMAT
Official
1.
The Detailed Specification may be in the Contractor’s format.
2.
The Detailed Specification shall be written in English.
the
3.
The Detailed Specification shall be delivered in an electronic format capable of being
read, copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
under
4.
The Detailed Specification shall be a full detailed specification that describes each
Utility Vehicle variant as a whole (each, a ‘System’ – see Terms and Conditions) and
associated equipment, including Spares and Support and Test Equipment (S&TE), proposed
to be delivered under the Acquisition Contract; including:
a.
a technical description of the System; its systems and subsystems, including:
Released
(1)
the nomenclature of items to be used, including make, model and version
number;
(2)
the part number for all main supply items and significant materiel items; and
(3)
the software version loaded (if applicable);
b.
the performance characteristics and functionality of the System, its systems and
subsystems with specific cross-reference to the requirements that are defined in
the Statement of Requirements;

P a g e  31 | 119

c.
specifications, standards and manufacturing processes used to design and
produce the System, systems and subsystems;
d.
the design methods and reference standards or specifications used to design the
System, systems and subsystems; and
e.
software specifications for the System (if applicable).
System/Subsystem Performance
5.
The Detailed Specification shall describe the System’s performance in accordance
with the Statement of Requirements.
1982
QUANTITY
6.
The Contractor shall provide one electronic copy.

Act
Information
Official
the
under
Released

P a g e 32 | 119

DID PROJ-1.9 – Statement of Work (Acquisition
Contract)
REFERENCE NUMBER
TITLE:
DID PROJ-1.9
STATEMENT OF WORK (ACQUISTION CONTRACT)
DESCRIPTION/PURPOSE:
1982
The Statement of Work (Acquisition Contract) describes the work to be done in developing
or producing the Contract Deliverables. The successful Respondent’s Statement of Work
(Acquisition Contract) will be negotiated and converted into the Statement of Work that
Act
forms Annex A to the Contract.
ISSUE DATE:
Draft: Proposal.
Final: During negotiation of the Acquisition Contract, to be converted into the Contract
Statement of Work prior to the Contract Execution Date.
Information
FORMAT
1.
The Statement of Work (Acquisition Contract) may be in the Contractor’s format.
2.
The Statement of Work (Acquisition Contract) shall be written in English.
Official
3.
The Statement of Work (Acquisition Contract) shall be delivered in an electronic format
capable of being read, copied, searched and printed by the Crown using Microsoft Word™.
the
CONTENT
4.
The Statement of Work (Acquisition Contract) shall define (either directly or by
reference to other documents) all work (non-Specification) elements of contractor effort for
the Contract Deliverables (including, for the avoidance of doubt, all work the Contractor
under
subcontracts).
5.
For each task, the Contractor shall detail the following:
a.
the work to be performed under the Acquisition Contract, split into design,
prototype and test, production, test, delivery and support activities;
b.
the performance requirements for the work, stated in terms of desired results;
and
Released
c.
the locations of the activities and the organisation responsible for performing the
task.
6.
The following major activities shall be included, but the Statement of Work is not limited
to:
a.
a summary of the activities defined in the Systems Engineering Plan;

P a g e 33 | 119

b.
a summary of the programme of testing and verification, per the Master Test
Plan, including testing, analyses, and production of subsequent reports;
c.
a summary of the delivery of the Training Plan;
d.
stowage and loading trials;
e.
mobility and stability testing and demonstrations;
f.
activities to achieve homologation with the New Zealand Transport Agency
(NZTA);
g.
integration of the relevant C4I systems into all vehicles. Note for Respondents:
1982
This may be included in the C4I Integration Proposal (DID PROJ-1.11) for the
Proposal, but will be included in the Statement of Work if agreed for the
Acquisition Contract;
Act
h.
work to develop and validate the Roll Over Protection Structure requirements,
including for the UV-M General Service Troop Carrying modules; and
i.
delivery of the Safety Programme per the System Safety Plan defined in the
Systems Engineering Plan (DID ENG-2.1) with identification of the safety reviews
that occur with Crown participation.
7.
The tasks in the Statement of Work (Acquisition Contract) shall use the terminology
and unique identifiers for tasks that are used in the Contract Terms and Conditions, Project
Information
Schedule and any Contract Work Breakdown Structure.
QUANTITY
8.
The Contractor shall provide one electronic copy.

Official
the
under
Released

P a g e 34 | 119

DID PROJ-1.10 – Verification Cross Reference
Index
REFERENCE NUMBER
TITLE:
DID PROJ-1.10
VERIFICATION CROSS REFERENCE INDEX
DESCRIPTION/PURPOSE:
1982
The Verification Cross Reference Index describes how the Contractor will verify that each
element of the Technical Specification and Statement of Work has been fully met.
Act
ISSUE DATE:
Draft: at Shortlist / Negotiations.
Final: Contract Execution Date of Acquisition Contract.
FORMAT
1.
The Verification Cross Reference Index may be in the Contractor’s layout.
Information
2.
The Verification Cross Reference Index shall be written in English.
3.
The Verification Cross Reference Index shall be delivered in an editable electronic
format capable of being read, copied, searched and printed by the Crown using Microsoft
Excel ™.
Official
CONTENT
the
4.
The Verification Cross Reference Index shall indicate the intended method of
compliance for each element in the Technical Specification.
5.
The Verification Cross Reference Index shall describe the Method, the Location and
the Procedure for verifying each element.
under
6.
The definitions and abbreviations listed in the following sections shall be used.
VERIFICATION METHOD DEFINITIONS
7.
Analysis (A): Analysis shall be defined as the evaluation of data using analytical
techniques such as equations, formulas, statistics, charts, modelling or probability theory
and/or the review of information to verify that a specified requirement has been met. Analysis
is the review of 'Data' to confirm that a requirement has been achieved.  It does not involve
Released
the real equipment.
8.
Inspection (I): Inspection shall be defined as a visual verification that existing data,
components, equipment, systems and installations conform to the requirements
documentation to which they were produced. Inspections do not require components or
equipment to be operating.  Inspection is a simple activity that does not require a test
procedure or a detailed test report. The outcome may simply be written agreement that the
requirement has been achieved.  The VCRI method of 'Inspection' also covers
'Demonstration' in the Statement of Requirement / Part 1 of the Technical Specification.

P a g e  35 | 119

9.
Test (T): Test shall be defined as an instrumented or non-instrumented test of
components, equipment, or installations to verify that a specified requirement has been met.
Tests are defined physical activities that involve the actual equipment. Success is
determined by observing the real-time results of the test or by performing post-test data
reduction or data analysis. Tests scheduled to be undertaken during the Project shall be
described in the Project Schedule and the Master Test Plan and associated sub-DIDs. Tests
may also be further defined by the Test Plans and in some cases have Test Procedures.
Test Reports are required to document the verification outcomes.
10.  Equivalence (E): Equivalence shall be defined as evidence drawn from other
products/projects/programmes showing that equipment or Systems meet performance
requirements. Donor projects/programmes could be military or civilian and evidence could be
from external parties, including design recognition by other authorities.  Equivalence is a 1982
verification of ‘Data’. i.e. it does not involve any physical testing. The verification is
accomplished via written agreement that the design has been recognised as being
substantially similar to other designs that have been already qualified.
Act
10.11.  Certification (C). Certification shall be defined as the formal documentation
(Certificates) that attest the compliance against requirements. Certification may originate
from the Contractor, a sub-contractor, vendors or third-party regulatory authorities.
VERIFICATION LOCATION DEFINITIONS
11.12.  Data (D): Data verifications shall include those Inspections and Aanalyses that are
performed on documentation and data at any time other than ‘Design Review’.
Information
13.  Design Review (R): Design Review verifications shall include the proofs that are
furnished and agreed during formal Design Reviews to verify that the design will meet the
requirement. All Design Review verifications are a sub-set of the verifications of 'Data'.
Design Review is specifically identified as a subset location to aid the subsequent
development of the agendas for the design reviews.
Official
12.14.  Laboratory (L): Laboratory verifications shall include any testing that is not performed
on the complete System. Laboratory verifications shall include System Integration Facility
testing, Production Reliability Acceptance testing, Qualification testing (Hardware and
the
Software), BIT Assessment testing and Subsystem EMI testing.
13.  Design Review (R): Design Review verifications shall include the proofs that are
furnished and agreed during formal Design Reviews to verify that the design will meet the
requirement.
under
15.  System Testing (ST): System Testing verification shall include the activities that occur
on the complete System in locations such as proving grounds, test facilities, or during
Factory Acceptance Tests. The VCRI method of ‘System Testing’ also covers 'Trial' in the
Statement of Requirement / Part 1 of the Technical Specification.

Released
PROJECT PHASE
14.16.  The Contractor shall identify the appropriate phases of the Project where the
requirements are to be verified with reference to the activities in the Systems Engineering
Plan, Master Test Plan and Project Schedule.
15.17.  The Verification Cross Reference Index (VCRI) shal  have ‘Prototype’ and
‘Production’ columns. The Prototype column shal  define the verification applicable to the
‘first-of-type’ aspects, including for al  variants. The Production column shal  define the sub-
set of verification that is applicable to and therefore, repeated on, each unit of production.

P a g e  36 | 119

QUANTITY
16.18. The Contractor shall provide one electronic copy.

1982
Act
Information
Official
the
under
Released

P a g e 37 | 119

DID PROJ-1.11 – C4I Integration Proposal
REFERENCE NUMBER
TITLE:
DID PROJ-1.11
C4I INTEGRATION PROPOSAL
DESCRIPTION/PURPOSE:
The C4I Integration Proposal describes the offer that the Respondent makes for the
integration of Command, Control, Communications, Computing and Intelligence (C4I)  1982
systems into the Utility Vehicles.
ISSUE DATE:
Act
Draft: Not Applicable
Final: Proposal.
FORMAT
1.
The C4I Integration Proposal shall be in the Contractor’s layout.
Information
2.
The C4I Integration Proposal shall be written in English.
3.
The C4I Integration Proposal shall be delivered in an editable electronic format
capable of being read, copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The C4I Integration Proposal shall describe the approach that the Respondent
proposes for the procurement, design, prototyping, testing, production and installation
the
(col ectively the ‘C4I scope’) of the C4I systems in all variants of Utility Vehicles.
5.
The C4I Integration Proposal shall be a response to, and be based upon, the
information and concepts outlined in the ‘C4I Integration Information’ at RFP Part 2,
Enclosure 4.
under
6.
The C4I Integration Proposal shall be consistent with all other elements of the
Proposal. If any aspect of the C4I Integration Proposal invalidates any other aspect of the
Proposal then the difference shall be clearly described in the C4I Integration Proposal.
7.
The C4I Integration Proposal shall include (without limitation):
a.
the identities and C4I experience of the Contractor and its proposed
Released
Subcontractors (including Suppliers);
b.
the roles proposed for the Contractor and its Subcontractors (including
Suppliers), the Crown and L-3 Harris to deliver the C4I scope;
c.
Controlled Cryptographic Item (CCI) handling and storage arrangements,
including where and when CCI will be required and an indication of whether the
Contractor’s government is likely to support CCI transfers to national
Communications Security (COMSEC) accounts (per requirements at DID PROJ-
1.5 Security Plan);

P a g e  38 | 119

d.
the design process for C4I Integration including Design Reviews and test facilities
(per requirements at DID ECP-2.1 Systems Engineering Plan);
e.
the locations for all design and prototype and testing activities for the for C4I
Integration, including TEMPEST testing;
f.
the high-level schedule that synchronises with milestones in the Project Schedule
(DID PROJ-1.2);
g.
the design practices and/or specifications that will be employed to minimise risks
of Electro Magnetic Interference (EMI), TEMPEST, co-site interference, radiation
hazards, antenna shadowing and adverse effects to radio performance. This may
include the information on the vehicle’s existing EMI characteristics, design  1982
specifications to be used, antenna locations and separation, description of
shielding, cable specifications, bulkhead penetrations and physical separation of
cables;
Act
h.
the design approach proposed to ensure that the human – machine interface
factors are considered, including viewing angles of displays, obscuration of other
vehicle equipment or external visibility, reach, lighting and audibility of speakers;
i.
information that is required to be provided by the Crown and/or L-3-Harris;
j.
any perceived export control restrictions (e.g., International Traffic in Arms
Regulations (ITAR)) that wil  apply to the Respondent’s C4I Integration Proposal;
Information
k.
confirmation of the Government Furnished Materiel (GFM) to be provided by the
Crown pertaining to the C4I Integration (refer RFP Part Two, Enclosure 4 for a
the potential GFM that has been identified but this may not be the full list of GFM
that is required);
l.
the suggested sequencing of the L-3 Harris ‘Platform Site Survey’ (refer RFP Part
Official
Two, Enclosure 4) into the design process;
m.
an outline of proposed prototype installations (e.g. antenna locations) and testing
the
(including Radio Frequency co-site surveys);
n.
the processes and controls to assure and document the outcomes for safety
aspects of the C4I Integration  (including Radiation Hazards and equipment
restraint in the vehicles);
under
o.
the production installation activities and sequencing for the “fitted for but not with”
installations;
p.
a description of suggested Contractor furnished equipment (e.g., the mount for
the EUD / docking station, radio frequency, data and power cables, mounting
hardware and mounting provisions in the vehicle, cable connectors and back
shells and some couplers, filters and splitters); and
Released
q.
what obligations the Respondent is not prepared to assume under the Contract,
for the outcomes of the integrated performance of the Utility Vehicles and the C4I
systems.
QUANTITY
8.
The Contractor shall provide one electronic copy.

P a g e  39 | 119

1982
Act
Information
Section 2 – Engineering Control Plans

Official
the
under
Released

P a g e 40 | 119

DID ECP-2.1 – Systems Engineering Plan
REFERENCE NUMBER
TITLE:
DID ECP-2.1
SYSTEMS ENGINEERING PLAN
DESCRIPTION/PURPOSE:
The Systems Engineering Plan shall provide details of the Contractor’s (including sub-
contractors) design organisation and approach to engineering integration and coordination
1982
throughout the Project.
ISSUE DATE:
Act
Draft: Shortlist / Negotiations’Proposal.
Final: Contract Execution Date of Acquisition Contract.
FORMAT
1.
The Systems Engineering Plan may be in the Contractor’s layout.
Information
2.
The Systems Engineering Plan shall be written in English.
3.
The Systems Engineering Plan shall be delivered in an electronic format capable of
being read, copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The Systems Engineering Plan shall describe the Contractor’s organisational structure
that is offered to promote a systems approach to the engineering effort for the Utility Vehicles
the
and associated deliverables (e.g., training devices, if any).
5.
The Systems Engineering Plan shall include the following three elements:
a.
Contractor Design Organisation, which shall include:
under
(1)
details of the responsibilities and authorities of key officials in the
organisation;
(2)
lines of authority;
(3)
name of Chief Designer, or person fulfilling the duties and responsibilities of
Chief Designer, including approving the exit from reviews;
Released
(4)
linkages between the Contractor’s design organisation and the design
organisations of subcontractors (including suppliers);
(5)
accreditations or other approvals of Design Authority granted by other
sources or government agencies; and
(6)
the level of prior experience within the Contractor’s organisation in the
application of the proposed framework.
b.
Contractor Design Management System, which shall include:

P a g e 41 | 119

(1)
description of the systems engineering framework to be used by the
Contractor, with reference to any internationally recognised standard(s);
(2)
description of the approach that will be used for technical programme
planning and control for the Utility Vehicles, including:
(a)
Design, Build and Acceptance (Test) Reviews (including for each
variant as applicable) and the control and Contractor sign-off
procedures and the proposed degree of Crown participation. Entry
criteria and exit criteria for each Design, Build and Acceptance
Review are also to be stated.
(b)
Description of all Systems Engineering activities that are required to
1982
adapt existing Utility Vehicle designs to meet the Contract
requirements. This is to include, but is not limited to:
Act
i.
integration of Command, Control, Communications, Computers
and Intelligence (C4I) systems;
ii.
Roll Over Protection Structures including the removable Troop
Carrying modules on the UV-M General Service variant;
iii.
modifications for Right Hand Drive (if any); and
iv.
modifications to the Cab Chassis of the vehicles (if any);
Information
(3)
mechanisms and procedures to manage and control the integration of
specialist design/engineering activities;
(4)
interface control procedures between the differing work areas (particularly
associated with any sub-contractors);
Official
(5)
Systems safety planning. Describe the Contractor’s plans to identify,
evaluate and manage system safety hazards and their associated risks
throughout the system life cycle. The Contractor shall develop the System
the
Safety Programme Plan in accordance with MIL-STD-882E Task 102 or
any equivalent approved by the Crown;
(6)
procedures for the management and control of design documentation and
technical data items (including any proprietary data);
under
(7)
internal design validation and verification review mechanisms such as peer
review, walk-throughs and design sign-off procedures;
(8)
Technical Audits (including Functional Configuration Audits and Physical
Configuration Audits). Refer Contract clause 16;
(9)
any external (independent) technical and quality reviews and audits;
Released
(10)  procedures and plans for design certification, with reference to the Master
Test Plan (DID TEST-4.1), as appropriate; and
(11)  production, manufacturing and process control mechanisms.
c.
Design Resource Management, which shall include:
(1)
description of the specialist engineering personnel who will be involved;

P a g e  42 | 119

(2)
description of the records such as technical data libraries and any software
development libraries that will maintained after delivery and/or transferred
to the Crown;
(3)
description of any integration tools such as test and evaluation laboratories,
equipment, rigs, hot mock-ups and computer simulations;
(4)
description of any computer-based design and management tools; and
(5)
description of the computer software support environments for any safety or
mission critical software, including compilers, linkers, assemblers, editors,
debuggers and other support tools.
1982
QUANTITY
6.
The Contractor shall provide one electronic copy.

Act
Information
Official
the
under
Released

P a g e 43 | 119

DID ECP-2.2 – Configuration Management Plan
REFERENCE NUMBER
TITLE:
DID ECP-2.2
CONFIGURATION MANAGEMENT PLAN
DESCRIPTION/PURPOSE:
The Contractor shall provide a Configuration Management Plan that details the processes
that shall be used to maintain configuration control of each variant of the Utility Vehicle (UV).
1982
ISSUE DATE:
Act
Draft: at Shortlist / Negotiations.
Final: Contract Execution Date of Acquisition Contract.
FORMAT
1.
The Configuration Management Plan may be in the Contractor’s layout.
2.
The Configuration Management Plan shall be written in English.
Information
3.
The Configuration Management Plan shall be delivered in an electronic format capable
of being read, copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The Configuration Management Plan shall identify the processes the Contractor will
undertake maintain control of the configuration of deliverables, including
equipment/hardware, software, firmware and Contract Data items.
the
5.
The Configuration Management Plan shall reference the requirements of clause 15.2
of the Contract.
6.
The Configuration Management Plan shall describe:
under
a.
how the Contractor’s configuration management programme is organised,
including configuration management responsibilities;
b.
the methods, procedures and controls that will be used to assure effective
configuration identification, change control, status accounting and audits of
configuration (including Technical Audits referred to in clause 16 of the Contract);
and
Released
c.
how and when configuration management responsibilities and records will be
transferred to the Crown.
7.
The following DIDs are also relevant to configuration control and the Configuration
Management Plan shall define the management processes to ensure that these Contract
Data Items will be maintained as part of the configuration baseline:
a.
Engineering Drawing Index (DID ENG-3.1);
b.
Engineering Drawing Package (DID ENG-3.2);

P a g e 44 | 119

c.
Circuit diagrams (DID ENG-3.3);
d.
Equipment Layout Diagrams (DID ENG-3.4);
e.
Communication System Schematic (DID ENG-3.5);
f.
Complete Equipment Schedule Illustrations (DID ENG-3.6); and
g.
Configuration Records (DID ENG-3.7).
QUANTITY
8.
The Contractor shall provide one electronic copy.

1982
Act
Information
Official
the
under
Released

P a g e 45 | 119

DID ECP-2.3 – Electromagnetic Environmental
Effects Control Plan
REFERENCE NUMBER
TITLE:
DID ECP-2.3
ELECTROMAGNETIC ENVIRONMENTAL EFFECTS
CONTROL PLAN
DESCRIPTION/PURPOSE:
1982
The Electromagnetic Environmental Effects Control Plan shall describe how the Contractor
will control Electromagnetic Environmental Effects (EEE) on each variant of the Utility
Vehicle (UV).
Act
ISSUE DATE:
Draft: Example at Proposal.
Final: Contract Execution Date of Acquisition Contract.
FORMAT
Information
1.
The Electromagnetic Environmental Effects Control Plan may be in the Contractor’s
layout.
2.
The Electromagnetic Environmental Effects Control Plan shall be written in English.
3.
The Electromagnetic Environmental Effects Control Plan shall be delivered in an
Official
electronic format capable of being read, copied, searched and printed by the Crown using
Microsoft Word™.
the
CONTENT
4.
The Electromagnetic Environmental Effects Control Plan shall describe how the
Contractor will control Electromagnetic Environmental Effects, including:
under
a.
Electromagnetic Interference (EMI);
b.
Electromagnetic Compatibility (EMC);
c.
Electromagnetic Vulnerability (EMV);
d.
Hazard of Electromagnetic Radiation to Ordnance (HERO);
e.
Hazard of Electromagnetic Radiation to Personnel (HERP);
Released
f.
Hazard of Electromagnetic Radiation to Fuels (HERF);
g.
Lightning;
h.
Precipitation Static; and
i.
Electrostatic Discharge.
5.
The Electromagnetic Environmental Effects Control Plan shall include:

P a g e 46 | 119

a.
a list of standards and specifications that the Contractor will use during the
design and installation of equipment;
b.
test methods for validation of EEE control measures; and
c.
the management process(es) the Contractor will use to ensure that the installed
equipment satisfies the EEE requirements specified.
QUANTITY
6.
The Contractor shall provide one electronic copy.

1982
Act
Information
Official
the
under
Released

P a g e 47 | 119

DID ECP-2.4 – TEMPEST Control Plan
REFERENCE NUMBER
TITLE:
DID ECP-2.4
TEMPEST CONTROL PLAN
DESCRIPTION/PURPOSE:
The TEMPEST Control Plan describes how the Contractor will provide and install equipment
into the Command and Control Variants of the Utility Vehicle (UV) to satisfy the TEMPEST
1982
requirements defined in the Contract.
ISSUE DATE:
Act
Draft: Contract Negotiation.
Final: Contract Execution Date of Acquisition Contract.
FORMAT
1.
The TEMPEST Control Plan may be in the Contractor’s layout.
Information
2.
The TEMPEST Control Plan shall be written in English.
3.
The TEMPEST Control Plan shall be delivered in an electronic format capable of being
read, copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The TEMPEST Control Plan shall describe how the Contractor will design, provide and
install equipment so that the UV will satisfy the TEMPEST requirements of the Statement of
the
Requirements. The TEMPEST requirements pertain to all subsystems including, Command,
Control, Communications, Computers and Intelligence (C4I) systems installed in the Utility
Vehicles.
5.
The TEMPEST design requirements are defined in Requirement 1.1.2-05 in the
under
Statement of Requirements.  These design requirements are in accordance with CNSSAM
TEMPEST/01-13 (U) “RED/BLACK Instal ation Guidance” (available from
https://cryptome.org/2014/10/cnssam-tempest-1-13.pdf ) and as modified by the NZ
Addendum to US CNSSAM TEMPEST/01-13 which is provided as reference information per
the listing at Serial #46 at Annex G to the Statement of Requirements.
6.
The TEMPEST Control Plan shall describe the installation standard(s) and procedures
that the Contractor will use during the design and installation of equipment into the UV
Released
Command and Control variants to ensure compliance with the TEMPEST design
requirements.
QUANTITY
7.
The Contractor shall provide one electronic copy.

P a g e  48 | 119

1982
Act
Information
Section 3 – Engineering Data

Official
the
under
Released

P a g e 49 | 119

DID ENG-3.1 – Engineering Drawing Index
REFERENCE NUMBER
TITLE:
DID ENG-3.1
ENGINEERING DRAWING INDEX
DESCRIPTION/PURPOSE:
The Contractor shall provide an Engineering Drawing Index that shows the hierarchical
structure and groupings of engineering drawings associated with the Utility Vehicle (UV).
1982
ISSUE DATE:
Act
Draft: Example at Proposal.
Final: Two months after Final Design Review of each variant.
FORMAT
1.
The Engineering Drawing Index data may be in the Contractor’s layout.
2.
The Engineering Drawing Index data shall be written in English.
Information
3.
The Engineering Drawing Index data shall be delivered in an electronic format capable
of being read, copied, searched and printed by the Crown using Adobe Acrobat™ or
Microsoft Office™ .
CONTENT
Official
4.
An Engineering Drawing Index presents the hierarchical structure and interdependence
of the engineering drawings associated with the work carried out by the Contractor
the
during the period of the Contract. The requirement is to provide the Crown with a
structured list of all drawings associated with UV, including those associated with each
variant, installation of equipment, and production of support facilities and equipment.
5.
The Contractor shall provide an Engineering Drawing Index that identifies all drawings
under
by name and number. The Engineering Drawing Index shall be updated with the
current Revision state of each drawing.
QUANTITY
6.
The Contractor shall provide one electronic copy of the Draft (Example).
6.7.  The Contractor shall provide one electronic copy as a complete Final set on CD with
Released
licence rights to produce unlimited hard copies and store electronic copies on NZDF and
support contractor information technology equipment, including mobile devices with
distributed access via servers.

P a g e  50 | 119

DID ENG-3.2 – Engineering Drawing Package
REFERENCE NUMBER
TITLE:
DID ENG-3.2
ENGINEERING DRAWING PACKAGE
DESCRIPTION/PURPOSE:
The Engineering Drawing Package (EDP) describes the technical information the Contractor
shall provide in order for the Crown to support the in-service management of the Utility 1982
Vehicle (UV).
ISSUE DATE:
Act
Draft: Example of Drawings at Proposal and confirmation of whether 3D dataset and/or
manufacturing drawings will be provided.
Final: For each variant, two months prior to first vehicle of that variant delivery in New
Zealand.
FORMAT
Information
1.
The EDP may be in the Contractor’s layout.
2.
The EDP shall be written in English.
3.
The EDP shall be delivered in an electronic format capable of being read, copied,
searched and printed by the Crown using any of the formats listed below.
Official
CONTENT
the
4.
The Contractor shall deliver an EDP for each UV variant, training aid, specialist tool
and test equipment. The EDP shall include approved design, test and production
descriptions and documentation sufficient to technically define the elements to permit
maintenance, and procurement of component parts without further need for research or
development.
under
5.
The contents of the EDP shall include Level 3 drawings to include the following:
a.
detailed drawings;
b.
assembly drawings and parts lists; and
c.
exploded assembly drawings that are used in the Illustrated Parts Catalogues.
Released
6.
The Contractor shall compile the elements of the EDP electronically in any of the
following formats:
a.
Drawing formats, in order of preference:
(1)
AutoDesk Inventor .IDW
(2)
AutoDesk Inventor .DWG
(3)
AutoCaD .DWG

P a g e  51 | 119

b.
Parts Lists: Microsoft Excel format.
7.
As part of the design reviews, the Contractor shall deliver to the Crown a draft
summary level EDP of the relevant vehicle systems to assist in compliance evaluation.
8.
The Contractor may deliver an EDP sufficient to technically define the elements to
permit the manufacture of components without further need for research or
development together with the rights for the Crown to use this information in
accordance with clause 31.2 of the Contract.
9.
The Contractor may provide a 3D dataset of drawings. A 3D dataset is only a
deliverable where it exists and is easily provided within the Contract Price. If providing
a 3D dataset, the preferred format is STEP/STP.
1982
QUANTITY
Act
10.  The Contractor shall provide one electronic copy of the Draft (Example).
10.11.  The Contractor shall provide one electronic copy as a complete Final set on CD with
licence rights to produce unlimited hard copies and store electronic copies on NZDF and
support contractor information technology equipment, including mobile devices with
distributed access via servers.

Information
Official
the
under
Released

P a g e  52 | 119

DID ENG-3.3 – Circuit Diagrams
REFERENCE NUMBER
TITLE:
DID ENG-3.3
CIRCUIT DIAGRAMS (ELECTRICAL, HYDRAULIC &
PNEUMATIC)
DESCRIPTION/PURPOSE:
The Contractor shall provide circuit diagrams for each variant of the Utility Vehicle (UV).
1982
ISSUE DATE:
Act
Draft: Example at Proposal.
Final: For each variant, two months after Final Design Review of that variant.
FORMAT
1.
The Electrical, Hydraulic & Pneumatic Circuit Diagrams may be in the Contractor’s
layout.
Information
2.
The Electrical, Hydraulic & Pneumatic Circuit Diagrams shall be written in English.
3.
The Electrical, Hydraulic & Pneumatic Circuit Diagrams shall be delivered in an
electronic format capable of being read, copied, searched and printed by the Crown
using any of the formats listed below.
Official
CONTENT
4.
The Contractor shall provide electrical, hydraulic and pneumatic circuit diagrams for
the
each UV variant that reflects all equipment installed under the Contract.
5.
The Contractor shall deliver drawings to the Crown in the following formats, in order of
preference:
a.
AutoCaD .DWG, or
under
b.
AutoDesk Inventor .DWG
6.
The Contractor shall produce all drawings in metric measurement format (Contract
clause 44.12 refers).
QUANTITY
Released
7.
The Contractor shall provide one electronic copy of the Draft (Example).
7.8.  The Contractor shall provide one electronic copy as a complete Final set on CD with
licence rights to produce unlimited hard copies and store electronic copies on NZDF
and support contractor information technology equipment, including mobile devices
with distributed access via servers.

P a g e  53 | 119

DID ENG-3.4 – Equipment Layout Diagrams
REFERENCE NUMBER
TITLE:
DID ENG-3.4
EQUIPMENT LAYOUT DIAGRAMS
DESCRIPTION/PURPOSE:
The Contractor shall provide diagrams detailing the layout of equipment within the Utility
Vehicle (UV).
1982
ISSUE DATE:
Act
Draft: Example at Proposal.
Final: For each variant, two months prior to first vehicle of that variant delivery in New
Zealand.
FORMAT
1.
The Equipment Layout Drawings may be in the Contractor’s layout.
Information
2.
The Equipment Layout Drawings shall be written in English.
3.
The Equipment Layout Drawings shall be delivered in an electronic format capable of
being read, copied, searched and printed by the Crown using any of the formats listed
below.
Official
CONTENT
4.
The Contractor shall provide diagrams to detail the layout of all stowed equipment
the
within each UV variant. The diagrams may include tables of contents for stowage
locations and photographs.
5.
The Contractor shall deliver drawings to the Crown in the following formats, in order or
preference:  under
a.
AutoCaD .DWG
b.
AutoDesk inventor  .DWG, or
c.
High resolution (3 MB) raster images, in any of the below file types:
(1)
Portable Network Graphic .PNG
Released
(2)
Joint Photographic experts Group .JPG
(3)
Portable Document Format . PDF, either standard or layered.
QUANTITY
6.
The Contractor shall provide one electronic copy of the Draft (Example).
6.7.  The Contractor shall provide one electronic copy as a complete Final set on CD with
licence rights to produce unlimited hard copies and store electronic copies on NZDF and

P a g e  54 | 119

support contractor information technology equipment, including mobile devices with
distributed access via servers.

1982
Act
Information
Official
the
under
Released

P a g e 55 | 119

DID ENG-3.5 – Communications System
Schematic
REFERENCE NUMBER
TITLE:
DID ENG 3.5
COMMUNICATIONS SYSTEM SCHEMATIC
DESCRIPTION/PURPOSE:
1982
The Contractor shall provide a vehicle Communications System Schematic outlining the
architecture of the communication and data systems for each variant of the Utility Vehicle
(UV).
Act
ISSUE DATE:
Draft: Example at Proposal.
Final: For each variant, two months after Final Design Review of that variant.
FORMAT
Information
1.
The Communications System Schematic may be in the Contractor’s layout.
2.
The Communications System Schematic shall be written in English.
3.
The Communications System Schematic shall be delivered in an electronic format
capable of being read, copied, searched and printed by the Crown using Adobe
Official
Acrobat™.
CONTENT
the
4.
The Communications System Schematic shall provide the Crown with schematic
diagrams of the Contractor’s proposed communication system for each variant of the
UV. The schematics shall depict the system layouts in each variant. This includes the
intended location of all communications equipment (e.g., radios) and all connected
under
items (e.g., antennas, End User Devices, etc.).
5.
Communications System Schematics shall be in either of the following formats, in order
of preference:
a.
AutoCaD .DWG
b.
AutoDesk inventor .DWG
Released
QUANTITY
6.
The Contractor shall provide one electronic copy of the Draft (Example).
6.7.  The Contractor shall provide one electronic copy as a complete Final set on CD with
licence rights to produce unlimited hard copies and store electronic copies on NZDF and
support contractor information technology equipment, including mobile devices, with
distributed access via servers.

P a g e  56 | 119

DID ENG-3.6 – Complete Equipment Schedule
Illustrations
REFERENCE NUMBER
TITLE:
DID ENG-3.6
COMPLETE EQUIPMENT SCHEDULE ILLUSTRATIONS
DESCRIPTION/PURPOSE:
1982
The Contractor shall provide Complete Equipment Schedules (CES) Illustrations in support
of the UV.
Act
ISSUE DATE:
Draft: Two months after confirmation of CES (via Provisioning Conference).
Final: For each variant, two months prior to first vehicle of that variant delivery in New
Zealand.
FORMAT
Information
1.
The CES Illustrations may be in the Contractor’s layout.
2.
The CES Illustrations shall be written in English.
3.
The CES Illustrations shall be delivered in an electronic format capable of being read,
copied, searched and printed by the Crown using Adobe Acrobat™ and/or Microsoft
Official
Office™.
CONTENT
the
4.
The Contractor shall provide the necessary illustrations and descriptions of Contractor
supplied items to enable the Crown to complete its Complete Equipment Schedules.
The Complete Equipment Schedules illustrations need to provide sufficient detail to
allow operators, support and maintenance personnel to identify Basic Issue Items and
under
components used on all variants.
5.
CES Illustrations shall be delivered in any of the following formats, High Resolution
(3MB) Raster images or any of the below file types:
a.
Portable Network Graphic .PNG
b.
Joint Photographic experts Group .JPG
Released
c.
Portable Document Format . PDF, either standard or layered.
QUANTITY
6.
The Contractor shall provide one electronic copy as a complete set on CD with licence
rights to produce unlimited hard copies and store electronic copies on NZDF and
support contractor information technology equipment, including mobile devices, with
distributed access via servers.

P a g e  57 | 119

DID ENG-3.7 – Configuration Records
REFERENCE NUMBER
TITLE:
DID ENG-3.7
CONFIGURATION RECORDS
DESCRIPTION/PURPOSE:
The Contractor shall provide Configuration Records for the Utility Vehicle (UV).
1982
ISSUE DATE:
Act
Draft: Example at Proposal.
Final: For each vehicle, one month before delivery of vehicle.
FORMAT
1.
The Configuration Records may be in the Contractor’s layout.
2.
The Configuration Records shall be written in English.
Information
3.
The Configuration Records shall be delivered in an electronic format capable of being
read, copied, searched and printed by the Crown using Microsoft Excel™ or Microsoft
Word™.
CONTENT
Official
4.
The Configuration Records shall identify and record the serial numbers of serialised
equipment installed on each UV. The Configuration Records shall also record any
the
manufacturing concessions, deviations or waivers relating to that equipment or to its
installation in each UV.
QUANTITY
5.
The Contractor shall provide one electronic copy of the Draft (Example).
under
5.6. The Contractor shall provide one electronic copy as a complete Final set on CD with
licence rights to produce unlimited hard copies and store electronic copies on NZDF and
support contractor information technology equipment, including mobile devices, with
distributed access via servers.

Released

P a g e 58 | 119

DID ENG-3.8 – Antenna Compatibility Analysis
REFERENCE NUMBER
TITLE:
DID ENG-3.8
ANTENNA COMPATIBILITY ANALYSIS
DESCRIPTION/PURPOSE:
The Antenna Compatibility Analysis demonstrates Antenna compatibility and interference
modelling particular for each variant of the Utility Vehicle (UV).
1982
ISSUE DATE:
Act
Draft: Example at Proposal.
Final: For each variant, two months after Final Design Review of that variant.
FORMAT
1.
The Antenna Compatibility Analysis may be in the Contractor’s layout.
2.
The Antenna Compatibility Analysis shall be written in English.
Information
3.
The Antenna Compatibility Analysis shall be delivered in an electronic format capable
of being read, copied, searched and printed by the Crown using Microsoft Word™ or
Adobe Acrobat™.
CONTENT
Official
4.
The Antenna Compatibility Analysis shall demonstrate that the antenna layout has
been optimised to minimise interference on or degradation of UV systems.
the
5.
The Contractor shall provide an Antenna Compatibility Analysis for each variant of the
UV.
QUANTITY
under
6.
The Contractor shall provide one electronic copy of the Antenna Compatibility Analysis.

Released

P a g e 59 | 119

DID ENG-3.9 – Failure Mode, Effects and
Criticality Analysis
REFERENCE NUMBER
TITLE:
DID ENG-3.9
FAILURE MODE, EFFECTS AND CRITICALITY ANALYSIS
DESCRIPTION/PURPOSE:
1982
The Failure Mode, Effects and Criticality Analysis (FMECA) will outline potential failure
mechanisms associated with the Utility Vehicle (UV).
Act
ISSUE DATE:
Draft: Example at Proposal.
Final: Three months after Final Design Review of the last variant.
FORMAT
1.
The FMECA report may be in the Contractor’s layout.
Information
2.
The FMECA report shall be completed by subsystem.
3.
The FMECA report shall be written in English.
4.
The FMECA report shall be delivered in an electronic format capable of being read,
Official
copied, searched and printed by the Crown using Microsoft Word™ or Adobe
Acrobat™.
the
CONTENT
5.
The FMECA is only a deliverable where such data already exists or is easily collated.
6.
The FMECA shall identify potential failure mechanisms associated with a systems
under
design and architecture, and the effects and consequences on system reliability.
7.
The analyses shall go down to the lowest level of indenture for which original
equipment manufacturer (OEM) reliability data and failure information is available. For
all developmental items the analyses shall go down to the component level. Where the
Contractor has identified specific equipment, the analyses shall follow the hardware
approach, otherwise the functional approach can be adopted.
8.
The Contractor shall carry out a Failure Mode Effects and Criticality Analysis at the
Released
System level to identify the following:
a.
system weaknesses;
b.
potential failure mechanisms and causes;
c.
effects and consequences of failures on system reliability; and
d.
safety critical components with a single point of failure and steps that have been
taken to mitigate the risk.

P a g e 60 | 119

QUANTITY
9.
The Contractor shall provide one electronic copy of the FMECA.

1982
Act
Information
Official
the
under
Released

P a g e 61 | 119

DID ENG-3.10 – Weight, Balance and Stability
Analysis
REFERENCE NUMBER
TITLE:
DID ENG-3.10
WEIGHT, BALANCE AND STABILITY ANALYSIS
DESCRIPTION/PURPOSE:
1982
The Weight, Balance and Stability Analysis shall provide information on the centre of gravity
and the impact of installation and removal of equipment from the Utility Vehicle (UV).
Act
ISSUE DATE:
Draft: Example at Proposal.
Final: For each variant, three months after the Final Design Review for that variant.
FORMAT
1.
The Weight, Balance and Stability Analysis may be in the Contractor’s layout.
Information
2.
The Weight, Balance and Stability Analysis shall be written in English.
3.
The Weight, Balance and Stability Analysis shall be delivered in an electronic format
capable of being read, copied, searched and printed by the Crown using Microsoft
Word™.
Official
CONTENT
the
4.
The Contractor shall provide the Weight, Balance and Stability Analysis to define the
centre of gravity, the distribution of weight across axles and to define the impact that
the installation or removal of equipment will have on the weight, balance and stability of
each UV variant.
under
QUANTITY
5.
The Contractor shall provide one electronic copy of the Weight, Balance and Stability
Analysis report.

Released

P a g e 62 | 119

DID ENG-3.11 – Safety Assessment Report
REFERENCE NUMBER
TITLE:
DID ENG-3.11
SAFETY ASSESSMENT REPORT
DESCRIPTION/PURPOSE:
The Contractor shall provide a Safety Assessment Report for the Utility Vehicle (UV). 1982
ISSUE DATE:
Act
Draft: Example at Proposal. Draft 2 months before first of each variant delivery.
Final: Three months after Final Design Review of the last variant.
FORMAT
1.
The Safety Assessment Report for UV may be in the Contractor’s layout.
2.
The Safety Assessment Report for UV shall be written in English.
Information
3.
The Safety Assessment Report for UV shall be delivered in an electronic format
capable of being read, copied, searched and printed by the Crown using Adobe
Acrobat™ or Microsoft Word™.
CONTENT
Official
4.
The Contractor shall provide the Safety Assessment Report (including Hazard Log),
pursuant to the Safety Plan (as defined in the Systems Engineering Plan at DID ENG-
the
2.1) and in accordance with the requirements of MIL-STD-882E, Task 301 or any
equivalent approved by the Crown.
5.
The Safety Assessment Report shall cover all Contract deliverables.
QUANTITY
under
6.
The Contractor shall provide one electronic copy.

Released

P a g e 63 | 119

1982
Act
Information
Section 4 – Test and Evaluation

Official
the
under
Released

P a g e 64 | 119

DID TEST-4.1 – Master Test Plan
REFERENCE NUMBER
TITLE:
DID TEST-4.1
MASTER TEST PLAN
DESCRIPTION/PURPOSE:
The Master Test Plan shall define the structure and content of testing that the Contractor
and Subcontractors (including Suppliers), have performed or will perform on the Utility  1982
Vehicle (UV) to satisfy verification requirements during the performance of the Contract.
ISSUE DATE:
Act
Draft: at Shortlist / Negotiations.
Final: Contract Execution Date of Acquisition Contract.
FORMAT
1.
The Master Test Plan may be in the Contractor’s layout.
Information
2.
The Master Test Plan shall be written in English.
3.
The Master Test Plan shall be delivered in an electronic format capable of being read,
copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The Master Test Plan shall describe the holistic approach to the entire programme of
testing.
the
5.
The Master Test Plan shall define the content and schedule of testing that the
Contractor and its Subcontractors (including Suppliers) have conducted, or will
conduct.
under
6.
The Master Test Plan shall include reference to (without limitation):
a.
test activities defined in the Project Schedule (DID PROJ-1.2);
b.
the programme of test activities (annotated ‘T’) that are defined in the Verification
Cross Reference Index (VCRI) delivered in accordance with DID PROJ-1.10;
c.
the Electrical Load Test Plan delivered in accordance with DID TEST-4.4;
Released
d.
the Electromagnetic Environmental Effects Test Plan delivered in accordance
with DID TEST-4.5;
e.
tests of the integrated C4I systems;
f.
any Roll Over Protection Structure (ROPS) tests;
g.
any antenna compatibility tests;
h.
any mobility, stability, ride quality and towing tests;

P a g e  65 | 119

i.
any vehicle signature testing (thermal, visual, acoustic, electronic);
j.
testing of fuel and battery capacities;
k.
any environmental or climate tests;
l.
any anthropometric/ergonomic/internal illumination tests; and
m.
Factory Acceptance Tests.
7.
The Master Test Plan shall:
a.
identify the hierarchy, order and interdependence (including pre-requisites) of all
1982
testing that the Contractor, and its Subcontractors, will perform during the
Contract; and
Act
b.
describe the process for the Contractor to update the VCRI and provide a cross-
reference between each series of tests and the corresponding Contract
requirements. The cross-reference shall identify the components that contribute
to satisfying the Contract requirements.
8.
The Master Test Plan shall be broadly structured as follows:
a.
Table of Contents.
b.
Applicable Documents and References.
Information
c.
Introduction.
d.
Brief system descriptions for the Contract Deliverables that are subject to testing.
e.
Test Programme Summary. Description of the conduct of the integrated Test
Official
Programme, including milestones at which the Contractor and the Crown will
review the test programme and the Contractor’s procedures for coordinating the
programme with other Systems Engineering activities. The summary shall outline
the
the requirements for, and interrelationship between, all prototype, production and
Crown acceptance plans.
f.
Prototype Testing. An overview of the one-off tests that will be conducted to verify
the unique design aspects of the prototype(s) (first-of-type) for the Contract
under
requirements. Note that the VCRI shal  include a ‘Prototype’ column which will
identify the applicable specifications that will be verified via prototype testing.
Prototype testing that is first of type is likely to include C4I integration and any
testing for Roll Over Protection but may be applicable for any unique
requirements of the Contract. The overview shall describe how the programme of
prototype testing meshes with any previous validation (existing test results) that is
proposed for use as a baseline for the Utility Vehicles. The overview shall also
identify any prototype test activities that are planned to be performed at sub-
Released
system vendor or Subcontractor facilities.
g.
Production Test and Evaluation. An overview of the Contractor’s production
testing programme that will be conducted to verify quality, serviceability,
configuration control and compliance with the design for each unit of production.
The Production Test programme should be a subset of the Prototype Test
programme. Note that the VCRI shal  include a ‘production’ column that identifies
the sub-set of specifications that apply to the production testing. The overview
shall describe any production programme substantiation methods that are unique
to the production phase. The overview shall identify any production test activities
that are planned to be performed at sub-system vendor or Subcontractor

P a g e  66 | 119

facilities. The overview shall identify the interrelationship between all Production
Test Plans.
9.
The overviews may include, as appropriate for each phase, reference to the following
categories of test activity:
a.
Safety.
b.
Roll Over Protection Structure.
c.
Homologation.
d.
Mobility performance and handling.
1982
e.
Weight and Balance.
Act
f.
Environmental qualifications.
g.
Electrical loads.
h.
Electromagnetic Environmental Effects and/or Radiation Hazards.
i.
Special Tests, including System Reliability Demonstration, Maintainability
Demonstration and software stress tests.
j.
Stowage loads, retention, carriage and access.
Information
k.
Integrated C4I performance.
l.
Heating, cooling and ventilation, and thermal properties.
m.
Human factors, including visibility, egress, lighting, sound levels and
Official
ventilation/climate control.
Test and Evaluation Resource Summary
the
10.  The Master Test Plan shall identify and characterise the major Contractor resources,
and any agreed Crown resources included in the Contract GFM List, that will be
required to support the test activities of the Contract, including:
under
a.
test ranges and facilities.
b.
test support equipment and instrumentation.
c.
test targets and threat simulators.
d.
simulation, software models and test beds.
e.
Crown resources (if any).
Released
f.
post-test activities such as data processing or data reduction.
11.  The Master Test Plan shall provide generic instructions and associated definitions to
be used for the following subordinate Test and Evaluation planning and reporting
documents:
a.
Test Plans in accordance with DID TEST-4.2;
b.
Test Procedures in accordance with DID TEST-4.3; and

P a g e  67 | 119

c.
Test Reports in accordance with DID TEST-4.4.
Updates
12.  The Master Test Plan documents dynamic activities and shall be kept current in
accordance with clause 7.2 of the Contract.
QUANTITY
13.  The Contractor shall provide one electronic copy.
1982
Act
Information
Official
the
under
Released

P a g e  68 | 119

DID TEST-4.2 – Test Plans
REFERENCE NUMBER
TITLE:
DID TEST-4.2
TEST PLANS
DESCRIPTION/PURPOSE:
The Test Plans describe the testing methodology, test data requirements, schedules,  1982
management and organisational relationships and the documentation that will be used to
control the testing process.
Act
ISSUE DATE:
Draft:  Relevant Test Programme -60 Business Days
Final:  Relevant Test Programme -20 Business Days.
FORMAT
1.
The Test Plan may be in the Contractor’s layout.  Information
2.
The Test Plan shall be written in English.
3.
The Test Plan shall be delivered in an electronic format capable of being read, copied,
searched and printed by the Crown using Microsoft WORD™.
Official
CONTENT
4.
The Test Plans shall be consistent with the templates, methods, procedures and
the
standards defined in the Master Test Plan.
5.
The Test Plan shall include, but is not limited to:
a.
test objectives;
under
b.
reference documents and standards;
c.
hierarchy, order and interdependence (including pre-requisites) with other tests;
d.
aim of the test;
e.
equipment, software or systems under test;
Released
f.
proposed test procedure, including equipment and facilities and safety
precautions;
g.
test schedule;
h.
Test Management and Review Processes, including the method for recording
and analysing results, correction factors, test tolerances, datum information and
modelling techniques;

P a g e  69 | 119

i.
pass/fail criteria;
j.
re-test procedures; and
k.
Test Failure Reporting and Corrective Action Processes.
QUANTITY
6.
The Contractor shall provide one electronic copy.

1982
Act
Information
Official
the
under
Released

P a g e 70 | 119

DID TEST-4.3 – Test Procedures
REFERENCE NUMBER
TITLE:
DID TEST-4.3
TEST PROCEDURES
DESCRIPTION/PURPOSE:
The Test Procedures describe the step-by-step testing operations to be performed on items
undergoing testing.
1982
ISSUE DATE:
Act
Draft: Relevant Test Programme -20 Business Days.
Final:. Relevant Test -5 Business Days.
FORMAT
1.
The Test Procedures may be in the Contractor’s layout.
2.
The Test Procedures shall be written in English.  Information
3.
The Test Procedures shall be delivered in an electronic format capable of being read,
copied, searched and printed by the Crown using Microsoft WORD™.
CONTENT
Official
4.
The Test Procedures shall be consistent with the templates, methods, procedures and
standards defined in the Master Test Plan.
the
5.
The Test Procedures shall include, but are not limited to:
a.
applicable documents and references;
b.
equipment to be tested;
under
c.
step-by-step testing procedures. The step-by-step description shall include the
parameters to be tested or measured, means of measurement. The step-by-step
description shall be designed in a modular manner, such that a failed test step
can be repeated without repeating the entire test, wherever practicable;
d.
test data sheets for recording test measurements, observations and results. The
data sheets shall identify the objective performance values, with associated
Released
tolerances, or assessment criteria for each of the test steps;
e.
Safety Precautions and Emergency Procedures, being reiteration and expansion
of the safety precautions identified in the relevant Test Plan, including any notes,
cautions and warnings associated with the test steps; and
f.
Security Classification including security markings appropriate for the test, test
equipment and any results that may be recorded during the conduct of the test.

P a g e  71 | 119

QUANTITY
6.
The Contractor shall provide one electronic copy.

1982
Act
Information
Official
the
under
Released

P a g e 72 | 119

DID TEST-4.4 – Test Reports
REFERENCE NUMBER
TITLE:
DID TEST-4.4
TEST REPORTS
DESCRIPTION/PURPOSE:
The Test Reports describe the testing that has taken place and provide the record of the test
procedure used and the test results.
1982
ISSUE DATE:
Act
Draft: Not applicable.
Final: Relevant Test +10 business days.
FORMAT
1.
The Test Report may be in the Contractor’s layout.
2.
The Test Report shall be written in English.
Information
3.
The Test Report shall be delivered in an electronic format capable of being read,
copied, searched and printed by the Crown using Microsoft WORD™.
CONTENT
Official
4.
The Test Reports are be provided at the completion of each Test Procedure.
5.
The Test Report shall include, but is not limited to:
the
a.
applicable documents and references, with the standards and specifications and
all interrelated and linked test reports shall be identified;
b.
equipment tested, including setup and configuration, all resources used for the
under
test, including test equipment, facilities and personnel;
c.
location and duration of the test;
d.
summary of any constraints and limitations affecting the test and the effect of
these constraints or limitations, including any departures from the test set-up or
test procedure;
e.
description of observed performance, a summary of the results observed during
Released
the test, with all anomalies, failures and out-of-tolerance conditions shall be
recorded and, where possible, explained;
f.
analysis of results including a log of test failures and the associated corrective
action. Annexes may be used for any complex calculations or long lists; and
g.
conclusions and recommendations including an assessment of the success, or
otherwise, of the test in verifying compliance with the associated Contract

P a g e 73 | 119

requirements. When a test fails to fully verify compliance, the Test Report shall
include a recommendation for corrective or follow-on action.
QUANTITY
6.
The Contractor shall provide one electronic copy.

1982
Act
Information
Official
the
under
Released

P a g e 74 | 119

DID TEST-4.5 – Electrical Load Test Plan
REFERENCE NUMBER
TITLE:
DID TEST-4.5
ELECTRICAL LOAD TEST PLAN
DESCRIPTION/PURPOSE:
The Electrical Load Test Plan describes the testing regime the Contractor will undertake to
demonstrate that the Utility Vehicle (UV) electrical system satisfies the specified
1982
requirements.
ISSUE DATE:
Act
Draft: Example at Proposal.
Final: Relevant Test Programme Commencement -20 Business Days.
FORMAT
1.
The Electrical Load Test Plan may be in the Contractor’s layout.
Information
2.
The Electrical Load Test Plan shall be written in English.
3.
The Electrical Load Test Plan shall be delivered in an electronic format capable of
being read, copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The Electrical Load Test Plan shall describe the testing the Contractor will undertake to
demonstrate that the UV electrical system satisfies the Electrical Load requirements
the
specified.
5.
The Electrical Load Test Plan shall include An Electrical Load Test for each UV variant
with (without limitation):
under
a.
description of the test system;
b.
test objectives;
c.
reference documents and standards;
d.
hierarchy, order and interdependence (including pre-requisites) with other tests;
e.
equipment, software or systems under test;
Released
f.
proposed test procedure, including equipment and facilities;
g.
pass/fail criteria;
h.
re-test procedures; and
i.
Test Failure Reporting and Corrective Action Processes.

P a g e 75 | 119

6.
Documentation of test results shall be in accordance with the requirements of the DID
TEST-4.4 Test Reports.
QUANTITY
7.
The Contractor shall provide one electronic copy.

1982
Act
Information
Official
the
under
Released

P a g e 76 | 119

DID TEST-4.6 – Electromagnetic Environmental
Effects Test Plan
REFERENCE NUMBER
TITLE:
DID TEST-4.6
ELECTROMAGNETIC ENVIRONMENTAL EFFECTS TEST
PLAN
DESCRIPTION/PURPOSE:
1982
The Electromagnetic Environmental Effects Test Plan describes how the Contractor will
demonstrate the specified requirements that apply to Utility Vehicle (UV) have been
achieved.
Act
ISSUE DATE:
Draft: Example at Proposal.
Final: Relevant Test Programme Commencement  -20 Business Days
FORMAT
Information
1.
The Electromagnetic Environmental Effects Test Plan may be in the Contractor’s
layout.
2.
The Electromagnetic Environmental Effects Test Plan shall be written in English.
3.
The Electromagnetic Environmental Effects Test Plan shall be delivered in an
Official
electronic format capable of being read, copied, searched and printed by the Crown
using Microsoft Word™.  the
CONTENT
4.
The Electromagnetic Environmental Effects Test Plan shall describe how the
Contractor will demonstrate that:
under
a.
Electromagnetic Environmental Effects (EEE) of UV equipment does not interfere
with or degrade the performance and function of other systems.
b.
Electromagnetic Environmental Effects (EEE) of the UV equipment does not
interfere with or degrade the performance and function of equipment in the
proximity of the UV.
c.
The function and performance of the UV systems are not degraded by the
accumulation and discharge of electric charge associated with Precipitation Static
Released
(P-Static).
5.
The Electromagnetic Environmental Effects Test Plan shall include:
a.
test objectives;
b.
reference documentation and standards;
c.
hierarchy, order and interdependence (including pre-requisites) with other tests;

P a g e  77 | 119

d.
equipment, software or system under test;
e.
proposed test structure, including equipment and failures;
f.
pass/fail criteria;
g.
re-test procedures; and
h.
Test Failure Reporting and Corrective Action Process.
6.
Documentation of test results shall be in accordance with the requirements of the DID
TEST-4.4 Test Reports.
1982
QUANTITY
7.
The Contractor shall provide one electronic copy.

Act
Information
Official
the
under
Released

P a g e 78 | 119

DID TEST-4.7 – Roll Over Protection Structure
Report
REFERENCE NUMBER
TITLE:
DID TEST-4.7
ROLL OVER PROTECTION STRUCTURE REPORT
DESCRIPTION/PURPOSE:
1982
The Roll Over Protection Structure (ROPS) Report describes how the Contractor will
demonstrate that the specified requirements have been achieved for the Utility Vehicle (UV).
Act
ISSUE DATE:
Draft: Not applicable.
Final: For each variant, one month after Final Design Review for that variant.
FORMAT
Information
1.
The ROPS Report may be in the Contractor’s layout.
2.
The ROPS Report shall be written in English.
3.
The ROPS Report shall be delivered in an electronic format capable of being read,
copied, searched and printed by the Crown using Microsoft Word™.
Official
CONTENT
the
4.
The ROPS Report shall describe how the Contractor has demonstrated compliance
with the ROPS requirements of the Contract.
5.
The ROPS Report shall include the following aspects for the validation of compliance,
as applicable:
under
a.
reference documentation and standards;
b.
results of theoretical analysis that validate compliance;
c.
results of any physical testing used to validate compliance including test
approach, test equipment, test procedures, pass/fail criteria, any test failures and
remediation, with documentation of test results in accordance with the
requirements of the DID TEST-4.4 Test Reports; and
Released
d.
if previous ROPS certification has been used as part of the agreed demonstration
of compliance, copies of the test reports for previous tests and any other relevant
supporting information (e.g., analysis results, analysis of previous test relevance
to UV).
QUANTITY
6.
The Contractor shall provide one electronic copy.

P a g e 79 | 119

DID TEST-4.8 – Cyber Vulnerability Report
REFERENCE NUMBER
TITLE:
DID TEST-4.8
CYBER VULNERABILITY REPORT
DESCRIPTION/PURPOSE:
The Cyber Vulnerability Report describes the safe-guards the Contractor has put in place to
ensure that all IT hardware, firmware and software inherent to the Utility Vehicle (UV) and its
1982
associated equipment are protected from cyber threats.
ISSUE DATE:
Act
Draft: If Contractor has this information, EXAMPLE at Proposal.
Final: For each variant, one month after Final Design Review of that variant.
FORMAT
1.
The Cyber Vulnerability Report may be in the Contractor’s layout.
Information
2.
The Cyber Vulnerability Report shall be written in English.
3.
The Cyber Vulnerability Report shall be delivered in an electronic format capable of
being read, copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The Contractor shall provide a Cyber Vulnerability Report that demonstrates the
following:
the
a.
List of hardware, firmware and software inherent to UV vehicles that may be
susceptible to cyber vulnerabilities and the mitigations.
b.
List of hardware, firmware and software inherent to UV sub-systems, diagnostic
under
tools and supporting Information Technology systems that may be susceptible to
cyber vulnerabilities and the mitigations.
c.
A risk assessment of the integrity of the Contractor’s supply chain for electronic
equipment. The supply chain has high risks as a possible vector for cyber
vulnerabilities (attack vector). The cyber risk assessment shall define the
following:
Released
(1)
control measures established to promote and ensure integrity of the supply
chain;
(2)
any certifications that the Contractor and Key Subcontractors has in Cyber
security  (e.g. UK ‘Cyber Essentials’, etc ); and
(3)
procedures for, and results of, cyber security audits of internal and/or
external supply chains.

P a g e  80 | 119

QUANTITY
5.
The Contractor shall provide one electronic copy.

1982
Act
Information
Official
the
under
Released

P a g e 81 | 119

1982
Act
Information
Section 5 – Integrated Logistics Support Data

Official

the
under
Released

P a g e 82 | 119

DID ILS-5.1 – Government Furnished Materiel
List
REFERENCE NUMBER
TITLE:
DID ILS-5.1
GOVERNMENT FURNISHED MATERIEL LIST
DESCRIPTION/PURPOSE:
1982
The Government Furnished Materiel (GFM) List defines the materiel (equipment, services
and data) that the Contractor requests that the Crown supply during the Acquisition
Contract.
Act
ISSUE DATE:
Draft: Proposal.
Final: Agreed GFM included in Annex J (GFM List) of Contract.
FORMAT
Information
1.
The GFM List shall be in the layout shown in Annex J of the Contract.
2.
The GFM List shall be written in English.
3.
The draft GFM List shall be delivered in an electronic format capable of being read,
copied, searched and printed by the Crown using Microsoft Excel™ or Microsoft
Official
Word™.
CONTENT
the
4.
The GFM List identifies materiel (information, support services and equipment) that the
Contractor requests the Crown to supply during the course of the Acquisition Contract.
GFM may include data and/or equipment to be incorporated with Contract Deliverables,
or equipment that will be carried in the vehicles in order for the Contractor to design
under
associated mounts, stowage or support equipment.
5.
The GFM List will become part of the Contract with the successful Respondent.
6.
As a general principle, the Crown relies on the Contractor to source all materiel
required to manufacture and supply the Contract Deliverables. Items must only be
proposed as GFM in the following instances:
a.
equipment for incorporation with Contract Deliverables and any supporting data
Released
that can only be procured via government to government channels;
b.
equipment that the Crown already has in inventory, typically:
(1)
samples of equipment to enable the design of mounts and stowage;
(2)
equipment that affects design of the Contract Deliverables (e.g.,
ergonomics and function);

P a g e 83 | 119

c.
services that can only be performed by Crown agencies (e.g., test personnel,
TEMPEST testing, etc); or
d.
materiel where there is a compelling cost or supply advantage in the Crown
sourcing it.
7.
The GFM List shall provide sufficient information to allow the Crown to identify,
consider and, if acceptable to the Crown and included in the Contract’s GFM List,
procure and deliver the GFM to the Contractor. The GFM List shall include, but is not
limited to:
a.
a description of the information, publications, equipment, material, software,
including associated identification codes, NATO Stock Number, manufacturer’s
1982
reference, and part number, as appropriate;
b.
required quality;
Act
c.
required delivery schedule;
d.
Estimated Cost (if known);
e.
special delivery preparation, procedures, instructions or requirements;
f.
specification for any services and resources required;
g.
details of personnel, including numbers and skills required;
Information
h.
any storage or security considerations;
i.
any services, facilities and government-to-government compliances that it
requests the Crown to supply;
Official
j.
the reasons for the request, rather than being Contractor furnished; and
k.
the benefits that may accrue to the Crown if the Crown agrees to supply such
the
GFM.
QUANTITY
8.
The Contractor shall provide one electronic copy.

under
Released

P a g e 84 | 119

DID ILS-5.2 – Codification
REFERENCE NUMBER
TITLE:
DID ILS-5.2
CODIFICATION
DESCRIPTION/PURPOSE:
Codification Data describes how the Contractor will provide all supporting data to satisfy the
Crown’s requirement for Codification.
1982
ISSUE DATE:
Act
Draft: Example at Proposal.
Final: Two months after relevant Crown Provisioning Notice (for items not already codified).
FORMAT
1.
Codification Data shall be in the format outlined at DID ILS-5.2 Annex A.
2.
Codification Data shall be written in English.
Information
3.
Codification Data shall be delivered in an electronic format capable of being read,
copied, searched and printed by the Crown using Microsoft Excel™ or Microsoft
Word™.
CONTENT
Official
4.
The Crown shall be responsible for assigning a NATO Stock Number (NSN) to all new
procurable items that do not have an NSN. An explanation of the Codification system is
the
at DID ILS-5.2 Annex A.
5.
The Contractor shall provide codification information in the form of a list. The listing
shall include all goods procured from subcontractors and vendors.
under
6.
Codification information shall be provided as follows:
a.
for all goods not codified (i.e., not allocated an NSN) in the format at Annex B to
this DID: All columns need to be completed (except for column (c));
b.
for goods already codified but not listed in the Complete Support Equipment
Price List (CSEPL) or the Illustrated Parts Catalogue (IPC): in the format at
Annex B to this DID: Columns (a) to (f) need to be completed; and
Released
c.
for goods already codified and listed in the CSEPL or the IPC: No further action is
required.
QUANTITY
7.
The Contractor shall provide one electronic copy.

P a g e 85 | 119

ANNEX A
TO DID ILS-5.2
CODIFICATION
General
1.
The NATO Codification System (NCS) in conjunction with the NZDF Corporate Supply
and Finance System (SAP R/3) is designed to provide a common materials management
language nationally within and between NZDF and associated Government Departments,
and internationally between NZ, Australian and other friendly participating nations.
Codification provides the basis for:
1982
a.
classification of items;
b.
the application of one unique identifying stock number;
Act
c.
the application of a standard system for naming and describing items;
d.
a method of recording known manufacturer for a particular item; and
e.
access to the inventories of friendly, participating nations.
2.
The NZDF supply and finance system requires each item of equipment to be assigned
a NATO Stock Number (NSN) before that item can be accepted into service and paid for. For
this reason, codification is essential prior to delivery of the offered solution.
Information
NCS
3.
The NCS is an international system for allocating unique identification numbers to
equipment and spare parts. Each item is uniquely identified, catalogued and assigned an
identifying NSN. The NSN permits forces in operational or non-operational environments to
Official
be supplied with the right item, in the right place, at the right time.
4.
Responsibility for codification of an item lies with the NATO Codification Bureau (NCB)
the
of the country where the item is manufactured. Provision of information needed to carry out
the codification is the responsibility of the Prime contractor.
5.
Codification of NZ manufactured items is carried out by the New Zealand NCB (NZ
NCB).
under
NSN
6.
Each item of supply is identified in the NCS by a unique 13 digit NSN. The NSN
consists of three identifying parts:
a.
a four digit NSC, also known as "Group Class", this places the item into a group
classification, for example generators, aircraft engines etc;
Released
b.
a two digit NC, also known as “Nation Code” this identifies the nation of
manufacture; and
c.
a seven digit IIN, also known as ‘Item Identification Number” which, together with
the NC, is unique to that item.
7.
An example of a NSN is 5820-00-930-3725, where:

P a g e 86 | 119

a.
5820 is the NSC/Group Class for "Radio and Television Communication
Equipment; Non-Airborne";
b.
00 is the NC for the USA (New Zealand NC is 98); and
c.
930-3725 is the IIN.

1982
Act
Information
Official
the
under
Released

P a g e 87 | 119

ANNEX B
To DID ILS-5.2
1982
CODIFICATION INFORMATION REQUIREMENTS

End Item
Sheet of
Act

Supplier’s Part
True
Approved Item
Unit
Supplier/NGAGE
True Manufacturer
Manufacturer’s
IPC Cross
Unit
Number
Serial
NSN
Name (AIN)
of
Part Number
Reference
Cost
or
Qty
Mandatory for Items not allocated a NATO Stock Number (NSN)
IPC Item Name
(a)
(b)
(c)
(d)
(e)
(f)
(g)
(h)
(i)
(j)

Information

Official

the

under
Released

P a g e  88 | 119

EXPLANATORY NOTES ON CODIFICATION INFORMATION REQUIREMENTS
1.
A separate listing is required for each end item supplied under the contract including
accessories and Support and Test Equipment.
2.
The full address, telephone, and facsimile number for each Manufacturer and Supplier are to be
provided; however this need only be given once on the first occurrence in each listing. Where
known the Manufacturer's Code for each Manufacturer and Supplier is to be provided.
3.
A new listing is to be provided for each major assembly. Each listing is to clearly identify the
End Item to which it belongs in the top left-hand corner of each page.
4.
The information required in each of the columns is as follows:

Serial
This is a sequential number commencing at 001 and entered for
each item. These are to run sequentially throughout the list and
1982
not start anew with each end item.

IPC Cross Reference
A cross reference to the Illustrated Parts Catalogue (IPC) page
Act
and item number which identifies the part.

NSN
The NSN allocated by the NCS (if known).

Approved Item Name
This is the approved item name or Item Name given in the NCS
(if known). Where this is not available the item name used in the
IPC is to be given.

Unit of Qty
The unit in which the item is supplied e.g., each, box of 10,
Information
Kilogram, Metre, etc.

Unit Cost
The price of each item individually.

Supplier
The name and address of the Supplier of the item.

Official
Supplier's Part No
The Part Number used by the Supplier to Identify the Item. If not
codified.
the

True Manufacturer
The name and address of the True Manufacturer of the item
where this differs from the Supplier. If not codified.

True Manufacturer's Part
The Part Number used by the Manufacturer to Identify the Item.
under
Number

Released

DID ILS-5.3 – Manufacturer’s Recommended
Spares List
REFERENCE NUMBER
TITLE:
DID ILS-5.3
MANUFACTURER’S RECOMMENDED SPARES LIST
DESCRIPTION/PURPOSE:
The Manufacturer’s Recommended Spares List (MRSL) is a list provided by the Contractor
of spares recommended for the Crown to procure to support the Utility Vehicles (UV), their
1982
sub-systems and ancillary equipment. The MRSL informs the Crown’s consideration of
Spares to purchase.
Act
ISSUE DATE:
Draft: Proposal.
Final: One month prior to the initial Provisioning Conference.
FORMAT
Information
1.
The MRSL shall be in the Contractor’s format. It shall include spares quantities and
price information for all line items, with all price information to be in accordance with
clause 6 of the Contract.
2.
The MRSL shall be written in English.
Official
3.
The MRSL shall be delivered in an electronic format capable of being read, copied,
searched and printed by the Crown using Microsoft Excel™ or Microsoft Word™.
the
CONTENT
4.
The MRSL shall be consistent with the proposed maintenance philosophy, mission
profile and operating conditions specified in the Statement of Requirements and
established in the subsequent Technical Specification. The Contractor
recommendations must be consistent with its experience elsewhere and the proposed
under
support system.
5.
For each support option identified for each system (includes all variants, support
equipment and training aids), the Contractor shall provide a complete MRSL for all
spares used in that system, based on:
a.
Mean Time Between Failure (MTBF) and Mean Time To Repair (MTTR) data
relevant to the operational availability and requirements set in the Technical
Released
Specification;
b.
the operating profile as detailed in the Technical Specification;
c.
three maintenance locations; and
c.d.  The fleet numbers of each variant (refer the 'likely' quantities of vehicles/variants
in table 1 of Section 3 of the RFP).

P a g e  90 | 119

6.
The MRSL shall identify those spares that are unique to one or more vehicle variants.
7.
The Contractor shall supply a separate list of all items specified in the MRSL, that have
a supply lead time that is greater than 60 days from date of order. Against each such
item the Contractor shal  specify a “no later than” ordering date that will required to be
met in order to not impact the proposed Project Schedule.
8.
The following information (fields) shall be included in the MRSL (without limitation):
a.
Item Number;
b.
Part Number;
c.
NSN (where it already exists);
1982
d.
Item Description;
e.
Consumable, repairable or replaceable;
Act
f.
Quantity per assembly/vehicle/variant;
g.
Minimum order quantity;
h.
Price per unit (in accordance with clause 6 of the Contract);
i.
MTBF (where data already exists);
Information
j.
MTTR (where data already exists);
k.
Shelf-life (where applicable);
l.
Lead Time; and.
Official
l.m.  Recommended Quantity.
QUANTITY
the
9.
The Contractor shall provide one electronic copy.

under
Released

P a g e  91 | 119

DID ILS-5.4 – Recommended Support and Test
Equipment List
REFERENCE NUMBER
TITLE:
DID ILS-5.4
RECOMMENDED SUPPORT AND TEST EQUIPMENT LIST
DESCRIPTION/PURPOSE:
The Recommended Support and Test Equipment List (RSTEL) is a list provided by the
Contractor of recommended specific tools and equipment to support all variants of the Utility
1982
Vehicle (UV), its sub-systems and ancillary equipment. The RSTEL is to aid the Crown’s
consideration of Support and Test Equipment (S&TE) to purchase.
Act
ISSUE DATE:
Draft: Proposal.
Final: One month prior to the relevant Provisioning Conference.
FORMAT
Information
1.
The RSTEL may be in the Contractor’s layout.
2.
The RSTEL shall be written in English.
3.
The RSTEL shall be delivered in an electronic format capable of being read, copied,
searched and printed by the Crown using Microsoft Excel™ or Microsoft Word™.
Official
CONTENT
4.
For each support option identified in the Through Life Support Contract proposal the
the
contractor shall provide a complete RSTEL based on:
a.
Mean Time Between Failure (MTBF) and Mean Time To Repair (MTTR) data,
derived from the operational availability and mission profile; and
under
b.
the requirements for operational deployments, based on information provided in
the mission profile.
5.
S&TE includes:
a.
equipment, such as tools, covers, stands, test benches, holding fixtures,
alignment tools and replenishment rigs, and
Released
b.
test equipment, such as the equipment required to test the function of systems,
components or Line Replaceable Units (LRUs) that are installed in the UV or
repair shops.
6.
The Recommended Support and Test Equipment List (RSTEL) shall list equipment in
two categories:

P a g e 92 | 119

a.
General Purpose Test Equipment.  The RSTEL shall identify what general
purpose test equipment is required and what testing regime is needed (activity
and frequency of test).
b.
Special-to-Type Test Equipment.  The RSTEL shall identify the Test equipment
and support tools that are unique to this type of vehicle and outline how these are
used to provide support.  The Contractor will provide an ongoing service via the
TLSC to support the Special-to-Type Test Equipment
7.
The RSTEL shall contain the following fields:
a.
Item Description;
b.
Manufacturer;
1982
c.
Manufacturer/Supplier Part Number;
d.
NATO Stock Number (if already codified);
Act
e.
NATO Commercial Government Entity Code (NCAGE) (if already codified);
f.
Technical specification (including power supply requirements);
g.
Levels of maintenance that the item is required for;
h.
Quantity per assembly;
Information
i.
Unit Cost (in accordance with clause 6 of the Contract);
j.
Number required to support proposed operations [refer TLS Requirement #1 in
the Through Life Support (TLS) Requirements (Statement of Work) at Enclosure
2 to Part 2 of the RFP) and that this requirement specifies that Utility Vehicle
maintenance support occurs at Trentham, Linton and Burnham];
Official
k.
Items for local manufacture in New Zealand and reasons why this is proposed;
the
l.
Scheduled maintenance and calibration requirements;
m.
Maintenance Manual and Illustrated Parts Catalogue reference/identification
number (if available at time of submission; otherwise this information will only be
required after Contract signature);
under
n.
Training requirement for any special to type support equipment and cost;
o.
Recommended initial spares purchase for the S&TE;
p.
Lead-time;
q.
Recommended maintenance levels; and
Released
r.
Manufacturers qualified repair points.
QUANTITY
8.
The Contractor shall provide one electronic copy.

P a g e  93 | 119

DID ILS-5.5 – Packaging Handling Storage and
Transportation Data
REFERENCE NUMBER
TITLE:
DID ILS-5.5
PACKAGING HANDLING STORAGE AND
TRANSPORTATION DATA
DESCRIPTION/PURPOSE:
Packaging, Handling, Storage and Transportation (PHS&T) Data describes the logistics
considerations for all items that require special packaging, handling, shipping and
1982
transportation throughout the life of the Contract Deliverables.
Act
ISSUE DATE:
Draft: Two months after Contract Execution Date of Acquisition Contract.
Final: Final Provisioning Conference.
FORMAT
1.
PHS&T Data may be in the Contractor’s layout.  Information
2.
PHS&T Data shall be written in English.
3.
PHS&T Data shall be delivered in an electronic format capable of being read, copied,
searched and printed by the Crown using Microsoft Excel™ or Microsoft Word™.
Official
PACKAGING
4.
PHS&T Data shall identify all special handling requirements including identification
methods, for items that are:
the
a.
fragile; or
b.
electrostatically sensitive; or
under
c.
hazardous substances; or
d.
ozone depleting and/or otherwise hazardous to the environment; or
e.
explosive ordnance (if any); or
f.
secure (e.g., COMSEC) items; or
Released
g.
shelf-lifed.
HANDLING AND STORAGE
5.
PHS&T Data shall identify for each of the above items the minimum requirement,
quantity and source of:
a.
specialist storage facilities;

P a g e  94 | 119

b.
Special To Type Containers (STTC); and
c.
lifting equipment and handling aids.
6.
PHS&T Data shall provide justification for the quality and quantity of packaging
recommended to provide logistic support for each level of operation, maintenance and
support of the UV and support system components.
TRANSPORTATION
7.
PHS&T Data shall identify any special transportation provisions for any items to be
supplied as part of the UV acquisition.
QUANTITY
1982
8.
The Contractor shall provide one electronic copy.

Act
Information
Official
the
under
Released

P a g e 95 | 119

DID ILS-5.6 – Human Machine Interface
Analysis Report
REFERENCE NUMBER
TITLE:
DID ILS-5.6
HUMAN MACHINE INTERFACE ANALYSIS REPORT
DESCRIPTION/PURPOSE:
The Contractor shall provide a Human Machine Interface Analysis Report (HMIAR) for the
Utility Vehicle (UV).
1982
ISSUE DATE:
Act
Draft: For each variant, five Business Days before the Final Design Review of that variant.
Final: For each variant, one month after Final Design Review of that variant.
FORMAT
1.
The HMIAR may be in the Contractor’s layout.
Information
2.
The HMIAR shall be written in English.
3.
The HMIAR shall be delivered in an electronic format capable of being read, copied,
searched and printed by the Crown using Adobe Acrobat™ or Microsoft Word™.
CONTENT
Official
4.
The HMIAR shall describe the processes used by the Contractor to effectively
integrate personnel into the design of the Utility Vehicles.
the
5.
The HMIAR shall document the following aspects for each crew position:
a.
layout and arrangement;
b.
access to and visibility of controls and displays used at that position;
under
c.
field of view outside the vehicle;
d.
internal environmental factors such as ventilation;
e.
lighting;
f.
aural and visual signals and alerts; and
Released
g.
Ingress and egress.
QUANTITY
6.
The Contractor shall provide one electronic copy.

P a g e 96 | 119

DID ILS-5.7 – Facilities Data
REFERENCE NUMBER
TITLE:
DID ILS-5.7
FACILITIES DATA
DESCRIPTION/PURPOSE:
The Contractor shall provide Facilities Data for any special-to-type support equipment for
the Utility Vehicle (UV).
1982
ISSUE DATE:
Draft: If Contractor has this information, example at Proposal
Act
Final: Four months after Contract Execution Date of Acquisition Contract.
FORMAT
1.
The Facilities Data may be in the Contractor’s layout.
2.
The Facilities Data shall be written in English.
Information
3.
The Facilities Data shall be delivered in an electronic format capable of being read,
copied, searched and printed by the Crown using Adobe Acrobat™ or Microsoft
Word™.
CONTENT
Official
4.
The Facilities Data shall provide sufficient detail for the Crown to prepare any special-
to-type facilities for support of the Utility Vehicles, e.g., Synthetic Training Devices [if
any], special support equipment, etc. Facilities data is not required for garages,
the
parking, hazardous materials storage, fuelling, wash facilities, material warehouses,
generic training classrooms or support offices.
5.
The Facilities Data shall describe the following for each room required:
under
a.
Room name;
b.
Function;
c.
Relationship to other areas (if any);
d.
Floor Area. Physical space requirements including safety distances;
e.
Architectural Requirements. Size of entrance doors, Storage space requirements,
Released
Floor loading, Noise insulation;
f.
Utility Services. Plumbing services, mechanical services, waste
extraction/removal;
g.
Electrical services. Including anticipated peak loadings in “worst case” scenarios,
power cleanliness (equipment susceptibility to spikes in power), Electromagnetic
Interference/Electromagnetic Compatibility and Static Bonding requirements;

P a g e  97 | 119

h.
Heating, Cooling and Ventilation Services. Air conditioning, de-humidification,
dust control, clean room;
i.
Fire Protection. Fire detection and control systems;
j.
Computer and telecommunications. Space, proximity and data interface
requirements;
k.
Furniture and Fittings; and
l.
Security Requirements.
6.
The Facilities Data shall also identify the vehicle-specific requirements for
maintenance facilities including aspects such as clearances around the vehicle for 1982
maintenance access and removals, the clear space required for maintenance tasks
(e.g., clearances above the vehicle for cab tilting, engine lift, etc.) and the storage
space needed for temporary storage of equipment that is removed for maintenance.
Act
7.
The Facilities Data shall identify any key assumptions for the analysis and
recommendations.
QUANTITY
8.
The Contractor shall provide one electronic copy.

Information
Official
the
under
Released

P a g e 98 | 119

DID ILS-5.8 – Material Safety Data Sheets
REFERENCE NUMBER
TITLE:
DID ILS-5.8
MATERIAL SAFETY DATA SHEETS
DESCRIPTION/PURPOSE:
The Contractor shall provide Material Safety Data Sheets (MSDS) for the hazardous
substances required to operate, maintain and support the Utility Vehicle (UV) and any other
Contract Deliverables.
1982
ISSUE DATE:
Act
Draft: Proposal.
Final: For each variant, three months after Final Design Review of that variant.
FORMAT
1.
The MSDS may be in the Contractor’s layout.
2.
The MSDS shall be written in English.
Information
3.
The MSDS shall be delivered in an electronic format capable of being read, copied,
searched and printed by the Crown using Adobe Acrobat™.
CONTENT
Official
4.
The Contractor shall provide MSDS for the hazardous substances required to operate,
maintain and support the UV and any other Contract Deliverables (e.g., support
equipment).
the
QUANTITY
5.
The Contractor shall provide one electronic copy of the Draft.
5.6. The Contractor shall provide one electronic copy as a complete Final set on CD with
under
licence rights to produce unlimited hard copies and store electronic copies on NZDF and
support contractor information technology equipment, including mobile devices, with
distributed access via servers.

Released

P a g e 99 | 119

DID ILS-5.9 – Reliability, Availability and
Maintainability Data
REFERENCE NUMBER
TITLE:
DID ILS-5.9
RELIABILITY, AVAILABILITY AND MAINTAINABILITY
DATA
DESCRIPTION/PURPOSE:
The Contractor shall provide Reliability, Availability and Maintainability (RAM) Data relating
to each variant of the Utility Vehicle (UV) and demonstrate that a full RAM analysis has been
1982
conducted.
Act
ISSUE DATE:
Draft: Proposal.
Final: For each variant, three months after Final Design Review of that variant.
FORMAT
1.
RAM Data may be in the Contractor’s layout.
Information
2.
RAM Data shall be written in English.
3.
RAM Data shall be delivered in an electronic format capable of being read, copied,
searched and printed by the Crown using Adobe Acrobat™ Microsoft Excel™ or
Microsoft Word™.
Official
CONTENT
4.
The Contractor will provide supporting Reliability, Availability and Maintainability (RAM)
the
data for each UV variant as the output of a RAM Analysis. Where required, the
Contractor will amend any existing RAM data to incorporate Contract specific vehicle
changes.
QUANTITY
under
5.
The Contractor shall provide one electronic copy.

Released

P a g e 100 | 119

DID ILS-5.10 – Pass Through Warranty
Information
REFERENCE NUMBER
TITLE:
DID ILS-5.10
PASS THROUGH WARRANTY INFORMATION
DESCRIPTION/PURPOSE:
Describe any component or Support Equipment warranties that will be passed on to the
Crown/NZDF.
1982
ISSUE DATE:
Act
Draft: Proposal.
Final: For each variant, one month after Final Design Review of that variant.
FORMAT
1.
The Pass Through Warranty information may be in the Contractor’s format.
Information
2.
The Pass Through Warranty information shall be written in English.
3.
The Pass Through Warranty information shall be delivered in an electronic format
capable of being read, copied, searched and printed by the Crown using Microsoft
Word™.
Official
CONTENT
4.
The Contractor shall provide a list of Suppliers that have Pass Through Warranties for
any component of any variant of the UV. The Contractor shall provide the following
the
information.
a.
OEM Name and Address;
b.
Contact details (phone and e-mail);
under
c.
Part number;
d.
Model number;
e.
Description;
f.
Length of warranty and start date;
Released
g.
Warranty Terms; and
h.
Authorised Dealer in New Zealand.
5.
In no event shal  any Pass Through Warranty Information reduce the Contractor’s
warranty obligations under the Contract.

P a g e  101 | 119

QUANTITY
6.
The Contractor shall provide one electronic copy.

1982
Act
Information
Official
the
under
Released

P a g e 102 | 119

1982
Act
Information
Section 6 – Publications Package

Official
the
under
Released

P a g e 103 | 119

DID PUB-6.1 – Operator Manuals
REFERENCE NUMBER
TITLE:
DID PUB-6.1
OPERATOR MANUALS
DESCRIPTION/PURPOSE:
The Contractor shall provide Operator Manuals for Utility Vehicle (UV) to allow the operator
to safely and effectively operate the vehicle, perform all operator maintenance and how to
handle vehicle emergencies.
1982
ISSUE DATE:
Act
Outline or Examples at Proposal.
Draft: Two months prior to start of the relevant training course.
Final: Four months after completion of respective training course.
FORMAT
1.
The Operator Manuals may be in the Contractor’s layout.
Information
2.
The Operator Manuals shall be written in English.
3.
The Operator Manuals shall be delivered in an electronic PDF format capable of being
edited, read, copied, searched and printed by the Crown using Adobe Acrobat™.
Official
CONTENT
4.
The Operator Manuals shall provide Utility Vehicle Crew with:
the
a.
general System descriptions;
b.
details on the safe use of the Systems;
c.
maintenance tasks that are typically performed by the operators;
under
d.
emergency procedures; and
e.
associated safety warnings.
HARD COPY FORMAT PUBLICATIONS
5.
The Contractor shall produce manuals of a quality suitable for operator use. Hard copy
Released
sizes and legibility shall be readable in low light conditions when illuminated with a
filtered red torch/light.
QUANTITY
6.
The following quantities of Operator Manuals are required:
a.
One electronic copy of the Outline or Example.

P a g e  104 | 119

b.
Draft and Final:
(1)
Electronic Copy: one complete set on CD with licence rights to produce
unlimited hard copies and store electronic copies on NZDF and support
contractor information technology equipment, including mobile devices, with
distributed access via servers.
(2)
Paper Copy: one paper copy per vehicle, bound in a hard cover and
delivered with each vehicle in the applicable stowage area.

1982
Act
Information
Official
the
under
Released

P a g e 105 | 119

DID PUB-6.2 – Equipment Maintenance
Manuals
REFERENCE NUMBER
TITLE:
DID PUB-6.2
EQUIPMENT MAINTENANCE MANUALS
DESCRIPTION/PURPOSE:
The Contractor shall provide Equipment Maintenance Manuals to support maintenance
activities on all Utility Vehicles (UV).
1982
ISSUE DATE:
Act
Outline or Examples at Proposal.
Draft: Two months prior to start of the relevant training course.
Final: Four months after completion of respective training course.
FORMAT
Information
1.
The Equipment Maintenance Manuals may be in the Contractor’s layout.
2.
The Equipment Maintenance Manuals shall be written in English.
3.
The Equipment Maintenance Manuals shall be delivered in an electronic format
capable of being edited, read, copied, searched and printed by the Crown using Adobe
Acrobat™.
Official

CONTENT
the
4.
The Equipment Maintenance Manuals shall provide maintenance personnel with a
general system and component description (including circuit diagrams or schematics)
and details on the maintenance, repair and test of all components for light and medium
grades of repair for all variants.
under
5.
The Equipment Maintenance Manuals shall specify inspection criteria, acceptance
standards, condemnation limits, and demonstrate the use of Support and Test
Equipment. Detail of repair procedures is to be broken down to match the grades of
repair previously identified.
6.
The electronic versions of any Equipment Maintenance Manuals that contain more than
50 pages/screens shall have internal hyperlinks that permit swift navigation between
referenced sections within the manual.
Released
QUANTITY
7.
The Contractor shall provide one electronic copy of the Outline or Example.
7.8. The Contractor shall provide one electronic copy as a complete Draft or Final set on
CD with licence rights to produce unlimited hard copies and store electronic copies on NZDF
and support contractor information technology equipment, including mobile devices, with
distributed access via servers.

P a g e 106 | 119

DID PUB-6.3 – Support and Test Equipment
Manuals
REFERENCE NUMBER
TITLE:
DID PUB-6.3
SUPPORT AND TEST EQUIPMENT MANUALS
DESCRIPTION/PURPOSE:
The Contractor shall provide Support and Test Equipment Manuals in support of all variants
of the Utility Vehicle (UV) to allow for the effective and safe maintenance and repair of UV
1982
Support and Test Equipment.
Act
ISSUE DATE:
Outline or Examples at Proposal.
Draft: Two months prior to start of the relevant training course.
Final: Four months after completion of respective training course.
FORMAT
Information
1.
The Support and Test Equipment Manuals may be in the Contractor’s layout.
2.
The Support and Test Equipment Manuals shall be written in English.
3.
The Support and Test Equipment Manuals shall be delivered in an electronic format
Official
capable of being edited read, copied, searched and printed by the Crown using Adobe
Acrobat™.
CONTENT
the
4.
The Contractor shall provide Support and Test Equipment (ST&E) Manuals (including,
but not limited to, training aids and Special to Type Test Equipment) to provide
maintenance personnel with a general equipment description. The description shall
include circuit diagrams, schematics and details on the operation, maintenance, repair,
under
test and calibration of the equipment, complete with an Illustrated Parts Catalogue to
each Repair Item.
QUANTITY
5.
The following quantities of Support and Test Equipment Manuals are required:
a.
Outline or Examples : One electronic copy.
Released
b.
Draft or Final:
(1)
Hard Copy: five complete sets; and
(2)
One electronic copy: as a complete set on CD with licence rights to
produce unlimited hard copies and store electronic copies on NZDF and
maintenance provider’s IT equipment, including mobile devices, and
distributed access via servers.

P a g e  107 | 119

DID PUB-6.4 – Illustrated Parts Catalogue
REFERENCE NUMBER
TITLE:
DID PUB-6.4
ILLUSTRATED PARTS CATALOGUE
DESCRIPTION/PURPOSE:
The Contractor shall provide Illustrated Parts Catalogue(s) (IPC) in support of all variants of
the Utility Vehicle (UV).
1982
ISSUE DATE:
Example at Proposal.
Act
Draft: Two months after initial Provisioning Conference.
Final: For each variant, two months before delivery of first vehicle of that variant.
FORMAT
1.
The Illustrated Parts Catalogue shall be in the format described at Annex A.
Information
2.
The Illustrated Parts Catalogue shall be written in English.
3.
The Illustrated Parts Catalogue shall be delivered in an electronic format capable of
being read, copied, searched and printed by the Crown using Adobe Acrobat™.
CONTENT
Official
4.
The Contractor shall provide an IPC that allows operators and maintenance personnel
to identify all components relevant to the stated repair philosophy.
the
QUANTITY
5.
The Contractor shall provide one electronic copy of the Example.
5.6. The Contractor shall provide one electronic copy: as a complete Draft or Final set on
under
CD with licence rights to produce unlimited hard copies and store electronic copies on NZDF
and maintenance provider’s IT equipment, including mobile devices, and distributed access
via servers.

Released

P a g e 108 | 119

ANNEX A
to DID PUB-6.4
ILLUSTRATED PARTS CATALOGUE (IPC)
Introduction
1.
This Annex details the minimum requirements for the IPC. The IPC is to provide, in
English, sufficient technical data, including illustrations, to enable NZ Army to identify each
and every item contained in the equipment supplied by the Contractor. The information
required forms the basis of the preparation of NZ Army documents.
Applicability
2.
The IPC shall be applicable only to the make and model of the item or equipment being
1982
supplied as part of the Acquisition Contract.
Repair Kits
Act
3.
A summary of any repair or servicing kits is to be provided together with details of
components of each kit. The manufacturers’ code, reference or part number is also to be
provided for each component and kit.
4.
The format is to be as per Enclosure 1 to this Annex.
IPC Illustrations
4.
Illustrations are to be in any of the following formats, in order of preference:
Information
a.
CorelDraw up to version 22.0;
b.
AutoCAD .DWG or .DXF;
c.
Scalable Vector Graphic.SVG (version 1.0 or 1.1); or
Official
d.
Layered Portable Document Format .PDF.
the
5.
If they are provided in PDF format they are to be printed to PDF from within the
ORIGINAL software and not scanned then formed into a PDF book.
6.
The IPC Illustrations are to be provided in electronic format complete with text (Excel
spreadsheet) for each and every item on each illustration using the headings in Annex A.
under
The Illustration electronic format is to be suitable for importation direct into Autocad (dwg),
Autodesk Inventor, CorelDraw or STEP (Exchange format for 3D models).
7.
On receipt, subject to any intellectual property provisions agreed between the parties,
IPC il ustrations shal  become the property of the “the Crown”. If the equipment is modified in
any way, which results in a drawing alteration, a new master copy shall be forwarded to the
NZDF, as soon as possible.
Released
Artwork Illustrations
8.
Illustrations shall be in isometric exploded form, be concise with components displayed
in assembly sequence, in relevant detail, with balance in layout and cosmetics.
9.
The overall dimensions of a hard copy illustration shall not exceed 420mm x 297 mm
(A3) landscape.
10.  All illustrations shall be originals.

P a g e  109 | 119

Item Numbering
11.  Identical items that appear more than once on a single frame must have the same item
number.
Major Components
12.  Major components shall be indicated on the main drawing of the equipment only, and a
further frame used to illustrate total component break down of that assembly.
13.  The IPC is to identify all assemblies/sub-assemblies that cannot be broken down
further.
Non-Illustrated Items
1982
14.  Non-illustrated items are items that shall be provided for repair of the equipment, but
the size of the drawing does not permit their inclusion.
Act
Use of Reference Items
15.  Reference items are items that are shown on the drawing to aid in the location of other
components.
16.  Reference items shall be drawn in a broken line style silhouette.

Information
Official
the
under
Released

P a g e  110 | 119

ENCLOSURE 1
to Annex A
1982 to DID PUB-6.4

DRAWING TITLE:

Act

Manufacturers Drawing Identification:

Sheet of

Drg Ref (Item
NSN
Technical
Qty on
MFR NCAGE (if
Mfr Part No
Component
Drg Cross
No)
(if known)
Description
Drg
known) or MFR
Reference(s)
Ref
name
(a)
(b)
(c)
(d)

(e)
(f)
(g)
Item 2 OR
-
BOLT, HEX HEAD,
3
Boltholder NZ
12345-12
-
Fig 1.0
2
M6x25,stainless
Information
steel,
Official
the
under
Released

P a g e  111 | 119

EXPLANATORY NOTES ON IPC TEXT
1.
The IPC shall describe by assemblies and sub-assemblies, every item/component in
the complete equipment.
2.
The following information is required in the header:
a.
Drawing Title: The Title of the drawing or frame.
b.
Manufacturers Drawing Identification: This is the drawing identification, plate
or frame identification number.
1982
c.
Sheet Number: The number of sheets per drawing.
3.
The information required for each of the columns of the IPC are:
Act
a.
Dwg Ref (item No): This is a sequential number, which commences at the top
left-hand corner of the illustration. It progresses sequentially in a clockwise
direction around the drawing. Identical items that appear more than once on the
frame must carry the same number.
b.
NSN: The NATO Stock Number (NSN) allocated by the NATO Codification
System.
c.
Technical Description: The full technical description of the item (for example;
Information
CAPACITOR, FIXED, ELECTROLYTIC l.0µF +/-5%, 100V).
d.
Qty on Dwg: The number of items that appear on the drawing.
e.
Mfr part no: The true manufacturers’ part number used to identify the items(s).
Official
f.
Component Reference(s): This is a list of component references that are
applicable to the item shown on the illustration and based on the schematic
diagram (for example; C1, C2, C5-7, R203, 1C1, 1C3, TR101, etc.).
the
g.
Dwg Cross Ref: This is a list indicating the location of this item in other drawings
(for example; drawing 1 EA item 3, 3FB item 1 0, etc.).

under
Released

P a g e  112 | 119

DID PUB-6.5 – Tie Down Scheme for Maritime,
Air and Rail Transportation
REFERENCE NUMBER
TITLE:
DID PUB-6.5
TIE DOWN SCHEME FOR MARITIME, AIR AND RAIL
TRANSPORTATION
DESCRIPTION/PURPOSE:
1982
If the Contractor has this information, the Contractor shall provide the Tie Down Scheme for
Maritime, Air and Rail Transportation for all variants of the Utility Vehicle (UV). Act
ISSUE DATE:
Draft: If Contractor has this information, example at Proposal.
Final: For each variant, two months before delivery of first vehicle of that variant.
FORMAT
1.
The Tie Down Schemes Information may be in the Contractor’s layout.
Information
2.
The Tie Down Schemes Information shall be written in English.
3.
The Tie Down Schemes Information shall be delivered in an electronic format capable
of being read, copied, searched and printed by the Crown using Microsoft Word™ or
Adobe Acrobat™.
Official
CONTENT
the
4.
The Contractor shall provide the Tie Down Scheme for Maritime, Air and Rail
Transportation.
QUANTITY
under
5.
The Contractor shall provide one electronic copy.

Released

P a g e 113 | 119

1982
Act
Information
Section 7 – Training Data

Official

the
under
Released

P a g e 114 | 119

DID TRA-7.1 – Training Plan
REFERENCE NUMBER
TITLE:
DID TRA-7.1
TRAINING PLAN
DESCRIPTION/PURPOSE:
The Training Plan shal  provide details of the Contractor’s approach to providing Training
Contract Deliverables.
1982
ISSUE DATE:
Act
Draft: Shortlist / NegotiationsProposal.
Final: Contract Execution Date of Acquisition Contract.
FORMAT
1.
The Training Plan may be in the Contractor’s layout.
2.
The Training Plan shall be written in English.
Information
3.
The Training Plan shall be delivered in an electronic format capable of being read,
copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The Training Plan shall describe how the Contractor proposes to deliver training and
training packages for the Utility Vehicles.
the
5.
The Training Plan shall be based on a ‘train-the-trainers’ approach, where:
a.
each course that is delivered by the contractor has the objective of providing
sufficient training to enable the students to subsequently provide the same
training in NZDF training facilities, and
under
b.
the contents of the training package provide sufficient training resources and
training aids to enable the NZDF to subsequently provide the same training in
NZDF training facilities.
6.
The Training Plan shall, as a minimum, include the following items:
a.
name and description of the courses to be developed;
Released
b.
process for Training Package (DID TRA-7.2) development and production;
c.
training delivery reviews, including Crown participation;
d.
duration, location and assumed training/expertise of students for each course;
and
e.
schedule for delivery of training courses and training packages in accordance
with the Contract and the Project Schedule (DID PROJ-1.2).

P a g e  115 | 119

QUANTITY
7.
The Contractor shall provide one electronic copy as a complete set on CD with licence
rights to produce unlimited hard copies and store electronic copies on NZDF and
support contractor information technology equipment, including mobile devices, with
distributed access via servers.

1982
Act
Information
Official
the
under
Released

P a g e 116 | 119

DID TRA-7.2 – Training Package
REFERENCE NUMBER
TITLE:
DID TRA-7.2
TRAINING PACKAGE
DESCRIPTION/PURPOSE:
The Contractor shall provide a Training Package for the Utility Vehicle (UV).
1982
ISSUE DATE:
Act
Draft: 90 Business Days prior to commencement of the first training course.
Final: 20 Business Days prior to commencement of the first training course.
FORMAT
1.
The Training Package may be in the Contractor’s layout.
2.
The Training Package shall be written in English. Information
3.
The Training Package shall be delivered in an electronic format capable of being read,
copied, searched and printed by the Crown using Microsoft Word™.
CONTENT
Official
4.
The Contractor shall deliver a Training Package for each variant of the UV. The
Training Package shall provide Crown operators and maintenance personnel with
sufficient information and skills to safely operate and conduct maintenance on each
the
variant of the UV and ancillary equipment.
5.
The Training Package shall include, but not necessarily be limited to, the following:
a.
Introduction:
under
(1)
Course data sheet; and
(2)
Course description;
b.
Course content:
(1)
Course length;
Released
(2)
Training objectives;
(3)
Training programme;
(4)
Instructional objectives; and
(5)
Lesson plans;
c.
Instructional Resources:
(1)
Instructor guides;

P a g e 117 | 119

(2)
Instructor notes; and
(3)
Test Question Banks;
d.
Training aids, e.g.:
(1)
Pre-course information (see DID TRA-7.3);
(2)
Computer based presentations;
(3)
Slides;
(4)
Videos;
1982
(5)
Charts;
Act
(6)
Student workbooks; and
(7)
Desktop software simulations (if any).
QUANTITY
6.
The Contractor shall provide one electronic copy as a complete set on CD with licence
rights to produce unlimited hard copies and store electronic copies on NZDF and
support contractor information technology equipment, including mobile devices, with
distributed access via servers.

Information
Official
the
under
Released

P a g e 118 | 119

DID TRA-7.3 – Pre-Course Information
REFERENCE NUMBER
TITLE:
DID TRA-7.3
PRE-COURSE INFORMATION
DESCRIPTION/PURPOSE:
The Contractor shall provide Pre-Course Information for each course to be delivered to
operate and support the Utility Vehicles (UV).
1982
ISSUE DATE:
Act
Draft: Four months prior to commencement of each relevant training course.
Final: Two months after completion of each training course (as part of DID TRA-7.2).
FORMAT
1.
Pre-Course Information may be in the Contractor’s layout.
2.
Pre-Course Information shall be written in English.
Information
3.
Pre-Course Information shall be delivered in an electronic format capable of being
read, copied, searched and printed by the Crown using Adobe Acrobat™ or Microsoft
Word™.
CONTENT
Official
4.
The Pre-Course Information shall include, but not necessarily be limited to, the
following:
the
a.
Course title;
b.
Course syllabus and assessment criteria;
under
c.
Competency levels attained;
d.
Course duration;
e.
Course location;
f.
Qualifications for attendance;
g.
Course student numbers (min - max);
Released
h.
Security requirements (personnel); and
i.
Instructor to student ratio.
QUANTITY
5.
The Contractor shall provide one electronic copy as a complete set on CD with licence
rights to produce unlimited hard copies and store electronic copies on NZDF and
support contractor information technology equipment, including mobile devices, with
distributed access via servers.

P a g e 119 | 119