data item description parent company guarantee pm201 · 2018. 6. 20. · pm201 . prepared by:...

Parent Company Guarantee, Rev 0 Document #: VSY-A08.22-0027 Agreement #: [* insert Agreement #]

NOT PROTECTIVELY MARKED

Unclassified of 4 Uncontrolled when Printed Purchaser’s initials: _____ See disclosure statement on front page of the Subcontract Supplier’s initials: _____

Data Item Description

Parent Company Guarantee

PM201

Prepared by : Vancouver Sh ipyards Co. L td . 2 Pe mber ton Ave . Nor th Van couver , BC, Canada, V7 P 2R2 Te l : (604) 988-3111 Fax: (604) 984-1636

© Vancouver Shipyards Co. Ltd. 2016




Parent Company Guarantee PM201

Purpose

The purpose of the Parent Company Guarantee is to secure the performance of the Supplier’s obligations under the Subcontract. The Parent Company Guarantee is in addition to, and not a substitute for, other remedies and protection in favour of the Purchaser provided in the Subcontract.

References

This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 2 (Project Management) of the SOW.

Preparation Instructions

This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) of Schedule D1 (SOW).

Format and Content

1 Complete attachment A to this DID (pro forma Parent Company Guarantee).




Attachment A to DID PM201

PARENT COMPANY GUARANTEE

THIS GUARANTEE made in duplicate as of the [* insert day] day of [* insert month] 201[* insert year].

BETWEEN: Vancouver Shipyards Co. Ltd. a company organized under the laws of British Columbia and having an office at 2 Pemberton Avenue, North Vancouver, British Columbia, CANADA, V7P 2R2 (hereinafter called “VSY”)

OF THE FIRST PART

AND: [Subcontractor Parent Information] (hereinafter referred to as the "Guarantor")

OF THE SECOND PART

WHEREAS VSY proposes to enter into Subcontract number [* insert number] (hereinafter referred to as "the "Subcontract") with [* insert full legal name of the Supplier] (hereinafter referred to as the "Supplier") under which the Supplier is to perform the Work as described in the Subcontract; and

WHEREAS the Guarantor acknowledges that VSY is willing to enter into such Subcontract only if the Guarantor guarantees the performance of the obligations of the Supplier under the Subcontract unconditionally and irrevocably; and

WHEREAS the Guarantor has agreed to guarantee to VSY unconditionally and irrevocably the Supplier’s performance of all the Supplier's obligations under the Subcontract;

NOW THEREFORE, in consideration of VSY’s issuance of the Subcontract, and the mutual covenants, promises, conditions and agreements hereinafter set out, the parties hereby agree:

1. The Guarantor unconditionally and irrevocably guarantees the performance and fulfilment of each and every obligation of the Supplier contained in or flowing from the Subcontract. In this Guarantee “obligation” includes all representations and warranties of the Supplier, all undertakings and promises of the Supplier and the payment of all damages for which the Supplier may become liable to VSY in relation to the Subcontract.

2. VSY shall not be obliged to resort to or exhaust any recourse which it may have against the Supplier or any other person before being entitled to claim against the Guarantor.

3. If the Supplier should fail to perform or fulfill any of its obligations, then forthwith upon the date of receipt by the Guarantor of a written call from VSY, the Guarantor shall undertake or cause to be undertaken the performance of all outstanding obligations as a primary obligor and not as surety, and the Guarantor does hereby guarantee to indemnify and save harmless VSY from and against all damages and claims of any nature relating to or occasioned by the Supplier’s failure to perform or discharge each and every one of the obligations, conditions and liabilities on the part of the Supplier to be observed or performed under the Subcontract.

4. It is further understood and agreed that the receipt by the Supplier or the Guarantor of any monies paid by VSY to the Supplier or the Guarantor, as the case may be, under or in respect of the Subcontract, shall be in complete discharge and release to VSY for and in respect of all monies so paid irrespective of the date when or the party to whom, but for this Guarantee, such monies were or might, or would have been payable.

5. No dealings of whatsoever kind between VSY and the Supplier whether with or without notice to the Guarantor, shall exonerate the Guarantor in whole or in part, and in particular, but without limitation, VSY may modify, amend or vary the Subcontract, exercise options, issue new subcontracts, grant any indulgence, release, postponement or extension of time, waive any term or condition of the Subcontract or any obligation of the Supplier, take or release any securities or other guarantees for performance and otherwise deal with the Supplier, the Subcontract in question, and any other persons as VSY may see fit, without affecting, lessening or impairing in any way the liability of the Guarantor.

6. No assignment of the Subcontract, sub-subcontract or any other dealings therewith by the Subcontractor, whether with or without the consent of VSY, shall affect this Guarantee.




7. Nothing whatsoever except the performance in full of all of the obligations of the Supplier under the Subcontract shall discharge the Guarantor of this Guarantee.

8. Wherever any determination of any dispute is made pursuant to the provisions of the Subcontract or any settlement or any judgment or finding of a court of competent jurisdiction is issued or made which is binding upon the Supplier in respect of the Subcontract, such determination or judgment or finding shall be binding upon the Guarantor.

9. Any settlement between the Supplier and VSY and any determination made pursuant to any provision of the Subcontract which is expressed to be binding upon the Supplier shall be immediately binding upon the Guarantor.

10. This Guarantee shall not be impaired by any loss of any security now or hereafter held by or on behalf of VSY, whether occasioned through its fault, negligence or otherwise (including without limitation any loss occasioned by the failure to register, perfect, maintain the registration or perfection of, re-register, re-perfect or renew any such security or filing of any financing statement, financing change statement or other document, instrument or thing whatsoever).

11. Demands and calls under this Guarantee may be made by VSY from time to time.

12. No delay on the part of VSY in exercising any of its options, powers or rights hereunder or any partial or single exercise thereof shall constitute a waiver thereof. No waiver of any of VSY's options, powers or rights hereunder and no modification of this Guarantee shall be effective unless the same shall be in writing, duly signed on behalf of VSY and each such waiver, if any, shall apply only with respect to the specific instance involved, and shall in no way impair the options, powers or rights of VSY or the obligations of the Guarantor hereunder in any other respect or at any other time.

13. This Guarantee is in addition and without prejudice to any security of any kind or any other Guarantee which may at any time after the date hereof be acquired by VSY and any other rights or remedies that VSY might have against the Supplier.

14. This Guarantee shall be in force and effect from the date of execution of the Subcontract until all obligations of the Supplier under the Subcontract have been fulfilled to the satisfaction of VSY.

15. This Guarantee shall be governed by the laws in force in the Province of British Columbia, Canada, and the Guarantor submits to the jurisdiction of the Canadian courts in respect of this Guarantee.

IN WITNESS WHEREOF this Guarantee has been executed and sealed on behalf of VSY by the authorized officers of VSY and by the Guarantor under its corporate seal duly attested by the hands of its respective officers authorized in that behalf.

SIGNED, SEALED AND DELIVERED:

VANCOUVER SHIPYARDS CO. LTD.

[LEGAL NAME OF PARENT COMPANY]

Signature Signature

Name/Title Name/Title

Corporate Secretary (We have authority to bind the corporation)

Insurance Certificate, Rev 0 Document #: VSY-A08.22-0028 Agreement #: [* insert Agreement #]


Unclassified Page 1 of 2 Uncontrolled when Printed Purchaser’s initials: _____ See disclosure statement on front page of the Subcontract Supplier’s initials: _____


Insurance Certificate

PM202



Insurance Certificate, Rev 0 Document #: VSY-A08.22-0028 Agreement #: [* insert Agreement #]



Insurance Certificate PM202

Purpose

The purpose of the Insurance Certificate is to demonstrate to the Subcontracting Authority that the Supplier has the required insurance coverage required by the Subcontract.

References




Format and Content

1 The Supplier to provide evidence of the required insurance coverage from the Supplier’s insurance company or companies.

Ambiguities, Inconsistencies and Conflicts Advice, Rev 0

Document #: VSY-A08.22-0029 Agreement #: [* insert Agreement #]




Ambiguities, Inconsistencies and Conflicts Advice

PM203



Ambiguities, Inconsistencies and Conflicts Advice, Rev 0




Ambiguities, Inconsistencies and Conflicts Advice PM203

Purpose

The Ambiguities, Inconsistencies or Conflicts Advice is intended to make the Subcontracting Authority aware of any ambiguities, inconsistencies or conflicts found by the Supplier relating to one or more provisions in the documents making up the Subcontract that affect the performance of the Work.

References

This DID must be read in conjunction with Schedule A (General Conditions) and the corresponding SOW reference.



Format and Content

The Ambiguities, Inconsistencies or Conflicts Advice shall be prepared in the following format and contain the following information:

1 Ambiguities, Inconsistencies or Conflicts

This section shall list the various provisions between and/or within the documents making up the Subcontract that are considered to be either ambiguous, inconsistent or in conflict. The section shall quote the putative provisions in full using underlining to show the alleged ambiguities, inconsistencies or conflict.

2 Effect Upon the Work

This section shall describe in a narrative manner the effect the identified ambiguous, inconsistent or conflicting provisions have upon the Work and the Supplier’s obligations under the Subcontract.

3 Effect on the Supplier’s Level 0 Schedule

This section shall describe in a narrative manner the effect the identified ambiguous, inconsistent or conflicting provisions have upon the Supplier’s Level 0 Schedule and Supplier’s Master Schedule (SMS), as applicable.

4 Effect on the Price, Options or Ceiling Price Offers

This section shall describe in a narrative manner the effect the identified ambiguous, inconsistent or conflicting provisions have upon the Price, Options or Ceiling Price offers.

Direction or Instruction Advice, Rev 0 Document #: VSY-A08.22-0030 Agreement #: [* insert Agreement #]




Direction or Instruction Advice

PM204



Direction or Instruction Advice, Rev 0 Document #: VSY-A08.22-0030 Agreement #: [* insert Agreement #]



Direction or Instruction Advice PM204

Purpose

The Direction or Instruction Advice is intended to make the Subcontracting Authority aware of any direction or instruction given by any individual, other than the Subcontracting Authority, that the Supplier believes adversely modifies, varies or amends the Work or the Statement of Requirements in any way whatsoever.

References




Format and Content

The Direction or Instruction Advice shall be prepared in the following format and contain the following information:

1. Identity of the Individual Providing the Direction or Instruction

The Supplier shall identify in this section the identity of the individual, other than Subcontracting Authority, who the Supplier claims has directed or instructed it in a manner which constitutes an unauthorised modification of the Work or the Statement of Requirements.

2. Date, Time, Receiver and Manner the Direction or Instruction was Given

The Supplier shall state in this section when the direction or instruction was given, to whom the direction or instruction was given, and whether the direction or instruction was given orally or in writing.

3. Nature of the Direction or Instruction

The Supplier shall describe in this section the nature of the direction or instruction and attach a copy of the direction or instruction (if given in writing) and any supporting documentation.

4. Effect Upon the Work and/or the Subcontract

The Supplier shall describe in this section the effect upon the Work and/or the Statement of Requirements that the direction or instruction will or may cause, together with supporting documentation.

5. Subcontract Provisions and Requirements

The Supplier shall identify in this section those Subcontract provisions in the Subcontract that are affected by the direction or instruction.

Non-Compliant Issued Property/Issued Document Advice, Rev 1





Non-Compliant Issued Property/Issued Document Advice

PM205



Non-Compliant Issued Property/Issued Document Advice, Rev 1




Non-Compliant Issued Property/Issued Document Advice PM205

Purpose

The Non-Compliant Issued Property Advice is intended to make the Subcontracting Authority aware of any Claim by the Supplier that any items, facilities, utilities or services furnished by the Purchaser and/or the Customer to the Supplier in order for the Supplier to perform the Work is late, inadequate, defective, insufficient or non-compliant to the agreed standard or configuration. The Issued Property is listed as an Appendix (Supplier’s Requirements) in the Articles of Agreement.

References




Format and Content

The late, inadequate, defective, insufficient or non-compliant Issued Property shall be prepared in the following format:

1 List of items furnished by the Purchaser and/or the Customer to the Supplier

The Supplier shall list in this section all items furnished by the Purchaser and/or the Customer to the Supplier.

2 List of services furnished by the Purchaser and/or the Customer to the Supplier

The Supplier shall list in this section all services furnished by the Purchaser and/or the Customer to the Supplier.

3 Financial arrangements relating to the use of the furnished items or furnished services.

The Supplier shall describe all the financial arrangements, if any, relating to each item furnished and/or each service provided to it.

4 Agreed Delivery Date

The Supplier shall set out the agreed delivery dates for the furnished items and/or services.

5 Nature of the Defect or Insufficiency

The Supplier shall identify in this section the exact identity of the furnished item and/or service that is said to be late, inadequate, defective or insufficient and a detailed account of the complaint. This section shall also include the date and time when the late, inadequate, defective or insufficiency was known, when such was first made known to the Subcontracting Authority and all steps taken since that time to mitigate any delay or disruption to the Work.

6 Effect of the Complaint

The Supplier shall describe in this section the effect the complaint has or will have on the performance of the Work and/or delivery of the Deliverables to the quality standards and Delivery Dates.

Obsolescence Advice, Rev 0 Document #: VSY-A08.22-0032 Agreement #: [* insert Agreement #]




Obsolescence Advice

PM206



Obsolescence Advice, Rev 0 Document #: VSY-A08.22-0032 Agreement #: [* insert Agreement #]



Obsolescence Advice PM206

Purpose

The purpose of the Obsolescence Advice is to make the Subcontracting Authority aware of any obsolescence relating to the Deliverables (other than Services) supplied by the Supplier or the Supplier’s lower tier suppliers (i.e. Sub-supplier).

References




Format and Content

The Obsolescence Advice shall be prepared in the following format:

1 Identification of the Obsolete Deliverable (other than Services)

This section shall identify the Deliverable (other than Services) that is obsolete by reference to the provision in the Subcontract (i.e. SLIN, line item of the Covering Purchase Order, description of the Equipment or Item of the Equipment, Supplier’s part number, etc.)

2 Reasons for the Obsolescence

This section shall state why the Equipment or item of the Equipment has become or will be obsolete.

3 Supplier’s Recommendation

This section shall describe the Supplier’s proposed recommendation, solution or one or more options to overcome the obsolescence.

Discontinuance Advice, Rev 0 Document #: VSY-A08.22-0033 Agreement #: [* insert Agreement #]




Discontinuance Advice

PM207



Discontinuance Advice, Rev 0 Document #: VSY-A08.22-0033 Agreement #: [* insert Agreement #]



Discontinuance Advice PM207

Purpose

The purpose of the Discontinuance Advice is to make the Subcontracting Authority aware of any intentions or plans by the Supplier and its lower tier suppliers (i.e. Sub-supplier) to discontinue the provision, supply and support of any Deliverable supplied under the Subcontract.

References




Format and Content

The Discontinuance Advice shall be prepared in the following format:

1 Identification of the Discontinued Deliverable

This section shall identify the Deliverable that will be discontinued by reference to the provision in the Subcontract (i.e. Covering Purchase Order number, description of the Equipment or Item of the Equipment, Supplier’s part number, SLIN etc.);

2 Identification of the Discontinued Deliverable

This section shall identify any Deliverable that has/will be discontinued by reference to the SOW, SDRL and DID set out in the Subcontract.

3 Reasons for the Discontinuance

This section shall state why the Equipment, items of the Equipment, Deliverable Software or Data Item will be discontinued.

4 Support Obligations

This section must address any support obligations required in the Subcontract that may be, will be affected by the discontinuance.

5 Supplier’s Recommendation

This section shall describe the Supplier’s proposed recommendation, solution or one or more options to overcome the discontinuance.

Claims Advice, Rev 0 Document #: VSY-A08.22-0034 Agreement #: [* insert Agreement #]




Claims Advice

PM208



Claims Advice, Rev 0 Document #: VSY-A08.22-0034 Agreement #: [* insert Agreement #]



Purpose

A Claims Advice (including IP Infringement Claims) is intended to make the Purchaser aware of the basis and quantum of any and all Claims for delay and disruption, damages, demands, initiation of mediation, arbitral or judicial proceedings, liens, or causes of action of any nature.

References



The Supplier’s Claim Advice shall be prepared in the following format and contain the following information:

1 Background

This section shall set out the background facts required to understand the Claim.

2 Legal Basis

This section shall describe the legal basis for the claim.

3 Quantum

This section shall describe the basis of calculating the value of the amount claimed.

Special Instructions

None.

Claims Advice PM208

Denial of Access Advice, Rev 0 Document #: VSY-A08.22-0035 Agreement #: [* insert Agreement #]




Denial of Access Advice

PM209



Denial of Access Advice, Rev 0 Document #: VSY-A08.22-0035 Agreement #: [* insert Agreement #]



Denial of Access Advice PM209

Purpose

The Denial of Access Advice is intended to make the Subcontracting Authority aware of any Claim by the Supplier that, following agreement with the Purchaser regarding a date, time and place for access to the Ship in response to a Call-Off Instruction (COI) for Services, the Ship's systems, Equipment or space is denied by a party having custody and control of the Ship, Ship's systems, Equipment or space.

References




Format and Content

The Denial of Access Advice shall be prepared in the following format:

1 Denial of Access to the Ship, Ship's systems, Equipment or Space

The Supplier shall identify in this section the exact nature of the complaint. The description shall include the following information:

(a) Date and time the Supplier was instructed to attend the Purchaser’s premises and/or Ship to perform Services with respect to the Ship, Ship's systems, Equipment or space (i.e. the COI information);

(b) Date and time of Supplier’s request for access to the Ship, Ship's systems, Equipment or space and the identity of the individual to whom the request was made;

(c) Date and time of Purchaser’s approval and the identity of the individual who gave the approval; and

(d) Nature of the complaint.

2 Effect of the Complaint on the Work.

The Supplier shall provide a narrative as to the effect on the Work.

Objection Advice, Rev 0 Document #: VSY-A08.22-0036 Agreement #: [* insert Agreement #]




Objection Advice

PM210



Objection Advice, Rev 0 Document #: VSY-A08.22-0036 Agreement #: [* insert Agreement #]



Objection Advice PM210

Purpose

The Objection Advice is intended to make the Subcontracting Authority aware of any objection the Supplier has to the Purchaser’s determination of a Dispute or non-conformity to the requirements of the Subcontract.

References




Format and Content

The Objection Advice shall be prepared in the following format and contain the following information:

1 Background

This section shall set out the background facts required to understand the Claim.

2 Dispute or Non Conformity

This section shall describe the nature of the Dispute or the non-conformity complained of.

3 Objection

This section shall describe nature of the Supplier’s objection.

4 Impact of the Dispute or Non Conformity

This section shall describe the adverse impact of the Dispute or the non-conformity on the Work.

Significant Event Advice, Rev 0 Document #: VSY-A08.22-0179 Agreement #: [* insert Agreement #]




Significant Event Advice

PM211



Significant Event Advice, Rev 0 Document #: VSY-A08.22-0179 Agreement #: [* insert Agreement #]



Significant Event Advice PM211

Purpose

A Significant Event Advice is intended to make the Purchaser aware of any upcoming significant incidents in connection with the Work including: (a) an accident involving harm to personnel or to facilities; (b) any event that materially impacts, or could reasonably be expected to materially impact cost or quality, including any indication of labour problems which may bring about a strike, lockout or work slowdown; (c) any liens or other encumbrances placed on the Work; (d) any actual or threatened legal proceedings by a third party that could materially affect the Work; or (e) an event that creates media interest in respect to the Project.

References



1 To the extent known at the time, the Supplier must indicate:

(a) the nature of the incident;

(b) its possible effect on the conduct and performance of the Work;

(c) the respective contractual obligations of the Supplier;

(d) the respective contractual obligations of the Purchaser; and

(e) any proposed solutions, preventive actions or work around or damage control plans.


None.

Supporting Documents to Claims Advice, Rev 0





Supporting Documents to Claims Advice

PM213



Supporting Documents to Claims Advice, Rev 0




Supporting Documents to Claims Advice PM213

Purpose

The Supporting Documents to Claims Advice (including IP Infringement Claims) is intended to make the Purchaser aware of the documentation supporting a Claims Advice (see DID PM208).

References



1 The Supplier’s supporting documentation shall be prepared in the following format and contain the following information:

(a) Background

This section shall set out the background facts required to understand the claim.

(b) Legal Basis

This section shall describe the legal basis for the claim, namely: one founded in contract, tort, statute or combination of one or more. Specific quotes of any clauses, sections and legislation relied upon shall be stated.

(c) Supporting Facts and Documents

This section shall describe the specific facts and documents underpinning the legal basis of the claim. Copies of the supporting documentation shall be attached.

(d) Witnesses

This section shall identify (i.e. names and addresses) potential witnesses, including any ‘expert witnesses’, and brief descriptions of the nature of their evidence in the form of a signed witness statement.

(e) Quantum

This section shall describe the basis of calculating the value of the amount claimed. Copies of supporting documentation shall be attached.


None.

Red Flag Report, Rev 0 Document #: VSY-A08.22-0037 Agreement #: [* insert Agreement #]




Red Flag Report

PM230



Red Flag Report, Rev 0 Document #: VSY-A08.22-0037 Agreement #: [* insert Agreement #]



Red Flag Report PM230

Purpose

The Red Flag Report is intended to make the Subcontracting Authority aware of any unforeseen or unforeseeable event which has or could affect the performance of the Work, the achievement of the Supplier’s Level 0 Schedule, Milestone, or Delivery Date for any Deliverable.

References




Format and Content

The Red Flag Report shall be brief, concise, but contain sufficient information to allow an initial high level appraisal by the Subcontracting Authority of the unforeseen event being reported.

The Red Flag Report shall not be delayed due to a lack of supporting documentation or information which shall be contained in a follow-up Recovery Plan (see SDRL PM231 and DID PM231).

The Red Flag Report shall cover the following points:

1. the nature and description of the unforeseen event;

2. when the Supplier first became aware of the event; and

3. the potential effect of the unforeseen event on:

(a) the Purchaser’s Technical Requirements;

(b) Data Items already submitted and to-be-submitted;

(c) Services to be performed;

(d) the scheduled activity on the “Critical Path” of the Supplier’s Master Schedule (SMS) that has/may/will be adversely affected;

(e) the effect, if any, on the Supplier’s Level 0 Schedule, Milestones and Delivery Dates for the Deliverables; and

(f) the Delivery Date for a Recovery Plan (see SDRL PM231 and DID PM231).

Recovery Plan, Rev 1 Document #: VSY-A08.22-0038 Agreement #: [* insert Agreement #]


Unclassified Page 1 of 2 Uncontrolled when printed Purchaser’s initials: _____ See disclosure statement on front page of the Subcontract Supplier’s initials: _____


Recovery Plan

PM231



Recovery Plan, Rev 1 Document #: VSY-A08.22-0038 Agreement #: [* insert Agreement #]


Unclassified Page 2 of 2 Uncontrolled when printed Purchaser’s initials: _____ See disclosure statement on front page of the Subcontract Supplier’s initials: _____

Recovery Plan PM231

Purpose

The Recovery Plan is intended to make the Subcontracting Authority aware of the Supplier’s plan to recover from any adverse deviation from the Schedule F (Supplier’s Level 0 Schedule), Milestone and/or delivery of a Deliverable to the Delivery Date. It is a follow up to a Red Flag Reports (see SDRL PM230 and DID PM230).

References




Format and Content

1 The Recovery Plan shall fully disclose all pertinent information in sufficient detail to demonstrate, by objective evidence, that the Supplier is using all reasonable commercial efforts to recover the Supplier’s Level 0 Schedule, Milestone and/or Delivery Date for the Deliverable or Deliverables without adversely affecting the Purchaser.

2 The Recovery Plan shall explain in detail:

(a) the various options and steps that the Supplier proposes to take in order to minimize the impact of the delay;

(b) any impact on the Work, the Supplier’s Solution, the Supplier’s Level 0 Schedule and Costs for each option described in section (a) above;

(c) any alternative sources of factory space, equipment, materials or labour if the event causing the delay involves one or more of them;

(d) any alternative technical solution; and

(e) any required changes to payment terms.

3 The Supplier shall deliver with the Recovery Plan, copies of all supporting documentation available at the time of delivery.

Project Execution Plan, Rev 0 Document #: VSY-A08.22-0039 Agreement #: [* insert Agreement #]




Project Execution Plan

PM250






Project Execution Plan PM250 Purpose

The Project Execution Plan (PEP) provides an overview of the different Project processes and how they fit together to form a totally integrated management system for the Project.

The Supplier uses the PEP, including or supplemented by subordinate plans, to provide direction and guidance to the Supplier’s management team responsible for the conduct of the Work under the Subcontract.

The Purchaser uses the PEP to: (a) gain visibility into the Supplier’s planning; (b) understand and evaluate the Supplier’s approach to managing the Project; and together with the Supplier’s Schedule, (c) provide input into the Purchaser’s planning.

The PEP is the primary plan for the Subcontract. All other plans related to the Subcontract fit beneath the umbrella of the PEP.

References




Format and Content

1. General

The PEP shall be a stand-alone document that provides sufficient information to allow the reader to understand how the Project will be managed without referring to other documents. The Supplier shall not simply reference a document, procedure or standard without providing an overview of the material referenced.

The PEP shall be the master planning document, integrating, summarising and referencing other Project plans and schedules required in this DID and elsewhere in the Subcontract.

The following paragraphs outline the framework of the PEP. This framework should not limit the Supplier in developing the PEP, which must reflect the way in which the Supplier manages the performance of its Subcontract obligations.

The PEP may be divided into volumes, sections and/or sub plans provided that the head document links all sub documents together as a cohesive whole.

2. Project Objectives

The PEP shall describe the objectives related to success of the Project overall, with particular emphasis on the Subcontract. Project objectives shall include capability, cost, schedule, effective issues management, avoidance of conflict, the environment, public good, safety, law, and other outcomes as appropriate.

3. System Overview

The PEP shall:

(a) give a brief overview of the System and/or Equipment being developed and its purpose;

(b) clearly state the operational capability that the System and/or the Equipment is delivering;

(c) identify the key functions of the System and/or the Equipment;

(d) identify major subsystems within the System and/or Equipment;

(e) show the context of the System and/or Equipment within the next higher-level system, as appropriate; and

(f) identify major interfaces.




4. Project Scope

The PEP shall clearly identify the scope of Work to be undertaken by the Supplier and its lower tier suppliers (i.e. Sub-suppliers).

5. Project Organisation

The PEP shall describe the organisational structure responsible for managing and performing the Work under the Subcontract. The Supplier may reference or include its Project Resourcing Strategy as part of this PEP. The content shall include:

(a) the Supplier's company organisation structure;

(b) the Supplier's project management organisation;

(c) the Supplier's contractual relationship with lower tier suppliers (i.e. Sub-suppliers) for the purpose of the Project;

(d) the identification of ‘Key Staff’ positions within the Supplier’s organisation;

(e) the definition of the person/position specifications, or responsibilities and authorities for each ‘Key Staff’ position within the Project team organisation and the skill sets needed to fill that position; and

(f) the identification of relevant background skills and experience of each ‘Key Person’.

6. Team and Sub-Team Composition and Purpose

The PEP shall identify, and describe the make-up and purpose of, each team to be employed in performance of the Project. Example teams are:

(a) Integrated Product Teams (e.g. engineering, operations, QA, procurement, etc…);

(b) systems engineering team (as appropriate);

(c) ILS team;

(d) financial team; and the

(e) IRB team.

7. Structure of Supplier Plans

The PEP shall contain a structured, indentured list of the plans to be used by the Supplier in the execution of the Subcontract, showing the hierarchical relationship of the plans.

8. Work Breakdown Structure (WBS) and the Ship Work Breakdown Structure (SWBS)

The PEP shall use, where applicable the Purchaser’s Work Breakdown Structure (WBS) as well as the Purchaser’s SWBS.

9. Supplier’s Schedule

The PEP shall contain an overview of the Supplier’s Schedule, including the critical path, to the level of detail to show milestones for activities.

10. Staff Skills Profile

The PEP shall contain aggregate, labour-category-based, time-phased plans for the use of the Supplier’s human resources in the performance of the Work. The staff skills profile shall be consistent with the identified work and the Supplier’s Schedule identified in section 9 of this DID.

11. Business Resource Planning

(a) The PEP shall demonstrate that Supplier resources are available to meet the current and future obligations of this Subcontract. In particular, addressing: (i) obligations in regard to current and future project/work;

(j) use of resources such as:

i. human capital in relation to current and envisaged Projects;




ii. financial resources;

iii. physical resources;

iv. intellectual property resources;

v. other organisational resources; and

vi. lower tier supplier relationships and other supply arrangements;

(b) details of the Supplier's capabilities to satisfactorily discharge its responsibilities under the Subcontract in relation to the above; and

(c) arrangements for reprioritising resources across the term of the Subcontract.

12. Project Planning and Control

(a) The PEP shall contain an overview of the processes used by the Supplier to ensure the integration of technical, cost and schedule planning and control for the management of the Project.

(b) The PEP shall identify the tools to be used in support of project management, and shall describe the planned purpose and method of usage of each tool. Example of tools that may be addressed are management information systems, databases, spreadsheets, cost estimating tools, network scheduling tools and decision analysis tools.

13. Engineering Program

The PEP shall contain an overview of the project engineering program, referring to the detailed engineering plans as appropriate.

14. Integrated Logistics Support (ILS) Program

The PEP shall contain an overview of the project ILS program, referring to the detailed ILS plans as appropriate.

15. Configuration Management

The PEP shall contain an overview of the Configuration Management arrangements for the Subcontract, referring to the Configuration Management Plan (CMP) as appropriate.

16. Intellectual Property Management

The PEP shall provide contain an overview of the Intellectual Property Management arrangements for the Subcontract, referring to the Intellectual Property Plan (IPP) as appropriate.

17. Project Risk Management

The PEP shall contain an overview of the Risk Management processes, tools and ‘Risk Register’ to be used by the Supplier.

18. Quality Management

The PEP shall provide contain an overview of the Quality Assurance arrangements for the Subcontract, referring to the Quality Assurance Plan as appropriate.

19. Defect Management

The PEP shall provide an overview of the Defect Rectification process, referring to the Defect Rectification and Warranty Plan as appropriate.

20. Project Issue Management

The PEP shall describe the Supplier’s processes and tools used for managing issues for the Project. Typical issues include:

(a) Action Items from Meetings;

(b) Issues arising from Meetings;

(c) corrective actions;

(d) issues arising from the metrics collection and analysis;




(e) issues arising from deviation of progress against plan; and

(f) issues arising from reviews of process application.

Note 1: In this context, ‘issues’ are items whose progress needs to be monitored, but which are not included in the EVM plans because they are either too short-term or too insignificant. They do not appear in the Risk Register because they are technically not risk, as they do not represent any cost or schedule threat to the project at this point in time.

Note 2: see the Action Item and Issue Status Report (SDRL PM273 and DID PM273).

21. Management of Lower Tier Suppliers

The PEP shall provide an overview describing how the Supplier intends to manage its lower tier suppliers including:

(a) the communications, meeting and review plan for each lower tier supplier;

(b) the method for ensuring that each lower tier supplier has an integrated technical, cost and schedule control mechanism in place;

(c) the method for ensuring that each lower tier supplier is collecting and analysing relevant Project metrics to enable progress to be tracked against plan; and

(d) the method for ensuring that each lower tier supplier is managing its own lower tier suppliers.

22. Security Management

The PEP shall include an overview of the processes implemented by the Supplier to satisfy the Security Requirements set out in Schedule D1 (General Conditions) and Part 7 (Security) of Schedule D1 (SOW) and shall refer to any separate Security Management Plan if such a plan is required under the Subcontract.

23. Human Resources

The PEP shall contain the Supplier’s staffing strategy, including the Supplier’s approach to recruiting and retaining staff. The Supplier may reference or include its Project Resourcing Strategy as part of this PEP.

24. Issued Property

The PEP shall describe the Supplier’s arrangements for the receipt, custody, storage, care, maintenance and use of any Issued Property provided to the Supplier under the Subcontract and listed in the Articles of Agreement.

Supplier’s Master Schedule, Rev 0





Supplier’s Master Schedule

PM251

Prepared by : Vancouver Sh ipyards Co. L td .

2 Pe mber ton Ave . Nor th Van couver , BC, Canada, V7 P 2R2 Te l : (604) 988-3111 Fax: (604) 984-1636






Supplier’s Master Schedule PM251 Purpose

The Supplier’s Master Schedule (SMS) describes the Supplier’s planned sequence of activities, internal milestones, Subcontract Milestones, and decision points to enable the Work and obligations of the Subcontract to be performed and met. Additionally, the SMS defines the current Project schedule status, comparing the current schedule with the Subcontracted schedule, a high level of which is set out in the Supplier’s Level 0 Schedule (see Schedule F). The SMS also compares the current schedule status with any applicable baseline schedule.

The Supplier uses the SMS, including or supplemented by subordinate schedules, to:

(a) plan the activities and sequencing of those activities to achieve the requirements of the Subcontract; and

(b) provide schedule direction and status to the management team responsible for conduct of the work.

The Purchaser uses the SMS to:

(a) ensure that that it aligns to the Purchaser’s Integrated Master Schedule (IMS) for the Project);

(b) gain visibility into the Supplier’s planning;

(c) understand and evaluate the Supplier’s approach to meeting the requirements of the Subcontract;

(d) assist with monitoring the progress of the Supplier in meeting the requirements of the Subcontract; and

(e) as a source of input to planning performed by the Purchaser’s planning and estimating department.

References




Format and Content

General

The Supplier’s Schedule shall:

(a) be developed using Primavera P6 or a similar program compatible with Primavera P6;

(b) support the PEP and (if required) the Purchaser’s Integrated Master Schedule (IMS) for the Project;

(c) follow the Purchaser’s WBS and SWBS (if required as part of Part 15 Estimating of the SOW);

(d) be resource loaded by identifying total hours against each activity (product or support task);

(e) not exceed the resource hours / allocation submitted in its relating proposal;

(f) identify the durations of each activity (if required to align with the AEP timeline);

(g) identify the float available on each activity;

(h) identify the milestones of each activity in accordance with the relating AEP (if required); and

(i) identify its critical path(s).





Narrative Analysis

If not addressed in the associated Status Report, each submission of the SMS shall contain an explanation of the cause of each rescheduled or forecast date that is later than the milestone's, or activity’s original scheduled date for the issue of the SMS in which the rescheduled date or forecast date is first reported. Subsequent issues shall address changes from previously reported dates. The narrative analysis for the SMS shall address possible impact on other milestones and activities, and shall describe recovery plans to minimise the impact (see also SDRL PM231 and DID PM231 Recovery Plan).

Intellectual Property Management Plan, Rev 0





Intellectual Property Management Plan

PM255







Intellectual Property Management Plan PM255

Purpose

The Intellectual Property Management Plan (IPMP) describes the Supplier’s plans and Intellectual Property management activities to satisfy the intellectual property requirements under the Subcontract.

The IPMP must be developed and prepared to:

(a) define the Intellectual Property management requirements relevant to all tasks for all Subcontracts relating to the Project;

(b) track all Subcontract activities which receive, use, produce or manage Intellectual Property; and

(c) record, on an on-going basis, in an Intellectual Property Schedule as detailed in this DID, all applicable Intellectual Property information generated or acquired in the course of all Subcontract activities.

The Intellectual Property Schedule in the IPMP must provide up-to-date information on the nature and status of all Intellectual Property.

References




Format and Content

1 The IPMP must be in the Supplier's format, but must contain, as a minimum, the Data described below.

2 The Title page must contain the following information:

(a) Title Page;

(b) Title: Intellectual Property Management Plan – [* insert name of Project] – [* insert Phase as applicable] - [* insert DD MMM YY];

(c) Subcontract number: [* insert number];

(d) SWBS number: [* insert number];

(e) Prepared By: [* insert Subcontractor’s name and address]; and

(f) Authenticated By: [* insert Subcontractor approval signature(s) and date].

3 The IPMP must include the following information, with each section clearly and separately identified:

(a) Section A: Overview and Summary of Usage Restrictions

This section must provide an overview of the IPMP and how the Subcontractor will protect, safe-guard and use Intellectual Property. This includes how the Intellectual Property will be stored in hard and soft copy. Also, any restrictions that might apply on the Customer’s use of such Intellectual Property (including third parties that may be used by the Customer) are to be summarized.





(b) Section B: Management and Monitoring or Intellectual Property

This section must describe the Subcontractor’s processes for managing (i.e. monitoring, recording and reporting on) the Intellectual Property created, modified or acquired under the Subcontract, including the creation and maintenance of an ‘Intellectual Property Database’.

3 Section C: Intellectual Property Schedule

Note: The Intellectual Property Schedule may be prepared using the Subcontractor’s own format and contain information to enable the Customer to clearly understand the Intellectual Property and licensing considerations for each document used and or produced under the Subcontract. A Microsoft Excel spreadsheet is preferred and must contain, as a minimum, the following elements for each item:

(a) a unique configuration identifier (e.g. correlating to a SWBS number, document ID or to an item listed in the configuration baseline(s));

(b) title/description;

(c) Deliverable indicator (Yes/No);

(d) artefact type (e.g. drawing, Report, Specification, manual, Data Item);

(e) originator of artefact (e.g. Subcontractor, specific OEM’s name, etc…);

(f) format of artefact (e.g. 2D CAD drawing, MS-Word, 3D model);

(g) Intellectual Property designation (i.e. ‘No IP’: ‘Only Background Information’; ‘Some Background Information’; ‘Only Foreground Information’; and ‘Background Information and Foreground Information’);

(h) Intellectual Property location within each artefact;

(i) applicable Intellectual Property owner or licensor (if different from the owner);

(j) Intellectual Property Rights (e.g. Full License Rights, Permitted Uses, etc…);

(k) license requirements to use Intellectual Property, as applicable;

(l) time/phase when used; and

(m) remarks / additional info, as applicable.

Configuration Management Plan, Rev 0 Document #: VSY-A08.22-0043 Agreement #: [* insert Agreement #]




Configuration Management Plan

PM256






Configuration Management Plan DID PM256

Purpose

The Configuration Management Plan (CMP) defines the Supplier’s policy, procedures and responsibilities for configuration management during the conduct of the Work. The CMP shall include the definition of Configuration Management (CM) activities for all Configuration Items (CI) related to the Subcontract.

The Supplier uses the CMP to manage, coordinate and monitor the CM program for the Subcontract.

The Purchaser uses the CMP to:

(a) evaluate the way the Supplier will conduct the Subcontract;

(b) assess the adequacy and monitor the progress of the Subcontract; and

(c) identify the Purchaser’s involvement in the CM program.

The CMP will be traceable from the earlier CMP versions and earlier Phase of the Project as appropriate.

References




Format and Content

1 Configuration Management Organisation

The CMP shall describe the configuration management organisation for the Subcontract, including:

(a) the functional structure of the Supplier's and major Sub-suppliers’ CM organisations;

(b) lines of authority within the CM organisation and between the CM and engineering and project management organisations;

(c) details of the formal links between the Supplier's CM organisation and lower tier suppliers (i.e. Sub-suppliers); and

(d) the responsibilities and authority of participating groups, organisations and individuals involved in CM, including their role in Configuration Control Boards (CCBs) and Interface Control Working Groups (ICWGs).

2 Configuration Management Integration

The CMP shall:

(a) identify and detail the integration of CM functions with other Subcontract activities;

(b) detail the Purchaser’s involvement and responsibilities in the Supplier’s CM process, including the Purchaser’s involvement in CCBs and ICWGs (if called for in Schedule D1 (SOW); and

(c) describe the integration of CM functions with other Subcontract activities, such as Design Reviews and Acceptance Events (see Part 3 (Engineering) of Schedule D1(SOW)).




3 Configuration Management Phasing and Milestones

The CMP shall describe and graphically portray the sequence of events and milestones for implementation of CM in phase with major Subcontract milestones and Acceptance Events. Where possible, this shall be done by cross-referencing to the applicable document. Events should include:

(a) the release and submission of Configuration Documentation in relation to Subcontract events (e.g. Design Reviews, Acceptance Events, etc…);

(b) the establishment of internal developmental configuration and Subcontract baselines;

(c) the implementation of internal and Purchaser configuration control;

(d) the establishment of CCBs and ICWGs; and

(e) the conduct of configuration audits.

4 Data Management

(a) Specification Tree

The CMP shall define the relationship between the Specification tree, as captured in the technical documentation tree and Configuration Item (CI) list and define how these will be managed.

(b) Document Management

The CMP shall define the process and procedures to be used for managing all documents and documentation required for the conduct of the Subcontract, including both formal deliverables and internal Supplier and lower tier supplier documentation (i.e. Data Items or documentation received from Sub-subcontractors).

(c) Drawing Management

The CMP shall define the process and procedures to be used for managing the engineering drawings and shall include, as a minimum:

(i) identification of the engineering drawing practices standard used both by the Supplier and lower tier suppliers;

(ii) a statement of any need for deviation from the content of this standard during the Project; and

(iii) an overview of the drawing management system including:

a. a description of any information system tools used (e.g. Drawing Management Database) to support the drawing management system; and

b. a definition of the drawing procedures to be used.

(d) Configuration Identification

(i) Configuration Identification

The CMP shall define the procedures for the selection of CIs, and detail the criteria used for their selection. The CMP shall, by inclusion or reference, define the list of CIs and their respective specifications and other defining top-level documentation.

(ii) Configuration Identifiers

The CMP shall define the procedures for assignment and physical marking of configuration identifiers, including:

a. document numbers and revision markings to documentation;

b. nomenclature, serial numbers and part numbers to hardware; and

c. software identifiers to Software and firmware.

(iii) Developmental Configuration




The CMP shall define the procedures for establishing and controlling the documentation and repositories containing the elements of the developmental configuration, including:

a. the procedures for reporting, processing, tracking, rectifying and recording problems identified in the documentation defining the developmental configuration; and

b. the procedures for the establishment and control of a documentation library, drawing library and software development library.

(iv) Configuration Baselines

The CMP shall define the requirements for establishing Configuration Baselines, and include:

a. the procedures for the establishment of, at least, the Functional, Allocated and Product Baselines; and

b. the documentation to be used to define each baseline.

(v) Engineering and ILS Release

The CMP shall define the procedures for issuing approved configuration documentation, and amendments to this documentation, to functional activities (e.g. manufacturing, ILS, logistics, and acquisition) within the Supplier's organisation.

5 Configuration Control

(a) The CMP shall define and detail the functions, membership, responsibilities and authority of the CCBs planned for the Subcontract.

(b) The CMP shall define the procedures, including Purchaser involvement if required under Schedule D1 (SOW), and associated documentation for processing the following:

(i) classification of changes, and the level of authority for change approval/concurrence;

(ii) Subcontract Change Order Requests;

(iii) implementation of authorised Change Orders;

(iv) Major (Class I) Engineering Change Proposals (ECPs);

(v) Minor (Class II) ECPs;

(vi) requests for deviations; and

(vii) requests for concessions.

6 Configuration Status Accounting (CSA)

The CMP shall define the procedures for CSA, including:

(a) methods for collecting, recording, processing and maintaining the data required to provide the status of accounting information through reports and / or access to a ‘CSA Database’ (CSAD);

(b) a complete description of the CSAD with respect to the areas related to:

(i) the identification of the currently approved configuration documentation and configuration identifiers associated with each CI;

(ii) the status of proposed engineering changes from initiation to implementation;

(iii) the results of configuration audits, and the status and disposition of discrepancies;

(iv) the status of requests for deviations;

(v) the ability to trace changes from the baseline documentation of each CI; and

(vi) the effectiveness and installation status of configuration changes to all CIs at all locations; and




(vii) identification and description of the reports available from the CSAD and their frequency of reporting and distribution.

7 Configuration Audits

The CMP shall:

(a) describe the Supplier’s methodology and processes to establish and conduct Functional Configuration Audits and Physical Configuration Audits;

(b) detail, for each audit, the proposed audit venue(s) and the details of the organisation(s) and individuals involved in the audits and their specific audit responsibilities;

(c) define entry, exit and checklist items for each of the audits;

(d) describe the plans, procedures, documentation, and schedules for the audits;

(e) describe the format for reporting results of in-process audits; and

(f) describe the format for recording and managing Corrective Action Requests (CARs) resulting from an audit.

8 Control of the Supplier’s Lower Tier Suppliers

The CMP shall define the methods used to ensure that lower tier suppliers comply with the CM requirements of the Subcontract.

9 Master Record Indexes

If required under the Subcontract, the CMP shall define the production and management of Master Record Indexes (MRIs), including schedule, organisational responsibilities, and maintenance.

Risk Management Plan, Rev 0 Document #: VSY-A08.22-0044 Agreement #: [* insert Agreement #]


Unclassified Uncontrolled when Printed

Page 1 of 2

Purchaser’s initials: _____ See disclosure statement on front page of the Subcontract Supplier’s initials: _____


Risk Management Plan

PM257




Risk Management Plan, Rev 0 Document #: VSY-A08.22-0044 Agreement #: [* insert Agreement #]



Page 2 of 2


Risk Management Plan PM257

Purpose

The Risk Management Plan (RMP) defines the Supplier's procedures for identifying, capturing, analysing, assessing, prioritising, monitoring and reviewing Project risks and opportunities and details the responses required to handle those risks and utilise opportunities. The RMP also defines the Supplier’s processes towards contribution to and maintaining its risks and opportunities on the IPT Risk Register and procedures for using the IPT Risk Register to capture the dynamic elements of the risk management process.

The Supplier uses the RMP to define the organisational elements and procedures that it will apply to the management of risk throughout the period of performance.

The Purchaser uses the RMP to assist with monitoring the performance of the Supplier.

References




Format and Content

1 The RMP shall include:

(a) the risk-management organisation to be applied to the Project, including clear definitions of responsibilities for the Project Management, the Engineering, the ILS and the IRB aspects of risk management;

(b) procedures for identifying and capturing risks (Note: A rigorous risk-identification process is considered by the Purchaser to be essential to the management of risk);

(c) procedures for analysing risks;

(d) procedures for assessing and evaluating risks;

(e) establishing a risk reserve ($)

(f) procedures for treating risks, including:

i. avoiding the risk; ii. reducing the likelihood of the risk; iii. reducing the consequence of the risk; iv. transferring the risk; and v. retaining the risk;

(g) procedures for reporting risks

(note that the Supplier is to contribute towards a IPT Risk Register and IPT risk management meeting);

(h) procedures for monitoring and reviewing risks; and

(i) the processes for integrating the risk-management activities into project planning and control (e.g. EVM, etc.).

Risk Register, Rev 0 Document #: VSY-A08.22-0045 Agreement #: [* insert Agreement #]



Page 1 of 2



Risk Register

PM258



Risk Register, Rev 0 Document #: VSY-A08.22-0045 Agreement #: [* insert Agreement #]



Page 2 of 2


Risk Register PM258

Purpose

The Risk Register captures the dynamic elements of the risk management process as described in the Risk Management Plan (see SDRL PM257 and DID PM257).

References



This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) of Schedule D1 (SOW) and Part 1 of Schedule D2 (SDRL).

Format and Content

1 The Risk Register shall be based in electronic form (e.g. database or spreadsheet), but when printed, shall consist of a table with an entry for each risk in the Risk Register (or defined subset of the Risk Register).

2 For each risk, the Risk Register shall include:

(a) the SWBS element number;

(b) a risk identification number;

(c) a brief outline of risk;

(d) the risk priority;

(e) the source of risk (e.g. whether the risk stems from the Purchaser or from the Supplier (including lower tier suppliers));

(f) the likelihood of the risk event;

(g) the consequence of the risk event in terms of Life Cycle Cost (LCC), Project cost, Project schedule and/or performance or suitability of the Deliverables or support to the Deliverables;

(h) the individual responsible for treating the risk; and

(i) the risk-treatment option(s) (i.e. avoid, reduce the likelihood, reduce the consequence, transfer, or retain).

3 For risks that are to be treated, the Risk Register shall include:

(a) the risk-treatment plan;

(b) the work package ID, budget and schedule allocated to the risk-treatment plan; and

(c) progress against the risk-treatment plan.

(d) The Risk Register shall also contain:

(i) the total cost exposure caused by all risks to the Supplier's performance of its obligations;

(ii) the budget reserve remaining for cost risks;

(iii) the total schedule exposure caused by all risks to the Supplier's performance of its obligations; and

(iv) the total schedule reserve remaining.

Defect Rectification and Warranty Procedure, Rev 0




Page 1 of 2



Defect Rectification and Warranty Procedure

PM259



Defect Rectification and Warranty Procedure, Rev 0




Page 2 of 2


Defect Rectification and Warranty Procedure PM259

Purpose

The Defect Rectification and Warranty Procedure is intended to make the Subcontracting Authority aware of the process the Supplier proposes to employ to fulfil its Defect Rectification and Warranty obligations.

References




Format and Content

Supplier’s format.

The Defect Rectification and Warranty Procedure shall contain, as a minimum, the following information:

1 responsibilities and authority of the Supplier’s representatives tasked with Defect and Warranty claims;

2 procedures and instructions relating to how Defects and warranty claims are handled and processed;

3 the manner of allocation of priorities with respect to each Defect and Warranty claim;

4 monitoring the progress of each Defect Rectification and Warranty claim;

5 arrangements for the Purchaser to accept the corrected items;

6 disposal of Defective items; and

7 Defect and Warranty claim contact information:

Name: [* insert name]

Telephone Number: [* insert office telephone number]

Cell Number: [* insert cell number]

Email [* insert email address]

Status Report, Rev 0 Document #: VSY-A08.22-0047 Agreement #: [* insert Agreement #]



Page 1 of 2



Status Report

PM260




Status Report, Rev 0 Document #: VSY-A08.22-0047 Agreement #: [* insert Agreement #]



Page 2 of 2


Status Report PM260

Purpose

The purpose of the Status Report is to provide the Subcontract Authority with an up-to-date, succinct, relevant, focused, brief ‘snap shot’ view of the Supplier’s present performance and possible effect on the Project’s overall schedule. e.g. A ‘Cost, Schedule and Performance’ status report. It is to be maintained by the Representative of the Supplier responsible for managing the Subcontract. The Status Report shall be up-to-date and continuously ‘live’ on an electronic platform available to the Purchaser.

References




Format and Content

The Status Report shall, as a minimum, contain the status of the following elements of the Subcontract:

1. planned work scope completion per week and cumulative;

2. actual-to-planned work scope completion since last and cumulative;

3. variance analysis where actual work scope completion is behind planned work scope completion. Variance analysis shall segregate variance into two (2) categories:

(a) non-recoverable schedule variance (work scope planned for completion, but not accomplished and conditions will not allow recovery to schedule);

(b) recoverable schedule variance (work scope planned for completion, but not accomplished and conditions will allow for corrective action to recover to schedule);

4. root cause(s) for variance;

5. corrective action(s) to address root cause(s) of:

(a) non-recoverable schedule variance and corrective actions will address how the Supplier will prevent similar circumstances leading to further non-recoverable schedule variance

(b) recoverable schedule variance will address corrective action(s) plans to get back on schedule with estimated date of recovery

6. assessment of success of implemented corrective action(s) and modification(s) to corrective action(s) where expected recovery not being achieved;

7. a calculated Schedule Performance Index (SPI) for the week and cumulative;

8. staffing profile;

9. risk impacts and mitigation; and

10. Issues, if any.

11. The purchaser requires the attached template A or template B (as applicable to the phase) to be submitted weekly as part of its Status Report.

Progress Report, Rev 0 Document #: VSY-A08.22-0048 Agreement #: [* insert Agreement #]




Progress Report

PM261






Progress Report PM261

Purpose

The Progress Report is intended to make the Subcontracting Authority aware of the Supplier’s progress of the Work against the Supplier’s Level 0 Schedule (see Schedule F), and Supplier’s Master Schedule (SMS – see SDRL PM251 and DID PM251) as applicable. Each Progress Report is intended to be a formal, contractually significant tool to provide an objective, accurate, candid, truthful and comprehensive report as to its progress of the Work current in all respects at the time of preparation.

The Progress Report is in a pro forma template so as to permit consistency and ease of ‘backward reference’ to earlier Progress Reports. However, if the Supplier is of the opinion that the pro forma template precludes an objective, accurate, candid and truthful report as to progress of the Work being declared, then the Supplier shall add whatever additional sections to the end of the report that is considered necessary.

References




Format and Content

1 The Progress Report shall contain the following information in the following structure:

Section 0. Executive Summary

[* insert text]

Section 1. Introduction

This section shall provide an introduction identifying the following:

a. Agreement number: [*]

b. Amendment number (if any): [*]

c. Covering Purchase Order #: [*]

d. Description of the System: [*]

e. Description of the Equipment: [*]

f. Purchaser’s SWBS #: [*]

g. Change in Price since Contract Award +/-: [*]

h. Narrative for Section 1, including a summary of progress since the last Progress Report and planned progress until the next Progress Report.

[* insert text]




Section 2. Commercial

This section shall identify the following:

a. Outstanding Change Orders: Nos: [*] Dates: DDMMMYY Description: [*]

b. Outstanding Change Order Request: Nos: [*] Dates DDMMMYY Description: [*]

c. Directions from Purchaser: Nos: [*] Dates: DDMMMYY Description: [*]

d. Notices of Default: Nos: [*] Dates: DDMMMYY Description: [*]

e. Recovery Plans: Nos: [*] Dates: DDMMMYY Description: [*]

f. Disputes: Nos: [*] Dates: DDMMMYY Description: [*]

g. Claims against the Purchaser: Y/N [*] Identify: DDMMMYY Description: [*]

h. Warranty claims: Nos: [*] Dates: DDMMMYY Description: [*]

i. Anticipated Defaults: [*]

j. Narrative for Section 2

[*insert text]

Section 3. Financial


a. Payments made to date: Planned: $ [*] Actual: $ [*]

b. Payments claimed but not paid: $ [*] Dates: DDMMMYY

c. Claim forecast for next six (6) Months: $ [*]

d. Narrative for Section 3

[* insert text]

Section 4. Schedule


a. Revision level from Supplier's Level 0 Schedule: Rev: [*]

b. Actual revision level of Supplier’s Level 0 Schedule being used: Rev: [*]

c. If Delivery Dates not met, list and provide forecast delivery dates: Forecast Delivery Dates

Equipment DDMMMYY

On Loan Items DDMMMYY

SPT DDMMMYY

Deliverable Software DDMMMYY

Data Items DDMMMYY

Services DDMMMYY

d. List all Data Items to be delivered during the next six (6) Months: [*]




e. Planned Meetings (if any) to be held before delivery of next Progress Report:

Date(s): DDMMMYY Location(s): [*]

Subject(s): [*]

f. Status of Recovery Plans: Nos: [*] Description: [*] Forecast: DDMMMYY

g. Milestones achieved to date: Nos: [*] Dates: DDMMMYY Forecast: DDMMMYY

h. Milestones missed to date: Nos: [*] Dates: DDMMMYY Forecast: DDMMMYY

i. Reason for Milestones not achieved:

j. Narrative for Section 4:

[* insert text]

Section 5. Meetings Held Since Last Progress Report

Date(s): DDMMMYY Location: [*] Subject(s): [*]

Action Item responses from Meetings: {*]

Outstanding Action Items from Meetings: [*]

Narrative for Section 5:

[* insert text]

Section 6. Attendance at the Purchaser’s Premises and/or Ship

a. Tabulate and provide reasons for:

• Number of man days attended at Purchaser’s premises/ship since CA: [*]

• Number of man days since last Progress Report: [*]

• Nature of Work performed at Purchaser’s premises/ship since last Progress Report: [*]

• Number of man-days planned at Purchaser’s premises/ship before next Progress Report: [*]

b. Narrative for Section 6:

[* insert text]

Section 7. Engineering

This is a narrative section to describe the status and forecast for completion of the technical Work.

a. List here all Design Reviews and Acceptance Events as required by the SOW, if any, and the status against each one.

[*]

b. List here a brief summary of any ‘technical issues’ (if any) and (if available) potential solutions.




[*]

Section 8. Integrated Logistics Support (ILS) or Support

This is a narrative section to describe the status and forecast for completion of the ILS or Support Work.

a. List here all formal reviews as required by the SOW, (if any) and the status against each one.

[*]

b. List here a brief summary of any ‘support issues’ (if any) and (if available) potential solutions.

[*]

Section 9. Quality Assurance

This section contains both a narrative and numerical analysis to describe the status of the quality of the Work being performed and compliance to documented procedures.

a. List all Quality issues and concerns: [*]

b. List all Supplier’s audits: ‘planned’ and ‘actual’: [*]

c. List Supplier’s and lower tier suppliers (i.e. major Sub-subcontractors) audits: ‘planned’ and ‘conducted’: [*]

d. Status report on audit non-compliances (including corrective and preventative actions) specific to the Subcontract: [*]

e. Status of any Defects/deficiencies/non-conformances:

[* insert text

Section 10. HSE Report

Typical items to report include:

a. HSE issues and concerns: [*]

b. Incidents this month (reportable and recordable)’ [*]

Section 11. Project Management Organisation

This is a narrative section to describe the status of the Project Management organisation and whether any of the ‘Key Staff’ identified in the Project Execution Plan have ceased being employed by the Supplier or diverted to other projects or work and, if so, plans to replace them.

[* insert text]




Section 12. Resource Plan

This is a narrative section to describe the status of the Resource Plan (if required by the SOW) and to identify any changes from the Project Execution Plan.

[* insert text]

Section 13. Industrial and Regional Benefits (IRB)

This is a narrative section to describe the status of commitment against the IRB obligations and to identify any changes from the last Progress Report.

[* insert text]

Section 14. Risk Management

This is a narrative section to describe the status of management of risk and to identify any changes from the last Progress Report.

[* insert text]

Section 15. Delivery Schedule

This is a narrative section that describes the actual delivery of the Deliverables against the Delivery Dates (if not already covered elsewhere in this report).

[* insert text]

Section 16. Items Raised By Purchaser

This narrative section is to answer any questions and/or complaints that the Purchaser has raised either in response to the last Status Report (if required by the SOW), Progress Report, Meetings, Project Review, Minutes, inspections or audits of the Work, correspondence, Notices, etc...

[* insert text]

Section 17. Items Raised By Supplier

This narrative section is to record any questions and/or complaints that the Supplier has raised in the last Status Report (if required by the SOW), Progress Report, Meetings, Project Review, Minutes, correspondence, Notices, etc...

[* insert text]

Section 18. Closure of Action Items and Issues

a. List in tabular or graphic form "opening" versus "closure" of Action Items and issues:

[*];




b. List all open Action Items and issues over thirty (30) calendar days old:

[*]

(insert Action Item and issues spreadsheet tabular format if more convenient)

Section 19. Areas of Concern

‘Areas of Concern’, together with proposals or recommendations of remedial actions.

[* insert text]

Section 20. Export Control / Security

Are the deliverables Controlled Goods? Yes/No

Are the Deliverables controlled by ITAR or EAR? Yes/No

[* insert text]

Section 21. Other Matters Not Covered Above

This is a narrative section to cover any and all material matters that the Supplier believes has not previously been covered above. The Supplier shall add any matter in this section that has, is or will adversely affect progress and quality of the Work in order to present to the Supplier an objective, accurate, candid and truthful report as to the progress of the Work and its performance of its obligations.

[* insert text]


All documents, if any, referred to in a Progress Report shall be attached to each Progress Report as Attachment A., Attachment B, etc…

Presentation Materials, Rev 0 Document #: VSY-A08.22-0049 Agreement #: [* insert Agreement #]




Presentation Materials

PM262



Presentation Materials, Rev 0 Document #: VSY-A08.22-0049 Agreement #: [* insert Agreement #]



Presentation Materials DID PM262

Purpose

The purpose of the Presentation Materials is to make the Purchaser aware of the contents of the Supplier’s presentation prior to the presentation itself.

References




Format and Content

1 Supplier’s format.

Change Request, Rev 0 Document #: VSY-A08.22-0050 Agreement #: [* insert Agreement #]




Change Request

PM270







Change Request PM270

Purpose

A Change Request is intended to make the Subcontracting Authority aware of any proposed amendments to the Subcontract.

References




Format and Content

1 The Change Request shall be prepared in the format attached as Attachment A (completion instructions are on the following page).

2 The following documents shall be attached to the Change Request:

(a) a complete copy of the proposed amended document (all proposed changes are to be highlighted in the ‘Amendment Record’ and/or side bars (see Part 1 (Introduction) of the SOW);

(b) a complete copy of the original document currently included in the Subcontract which is proposed to be amended; and

(c) a Price breakdown/back up showing that the proposed Price for the Change Request is being offered on a Fair and Reasonable Basis and/or in accordance with the Subcontract.




Attachment A

CHANGE REQUEST

Project: [*]

Name of Supplier: [*]

Description of Equipment or System: [*]

Agreement #: [*]

Covering Purchase Order #: [*]

Supplier’s Change Request #: [*]

Purchaser’s Request #: [*]

Purchaser’s SWBS #: [*]

Date: DDMMMYY

Change Classification e.g. Class I, Class II or Class III: [*]

Change Priority e.g. Emergency, Urgent or Routine please state:

[*]

Change Order Request Requested by: [*]

Description of Change Order Request:

[*]

Variation of Milestone Description and Payment Plan:

[*]

Variation to Delivery Dates of the Deliverables:

[*]

Variation to the Conditions of Subcontract:

[*]

Effect on other Schedules of the Subcontract:

[*]

For and on behalf of:

Vancouver Shipyards Co. Ltd.


[* insert legal name of Supplier]

Signature: Signature:

I warrant that I have authority to bind the company. I warrant that I have authority to bind the company.

Print name: [*] Print name: [*]

Title: [*] Title: [*]

Date: [*] Date: [*]




Instructions for filling in Attachment A

1 Project:: [* insert name of Project]

2 Name of Supplier: [*Insert name of Supplier]

3 Description of Equipment or System: [*]

4 Agreement #: [*]

5 Covering Purchase Order #: [*]

6 Change Classification: [*]

All Change Order requests shall be classified by the Supplier:

(a) Class I

i. New work-scope and budget;

ii. Milestones;

iii. Price;

iv. Interface Requirements (Hardware budgets/Data Interfaces/Equipment Level Interface);

v. Baselined solution (e.g. Subsystem Description Document - SSDD);

vi. Changes that affect one or more of the following after the baseline for the Equipment has been established:

• Safety;

• Interchangeability;

• Support;

• Maintenance;

• Testability;

• Reliability;

• Maintainability;

• Performance; and

• Producibility.

(b) Class II

Not Class 1 or Class 3

(c) Class III




Changes to the Subcontract, or other “baselined configuration item documentation”, that are not cross-functional and are only textual changes not affecting the intent. e.g. grammar, spelling, formatting, etc….

7 Change Priority:

All Change Requests shall be assigned a ‘priority’ depending on their impact to the Project:

Emergency means a change that is required for the immediate safety of personnel, or to avoid damage that could result in Equipment or System failure. Immediate discussion shall be convened between the Purchaser and the Supplier to resolve. The target schedule for the consideration and approval of an Emergency Change Order request, from receipt to issue of a Change Order, is twenty four (24) hours.

Urgent means a change proposed for operational effectiveness of delivered Equipment where a condition exists which is potentially hazardous and will affect safety and/or where processing the Change Order Request in a routine manner would adversely affect cost and schedule. Purchaser ‘Change Control Board’ called out of sequence if necessary. The target schedule for consideration and approval of an Urgent Change Order request, from receipt to the issue of a Change Order request, is ten (10) Working Days.

Routine means a change when the criteria for Emergency and Urgent are not met. Addressed at regular Purchaser’s Change Control Board. The target schedule for routine changes, from receipt to issue of a Change Order request is thirty (30) Workings Days.

8 Change Order Requested By: name of the person who has requested the Change Order

9 Description of Change Order Request: Change Order request description

10 Price/Variation of Milestone Description and Payment Plan: Describe the effect on the Price and/or variation of the Milestone Description and Payment Plan.

11 Delivery Dates: Describe the effect on the Delivery Dates to any of the Deliverables.

12 Terms and Conditions of Subcontract: Describe the effect on the Terms and Conditions of the Subcontract.

13 Effect on other Schedules of the Subcontract: Describe the effect on the other Schedules of the Subcontract (if any).

Referenced Document Request, Rev 0 Document #: VSY-A08.22-0051 Agreement #: [* insert Agreement #]




Referenced Document Request

PM271




Referenced Document Request, Rev 0 Document #: VSY-A08.22-0051 Agreement #: [* insert Agreement #]



Referenced Document Request PM271

Purpose

The Referenced Document Request is intended to identify to the Subcontracting Authority any request made by the Supplier for a copy of any documents referenced in the Subcontract that is not available in the public domain.

References




Format and Content

The Referenced Document Request shall be prepared in the following format and contain the following information:

Project: [* insert name of Project] Name of Supplier [* insert name]

Agreement #: [* insert agreement #] VSY Supplier Code: [* insert code]

Covering Purchase Order #: [* insert Covering PO #]

Description of the System: [* insert description of the System]

Description of Equipment: [* insert description of the Equipment]

Purchaser’s SWBS #: [* insert SWBS #]

Identify section of the Subcontract where the reference is made:

[* insert reference]

Description of referenced document(s) being requested: [* Title, reference, date]

Describe the effect

Minutes, Rev 0 Document #: VSY-A08.22-0052 Agreement #: [* insert Agreement #]




Minutes

PM272






Minutes PM272

Purpose

The Minutes are intended to document the proceedings, issues, discussions, concurrence or non-concurrence reached, actions taken and Data presented at all Meetings (i.e. face-to-face, video conference and telephone conference) between the Parties and/or the Parties and third parties. Minutes cannot and do not modify or amend the Subcontract in any way.

References




Format and Content

1 Template

See Attachment A for Minutes template.

2 The title of each set of Minutes shall be shown as follows:

“Minutes – [name of Meeting] – [date in DDMMMYY format]”.

3 The signature of a representative of each attending party evidences that the Minutes accurately reflect the events and discussions of the Meeting and shall not be construed as modifying or amending the Subcontract.

4 Header and Footer

The ‘Header’ and ‘Footer’ of each page of the Minutes shall include the following statement:

“Nothing Contained Within These Minutes Shall Modify The Work or Amend The Subcontract”.

5 Addresses of the attendees

The Supplier shall record the full postal address and email addresses of the attendees.

6 Purpose of the Meeting

The Supplier shall concisely describe the purpose of the Meeting, by whom it was called, references to correspondence arranging the Meeting, the Agenda and its distribution.

7 Agenda

The Supplier shall attach a copy of the Agenda to the Minutes. The Agenda shall clearly state the items to be discussed, the identity of the author and the date it was issued in DDMMMYY format. The Agenda shall include an item mandating the review of all prior Action Items undertaken to be completed from prior Meetings. If additional items are added to the Agenda during the Meeting, these shall be identified.




8 Documentation and Presentations

The Supplier shall list in this section all documentation distributed at the Meeting. A hard copy of all the materials shall be attached to the Minutes. A soft copy to be submitted on media agreeable to the Parties.

9 Possible Adverse Effect on the Subcontract

The Supplier shall record any declared event that has, is, may or will adversely affect the Supplier’s ability to fulfil its obligations under the Subcontract respecting the Technical Requirements, the Supplier’s Level 0 Schedule, Milestones and the delivery of the Deliverables on or before the Delivery Dates.

10 Action Item Database

The Supplier shall record all Action Items arising from all Meetings in an Action Item Status Report established and maintained in accordance with SDRL PM273 and DID PM273.

11 Summary of the Events

The Supplier shall accurately, succinctly and faithfully record a précis of the pertinent and relevant discussions, issues, decisions, concurrence and/or non-concurrence reached and Action Items undertaken or agreed to be completed by the attendees.




Attachment A – Minutes Template

MINUTES - [Name of Meeting] - [DDMMMYY]

Project: [*] Agenda Reference: [*]

Description of the Equipment/ System:

[*] SWBS: [*]

Title of Meeting: [*] Date Meeting Held: [*]

Name of Supplier: [*] Date Minutes Produced: [*]

Agreement Number: [*] [*]

Type of Meeting: [*] Location of Meeting: [*]

Meeting called by: [*] Start Time: [*]

Ref. Meeting no.: [*] End Time: [*]

Name of Chairperson: [*] Minute recorded by: [*]

Attendees Title Company Office Tel # Office fax # Email address

[*] [*] [*] [*] [*] [*]

Address of Attendees: [*]

Purpose of Meeting: [*]

Agenda: Attached as Annex A to these Minutes

Documentation and Presentations: Attached as Annex B to these Minutes.

Possible Adverse Effect on the Subcontract: [*]

Summary of Events:

[*]

Action Item and Issue Status Report, Rev 0





Action Item and Issue Status Report

PM273








Action Item and Issue Status Report PM273

Purpose

The Action Item and Issue Status Report is intended to record all Action Items and issues relating to or arising from the Subcontract. The Action Item and Issue Status Report records, tracks, monitors and manages Action Items and issues arising from correspondence and Meetings (see definition below) and provide a status against each.

References




Format and Content

Field Descriptions using an Excel spreadsheet or Access Database

1 Project description: (alpha numeric– 25 digits/characters);

2 Subcontract #: (alpha numeric – 15 digits/characters);

3 Covering Purchase Order #: (alpha numeric – 20 digits/characters);

4 Name of Supplier (text field – 25 characters);

5 Purchaser’s SWBS number (text filed – 10 characters)

6 Criticality of the Action Item / Issue (numeric field – 2 digits) criticality measured from 1 to 3 where 1 means ‘low’, 2 means ‘moderate’ and 3 means ‘high’);

7 Action Item Number (alpha numeric – 16 digits/characters) as follows:

DDMMMYY-xxMT-MTN

Where

DDMMYY = Date of Action Item arose

xx

= Meeting type where: xx means PM = Project Management ENG = Engineering (includes ILS = Integrated Logistics Support QA = Quality Assurance OPS = Operations COM = Commissioning, Test & Trials FIN = Finance SEC = Security HSE = Health, safety and the Environment IRB = Industrial and Regional Benefit





LOG = Logistics IT = Information Technology and Information Management PLA = Planning EST = Estimating PRO = Procurement OTH = Other and

MT = Meeting

MTN = Meeting number (i.e. 001, 002, 003, etc.…)

AIN = Action Item number within the same MT (i.e. 01, 02, 03, etc.…)

Examples:

150317-PMMT-007-03 = the 3rd Action Item recorded in the 7th Project Management Meeting held 15 Mar 17

120318-ENGMT-013-11 = The 11th Action Item recorded in the 13th Engineering Meeting held 12 Feb 18

8 Action Item SOW identifier (numeric – 2 digits), where:

1 represents Introduction; 2 represents Project Management (PM); 3 represents Engineering (ENG); 4 represents Integrated Logistics Support (ILS); 5 represents Quality Assurance (QA); 6 represents Operations (OPS); 7 represents Commissioning (COM); 8 represents Finance and Insurance (FIN) 9 represents Security (SEC); 10 represents H S & E (HSE); 11 represents Industrial and Regional Benefits (IRB); 12 represents Logistics (LOG) 13 represents CM/DM; 14 represents Planning (PLA); 15 represents Estimating (EST); and 16 represents Procurement.

9 A column to identify the action item to the relevant DID

Examples:

Project Execution Plan would be ‘PM250’

Engineering Level 0 Guidance data would be ‘E001’

10 Description of System/Equipment/Brief: (text field – 25 characters. Same identification as in the Agreement);

11 Action Item / issue description (text field – 256 characters);

12 Company or organisation of Actionee (text field – 25 characters);

13 Identity of Actionee responsible for closing the Action Item / issue (text field);

14 Date Action Item / issue opened (date field);





15 Committed closure date for completion of the Action Item / issue(date field);

16 Date Action Item / issue actually closed (date field);

17 Reference to closure action, e.g. Letter, Meeting etc., date, paragraph reference etc.…;

18 Comments field 1 (text - field 256 characters);

19 Comments field 2 (text - field 256 characters);

20 Ageing field – (numeric - field 3 numeric characters (how long has the Action Item / issue been outstanding))

The Action Item and Issue Status Report shall enable the Action Items /issues to be sorted on any single or combination of fields and permit pro forma and ad hoc reports and metrics to be generated.

Travel Plan, Rev 0 Document #: VSY-A08.22-0054 Agreement #: [* insert Agreement #]




Travel Plan

PM280







Travel Plan PM280

Purpose

The purpose of the Travel Plan is to advise the Subcontracting Authority of the Supplier’s travel, accommodation and subsistence requirements in support of the Project for a defined period described in Part 2 (Project Management) of Schedule D1 (SOW).

References




Format and Content

1 The Supplier shall complete the pro forma Travel Plan spreadsheet attached as Attachment A.




Attachment A

Updated Schedule E - Goods, Rev 0





Updated Schedule E - Goods

PM282







Updated Schedule E - Goods PM282

Purpose

The purpose of the Update to Schedule E is to provide the Purchaser with the latest required data relating to the Goods and Software.

References




Format and Content

1 Complete the attached Excel spreadsheet entitled “Updated Schedule E – Goods”.





Attachment A

Schedule E (Goods)

06 Schedule E (CAT B1 and B2) Goods.xlsx

Original Warranties, Rev 0





Original Warranties

PM290




Original Warranties, Rev 0




Original Warranties PM290

Purpose

The purpose of the Original Warranties is to demonstrate to the Subcontracting Authority that the Supplier has the required warranties for it Sub-suppliers required by the Subcontract.

References




Format and Content

1 The Supplier to provide the original warranties obtained from its Sub-suppliers required by the Subcontract.

WorkSafeBC Clearance Letter, Rev 0





WorkSafeBC Clearance Letter

PM291



WorkSafeBC Clearance Letter, Rev 0




WorkSafeBC Clearance Letter PM291

Purpose

The purpose of the WorkSafeBC Clearance Letter is to provide evidence that the Supplier is covered by the British Columbia Workers’ Compensation scheme.

References

This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 2 (Project Management) of Schedule D1 (SOW).



Format and Content

1 Deliver a copy of a letter from WorkSafeBC Clearance letter.





Page 1 of 3



Supplier’s Master Schedule

PM351








Page 2 of 3


Supplier’s Master Schedule PM351 Purpose

The Supplier’s Master Schedule (SMS) describes the Supplier’s planned sequence of activities, internal milestones, Subcontract Milestones, and decision points to enable the Work and obligations of the Subcontract to be performed and met. Additionally, the SMS defines the current Project schedule status, comparing the current schedule with the Subcontracted schedule, a high level of which is set out in the Supplier’s Level 0 Schedule (see Schedule F). The SMS also compares the current schedule status with any applicable baseline schedule.

The Supplier uses the SMS, including or supplemented by subordinate schedules, to:

(a) plan the activities and sequencing of those activities to achieve the requirements of the Subcontract; and

(b) provide schedule direction and status to the management team responsible for conduct of the work.

The Purchaser uses the SMS to:

(a) ensure that that it aligns to the Purchaser’s Integrated Master Schedule (IMS) for the Project);

(b) gain visibility into the Supplier’s planning;

(c) understand and evaluate the Supplier’s approach to meeting the requirements of the Subcontract;

(d) assist with monitoring the progress of the Supplier in meeting the requirements of the Subcontract; and

(e) as a source of input to planning performed by the Purchaser’s planning and estimating department.

References




Format and Content

General

The Supplier’s Schedule shall:

(a) be developed using Primavera P6 or a similar program compatible with Primavera P6;

(b) support the PEP and (if required) the Purchaser’s Integrated Master Schedule (IMS) for the Project;

(c) follow the Purchaser’s WBS and SWBS (if required as part of Part 15 Estimating of the SOW);

(d) be resource loaded by identifying total hours against each activity (product or support task);

(e) not exceed the resource hours / allocation submitted in its relating proposal;

(f) identify the durations of each activity (if required to align with the AEP timeline);

(g) identify the float available on each activity;

(h) identify the milestones of each activity in accordance with the relating AEP (if required); and

(i) identify its critical path(s).





Page 3 of 3


Narrative Analysis

If not addressed in the associated Status Report, each submission of the SMS shall contain an explanation of the cause of each rescheduled or forecast date that is later than the milestone's, or activity’s original scheduled date for the issue of the SMS in which the rescheduled date or forecast date is first reported. Subsequent issues shall address changes from previously reported dates. The narrative analysis for the SMS shall address possible impact on other milestones and activities, and shall describe recovery plans to minimise the impact (see also SDRL PM231 and DID PM231 Recovery Plan).

Progress Report, Rev 0




Page 1 of 4



Progress Report

PM361







Page 2 of 4


Progress Report PM361

Purpose

The Progress Report is intended to make the Purchaser aware of the Supplier’s progress of the Work against the Integrated Project Team’s Master Schedule. Each Progress Report is intended to be a formal, contractually significant tool to provide an objective, accurate, candid, truthful and comprehensive report as to its progress of the Work current in all respects at the time of preparation.

The Progress Report is in a pro forma template so as to permit consistency and ease of ‘backward reference’ to earlier Progress Reports. However, if the Supplier is of the opinion that the pro forma template precludes an objective, accurate, candid and truthful report as to progress of the Work being declared, then the Supplier shall add whatever additional sections to the end of the report that is considered necessary. The Supplier shall support the sections identified below with its own in-house produced management information and Data.

References




Format and Content

1 The Progress Report shall contain the following information in the following structure:

Section 1. Introduction

This section shall provide an introduction identifying the following:

a. Agreement number: [*]

b. Covering Purchase Order #: [*]

c. Description of the system and/or Goods: [*]

d. Summary of change in Price since Contract Award +/-: [*]

e. Narrative for Section 1, including a summary of progress since the last Progress Report and summary of planned progress until the next Progress Report.

[* insert text]

Section 2. HSE Report

Typical items to report include:

a. HSE issues and concerns on the Project: [*]

b. Incidents this month (reportable and recordable)’ [*]





Page 3 of 4


Since Last Progress Report To Date

Near Misses

First Aid(s)

Reportable Incidence(s)

Days Lost

Section 3. Activities

This section shall identify the activities to be carried out during the next reporting period, as a minimum the following are to be included:

a. Critical activities scheduled till the next reporting period and details of any issues relating to these critical activities; b. Goods due to be delivered and details of any issues relating to meeting the expected date of delivery; and c.

Section 4. Schedule

Subject(s): [*]

f. Status of Recovery Plans: Nos: [*] Description: [*] Forecast: DDMMMYY

g. Milestones achieved to date: Nos: [*] Dates: DDMMYYY Forecast: DDMMMYYY

h. Milestones missed to date: Nos: [*] Dates: DDMMMYY Forecast: DDMMMYY

i. Reason for Milestones not achieved:

j. Narrative for Section 4:

[* insert text]This

Section 5. Resources

a. This is a narrative section to describe any issues related to labour and any changes in personnel, particularly key personnel, which have the potential to directly affect the Work.

[* insert text]

b. [*insert labour statistics table], the labour statistics table details the number of employees for this reporting period and forecasted for the next reporting period, the table should indicate what functional area the personnel will work on and what category of labour the personnel is covered under.





Page 4 of 4


Section 6. Risk & Opportunity Management

This is a narrative section to describe any risks that need to be addressed or any opportunities for improvement during the next reporting period and the Supplier’s mitigation strategy.

[* insert text]

Section 7. Other Issues and/or Actions

This is a narrative section to describe any Issues and/or Actions that have been resolved since the last reporting period if not covered elsewhere on this report and any Issues and/or Actions that should be resolved during the next reporting period.

[* insert text]

Section 8. Commercial


a. Unresolved Change(s): Nos: [*] Dates: DDMMMYY Description: [*]

c. Directions from Purchaser: Nos: [*] Dates: DDMMMYY Description: [*]

h. Warranty claims: Nos: [*] Dates: DDMMMYY Description: [*]

f. Disputes: Nos: [*] Dates: DDMMMYY Description: [*]

Section 9. Financial


b. Approved Payment Claims not paid: $ [*] Dates: DDMMMYY

c. Claim forecast for next six (6) Months: $ [*]

d. Narrative for Section 3 / Other issues relating to invoices and/or payments

[* insert text]

Section 10. Other Matters Not Covered Above

This is a narrative section to cover any and all material matters that the Supplier believes has not previously been covered above. The Supplier shall add any matter in this section that has, is or will adversely affect progress and quality of the Work in order to present to the Supplier an objective, accurate, candid and truthful report as to the progress of the Work and its performance of its obligations.

[* insert text]


All documents, if any, referred to in a Progress Report shall be attached to each Progress Report as Attachment A., Attachment B, etc.

DID Front Cover Engineering

Rev 2

Document No: [*]

Template ref: 05 D3 Front Cover Engineering Unclassified Page 1 of 1 Purchaser’s initials: _____ Uncontrolled when Printed Supplier’s initials: _____ Intellectual Property Rights owned by Vancouver

Shipyards Co. Ltd

]

Document Identifier Number: Not used Rev: 2

Title: DID Front Cover Engineering Ship applicability: All

Master Template Ref: DID Front Cover Engineering Project: Joint Support Ship

Type Organization Area Supplier VSY Supplier Code SWBS

DID VSY Engineering N/A N/A All

Schedule D3

Data Item Descriptions

Engineering



Level 0 Design Guidance Data, Rev 2 Document #: VSY-A02.01-0004 Agreement #: [* insert Agreement #]




Level 0 Design Guidance Data

DID E001



.




PURPOSE

Level 0 Design Guidance Data is required by the Purchaser to enable the initial design of the Ship to proceed.

REFERENCES

This DID must be read in conjunction with Part 3 (Engineering) of Schedule D1 (SOW).

PREPARATION INSTRUCTIONS

The supplier shall provide a DID Compliance Matrix indicating which submission files contain the items listed in this DID.

For written style documents (eg. manuals, performance specification documents, etc) larger than 10 pages the document shall include a Table of Contents that contains links to the various section headers within the document.

CONTENT AND STRUCTURE

All physical parameters quoted at this stage are to be within five per cent (5%) of final design figures.

The following Technical Information shall be provided:

(a) General description of the Equipment (along with the normal and emergency operating modes, controls, and any other relevant functionality);

(b) General arrangement drawings of the Equipment, including indications of access and maintenance spaces;

(c) Piping and instrumentation diagram (P&ID) of the Equipment including:

(i) Stream names, flow rates, flow directions, pressure, temperatures

(ii) Equipment descriptions: make, type, size, capacity

(iii) Line sizes, piping connections

(iv) Piping specifications

(v) Instruments and controls with ranges and set points

(vi) Heat tracing requirements

(vii) Insulation type and thickness

(viii) Symbols legend

(ix) Identifiers which relate items in the P&ID to Bills of Materials

(d) Overall and other leading dimensions of the Equipment;

(e) Dry weights of the Equipment;

(f) Wet weights of the Equipment;

(g) Performance details listed in the Supplier’s Specifications supported by type test results if available;

(h) The time required for the Equipment to reach full output;




(i) Guaranteed maximum requirements for cooling water, compressed air, etc…

(j) Heat dissipation of the Equipment in to the space;

(k) Pump information:

(i) Pump shaft bearing life in hours of continuous running;

(ii) Pump shaft seal life in hours of continuous running;

(iii) Pump Minimum Efficiency Index (MEI) rating for pumps larger than 1 hp.

(l) Electrical demands and specifications (voltages, frequencies, phase, etc…) including full load currents, maximum continuous load, average power, duty cycle, full load power factors, starting/in-rush currents, quality of electric power supply, starting current duration, starting power factors and any harmonic distortion effects produced by the load;

(m) Motor starter details

(n) Operating temperatures

(o) The engineering standards applicable;

(p) Airborne noise measurements and vibration measurements;

(q) A clear statement or drawing detailing the scope of supply, drawing attention to associated items that will have to be procured by the Purchaser (if any);

(r) Information on oils and greases as required below:

(i) Oils (see Schedule B3 (General Technical Requirements, VCRI and Compliance Matrix); and

(ii) Greases (see Schedule B3 (General Technical Requirements, VCRI and Compliance Matrix);

(s) An electrical interconnectivity diagram in the format of the example shown in Attachment A, including labels with electrical details for all interconnections.

(t) Wiring Diagrams

(u) Cable Lists

(v) Drawings showing the size and location with dimensional tolerances of the Equipment’s piping connections to external interfaces

(w) Drawings showing the size and location with dimensional tolerances of Equipment’s cable entry, connector type, terminations, wiring details, and connectors to external interfaces; including gland size if appropriate and power supply cable route(s) within the Equipment Unit;

(x) EMI/EMC (electromagnetic interference and compatibility) information

(y) Regulatory Body Certifications

(z) Certified Performance Test Curves

(aa) For engines also provide as a minimum:




(i) Engine torque versus speed and fuel rack positioning

(ii) Exhaust gas temperature versus fuel rack positioning

(iii) Intake and exhaust configuration diagram and operating characteristics

(iv) Lubrication oil diagram and operating characteristics

(v) Fresh water cooling diagram and operating characteristics

(vi) Seawater cooling diagram and operating characteristics

(vii) Engine speed controller functional description

(viii) Local control panel logic (if fitted).

(bb) For propulsion motors also provide as a minimum:

(i) Controller functional description

(cc) For gearboxes also provide as a minimum:

(i) Gearbox general arrangement

(ii) Gear ratios

(iii) Bearing arrangement and types

(iv) Gearbox efficiency over the full operating range

(v) Gearbox moment of inertia with respect to output shaft.

(vi) Lubrication Oil Pressure in the gearbox

(dd) For clutches also provide as a minimum:

(i) Limiting parameters (maximum torque, etc.).

(ee) For propeller shafts also provide as a minimum:

(i) Moment of inertia

(ii) Bearing arrangement and types

(ff) For propellers also provide as a minimum:

(iii) Torque and thrust maps as a function of ship and shaft speed

(iv) Diameter

(v) Moment of inertia.

(gg) For hydraulic systems also provide as a minimum:

(i) Heat exchanger data such as a rated heat transfer rate at given hot and cold side inlet temperatures and




flows

(ii) Equipment and valve local control logic, where applicable

(hh) The Equipment Specifications Table shall be populated with the following information for each piece of Equipment:

(i) ID Number (provided by Purchaser)

(ii) Equipment Name

(iii) Original Equipment Manufacturer

(iv) OEM Model Number

(v) Quantity

(vi) Name Plate Description

(vii) Dry Weight (kg)

(viii) Wet Weight (kg)

(ix) Width (mm)

(x) Depth (mm)

(xi) Height (mm)

(xii) C of G Width (mm)

(xiii) C of G Depth (mm)

(xiv) C of G Height (mm)

(xv) Maintenance Space Required? (y/n)

(xvi) Acoustic Noise Level (dBA)

(xvii) Heat Dissipation (kW)

(xviii) Pertinent Equipment Ratings (eg Crane Rating)

(xix) Electric Power Voltage (V)/Frequency (Hz)/Phase

(xx) Power Required (kW)

(xxi) Protection Class (IP Rating)

(xxii) Construction Materials

(xxiii) Design Standards Used

(xxiv) Motor Starter Type

(xxv) Temperature Rating




(xxvi) Chilled Water Flow (m^3/hr)

(xxvii) Chilled Water Pressure (bar)

(xxviii) Chilled Water Press. Drop (bar)

(xxix) Chilled Water Load/Duty (kW)

(xxx) Chilled Water Design Temp. Differential ('C)

(xxxi) Air Pressure Min /Max (bar)

(xxxii) Air Quantity (Std. m^3/min)

(xxxiii) Air Dryness Dewpoint ('C)

(xxxiv) Air Purity (Micron)

(xxxv) Air Oil Content (ppm)

STRUCTURE

• I.a.w Attachment A: Interconnectivity Diagram Example • I.a.w Attachment B: Equipment Specifications Table in Excel format • Separate file submission where appropriate (eg. Where the information requested does not reside as part of an

interconnectivity diagram or the Equipment Specifications Table)

SPECIAL INSTRUCTIONS

Information that pertains to Equipment physical dimensions and arrangements shall be provided in AutoCAD format (.dwg) to facilitate the development of ship arrangement drawings.

All fields in Attachment A shall be completed, if a piece of information is not applicable “NA” shall be entered.



Unclassified Page 7 of 10

Uncontrolled when Printed Purchaser’s initials: _____ See disclosure statement on front page of the Subcontract Supplier’s initials: _____

Attachment A

Interconnectivity Diagram

EQUIPMENT: [* insert description of the Equipment]

ALL CABLES TO AND FROM EQUIPMENT WITHIN A SYSTEM SHOULD BE IDENTIFIED ON THIS DIAGRAM

UNIT A UNIT B UNIT C

POWERSUPPLY

FOR EXAMPLE





Attachment B

Equipment Specifications Table


ID Number Equipment Name

Original Equipment

Manufacturer

OEM Model

Number Quantity Name Plate

Description

Dry Weight

(kg)

Wet Weight

(kg)

Width (mm)

Depth (mm)

Height (mm)

C of G Width (mm)

C of G Depth (mm)

C of G Height (mm)

Maintenance Space

Required? (y/n)

Acoustic Noise Level

(dBA)

Heat Dissipation (kW)





Equipment Specifications Table (continued)

ID Number Pertinent Equipment

Ratings (eg Crane Rating)

Electric Power Voltage (V)/Frequency (Hz)/Phase Power Required (kW) Protection Class

(IP Rating) Construction Materials Design Standards Used Motor Starter Type Temperature Rating






ID Number Chilled Water Flow (m^3/hr)

Chilled Water Pressure

(bar)

Chilled Water Press. Drop

(bar)

Chilled Water Load/Duty

(kW)

Chilled Water Design Temp. Differential

('C)

Air Pressure Min /Max (bar)

Air Quantity (Std. m^3/min)

Air Dryness Dewpoint ('C)

Air Purity (Micron)

Air Oil Content (ppm)






DID E002






PURPOSE

Level 1 Design Guidance Data is required to enable the detailed design of the Ship to proceed.

SCOPE

Information as required below and Attachment A. The “Compartment No.” column in the tables at Attachment A are for the Purchaser’s use only.

REFERENCES





CONTENT AND FORMAT

All physical parameters quoted at this stage are to be within one per cent (1%) of final design figures.

Level 1 Design Guidance data includes, where applicable:

(a) Update to all information and Equipment Specification Table entries provided in SDRL E001 and DID E001. Note, if a piece of information is not updated in this submittal it is by default implied to be “within one per cent (1%) of final design figures” per the statement above.

(b) Where a Supplier is providing cables that run between equipment cable supporting data as follows shall be provided:

(i) Cable and connector / terminal data with pattern numbers / OEM part numbers

(ii) Number of cores and cross section.

(iii) Outside diameter.

(iv) Screening details.

(v) LFH/Non LFH

(Note: If non LFH, reasons are to be given.)

(vi) Cable length constraints.

(vii) Cable separation criteria.

(viii) Minimum bending radius.




(c) Waveguide requirements and Specifications.

(d) Details of seating, foundations, mounting and securing points together with hole sizes, securing bolt specifications and related dimensional tolerances.

(e) Positions of lifting eyes where appropriate.

(f) Detail of shock and vibration mounts where applicable.

(g) Maintenance envelopes, access and withdrawal spaces for all Equipment nits including isometric views and all primary views.

(h) Electrical power:

(i) Longest supply interruption that can be tolerated without need for re-start, and/or details of battery back up / Uninterruptable Power Supply Equipment (UPSE).

(ii) Time to become operational after interruption exceeding that in (vi) above.

(iii) The efficiency of any safety devices fitted, both from personnel and ship safety aspects, and the general electrical safety of the equipment.

(iv) Whether or not the equipment presents an unbalanced load, and the actual loads presented.

(v) Whether or not the equipment draws a pulsed current and if so, its characteristics.

(vi) Whether or not the equipment causes waveform distortion on the supply lines and if so, the magnitude and phase angle of each harmonic (voltage and current).

(vii) If 3 phase motors have an Active Front End (AFE) drive, then harmonics analysis must be provided up to the 100th current harmonic.

(viii) Whether or not the equipment is a source of radio interference, either mains borne or radiated, and to what degree.

(i) Liquid Cooling

(i) Chilled water flow rates, pressures, temperature rise and heat quantity in kilowatts to be removed by chilled water supply.

(ii) How coolant failure is sensed and if override exists where applicable.

(iii) Time from loss of water flow for a critical component or components to reach:

a) Their maximum operating temperature.

b) Failure temperature.

(iv) Chilled water temperature above which a critical component will exceed its maximum operating temperature.

(v) If fitted with a temperature sensor/trip, time from loss of coolant before warning or trip occurs where applicable.




(j) Air cooling

(i) For equipment that relies on compartment air cooling, the ambient temperature at which critical components will reach maximum operating temperature.

(ii) If fitted with a temperature sensor/trip, and whether fitted with an override.

(k) Other Services:

(i) Dry air, hydraulic power, HP air etc. Quantity, quality and dependencies are to be stated.

(l) A signal interface diagram identifying all equipment signal interfaces for remote control and surveillance of the equipment. The diagram shall include as a minimum:

(i) Remote control switched inputs (e.g. Start/Stop, Valve Actuation, etc.).

(ii) Remote switched outputs (e.g. plant status indication, etc.).

(iii) Alarm and warning indicators (3 wire volt free contacts).

(iv) Analogue surveillance signals (4 - 20 mA).

(v) Temperature sensors (PRTs, Cr/Al thermocouples etc.).

(vi) Vibration, speed, flow signals.

(m) Although not common, in the event that the ship’s IPMS will have sequenced automation control over the Equipment (Purchaser will advise if this is the case) then the Supplier shall provide control logic sequences for the Equipment;

(n) Weights of each interchangeable assembly/sub-assembly in excess of 70kg.

(o) Antenna Clear Arcs and Seating Details, (flatness/level/ thickness etc.)

(p) Stiffness of mounting structures.

(q) Recoil Forces from Weapons

(r) Efflux envelopes and Blast Curves for Weapons, including any special protection for Efflux, or debris management.

(s) Weapon Alignment Requirements, including the requirement for any special alignment facilities on board or ashore.

(t) Antenna Power Contours, RADHAZ criteria and parameters, including any RADHAZ precautions to be observed.

(u) Details of Safe to Rotate/Safe to Transmit Precautions fitted to Equipment.

(v) The Supplier must provide 3D Computer Aided Drafting (CAD) files for all provided equipment:

(i) File format must be AutoCAD 3D, or other file type compatible with ShipConstructor;

(ii) 3D model must be simplified and not include unnecessary details for computer performance reasons; and

(iii) 3D model should include connection locations, connection types, and item weights.




STRUCTURE

I.a.w. Attachment A: Equipment Specification Table in Excel format

Separate file submission where appropriate (eg. 3D model, information not listed in Attachment A)


Supplier must provide an update to information provided with SDRL E001 and DID E001 where applicable. Changes to the information provided must be clearly identified.

Information that pertains to physical dimensions and arrangements shall be provided in AutoCAD format (.dwg).




Attachment A to DIDE002




Original Equipment

Manufacturer

OEM Model


Description

Dry Weight

(kg)

Wet Weight

(kg)

Width (mm)

Depth (mm)

Height (mm)

C of G Width (mm)

C of G Depth (mm)

C of G Height (mm)

Maint. Space Required?

(y/n)

Acoustic Noise Level (dBA)

Heat Dissipation

(kW)

Level 0 Guidance Data is within 5% of actual final design figures

Level 1 Guidance Data is within 1% of actual final design figures





ID Number Pertinent Equipment Ratings

Electric Power Voltage (V)/Frequency

(Hz)/Phase Power Required (kW) Protection Class (IP

Rating) Construction Materials Design Standards Used Motor Starter Type Temperature Rating

Level 0 Data is within 5% of actual final design figures






ID Number Chilled Water

Flow (m^3/hr)


(bar)


(bar)


(kW)


('C)




Air Purity (Micron)









DID E003

Prepared by : Vancouver Sh ipyards Co. L td . 2 Pember ton Ave . Nor th Vancouver , BC, Canada, V7P 2R2 Te l : (604) 988-3111 Fax: (604) 984-1636





PURPOSE

Level 2 Design Guidance Data is required to enable the final design of the Ship to proceed.

SCOPE

Information as required below .

REFERENCES





CONTENT AND FORMAT

All physical parameters quoted at this stage are to be the actual final design standard.

Level 2 Design Guidance Data includes, where applicable:

(a) Update to all information and Equipment Specification Table entries provided in SDRLs E001 and E002 and DIDs E001 and E002. Note, if a piece of information is not updated in this submittal it is by default implied to be “the actual final design standard” per the statement above.

(b) All Connection Data, to enable connectors to be made up, without additional information (e.g. from third party connector manufacturers). As a minimum this data must include:

(i) preparation of cable cores, screens and insulation

(ii) screen termination definition and procedures

(iii) core termination procedures

(iv) heat-shrink boot fitting procedures

(c) A comprehensive list of cable and connection tools necessary for correct installation of mating connectors and backshells or heat shrink glands and boots. The list is to include all necessary crimping, insertion and extraction tools, and must highlight tools peculiar to one particular cable/connector type or manufacturer.

(d) Any specialised technical information not already included in SDRL’s E001 and E002.

STRUCTURE

Separate file submission where appropriate (eg. Where the information requested does not reside as part of an interconnectivity diagram or the Equipment Specifications Table).





Supplier must provide an update to information provided with SDRLs E001 and E002 and DIDs E001 and E002 where applicable. Changes to the information provided must be clearly identified.

Information that pertains to physical dimensions and arrangements shall be provided in AutoCAD format (.dwg).

Design Guidance Data, Rev 0 Document #: 193-A02.01-0015 Agreement #: [* insert Agreement #]




Design Guidance Data

DID E005-1






PURPOSE

Design Guidance Data is required to enable the final design of the Ship to proceed.

SCOPE

Information as required below.

REFERENCES



The Supplier shall provide a DID Compliance Matrix indicating which submission files contain the items listed in this DID.


CONTENT AND FORMAT

Unless otherwise specifically stated in this DID, all physical parameters quoted below are to be the actual final design standard.

Where applicable the following Technical Information shall be provided:

(a) General description of the Equipment (along with the normal and emergency operating modes, controls, and any other relevant functionality).

(b) General arrangement drawings of the Equipment, including indications of access and maintenance spaces.

(c) Piping and instrumentation diagram (P&ID) of the Equipment including:

(i) Stream names, flow rates, flow directions, pressure, temperatures;

(ii) Equipment descriptions: make, type, size, capacity;

(iii) Line sizes, piping connections;

(iv) Piping specifications;

(v) Instruments and controls with ranges and set points;

(vi) Heat tracing requirements;

(vii) Insulation type and thickness:

(viii) Symbols legend; and

(ix) Identifiers which relate items in the P&ID to Bills of Materials.




(d) Overall and other leading dimensions of the Equipment.

(e) Dry weights of the Equipment, must be within 4% of the final weight.

(f) Wet weights of the Equipment, must be within 4% of the final weight.

(g) Performance details listed in the Supplier’s Specifications supported by type test results if available.

(h) The time required for the Equipment to reach full output.

(i) Guaranteed maximum requirements for cooling water, compressed air, etc.

(j) Heat dissipation of the Equipment in to the space.

(k) Pump information:

(i) Pump shaft bearing life in hours of continuous running;

(ii) Pump shaft seal life in hours of continuous running; and

(iii) Pump Minimum Efficiency Index (MEI) rating for pumps larger than 1 hp.

(l) Electrical demands and specifications (voltages, frequencies, phase, etc…) including full load currents, maximum continuous load, average power, duty cycle, full load power factors, starting/in-rush currents, quality of electric power supply, starting current duration, starting power factors and any harmonic distortion effects produced by the load.

(m) Motor starter details.

(n) Operating temperatures.

(o) The engineering standards applicable.

(p) Airborne noise measurements and vibration measurements.

(q) A clear statement or drawing detailing the scope of supply, drawing attention to associated items that will have to be procured by the Purchaser (if any).

(r) Information on oils and greases as required below:

(i) Oils (see Schedule B3 (General Technical Requirements, VCRI and Compliance Matrix); and

(ii) Greases (see Schedule B3 (General Technical Requirements, VCRI and Compliance Matrix).

(s) An electrical interconnectivity diagram in the format of the example shown in Attachment A, including labels with electrical details for all interconnections.

(t) Wiring diagrams.

(u) Cable lists.

(v) Drawings showing the size and location with dimensional tolerances of the Equipment’s piping connections to external




interfaces.

(w) Drawings showing the size and location with dimensional tolerances of Equipment’s cable entry, connector type, terminations, wiring details, and connectors to external interfaces; including gland size if appropriate and power supply cable route(s) within the Equipment unit.

(x) EMI/EMC (electromagnetic interference and compatibility) information.

(y) Regulatory Body Certifications.

(z) Certified Performance Test Curves.

(aa) For hydraulic systems also provide as a minimum:

(i) Heat exchanger data such as a rated heat transfer rate at given hot and cold side inlet temperatures and flows; and

(ii) Equipment and valve local control logic, where applicable.

(bb) Waveguide requirements and specifications, where applicable.

(cc) Details of seating, foundations, mounting and securing points together with hole sizes, securing bolt specifications and related dimensional tolerances.

(dd) Positions of lifting eyes where appropriate.

(ee) Detail of shock and vibration mounts where applicable.

(ff) Maintenance envelopes, access and withdrawal spaces for all Equipment items including isometric views and all primary views.

(gg) Electrical power:

(i) Whether or not the equipment presents an unbalanced load, and the actual loads presented;

(ii) Whether or not the equipment draws a pulsed current and if so, its characteristics;

(iii) Whether or not the equipment causes waveform distortion on the supply lines and if so, the magnitude and phase angle of each harmonic (voltage and current);

(iv) If 3 phase motors have an Active Front End (AFE) drive, then harmonics analysis must be provided up to the 100th current harmonic; and

(v) Whether or not the equipment is a source of radio interference, either mains borne or radiated, and to what degree.

(hh) Liquid cooling:

(i) Chilled water flow rates, pressures, temperature rise and heat quantity in kilowatts to be removed by chilled water supply;

(ii) How coolant failure is sensed and if override exists where applicable;




(iii) Time from loss of water flow for a critical component or components to reach:

a) Their maximum operating temperature; and

b) Failure temperature;

(iv) Chilled water temperature above which a critical component will exceed its maximum operating temperature; and

(v) If fitted with a temperature sensor/trip, time from loss of coolant before warning or trip occurs where applicable.

(ii) Air cooling:

(i) For equipment that relies on compartment air cooling, the ambient temperature at which critical components will reach maximum operating temperature; and

(ii) If fitted with a temperature sensor/trip, and whether fitted with an override.

(jj) Other services:

(i) Dry air, hydraulic power, HP air etc., quantity, quality and dependencies are to be stated.

(kk) A signal interface diagram identifying all equipment signal interfaces for remote control and surveillance of the Equipment, The diagram shall include as a minimum:

(i) Remote control switched inputs (e.g. Start/Stop, Valve Actuation, etc.);

(ii) Remote switched outputs (e.g. plant status indication, etc.);

(iii) Alarm and warning indicators (3 wire volt free contacts);

(iv) Analogue surveillance signals (4 - 20 mA);

(v) Temperature sensors (PRTs, Cr/Al thermocouples etc.); and

(vi) Vibration, speed, flow signals.

(ll) Although not common, in the event that the ship’s IPMS will have sequenced automation control over the Equipment (Purchaser will advise if this is the case) then the Supplier shall provide control logic sequences for the Equipment.

(mm) Weights of each interchangeable assembly/sub-assembly in excess of 70kg.

(nn) Antenna Clear Arcs and Seating Details, (flatness/level/ thickness etc.).

(oo) Stiffness of mounting structures.

(pp) The Supplier must provide 3D Computer Aided Drafting (CAD) files for all provided equipment with the following parameters:

(i) The file format must be AutoCAD 3D “.dwg”, or one of the following file types (which is suitable for import into AutoCAD 2016);




a) IGES - .igs, .iges;

b) STEP - .stp, .step;

c) Solidworks 2014 - .prt, .sldprt, .asm, .sldasm;

d) Autodesk Inventor 2014 - .ipt, .asm; or

e) Rhino 4 or 5 - .3dm;

(ii) 3D models must be simplified (with a target maximum size of less than 1 Mb) and must not include unnecessary details (eg. shall not include unnecessary internal parts or features) for computer performance reasons, yet must be adequately detailed to convey the physical attributes of the Equipment as provided in the this DID E001, and E002 including:

a) External shape;

b) Centre of mass location;

c) Mounting features;

d) Maintenance and service envelopes are to be included as a separate layer, object or file. These envelopes to include cabinet doors, service panels and other areas needing ongoing inspection and/or maintenance;

e) Lifting points;

f) All pipe connections (water, coolant, hydraulic, compressed air, fuel, exhaust, etc.); and

g) All electrical power, control and instrumentation connection points, control fluids and pressure gauge port connections;

(iii) Separate 3D files shall be supplied for each self-standing / loose equipment part (note, single part representations of a merged assembly are acceptable). For example: An incinerator would be one file, and the loose shipped spark arrestor would be one file; Skid mounted assemblies (5 pumps on one skid) would be one file;

(iv) The 3D model must be in SI units, specifically millimeters for physical parameters and kilograms for mass properties; and

(v) The 3D model shall use an XYZ coordinate system with +Z representing vertical up when installed in the conventional orientation aboard a ship and with an origin located at the center of mass of the part.

(qq) Any specialised technical information not already included in SDRL and DID E003.

(rr) The Equipment Specifications Table (see Attachment B) shall be populated with the following information for each piece of Equipment:

(i) ID Number (provided by Purchaser);




(ii) Equipment Name;

(iii) Original Equipment Manufacturer;

(iv) OEM Model Number;

(v) Quantity;

(vi) Name Plate Description;

(vii) Dry Weight (kg) (see paragraph (e) above);

(viii) Wet Weight (kg) (see paragraph (f) above);

(ix) Width (mm);

(x) Depth (mm);

(xi) Height (mm);

(xii) C of G Width (mm);

(xiii) C of G Depth (mm);

(xiv) C of G Height (mm);

(xv) Maintenance Space Required? (y/n);

(xvi) Acoustic Noise Level (dBA);

(xvii) Heat Dissipation (kW);

(xviii) Pertinent Equipment Ratings (eg Crane Rating);

(xix) Electric Power Voltage (V)/Frequency (Hz)/Phase;

(xx) Power Required (kW);

(xxi) Protection Class (Ingress Protection Rating);

(xxii) Construction Materials;

(xxiii) Design Standards Used;

(xxiv) Motor Starter Type;

(xxv) Temperature Rating;

(xxvi) Chilled Water Flow (m^3/hr);

(xxvii) Chilled Water Pressure (bar);




(xxviii) Chilled Water Press. Drop (bar);

(xxix) Chilled Water Load/Duty (kW);

(xxx) Chilled Water Design Temp. Differential ('C);

(xxxi) Air Pressure Min /Max (bar);

(xxxii) Air Quantity (Std. m^3/min);

(xxxiii) Air Dryness Dewpoint ('C);

(xxxiv) Air Purity (Micron); and

(xxxv) Air Oil Content (ppm).

STRUCTURE

Separate file submission where appropriate (eg. Where the information requested does not reside as part of an interconnectivity diagram or the Equipment Specifications Table).

• I.a.w Attachment A: Interconnectivity Diagram Example • I.a.w Attachment B: Equipment Specifications Table in Excel format • Separate file submission where appropriate (eg. Where the information requested does not reside as part of an

interconnectivity diagram or the Equipment Specifications Table)


Information that pertains to Equipment physical dimensions and arrangements shall be provided in AutoCAD format (.dwg) to facilitate the development of ship arrangement drawings.

All fields in Attachment A shall be completed, if a piece of information is not applicable “NA” shall be entered.




Attachment A

Interconnectivity Diagram

EQUIPMENT: [* insert description of the Equipment]

ALL CABLES TO AND FROM EQUIPMENT WITHIN A SYSTEM SHOULD BE IDENTIFIED ON THIS DIAGRAM

UNIT A UNIT B UNIT C

POWERSUPPLY

FOR EXAMPLE




Attachment B




Original Equipment

Manufacturer

OEM Model


Description

Dry Weight

(kg) [+/- %

noted in paragraph

(e)]

Wet Weight

(kg) [+/- %

noted in paragraph

(f)]

Width (mm)

Depth (mm)

Height (mm)

C of G Width (mm)

C of G Depth (mm)

C of G Height (mm)

Maintenance Space

Required? (y/n)

Acoustic Noise Level

(dBA)

Heat Dissipation (kW)





ID Number Pertinent Equipment

Ratings (eg Crane Rating)

Electric Power Voltage (V)/Frequency (Hz)/Phase Power Required (kW) Protection Class

(IP Rating) Construction Materials Design Standards Used Motor Starter Type Temperature Rating





ID Number Chilled Water Flow (m^3/hr)


(bar)


(bar)


(kW)


('C)




Air Purity (Micron)


Comments on Compartment Layouts, Rev 2 Document #: VSY-A02.01-0021 Agreement #: [* insert Agreement #]




Comments on Compartment Layouts

DID E006



Comments on Compartment Layouts, Rev 2 Document #: VSY-A02.01-0021 Agreement #: [* insert Agreement #]



PURPOSE

To assure the Purchaser that the Equipment is compatible with the compartment arrangements.

SCOPE

The Supplier is to review applicable compartment layout drawings and 3D model files (NavisWorks) and/or 3D model views (screen shots) produced by the Purchaser. These reviews shall include feasibility and safety of installation, removal and operation of the Equipment.

REFERENCES

This DID must be read in conjunction with the SOW.


CONTENT AND FORMAT

The Subcontractor shall provide a statement to confirm that the compartment layout will not impede the Equipment’s operability. This will include all items fitted within the ship and on weatherdecks.

STRUCTURE

This should include the Equipment name, the compartment name, number and the statement to confirm that the compartment will not impede the Equipment’s operability.


Soft copies of the layout will be made available by the Purchaser.

Engineering Report, Rev 2 Document #: VSY-A02.01-0002 Agreement #: [* insert Agreement #]



Document Identifier Number: VSY-A02.05-0002 Rev: 1

Title: DID E010 - Engineering Report Ship applicability: All

Master Template Ref: DID Template Project: Joint Support Ship


DID VSY Engineering N/A N/A All


Engineering Report

DID E010



Engineering Report, Rev 2 Document #: VSY-A02.01-0002 Agreement #: [* insert Agreement #]



PURPOSE

The Engineering Report shall document the technical process implemented by the Supplier in identifying, reviewing and resolving engineering tasks performed as a result of a deviation to the Contractor’s Level 1 Schedule, as described in a Red Flag Report, Recovery Plan, proposed Change Request and/or Non-Conformance report.

SCOPE

This DID contains the preparation instructions, content, structure and special instructions, for the preparation of an Engineering Report.


Contractor’s format.

CONTENT

The Engineering Report shall contain the following information:

1. Description of the original problem or error

The Contractor shall provide in this section an in depth review and analysis of the events that necessitated the engineering effort.

2. Description of the effect upon the Articles.

The Contractor shall provide in this section detail of the impact of the problem upon the Articles, including the extent of any deviation from interfaces and an understanding of how different shipsets have been affected (if applicable).

3. Discussion of Options

The Contractor shall provide in this section a discussion of the options considered. This shall also address the trade-off studies used to arrive at the recommended solution.

4. The proposed technical solution for the rectification of errors as applied to the detail at 2 above.

The Contractor shall provide in this section information pertaining to the execution of the schedule of work agreed with the Purchaser to rectify the problem or error. Any diagnostic results from the rectification and specific information on any materials was used in the process of rectification should be supplied.

5. Conclusive assurance from Contractor.

The Contractor shall provide in this section supporting evidence that will demonstrate that the solution that has been applied is within the Requirements and does not necessitate the requirement for additional tests. Also, the Contractor should provide assurance that warranty and/or guarantees have not been affected.

STRUCTURE

Contractor defined format.


All documents referred to in the Engineering Report, if any, shall be attached to the Engineering Report at the time it is delivered.

Master Record Index, Rev 2 Document #: VSY-A02.01-0022 Agreement #: [* insert Agreement #]




Master Record Index

E011






PURPOSE

The Master Record Index (MRI) defines the configuration of the build of the Equipment, the relationship between documentation and the Equipment hierarchy, and the relationship between support equipment and the Equipment hierarchy.

REFERENCES




FORMAT AND CONTENT

1 As a minimum, the MRI shall consist of the following:

(a) Index of Amendments And Modifications;

(b) Asset Breakdown Structure;

(c) Index of Configuration Documentation;

(d) Index of Ancillary Equipment.

Index of Amendments and Modifications

1 Index of ‘amendments and modifications’ shall list all amendments and modifications introduced that effect the Equipment design.

Asset Breakdown Structure

1 The Asset Breakdown Structure (ABS) shall list, in hierarchical form, all the Equipment, subsystems and parts constituting the Equipment.

2 For each piece of Equipment, the ABS shall detail the following information:

(a) ABS Number (ABSN): this field shall define a unique identification number for each line entry;

(b) Name: this field shall detail the name allocated to the line entry;

(c) Type: this field shall detail whether the line entry item is a Hardware or Software;

(d) Hardware: this field is applicable to Software line entries only and shall detail the Hardware that the Software is resident in;

(e) Parent ABSN: this field shall detail the ABSN of the line entry’s parent (or next higher level assembly);




(f) Indenture Level: this field shall detail the indenture level of the line entry within the ABS (eg level 1 is the highest level in the structure); and

(g) Supplier Part Number: this field shall document the Supplier Part Number for the line entry.

(h) Supplier Part Number Revision: this field shall document the revision of the Supplier Part Number;

(i) Supplier Part Number Status: this field shall contain the status of the Part Number (e.g. PROPOSED, CURRENT, OBSOLETE and HISTORICAL);

(j) OEM Part Number: this field shall document the Supplier Part Number for the line entry;

(k) OEM Part Number Revision: this field shall document the revision of the Supplier Part Number, as applicable;

(l) Alternate OEM Part Numbers: When more than one variant of a part has been used in the construction of the Equipment the alternate part numbers used shall be provided (including revision);

(m) Quantity Fitted: this field shall document the quantity of the Item fitted to the Item’s next higher assembly;

(n) Quantity Procured: This field shall document the quantity of the item procured, applicable only to the Equipment level.

Index of Configuration Documentation

3 The Index of Configuration Documentation (IOCD) shall list the Configuration Documentation describing the functional, allocated and product baselines for the System.

4 For each document, the IOCD shall detail the following information:

(a) Reference ABSN. This field shall detail the ABSN(s) from the ABS that the document is applicable to;

(b) Reference Equipment Name. This field shall detail the name(s) from the ABS that the document is applicable to;

(c) Document Number: This field shall detail the number of the document;

(d) Document Revision. This field shall detail the Revision of the Document;

(e) Document Title. This field shall detail the title of the document;

(f) Document Type. This field shall detail the type of document the Document belongs to, for example:

a. Drawing;

b. Specification Sheet;

c. System Manual;

d. Operating Manual;

e. Maintenance Manual;

f. Installation Manual (includes setting to work);




g. Design Guidance Data Compliance Matrices (from SDRL E001, E002, E003);

h. Equipment Specifications Table (from SDRL E001, E002, E003);

i. Interface Data Sheet;

j. IPMS Signal List;

k. Software Version Description;

l. Test Plans & Procedures;

m. Test Reports;

n. Other (please specify);

(g) Drawing Type. This field shall detail the type of drawing when drawings are listed (eg P&ID, System Block Diagram, Wiring Diagram, General Arrangement, Reliability Block Diagram, Other (please specify), etc).

Index of Ancillary Equipment

5 The Index of Ancillary Equipment (IAE) shall list the Support Equipment required to support the maintenance/operation of the System and its constituent Items. Note: Support Equipment includes, but shall not be limited to Automatic Test Equipment and Special-to-Type Tooling.

6 For each piece of Support Equipment, the IAE shall detail the following information:

(a) Support Equipment Name. This field shall document the name of the Support Equipment;

(b) Support Equipment Part Number: This field shall document the support equipment part number.

(c) Support Equipment Type. This field shall document the support equipment type the Support Equipment belongs to (for example Ground Support Equipment, Automatic Test Equipment, Special to Type Tooling, etc);

(d) Reference ABSN. This field shall document the ABSN(s) from the ABS that the Support Equipment is applicable to;

(e) Part Revision. This field shall document the Part revision supported by the Support Equipment; and

(f) Affected Part Numbers. If the Item(s) supported by the Support Equipment is (are) below the ABSN level then this field shall document the Part Number(s) of the Item(s) supported by the Support Equipment.


The submission shall be made in MS Excel format with each listing resident on a suitably named tab (eg ABS, IOCD, IAE).

Equipment Noise and Vibration Testing, Rev 0 Document #: VSY-A08.22-0168 Agreement #: [* insert Agreement #]




Equipment Noise and Vibration Testing

DID E073-6

Pr epar ed by: Vancouver Shi pyar ds Co. Ltd. 50 Pe mber ton Ave. Nor th Van couver , BC, Canada, V 7 P 2R 2 T el : ( 604) 988 - 3111 F ax: ( 604) 984 - 1636





PURPOSE

The purpose of this DID is to describe the requirements for the Equipment Noise Level Testing.

REFERENCES

ISO 11200 series: Acoustics -- Noise emitted by machinery and equipment -- Guidelines for the use of basic standards for the determination of emission sound pressure levels at a work station and at other specified positions


This Data Item shall comply with the general format, content, and preparation instructions set out in Part 1 (Introduction) of Schedule D1 (SOW) and Part 1 of Schedule D2 (SDRL).

The reports must be presented, including text, graphs, and supporting calculations. All input data must be provided electronically with the results (see Deliverables).

CONTENT AND FORMAT

See format on following pages.

DELIVERABLES

One (1) digital package including text, drawings, tabulated results of analysis and all supporting data used in the development of this DID must be provided.




Supplier:

Equipment (list of):

Noise source equipment size (L x W x H): ____________________________________ m

Vibration source equipment foundation (L x W): ______________________________ m

Vibration source equipment mass: _________________________________________ kg

Narrow band component, Yes □ No □ Frequency / Octave band: Hz__________________________________________________

Method of the Noise Level Test: _______________________________________________________________________________________

Note 1 – The vibration levels shall be as measured at the structural supports. For vibration isolated machinery the vibration shall be measured on the top of the vibration isolators.

Supplier Data –airborne noise level limits – to be filled by the Supplier

Item tag and description

Sound Pressure Level (SPL) in dB (re. 20 µPa) at 1.0 m distance free field condition

dB(A) Octave Band Centre Frequency, Hz

31.5 63 125 250 500 1000

2000

4000

8000

Supplier Data – vibration level limits – to be filled by the Supplier

Item tag and description

Vibration Levels, La in dB (re. 10 µm/s2) note 1 Isolation mounts (yes/no)

Octave Band Centre Frequency, Hz 31.5 63 125 250 500 100

0 200

0 400

0 800

0




1. Air borne noise measurement For measurements of free field sound pressure levels at specified positions, the standards in the ISO 11200 series should be used. Alternatively, specific product standards based on these main standards may be used. When the machine is installed in a room, the noise level will be higher than in a free field. The standards stipulate corrections for the reflected noise caused by the room, so that free field values can be calculated ISO 11201 with engineering grade of accuracy is recommended.

Noise data should be provided as: > Preferable: sound pressure level (SPL) in dB relative to 20 µPa, measured at 1.0 m distance in free field condition. > Alternative: sound power level (SWL) in dB relative to 1 pW. > Other: Other noise measurement system that is convertible to SPL. The conditions of measurement need to be specified.

2. Vibration measurement Vibration from the machinery supports will always be transmitted to adjacent areas and radiate noise, i.e. structure borne noise. In work areas, structure borne noise may usually be neglected compared to air transmitted noise. There are exceptions, however, and especially in living quarters and control rooms the structure borne noise level should be evaluated.

The input data for analysis of structure borne noise from machinery shall be given as vibration level at the supports. For vibration isolated machinery the vibration shall be measured on the top of the vibration isolators. The vibration level in these positions is for medium and high frequencies independent of the stiffness of the deck, and is easy to control by measurements. The mean value of the vibration level of all the supports points should be given in octave bands from 31.5 to 8000 Hz.

Vibration data should be provided as: > Preferable: acceleration level dB relative to 10 µm/s2 (10 µm/s2 10-6 is approximately equal to 1 µg (9, 81 x 10-6 m/s2)). > Other: Other vibration measurement system that is convertible to acceleration levels. The place of measurement need to be specified.

For a machine that is fastened directly to the deck, the vibration level at the support points will depend on the stiffness and other details of the deck and support points. Vibration shall be measured at the carrying frames as near as possible to the machine support points. The mean value of vibration on the supports shall be given, as specified above. These data are only valuable if the details of the deck, frames and supports, in which the measurements are taken, are described in detail.

* In general all vibration generating equipment intended for continuous operation should be mounted on vibration isolation mounts. A single stage of standard marine grade vibration isolation mounts is considered adequate for all equipment. The design details of the vibration isolation system and the technical specification of the vibration isolators shall be presented to the Purchaser for approval.

As a recommendation, all isolation mounted systems should be evaluated for mount loading and six degree of freedom resonance avoidance. In cases where the entire equipment skid is mounted on vibration isolators, and the flexible connections to fixed pipes and ducts are supplied by others, if required, the Supplier may request information for the flexible connections from the Purchaser.

Final Certified Weight, Rev 1 Document #: VSY-A02.01-0041 Agreement #: [* insert Agreement #]




Final Certified Weight

DID E096



.




PURPOSE

Supplier weight control is required in order for the Supplier to be to be conscious of the mass properties of the Equipment throughout the design and manufacture and its impact on the Ship on which it will be installed. Weight and moment control is critical to the Purchaser meeting its naval architectural contractual requirements for list, trim, service life allowance, and performance. Therefore, it is imperative that the Supplier submit accurate weight data for the purchased item.

REFERENCES





CONTENT AND STRUCTURE

CONTENT

The Supplier shall report weight and centre of gravity information to the purchaser as follows:

1. Final Certified Weight - Prior to crating of the Equipment for shipment, the Supplier shall weigh the Equipment. The following information shall be forwarded to the Purchaser:

a) Scale weight of the Equipment (with clear indication of dry or wet weight); b) List of accessories and other parts of the Equipment which have not been included in the above weight; c) Brief description of the weighing device:

i. Type and make of scale; ii. Accuracy; iii. Maximum rated capacity; iv. Sensitivity; and v. Scale calibration data.

2. Location of Centre of Gravity - The supplier shall provide a location of the centre of gravity of the Equipment in an

operating condition.

STRUCTURE

• Attachment A: Equipment Centre of Gravity Specifications Sketch • Attachment B: Supplier Equipment Weight Reporting Form


Notes for completing Attachment A - Equipment Centre of Gravity Specifications Sketch

Provide an estimated location of the Center of Gravity of the Equipment in an operating condition by a sketch as per the sample format provided. If already provided on a drawing supplied by the Supplier, just submit the drawing; a sketch would not be required.




Notes for completing Attachment B - Supplier Equipment Weight Reporting Form

Each individual or separate Equipment Item supplied should be reflected on this form. Additional sheets may be added as necessary to provide the information requested.

A. Supplier Information:

1. Enter name of your company for Supplier Name. 2. Provide the name of the original manufacturer, if you are acting as an agent for a product produced by another firm. If

you are both the supplier and the manufacturer, this box may be left blank. 3. Provide the model number of the supplied item(s) if applicable. 4. Provide the Purchase Order No. and Item No. under which you are providing this Equipment. 5. Provide a brief description of the Item(s) being supplied. 6. Provide the VSY Part Number of the item(s), if known. Otherwise, leave blank. 7. Provide the Supplier Drawing Number, which describes the item(s) supplied. 8. Enter VSY Hull Number if known, otherwise, leave blank. 9. Enter VSY Drawing Number if known, otherwise, leave blank.

B. Weighed Weight and CG Information:

10. Enter name of Weighed Item of Equipment. 11. Provide the unit weighed weight of each Item of Equipment.

This weight should not include any packaging, dunnage, or temporary additions. The weight reported should be the weight of the Item of Equipment, as it will be installed on the Ship. Use appropriate unit of measure, for example:

A. For pipe and cable, weight should be reported as kg per linear meter. B. For tile, weight should be reported as kg, per cubic meter or kg per square meter.

C. List of Item(s) Not Included in Weighed Weight:

12. Enter the estimated/calculated weight of any missing operating fluids or additional accessories not included in the weighed weight that are required for a normal operating ship condition.

D. Weighing Equipment Information:

13. Provide the information on the weighing equipment used to measure weight.

E. Approval Signature:

14. Provide signature/name signifying that the data provided for use in weight estimating accurately and completely describes the item furnished to the best of your capability.

F. Proof of Calibration

15. Provide attachment with evidence of calibration of weighing equipment used at time of weighing (i.e. Calibration Certificate)




Attachment A – Sample Centre of Gravity Sketch

Sketch Indicating the Centre of Gravity and Reference Points:




Attachment B - Supplier Weight Reporting Form A. Supplier Information:

Supplier Information

Supplier Name:

Manufacturer (If Different than Supplier):

Model Number (If Applicable):

Purchase Order Number:

VSY Part Number:

Hull Number:

Supplier Drawing Number(s):

VSY Drawing Number(s):

B. Weight Information of Weighed Equipment(s):

Final Recorded Weight(s)

Weighed Item of Equipment Recorded Weight (kg) Notes

C. List of Item(s) Not Included in Weighed Weight (i.e. Operating Fluids etc.):

Additional Items Not Weighed, Required for Normal Ship Operation

Item of Equipment Weight (kg) Notes

D. Weighing Equipment Information:

Weighing Equipment

Make:

Type:

Range:

Accuracy:

Calibration Date:

Date Weighed:

E. Approval Signature

The Technical Information on This Form Accurately and Completely Describe the Item(s) Furnished

Printed Name:

Signature:

Date:

F. Proof of Calibration Attach evidence of calibration of weighing equipment at time of weighing (i.e. Calibration Certificate)

Equipment Safety Questionnaire, Rev 2 Document #: VSY-A02.01-0023 Agreement #: [* insert Agreement #]




Equipment Safety Questionnaire

DID E101






PURPOSE

The purpose of the Safety Questionnaire is to allow the Purchaser to identify any likely hazards that exist or are likely to exist.

SCOPE

To provide a statement on the Safety aspects of the Equipment by completing the attached questionnaire. All sections must be completed including identification of those not applicable.

REFERENCES



CONTENT

I.a.w. Attachment A

STRUCTURE

I.a.w. Attachment A


Nil




[* insert name of Project] Project

Attachment A to DID E101

Safety Questionnaire

[* insert name of Equipment]

Produced by: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

<Name> <Company / Position in Company>

Authorised by: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Approved by: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





0.1 AMENDMENT RECORD

Issue Status Issue Date Inserted By Date Inserted

0.2 INSTRUCTIONS FOR COMPLETION

1. The questionnaire addresses the Platform Systems, Combat System, systems, assemblies and Equipment, only in so far as they are supplied, assembled or installed by a single contractor or group of contractors independent of the Purchaser.

(Note: Hazards arising from Platform Systems, Combat System, systems, assemblies and Equipment manufactured or installed by the contractor are to be addressed in the Hazard Log).

2. The questionnaire is intended to demonstrate that the Platform Systems, Combat System, systems, assemblies and Equipment is safe or to identify any safety hazards that are intrinsic to the system, assemblies or Equipment.

3. The questionnaire is intended to guide the Project Safety Management in the mitigation of any additional hazards arising as a result of the installation of the Platform Systems, Combat System, systems, assemblies and Equipment being installed on the Vessels.

4. The questionnaire is intended to be comprehensive in establishing the safety of any Platform Systems, Combat System, systems, assemblies and Equipment, however it is incumbent on the Sub-contractor to provide any additional information relevant to the aim of reducing hazards to a level as low as is reasonably practical.

5. This questionnaire will form part of an auditable trail in the preparation of the ship safety case and therefore any answer given may require justification.

6. Please give a response to all questions, should a question(s) be inapplicable to the system / Equipment please indicate by entering N/A next to the “No” box for that question(s).

7. Use reverse of questionnaire sheets, or insert additional pages, as necessary.




0.3 TABLE OF CONTENTS 1 GENERAL ............................................................................................................................................................................................... 6 2 FLUID SYSTEM SAFETY ....................................................................................................................................................................... 7 3 MECHANICAL SAFETY .......................................................................................................................................................................... 9 4 ELECTRICAL SAFETY ........................................................................................................................................................................... 11 5 RF RADIATION HAZARDS (RADHAZ) ................................................................................................................................................... 12 6 ACOUSTIC RADIATION HAZARDS ....................................................................................................................................................... 13 7 IONISING RADIATION HAZARDS ......................................................................................................................................................... 13 8 CHEMICAL AND ENVIRONMENTAL HAZARDS .................................................................................................................................... 14 9 LASER HAZARDS .................................................................................................................................................................................. 15 10 FIRE HAZARDS .................................................................................................................................................................................... 16 11 SAFETY RELATED SOFTWARE ......................................................................................................................................................... 16 12 FINALLY... ............................................................................................................................................................................................ 17




1 GENERAL

1.1 STANDARDS

Has the Equipment or any of its major components been tested / approved under any recognised code? (e.g. BS, ISO, Classification Society).

YES NO

If YES Specify Equipment/ component and give the relevant standard(s).

1.2 SYSTEM/EQUIPMENT ACCEPTANCE INTO SERVICE STATUS

What, if any, ‘introduction into service’ procedures have been conducted, are planned or programmed?

When did it, or is it expected to, enter service?

How many are, or expected to be, in service?

Give details of Handbook / Drawing Ref. Nos.

1.3 SAFETY ASSESSMENT

Have any hazards, i.e. hazards associated with magazine design and the application of magazine explosive regulations, been identified for the system / Equipment?

YES NO

If YES specify hazards identified.

Has an assessment of potential Hazards been made? YES NO

If YES give details of assessment findings.

Has the assessment or customer requirement identified the need for dedicated magazines. E.g. SHIPCAT 5? YES NO

If Yes produce an Armaments Statement iaw [* insert standard].

Have Hazards been categorised into ones affecting the Health and Safety of Personnel and ones causing possible damage to Material / Equipment / Environment?

YES NO

What mitigating precautions have been identified?

1.4 OPERATOR AND MAINTAINER SAFETY

In the normal operating mode are all protective guards in place? YES NO

Are suitable electrical and/or mechanical interlocks provided? YES NO

Has allowance has been made for full and safe access by both Operators and Maintainers in the confined spaces of a sea-going vessel?

YES NO

If YES specify measures taken.

1.5 ALARMS AND WARNING MARKINGS

Are Audible and/or Visual ALARMS incorporated? (e.g. bells, lamps/lights) YES NO

If YES specify type and location.

Are WARNING MARKINGS incorporated, both externally and internally? (e.g. on mountings, inside electronic cabinets) YES NO

If YES specify type and location.




Is a monitoring system required for the ALARMS and/or WARNING indications? YES NO

If YES specify type.

Are the ALARMS and WARNING systems provided with Acceptance, Resetting and Emergency Muting facilities? YES NO

Are WARNING MARKINGS coloured in accordance with BS 5378/1980? YES NO

Are there any alarms/ warning test arrangements included in Equipment supplied? YES NO

1.6 HANDBOOKS (SYSTEMS & EQUIPMENTS)

Are all potential Hazards documented in the appropriate publications? (e.g. handbooks, drawings, etc.) YES NO

Are appropriate Hazard Warning signs graphically illustrated indicating type, colour and size in all handbooks and drawings? YES NO

1.7 SHIP’S HAZARD STATEBOARD

Hazard Stateboard identified? YES NO

If YES please identify hazards below.

Are suitable locking devices (keys, fuses, etc.) provided, and clearly marked with engraved tallies attached?

2 FLUID SYSTEM SAFETY

2.1 STANDARDS

Have the components (including pipes) been manufactured / tested / approved under any recognised code (e.g. BS, ISO, Classification Society?)

YES NO

If YES specify Equipment/component and give the relevant standard(s).

If NO please provide justification.

2.2 ASSEMBLY STANDARDS

Have the major components been assembled under any recognised code (e.g. BS, ISO, Classification Society, shipyard published standard)?

YES NO

If YES give the relevant standard(s).


2.3 TESTS AND COMMISSIONING

Is the system required to be subjected to any acceptance test (e.g. pressure test)? YES NO

If YES give details of the relevant test parameters or acceptance criteria.





2.4 VALVES - SUPPLIED WITH SYSTEMS

Are all valves clearly marked with permanent tallies to indicate function? YES NO

Are all valves clearly marked with permanent tallies to indicate direction of opening/closing? YES NO

Are valves part of a safety Related system? YES NO

Are valves required to be operated remotely? YES NO

If YES is remote operation Manual / Mechanical (delete as appropriate) Manual Valves

Are extended spindles free of articulation/gearing? YES NO

Do spindles require support bearings? YES NO

Has provision been made for lubricating bearings/gears? YES NO

Can valves be operated without the use of keys? YES NO

Mechanical Valves (electrically/pneumatically/hydraulically actuated)

Are electrical connections protected from fluid leakage? YES NO

Are indicator lamps provided to show state of valve? YES NO

Are moving/rotating parts fitted with guards? YES NO

2.5 SYSTEM HAZARDS

Are system fluids at pressures exceeding 1 bar? YES NO

Are system fluids at temperature below 70 C or above -10 C? YES NO

Is pipework insulated? (see also section 10) YES NO

Is insulation non-flammable? (see also section 10) YES NO

2.6 FLUID HAZARDS

Are system fluids non-corrosive? (see also section 8) YES NO

Are system fluids non-flammable? (see also section 10) YES NO

Are system fluids hazardous to the environment? YES NO

If YES what precautions are necessary to prevent discharge during

maintenance? (see also section 8)




de-commissioning? (see also section 8)

3 MECHANICAL SAFETY

3.1 SEA-GOING ENVIRONMENT

Is the System/Equipment designed to operate and be maintained in a sea-going environment? YES NO

Is the design ‘fail-safe’ in terms of:

Personnel Safety? YES NO

Ship Safety? YES NO

Equipment Safety? YES NO

To what maximum angles of ship pitch and roll will correct operation and functioning continue?

Will correct operation and functioning continue when subjected to ship vibration? Specify design levels: YES NO

Has the system/ Equipment been shock tested? YES NO

3.2 MOVING STRUCTURES

What Hazards associated with large moving structures exist? (e.g. gun mountings, antennas, etc.)

Can movement be positively inhibited making authorised access safe? (see also paragraph. 1.7 above) YES NO

What mechanical locking devices are provided for both manual and electro-mechanically controlled movement?

Can positive “locking-off” of power be achieved prior to manual operation, if required? YES NO

What special features are fitted, or what special procedures are to be implemented, to protect other systems/Equipment, or personnel, during normal operation? (e.g. inhibiting of gun firing circuits when line of fire traverses the weather deck)

How are personnel protected from moving parts? (e.g. physical guards fitted to ammunition hoists, missile handling Equipment, etc.)

Are positions of servicing and lubricating points located clear of moving parts to ensure the safety of maintenance personnel? YES NO

3.3 SAFETY KEYS

Are unique ‘Safe to Rotate/Safe to Operate’ Keys provided, in duplicate, which are suitably and clearly identified with a non-removable engraved tally plate? (see also paragraph. 1.7 above)

YES NO

Does removal of the KEY render it impossible to start powered motion in normal operating

conditions? YES NO

Does removal of the KEY during powered motion render it impossible to continue powered motion? YES NO

Are the KEY locks of a type which can only be replaced, as a unit, from the outside? YES NO




Is a label provided adjacent to the locking device worded ‘SAFE -to-ROTATE or OPERATE’? (see also paragraph. 1.4 above) YES NO

Are labels provided clearly informing personnel of the need for safe operation? (see also paragraph. 1.5 above) YES NO

3.4 EMERGENCY-STOP PUSHES

What EMERGENCY-STOP Pushes are fitted, or specified as a requirement for the ship fitting arrangements?

Are they conspicuous and coloured with warning signs i.a.w. BS 5378 Part 3? YES NO

Are they positioned within easy reach of personnel and on or near any moving machinery? YES NO

Are they available for operation without the need to remove protective covers? YES NO

Are they un-shrouded? YES NO

Are they outside the Danger Arc of any remotely controlled machinery? YES NO

3.5 WITHDRAWABLE UNITS

What Withdrawable Units are incorporated?

Are units which can be withdrawn from their housings for maintenance purposes provided with a positive mechanical locking device/arrangement? (e.g. on telescopic runners)

YES NO

What means are used on removable units to permit removal, insertion and handling without dropping, tipping, or tilting and to ensure correct fitting? (e.g. adequate handling facilities, mechanical key-ways)

3.6 ARRANGEMENTS FOR HANDLING, LIFTING OR MOVING

What arrangements are fitted, provided, or specified as a requirement, to allow the necessary handling, lifting or moving by personnel during normal operation and maintenance?

What is the maximum weight of any item which has to be handled, lifted or moved, (including any items designated as portable) during normal operation and maintenance?

3.7 EXPOSED OR DANGEROUS LOCATIONS

Is safe access possible with the Equipment installed in an exposed and/or hazardous situation? YES NO

Are safe platforms fitted around or near rotating or moving Equipment, or specified as a requirement for the ship fitting? YES NO

What facilities or features are fitted, or procedures to be implemented to ensure that personnel can safely enter or leave manned moveable Equipment?

Is a suitable isolating device or key-switch fitted, or provided for ship fitting, to ensure the safety of maintenance personnel? (see also paragraph. 1.6 above)

YES NO

3.8 POWER ON INDICATION

Is a ‘Power ON’ indicator lamp fitted? YES NO

Is the lamp(s) clearly visible to the maintainer with the Equipment open? YES NO




4 ELECTRICAL SAFETY

4.1 GENERAL

What safeguards and precautions against the likelihood of electric shock are incorporated?

Are personnel (operators/maintainers) prevented from coming into contact with live parts while undertaking their normal duties? YES NO

Are Warning labels and Symbols for hazardous voltages clearly displayed? (see paragraph. 1.5 above) YES NO

Are isolating devices/locking-keys to protect personnel against hazardous voltages provided? (see paragraphs. 1.4 and 3.3 above) YES NO

Is a Power ON indicator lamp provided? (see paragraph. 3.8 above) YES NO

Is the build-up of static electricity precluded or its discharge ensured? YES NO

Are capacitors which are likely to remain charged provided with the means to be discharged either automatically or manually? YES NO

Is Equipment supplied by voltages above 50v DC ripple-free and 35v AC rms. rigidly enclosed? YES NO

4.2 EARTH BONDING

Are enclosures containing circuits operating with voltages exceeding 50v DC or 35v AC provided with a connection to the installation earth/grounding System?

YES NO

Will Equipment enclosures be effectively bonded to the ship’s structure? YES NO

Is a suitable earth terminal provided? YES NO

Are panels carrying electrically live metal parts insulated from the enclosure? YES NO

Are alternative bonding arrangements for operating outside normal condition designed to avoid the compromise of the safety bonding? YES NO

4.3 FUSES

Do any enclosures contain fuses? YES NO

Is the ‘LIVE’ end of each fuse clearly marked? YES NO

Does the arrangement of fuses and bus-bars render it impossible to accidentally bridge from line-to-earth or line-to-line? YES NO

4.4 EMERGENCY-STOP PUSH SWITCHES

(See paragraph. 3.4, above)

Are EMERGENCY-STOP Push Switches fitted? YES NO

Can Equipment only be re-started from the NORMAL position? YES NO

Does the design of the “PUSHES” preclude re-setting? YES NO

Are they available for operation without the need to remove protective covers?




YES NO

4.5 MAINTAINER SAFETY

What practical & operational measures are incorporated into the electrical features to ensure the safety of maintenance personnel?

Are electrical safety interlocks provided? (see also paragraph. 1.4b above) YES NO

Are internal pre-set controls easily and safely accessible? YES NO

Are Warning labels provided? (see also paragraph. 1.5 above) YES NO

4.6 WEAPON FIRING CIRCUITS

Are firing circuits part of the system? YES NO

Are firing circuit cables run in electrically resistant welded (ERW) steel conduit which is continuously earthed, and/or specified as a requirement for the ship fitting arrangements?

YES NO

Are conduit runs as short as possible and segregated from other wiring? YES NO

Are the firing circuit connector contacts remote from other high voltage contacts? YES NO

Are firing controls safeguarded by locked covers? YES NO

4.7 CATHODE-RAY TUBES

Are Cathode-ray tubes fitted which are liable to implosion? YES NO

If YES is a protective screen fitted? YES NO

If YES is the protective screen provided with a Warning label? YES NO

Do CRTs with a normal face dimension above 160 mm meet the requirements of BS 415? YES .NO

4.8 ELECTRICAL CABLING / WIRING

To what Standard(s) for electrical cabling/wiring is the proposed In-Service Equipment manufactured (e.g. use of LFH, PVC or PTFE coverings)?

To what Standard(s) for electrical cabling/wiring is the proposed New-to-Service Equipment manufactured (e.g. use of LFH, PVC or PTFE coverings)? (See also Question 10.1)

5 RF RADIATION HAZARDS (RADHAZ)

Will the design of the System / Equipment give rise to a RF Radiation Personnel Hazard? YES NO

If YES:

Are appropriate Warning Notices fitted to the antenna or wire feeders capable of being connected to a Transmitter having a mean unmodulated power of 50 Watts or greater?

YES NO




Are adequate earthing and bonding arrangements provided to prevent the build-up of RF induced voltages? YES NO

Are emitters of RF energy radiating more than 50 Watts or a field in excess of 100W/metre squared power density provided with the means to positively ‘lock-off’ the emission? (SAFE-to-TRANSMIT) (see also paragraphs. 1.7 and 3.3 above).

YES NO

5.1 PREVENTATIVE MEASURES

What arrangements are provided to prevent the hazardous irradiation of personnel, EEDs and fuel?

Can antenna power be cut-off or reduced to a safe level over designated areas? YES NO

Is the cut-off device incorporated designed to “fail-safe”? YES NO

Will antennas with normally continuous rotation or electronically switched beam steering cease transmission when stationary? YES NO

Can sector blanking be provided with either transmitter power OFF, or reduced power, with the means to accurately identify the sector blanked areas?

YES NO

Are antennas with variable azimuth and elevation motions provided with the means to accurately identify the beam position at the transmission cut-off point?

YES NO

6 ACOUSTIC RADIATION HAZARDS

Will the design of the System / Equipment give rise to an Acoustic Radiation Personnel Hazard? YES NO

If YES

Has the noise level been assessed and expressed i.a.w. BS 3045? YES NO

Has a noise emission test certificate been provided? YES .NO

What safeguards are fitted?

What safeguards are required to be incorporated into the ship fitting arrangements?

Is the provision of ear protectors to BS 5108 necessary for the protection of personnel? YES NO

Are appropriate Warning Notices fitted? (see also paragraph. 1.4 and 1.5 above) YES NO

7 IONISING RADIATION HAZARDS

Does the design of the System / Equipment incorporate the use of Radioactive materials or other sources of Ionising Radiation? YES NO

If YES:

Can Equipment performance equally be achieved by alternative means? YES NO

Is shielding provided to reduce instantaneous dose rate in both the operational and maintenance modes? YES NO




Does the level of shielding provided achieve a dose rate below 7.5 micro-sieverts/hour? YES NO

Is a test certificate provided for the level of shielding achieved? YES NO

Are source items incapable of being activated unless the shielding is in place? YES NO

What other safeguards are fitted?


Are appropriate Warning Notices fitted, or specified as a requirement for the ship fitting arrangements? (see also paragraph. 1.4 and 1.5 above)

YES NO

Does the design of the System / Equipment include the use of luminous items? YES NO

If YES:

Is the use of radioactive luminizing compound restricted to Promethium 147 or tritium only? YES NO

Does the design include the use of Gaseous Tritium Light Sources (GTLS)? YES NO

If NO what material is used?

Is adequate information available on all potential radiological hazards associated with the item? YES NO

If YES:

Are clear instructions provided for the disposal or return of items containing radioactive material? YES NO

Are all fitted sources of ionising radiation and their packaging/enclosures clearly identified and labelled appropriately? (see also paragraph. 1.5 above)

YES NO

Are clear instructions provided for actions required in the event of radiation leakage? YES NO

8 CHEMICAL AND ENVIRONMENTAL HAZARDS

Does the design of the System / Equipment incorporate the use of materials (e.g. toxic, corrosive, harmful or irritant) which may give rise to a Chemical Hazard to personnel in either normal operations or after accidental damage. E.g. Fire?

YES NO

If YES:

What form does the Hazard take? Toxic vapour, dust particles, etc.?






Is attention drawn to all such hazards in the relevant documentation? (see also paragraph. 1.6 above) YES NO

Can the Equipment be operated/maintained without the necessity of using masks, protective clothing, or other necessary protective Equipment?

YES NO

Can the Equipment be maintained without the necessity for a fume extraction system required in workshop spaces, etc.? YES NO

Has the use of corrosion resistant materials which may present a Hazard in a salt-water environment been avoided? YES NO

Are appropriate Warning Notices fitted, or specified as a requirement for the ship fitting arrangements? (see also paragraph. 1.4 and 1.5 above)

YES NO

Is the Equipment approved against any standard for discharge to the environment? (MARPOL, U.S.C.G. etc.) YES NO

If YES, give details.

If NO, give details of the type, composition, and quantity of discharge.

What precautions are necessary to prevent the release of any environmentally hazardous material:

During maintenance?

At disposal?

Does the Equipment contain specifically, any of the following materials:- Asbestos?

YES NO Cadmium?

YES NO Beryllium?

YES NO

Viton? YES NO

Materials which may emit toxic fumes when heated? YES NO

If YES, give details, and explain in detail what action is being taken to remove from the Equipment.

9 LASER HAZARDS

Does the design of the System / Equipment incorporate the use of lasers? YES NO

If YES:

Has a laser hazard evaluation been conducted? YES NO

What class is the laser hazard?




How is the presence of a laser hazard identified?



Is the provision of Laser Protective Goggles necessary for the protection of personnel? YES NO

Are appropriate Warning Notices fitted, or specified as a requirement for the ship fitting arrangements to the Wholeship Design Authority?

YES NO

Are there any safeguards that should be implemented during operation of the Equipment? YES NO

10 FIRE HAZARDS

Does the design of the System / Equipment incorporate fire resistant material and finishes in order to minimise the fire hazard? YES NO

If YES:

Has an assessment been made of the Equipment ability, in the shipboard environment, to remain safe in the event of fire breaking out?

YES NO

What fire hazardous materials, if any, are present in the Equipment design?

What is the heat dissipated by the Equipment?

Are thermal detectors fitted? YES NO

If YES: specify type.

What cooling devices are required to reduce the risk of fire?

List the standards employed for the fire resistant materials and finishes.

10.1 FIRE FIGHTING FACILITIES

What ‘special-to-type’ Fire Fighting facilities are fitted? (e.g. CO2 injection sockets, ‘total flooding’ arrangements ?)

What ‘special-to-type’ Fire Fighting facilities are required to be incorporated into the ship fitting arrangements?

11 SAFETY RELATED SOFTWARE

DOES THE SYSTEM / EQUIPMENT DESIGN INCLUDE SAFETY RELATED SOFTWARE (SCS)? (DEF STAN 00-55 REFERS) YES NO

If YES:




Is a detailed Hazard Analysis Report available identifying the critical features and integrity of the System software? YES NO

Is a detailed Safety Integrity Analysis Report available which determines the integrity of the software solutions proposed for the Hazards identified?

YES NO

Has a Software Formal Mathematical Specification for SCS elements been prepared from the Software Requirements Specification? YES NO

Is a Software Safety Plan available detailing all identified safety Related aspects and failure modes and the necessary checks, proofs and tests required for acceptance?

YES NO

Has a Software Safety Record log been raised for SCS in support of the Software Safety Plan? YES NO

Will a Software Safety Certificate be raised for the design prior to acceptance? YES NO

If NO, give reason(s).

12 FINALLY...

Are there any additional safety hazards associated with this Equipment that have not been highlighted by this Equipment Safety Questionnaire.

YES NO

Have these matters been brought to the Purchaser’s attention? YES NO

If NO, what are they ?

COSHH and Hazardous Material Report, Rev 2 Document #: VSY-A02.01-0024 Agreement #: [* insert Agreement #]




COSHH and Hazardous Materials Report

DID E102






Purpose

Provision of a COSHH Register recording the hazardous materials identified by the Supplier in the Hazard Log (DID No. E103). This Register together with the Materials Safety Data Sheets (MSDSs) provided will be used by the Purchaser as inputs to the Ship COSHH Register prepared by the Purchaser.

The aim is to complete the first draft of the COSHH register at the design stage so that any hazardous materials deemed unacceptable can be changed before the build stage.

It should be noted that before inclusion in the Ship COSHH Register, the Purchaser will check that the hazardous materials have been endorsed by the Safety Group.

Scope

The COSHH Register shall record the hazardous materials identified by the Supplier relating to the Equipment. The hazard could be to personnel, or the environment.


Content and Format

The MSDSs shall be supplied in hard and soft copies. The hard copies shall take the form of an A4 size document, bound in ring binders. The soft copies take the form of a separate copy for each material, preferably in Acrobat format.

Detailed Content

The COSHH Register shall comprise a Cover Sheet or Title Box, and a number of columns as illustrated in Attachment A.

The Cover Sheet or Title Box shall detail the Item/Equipment, Supplier, Supplier Signatory, and Date.

The Content of each column shall be prepared in accordance with the following:

(a) Record Number.

The record number of the material in the Register. The numbers shall be in ascending order.

(b) Material Description

The description of the material or its generic type.

(c) Material Trade Name

The Trade Name of the Material

(d) Manufacturer of the material

The name of the manufacturing company of the material.




(e) Electronic filename of Manufacturers Materials Safety Data Sheet (MSDS)

The electronic file name of the Manufacturers Materials Safety Data Sheet (MSDS)

(f) Physical Location by Compartment Number and Name.

This will be completed by the Supplier.

(g) Quantity.

The approximate numerical quantity of the material in the units given in the next column

(h) Unit of measure.

The units for the quantity above. The units shall be metric/SI units.

(i) Item or Equipment containing the hazardous material.

A concise description of the system item or equipment that contains the hazardous material.

(j) Hazard Log Number and Process Activity that uses the material with the quantity involved.

The Hazard Log Number is to be quoted (further to DID E103), followed by details of the process activity using the hazardous material with a statement on the approximate quantity involved (quoted in the same units as above). Where the material is part of the build itself, as opposed to a separate process activity, then n/a should be entered with reference to the activity.

Structure

The layout of the table is identified at Attachment A. The COSHH Register shall be compiled and maintained in accordance with the content procedures listed below.


(a) Should any additional hazardous materials be identified during the design, build or installation stages then the Register is to be updated and reissued, and the additional MSDSs supplied.

(b) Should the item or product not contain any hazardous materials then the Register is to be supplied stating Nil return’ on it.




Attachment A to DID E102

Record No.

Material Description

Material Trade Name Manufacturer of the material

Electronic filename of Manufacturer’s Materials

Safety Data Sheet (MSDS)

Physical location by Compartment

Number and Name

Quantity Unit of Measure

Item or Equipment

containing the Hazardous Material.

Hazard Log Number and Process Activity that uses the Material with the Quantity involved

Supplier Hazard Log, Rev 2 Document #: VSY-A02.01-0025 Agreement #: [* insert Agreement #]




Supplier Hazard Log

E103






Purpose

The purpose of the Supplier Hazard Log (SHL) is to provide a continually updated record of the hazards, accident sequences and accidents associated with a system. It includes information documenting risk management for each Hazard and Accident and is a continuously evolving record that stays with the system throughout its life cycle and includes:

a. A description of each identified hazard

b. A definition of fault sequences,

c. Engineering-based safety functions (safety requirements) and management controls to either eliminate the hazard or reduce the risk

d. An estimate of the unmitigated and mitigated risk and

Scope

The Supplier Hazard Log shall contain a comprehensive record of In Service hazards associated with the equipment. This record shall include hazards experienced during Test and Commissioning, Operation and Disposal.


Content and Format

The electronic format of the SHL shall be capable of being integrated into the Purchaser’s Hazard Log and the format shall be agreed with the Purchaser prior to first submission.

The document may be prepared in accordance with the Contractor's own document conventions and formats but must contain the following information:

Title Pages

Authorisation to include approval by Subcontractor’s authorised design signatory.

Supplier Hazard Log

Annex A specifies the minimum information requirements.

The process and methodology for carrying out the Safety Assessment is specified in the Safety and Environmental Management Plan. This forms the basis of the hazard information requiring input to the SHL. Safety Integrity Levels (SILs) where applicable are to be annotated in the Safety Function column within the SHL. Safety assessment criteria and SIL process and methodology are contained in Safety and Environmental Assessment Report.




Annex A to DID E095

Hazard Number

Hazard Description

Cause(s) Sequence of Events

Consequences Unmitigated Risk Env Safety Function

Saf

ety

Crit

ical

ity

Mitigated Risk Hazard Status

Freq Sev Risk Class

Freq Sev Risk Class

Acceptance Test Plan, Rev 2 Document #: VSY-A02.01-0008 Agreement #: [* insert Agreement #]




Acceptance Test Plan

DID E202



Acceptance Test Plan, Rev 2 Document #: VSY-A02.01-0008 Agreement #: [* insert Agreement #]



Purpose

The Acceptance Test Plan outlines the process by which the Supplier will plan and perform a programme of activities, tests and trials to achieve acceptance by demonstrating the required parameters, functions and attributes described in the Supplier’s Specifications and other contracted requirements.

Scope

The Supplier’s Acceptance Test Plan shall cover all test and acceptance activities. It shall address the testing categories (CAT 0 through 6) in the VCRIs contained in the B Schedules of the Subcontract.


nil

Content and Format

The Acceptance Test Plan shall:

• List tests (refer to CAT 1 through 6 definitions in the VCRI) that will be performed to verify compliance with the requirements set out in the VCRI for each piece of equipment or system being supplied. Indicate which requirements are verified by which test.

• List documents (refer to CAT 0 definition in the VCRI) that will be created to verify compliance with the requirements set out in the VCRI for each piece of equipment or system being supplied. Indicate which requirements are verified by which document.

• Provide a sequence that the tests will be performed in.

• Identify any specific Classification society or Flagstate Regulations required tests or hold points that will not otherwise be captured by the VCRI categories.

• Identify the locations of all tests.

Document Structure

To be determined by the Contractor.

FAT Schedule, Rev 2 Document #: VSY-A02.01-0026 Agreement #: [* insert Agreement #]




FAT Schedule

DID E205






PURPOSE

To describe the schedule of inspections required to demonstrate to the Purchaser that the Equipment complies with the Purchaser’s Technical Requirements. The FAT Schedule enables the Purchaser to assess and agree the content and planning of the FAT.


CONTENT AND FORMAT

The schedule shall consist of the following:

(a) Front material

(b) Scope.

(c) Referenced documents.

(d) Factory Acceptance Test Schedule.

(e) Test environment.

(f) Data recording, reduction and analysis.

(g) Notes.

FRONT MATERIAL

This shall include the signature page, List of Contents and any other material required by the Supplier's own procedures

SCOPE

This section shall include but not be limited to the following items:

(a) Identification.

The approved identification number, Title, and abbreviation, if applicable, of the system to which this FAT Schedule applies

(b) System overview.

The Purpose of the system to which this FAT Schedule applies.

(c) Document overview.

This paragraph shall summarise the Purpose and Contents of this document.

(d) Relationship to other plans.




The relationship, if any, of this Schedule to the Supplier Trials & Acceptance Plan and associated FAT.

REFERENCED DOCUMENTS.

A list by document number and Title of all documents referenced in this FAT Schedule.

FACTORY ACCEPTANCE TEST SCHEDULE.

This section shall be divided into paragraphs and subparagraphs as appropriate to describe the factory acceptance test of the deliverable production Equipment, detailing each separately identified test and which function or performance parameter it demonstrates. The information provided for each test shall include but not be limited to:

(a) Unique test identifier

(b) Test Description.

The Purpose and scope of the test.

(c) Requirement.

The identifier and text of the requirement(s) being tested.

(d) Test Method.

How the test will be conducted, detailing the steps to be followed and the results expected at each step. Where measurement or analysis is to be performed, the method of establishing the results shall be documented.

(e) Acceptance Criteria.

TEST PERSONNEL.

This section shall identify the personnel necessary to plan, prepare, conduct and analyse the factory acceptance tests.

TEST ENVIRONMENT.

This section shall identify and describe the plans for implementing and controlling the resources necessary to perform factory acceptance testing, including the following:

(a) Special to Type Test Equipment

A description of each item of STTE required for the factory acceptance testing, identifying the process by which it shall be provided, validated and maintained.

(b) Software

This shall identify the software Equipment necessary to perform the factory acceptance testing activities. This paragraph shall describe the Purpose of each Equipment and shall identify any classified processing or security issues associated with the software Equipment.

(c) Hardware and firmware Equipment

This shall identify the computer hardware, interfacing equipment, and firmware Equipments that will be used in the test environment. This paragraph shall describe the Purpose of each Equipment and shall identify any classified processing or security issues associated with the hardware or firmware Equipments.

(d) Installation, testing and control.

This paragraph shall identify the Suppliers plans for installing and testing each Equipment prior to its use. This paragraph shall also describe the supplier's plans for controlling and maintaining each element of the test environment.




DATA RECORDING, REDUCTION, AND ANALYSIS.

This section shall describe the data reduction and analysis procedures to be used during and following the tests identified in this FAT Schedule. This section shall document how information resulting from data reduction and analysis will be retained. The results of data recording, reduction, and analysis activities shall be documented in such a way that the resulting information will clearly show whether the test objectives have been met.

NOTES.

This section shall contain any general information that aids in understanding this document. This section shall include an alphabetical listing of all acronyms, abbreviations and their meanings as used in this document.

STRUCTURE

Each test description shall clearly define which mode/parameter/function of the Equipment is being demonstrated.


Nil

Factory Acceptance Test Report, Rev 2 Document #: VSY-A02.01-0003 Agreement #: [* insert Agreement #]




Factory Acceptance Test Report

DID E206






PURPOSE

The Factory Acceptance Test Report (FATR) records the tests or inspections required to demonstrate to the Purchaser that each deliverable production item of the Equipment is built to an identical build standard as that used for Proof of Compliance and that sufficient tests, demonstrations and analyses are performed on each item of production Equipment to safeguard the continued achievement of performance specified in the Purchaser’s Technical Requirements.

SCOPE

The FATR is used for Proof of Compliance and that sufficient tests, demonstrations and analyses are performed on each item of production equipment to safeguard the continued achievement of performance specified in the Purchaser’s Technical Requirements.

REFERENCES



CONTENT

The FATR shall include, but not be limited to, the following information for each test carried out during the FAT:

(a) Identifier of the test, including test name.

(b) Date of Test.

(c) Location of Test.

(d) Test Technician.

(e) Serial Number/unique identifier of the Equipment tested.

(f) Test equipment and calibration certificates.

(g) Summary of test results, including success/failure and problems identified.

(h) Approval signature sheet including Class witnessing.

(i) Chronological record of events relevant to test preparation, performance & analysis.

(j) Detailed test results including pass/fail assessment as agreed between Subcontractor and the Class Society Surveyor or Purchaser (if no Class approval required) at the Trial.

(k) Deviations from the test procedure.

(l) Evaluation of impact on the Equipment of deficiencies identified.

TITLE PAGE

The title page shall contain the information identified below in the indicated format:

(Document control number and date: Volume x of y (if multi-volume))




(Rev. indicator: date of Rev. )

FACTORY ACCEPTANCE TEST REPORT

FOR THE

[* insert name of Equipment]]

Agreement number: ...........

SDRL NO. ...........

Prepared for: [* insert name of the Purchaser]

Prepared by: [* insert name of Supplier, address and telephone number]

STRUCTURE

As above


Nil

Test Readiness Review Structure, Rev 2 Document #: VSY-A02.01-0007 Agreement #: [* insert Agreement #]




Test Readiness Review Structure

DID E209



Test Readiness Review Structure, Rev 2 Document #: VSY-A02.01-0007 Agreement #: [* insert Agreement #]



Purpose

The Test Readiness Review (TRR) Structure outlines the requirements expected for performance of Test Readiness Review meetings in advance of a test.

Scope

The TRR shall apply to FATs and any subsequent formal tests/trials conducted by the Supplier.


nil

Content and Format

The TRR shall incorporate the following:

The TRR assesses test objectives, test methods and procedures, scope of tests, and safety and confirms that required test resources have been properly identified and coordinated to support planned tests. The TRR verifies the traceability of planned tests to program requirements and user needs. The TRR also assesses the system under review for development maturity, cost/ schedule effectiveness, and risk to determine readiness to proceed to formal testing.

The TRR shall encompass the following:

• Review the list of equipment being tested.

• Review and address any open comments/actions against the Acceptance Test Plan and Test Procedures/Agendas for the equipment to be tested.

• Verify that the manufacturing of the equipment or system has been completed, and if not come to agreement as to whether or not the testing can still proceed.

• Present an evaluation demonstrating that all planned preliminary, informal, functional, unit level, subsystem, system, and qualification tests have been conducted successfully.

• Present an evaluation demonstrating that the equipment or system is expected to pass the test.

• Illustrate that the planned test is properly resourced (people, test article or articles, facilities, data systems, support equipment, logistics, etc).

• Present the fall-back plan should a technical issue or potential showstopper arise during testing.

Document Structure

No document submission

EMC Qualification Test Schedule, Rev 2 Document #: VSY-A02.01-0027 Agreement #: [* insert Agreement #]




EMC Qualification Test Schedule

DID E301






PURPOSE

The Electromagnetic Compatibility Qualification Test Schedule (EMCQTS) specifies the EMC testing to be performed on the Subcontractor’s Equipment. The EMC Qualification Test Schedule provides the Purchaser with a description and a permanent record of the testing to be performed on a Subsystem. The EMC Qualification Test Schedule may be used by the Subcontractor as a basis for re-testing of a subsystem.

SCOPE

The EMCQTS is used to describe one or more EMC tests defined in the Acceptance Test Plan. The EMCQTS provides the source data for the EMC Qualification Test Report that is produced when testing has been completed. The EMCQTS defines the method of performing each test, the testing plan (i.e. sequence of tests) and the equipment required to perform each test. Any Equipment which is being put up for acceptance on the evidence of previous testing or by analogy to previous testing of similar equipment should be clearly identified at this stage. Evidence of previous testing shall be included in the EMC Qualification Test Report. The tests included shall cover all the EMC requirements from the appropriate Schedule B documents.

REFERENCES



CONTENT

Media

The document shall be supplied soft copy.

Detailed Content

This document shall consist of the following:

(a) Front Matter

(b) Scope

(c) Referenced documents

(d) Test Descriptions

(e) Test Plan

(f) Test Personnel

(g) Test Facility Requirements

(h) Notes

(i) Appendices




CONTENTS

Front Matter

This section shall include a Title page, List of contents and any other material required by the sub-contractors documentation procedures.

SCOPE.


(a) Identification.

The approved identification number, Title, and abbreviation, if applicable, of the system to which this EMCQT Schedule applies


The Purpose of the system to which this EMCQT Schedule applies.


This paragraph shall summarise the Purpose and contents of this document.


The relationship, if any, of this Schedule to the Subcontractor Trials & Acceptance Plan and associated EMCQT.

Reference Documents.

This section shall list by document number and Title all documents referenced in this Schedule.

Test Schedule

This section shall be divided into paragraphs and subparagraphs as appropriate to describe the EMC qualification test of the deliverable item, detailing each separately identified test. The information provided for each test shall include but not be limited to:


(b) Test Description


(c) Requirement


(d) Test Method

How the test will be conducted, detailing the steps to be followed and the results expected at each step. Where measurement or analysis is to be performed, the method of establishing the results shall be documented.

(e) Acceptance Criteria

Test Plan.

This section shall contain the proposed plan for EMC Qualification Testing. The tests described in the EMCQTS shall be listed in the order in which they are to be performed, with details of proposed grouping of




tests and details of the Test Houses to be used included. Intended start dates and duration for each group of tests are to be provided.

Test Personnel

This section shall identify the personnel necessary to plan, prepare, conduct and analyse the EMC tests.

Test Facility Requirements

This section shall detail the exact test equipment requirements for each test or group of tests. This section should contain sufficient information for the purchaser to be able contract a test house to perform independent testing if required. This section shall contain a description of all the Test and Recording equipment required to perform the tests or groups of tests to the required standard.

Notes.

This section shall contain any general information that aids in understanding this document (e.g., background information, glossary). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document.

Appendices.

Appendices may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be Referenced in the main body of the document where the data would normally have been provided.

STRUCTURE

Nil.


Nil

EMC Qualification Test Report, Rev 2 Document #: VSY-A02.01-0004 Agreement #: [* insert Agreement #]




EMC Qualification Test Report

DID E302






PURPOSE

The Electromagnetic Compatibility Qualification Test Report (EMCQTR) is a description and report of the EMC testing performed on the Subcontractor’s Equipment.

SCOPE

The EMC Qualification Test Reports are used to describe and record the results of one or more EMC tests defined in the Test & Acceptance Plan. The EMC Qualification Test Reports summarise test discrepancies and references the corresponding problem/change reports.

REFERENCES



CONTENT

Media

The document shall be supplied both in hard and soft copies. The hard copies shall take the form of an A4 size document, bound in ring binders.

Detailed Content


(a) Front Matter

(b) Scope


(d) Test Report

(e) Details of the tests conducted and standards achieved

FRONT MATTER

This section shall include a title page, list of contents, change and issue status and any other material required by the Subcontractor’s documentation procedures.

SCOPE


(a) Identification.

The approved identification number, Title, and abbreviation, if applicable, of the system to which his EMCQT Report applies


The Purpose of the system to which this EMCQT Report applies.







The relationship, if any, of this Report to the Subcontractor Trials & Acceptance Plan and associated EMCQT Schedule or Report.

Applicable Documents.

A list by document number and Title of all documents referenced in this EMCQT Schedule.

Test Report

This section shall be divided into paragraphs and subparagraphs as appropriate to describe the environmental qualification test of the deliverable item, detailing each separately identified test. The order of tests within this document shall correspond to the order of tests within the EMCQTS. The information provided shall include but not be limited to the following for each test carried out during the EMCQT:


(b) Summary of test results, including success/failure and problems identified.

(c) Chronological record of events relevant to test preparation, performance & analysis.

(d) Detailed test results.

(e) Deviations from the test procedure.

(f) Evaluation of impact on the Equipment of deficiencies identified.

(g) Proposed programme to rectify design shortcomings identified.

Notes.


Appendices.

Appendices may be used to provide information published separately for convenience in document maintenance (e.g. charts, classified data). Where available this section shall include any Graphs, response curves etc. supplied by the Test House during the course of testing. As applicable, each appendix shall be Referenced in the main body of the document where the data would normally have been provided.

STRUCTURE

Nil.


Nil

Environmental Qualification Test Schedule, Rev 2 Document #: VSY-A02.01-0004 Agreement #: [* insert Agreement #]




Environmental Qualification Test Schedule

DID E401






PURPOSE

The Environmental Qualification Test Schedule (EQTS) is a description and specification of the environmental testing to be performed on the Subcontractor’s Equipment. The EQTS provides the Purchaser with a description of the testing to be performed on an Equipment.

SCOPE

The EQTS is used to describe one or more environmental tests defined in the Subcontractor’s Acceptance Test Plan (SATP). The EQTS defines the method of performing each test, the testing plan (i.e. sequence of tests) and the equipment required to perform each test. Any Equipment which is being put up for acceptance on the evidence of previous testing or by analogy to previous testing of similar equipment should be clearly identified at this stage. Evidence of previous testing shall be included in the Environmental Qualification Test Report. The tests included shall cover all the environmental requirements from the Schedule B documents.

REFERENCES



CONTENT

Media

The document shall be supplied soft copy.

Detailed Content


(a) Front Matter

(b) Scope


(d) Test Descriptions

(e) Test Plan

(f) Test Personnel

(g) Test Facility Requirements

(h) Notes

(i) Appendices

CONTENTS

Front Matter

This section shall include a Title page, List of contents and any other material required by the Sub-contractors documentation procedures.




Scope


(a) Identification.

The approved identification number, Title, and abbreviation, if applicable, of the system to which this EQT Schedule applies


The Purpose of the system to which this EQT Schedule applies.




The relationship, if any, of this Schedule to the Subcontractor Trials & Acceptance Plan and associated EQT.


A list by document number and Title of all documents referenced in this EQT Schedule.

Test Schedule

This section shall be divided into paragraphs and subparagraphs as appropriate to describe the environmental qualification test of the deliverable item, detailing each separately identified test. The information provided for each test shall include but not be limited to:


(b) Test Description.


(c) Requirement.


(d) Test Method.

How the test will be conducted, detailing the steps to be followed and the results expected at each step. Where measurement or analysis is to be performed, the method of establishing the results shall be documented

(e) Acceptance Criteria

Test Plan.

This section shall contain the proposed plan for Environmental Qualification Testing. The tests described in the EQTS shall be listed in the order in which they are to be performed, with details of proposed grouping of tests and details of the test houses to be used included. Intended start dates and duration for each group of tests are to be provided.




Test Personnel

This section shall identify the personnel necessary to plan, prepare, conduct and analyse the environmental testing.

Test Facility Requirements

This section shall detail the exact test equipment requirements for each test or group of tests. This section should contain sufficient information for the purchaser to be able contract a test house to perform independent testing if required.

Notes.


Appendices.

Appendices may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided.

DOCUMENT MAINTENANCE

The Sub-contractor shall provide a draft Schedule for agreement with the purchaser. Once agreed, the Schedule shall be put under Configuration Management and all future testing shall be performed against this document. All further changes to this document shall be approved by the Purchaser.

STRUCTURE

Nil.


Nil

Environmental Qualification Test Report, Rev 2 Document #: VSY-A02.01-0005 Agreement #: [* insert Agreement #]




Environmental Qualification Test Report

DID E402






PURPOSE

The Environmental Qualification Test Report (EQTR) is a description and report of the specified environmental testing performed on the Subcontractor’s Equipment. The EQTR provides the Purchaser with a description and a permanent report of the testing performed on the Equipment. SCOPE The EQTR is used to describe and record the results of one or more environmental tests defined in the Acceptance Test Plan and described in the Environmental Qualification Test Schedule (EQTS). The EQTR documents test results and discrepancies and references the corresponding problem/change reports.

REFERENCES



CONTENT

Media

The document shall be supplied both in hard and soft copies. The hard copies shall take the form of an A4 size document, bound in ring binders.

Detailed Content


(a) Front Matter

(b) Scope


(d) Test Report

(e) Notes

(f) Appendices

Front Matter

This section shall include a Title page, List of contents and any other material required by the Sub-contractor documentation procedures.

Scope.


(a) Identification.

The approved identification number, Title, and abbreviation, if applicable, of the system to which this EQT Report applies





The Purpose of the system to which this EQT Report applies.




The relationship, if any, of this Report to the Subcontractor Trials & Acceptance Plan and associated EQT Schedule or Report.


A list by document number and Title of all documents referenced in this EQT Schedule.

Test Report

This section shall be divided into paragraphs and subparagraphs as appropriate to describe the environmental qualification test of the deliverable item, detailing each separately identified test. The order of tests within this document shall correspond to the order of tests within the EQTS. The information provided shall include but not be limited to the following for each test carried out during the EQT:


(b) Summary of test results, including success/failure and problems identified.

(c) Chronological record of events relevant to test preparation, performance & analysis.

(d) Detailed test results.

(e) Deviations from the test procedure.

(f) Evaluation of impact on the Equipment of deficiencies identified.

(g) Proposed programme to rectify design shortcomings identified.

Notes.

This section shall contain any general information that aids in understanding this document (e.g. background information, glossary). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document.

Appendices.

Appendices may be used to provide information published separately for convenience in document maintenance (e.g. charts, classified data). Where available this section shall include any Vibration response curves, shock waveforms, temperature and humidity records etc. supplied by the Test House during the course of testing, as applicable, each appendix shall be Referenced in the main body of the document where the data would normally have been provided.

STRUCTURE

Nil.


Nil

Software Version Description Document, Rev 2 Document #: VSY-A02.01-0029 Agreement #: [* insert Agreement #]




Software Version Description Document

DID E501






PURPOSE

The Software Version Description Document (SVDD) identifies and describes a version of a Software system. This document is used by the Subcontractor to release Software versions to the Purchaser. The SVDD is used by the Purchaser to track and control Software to be released into the Shore integration facilities and the operational environment.

Firmware and software must be defined at the hardware BIOS, operating system, and application levels. The intent is to describe the run-time environment for the purposes of monitoring security vulnerabilities and assessing risk during the JSS In Service Support. Firmware and software must be listed for any JSS system using commercial or open-source operating systems (for example, Windows, Linux, QNX, etc.) and/or applications (for example, Apache, Microsoft SQL, etc.). Embedded programmable logic controllers with unique hardware and firmware do not have to be included (for example, embedded main engine controllers unless they run commercial operating systems or applications).

SCOPE

This DID applies to all software and computer hardware items associated with the Equipment. This DID must be read in conjunction with the SOW.


In accordance with Attachment A. Sample data is for illustration purposes and should be removed for submission.

Submit in Excel format. List each software item in its own row in Excel.

STRUCTURE

For each commercial or open source operating system or application software the following must be supplied:

1. Supplier;

2. Equipment ID (VSY Designated number)

3. Associated Configuration Item;

4. Short description of the software’s purpose in the delivered system;

5. Software name;

6. Software version number and hotfix;

7. Software manufacturer;

8. Identify application, operating system or a run-time environment (such as JAVA);




9. Anticipated Support End date (Provide date when software is no longer supported by the manufacturer);

10. Associated computer hardware (if different from Configuration Item);

11. Associated firmware for hardware, if applicable;

12. Support philosophy: software support specific to JSS or OEM; and

13. Remarks.


Nil




Attachment A

Supplier Equ ID Associated Config Item

Software purpose

Software name

Software Version number and hotfix

Software manufacturer

Application, operating system or run-time environment

Anticipated Support End Date (mmm-yyyy)

Associated computer hardware (if different from Config Item)

Associated firmware for hardware (if applicable)

Support philosophy Remark

Sample Maintenance laptop

Windows 7 Enterprise

Service Pack 1 HotFixIDs: KB2849697 KB2849697 KB2849696 KB2849696 KB2841134 KB2841134 … Microsoft

Operating System Jan-2020

HP Elitebook 840 D1F44AV

HP Sure Start BIOS

OEM supported

Sample

Visual Basic office environment to build maintenance reports.

Office Standard 2010

10.0.7166.5000 HotFixIDs: KB3146963 KB3147071 KB3148198 KB3148851 KB3149090 KB976902 KB982018 … Microsoft Application Oct-2020

HP Elitebook 840 D1F44AV

HP Sure Start BIOS

OEM supported

Interface Data Sheet, Rev 2 Document #: VSY-A02.01-0030 Agreement #: [* insert Agreement #]




Interface Data Sheet

DID E701



Interface Data Sheet, Rev 2 Document #: VSY-A02.01-0030 Agreement #: [* insert Agreement #]



PURPOSE

Provision of an Interface Data Sheet.

SCOPE

This Data Item Description (DID) contains the Format and Preparation Instructions for the Interface Data Sheet.


CONTENT

• The interface Data Sheet shall include all interfaces to the Supplier’s equipment excluding those for physically securing the Equipment to the ship and IPMS interfaces.

• The Interface Data Sheet shall include the following information :

VSY Part Number

Unique ID

Interface Name

Connection Type (Mech / Elec)

Connection Spec. (incl. rating) Material Comments

FORMAT

The document shall be supplied in Excel format.

DOCUMENT STRUCTURE

Nil.

IPMS Signal List, Rev 2 Document #: VSY-A02.01-0033 Agreement #: [* insert Agreement #]




IPMS Signal List

DID E702






PURPOSE

Provision of an IPMS Signal List.

SCOPE

This Data Item Description (DID) contains the Format and Preparation Instructions for the IPMS Signal List.


CONTENT

• The IPMS Signal List shall include but not be limited to the following information of which the Supplier shall populate those fields that are within their scope of knowledge (note guidance will be given regarding suitable entry formats):

Data Field

LAST UPDATE

SIGNAL ID

SWBS #

SYSTEM/EQUIPMENT

PID DRAWING #

CABLE DIAGRAM #

SOURCE/DEST DEVICE

SOURCE/DEST TERMINATION

COMP'T #

COMPARTMENT NAME

SIGNAL DESCRIPTION (LONG TEXT) (60 CHAR MAX)

SLAVE UNIT LOCATION

SLAVE UNIT NR.

I/O TYPE

SIGNAL TYPE

DATA TYPE

PROTOCOL

BITRATE

BAUD RATE

FUNCTION

CAN BE GROUPED TO INS ?

PRIORITY

INS CATEGORY

SEND TO VDR ?

BIT NUMBER




SENSOR P/N

SENSOR RANGE

SENSOR EXCITATION

SENSOR CONTACT CONFIGURATION (N.O./N.C.)

SYSTEM RANGE

UNIT

LOW ALERT

LOW-LOW ALARM

HIGH ALERT

HIGH-HIGH ALARM

CLASS UMS REQUIREMENT

CLASS REQUIREMENT

SCHEDULE B REQUIREMENT (HBA #)

COMMENTS

• Entries within the IPMS Signal List shall be consistent where applicable.

FORMAT

The document shall be supplied in Excel format.

DOCUMENT STRUCTURE

Nil.

Cable Schedule, Rev 0 Document #: 193-A02.01-0033 Agreement #: [* insert Agreement #]




Cable Schedule

DID E703-1

Prepared by: Vancouver Sh ipyards Co. L td .



Cable Schedule, Rev 0 Document #: 193-A02.01-0033 Agreement #: [* insert Agreement #]



PURPOSE

The purpose for this document is to provide a structured format for delivery of technical information regarding to the ship’s electrical cable schedule and ship cable terminations that are included as part of the Integrator's/Supplier’s scope of supply. The cable schedule is a detailed itemized list of information that documents individual cable connections. The cable terminal schedule is a detailed itemized list describing each cable termination.

SCOPE

This document applies to any Integrator or Supplier that will deliver cable schedules and cable terminations to the Purchaser and is required to be filled out for each cable.

FORMAT AND CONTENT

The document shall be submitted to the Purchaser in Excel format in the template provided below. An electronic copy has been provided with the contract pack. For each supplemental delivery of this data, all changes for that revision are required to be clearly identified. The cable core identification shall be in the agreed format with the Purchaser. Cable manufacturing data shall be supplied to Purchaser for any cables that are not in accordance with the Purchaser’s standard cable catalogue STRUCTURE

The cable schedule format shall be in accordance with the file “Cable Schedule.xlsx”.

The cable termination schedule format shall be in accordance with the file “Cable Terminations.xlsx”.

Cable Termination.xlsx

Cable Schedule.xlsx

Interface Control Document, Rev 1 Document #: VSY-A08.22-0185 Agreement #: [* insert Agreement #]




Interface Control Document

DID E709

Prepared by: Vancouver Sh ipyards Co. L td . 2 Pe mber ton Ave . Nor th Van couver , BC, Canada, V7 P 2R2 Te l : (604) 988-3111 Fax: (604) 984-1636





PURPOSE

An Interface Control Document (ICD) defines the hardware and software protocols, and data flow requirements for serial communication interfaces between different pieces of equipment. This document is required to enable the Purchaser to coordinate integration of equipment provided by multiple Integrators/Suppliers to ensure compatibility between systems.

SCOPE

ICDs are required for all equipment or systems that connect to the Ship Control and Monitoring System (SCMS), Voyage Data Recorder (VDR), or that require direct data connection to another supplier’s piece of equipment. This document must be read in conjunction with Part 3 (Engineering) Schedule D1 for specific instructions.

FORMAT

The ICD developed by the Integrator/Supplier should be in Microsoft Word format using the Purchaser’s standard document template for the project.

CONTENT

The ICD shall be presented in report format which specifically address the following items:

1. Introduction 2. System Descriptions 3. Reference Documents 4. Applicable Regulations and Requirements 5. Interface Specification

5.1. States for Alert Conditions 5.2. Alert Priority 5.3. Physical Interface 5.4. Port Configurations 5.5. Data Tables




STRUCTURE

Below is an example of the physical interface specified in section 5.3.

The port configuration in section 5.4 should have the following information:

(1) data bits 8 (D7 =0), parity none (2) stop bits 1 (3) Baud rate is 115000 bps (4) RS 422 serial interfaces

The data tables in section 5.5 should have the following information:

IO List Table

SIGNAL ID

SYSTEM DESCRIPTION

EQUIPMENT DESCRIPTION

EQUIPMENT TAG

SIGNAL SUFFIX

DATA TYPE

DATA ADDRESS

UNITS

COMMENTS

Design Products, Rev 1 Document #: VSY-A08.22-0186 Agreement #: [* insert Agreement #]




Design Products

E900



Design Products, Rev 1 Document #: VSY-A08.22-0186 Agreement #: [* insert Agreement #]



PURPOSE

Submission of Design Products as defined in the Engineering SOW and the Engineering SDRL by the Supplier to the Purchaser.

REFERENCES




FORMAT AND CONTENT


Certificates, Rev 2 Document #: VSY-A02.01-0035 Agreement #: [* insert Agreement #]




Certificates

E901



Certificates, Rev 2 Document #: VSY-A02.01-0035 Agreement #: [* insert Agreement #]



PURPOSE

Submission of Certificates, from various sources, by the Supplier to the Purchaser.

REFERENCES




FORMAT AND CONTENT

1. Supplier’s format.

Life Cycle Cost Report, Rev 0





Life Cycle Cost Report

ILS-043-010



.





DATA ITEM DESCRIPTION

1. TITLE

Life Cycle Costing Report

2. IDENTIFICATION NUMBER

ILS-043-010

3. DESCRIPTION / PURPOSE

The Life Cycle Costing (LCC) report must describe the approach and methodology used to estimate the required sustainment and disposal costs elements. The report must describe the analysis conducted and provide the results obtained. Additionally, the report must supply the cost breakdown, summary and the associated risk and uncertainty analysis.

4. REFERENCES

Attachments: Nil

References: This DID must be read in conjunction with the appropriate paragraphs of the Statement of Work, Subcontract Data Requirements List and any references cited in the DID.

5. FORMAT

The following formatting guidelines must be considered when preparing the deliverables.

a. Unless a specific template is provided by VSY, the deliverables may be prepared in Supplier’s format upon review and approval by VSY.

b. The format shall not impose any restriction on searching, editing, copying, or printing.

c. The information shall be provided in English and in French, if available.

6. CONTENT

a. The LCC Report shall be broken down into the following chapters.

i. Descriptions of approach and methodology used (e.g. utilization, Service Sub-Contract [ISSC] SOW).

ii. Description of data sources, uncertainties, assumptions and justifications.

iii. Sustainment Cost Analysis.

iv. Disposal Cost Analysis.

b. Summary of amortized LCC per fiscal year. The following must be considered when developing the LCC chapters:

i. Descriptions of approach and methodology used including the basis for calculation and relationship between the sustainment costs and applicable furnished information (e.g. utilization, ISSC SOW);

ii. All assumptions utilized in the calculations of the LCC cost elements estimates and uncertainties around the LCC cost estimates;

iii. A description of the breakdown categories of the sustainment cost estimates including, as a minimum, for both in ISSC and Organic Support:

• Management cost.





• Maintenance support cost.

• Supply support cost including spares, storage and transportation.

• Technical Data Package maintenance costs; and

• Engineering support cost.

iv. A description of the breakdown categories of the disposal cost estimates including, as a minimum, the following:

• Management and disposal certification costs;

• Removal and disposal costs of any Controlled Goods;

• Removal and disposal costs of hazardous material;

• Towing costs;

• Cutting and scrapping costs; and

• Credit for scrap metal value. Removal, disposal or recycling cost.

• Special considerations for safety and hazardous material / equipment.

v. A description and summary of the LCC data sources utilized, describing:

• Why each data source is relevant and applicable to the Ship; and,

• The known limitations inherent in the data.

vi. A description of the LCC cost estimates summary against a yearly expenditure as per fiscal year.

c. Each chapter of the LCC data report described above must contain the following with respect to the uncertainty analysis:

i. A description of the processes and methods utilized for execution of the uncertainty analysis against the developed LCC cost estimates;

ii. Justifications of the uncertainty ranges determined for each line item of the LCC cost estimate;

iii. Uncertainty is to be represented by an upper percentile and lower percentile range away from the Contractor-provided cost estimates.

d. The LCC Report shall include all information required for general understanding and shall define all special terms and acronyms used.

Disposal Plan, Rev 0 Document #: VSY-A08.22-0159 Agreement #: [* insert Agreement #]




Disposal Plan

ILS-043-020



.





1. TITLE

Disposal Plan (DP)


ILS-043-020


The Disposal Plan (DP) provides details of the supplier's analysis of, and proposed recommendations for, the disposal of the equipment or items of the equipment supplied under the subcontract. This is to ensure the purchaser is made aware of adequate disposal provisions as well as potential safety and environmental impacts prior to any disposal action.

4. REFERENCES

Attachments: Nil

References: This DID must be read in conjunction with the appropriate paragraphs of the Statement of Work, Contract Data Requirements List and any references cited in the DID

5. FORMAT


a. Unless a specific template is provided by VSY, the deliverables may be prepared in contractor’s format upon review and approval by VSY.



6. CONTENT

a. The DP shall define disposal methods and procedures required for the equipment or items of the equipment supplied under the subcontract.

b. The DP shall include recommendations for the agencies and/or personnel responsible for the disposal action.

c. The DP shall take into account any special disposal provisions (e.g. packaging and handling, hazardous materials), and describe recommended disposal activities for items that meet the following conditions:

i. Retired from the inventory as part of planned maintenance, modification or upgrade schedules.

ii. Non-repairable, removed and replaced as part of Corrective Maintenance or Preventive Maintenance.

iii. Retired and removed from the inventory at the end of their operational life.

iv. Removed from inventory when there is no longer any need for the system.

d. The DP shall provide details identified below:

v. Reference to Configuration Item (CI) List in the Technical Data Package (TDP).




vi. Item nomenclature.

vii. Expected item life.

viii. Schedule for the withdrawal of Items with finite lives or with planned retirement times.

ix. Method of reclamation, re-cycling or disposal.

x. Safety provisions for disposal (if applicable).

xi. Environmental provisions for disposal (if applicable).

xii. Financial analysis and accounting of resale potential and achieved values for disposal items.

e. The DP shall include all information required for general understanding and shall define all special terms and acronyms used.

Obsolescence Notice Report, Rev 0 Document #: VSY-A08.22-0177 Agreement #: [* insert Agreement #]




Obsolescence Notice Report

ILS-043-030



.





1. TITLE

Obsolescence Notices Report


ILS-043-030


The purpose of the Obsolescence report is to provide a report on the analysis performed of the risks of obsolescence during design, build and delivery, and the second period during the lifecycle of operation and sustainment. The analysis is to be developed against the designing, building, operating and sustaining of systems, equipment and material and for:

• Risks of obsolescence, • Opportunity of interchangeability or prevalence of items, • Risks of the loss or impending loss of manufacturers/suppliers parts and material required.

The Obsolescence Notice Report provides details of the supplier's analysis, and proposed recommendations for managing the expected obsolescence of the equipment. This ensures the purchaser is made aware of expected equipment obsolescence as well as recommendations for replacement and maintenance of the equipment in the future.

4. REFERENCES

Attachments: Nil


5. FORMAT





a. CONTENT

b. The Obsolescence Notice Report shall provide OEM obsolescence notices and recommendations, where applicable.

c. The Obsolescence Notice Report shall include all information required for general understanding and shall define all special terms and acronyms used.

d. The Obsolescence Notice Report must contain an analysis of the risks of obsolescence:

i. First, during VSY’s design, build and delivery; and,

ii. Second, during the lifecycle of operation and sustainment.

e. The Obsolescence Notice Report must explain the method utilized for analysis, including:

i. Description of the nature of information requested from suppliers, including data




available and data utilized;

ii. Description of the data validation performed, and the results;

iii. Description of the analysis performed;

iv. Description of the risks and opportunities identified; and

v. Description of the strategies already in-place, suggested, or newly implemented for enabling positive outcomes.

f. The report must explain the analysis and results for the first period.

g. The report must explain the analysis and results for the second period.

h. The Obsolescence Notice Report shall include the following:

i. Reference to Configuration Item (CI) List in the Technical Data Package (TDP),

ii. Equipment Nomenclature,

iii. Date of Obsolescence Notice Release,

iv. End of Sale Date,

v. End of Support Date,

vi. Description of impact on systems affected,

vii. Supplier’s recommendations.

Failure Modes and Effects Analysis Report, Rev 0





Failure Modes and Effects Analysis Report

ILS-076-010



.






1. TITLE

Failure Modes and Effects Analysis Report


ILS-076-010


The Failures Modes and Effects Analysis (FMEA) Report must describe the approach, methodology and analysis conducted to identify the following:

a. Criteria for maintenance planning, logistics support analysis, test planning, inspection and checkout requirements.

b. Information with respect to maintainability design features that require corrective action. c. Information with respect to failure modes requiring corrective maintenance. d. Information for the Reliability-Centered Maintenance (RCM) process.

4. REFERENCES

Attachments: Nil


5. FORMAT



b. The format shall not impose any restriction on searching, editing, copying, or printing. c. The information shall be provided in English and in French, if available.

6. CONTENT

a. The FMEA report must include a description of the integrated approach and methodology the Contractor used for the analysis. The failure analysis must be conducted at the systems level and be used to determine the level of additional analysis if required.

b. The FMEA must be reported by systems, subsystem and equipment for critical systems to demonstrate that a single failure in active equipment or loss of an associated sub-system will not cause loss of all propulsion and/or steering capability as required by appropriate Class Notation.

i. These systems include but are not limited to:

o Propulsion systems.

o Electrical power supply systems.

o Steering systems.

ii. Typical sub-systems include associated control and monitoring arrangements, data communications, power supplies (electrical, hydraulic or pneumatic), fuel, lubricating,





cooling, etc.

iii. Analyses in accordance with IEC 60812, Analysis techniques for system reliability – Procedure for failure mode and effects analysis (FMEA) or IMO MSC Resolution 36(63) Annex 4 – Procedures for Failure Mode and Effects Analysis, would be acceptable.

c. The FMEA Report need not be developed as one document. It may be divided into volumes and sections, provided that the head document links all sub-documents together as a cohesive whole.

d. As a minimum, the FMEA Report shall:

i. Identify the level of analysis.

ii. Summarize the FMEA results.

iii. Integrate results of separate equipment FMEA Analyses into higher level system FMEA reports.

iv. Document the data sources and techniques used in performing the analysis.

v. Include a system definition narrative, resultant analysis data and worksheets. The worksheets supplied as part of FMEA Report shall be organised in descending order aligned to the indenture levels of the equipment.

e. As a minimum, each FMEA Study shall include the following:

i. Reference to Configuration Item (CI) List in the Technical Data Package (TDP).

ii. End Item Description and Function.

iii. Failure Mode and Cause Description.

iv. Failure Effect on Item.

v. Failure Effect on Next Higher Assembly (if applicable).

vi. Failure Effect on System (if applicable).

vii. Failure Detection Method.

viii. Effect on Operation (i.e. 1 = catastrophic to 4 = minor).

ix. Effect on Safety (i.e. 1 = catastrophic to 4 = minor).

x. Severity Class (i.e. 1 = catastrophic to 4 = minor).

xi. Failure Mode MTBF.

xii. Assumptions and remarks.

f. The FMEA Report shall include all information required for general understanding and shall define all special terms and acronyms used. The report must contain, as a minimum, the following:

i. A description of failure modes taken into account;

ii. An assessment of equipment failure criticality on system/subsystem functionality and criteria used; and

iii. For critical failures, the approach taken to minimize the failure probability.

iv. For each piece of equipment analysed the report shall identify all required maintenance tasks. The tasks shall be broken down as follows:

• Type of maintenance task (preventive, predictive, corrective);





• Task frequency (e.g. recommended, estimated);

• Applicable condition monitoring feature;

• Results of RCMA, if applicable; and

• Description of maintenance actions required by Classification Society.

• The equipment tasks summary must include basic equipment identification data.

Availability, Reliability & Maintainability, Rev 0





Availability, Reliability & Maintainability

ILS-076-020



.






1. TITLE

Availability, Reliability & Maintainability


ILS-076-020


The purpose of this DID is to define the Availability, Reliability and Maintainability (ARM) performance of the equipment on board the vessel.

4. REFERENCES

Attachments: Nil

References: DID ILS-076-010; DID ILS-081-010; DID ILS-081-20; This DID must be read in conjunction with the appropriate paragraphs of the Statement of Work, Contract Data Requirements List and any references cited in the DID

5. FORMAT





6. CONTENT

a. Utilizing existing ARM Data and material where available, the Supplier shall supply existing material with a cross reference to the Data requirements below, relevant to the equipment.

b. The operational cycle for the equipment as defined in the SOW. For equipment not nominated in the SOW, the contractor shall state:

i. The anticipated operating profiles on which the maintenance policy, reliability figures and spares provisioning have been based.

ii. Annual predicted usage against the various operating modes.

c. Maximum and minimum equipment operating times (e.g. fully Operational, Standby, and Powered Down) shall be considered when developing ARM.

d. Where the supplier’s solution is ‘existing’ equipment (i.e. maturity of the solution is 100%), evidence and standard of existing models and analyses and / or testing shall be provided.

e. Where the supplier’s solution is ‘new’ or ‘modified’ Equipment (i.e. maturity of the solution is less than 100%), the present status of the equipment shall be identified (i.e. % New or % Modified) for hardware (based on parts count) and software (based on lines of code). New Software represents completely recoded lines; modified indicates changes of parameters, screen menus, etc.).

f. For ‘new’ design or ‘modified’ Equipment, these Data requirements shall be completed with predicted or target data for all new development Equipment.





g. The environmental conditions under which the above data is provided shall be defined. This will include temperature and humidity.

h. The basis for the estimate of reliability shall be defined (i.e. prediction based on a defined method, reliability testing programme results, or in service field data). The detailed basis for the data shall be provided in support of Subcontractor representations.

i. Where the Equipment has been modified evidence of any programme to demonstrate the reliability and maintainability shall be described.

j. Where there are known reliability growth programmes defined these shall be provided, indicating the rationale for the growth programme, starting point data, target points and planned duration.

k. ARM data shall contain information listed below:

i. Reliability, Maintainability and Availability Prediction.

ii. Failure Modes, Effects and Criticality Analysis (refer to DID ILS-076-010).

iii. Level of Repair Analysis (refer to DID ILS-081-010).

iv. RCM Analysis: The report must discuss the reliability assessment results of each analysed system. For each analysed system the critical failures must be identified, their impact on system functionality assessed, and actions mitigating the probability of the failure and / or the impact must be recommended. These recommendations are to be actioned as per the Reliability Assessment Rules in the ILSP

v. Preventative Maintenance Task Analysis (refer to DID ILS-081-20).

vi. An Impact assessment of any Engineering Changes to the systems and an analysis, if required, to demonstrate that the reliability of the affected system has not been negatively impacted;

vii. A description of each of the systems analysed. The report must describe the system’s criticality to the mission as well as the extent to which the system’s performance may degrade without affecting the function(s) required to perform the mission;

viii. A description of the reliability block diagrams and how they have been developed including assumptions made, calculations used and the source of data used, including its associated level of confidence.

ix. The report must discuss the reliability assessment results of each analysed system. For each analysed system the critical failures must be identified, their impact on system functionality assessed, and actions mitigating the probability of the failure and / or the impact must be recommended.

l. The report must clearly define the systems and subsystems usage including assumptions made, the input data used and the calculations used.

Reliability Analysis Report, Rev 0





Reliability Analysis Report

ILS-076-030



.






1. TITLE

Reliability Analysis Report


ILS-076-030


The purpose of this DID is to define the Reliability Analysis Report performance of the equipment on board the Ship.

4. REFERENCES

Attachments: Nil


5. FORMAT





6. CONTENT

a. The Report must include the following information, as a minimum:

i. Executive summary covering the significant elements of the report;

ii. An Impact assessment of any Engineering Changes to the Ship systems described in the Design RAR and an analysis, if required, to demonstrate that the reliability of the affected system has not been negatively impacted;

iii. A description of each of the Ship systems analysed. The report must describe the system’s criticality to the mission as well as the extent to which the system’s performance may degrade without affecting the function(s) required to perform the mission;

iv. A description of the reliability block diagrams and how they have been developed including assumptions made, calculations used and the source of data used, including its associated level of confidence.

b. The report must discuss the reliability assessment results of each analysed system. For each analysed system the critical failures must be identified, their impact on system functionality assessed, and actions mitigating the probability of the failure and / or the impact must be recommended. These recommendations are to be actioned as per the Reliability Assessment Rules in the Integrated Logistic Support Plan (ILSP).

c. The report must clearly define the systems and subsystems usage including assumptions made, the input data used and the calculations used.





d. The Report scope and depth for each system analysed and results provided must, as a minimum, be equivalent to the scope and depth contained in the Design Reliability Assessment Report provided as GFI.

Integrated Logistic Support Plan, Rev 0





Integrated Logistic Support Plan

ILS-080-010



.






1. TITLE

Integrated Logistic Support Plan (ILSP)


ILS-080-010


The ILSP describes the Supplier’s approach and methodology to develop and deliver the Integrated Logistic Support (ILS) elements necessary to support the Ship. It must be the primary document describing what must be done, how it will be done and what must be produced within the ILS program.

4. REFERENCES

Attachments: Nil


5. FORMAT





6. CONTENT

a. The ILS Plan describes the management, processes and procedures, elements and products, and organizational structure that will be used for the ILS program related to the project. This plan must include a detailed description of the methodology for implementing the required tasks and it should describe how the Plan controls the ILS program. The ILS Plan must include the following Chapters:

i. Chapter 1 – General Information;

ii. Chapter 2 – Tasks to be undertaken during the work; and

iii. Chapter 3 – Tasks to be undertaken and deliverables during the Project.

b. For Chapter 1 of the ILS Plan, the Subject Matter must be broken down into the following sections:

i. Section I – General. This section provides a description of the ILS Plan so as to establish a clear understanding of the scope, content and organization of the material presented.

ii. Section II – Ship Operating Environment. The section provides a description of the operational environment of the system / equipment and how the operational requirements will drive the ILS program. Included must be details of the annual and cycle operating hours, duty cycles, maximum allowable downtime and operational life expectancy as stipulated in the Contract.





iii. Section III – Supplier’s Approach and Design Integration. This section describes the design interface / engineering discipline integration that will establish integration of all engineering, design, procurement and management efforts, and disciplines including Availability, Reliability and Maintainability (ARM), ILS, standardization and production. It must depict the processes to control the influences on the Product Support Analysis (PSA) programs, cost effective design enhancement and system/equipment design and selection. Included is identification of the audit trail and the reporting criteria.

c. For both Chapters 2 and 3 of the ILS Plan, the Subject Matter must be broken down into the following sections:

i. Section I – ILS Program Management, Organization and Performance. This section provides a description of the overall process for use in managing and executing the ILS program. This section contains the following sub-sections:

• Contractor's Objectives, Policies, General Management Procedures. The objectives, policies and general management procedures that relate to the ILS program.

• Contractor’s ILS Organizational Structure. The Contractor’s organizational and management structure that has been selected to accomplish the contracted ILS program requirements.

ii. Section II – ILS Program Tasks. This section contains a detailed description of how the Contractor will accomplish all ILS program tasks. This section contains the following sub-sections:

• PSA. Outlines the PSA strategy and processes to be followed by the Supplier Identification of any applicable ILS standard used;

• PSA Candidate List. Provides list of items upon which PSA will be performed and documented; and

• Product Support Analysis Record (PSAR) system. Contains a description of the PSAR system which will be used. Identification of any applicable ILS standard used must be included.

iii. Section III – ILS Element Plans. This section describes the specific techniques to be used and tasks to be performed to develop the End Item, and how the operational and utilization requirements will be met by each of the following:

• For chapter 2, the ILS schedule of activities during the work and their completion dates;

• For chapter 3, the schedule of ILS elements delivery during the Project; and

• Process chart demonstrating how the ILS elements will be integrated into the ship final design and construction activities.

Product Support Analysis, Rev 0





Product Support Analysis

ILS-080-020



.






1. TITLE

Product Support Analysis


ILS-080-20


The Product Support Analysis (PSA) Report must provide the logic and rationales used to identify equipment and components that require detailed PSA and list the candidates for PSA. The identified equipment and components that are critical to meeting the Ship’s Availability, Maintainability and Reliability (ARM) metrics during the vessel’s lifecycle are as stated in the Statement of Work (SOW). The PSA shall also produce a relational database holding the relevant logistical and ARM data for each identified piece of equipment.

4. REFERENCES

Attachments: Nil


5. FORMAT



b. The format shall not impose any restriction on searching, editing, copying, or printing. c. The information shall be provided in English and in French, if available. d. PSA Candidates Report must be prepared in the Supplier's format. Electronic copies of the

PSA Candidates Report that are delivered must be provided in a format compatible with the MS Office suite. Final copies of the PSA Candidates Report delivered must also be in PDF Format. The PSA Candidates Report must include the following sections:

i. Title Page; ii. Table of Contents; iii. Document Control Log; iv. Revision Record; v. Subject Matter; vi. Notes; and vii. Appendices.

e. Title Page - The Title page must contain the following information: i. Title: PSA Candidates Report – “Vessel” project; ii. Contract No: XXXXXXXXXXXX; iii. Prepared By: Supplier’s name and address; and iv. Authenticated By: Contractor approval signature(s) and date.

f. Table of Contents - The Table of Contents should list the title and page number of each titled paragraph and subparagraph, figure, table and appendix.

g. Document Control Log - The Document Control Log should contain three columns: Revision, Date and reason for the change.





h. Revision Record - The Revision Record should contain a listing of paragraphs and corresponding pages which are affected by the change.

i. Subject Matter - The plan text that addresses the material that is to be included in the document.

j. Notes - This section must contain any general information that aids in the understanding of the document (e.g. Background information, glossary). This section should include an alphabetical listing of all acronyms, abbreviations and their meanings as used in the plan. This listing must be included with the final plan.

k. Appendices - Appendices may be used to provide information published separately for convenience (e.g. charts, classified data). As applicable, each appendix must be referenced in the main body of the plan where the data would normally have been provided. Appendices may be bound as separate documents for ease of handling.

6. CONTENT

a. The PSA Report must include a description of the integrated approach and methodology used for the analysis.

b. As a minimum, the PSA Report shall comprise two main chapters: i. Ship System Overview.

• Description of systems and their intended functions, including system block diagrams and equipment family tree.

• Description of subsystems and equipment comprising the system. • Methodology and criteria for identifying equipment and components within the

system or subsystem, which require PSA. • Identification of equipment and components within the system or subsystem

which require further PSA. • Description of rationales, analysis conducted and basis for recommendations

whether further PSA is to be conducted or not; ii. PSA Candidates List, which is a list of equipment and components that are identified

as critical to meeting the Ship’s ARM metrics as per the SOW. Each item on the list must include the following information: • Reference to Configuration Items Index inside the Technical Data Package

(TDP). • Equipment Nomenclature. • Rationales, analysis conducted and basis for recommendations. • A relational database of the logistical and ARM data for each item on the PSA

Candidates List. The data shall include: Supplier / OEM Nomenclature; Supplier / OEM Equipment Part Number; NATO Stock Number (if applicable); Mean Time Between Failure (MTBF); Mean Time to Repair (MTTR); Turnaround Time (TAT) for Repairable Items; Adjusted TAT for Repairable Items; Procurement Lead Time for Non-Repairable Items; Operational Manual Document Reference;





Maintenance Manual Document Reference; Special Tools and Test Equipment (STTE); Obsolescence Notice; Warranty Info; Maintenance Plans and Spare Parts.

iii. Analysis and conclusion of the ARM data against the Ship’s life cycle ARM requirements as per the SOW.

iv. Contractor recommendations for any additional analysis. c. The PSA Report shall include all information required for general understanding and shall

define all special terms and acronyms used.

Product Support Analysis Record, Rev 0





Product Support Analysis Record

ILS-080-030



.

Product Support Analysis Record, Rev 0





1. TITLE

Product Support Analysis Record (PSAR)


ILS-080-030


The PSAR is a relational database holding various logistical and Availability, Reliability and Maintainability (AR&M) data.

4. REFERENCES

Attachments: Nil


5. FORMAT

a. The PSAR must be developed and prepared using the Supplier’s selected tool/system. b. The PSAR must be delivered to Canada as an XML file and in accordance with the GEIA-

STD-0007-B standard. c. The accompanying report to the PSAR must be prepared in the Contractor's format.

Electronic copies of the draft report that are delivered to Canada must be provided in a format compatible with the MS Office suite. Final copies of the report delivered to Canada must be in PDF Format. The report must contain the information in the Supplier’s format to include items cited in the “Report Content” section of this document.

6. CONTENT

a. The PSAR must record the results of the Product Support Analysis (PSA) as described in the SOW.

b. The Product Support Analysis Record must include all the information required in accordance with the PSAR Data Elements list as agreed to by Canada and VSY during relevant workshops under the contract.

c. The PSAR report must provide, as a minimum, the following information:

i. Description of the selected PSA tasks that have contributed to the PSAR data;

ii. Description of any applicable division of the PSAR;

iii. Summary description of all data collected, generated and updated during the PSA process and design process;

iv. List of (common) challenges regarding the population of PSAR data fields;

v. File Schema and data format standards applied to data fields of the PSAR; and,

vi. Additional Information. The report must include all information required for general understanding and must define all terms and acronyms used.

Master Equipment List, Rev 0





Master Equipment List

ILS-080-040



.






1. TITLE

Master Equipment List


ILS-080-040


The purpose of this DID is to identify the requirements for the development and presentation of the Master Equipment List. The Master Equipment List is to identify all the equipment that requires maintenance activities, configuration items and tracked serial numbers. The Master Equipment List further inputs into the Asset Breakdown Structure where the parent unit is identified with children breakdown.

4. REFERENCES

Attachments: Nil

References: Vessel Fleet Safety Manual; This DID must be read in conjunction with the appropriate paragraphs of the Statement of Work, Contract Data Requirements List and any references cited in the DID

5. FORMAT


a. The Master Equipment List format must be prepared in electronic format compatible with MS Office applications.

6. CONTENT

a. The Master Equipment List (MEL) is a listing of equipment and components used as unique items in the Client’s Maintenance Management System for the purpose of tracking maintenance data.

b. The MEL must specify equipment in accordance with the Supplier's Work Breakdown Structure.

c. Breakdown Structure and include:

i. Make, model, and serial number;

ii. Original Equipment Manufacturer (OEM's) name and address

iii. Supplier name and address

iv. Equipment nomenclature / description;

v. Weight;

vi. OEM model number;

vii. OEM's part number;

viii. NATO Stock Number, when available;

ix. Capacity and / or rating;





x. Quantity; and,

xi. OEM warranty information, including:

• Coverage;

• Terms; and,

• Start and end dates.

d. The MEL must include the following:

i. Identity of all components, sub-assemblies and parts down to the lowest repairable level;

ii. Identity of the versions of all hardware and software items; and,

iii. Listing of common consumable items, such as a-rings, fuses, gaskets, fasteners , and indicate where they are used.

e. The MEL must identify Critical Equipment as listed in the Vessel Fleet Safety Manual.

f. For each item identified as Critical Equipment on the MEL, the following additional information must be provided:

i. Regulatory body approval;

ii. Unit of issue;

iii. Production lead-time;

iv. Unique tools or support and test equipment necessary to inspect, test, calibrate, service, repair, or overhaul the end item; and,

v. Name, address, contact information of the vendor supplying the part.

g. DELIVERABLES

i. An electronic copy of the MEL is to be delivered in accordance with the Integrated Master Schedule

Asset Breakdown Structure, Rev 0






ILS-080-050



.






1. TITLE



ILS-080-050


The Asset Breakdown Structure identifies all Systems, Sub-Systems, Components and Equipment within the applicable system used in the Vessels operating profile.

4. REFERENCES

Attachments: Nil

References: Vessel Fleet Safety Manual; This DID must be read in conjunction with the appropriate paragraphs of the Statement of Work, Contract Data Requirements List and any references cited in the DID

5. FORMAT


a. The Asset Breakdown Structure format must be prepared in editable electronic format compatible with MS Excel.

b. The information shall be provided in English and in French, if available.

6. CONTENT

a. The Asset Breakdown Structure must as a minimum contain the following:

i. Equipment relation to Vessel design (SWBS);

ii. Vessel name;

iii. Asset Breakdown number;

iv. TAG number on associated drawing;

v. Supplier;

vi. Suppliers cage number (full address if no cage number allocated);

vii. Suppliers equipment nomenclature;

viii. Suppliers equipment part number;

ix. OEM;

x. OEM cage number (full address if no cage number allocated);

xi. OEM equipment nomenclature; and

xii. OEM part number;

xiii. Additional Information;

xiv. MSDS sheets to be delivered with a cover page and table of contents. The MSDS





sheets must not be more than 5 years old at time of delivery.

xv. The Asset Breakdown structure must be based on the Vessel design and should extend no deeper than the equipment level.

xvi. The ABS must include all designated hardware and software configuration items.

xvii. Hardware items must appear in the ABS at the level at which they will be removed and replaced.

xviii. Software items (if any) only need be identified by name, software identification number and version number.

Note : The Asset Breakdown Structure need not identify items internal to Commercial-Off-The-Shelf (COTS) equipment that will be maintained by industry. The lower levels of the Asset Breakdown Structure must not include repair parts, common items (such as “o”-rings, gaskets and fasteners) or bulk items (such as glues, paints and solvents) needed to perform maintenance.

b. Delivery

i. A digital copy of the publications must be delivered to the Prime as per the Integrated Master Schedule.

Material Identification Data, Rev 0





Material Identification Data

ILS-080-060








1. TITLE

Material Identification Data (DND)


ILS-080-060


The identification and provision of specific packages of information required for equipment in order to initiate the codification of selected / fitted equipment into the DND Supply System.

4. REFERENCES

Attachments: Nil


5. FORMAT


a. The report must be prepared in the format linked to the Product Support Analysis Report (PSAR). Electronic copies of the report that are delivered to the Purchaser must be provided in a report format compatible with the XML PSAR database. Final copies of the report delivered to Purchaser must be in PDF Format. The report must include the following sections:

i. Title Page;

ii. Table of Contents;

iii. Document Control Log;

iv. Revision Record;

v. Subject Matter;

vi. Notes; and

vii. Appendices.

b. Title Page - The Title page must contain the following information:

i. Title: Material Identification Data (including UII/UID) – Project Name;

ii. Contract Number;

iii. Prepared By: Supplier’s name and address; and

iv. Authenticated By: Supplier approval signature(s) and date.

c. Table of Contents - The Table of Contents should list the title and page number of each titled paragraph and subparagraph, figure, table and appendix.

d. Document Control Log - The Document Control Log should contain three columns: Revision, Date and reason for the change.

e. Revision Record - The Revision Record should contain a listing of paragraphs and corresponding pages which are affected by the change.

f. Subject Matter - The plan text that addresses the material that is to be included in the





document.

g. Notes - This section must contain any general information that aids in the understanding of the document (e.g. Background information, glossary). This section should include an alphabetical listing of all acronyms, abbreviations and their meanings as used in the plan. This listing must be included with the final plan.

h. Appendices - Appendices may be used to provide information published separately for convenience (e.g. charts, classified data). As applicable, each appendix must be referenced in the main body of the plan where the data would normally have been provided. Appendices may be bound as separate documents for ease of handling.

i. Unless a specific template is provided by VSY, the deliverables may be prepared in contractor’s format upon review and approval by VSY.

j. The format shall not impose any restriction on searching, editing, copying, or printing.

k. The information shall be provided in English and in French, if available.

6. CONTENT

a. Equipment Identification

i. UIIs must be used to generate and apply 2D Data Matrix UID marks for serially-managed materiel.

ii. For the following categories of materiel when materiel is owned by Canada, the Unique Item Identifiers (UII) must be generated in accordance with NATO STANAG 2290 and DAOD 3010-1, and the 2D Data Matrix mark positioned immediately adjacent to or as part of the equipment Nameplate/Label/Identification Plate:

• All items that are Configuration Items as indicated by D-01-002-007/SG-006, “Criteria for the Selection of Configuration Items”;

• All items that are subject to Preventive Maintenance;

• All items that are subject to Classification Society Inspections and Surveys;

• Training equipment, as applicable; and

• Support Tools and Test Equipment.

b. Where materiel is intended to be owned by an In Service Support Contractor (ISSC), the same data is required but the UII marking is not required.

c. For fitted equipment and spares that are identified to be serially managed for each category in 10.3.2.2 above, in addition to cataloguing requirements in Chapter 3.9 of D-01-100-214/SF-000 “Preparation Provisioning Documentation for Canadian Forces Equipment”, identify and record in a table the following Identification Data Set elements:

• Logistics Control Number, as identified in the PSAR;

• Item name, as identified in the PSAR (limit of 40 characters);

• Item description, as identified in the PSAR (limit of 40 characters);

• Manufacturer NATO CAGE Code, as identified in the PSAR (limit of 32 characters);

• Part Number (limit of 40 characters);

• Serial Number;

• Item dimensions (volumetrics);





• UII (see STANAG 2290 for derivation of the UII from the data encoded in the 2D Data Matrix UID Mark), UII, which is comprised of the following:

• Enterprise Identifier (EID) - NCAGE;

• Original part number or original batch/ lot number, as applicable (optional); and

• OEM Serial number;

d. NATO stock number (NSN) or Permanent System Control Number (PSCN); and

e. The onboard or shore location of the Item as delivered to Canada (NOTE: Onboard location must be deck, frame, space identification).

f. For general cataloguing requirements, generate a report based on LSAR DED info that provides data fields as identified in Chapter 3.9 of D-01-100-214/SF-000 “Preparation Provisioning Documentation for Canadian Forces Equipment”. The format must be as provided by the Purchaser.

Technical Data Package, Rev 0





Technical Data Package

ILS-080-070



.






1. TITLE

Technical Data Package


ILS-080-070


The Technical Data Package (TDP) includes the technical data, drawings, manuals and other supporting documentation progressively developed during the design and build phases and is required to assess the design, accept and support the ship during its operational cycle.

4. REFERENCES

Attachments: Appendix A


5. FORMAT




6. CONTENT

a. The TDP must consist, as a minimum, of the following: i. Description of how the TDP is organized and laid out; ii. Summary of the revisions to the TDP; iii. A TDP Index (list of documents and attributes); iv. The Baseline Technical Data; v. The Ship TDP; and vi. The In-Service Technical Data.

b. The TDP must be indexed in an electronic format. It must have search capability and it must provide electronic links to system and equipment specific data and documentation.

c. The Baseline Technical Data must consist of documentation that is recorded and stored for reference purposes. Baseline Technical Data must be comprised, as a minimum, of the following:

i. Description of how the TDP is organized and laid out. ii. A summary of the revisions to the TDP. iii. A table of contents. iv. Index of Amendments and Modifications. v. Index of Configuration Items (CIs) (Asset Breakdown Structure - ABS). vi. Index of Components or Items of the Equipment (Master Equipment List - MEL).





vii. Indentured Drawing List. viii. Index of Configuration Documentation. ix. Index of Technical Publications. x. Index of Class I (Major) Engineering Change Proposals. xi. Index of Class II (Minor) Engineer Change Proposals. xii. Index of Requests for Deviations. xiii. Index of Ancillary Equipment. xiv. The Baseline Technical Data:

• Design and Engineering Calculations, Analysis, Drawings and Reports. • Statement of Metacentric Height. • Final Weight Report. • Construction Bill of Materials (BOM) and Build Records. • Engineering Changes and Deviations. • Engineering Change Data Packages. • Completed Trials Report. • Maintenance and Supply Analysis. • Superseded drawings and technical publications. • Photographs. • Objective Quality Evidence as described in the SOW.

d. The Ship TDP must contain the technical data and documentation required by the vessels crew to operate and maintain the Ship. The TDP must be supplied in electronic format, contain an electronically linked and searchable index that follows the Equipment Family Tree Structure (EFT). The Ship TDP must contain, as a minimum, the following sections:

i. Technical Publications; ii. Ship’s Manuals; iii. Ship System Manuals; iv. As-Fitted Drawings; v. Equipment Family Tree; vi. Maintenance Documentation ; vii. Supply Documentations; and viii. Hazardous Material Documentation.

e. The In-Service Technical Data must consist of documentation that is controlled and managed to reflect current configuration for each Ship. In-Service Technical Data must be comprised of the following technical data and documentation in addition to the Ship TDP:

i. 3-Dimensional ship product model; ii. Software Documentation; iii. Configuration Item List; iv. Docking Plan; and v. Trial Documentation.

f. As a minimum, the TPD shall consist of the following: g. The requirements of each index are further defined in Appendix A. h. The TDP shall include all information required for general understanding and shall define

all special terms and acronyms used.


Appendix A – Definition of Indices

Document No: VSY-A08.22-0149


1. Index of Amendments and Modifications

The Index of Amendments and Modifications shall list all amendments and modifications introduced that affect the Equipment design.

2. Index of Configuration Items

The Index of CIs shall list, in hierarchical form, all the CIs constituting the Equipment. The Index of CIs shall be developed from data from the Configuration Item List. For each CI, the Index of Configuration Items shall detail the following information:

a. CI Reference Number - This field shall detail the reference number allocated to the CI by the Supplier. This number is to relate the CI to higher level assembly to which it belongs in a hierarchical manner to system level;

b. CI Nomenclature - This field shall detail the name allocated to the CI;

c. CI Type - This field shall detail whether the CI is a Hardware Configuration Item (HWCI) or a Computer Software Configuration Item (CSCI);

d. HWCI - This field is applicable to CSCIs only and shall detail the HWCI the CSCI is resident in;

e. Subsystem - This field shall detail the CI’s parent Subsystem;

f. System - This field shall detail the CI’s parent System; and

g. Design Organisation - This field shall detail the organisation responsible for design of the CI.

The Index of Configuration Items shall be sorted in Equipment and then Subsystem order. Headings shall be positioned in the Index of Configuration Items to identify where each System and Subsystem begin.

3. Index of Components

The Index of Components (IOC) shall detail, in hierarchal form, the physical build structure of the Equipment and shall go down to and include piece parts. The IOC shall be developed from Data contained in the Logistics Support Analysis Record (LSAR). For each Item in the IOC, the IOC shall detail the following information:

a. Indenture Level - This field shall document the indenture level of the Item. The Equipment is indenture level 1;

b. Part Number - This field shall document the Item’s Part Number;

c. Variant Number - When more than one variant of an Item has been used in the construction of the Equipment, the Part Number of each variant is to be given a variant number (e.g. 1,2,3). This field shall default to one (1) when only one variant of an Item has been used;

d. Part Number Status - This field shall contain the status of the Part Number (e.g. PROPOSED, CURRENT, OBSOLETE and HISTORICAL);

e. Quantity Fitted - This field shall document the quantity of the Item fitted to the Item’s next higher assembly;

f. Drawing Number - This field shall document the Drawing Number of the Item; and

g. Nomenclature - This field shall document the Item’s nomenclature.

The IOC shall be sorted in Equipment, then Subsystem, then CI order. Headings shall be positioned in the IOC to identify where each System, Subsystem and CI begin.





4. Indentured Drawing List

The Indentured Drawing List (IDL) shall list, in hierarchal form, all the drawings constituting the Equipment design, including Sub-subcontractor drawings. For each drawing, the IDL shall detail the following information:

a. Indenture Level - This field shall document the indenture level of the drawing;

b. Drawing Number - This field shall document the drawing number;

c. Revision Letter - This field shall document the latest revision letter of the drawing applicable to the Equipment;

d. Drawing Title - This field shall document the title of the drawing;

e. Drawing Type - This field shall document the drawing type which the drawing belongs to e.g. Detail Assembly Drawing, Specification Control Drawing, Wiring List, etc…;

f. Drawing Size - This field shall document the sheet size of the drawing e.g. A2, A3, etc; and

g. Number of Sheets - This field shall document the number of sheets making up the drawing.

5. Index of Configuration Documentation

The Index of Configuration Documentation (IOCD) shall list the Configuration Documentation describing the functional, allocated and product baselines for the Equipment (drawings are to be excluded from the IOCD as they have been listed elsewhere). For each document, the IOCD shall detail the following information:

a. CI Reference Number - This field shall detail the CI Reference Number the Document is applicable to;

b. CI Nomenclature - This field shall detail the CI's nomenclature;

c. Document Reference Number - This field shall detail the Document's Reference Number;

d. Document Revision Number - This field shall detail the Revision Number of the Document; and,

e. Document Type - This field shall detail the type of document the Document belongs to (e.g. Development Specification, Test Requirement Document, Software Requirements, etc.).

The following types of Configuration Documentation, as a minimum, shall be included in the list:

a. System Specifications;

b. Development Specifications;

c. Product Specifications;

d. Interface Control Documents;

e. Software Requirements Specifications;

f. Interface Requirements Specifications;

g. Software Product Specifications;

h. Software Version Descriptions;

i. Software Design Descriptions;

j. Interface Design Descriptions;

k. Database Design Descriptions;

l. Material Specifications; and

m. Process Specifications.





The IOCD shall be divided into two (2) sections. Section 1 shall be sorted in System then Subsystem then CI order. Section 2 shall be sorted in Document Type then Document Reference Number order. Headings shall be positioned in Section 1 to indicate where each System, Subsystem and CI begins. Headings shall be positioned in Section 2 to indicate where each Document Type begins.

6. Index of Technical Publications

The Index of Technical Manuals (IOTM) shall list the technical manuals developed under the Contract. For each Technical Manual, the IOTM shall detail the following information:

a. Supplier Reference Number - This field shall detail the Supplier Reference Number for the Technical Manual;

b. Title - This field shall detail the title of the Technical Manual; and

c. Related Cis - This field shall detail the Configuration Items the Technical Manual is applicable to.

The IOTM shall be divided into two (2) sections. Section 1 shall be sorted in System then Subsystem then CI order. Section 2 shall be sorted in Supplier Reference Number order. Headings shall be positioned in Section 1 to indicate where each System, Subsystem and CI begins. No headings shall be positioned in Section 2.

7. Index of Class I (Major) Engineering Change Proposals

The Index of Class I (Major) Engineering Change Proposals (ECPs) shall document all Class I ECPs raised against the Equipment and its constituent Items during the Subcontract, including those raised by the Sub-subcontractors. For each ECP, the Index of Class I ECPs shall detail the following information:

a. ECP Number - This field shall document the unique ECP identification number supplied by the Purchaser;

b. ECP Revision Number - This field shall document the revision level of the ECP i.e. R1 or R2;

c. ECP Justification Code - This field is as defined in MIL-HDBK-61A;

d. ECP Title - This field shall document the title of the ECP;

e. Date Raised - This field shall document the date the ECP was raised;

f. ECP Status - This field shall document the status of the ECP;

g. Status Date - This field shall document the date the status of the ECP changed;

h. CCB Decision - This field shall document the decision made by the Configuration Control Board (CCB) for approval to proceed;

i. Decision Date - This field shall document the date of the CCB decision;

j. Impacted Cis - This field shall document the CIs impacted by the ECP;

k. Affected Part Numbers - This field shall document the CI Part No variants impacted by the ECP; and,

l. New Part Numbers - This field shall document the new CI Part No variants introduced as a result of the ECP. Where the new Part No is a re-identification of an existing Part No this relationship shall be clearly shown.

8. Index of Minor Engineering Change Proposals

The Index of Class II (Minor) Engineering Change Proposals (ECPs) shall document all Class II ECPs raised against the System and its constituent Items during the Contract, including those raised by the Sub-subcontractors. For each ECP, the Index of Minor ECPs shall detail the following information:





a. ECP Number - This field shall document the unique ECP identification number supplied by the Purchaser;

b. ECP Revision Letter - This field shall document the revision level of the ECP i.e. R1 or R2;

c. ECP Title - This field shall document the title or a brief description of the ECP;

d. Date Raised - This field shall document the date the ECP was raised;

e. ECP Status - This field shall document the status of the ECP;

f. Approval Authority - This field shall document who approved or rejected the ECP;

g. Decision Date - This field shall document the date the approval authority approved or rejected the ECP;

h. Impacted CI - This field shall document the CI impacted by the ECP; and

i. CI Part Numbers - This field shall document the CI Part No variants impacted by the ECP.

9. Index of Requests for Deviation

The Index of Requests for Deviation (RFDs) shall document all RFDs raised against the Equipment and its constituent Items during the Subcontract, including those raised by the Sub-subcontractors.

For each RFD, the Index of RFDs shall detail the following information:

a. RFD Reference Number - This field shall document the unique RFD identification number;

b. RFD Title/Description - This field shall document the title or provide a brief description of the RFD;

c. RFD Class - This field shall document the class of the RFD i.e. Critical, Major or Minor;

d. Date Raised - This field shall document the date the RFD was raised;

e. RFD Status - This field shall document the status of the RFD;

f. Approval Authority - This field shall document who approved or rejected the RFD;

g. Decision Date - This field shall document the date the approval authority approved or rejected the RFD;

h. Impacted CI - This field shall document the CI impacted by the RFD;

i. CI Part Number - This field shall document the CI Part Number variant impacted by the RFD;

j. Affected Part Number - This field shall document the Part Number of the Item subject to the RFD;

k. Affected Serial Numbers - This field shall document the Serial Number(s) of the Item subject to the RFD;

l. MMI Part Number - If the affected Item is not a Maintenance Managed Item (MMI) and does not build directly to the CI then this field shall document the Part Number of the higher level MMI; and

m. MMI Serial Number(s) - This field shall document the Serial Number(s) of the MMI specified at subparagraph (l).

The Index of RFDs shall be divided into three (3) sections. Section 1 shall list RFDs classified as Critical, Section 2 shall list RFDs classified as Major and Section 3 shall list RFDs classified as Minor. Each Section shall be further subdivided into two (2) Subsections. Subsection 1 shall be sorted in RFD Reference No order. Subsection 2 shall be sorted in System then Subsystem then CI order. Headings shall be positioned in Subsection 2 to indicate where each System, Subsystem and CI begins. No headings shall be positioned in Subsection (1).





10. Index of Ancillary Equipment

The Index of Ancillary Equipment (IAE) shall list the support Equipment required to support the maintenance/operation of the Equipment and its constituent Items.

NOTE: Support Equipment includes, but shall not be limited to, Automatic Test Equipment and STTE.

For each piece of Support Equipment, the IAE shall detail the following information:

a. Support Equipment Designation - This field shall document the designation of the support Equipment;

b. Nomenclature - This field shall document the nomenclature of the support Equipment;

c. Support Equipment Type - This field shall document the support equipment type the Support Equipment belongs to (for example Ground Support Equipment, Automatic Test Equipment, Special to Type Tooling, etc.;

d. Supported CI(s) - This field shall document the CI(s) supported by the Support Equipment;

e. CI Part Number Variants - This field shall document the CI Part Number variant(s) supported by the Support Equipment; and

f. Affected Part Numbers - If the Item(s) supported by the support Equipment is (are) below the CI level then this field shall document the Part Number(s) of the Item(s) supported by the Support Equipment.

The IAE shall be divided into two (2) Sections. Section 1 shall be sorted by Support Equipment Type then by Support Equipment Designation. Section 2 shall be sorted by Supported CI then Support Equipment Type then Support Equipment Designation order. Headings shall be positioned in Section 1 to indicate where each Support Equipment Type begins. Headings shall be positioned in Section 2 to indicate where each CI begins.

Technical Document Tree, Rev 0





Technical Document Tree

ILS-080-080



.






1. TITLE

Technical Document Tree


ILS-080-080


The Technical Document Tree (TDT) must be a tracking index of existing and planned Design technical documents and their attributes. The tracking of documents is intended to be produced and delivered as rolling updates of the entirety of technical documents for the Design as planned and generated by VSY. Additionally, the TDT must identify those items which are deemed controlled goods, the Intellectual Property Rights associated with documents, and those items that have a requirement for Class Society approval as data attributes.

4. REFERENCES

Attachments: Nil


5. FORMAT




6. CONTENT

a. The TDT shall provide an index of all technical documents structured following the same hierarchy as the Equipment Tree of the ship.

b. As a minimum, each document on the TDT shall have the following attributes: i. Document number (unique identifier); ii. Document title; iii. Hierarchy ID (e.g. drawing, report, schedule) iv. Reference to Configuration Items v. Technical Data Package (TDP) item, Yes / No; vi. Current document version; vii. Current document version date; viii. Update Needed (Yes/No); ix. Status of document (New, In Planning, In Work, In Review, Submitted, Released); x. Appraisal by class society (Yes/No); xi. Controlled Goods (Yes/No); xii. OCI (Client Contact); xiii. Owner OPI (e.g. Thales, CSC);





xiv. SBWS tags (if applicable); xv. Related Documents; xvi. Document notes.

c. The TDT shall include all information required for general understanding and shall define all special terms and acronyms used.

Technical Documentation Development Plan, Rev 0





Technical Documentation Development Plan

ILS-080-090



.






1. TITLE Technical Documentation Development Plan

2. IDENTIFICATION NUMBER ILS-080-090


The Technical Documentation Development Plan (TDDP) includes a complete list of technical data planned for delivery during the course of the vessel contract. The TDDP includes the development plans, anticipated delivery milestones and associated maturity levels.

4. REFERENCES

Attachments: Nil

References: DID ILS 080-030; This DID must be read in conjunction with the appropriate paragraphs of the Statement of Work, Subcontract Data Requirements List and any references cited in the DID.

5. FORMAT




6. CONTENT

a. The TDDP must include a chapter to describe the overall strategy to develop technical documents for the duration of the vessel contract:

i. Description of the use and re-use of the existing documentation; ii. Description of standards applied (corporate or commercial) to the various types of

technical documentation and how this will help optimize the effort to meet the document requirements of the purchaser;

iii. Description of the maturity labels applied as status to the various technical documents.

iv. Description of other labels applied as status/conditions to the various documents. v. Description of the strategy for project documentation labelling and numbering; vi. Description of the Supplier’s plan to incorporate existing supplier documents.

b. The TDDP must be aligned with the list of technical documents contained in the TDT (DID ILS 080-030). The TDDP must include a list of all work planned for development of the technical documents. Each item in the list of planned work must have the following attributes:

i. Document number (unique identifier); ii. Document title; iii. Work Product Deliverable (Yes/No); iv. Hierarchy ID (e.g. drawing, report, schedule); v. Planned Dates for the “In Work”, “Submitted” and “Released” document status;





vi. Notes and comments c. The TDDP shall include all information required for general understanding and shall define


ILS Capabilities, Rev 0





ILS Capabilities

DID ILS-080-100



.

ILS Capabilities, Rev 0




Integrated Logistics Support Capabilities DID ILS-080-100

Purpose

The DID is to advise the Purchaser of the reliability, maintainability and availability of the Equipment and may be used to determine life cycle costs through Schedule B5 Requirements Matrix.

References




Format and Content

Provide the updated Schedule B5 noting all changes that occurred from last submission.

Initial Maintenance Task List, Rev 0





Initial Maintenance Task List

ILS-081-010



.






1. TITLE

Initial Maintenance Task List


ILS 081-010


The Initial Maintenance Task Analysis (IMTL) lists the tasks for each maintenance action, the skills, resources, duration, material’s, tools, test and support equipment to accomplish the task. The purpose of IMTL is to identify and categorize an initial list of maintenance tasks for an Expert Panel Review (EPR). Tasks selected by the EPR will be subject to detailed Maintenance Task Analysis (MTA) as per DID ILS 081-020.

4. REFERENCES

Attachments: Nil

References: DID ILS 081-020; This DID must be read in conjunction with the appropriate paragraphs of the Statement of Work, Contract Data Requirements List and any references cited in the DID

5. FORMAT




6. CONTENT

a. The IMTL shall prepare a list of maintenance tasks for presentation to the Expert Panel Review (EPR). The IMTL shall cover tasks within the maintenance levels outlined in the SOW.

b. At a minimum for each maintenance task, the IMTL shall contain the following: i. Identification of the system, subsystem or equipment under analysis, including

Equipment Family Tree, name, model and/or part number; ii. Reference to Configuration Items Index inside the Technical Data Package (TDP).

Each maintenance task description including: • Equipment name and function. • Task title. • Brief task description. • Task type (e.g. preventive maintenance (PM), or predictive maintenance

(PdM)). • Level of Maintenance. • Task interval. • Task source (e.g. OEM, or regulation). • Warranty mandated task (yes or no).





• Placeholder to record EPR decision and note. c. The IMTL shall include all information required for general understanding and shall define


Maintenance Task Analysis Report, Rev 0





Maintenance Task Analysis Report

ILS-081-020



.






1. TITLE

Maintenance Task Analysis Report


ILS-081-020


The Maintenance Task Analysis (MTA) Report describes, for each maintenance task, the skills, resources and equipment needed to accomplish the task.

4. REFERENCES

Attachments: Nil


5. FORMAT




6. CONTENT

a. Maintenance Task Analysis (MTA) shall be performed on tasks selected in the Expert Review Panel’s review of the Initial Maintenance Task List (IMTL). The MTA report must include a description the integrated approach and methodology the contractor will use for the analysis.

b. The report must contain at a minimum, the following data for each MTA performed:

i. Identification of the system, subsystem or equipment under analysis, including Equipment Family Tree, name, model and/or part number;

ii. Each maintenance task description including:

(a). Task number;

(b). Title;

(c). Activity description, including reference to Supplier manual;

(d). Task interval or frequency;

(e). Associated condition monitoring feature, as applicable;

(f). Task complexity (level 1, 2 or 3);

(g). Task responsibility (ship staff, or ISSC);

(h). Safety Precautions;

(i). Pre-maintenance conditions;





(j). Applicable technical data;

(k). Applicable regulations and standards;

(l). Required performance/validation tests;

(m). Personnel manpower and skill requirements;

(n). Supply support requirements (spares, consumable material, tools and test equipment); and,

(o). Expected task duration.

c. The MTA Report shall include all information required for general understanding and shall define all special terms and acronyms used.

Maintenance Plan, Rev 0





Maintenance Plan

ILS-081-030



.






1. TITLE

Maintenance Plan


ILS-081-030


The Maintenance Plan provides a summary of maintenance requirements as they relate to the vessels cycle of operations, including consideration for repair and overhaul during the lifecycle. The plan also demonstrates that the vessels availability and maintainability requirements are met.

4. REFERENCES

Attachments: Nil


5. FORMAT




6. CONTENT

a. The maintenance plan shall compile maintenance tasks for each system, subsystem or equipment and produce a corresponding life cycle maintenance plan.

b. As a minimum, the maintenance plan shall include:


ii. Outline of the availability and maintainability requirements to be met in conjunction with the ship’s operational profile as per the SOW.

iii. Summary of all planned maintenance activities providing, as a minimum, the following data:

• Reference to Configuration Item (CI) List in the Technical Data Package (TDP);

• System, subsystem or equipment nomenclature;

• Description of maintenance activities per system;

• Maintenance activity frequency;

• Time to complete each maintenance activity;

• Number of technicians and disciplines required per each activity.

c. If requested, maintenance plans shall be prepared in a template that is compatible with the client’s Computerized Maintenance Management Software (CMMS).





d. The Maintenance Plan shall include all information required for general understanding and shall define all special terms and acronyms used.

e. The Maintenance Plan shall capture a Record of Deterioration in order to perform system replacement or repair, prior to failure occurrence.

Repairable Items List, Rev 0





Repairable Items List

ILS-081-040



.

Repairable Items List, Rev 0





1. TITLE

Repairable Items List


ILS-081-040


This DID defines the Items of the Equipment that are repairable.

4. REFERENCES

Attachments: Nil


5. FORMAT





6. CONTENT

a. The following are the repairable Items of the Equipment:

i. Description of the Equipment;

ii. SWBS #;

iii. Name of the Supplier;

iv. Description of the repairable;

v. Supplier's part number of the repairable;

vi. NATO Stock Number (if applicable) of the repairable;

vii. Indication as to whether the repairable is controlled under an Export Control Jurisdiction and, if so, which jurisdiction;

viii. Quantity of repairable’s in the Equipment;

ix. Basis of recommendation e.g. modelling, field experience, standard package, Classification Society, etc.;

x. Repairable flag (Y indicates repairable);

xi. Predicted number of repairs per year; and

xii. Unit price for each repair (in original currency).

Recommended STTE & CRETE & CRMTE, Rev 0





Recommended STTE & CRETE & CRMTE

ILS-082-010



.






1. TITLE

Recommended STTE & CRETE & CRMTE


ILS-082-010


The Recommended STTE & CRETE & CRMTE Lists will advise the purchaser of the Special Tools and Test Equipment (STTE), Common Range Electrical Test Equipment (CRETE), Common Range Hand Tools (CRHT) and Common Range Mechanical Test Equipment (CRMTE) required to undertake the level(s) of maintenance defined in the SOW.

4. REFERENCES

Attachments: Nil


5. FORMAT




6. CONTENT

a. As a minimum, the Recommended STTE, CRETE, CRMTE and CRHT Lists will include the following data:

i. Description; ii. Name of the supplier / OEM; iii. Supplier / OEM part number; iv. NATO stock number (if applicable); v. Recommended quantity; vi. Calibration requirements; vii. Unit Price (in original currency); viii. Lead time (Working Days from placing an purchase order); ix. Anticipated usage per Year for preventative/planned maintenance (hrs); x. Anticipated usage per Year for corrective maintenance (hrs); xi. Basis of estimate; xii. Reparability flag; xiii. Remarks; xiv. Storage Location (Carried on Board or Carried in Depot)

b. The Recommended STTE, CRETE, CRMTE and CRHT Lists shall include all information required for general understanding and shall define all special terms and acronyms used.

Spares List, Rev 0





Spares List

ILS-083-010



.

Spares List, Rev 0





1. TITLE

Spares List


ILS-083-010


The Spares List advises the purchaser of the stock requirements to support the vessel, based on supplier recommendations, reliability modeling and regulatory standards.

4. REFERENCES

Attachments: Nil


5. FORMAT




6. CONTENT

a. The Spares List shall contain stock requirements for suppliers’ recommended spares, regulatory minimum spares as per Class guidelines, insurance spares, and spares required for the Test and Trials and Commissioning phases. The list shall consider the operational profile of the vessel and the equipment, repair turnaround and support facilities;

b. As a minimum, each item on the recommended spare parts list shall contain the following data:

i. Reference to Configuration Item (CI) List in the Technical Data Package (TDP). ii. Supplier Nomenclature. iii. Supplier’s Part Number. iv. Item Description. v. Basis of Recommendation.

• OEM. • Reliability Modelling. • Field Experience. • Regulatory Minimum (Include Appropriate Reference). • Insurance Spare (Long Lead Items required to ensure fleet support).

i. Storage Location. • On Board (Defined as per SOW; includes Test & Trials, and Commissioning). • On Base (Defined as per SOW).

Spares List, Rev 0




i. Spares Quantity. ii. Minimum Order Quantity. iii. Expected Shelf Life. iv. Repairable Flag yes or no.

• Turnaround Time (TAT) if Repairable. • Adjusted TAT (includes administrative buffer) if Repairable. • Disposal Plan if Not Repairable.

i. Unit Price (Original Currency). ii. Mean Time Between Failures (MTBF). iii. Estimated Procurement Lead Time.

c. The completed list is to be submitted for review and final approval before proceeding to procurement;

d. All spares provided by the Contractor under this Contract and subject to this DID must be packaged in accordance with the SOW;

e. The Contractor must provide an onboard storage layout plan for spare and repair parts, and all other materiel stored on-board. The plan must outline all special storage requirements, conditions and maintenance that may apply to spares and repair parts stored on-board and shore based;

f. The Spares List shall include all information required for general understanding and shall define all special terms and acronyms used.

Material and Provisioning List, Rev 0





Material and Provisioning List

ILS-083-020



.






1. TITLE

Material and Provisioning List


ILS-083-020


To document and report the results of the analysis that determines the Provisioning Parts Breakdown List (PPB), the Recommended Spare Parts List (RSPL) and Special Tools and Test Equipment (STTE) required to support the Ships.

4. REFERENCES

Attachments: Nil


5. FORMAT

a. The report must be prepared in the Supplier's format. Electronic copies of the report that are delivered to Canada must be provided in a report format compatible with the XML PSAR database. The report must contain the information in the Supplier’s format to include items cited in the “Report Content” section of this document.

6. CONTENT

a. The Material and Provisioning List report must include the following information as a minimum:


ii. Description of the approach and methodology used to identify the supply items, both repairable and consumable spares;

iii. Description of methodology used to optimize the spares required to support Level One and Level Two maintenance to meet Ship operational and utilization profile and availability requirements.

iv. Description of which elements of PSA were utilized and how they influenced the analysis outcome. As applicable, reference to relevant DID must be provided;

v. Description of the approach and methodology used to identify the insurance spares (long lead items); and

vi. Description of methodology used to identify and select the special tools and test equipment required to support Level One and Two maintenance.

b. Supply Documentation. The report must contain the following supply documentation based on the conducted sparing analysis:

i. Supplementary Provisioning Technical Documentation (SPTD). The SPTD must include the requirements indicated in Chapter 3.8 of the Reference.

ii. Provisioning Parts Breakdown List (PPB)

• The PPB must be in accordance with Chapter 3.9 of the Reference, down to





2nd level LRU plus attaching parts. The Contractor must create a report from the PSAR XML database that provides PPB data.

iii. A Recommended Spare Parts List (RSPL). The RSPL must provide a complete list of all required spares, both repairable and consumable. For each item in the RSPL, create a Report from PSAR XML database that provides cataloguing data elements from Chapter 3.9 of the Reference.

iv. An Insurance Spares List. The Insurance Spares List must identify the spares that meet the insurance spares criteria and are recommended to be procured at the time of equipment purchase. Create a Report from PSAR XML database that provides cataloguing data elements from Chapter 3.9 of the Reference.

v. A Special Tools and Test Equipment List (STTE). The STTE must be a complete list of all tools and test and support Equipment required to conduct Level One and Two maintenance. For each item on the list the following must be stated:

• Tool/equipment description, name and unique item identification (UII) if applicable;

• Maintenance action associated with the stated tool/equipment;

• Applicable system, subsystem and equipment;

• Unit price, and

• Required quantity on-board and ashore to support Ship maintenance profile.

vi. Common Tools. The contractor must also identify any common tools that are required to be carried on board.

c. The Report must describe the storeroom analysis conducted and identify the precise on-board location and storage requirements for RSPL and STTE items to be held on-board the vessel.

Consumable Items List, Rev 0





Consumable Items List

ILS-083-030



.

Consumable Items List, Rev 0





1. TITLE

Consumable Items List


ILS-083-030


This DID advises requirement of the consumable items relating to the Equipment.

4. REFERENCES

Attachments: Nil


5. FORMAT





6. CONTENT

a. The following are the Consumable requirements:

i. Description of the Equipment utilizing the Consumable;

ii. SWBS #;

iii. Description of the Consumable;

iv. Name of the Supplier;

v. Supplier's part number;

vi. NATO Stock Number (if applicable) of the consumable;

vii. Indication as to whether item is controlled under an Export Control Jurisdiction and, if so, which jurisdiction;

viii. Predicted quantity / amount required per year; and

ix. Unit price (in original currency).

NATO Codification Data, Rev 0





NATO Codification Data

ILS-083-040



.






1. TITLE

NATO Codification Data


ILS-083-040


As a sponsored Nation in the NATO Codification System (NCS), Canada is required to adhere to the policies and principles as published in the NATO Manual of Codification (ACodP 1). NATO Standardisation Agreement (STANAG) 4177 details a standard process for the acquisition of data in support of codification. This DID details the format, content and preparation instructions for the supply of Codification Data, which will be used by the Purchaser for codification purposes.

4. REFERENCES

Attachments: Nil


5. FORMAT





6. CONTENT

a. Data Required for Each Item of the Equipment Already Codified in the NATO Codification System.

b. For each Equipment and Item of Equipment that is already codified in the NATO Codification System, the Supplier shall list the following information:

i. NSN;

ii. item name;

iii. true manufacturer's name and NCAGE Code; and

iv. Item Reference/Part Number.

c. Data Required for each item of the Equipment NOT Codified in the NATO Codification System. For Equipment or items of the Equipment, SPT that is not codified in the NATO Codification System, the Supplier shall detail the following information:

i. Name and full address of the true manufacturer of the item - a manufacturer is deemed to be that organisation that controls the design specification of the item;

ii. NATO Commercial or Government Entity Code (NCAGE Code) of the true manufacturer (where this is known);

iii. Part / Reference Number assigned to the Item by the true manufacturer to uniquely





identify the Item;

iv. Name and full address of the supplier of the Item;

v. NCAGE Code of the supplier (where this is known);

vi. Supplier's Part/Reference Number for the item;

vii. Name of the item as it appears in the manufacturer's or supplier's documentation;

viii. Proposed NATO Stock Number (if appropriate or known);

ix. Proposed item name if appropriate;

x. The Part / Reference number, manufacturer and name of the next higher assembly;

xi. Documents that provide a comprehensive description of the Item (i.e. the design / procurement specification) and that define the characteristics or features required for form, fit and function (noting that, as appropriate, this information includes performance, dimensional, physical, electrical, mechanical, material, finishing and construction characteristics; and, as applicable, this sub-section might require the provision of design drawings, manuals, tender specifications, design specifications and other information); and

xii. Statement as to whether the particular part identified at section (iii) and (iv) above is fully item identifying (noting that a part number is fully item identifying where, without any further definition, any item of production bearing that part number has the characteristics defined at section (xi) above).

d. The Supplier shall complete a NATO Codification Form for each Equipment or System. One (1) Data Sheet and one (1) Cataloguing Data sheet is supplied as default in the Attachment A to this DID. The Supplier shall create as many additional Data Sheets as required to cover all Items of the Equipment.

e. Changes to Provided Data - If any Data provided to the Purchaser in accordance to this DID is subsequently found by the Supplier to be incorrect or to have changed or requires updating, the Supplier shall immediately provide to the Purchaser an amendment to this Data Item (as required by the SDRL) that details the changed information, appropriately cross-referenced to the manufacturer and part number originally advised.

Packaging, Handling, Storage, and Transportation, Rev 0





Packaging, Handling, Storage, and Transportation

ILS-084-010



.






1. TITLE

Packaging, Handling, Storage, and Transportation


ILS-084-010


The Packaging, Shipping, Storage and Handling (PHS&T) Report shall identify special requirements to packing, shipping, storage and transportation of equipment.

4. REFERENCES

Attachments: Nil


5. FORMAT




6. CONTENT

a. The Packaging, Shipping, Storage and Handling (PHS&T) Report shall identify special requirements that VSY and the purchaser should be aware of pertaining to packing, shipping, storage and transportation of equipment.

b. The PHS&T Report shall identify and describe considerations for the following if applicable: i. Subject to damage from electrostatic discharge; ii. Subject to damage from shock; iii. Subject to degradation from magnetic or electromagnetic radiation; iv. Subject to degradation from ultra-violet light; v. Subject to degradation from freezing; vi. Subject to degradation from humidity; vii. Subject to degradation from heat; viii. That are dangerous goods; ix. That are hazardous material; x. That must be kept in special orientation; xi. That require special external blocking or bracing; xii. That must have an external blocking / locking device engaged; xiii. That emit electromagnetic radiation that could degrade nearby susceptible items; xiv. That require continuous power application;





xv. That can be without power application only for a short period of time; xvi. That should not have protective packaging removed except in a clean room

environment; xvii. That can only be removed from a special storage environment for a short period of

time; xviii. That have any Controlled Goods considerations; xix. Highlight any items that transport or record data but do not require special handling

prior to installation, but may be considered Controlled Goods when dismantled and require special handling and/or demilitarization when removed.

xx. That are classified and must have an escort; and, xxi. That requires a special container; and, xxii. Any special packaging, handling, storage, or transportation requirements beyond

commercial practice. c. As a minimum, the PHS&T report shall contain the following data:

i. Reference to Configuration Item (CI) List in the Technical Data Package (TDP). ii. Item nomenclature and description. iii. Unit packaged sized (length x width x depth (mm)). iv. Unit packaged weight (kg). v. Description of special consideration and mitigation.

d. The PHS&T Report shall include all information required for general understanding and shall define all special terms and acronyms used.

Illustrated Parts Catalogue, Rev 0





Illustrated Parts Catalogue

ILS-086-009



.






1. TITLE

Illustrated Parts Catalogue


ILS-086-009


The DID is to advise the Purchaser of the Illustrated Parts down to the recommended level of maintenance.

4. REFERENCES

Attachments: Nil


5. FORMAT





6. CONTENT

a. For existing Equipment: Illustrated Parts Catalogues (IPC) to Military or Commercial Standards using Class 2 Interactive Electronic Technical Manuals (IETM) format.

b. For modified or new equipment: an updated IPC to Military or Commercial Standards using Class 2 Interactive Electronic Technical Manuals (IETM) format.

c. The following IPC data shall be provided for each Equipment or lower sub-assembly down to line replaceable unit:

i. Equipment designation;

ii. Part number/NATO stock number;

iii. Software issue;

iv. Build state reference;

v. Modification state;

vi. Quantity fitted;

vii. Special characteristics i.e. hazardous, special handling requirements etc.;

viii. General Arrangements;

ix. Functional Diagrams; and

x. Parts List.

Ship System Manuals / Special Purpose Manuals / Class Manuals, Rev 0





Ship System Manuals / Special Purpose Manuals / Class Manuals

ILS-086-010



.






1. TITLE

Ship System Manuals


ILS-086-010


The Ship System / Special Purpose / Class, Manuals describe system functionality, architecture and operating principles. They provide all necessary information aiding in operating and maintaining the systems.

4. REFERENCES

Attachments: Appendix A – Sample Verification Certificate


5. FORMAT




6. CONTENT

a. System Manuals shall be provided in accordance with requirements outlined in the SOW. Each system manual shall provide instructions for the operation and maintenance of the corresponding integrated system on the vessel.

b. The information may be provided in a single or several documents. Information required but not included in Supplier’s standard documentation, may be provided by amending the standard documentation or providing additional separate documentation.

c. Existing OEM Manuals may be utilized to develop System Manuals for integrated systems. OEM Manuals shall be provided unaltered from their original formats, which reflect the as-fitted configuration of the vessel. Class 2 Interactive Electronic Technical Manuals (IETM) preferred.

d. Each System Manual shall include a cover sheet that includes the following information: i. Reference to Master Records Index Configuration Item. ii. Equipment Name. iii. Equipment Description. iv. Supplier’s Name. v. Purchaser Name. vi. Hull Number. vii. Revision Number and Date. viii. Unique Document Number Provided By VSY.





e. A Technical Documentation Verification Certificate shall be provided for each manual to confirm that the information in the documentation conforms to the technical, health and safety requirements to operate and maintain the equipment. See Appendix A for example.

f. The System Manual shall include the following sub-categories: i. System Operating Manual. ii. System Maintenance Manual. iii. System Start-up / Shut-down Manual. iv. All information for equipment with Built in Test equipment (BIT), or Health Monitoring

Device (HMD), or the ability to have a diagnostic tests run, have programmable logistic controllers (PLCs), and variable-speed frequency drives (VFDs). The on-board system, or diagnostic's fault tree, to identify and define the malfunction and proposed corrective action.

g. The System Manual must include the following information as a minimum: i. A description of the system, equipment and components within the system; ii. General theory of operation; iii. Operating instructions including initial adjustment, start up, normal operation, special

procedures, emergency operation and shut down; iv. Troubleshooting data including, possible malfunctions, causes, and effects; v. Fault isolation techniques and solutions (at system level); and vi. A schematic of the system identifying all equipment and components that reflect the

system. h. The System Manuals shall include all information required for general understanding and

shall define all special terms and acronyms used.

Ship System Manual Appendix A – Sample Verification Certificate

Document No: DID ILS 086-020


TECHNICAL DOCUMENTATION VERIFICATION CERTIFICATE

Name of Supplier:

Address of Supplier:

Equipment / System description:

Configuration modification status:

Agreement No:

SWBS #:

Covering Purchase Order #:

DECLARATION

It is hereby declared that the information sets supplied for the above named Equipment, which are listed below have satisfactorily cleared verification, and that:

• Qualified personnel have verified all procedures.

• They are technically accurate.

• They incorporate all safety precautions and warnings that are considered to be necessary for the safe operation and maintenance of the equipment (including all relevant COSHH information).

• Their security classifications are in accordance with the Security Requirements for the above Equipment.

Name of Design Authority:

Signature of Design Authority:

Date of Signing:

Insert Designation of Signatory

Information Details Issue Number Issue date

Repair and Overhaul Manuals, Rev 0





Repair and Overhaul Manuals

ILS-086-020



.






1. TITLE

Repair and Overhaul Manuals


ILS-086-020


The Repair and Overhaul Manuals shall be provided to the purchaser for the purposes repair and overhaul maintenance.

4. REFERENCES

Attachments:


5. FORMAT



b. The format shall not impose any restriction on searching, editing, copying, or printing. c. The information shall be provided in English and in French if available. d. Class 2 Interactive Electronic Technical Manuals (IETM) are preferred (indicate if

publications are Class 2 IETM). e. The information may be provided in a single or several documents. Information required

for this Subcontract but not included in Supplier’s standard documentation may be provided by amending the standard documentation or providing additional separate documentation.

6. CONTENT

a. Existing OEM Repair and Overhaul Manuals shall be provided to the purchaser unaltered from their original formats, which reflect the as-fitted configuration of the vessel.

b. Where repair and overhaul manuals do not exist, the Supplier shall prepare them in the following three (3) stages enabling review and comments to be made by the Purchaser and incorporated into the next stage by the Supplier:

i. Repair and Overhaul Manuals – Synopsis; • Proposed contents list. • Proposed style and format. • Proposed technical publications standards to be applied. • Proposed electronic delivery standard. • Estimated page and diagram counts.

ii. Repair and Overhaul Manual – Draft; • Draft text, figures and drawings. • Binder with front cover details.

iii. Repair and Overhaul Manual – Camera Ready;





• Shall follow the same structure as the draft but will include the purchaser’s comments and instructions.

c. Each Repair and Overhaul Manual shall include a cover sheet that includes the following: i. Reference to Master Records Index Configuration Item. ii. Equipment Name. iii. Equipment Description. iv. Supplier’s Name. v. Purchaser Name. vi. Hull Number. vii. Revision Number and Date. viii. Unique Document Number Provided By VSY.

d. A Technical Documentation Verification Certificate shall be provided for each manual to confirm that the information in the documentation conforms to the technical, health and safety requirements to operate and maintain the equipment. See Appendix A.

e. As a minimum, the Repair and Overhaul Manuals shall include the following: i. General information. ii. General description of the Equipment. iii. Drawings, illustrations, and schematics that represent the Equipment. iv. Wiring diagrams. v. Warnings, cautions, and safety notes (including all statutory obligations). vi. Details of any dangerous or special materials used in construction including details

of any items subject to Control of Substances Hazardous to Health (COSHH). vii. List of symbols and abbreviations used. viii. Operating manuals including normal Start Up / Shut Down manuals. ix. Details of all controls and indicators. x. Commissioning procedures. xi. Safety precautions prior to maintenance. xii. Support and test equipment required for maintenance. xiii. Failure diagnosis information. xiv. Diagnostics instructions. xv. Special Tool and Test Equipment (STTE). xvi. Software Loading and Updating Instructions (where applicable). xvii. Test requirements. xviii. Testing instructions. xix. Calibration requirements.

f. The Repair and Overhaul Manuals shall include all information required for general understanding and shall define all special terms and acronyms used.

Repair and Overhaul Manuals Appendix A – Sample Verification Certificate



TECHNICAL DOCUMENTATION VERIFICATION CERTIFICATE

Name of Supplier:

Address of Supplier:

Equipment / System description:

Configuration modification status:

Agreement No:

SWBS #:

Covering Purchase Order #:

DECLARATION

It is hereby declared that the information sets supplied for the above named Equipment, which are listed below have satisfactorily cleared verification, and that:

• Qualified personnel have verified all procedures.

• They are technically accurate.

• They incorporate all safety precautions and warnings that are considered to be necessary for the safe operation and maintenance of the equipment (including all relevant COSHH information).

• Their security classifications are in accordance with the Security Requirements for the above Equipment.

Name of Design Authority:

Signature of Design Authority:

Date of Signing:

Insert Designation of Signatory:

Information Details Issue Number Issue date

Software Documentation, Rev 0





Software Documentation

ILS-086-040



.

Software Documentation, Rev 0





1. TITLE

Software Documentation


ILS-086-040


The Ship Software Documentation describes the architecture and processes used to develop, validate, test and approve Ship specific software.

4. REFERENCES

Attachments: Nil


5. FORMAT





6. CONTENT

a. The Software Documentation must include the following information as a minimum:

i. Software Requirements Analysis;

ii. Software Architectural Design;

iii. Software Detailed Design;

iv. Software Construction;

v. Software Integration; and

vi. Software Qualification.

b. The documentation must include all information; tables and diagrams required for general understanding and must define all terms and acronyms used.

Training Plan, Rev 0





Training Plan

ILS-088-010



.






1. TITLE

Training Plan


ILS-088-010


The Training Plan (TP) must describe the integrated approach and methodology the Contractor will use for the analysis, design, development and implementation of the Training Program, including support and transition to the in-service life of the vessel.

4. REFERENCES

Attachments: Appendix A – Skill Level Definitions

References: DID ILS 088-020; This DID must be read in conjunction with the appropriate paragraphs of the Statement of Work, Contract Data Requirements List and any references cited in the DID

5. FORMAT




6. CONTENT

a. The TP must describe the integrated approach and methodology the Contractor will use for the analysis, design, development, and implementation of the Training Program as well as the support and transition to the in-service life of the vessel.

b. As a minimum, the TP shall include the following: i. Overview of the Training Program (proposed training and training support activities

to meet all of the training requirements identified by and in response to the SOW); ii. Description of assumptions priorities and constraints on which the training program

is based; iii. Evidence of adherence to the Clients Individual Training and Education System.

The report must describe how the Contractor will adhere to the system, to include a description of the approach and methodology / process used to ensure the development, implementation and quality assurance of the training deliverables required of the SOW;

iv. Evidence of adherence to the Clients policies and directives related to training; v. Contractor’s training Organizational Breakdown Structure (OBS) to show the

authority and responsibility of each organizational unit, including Sub-Contractor organizational responsibilities to the Contractor and to the Purchaser;

vi. Contractor’s Responsibility Assignment Matrix showing all Prime and sub-Contractor task packages and deliverables and inter-relationships with the purchaser. The Responsibility Assignment Matrix must include a matrix of the all proposed deliverables cross-referenced to their approval authority between the Contractor, Sub-Contractors, and purchaser;





vii. A Schedule to identify work task packages, activities and milestones, complete with linkages to the Integrated Master Schedule required to meet the training program;

viii. Description of how the courseware will be integrated, verified and validated prior to delivery;

ix. A description of how the training requirements will be analysed and captured within the experience and competence levels (See Appendix A);

x. Description of how the first serial of all courses of the Initial Cadre Training and Know Your Ship will be validated, evaluated and updated before delivery of second serial;

xi. Proposed client involvement and the approach that will be used by the Contractor to incorporate the Training Development Working Group (TDWG) into all phases of work;

xii. Requirements Traceability Matrix (RTM) – to include an RTM capable of demonstrating that all contractual obligations have been met.

xiii. Confirmation that all rights to reproduce, modify, amend or otherwise change all training materials is conveyed to purchaser on delivery of these materials;

xiv. Description of Security as related to the training development and training delivery; xv. Description of the plans and intentions for Transition to In-Service (including risks,

issues and mitigation actions). c. The TP shall identify the required trainings to be developed based on the requirements of

the Training Needs Analysis (TNA) and Training Media Analysis (TMA) (See DID ILS 088-020). The plan shall address the training topics, intended audiences and qualifications and schedules, as well as resources needed to deliver the training.

d. As a minimum, the TP shall include the following for each training: i. Training name. ii. Purpose of the training. iii. Description of topics. iv. Intended audiences. v. Pre-requisites and/or qualifications. vi. Length of training. vii. Type of training (e.g. on-board, computer, etc.). viii. Required assessments. ix. Schedule and timeline (e.g. pre-delivery or post-delivery). x. Instructor qualifications / training. xi. Media resources required.

e. The Recommended Training Plan shall include all information required for general understanding and shall define all special terms and acronyms used.

Training Management Plan Appendix A – Skill Level Definitions



1. SKILL LEVEL DEFINITIONS

Student’s Skill Level is determined by the Examiner’s identifying at which level a student is engaging in a task or topic area. This reflects the fact that design professionals of all experience levels engage in the same types of activities, but depending on their level of experience, they engage in these activities in different ways. The following descriptions give students a sense of what the different Skill Levels, as well as “beginner,” “intermediate,” and “advanced” mean.

1.1. BEGINNER/SKILL LEVEL

Students, who are performing tasks, working, and learning at a “beginner” level are typically:

a. At an “intern” or “team member” position. b. Not directly managing other team members. c. Reporting directly to a team leader or senior intern. d. Working “day-to-day,” with a set of tasks to complete each day, towards the completion of

the overall project. e. In a “mentee” relationship with their peers, learning from their more experienced peers. f. Beginning to investigate professional licensure. g. Engaged in thinking tasks like listing, summarizing, clarifying, remembering, and

responding. h. Understanding the importance of professionalism as it pertains to timeliness, dress,

communication and responsiveness, and general comportment.

1.2. INTERMEDIATE – LOWER /SKILL LEVEL

Performing tasks, working, and learning at an “intermediate” level are typically:

a. Reporting directly to a senior, and beginning to work directly with associates. b. Directly engaged in design, and beginning to become familiar with several different project

phases. c. Working on tasks that span more than just “day to day,” and are beginning to strategically

plan their own task execution toward the completion of the overall project. d. Participating in meetings as an active support participant; often tasked with taking and

distributing minutes. e. Actively engaged in design culture, professional organizations, exhibitions, and student life

at the BAC. f. Enrolled in the appropriate professional licensing organization and actively pursuing

licensure, where possible. g. Engaged in thinking tasks like carrying out and checking work [such as redlines],

generating new content or design ideas, identifying, integrating, and differentiating. In summary, having a baseline knowledge that allows student to begin making design and process decisions.

h. Deepening their understanding of professionalism to include improving written and verbal communication, beginning to engage with clients, vendors, and other project team members outside of the firm, and improving work/school time management skills.

1.3. INTERMEDIATE – UPPER /SKILL LEVEL 5-6

Students who are performing tasks, working, and learning at an “intermediate” level are typically:

a. At an intern position, but beginning to take more active leadership within teams.

Training Management Plan Appendix A – Skill Level Definitions



b. Beginning to guide other more entry level interns. c. Reporting directly to a team leader or senior intern, and beginning to work directly with

associates or project architects. d. Beginning to mentor less experienced peers, though still actively being mentored by more

senior designers.

1.4. ADVANCED – LOWER / SKILL LEVEL 7-8

Students who are performing tasks, working, and learning at an “advanced” level are typically:

a. At a senior intern or team leader position. b. Actively managing team members. c. Reporting directly to an associate, project architect, or principal. d. Directly engaged in design, and beginning to become even more familiar with several

different project phases; often beginning to specialize in one design phase [CDs, CA, etc.] but has had significant exposure to all phases.

e. Working on tasks that span more than just “day to day,” and are actively, strategically planning their own task execution toward the completion of the overall project in concert with senior project managers/associates.

f. Actively mentoring less experienced peers, though still actively being mentored by more senior designers/principals.

g. Participating in meetings as an active participant or even leader; often tasked with taking and distributing minutes and developing agendas.

h. Actively engaged in design culture, professional organizations, exhibitions, and student life at the BAC.

i. Enrolled in, and making significant progress the appropriate professional licensing organization and actively pursuing licensure, where possible.

j. Engaged in thinking tasks like generating new designs and drawings, actively reflecting on project progress and execution, confronting cultural/intellectual/design biases, and making mature design decisions while weighing all factors.

k. Deepening their understanding of professionalism to include mature written and verbal communication, actively functioning as a firm representative with clients, vendors, and other project team members outside of the firm, and mature work/school time management skills.

1.5. ADVANCED – UPPER / SKILL LEVEL 9-11

Students who are performing tasks, working, and learning at this “advanced” level are typically:

a. Enrolled in, and has their professional licensing almost completed. b. Professionally presents research/work at an organized seminar, conference or workshop. c. Marketing for their employer and bringing in new projects. d. Project managing multiple complex projects. e. Assisting with the search and hiring of full-time and part-time employees for their

employer.

Training Needs and Training Media Analysis, Rev 0





Training Needs and Training Media Analysis

ILS-088-020



.






1. TITLE

Training Needs and Training Media Analysis


ILS-088-020


The Training Needs Analysis (TNA) is used to determine training requirements such as prerequisites, objectives, training times, resources. The resulting report shall identify significant knowledge and expertise gaps between current levels of end-customer training and experience and those required to safely operate the vessel.

The outcome of the TNA is the Training Needs Analysis Report that provides a full analysis of the training and training support requirements as a result of the introduction of the vessel. The TNA includes as a separate annex, the Training Media Analysis (TMA).

The Training Media Analysis (TMA) report must present a detailed and substantiated list of all training media, systems and equipment required to support the vessel training system. The TMA report must include a detailed analysis of existing training devices to determine suitability and sustainability for the vessel training system, as well as a list of proposed devices that will be included in the training system delivery.

4. REFERENCES

Attachments: Nil

References: DID-ILS-088-010; This DID must be read in conjunction with the appropriate paragraphs of the Statement of Work, Contract Data Requirements List and any references cited in the DID

5. FORMAT




6. CONTENT

a. The TNA report provides a full analysis of the training and training support requirements as a result of the introduction of the vessel.

b. The TMA report must present a detailed and substantiated list of all training media, systems and equipment required to support the training system.

c. The TNA/TMA Report must integrate input from all sub-contractors responsible for providing input to the training program and clearly shows how the training gaps or conflicts identified will be addressed.

d. As a minimum, the TNA report shall include the following: i. Executive Summary; ii. Overview of methodology employed in the conduct of the Training Needs Analysis





(TNA)/Training Media Analysis (TMA); iii. Identification of any performance gaps; iv. Description of how performance gaps will be addressed; v. Proposed list of training programs/courses, including description; vi. Proposed list of required Initial Cadre Training serials; vii. Notes section containing any general information aiding with understanding the

document; viii. Integrated TMA report.

e. Recommended outline for developing the TNA. i. Approach and Methodology – Analysis.

• Resource Research and Data Collection Methodology. o Training Target Population; o Prerequisites by Course; o Initial Cadre Training, training requirements by Occupation and Rank; o Familiarization Training and Know Your Ship training;

• Detailed Task Lists by Course. • Difficulty / Importance / Frequency Analysis.

ii. Approach and Methodology – Design. • Instructional Development Plan.

A. Method/Media Analysis overview for each course including opportunities to employ the following (but not limited to these examples): 1) Interactive multimedia Instruction (IMI) levels; 2) Mobile Learning Opportunities; 3) Component Systems Trainer (CST); 4) Part-Task Trainers (PTT); 5) Electronic Performance Support Systems (EPSS); 6) Intelligent Tutoring; 7) Embedded training; and, 8) Synthetic Environment.

B. Instructional Strategy employed: 1) Formal In-house training; 2) On-The-Job (OJT) on-board ship; 3) Trainers; 4) Distance / Distributed training; 5) Other strategies as identified; and, 6) Interaction between courseware and training devices.

C. Learning Network usage: 1) Courseware; and, 2) Storyboard Design.

D. Training device usage. iii. Approach and Methodology – Conduct

• Infrastructure requirements. • Estimate of resources required to deliver training.





• Concept of Training. • Anticipated Schedule of Training. • Student Assessment (i.e. description of methods used to verify that training

requirements were met): A. Formative; and, B. Summative.

• Small Group Trials (SGTs): A. Concept of Operations for SGTs; B. Overview of Plan for SGTs. Plan to ensure all requirements for change

are tracked and addressed prior to Initial Cadre Training. • Initial Cadre Training (ICT):

A. Concept of Operations for ICT; and, B. Overview of Plan for ICT.

• Familiarization Training: A. Overview of course content; B. Overview of Plan for Familiarization Training.

• Know Your Ship (KYS) Training: A. Concept of Operations for KYS; and, B. Overview of Plan for KYS.

• Train the Trainer Program: A. Orientation to Devices; and, B. Orientation to Courseware.

f. The TMA Report must outline any recommendation for the use of existing media assets or the acquisition of new training devices and include: (a) lifecycle assessment of the assets/devices; (b) overview of the proposed device, (c) how each device will be employed in the training program outlined in the TNA and (d) detailed cost benefit analysis.

g. Recommended outline for developing the TMA. i. New technology enabled learning. ii. Impact on existing trainers:

• Identification of trainers that can be re-purposed for the training system with an analysis of trainer capacity to accommodate the addition training throughput;

• Functional software and hardware changes required to trainers to accommodate training requirements;

• Changes that may be required to infrastructure as a result of training device modifications; and,

• Requirement for In-Service Support for life of vessel including maintenance and staffing.

iii. New Training Simulation / Device / Media Requirements: • Overview of proposed training devices; • Overview of how devices will be employed; • Functional specifications for the proposed training devices; • Identification of training device shortfalls; • Impact on Infrastructure;





• Cost benefit analysis; and, • In-service support recommendations.

iv. Synthetic Environment Connectivity: • For each simulator, assessment of whether connectivity would yield cost

effective training benefits; • Indication of which simulators should be connected to other devices; and, • Indication of what types of information should be shared by connected

simulators. h. The TNA/TMA Report shall include all information required for general understanding and

shall define all special terms and acronyms used.

Qualification Standard and Plans (QSP), Rev 0





Qualification Standard and Plans (QSP)

ILS-088-030



.

Qualification Standard and Plans (QSP), Rev 0





1. TITLE

Qualification Standard and Plans (QSP)


ILS-088-030


The Ship Class Training Package must include unique Qualification Standard and Plans (QSP) for each identified course in the Canada-approved TNA report. The QSPs must be delivered in accordance with the RCN QSP Template and identify the skills and knowledge expected of the student on completion of the course. The QSPs must be delivered in accordance with the RCN QSP Template and identify the skills and knowledge expected of the student on completion of the course, and how these will be assessed. The QSP Report must outline the course content, structure and testing methods to impart this knowledge to the student, whether the student is Canada personnel or Support personnel with the In-Service Support Contract (ISSC).

4. REFERENCES

Attachments: Nil


5. FORMAT





6. CONTENT

a. The QSP Report must contain all the QSPs identified in the Canada-approved TNA/TMA. The Contractor must consider integration and modularization of the courseware in each QSP to ensure maximum efficiency and effectiveness of training.

Training Development Report, Rev 0





Training Development Report

ILS-088-040



.






1. TITLE

Training Development Report


ILS-088-040


The Training Development Report shall outline the detailed training manuals as well as the required media resources to deliver the trainings.

4. REFERENCES

Attachments: Nil

References: DID ILS 081-030; DID ILS 086-020; DID ILS 086-030; DID ILS 088-010; DID ILS 088-020; This DID must be read in conjunction with the appropriate paragraphs of the Statement of Work, Contract Data Requirements List and any references cited in the DID

5. FORMAT




6. CONTENT

a. The Training Development Report must provide sufficient detail for the Customer to determine which of the following Crew and Technical Training is required:

i. Available OEM courses; and

ii. Available or to be developed System Level courses.

b. For the purpose of the Training Development Report, System Level course refers to all non-OEM equipment specific or special purpose training unique to the vessel configuration. System in this context refers to major functional areas assigned to the Single System Integrators (SSl’s), such as:

i. Propulsion;

ii. Power;

iii. Ship Control and Monitoring System (SCMS);

iv. Heating, Ventilation, and Air Conditioning (HVAC);

v. Hydraulic Power, Winches, Cranes and Mission Handling Systems; and,

vi. Communications, Navigation and Bridge Systems.

c. The Training Development Report must identify all recommended existing OEM courses along with all associated costs, including delivery.

d. The Training Development Report must identify recommended or proposed System Level





courses and all associated costs for the development of related course material and the delivery of the training.

e. The Supplier must consider details of the proposed structure of the training as well as how and when, training should be delivered as listed below. The Training Development Report must include a course syllabus (if available), excluding training materials. The list of System Level Training courses must be developed with the assistance and input of the Customer.

f. Technical Training courses listed in the Training Development Report must cover all equipment and systems listed in the Vessel Manuals developed for DID ILS 086-020, as fitted on-board the Vessel.

g. The Training Development Report must be sufficient to prepare the crew and shore-side support staff to maintain the equipment and systems, in accordance with OEM recommendations and the Vessel Maintenance Plan developed in accordance with DID ILS 081-030. The Supplier must include in the Training Development Report the following data elements related to the existing OEM courses:

a. The Training Development Report shall include the following for each training requirement:

i. Training Selection Criteria.

• Mandatory (yes or no).

• Type of Training (In-Person, Computer, etc.).

• Maximum Class Size.

• Special Media Requirements.

• Training Pre-requisites.

• Delivery Period (Pre / Post Acceptance).

• Post-Training Assessment Requirements.

ii. Training topics (Subject / Topic / System).

iii. Course Outline / Syllabus.

iv. System or equipment on the vessel.

v. Training Supplier / OEM.

vi. Training location(s) (e.g. onboard vessel or at Supplier's facility).

vii. Training Course duration.

viii. Intended audience.

ix. Identification of the instructor(s).

x. Cost to attend or deliver training.

xi. Cost to develop Lesson Plan(s) for each training topic, if one does not exist; and,

xii. Cost to develop Trainee Guide for each topic if one does not exist.

h. The Trainee Guide must include, as a minimum:

i. Applicable sections of approved technical manuals.

ii. OFSV Class Manual.

iii. Half-size ship construction / equipment drawings.

iv. Narrative descriptions, diagrams, sketches, charts, graphs, pictures, and other





material to support the Information presented in the course.

v. Ship orientation.

vi. Start-up, operation, shutdown procedures; and,

vii. Basic daily maintenance and troubleshooting for all equipment and systems.

7. DELIVERABLES

a. One (1) electronic copy of the Training Development Report must be provided for review and acceptance in accordance with the SOW.

8. RECOMMENDED CREW TRAINING

a. Familiarization Training - The Supplier must provide members of the Vessel Crew, as grouped below and identified by the Customer, with an understanding of the operation of specific equipment and systems fitted onboard the Vessel.

b. The Emergency Familiarization Training must cover, at minimum, the location and operation of the following items:

i. Fire-fighting equipment and arrangement including emergency operation;

ii. Life-saving equipment including emergency operation;

iii. Abandon ship procedures (lifeboat and life rafts);

iv. Watertight door operation and locations;

v. Steering system including emergency operation;

vi. Emergency telegraph procedures;

vii. Propulsion and machinery control systems emergency operation;

viii. Damage control equipment locations;

ix. First Aid equipment locations; and

x. Environmental protection equipment and system locations and operation.

c. The General Familiarization Training must cover, at minimum, the location and operation of the following items:

i. Key design features, unique to this vessel, which may impact operations;

ii. Key safety features;

iii. General safety and security, including confined spaces locations (not including confined space entry training);

iv. Science Program fitted equipment and systems operation, including drop keel and fishing gear;

v. Acoustic enclosures and treatments locations; and

vi. Any unique operating procedures as appropriate.

d. The Deck Department Familiarization Training must cover, at minimum, the location and operation of the following items:

i. Loading conditions which may affect stability, including tank arrangement;

ii. Ship specific propulsion (including thrusters) operation, constraints and recommended practices;

iii. Integrated bridge control and navigation work stations, including station keeping;





iv. Integrated bridge alarm system (including fire detection panel);

v. Integrated communication systems and equipment;

vi. Integrated scientific information systems and equipment;

vii. Deck equipment including anchor windlass, cranes, davits and winches.

e. The Engine Room Department Familiarization Training must cover, at minimum, the location and operation of the following items:

i. Ship specific propulsion (including thrusters) constraints and recommended practices;

ii. Review of sea trial data for all machinery, equipment and systems;

iii. Procedures for starting the machinery, equipment and systems on board vessel from a dead ship condition to full away condition. This must include the list of the normally expected parameter range for all relevant

iv. machinery, equipment and systems;

v. Stability control systems and equipment including tank arrangement;

vi. Propulsion and machinery control systems;

vii. Electrical generation and distribution systems including power management and emergency operation;

viii. Hydraulic systems;

ix. Compressed air systems;

x. MCR alarm system including fire detection panel;

xi. Fueling and ballasting systems and equipment;

xii. Water and waste management systems and equipment;

xiii. Deck equipment including anchor windlass, cranes, davits and winches;

xiv. HVAC equipment and systems; and

xv. Refrigeration Systems.

f. Technical Training - Technical training is a package delivered by the Supplier to the Customer through the ILS Authority. The Supplier must provide members of the Vessel crew and shore based in-service support personnel, with an understanding of specific equipment and systems fitted onboard the Vessel. The training topics must include, at a minimum the systems listed in the Class Manual with particular focus on, the following:

i. Main engines;

ii. Generators and power distribution systems;

iii. Propulsion system including motor;

iv. Steering systems;

v. Alarm & Monitoring systems;

vi. Lifeboat and life-raft davits;

vii. Safety equipment systems including Arc-flash training;

viii. Use of special tools and instruments;

ix. Navigation equipment;





x. Communication equipment; and

xi. Science systems

g. The Customer will provide the Supplier with information related to the experience, certification, and the knowledge level of the personnel that will attend the technical training.

b. The Training Development Report shall include all information required for general understanding and shall define all special terms and acronyms used.

Courseware Style Guide, Rev 0





Courseware Style Guide

ILS-088-050



.






1. TITLE

Courseware Style Guide


ILS-088-050


The Vessel Class Training Package must include unique Qualification Standard and Plans (QSP) for each identified course in the Canada-approved TNA report. The QSPs must be delivered in accordance with the RCN QSP Template and identify the skills and knowledge expected of the student on completion of the course. The QSPs must be delivered in accordance with the RCN QSP Template and identify the skills and knowledge expected of the student on completion of the course, and how these will be assessed. The QSP Report must outline the course content, structure and testing methods to impart this knowledge to the student, whether the student is Canada personnel or Support personnel with the In-Service Support Contract (ISSC).

4. REFERENCES

Attachments: Nil


5. FORMAT





6. CONTENT

a. The contractor must develop a Ship Courseware Style Guide for approval by CANADA, to set a standard for the development of all JSS Class courseware.

b. The Vessel Courseware Style Guide must be based on industry best practices, follow the guiding principles outlined in CFITES, and address the following, as a minimum:

i. Courseware writing and development standards;

• Writing standards and style;

• Text formatting standards;

• Paragraph standards;

• Sentence standards;

• Grammatical Standards;

• Technical standards; and

• Audio text narrative standards for self-paced lessons, if required;





ii. Media development standards;

iii. Metadata;

iv. Evaluation and/or assessment standards;

v. Instructional design best practices;

vi. Specifications for storyboards; and

vii. References.

c. The report must include a description of how the Contractor intends to meet the current Canadian-specific requirements of the Shareable Content Object Reference Model (SCORM) 2004 3rd edition requirements.

Master Records Index, Rev 0





Master Records Index

ILS-811-010



.






1. TITLE

Master Records Index


ILS-811-010


The Master Record Index – ILS (MRI-ILS) defines the standard of build of the Equipment. The index comprises a key to the approved drawings and associated records and lists all design changes introduced by amendments and modifications.

The MRI-ILS is used by the Supplier to define the Equipment. The MRI-ILS is used by the Purchaser to ensure that the Equipment meets its build standard.

4. REFERENCES

Attachments: Nil


5. FORMAT





6. CONTENT

a. MRI – ILS – Contents - As a minimum the MRI shall consist of the following:

i. Cover sheet;

ii. Index of amendments and modifications;

iii. Index of all Configuration Items (CIs);

iv. Index of components or Items of the Equipment;

v. Indentured drawing List;

vi. Index of Configuration Documentation;

vii. Index of Technical Manuals;

viii. Index of Class I (Major) Engineering Change Proposals;

ix. Index of Class II (Minor) Engineering Change Proposals;

x. Index of Requests for Deviations; and

xi. Index of Ancillary Equipment.

b. Index of Amendments and Modifications - The Index of Amendments and Modifications





shall list all amendments and modifications introduced that effect the Equipment design.

c. Index of Configuration Items - The Index of CIs shall list, in hierarchical form, all the CIs constituting the Equipment. The Index of CIs shall be developed from data from the Configuration Item List. For each CI, the Index of Configuration Items shall detail the following information:

i. CI Reference Number. This field shall detail the reference number allocated to the CI by the Supplier. This number is to relate the CI to higher level assembly to which it belongs in a hierarchical manner to system level;

ii. CI Nomenclature. This field shall detail the name allocated to the CI;

iii. CI Type. This field shall detail whether the CI is a Hardware Configuration Item (HWCI) or a Computer Software Configuration Item (CSCI);

iv. HWCI. This field is applicable to CSCIs only and shall detail the HWCI the CSCI is resident in;

• Subsystem. This field shall detail the CI’s parent Subsystem;

• System. This field shall detail the CI’s parent System; and

• Design Organisation. This field shall detail the organisation responsible for design of the CI.

v. The Index of Configuration Items shall be sorted in Equipment and then Subsystem order.

vi. Headings shall be positioned in the Index of Configuration Items to identify where each System and Subsystem begin.

d. Index of Components - The Index of Components (IOC) shall detail, in hierarchal form, the physical build structure of the Equipment and shall go down to and include piece parts. The IOC shall be developed from Data contained in the Logistics Support Analysis Record (LSAR). For each Item in the IOC, the IOC shall detail the following information:

i. Indenture Level. This field shall document the indenture level of the Item. The Equipment is indenture level 1;

ii. Part Number. This field shall document the Item’s Part Number;

iii. Variant Number. When more than one variant of an Item has been used in the construction of the Equipment, the Part Number of each variant is to be given a variant number (e.g. 1, 2, 3). This field shall default to one (1) when only one variant of an Item has been used;

iv. Part Number Status. This field shall contain the status of the Part Number (e.g. PROPOSED, CURRENT, OBSOLETE and HISTORICAL);

v. Quantity Fitted. This field shall document the quantity of the Item fitted to the Item’s next higher assembly;

vi. Drawing Number. This field shall document the Drawing Number of the Item; and

vii. Nomenclature. This field shall document the Item’s nomenclature.

viii. The IOC shall be sorted in Equipment, then Subsystem, then CI order.

ix. Headings shall be positioned in the IOC to identify where each System, Subsystem and CI begin.

e. Indentured Drawing List - The Indentured Drawing List (IDL) shall list, in hierarchal form, all





the drawings constituting the Equipment design, including Sub-subcontractor drawings as per Annex D (Required). For each drawing, the IDL shall detail the following information:

i. Indenture Level. This field shall document the indenture level of the drawing;

ii. Drawing Number. This field shall document the drawing number;

iii. Revision Letter. This field shall document the latest revision letter of the drawing applicable to the Equipment;

iv. Drawing Title. This field shall document the title of the drawing;

v. Drawing Type. This field shall document the drawing type which the drawing belongs to e.g. Detail Assembly Drawing, Specification Control Drawing, Wiring List, etc.;

vi. Drawing Size. This field shall document the sheet size of the drawing e.g. A2, A3, etc.; and

vii. Number of Sheets. This field shall document the number of sheets making up the drawing.

f. Index of Configuration Documentation - The Index of Configuration Documentation (IOCD) shall list the Configuration Documentation describing the functional, allocated and product baselines for the Equipment (drawings are to be excluded from the IOCD as they have been listed elsewhere). For each document, the IOCD shall detail the following information:

i. CI Reference Number. This field shall detail the CI Reference Number the Document is applicable to;

ii. CI Nomenclature. This field shall detail the CI's nomenclature;

iii. Document Reference Number. This field shall detail the Document's Reference Number;

iv. Document Revision Number. This field shall detail the Revision Number of the Document; and

v. Document Type. This field shall detail the type of document the Document belongs to (e.g. Development Specification, Test Requirement Document, Software Requirements Specification etc.).

The following types of Configuration Documentation, as a minimum, shall be included in the list:

i. System Specifications;

ii. Development Specifications;

iii. Product Specifications;

iv. Interface Control Documents;

v. Software Requirements Specifications;

vi. Interface Requirements Specifications;

vii. Software Product Specifications;

viii. Software Version Descriptions;

ix. Software Design Descriptions;





x. Interface Design Descriptions;

xi. Database Design Descriptions;

xii. Material Specifications; and

xiii. Process Specifications.

The IOCD shall be divided into two (2) sections. Section 1 shall be sorted in System then Subsystem then CI order. Section 2 shall be sorted in Document Type then Document Reference Number order. Headings shall be positioned in Section 1 to indicate where each System, Subsystem and CI begins. Headings shall be positioned in Section 2 to indicate where each Document Type begins.

g. Index of Technical Manuals - The Index of Technical Manuals (IOTM) shall list the technical manuals developed under the Contract. For each Technical Manual, the IOTM shall detail the following information:

i. Supplier Reference Number. This field shall detail the Supplier Reference Number for the Technical Manual;

ii. Title. This field shall detail the title of the Technical Manual; and

iii. Related CIs. This field shall detail the Configuration Items the Technical Manual is applicable to.

The IOTM shall be divided into two (2) sections. Section 1 shall be sorted in System then Subsystem then CI order. Section 2 shall be sorted in Supplier Reference Number order. Headings shall be positioned in Section 1 to indicate where each System, Subsystem and CI begins. No headings shall be positioned in Section 2.

h. Index of Class I (Major) Engineering Change Proposals - The Index of Class I (Major) Engineering Change Proposals (ECPs) shall document all Class I ECPs raised against the Equipment and its constituent Items during the Subcontract, including those raised by the Sub-subcontractors. For each ECP, the Index of Class I ECPs shall detail the following information:

i. ECP Number. This field shall document the unique ECP identification number supplied by the Purchaser;

ii. ECP Revision Number. This field shall document the revision level of the ECP i.e. R1 or R2;

iii. ECP Justification Code. This field is as defined in MIL-HDBK-61A;

iv. ECP Title. This field shall document the title of the ECP;

v. Date Raised. This field shall document the date the ECP was raised;

vi. ECP Status. This field shall document the status of the ECP;

vii. Status Date. This field shall document the date the status of the ECP changed;

viii. CCB Decision. This field shall document the decision made by the Configuration Control Board (CCB) for approval to proceed;

ix. Decision Date. This field shall document the date of the CCB decision;

x. Impacted CIs. This field shall document the CIs impacted by the ECP;

xi. Affected Part Numbers. This field shall document the CI Part No variants impacted by the ECP; and

xii. New Part Numbers. This field shall document the new CI Part No variants





introduced as a result of the ECP. Where the new Part No is a re-identification of an existing Part No this relationship shall be clearly shown.

i. Index of Minor Engineering Change Proposals - The Index of Class II (Minor) Engineering Change Proposals (ECPs) shall document all Class II ECPs raised against the System and its constituent Items during the Contract, including those raised by the Sub-subcontractors. For each ECP, the Index of Minor ECPs shall detail the following information:

i. ECP Number. This field shall document the unique ECP identification number supplied by the Purchaser;

ii. ECP Revision Letter. This field shall document the revision level of the ECP i.e. R1 or R2;

iii. ECP Title. This field shall document the title or a brief description of the ECP;

iv. Date Raised. This field shall document the date the ECP was raised;

v. ECP Status. This field shall document the status of the ECP;

vi. Approval Authority. This field shall document who approved or rejected the ECP;

vii. Decision Date. This field shall document the date the approval authority approved or rejected the ECP;

viii. Impacted CI. This field shall document the CI impacted by the ECP; and

ix. CI Part Numbers. This field shall document the CI Part No variants impacted by the ECP.

j. Index of Requests for Deviation - The Index of Requests for Deviation (RFDs) shall document all RFDs raised against the Equipment and its constituent Items during the Subcontract, including those raised by the Sub-subcontractors. For each RFD, the Index of RFDs shall detail the following information:

i. RFD Reference Number. This field shall document the unique RFD identification number;

ii. RFD Title/Description. This field shall document the title or provide a brief description of the RFD;

iii. RFD Class. This field shall document the class of the RFD i.e. Critical, Major or Minor;

iv. Date Raised. This field shall document the date the RFD was raised;

v. RFD Status. This field shall document the status of the RFD;

vi. Approval Authority. This field shall document who approved or rejected the RFD;

vii. Decision Date. This field shall document the date the approval authority approved or rejected the RFD;

viii. Impacted CI. This field shall document the CI impacted by the RFD;

ix. CI Part Number. This field shall document the CI Part Number variant impacted by the RFD;

x. Affected Part Number. This field shall document the Part Number of the Item subject to the RFD;

xi. Affected Serial Numbers. This field shall document the Serial Number(s) of the Item subject to the RFD;





xii. MMI Part Number. If the affected Item is not a Maintenance Managed Item (MMI) and does not build directly to the CI then this field shall document the Part Number of the higher level MMI; and

xiii. MMI Serial Number(s). This field shall document the Serial Number(s) of the MMI specified at subparagraph (l).

The Index of RFDs shall be divided into three (3) sections. Section 1 shall list RFDs classified as Critical, Section 2 shall list RFDs classified as Major and Section 3 shall list RFDs classified as Minor. Each Section shall be further subdivided into two (2) Subsections. Subsection 1 shall be sorted in RFD Reference No order. Subsection 2 shall be sorted in System then Subsystem then CI order. Headings shall be positioned in Subsection 2 to indicate where each System, Subsystem and CI begins. No headings shall be positioned in Subsection (1).

k. Index of Ancillary Equipment - The Index of Ancillary Equipment (IAE) shall list the support Equipment required to support the maintenance/operation of the Equipment and its constituent Items. NOTE: Support Equipment includes, but shall not be limited to, Automatic Test Equipment and STTE. For each piece of Support Equipment, the IAE shall detail the following information:

i. (a) Support Equipment Designation. This field shall document the designation of the support Equipment;

ii. (b) Nomenclature. This field shall document the nomenclature of the support Equipment;

iii. (c) Support Equipment Type. This field shall document the support equipment type the Support Equipment belongs to (for example Ground Support Equipment, Automatic Test Equipment, Special to Type Tooling, etc.);

iv. (d) Supported CI(s). This field shall document the CI(s) supported by the Support Equipment;

v. (e) CI Part Number Variants. This field shall document the CI Part Number variant(s) supported by the Support Equipment; and

vi. (f) Affected Part Numbers. If the Item(s) supported by the support Equipment is (are) below the CI level then this field shall document the Part Number(s) of the Item(s) supported by the Support Equipment.

The IAE shall be divided into two (2) Sections. Section 1 shall be sorted by Support Equipment Type then by Support Equipment Designation. Section 2 shall be sorted by Supported CI then Support Equipment Type then Support Equipment Designation order. Headings shall be positioned in Section 1 to indicate where each Support Equipment Type begins. Headings shall be positioned in Section 2 to indicate where each CI begins.

Quality Plan, Rev 0

Document #:VSY-A08.22-0084 Agreement #: N/A




Quality Plan

QA201



Quality Plan, Rev 0




Quality Plan QA201

Purpose

The purpose of the Quality Plan (QP) is to detail the Supplier’s specific quality arrangements, practices, processes, procedures, resources and activities pertaining to the development, design, manufacture, testing and release of the Work performed under the Subcontract. The QP shall, as much as possible and consistent with the requirements set out below, utilise the same management tools and methods already in use by the Supplier to manage and monitor its own business. The QP will be referenced by the Purchaser when conducting Supplier audits.

References



This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 5 (Quality Assurance) of the SOW.

Format and Content

The QP shall include as a minimum:

1 title page;

2 contents and amendment record

3 introduction, Subcontract description, definitions, abbreviations, etc…;

4 purpose and scope of QP;

5 details of the Supplier’s quality management system and scope of ISO 9001 registration;

6 details of the organisation, roles and responsibilities and the interfaces relevant to this Subcontract lists of applicable standards, specifications, QA/QC documentation and certification records relevant to the Subcontract;

7 quality risks associated with the SOW and Supplier’s method of operation;

8 a list of all processes and procedures relevant to the Subcontract and available during supplier audits;

9 the specific arrangements for providing assurance of the satisfactory quality of Deliverables from the Supplier and the Supplier’s lower tier suppliers and the measures to be adopted to ensure compliance. Include (or make reference to) all major lower tier suppliers, scope of supply, activities, and show the Supplier’s proposed involvement;

10 specific arrangements for satisfying Classification Society material certification and traceability requirements relevant to the Subcontract;

11 procedures for configuration management and change control processes;

Quality Plan, Rev 0




12 reference to measurement, analysis and improvement activities including a schedule of internal audits specific to the Subcontract and its requirements;

13 procedures for processing non-conformance reports and concession requests;

14 in addition for any Software supply, the Supplier shall comply with the requirements of Part 3 (Engineering) of the SOW and include a Software Quality Plan;

15 contact details for the Supplier’s Independent QA/QC representative;

16 details of the Inspection and Test Plan including all Hold Points and Witness points for the Purchaser and Classification Society; and

17 in the event that the Work includes fabrication of part or parts of a Ship, the QP shall include the following additional information:

(a) scope of Classification Society activities;

(b) list of Dimensional control procedures;

(c) list of Welding Procedure, Procedure Qualification Records and Welder Qualification records; and

(d) list of Applicable Non Destructive Test procedures.

Request for Waiver, Deviation or Equivalent Item, Rev 0

Document #: VSY-A08.22-0085 Agreement #: N/A




Request for Waiver, Deviation or Equivalent Item

QA202







Request for Waiver, Deviation or Equivalent Item QA202

Purpose

The Request for Waiver Deviation or Equivalent Item is the method for the Supplier to request acceptance of a non-conforming Deliverable.

References




Format and Content

The Supplier shall complete and deliver the Attached Request for Waiver Deviation or Equivalent Item.

Inspection and Test Plan, Rev 0

Document #: VSY-A08.22-0086

Agreement #: N/A




Inspection and Test Plan

QA203





Agreement #: N/A



Inspection and Test Plan QA203

Purpose

The Inspection and Test Plan (ITP) is intended to layout the plan for manufacture, testing/progressive acceptance events to meet the Requirements of the Subcontracts.

The purpose of the ITP is to detail the Supplier’s specific quality control arrangements for the product realisation from material sub-orders, manufacture, inspection, test, integration and Final Acceptance of the Equipment, SPT and Spares.

The ITP shall, as much as possible and consistent with the requirements set out below, utilise the same management tools and methods already in use by the Supplier to manage and monitor its own business.

The ITP will be required for equipment, sub-system & system and the ITP may be split as required.

References




Format and Content

The ITP shall comply with the requirements of the Subcontract and shall include as a minimum (Attachment A is an example of how this can be achieved):

1. equipment description(/sub-system or system, as applicable) , amendment record and distribution etc.;

2. subcontract description, definitions, legend for abbreviations etc.;

3. purpose and scope of ITP;

4. sequential stages and activities including manufacture, testing, acceptance and release;

5. Progressive Acceptance Events / Provisional and Final Acceptance criteria;

6. the characteristic that will be checked/inspected/tested (e.g. dimensions, welds);

7. the document that requires this characteristic to be checked (usually it is the contract or similar document-specification);

8. the document that according to, this characteristic will be inspected/tested (usually a standard or a statutory requirement);

9. the kind of inspection that needs to be performed (visual inspection, document approval etc.);

10. the frequency that this inspection needs to be performed (e.g. radiographic testing 5% of all welds);



Agreement #: N/A



11. the objective criteria/tolerance parameters that will determine if the inspection/test for that characteristic has passed or not;

12. Verification Records: the kind of document that will be prepared and saved as a record of pass or failure (usually a certificate, signed inspection records, a testing machine print-out, a photo, etc.);

13. if this record needs to be a deliverable, meaning that it needs to be kept and handed over to the Purchaser at the end of the Project as part of the Supplier’s Technical Data Package;

14. the responsibilities of every party involved (Supplier, Purchaser, Canada, Classification Society, etc.) - codified system of responsibilities as following:

H= Hold Point (the party has to perform this check and it needs to be successful in order to proceed to the next stage of the construction);

W= Witness Point (the party e.g. Canada has to be informed that a test is being performed but its presence and signature is not obligatory to move on to the next stage);

R= Review Point (the party has only to review the record/document that the check has been done and it passed).



Agreement #: N/A



ATTACHMENT A

(Example ITP)



Agreement #: N/A



Certificate of Conformance, Rev 0





Certificate of Conformance

QA204







Certificate of Conformance QA204

Purpose

The Certificate of Conformity (CoC) is intended to assure the Purchaser that the Work undertaken by the Supplier and the Supplier’s lower tier suppliers complies with the requirements of the Subcontract.

References




Format and Content

The Certificate of Conformity shall include as a minimum:

1 Description of the Equipment;

2 SWBS #;

3 Agreement #:

4 Covering Purchase Order #

5 Purchaser’s part numbers;

6 Supplier’s part numbers;

7 NATO Stock Number (if codified);

8 issue and modification status of each Equipment, SPT and Spare SWBS #;

9 identification of any outstanding Defects, deficiencies, non-conformances or equivalent terminology;

10 statement of any concessions or production permits;

11 where applicable, a statement of calibration status supported with a valid Certificate of Calibration showing date of calibration and calibration period [or when recalibration is required];

12 items of the Equipment or Spares subject to shelf life the expiry date/dates must be stated;

13 lifting load handling data must be included where applicable;





14 The following statement:

“We hereby certify that the Equipment, SPT or Spares detailed herein have been inspected, tested and conform in all respects with the requirement of the Subcontract. The quality control and assurance arrangements adopted in respect of the items have accorded with the conditions of our ISO 9001 registration.”

15 The Certificate of Conformity shall be signed by the Supplier’s Quality Manager or his nominated representative.

Hold, Witness and Review Advice, Rev 0





Hold, Witness and Review Advice

QA205



Hold, Witness and Review Advice, Rev 0




Hold, Witness and Review Advice QA205

Purpose

The Hold, Witness and Review Advice is intended to make the Quality Assurance Authority aware of any upcoming hold, witness, review and Acceptance Event agreed in the Inspection and Test Plan (see SDRL QA203 and DID QA203) that the Purchaser may wish to attend or witness.

References




Format and Content

1 The Supplier’s Hold, Witness and Review Advice shall be prepared in the following format and contain the following information:

Description of Hold, Witness, Review or Acceptance Event

Location Date

[* insert description] [* insert location where the hold, witness, Review or Acceptance Event will take place]

[* insert DDMMMYY]

Etc…

2 A separate Hold, Witness and Review Advice shall be submitted for each Acceptance Event.

Ready for Inspection Advice, Rev 0 Document #: VSY-A08.22-0192 Agreement #: [* insert Agreement #]




Ready for Inspection Advice

QA206



Ready for Inspection Advice, Rev 0 Document #: VSY-A08.22-0192 Agreement #: [* insert Agreement #]



Ready for Inspection Advice QA206

Purpose

The purpose of this document is to provide instructions to Suppliers on the standards and contents of their Ready for Inspection Advice to meet the Purchaser’s requirements.

References

This DID must be read in conjunction with Schedule A (General Conditions), Part 5 (QA) of the SOW, Part 12 (LOG) of the SOW, Supplier’s Quality Plan and ITP.


This DID shall comply with the general format, content and preparation instructions set out in Part 1 (INTRO) and Part 5 (QA) of the SOW.

Format and Content

The Ready for Inspection Advice shall be issued in Supplier’s own format.

The Ready for Inspection Advice shall contain the following information at a minimum:

(a) Project and Subcontract Reference (b) Date and time of inspection activities; (c) Anticipated duration; (d) Location; (e) ITP activity reference(s); (f) List of completed items to be inspected; (g) Details of principal contact for inspection activity (email, phone); (h) Any special site requirements such as PPEs; (i) Supply As-built drawings for equipment to be inspected; and (j) Purchaser and third party acknowledgment request (Attendance/attendance waiver/comments). (k) Supplier shall provide any additional information necessary for the inspection of the product(s).


(a) Where verified copies are required they will be stamped as such in red and will include Supplier’s name/logo and verifier’s name.

(b) The Ready for Inspection Advice shall be issued with a reference number e.g. RFI-001.

Manufacturing Completions Records, Rev 0 Document #: VSY-A08.22-0193 Agreement #: [* insert Agreement #]




Manufacturing Completions Records

QA207






Manufacturing Completions Records QA207

Purpose

The purpose of this document is to provide instructions to Suppliers on the standards and contents of their Manufacturing Completions Records to meet the Purchaser’s requirements.

References

This DID must be read in conjunction with Schedule A (General Conditions), Part 5 (QA) of the SOW, Part 12 (LOG) of the SOW, Supplier’s Quality Plan and ITP.


This DID shall comply with the general format, content and preparation instructions set out in Part 1 (INTRO) and Part 5 (QA) of the SOW.

Format and Content

The Supplier may propose its own standard format and content provided prior agreement to do so has been obtained from the Purchaser’s Quality Assurance Authority.

The Manufacturing Completions Records shall be indexed in such a way to enable immediate retrieval of its contents and would typically contain:

1. Title Page detailing Material/Equipment description, Subcontract Number, Supplier’s contact name and telephone number;

2. Full and detailed packing list;

3. Acceptance Checklist;

4. Purchaser Inspection Release Note;

5. Third party release notes e.g Class (where appropriate);

6. Punch-list (Outstanding work punch-lists when Purchaser approves incomplete items for shipment. Agreed dates for

completion of outstanding work to be noted on punch-list);

7. Dimensional Survey

8. Weight certificate

9. Certificate of conformity

10. Type approval Certification;

11. Lifting/Proof Load/ Test Certificates;

12. Material Certificates for site welded interface items see note a) below;

13. As-built drawings;

14. Photos of completed items; and

15. Software Release Note (where appropriate).

NOTES:

1. All certificates included which are unique to the material/equipment supplied are to be annotated with Agreement number and item number and Material Reference Number.

2. Some of the documents listed above may change depending some the system type e.g. Mechanical, Electrical, etc. The index shall be agreed with Purchaser before completion and submission of the Manufacturing Completions Records.





1. Where verified copies are required they will be stamped as such in red and will include Supplier’s name/logo and verifier’s name.

2. The Manufacturing Completions Record shall be immediately prepared following final inspection and issuance of the Inspection Release Note.

3. The completed Manufacturing Completions Record shall be submitted to the Purchaser for approval prior to despatch.

4. Following the approval of the Manufacturing Completions Record, the call-Off Order shall be issued to Supplier, to authorize dispatch of completed items when required.

Manufacturing Records Book Index, Rev 0 Document #: VSY-A08.22-0194 Agreement #: [* insert Agreement #]




Manufacturing Records Book Index

QA208



Manufacturing Records Book Index, Rev 0 Document #: VSY-A08.22-0194 Agreement #: [* insert Agreement #]



Manufacturing Records Book Index QA208

Purpose

The purpose of this document is to index all the necessary data to verify the compliance of the Work in accordance with the Subcontract and Supplier’s legal requirements for product liability to permit the issue of a Certificate of Conformity.

It shall, as much as possible and consistent with the requirements set out below, utilise the same management tools and methods already in use by the Supplier to manage and monitor its own business.

References

This DID must be read in conjunction with Schedule A (General Conditions), Part 5 (QA) of the SOW, Supplier’s Quality Plan and ITP.


The Supplier shall prepare the Manufacturing Records Book Index using its own format and shall ensure the content meets the requirements set out below.

Format and Content

The Manufacturing Records shall be indexed in such a way to enable immediate retrieval of its contents and would typically reference:

1. Index

2. Design drawings and documents

3. Material certificates and material traceability drawings

4. Production records such as welding, heat treatment etc.

5. Dimensional survey records

6. Test records including NDE, pressure and FAT

7. Coating, painting or insulation records

8. Other transversals records such as electro magnetic engineering (EME), noise, shock, Materials, safety, etc.

NOTES:

1. Manufacturing records shall comply with specifications, relevant codes and standards and third party requirements.

Defect Recording and Corrective Action System Report (DRACAS Report), Rev 0


Agreement #: N/A




Defect Recording and Corrective Action System Report (DRACAS Report)

QA210




Defect Recording and Corrective Action System Report (DRACAS Report), Rev 0


Agreement #: N/A



Defect Recording and Corrective Action System Report QA210

Purpose

The purpose of the Defect Recording and Corrective Action System (DRACAS) is to capture the failures, remedies and improvements relating to Defects in the Deliverables.

References




Format and Content


2 The DRACAS Report shall contain all Defects and Corrective Action relating to the Equipment and/or Deliverable Software.

Installation Instructions, Rev 0





Installation Instructions

OPS201



Installation Instructions, Rev 0




Installation Instructions OPS201

Purpose

The purpose of the Installations Instructions is to describe to the Purchaser the preparation, processes and tools needed for the Purchaser to carry out installation.

References



This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 6 (Operations) of the SOW.

Format and Content

The Installation Instructions shall contain, as a minimum, the following:

1 Hardware

(a) assembly instructions;

(b) preparation of seatings;

(c) installation procedure;

(d) alignment procedures; and

(e) listing of special tools, jigs, installation aids, handling and lifting arrangement.

2 Electrical

(a) cable data connection and termination;

(b) listing of termination and crimping tools and connector tool kits.

3 precautions;

4 lifting and transit warnings;

5 safety notices and warnings;

6 identification of any special tools and test equipment, jigs, fixtures, templates, lifting gear, beams, etc. required by the Purchaser to install the Goods and listed in Schedule E (Goods); and

7 identify the On Loan Items required by the Purchaser to handle, maintain, install, test and calibrate the Goods following delivery. These On Loan Items are listed in Schedule E (Goods).

Installation Certificate, Rev 0





Installation Certificate

OPS202 Prepared by : Vancouver Sh ipyards Co. L td .







Installation Certificate OPS202

Purpose

The purpose of the Installation Certificate is to certify that the Equipment or items of the Equipment have been installed in accordance with the Installation Instructions provided by the Supplier in accordance with SDRL OPS201 and DID OPS201.

References




Format and Content

The Supplier to complete and return the attached pro forma certificate.





Attachment A to DID OPS202

CONFIRMATION OF INSTALLATION CERTIFICATE

Name of Supplier: [*]

Agreement number: [*]

Covering Purchase Order number: [*]

Description of the Equipment: [*]

SWBS number: [*]

I certify that the Equipment or Items of the Equipment listed below have been installed in accordance with the installation requirements.

Description of Equipment or Item of the Equipment Installation Instructions Ship # DDMMMYY

SDRL # DID #

Signed: [*] I have authority to bind the Company

Name: [*]

Title : [*]

Date: [* DDMMMYY]

Test Report, Rev 0





Test Report

OPS203 Prepared by : Vancouver Sh ipyards Co. L td .



Test Report, Rev 0




Test Report OPS203

Purpose

The purpose of the Test Report is to provide details of any tests undertaken by the Supplier and the results of those tests.

References




Format and Content


2 Test Results shall include as a minimum:

(a) the tests carried out by the Supplier; and

(b) the results of each test.

Maintenance Instructions – Post Equipment Acceptance, Rev 0





Maintenance Instructions – Post Equipment Acceptance

COM106 Prepared by : Vancouver Sh ipyards Co. L td .



Maintenance Instructions – Post Equipment Acceptance, Rev 0

Document #: N/A Agreement #: N/A


Unclassified Page 2 of 2 Purchaser’s initials: _____ Uncontrolled when Printed Supplier’s initials: _____ See disclosure statement on front page

Maintenance Instructions – Post Equipment Acceptance

COM106

Purpose

The purpose of the Maintenance Instructions (Post Equipment Acceptance) is to define the necessary preventative and corrective maintenance instructions to be undertaken by the Purchaser to maintain the equipment in a safe and operational condition onboard the vessel between the period of Final Acceptance of equipment and delivery to the Owner.

The Maintenance Instructions (Post Equipment Acceptance) shall also define the complimentary support and test equipment (S&TE) and materials required to carry out the defined maintenance tasks.

This DID contains the purpose, scope, references, preparation instructions, content, structure and special instructions, if any, for the preparation of a Defect Recording and Corrective Action System.

References



This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 7 (Commissioning, Test and Trials) of the SOW.

Format and Content

The Maintenance Instructions (Post Equipment Acceptance) shall include as a minimum:

a) Maintenance Task Reference Number;

b) Task title/description;

c) Required qualifications of maintainers (if any);

d) Periodicity of each task;

e) Safety procedures for each preventive maintenance task;

f) Instructions or procedures for completion of each maintenance task;

g) Lists of any S&TE, STTE, common tools and test equipment, stores, materials, preservatives spares etc, cross referenced to each task;

h) Duration of each task in man hours and elapsed time;

i) Identification of safety critical tasks;

j) Drawings and illustrations to assist the maintainer;

k) Post-maintenance tests to confirm the equipment fully operational; and

l) Be written in the Contractor’s format.

Detailed Commissioning Plan, Rev 0





Detailed Commissioning Plan

COM204




Detailed Commissioning Plan, Rev 0




Detailed Commissioning Plan COM204

Purpose

The purpose of this DID is to make the Contractor aware of the information required to be supplied in the Detailed Commissioning Plan. The Detailed Commissioning Plan informs the Purchaser how the Contractor will deliver the High Level Commissioning Strategy.

Scope

This DID contains the purpose, scope, references, preparation instructions, content, structure and special instructions, if any, for the preparation of the Detailed Commissioning Plan.

References



The Contractor shall prepare the Detailed Commissioning Plan in the content and format set out below.

Format and Content

a. Introduction – This section shall provide an overview of all aspects of commissioning work and statements of the objectives to be achieved.

b. Establishment of Requirements and Acceptance – This section shall describe how the Contractor intends to (1) identify the requirements of this contract and (2) demonstrably prove through documentary evidence the requirements have been met through a progressive acceptance process.

c. Resources – This section shall contain as a minimum:

i. Profile of Contractors resource on a monthly basis.

ii. Working calendar including privilege holidays, standard daily working pattern

iii. Indication of usage of sub-contractor and/or supplier resources.

d. Risk and opportunities Management – This section shall cover risks and opportunities identified by the contractor relevant to the delivery of the Commissioning SoW.

e. Document Management – This section shall describe how the Contractor intends to manage project documentation.

f. System integration – This section shall describe how the contractor intends to integrate its commissioning scope with other ship build activities.

g. Interface Management - This section shall describe how the contractor intends to manage commissioning interfaces on the project.

h. Programme Methodology - This section shall describe how the contractor will deliver the Commissioning SoW and how this will be integrated with the whole ship commissioning programme and the project integrated programme. It shall cover the order of delivering commissioning within the build yard and VSL.

i. Repair and Maintenance Management - This section shall describe how the contractor will satisfy its obligations regarding repair and maintenance.

Shelf Life Register, Rev 0





Shelf Life Register

COM205








Shelf Life Register COM205

Purpose

The purpose of the Shelf Life Register is to make the Purchaser aware of the Goods, or items of the Goods, that need to be replaced owing to degradation over time (shelf life). e.g.: hoses, bellows, pressurised bottles, accumulators, relief valves etc, …).

References




Format and Content

The Supplier shall complete the attached pro forma Excel spreadsheet.





Attachment A

Shelf Life Register

Pressure Vessel Register – Accumulators

Data fields -

Contract number; SLIN; ‘Parent Equipment’; location on Equipment; function (if known); True Manufacturer’s Serial Number; NATO Stock number (where known); True Manufacturers part number (PN); Proof Test Date; Manufacturer; Date of Manufacture; Use; Charge Date.

Pressure Vessel Register - Bottles

Data fields –

Contract number, SLIN, ‘Parent Equipment/System’; location on Equipment; function; True Manufacturers Serial No; NATO Stock number (where known); True Manufacturers PN; proof test date; True Manufacturer; date of manufacture; use; charge date.

Relief Valves Register

Data fields –

Contract number, CLIN, ‘Parent Equipment/System’; Manufacturers Serial No; Manufacturers Part No; NSN (where known); set pressure; proof test date; True Manufacturer; date of manufacture; Use.

Hose / Bellows Register

Data fields –

Contract number, SLIN, ‘Parent Equipment/System’; True Manufacturer’s PN; NATO Stock number (where known); cure date; batch; True Manufacturer; date of manufacture if non rubber; test date; date fitted to Equipment/system.

Rigging Warrant

Contract number, SLIN, ‘Parent Equipment/System’; True Manufacturers PN; description; NATO Stock number (where known); True Manufacturer; date fitted to Equipment/system; Shelf Life duration; test date (where known); disposal instructions.

Consumables Items

Data field –

Contract number, SLIN, ‘Parent Equipment/System’; True Manufacturers PN; description; NSN (where known); Manufacturer; Date fitted to equipment/system; Shelf life duration; Test date (where known); disposal instructions.

Equipment by Lifed expiry.

Data field –

Contract number, SLIN, ‘Parent Equipment/System’; True Manufacturers PN; description; NATO Stock number (where known); True Manufacturer; date fitted to Equipment/system; disposal instructions.

Training Needs Analysis – Purchaser’s Personnel, Rev 0





Training Needs Analysis – Purchaser’s Personnel

COM207




Training Needs Analysis – Purchaser’s Personnel, Rev 0




Training Needs Analysis – Purchaser’s Personnel

COM207

Purpose

The purpose of the Training Needs Analysis (Purchaser’s Personnel), is to identify the training requirements to be supplied to the Purchaser’s personnel so they can operate, fault diagnose and maintain the equipment in its operational state onboard the ship in a safe and competent manner.

References




Format and Content

The Training Needs Analysis (Purchasers Personnel), shall include as a minimum:

a. Existing training courses.

b. Required levels of competencies for Purchaser’s personnel.

c. Training required to close any gaps between current and required training.

d. How, where and by whom can this training be best conducted.

e. Be written in the Contractor’s format.

Detailed Course Syllabus and Lesson Plan, Rev 0





Detailed Course Syllabus

and Lesson Plan

COM208




Detailed Course Syllabus and Lesson Plan, Rev 0




Detailed Course Syllabus and Lesson Plan

COM208

Purpose

The purpose of the Detailed Course Syllabus and Lesson Plan – Purchaser’s Personnel is to define the training course to be supplied to the Purchaser’s personnel so that they can operate, fault diagnose and maintain the equipment in its operational state onboard the vessel in a safe and competent manner.

Scope

This DID contains the purpose, scope, references, preparation instructions, content, structure and special instructions, if any, for the preparation of a Detailed Course Syllabus and Lesson Plan – Purchaser’s Personnel.

References



The Contractor shall provide a Detailed Course Syllabus and Lesson Plan – Purchaser’s Personnel, using its own internal documentation.

Format and Content

The Detailed Course Syllabus and lesson Plan – Purchasers Personnel, shall include as a minimum:

a. The detailed course syllabus shall identify the subject areas to be addressed, details of assessment procedures to be used and usage of training aids and devices (if any)

b. The lesson plans shall include a detailed breakdown of course content against time. Periods of any social events and interactions shall be identified.

c. The contractor shall provide a proposal for the documentation necessary to conduct operating, maintenance and repair training for the equipment.

d. Pre-requisite skill and trade background for candidate students

e. List of training tasks

f. Measures of student performance

g. Description of instructional setting/facility

h. Learning objectives and learning steps

i. Entry tests and pre-tests if applicable

j. Complete instructional programs

k. Student notes or hand-outs.

Maintenance Records, Rev 0





Maintenance Records




Repair and Maintenance Records, Rev 0




Maintenance Records COM209

Purpose

The purpose of the Maintenance Records is to make the Purchaser aware of the repair and maintenance activities undertaken by the Supplier.

This DID contain the purpose, scope, references, preparation instructions, content, structure and special instructions, if any, for the preparation of Maintenance Records.

References




Format and Content

The Maintenance Records shall include as a minimum:

1. Repair and maintenance data for all supplied equipment.

2. Details of spare parts, special tools etc. required to carry out repairs or corrective maintenance.

3. Be written in the Supplier’s format.

Commissioning Documentation, Rev 0





Commissioning Documentation




Commissioning Documentation, Rev 0




Commissioning Documentation COM211

Purpose

The purpose of this DID is to identify to the Contractor the requirements for the development and presentation of the commissioning documentation to conduct set to work and commissioning activities.


References




Format and Content

1. The Contractor shall prepare commissioning documentation using their own format in such a manner that it can be integrated within the Purchaser`s own Test and Trials documents. The Purchaser shall supply the Contractor with its Commissioning Documentation format to indicate which part is to be provided by the Contractor.

2. Instructions:

The following information shall be provided by the Contractor:

a) Safety information - precautions, pre-requisites, risk assessments;

b) Technical reference documentation;

c) Technical drawings;

d) Equipment operation synopsis;

e) Pre-requisites and supporting services, equipment and tools;

f) Set to Work procedure;

g) Ship’s Control and Monitoring System (SMCS) I/O signal data; and

h) Any supporting documentation and guidance.

Defect Report, Rev 0





Defect Report




Defect Report, Rev 0




Defect Report COM213

Purpose

The purpose of the Defect Report is to make the Purchaser aware of the nature of a defect, the circumstances in which it appeared, the analysis of the root cause and the remedial actions taken by the Contractor.


References




Format and Content

1. The Contractor shall prepare commissioning documentation using their own format in such a manner that it can be integrated within the Purchaser`s own Test and Trails documents. The Purchaser shall supply the Contractor with its Commissioning Documentation format to indicate which part is to be provided by the Contractor.

2 Instructions:

The Defect Report shall include as a minimum:

a) Description of the original defect – The Contractor shall provide an in depth review and analysis of the events that lead to the defect arising;

b) Description of the effect on the article – The Contractor shall provide detail of the impact of the problem on the article;

c) Discussion of options - The Contractor shall provide a discussion of the options considered. This shall also address the trade-off studies used to arrive at the recommended solution;

d) The proposed technical solution for the rectification of the defects as applied to the detail at 2 above - The Contractor shall provide information pertaining to the execution of the programme of work to rectify the defect. Any diagnostic results from rectification and specific information on any materials was used in the process of rectification should be supplied;

e) Conclusive assurance from the Contractor – the Contractor shall provide supporting evidence that will demonstrate that the solution applied is within the requirements and does not necessitate a requirement for additional tests. Also the Contractor should provide assurance that warranty and/or guarantees have not been affected; and

f) All documents, if any, referred to in the defect report shall be attached.

Start Up/Shut Down and Operational Procedures, Rev 0





Start Up/Shut Down and Operational Procedures




Start Up/Shut Down and Operational Procedures, Rev 0




Start Up/Shut Down and Operational Procedures

COM214

Purpose

The purpose of the Start Up/Shut Down and Operational Procedures is to make the Purchaser aware of the procedures and pre-requisites necessary to start up, shut down and operate the equipment in normal, alternative and/or emergency modes where applicable.


References




Format and Content

1. The Supplier shall prepare commissioning documentation using their own format in such a manner that it can be integrated within the Purchaser`s own Test and Trails documents.

2. Instructions:

The Start Up and Shut Down Procedures shall include as a minimum:

a) Safety precautions;

b) Normal start up procedures;

c) Normal shutdown procedures;

d) Emergency start up procedures (if applicable);

e) Emergency Shutdown procedures (if applicable);

f) Post maintenance checks;

g) Pre-sea checks;

h) Operational checks and procedures; and

i) Associated system/equipment and location.

INCO Spares Request, Rev 0





INCO Spares Request

COM215




Spares Request, Rev 0




Spares Request COM215

Purpose

The purpose of the Spares Request is to make the purchaser aware of a request to support the Contractors testing and trialing activities.


References




Format and Content

1. The Contractor shall prepare commissioning documentation using their own format in such a manner that it can be integrated within the Purchaser`s own Test and Trails documents. The Purchaser shall supply the Contractor with its Commissioning Documentation format to indicate which part is to be provided by the Contractor.

2. The Contractor shall complete the pro forma attached as Annex A to this DID.

Post Ship Acceptance Test and Trials Report (NaMMS), Rev 0





Post Ship Acceptance Test and Trials Report (NaMMS)

COM216



Post Ship Acceptance Test and Trials Report (NaMMS), Rev 0

Document #: [* insert VSY Document #] Package #: [* insert VSY Package#]


Unclassified Page 2 of 2 Purchaser’s initials: _____ Uncontrolled when Printed Supplier’s initials: _____ See disclosure statement on front page Duplicate 1of 2

Post Ship Acceptance Test and Trials Report (NaMMS)

COM216

Purpose

The purpose of this DID is to make the Purchaser aware of the test and trial results.

References




Format and Content

1. The Contractor shall prepare this report in accordance with the directions, guidance and instructions contained in Part 9 of C-03-005-012/AM-001, "Naval Materiel Management System (NaMMS) Manual".

DID FIN301 Payment Claim



Ref: Payment Claim Unclassified Page 1 of 4 Uncontrolled when printed



Payment Claim

FIN301






Ref: Update to Schedule E Unclassified Page 2 of 4 Uncontrolled when printed


Payment Claim FIN301

Purpose

To submit a claim for payment for work performed under the Subcontract.

References

This DID must be read in conjunction with Schedule A (General Conditions), Part 8 (Finance) of Schedule D1 (SOW and DID FIN302 (Milestone Achievement Certificate).


Content and Format

1 Payment Claims must be made in the Supplier’s name using the Supplier’s standard invoice format (Invoice).

2 The Invoice must show:

(a) The date, the name and address of the Purchaser, item or reference numbers, deliverable / description of the Work, and the Agreement number;

(b) details of expenditures (such as item, quantity, unit of issue, unit price, Sub-subcontracts, as applicable) exclusive of Applicable Taxes;

(c) the extension of the totals, if applicable;

(d) the method of shipment together with date (if applicable), the SLIN number (see Schedule E (Goods), case numbers and part or reference numbers, shipment charges and any other additional charges;

(e) the Milestone number(s) and descriptions; and

(f) the Covering Purchase Order line number (if applicable).

3 If a credit to VSY is required, a separate credit memo shall be prepared (not to be included on a preceding claim for a future milestone or travel cost) including the following, if applicable:

3.1 reference to vendor’s original invoice number and date the credit relates to

3.2 reference to the PO line to be credited

3.3 Number of hours credits and details

3.4 Task authorization (or relevant category, milestone number or task category)

3.5 Cut-off requirements (i.e. calendar year-end, Canada fiscal year)

3.6 Holdback and sales tax (GST or HST) if previously billed

4 Applicable Taxes must be specified on all Invoices as a separate line item along with corresponding registration numbers from the applicable tax authorities. All items that are zero-rated, exempt or to which Applicable Taxes do not apply, must be identified as such on all Invoices.

5 Unless specified, claim holdback is not required for material milestone and travel cost claims.






6 If a Payment Claim relates to a Milestone, then the Invoice must also be supported by a completed Milestone Achievement Certificate (MAC) (see DID FIN302 in Part 8 (Finance) of Schedule D3 (DIDs)).

Travel Reimbursement (Ad-Hoc)

1 Travel related cost is deemed to be inclusive of the firm-fixed price, therefore travel reimbursement relates to ad-hoc travel requirements and /or requests.

2 If applicable, travel cost reimbursement requires preapproval from VSY’s Subcontracting Authority. Please refer to the most recent guidance provided by VSY for travel events expense reimbursement.

3 For any given travel event the claim for travel reimbursement shall cover all expenses and travel time related to that travel event. Specifically:

3.1 The travel expense claim for a travel event MUST NOT be split over 2 or more invoices; or

3.2 The travel time related to any given travel event MUST be included on the same invoice as the travel expenses

3 Approved Travel events may include the following

3.1 Travel Time Hours;

3.2 Flight Cost;

3.3 Accommodation costs (including parking costs at the hotel if included on the hotel’s invoice);

3.4 Car rental costs;

3.5 Transportation costs including but not limited to

1.1.1. Taxis as appropriate; 1.1.2. Parking as appropriate; 1.1.3. Gas; 1.1.4. Personal mileage expenses; and 1.1.5. Travel between the travellers home and the airport; 1.1.6. Per Diem costs (refer to section 5 below) 1.1.7. Visa Expenses; and 1.1.8. Canadian Bank/Credit card charges related to foreign currency expenditure for expenses that fall into one of

the above categories as per the contract clause relating to foreign expenses.

4 No other incidental or business expenses are claimable including but not limited to: tips (other than taxi tips), water, laundry, telephone calls, dependent care and similar expenses included within the NJC directive such as in sections 3.3.2 and 3.4.2 Per diems, Meal (and Incidental) Allowances

1 Effective 1 April, 2018 meal allowances have been replaced by a daily per diem rate of: CAD$ 90 in Canada; US$ 90 in the USA; Euro 124 in Germany Euro 123 in the Netherlands NOK 1378 in Norway DKK 1138 in Denmark GBP 94 in the United Kingdom (including Northern Ireland)






For countries not in the current VSY travel plan the per diem will be calculated based on the values of the NJC meal allowance excluding incidental allowance applicable to that country plus 4% rounded up to the nearest whole number.

2 Meal allowance details: 2.1 Applicable taxes are in addition to the daily per diem 2.2 The per diem applies in full to the day of travel, regardless of the time of day that travel commenced 2.3 Will cover all miscellaneous costs such as: water, phone calls, laundry, tips, newspaper, etc. 2.4 Please refer to the most recent guidance provided by VSY for travel events expense reimbursement

DID FIN302 Milestone Achievement Certificate Document #: VSY-A08.22-0112 Agreement #: [* insert Agreement #]


Ref: Milestone Achievement Certificate Unclassified Page 1 of 3 Uncontrolled when printed



Milestone Achievement Certificate

FIN302







Milestone Achievement Certificate FIN302

Purpose

The Milestone Achievement Certificate duly approved and countersigned by the Purchaser’s Subcontracting Authority, authorises the Supplier to submit a Payment Claim and/or an Escalation Payment Claim (as applicable).

References

This DID must be read in conjunction with Schedule A (General Conditions), Schedule G (Financial Arrangements), Part 8 (Finance) of Schedule D1 (SOW) and DID FIN301 (Payment Claim) (as applicable).


Content and Format

Complete Attachment A - Milestone Achievement Certificate.





Attachment A to DID FIN302 Milestone Achievement Certificate

MILESTONE ACHIEVEMENT CERTIFICATE

Agreement Number: ________________________________

Covering Purchase Order Number: ________________________________

Name of Supplier: ________________________________

Description of the Goods: __________________________

The Supplier hereby declares and certifies that it has achieved Milestone number [* insert Milestone number] of Schedule G (Financial Arrangement) subject only to the following exceptions:

Exceptions:

[* insert all exceptions to be specifically declared here. Use attachment if required].

The Parties have executed this Subcontract through their duly authorised representatives.


Vancouver Shipyards Co. Ltd.


[* insert legal name of Supplier]

Signature: Signature:

I warrant that I have authority to bind the company. I warrant that I have authority to bind the company.

Print name: [*] Print name: [*]

Title: [* insert Subcontracting Authority] Title: [* insert Representative of the Supplier]

Date: [*] Date: [*]

Signature: I warrant that I have authority to bind the company.

Print name: [*]

Title: [* insert CFO or equivalent]

Date: [*]

3

Visitor Clearance Request, Rev 0


Agreement #: N/A




Visitor Clearance Request

SEC202




Visitor Clearance Request, Rev 0


Agreement #: N/A



Visitor Clearance Request SEC202

Purpose

The purpose of the Visitor Clearance Request is to advise the Security Authority of intended visits to the Purchaser’s Premises or a Ship so as to allow a security check and authorisation to be conducted prior to attendance.

References

This DID must be read in conjunction with Appendix H (Security Requirements) and Schedule A (General Conditions) and the corresponding SOW reference.


This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 9 (Security) of the SOW.

Format and Content

The Supplier shall submit the Request for Visit online by completing the form at the Public Works and Government Services Canada website:

http://iss-ssi.pwgsc-tpsgc.gc.ca/ssi-iss-services/dv-rfv-eng.html

http://iss-ssi.pwgsc-tpsgc.gc.ca/ssi-iss-services/dv-rfv-eng.html

Non-Disclosure Agreement

Rev 1


Template ref: DID SEC 203 NDA Unclassified Page 1 of 4 Purchaser’s initials: _____ Uncontrolled when Printed Supplier’s initials: _____ VSY Proprietary / Commercial Sensitive


Title: Non-Disclosure Agreement Ship applicability: All

Master Template Ref: DID SEC203 Non-Disclosure Agreement Project: All


DID VSY Security NA NA ALL



SEC203



.


Rev 1



Non-Disclosure Agreement SEC203

Purpose

The purpose of the Non-Disclosure Agreement (NDA) is to ensure that the Supplier and its lower tier suppliers (i.e. Sub-subcontractors, representatives, consultants and/or agents comply with section 2030.23 10.c(i)(A) of Annex B to Schedule A (General Conditions).

References




Format and Content

1 Complete attachment A to this DID (pro forma NDA).


Rev 1




Non-Disclosure Agreement: Supplier’s Subcontractors to Canada and the Purchaser

To: Her Majesty the Queen in Right of Canada as represented by the Minister of Public Works and Government Services (“Canada”)

and

Vancouver Shipyards Co. Ltd. (“VSY”)

1 We, [* insert full legal name of Supplier] a company incorporated under the laws of [*insert jurisdiction of incorporation] (the “Company”) recognize that in the course of or as a result of our work as a contractor or subcontractor for services in relation to the Joint Support Ship Project, we may be given access to confidential information belonging to ThyssenKrupp Marine Systems Canada Inc., VSY, Canada or to other identified third parties (including ThyssenKrupp Marine Systems GmbH (“TKMS”)). In this Agreement, “confidential information” means any information in relation to the Joint Support Ship Project in any form, whether oral, hard copy or electronic, that is known to have or by its nature is likely to have financial value to the party disclosing it or to a third party, or any information that is known to be or by its nature is likely to be treated by the disclosing party as confidential information of itself or a third party that is disclosed to us during the performance of the contract or subcontract or as a result of it, and includes but is not limited to: any such documents, instructions, guidelines, data, drawings, specifications, materials, or any other information whether received orally, in printed form, recorded electronically, or otherwise and whether or not labeled as proprietary or sensitive.

2 We hereby agree and shall so instruct our employees that we shall not reproduce, duplicate, use, divulge, release or disclose, in whole or in part, in whatever way or form any confidential information or documentation to any person (other than to a person employed by VSY or Canada or to a person to whom disclosure has been expressly consented to by VSY or Canada) except on a need to know basis to employees within the Company and for the purpose of our contract, and hereby undertake to safeguard the same and take all necessary and appropriate measures, including those set out in any written instructions issued by Canada or VSY, to prevent the disclosure of or access to such information or documentation in contravention of this Agreement. Without limiting the generality of the foregoing, we understand and agree that information and documentation disclosed to us while performing work under the contract is not to be used for any purpose except to carry out the contract. For the purpose of this Non-Disclosure Agreement, embedded consultants who have been approved in writing by Canada and perform work for the Company under contracts of service are deemed to be employees of the Company, and the Company is responsible for them hereunder as if they were employees.

3 We shall not make use of any confidential information for any purpose other than the carrying out of our obligations under our contract, described above.

4 At the written request of Canada or VSY and at the expiry or termination of our contract, we will immediately deliver to VSY all hard copies of all confidential information that have come into our possession or have been made in the performance of the contract as well as every draft, working paper and note that contains any of the confidential information, and we will immediately delete all electronic records of any of those, except that we are under no obligation to delete back-up computer records provided that we make no attempt to retrieve such records.

5 Nothing in this Agreement shall be construed as preventing the disclosure or use of any confidential information to the extent that such information:

(a) is or becomes in the public domain through no fault of our own;

(b) is or becomes known to us from a source other than the other party to our contract or the party who disclosed it to us for purposes of the contract, except any source that is known to us to be under an obligation not to disclose the information; or


Rev 1



(c) is disclosed under compulsion of a legislative requirement or any order of a court or other tribunal having jurisdiction.

6 The Company acknowledges that the confidential information is proprietary and confidential and that Canada, VSY or their subcontractors, as the case may be, would be irreparably damaged if any of the provisions contained in this Agreement are not performed by the Company in accordance with the terms set out and therefore the Company agrees that, in addition to monetary damages and without limiting any other rights or remedies that Canada, VSY or their subcontractors may have, Canada, VSY and their subcontractors will have the right to immediate injunction and specific performance or other available equitable relief in any court of competent jurisdiction, enjoining any such threatened or actual breach of this Agreement by the Company.

7 No failure or delay by any party in exercising any right, power or privilege under this Agreement will operate as a waiver of that right, power or privilege, and the single or partial exercise of a right, power or privilege under this Agreement will not preclude any other or future exercise of that or any other right, power or privilege. Any amendment to this Agreement will be effective only if in writing signed by all the parties.

This Agreement must be interpreted and governed by the laws in force in British Columbia, Canada.

We agree that the terms of this Agreement shall survive the completion of the work under our contract or subcontract with VSY as the case may be.

[IF APPLICABLE INSERT THE FOLLOWING: This Non-Disclosure Agreement supersedes the Non-Disclosure and Confidentiality of Information Agreement signed on ________ for confidential information disclosed to us after the date hereof.]

IN WITNESS WHEREOF this Agreement has been duly signed and delivered this ________ day of______, 20__, by our officers duly authorized in this respect.

Company Name________________

Signature

_____________________________ _______________________________

(I have authority to bind the corporation)

End Use Certificate Request Rev 1


Template ref: DID SEC204 End Use Certificate Request Unclassified Page 1 of 3 Purchaser’s initials: _____ Uncontrolled when Printed Supplier’s initials: _____ VSY Proprietary / Commercial Sensitive


Title: End Use Certificate Request Ship applicability: All

Master Template Ref: DID SEC204 End Use Certificate Request Project: All




End Use Certificate Request

SEC204



.




End Use Certificate Request DID SEC204

Purpose

The End User Certificate Request is intended to make the Security Authority aware of any statutory obligations that the Supplier must fulfil by way of an End Use Certificate from the End User in order to provide the Supplies.

References




Format and Content

Format and Content

Complete attachment A to this DID (pro forma End Use Certificate).





INSTRUCTION: Letterhead (if possible) of company applying, address and contact info of the end-user (Vendor) in the country of destination (if you work through an agency, put the agency’s contact info)]

END-USE CERTIFICATE

In accordance with the regulations of the Federal Republic of Country of Germany, which state that granting of an individual export licence is dependent on the presentation of an end-use certificate, we certify that the technology supplied by;

Name of the supplier: [Name of Supplier]

Description of the technology: Documents and/or technology of the XXX in accordance with Contract # XXX-XXX/XXX/JSS

which is for the development/Build or use of the Canadian Joint Support Ship (JSS) within the frame of a contract between the Crown and ThyssenKrupp Marine Systems Canada Inc., will be treated strictly confidential. We shall neither pass the technology on to other companies nor shall we make knowledge available to third parties except for other governmental offices within Canada involved ThyssenKrupp Marine Systems Canada, and

Contractors and subcontractors, and Bidders for such contracts, involved in the design, construction, building, maintenance and modification of the ships in Canada, and training of personnel.

We certify that the goods which will be produced by the help of the transferred technology (derived goods) are intended for our final use in Canada except for operation and necessary maintenance of the JSS II anywhere in the world, and will only be used by us for the Canadian Joint Support Ship II (JSS II).

We certify that we will neither re-export the technology nor export the derived goods without the approval of the Federal Export Office (BAFA) of the Federal Republic of Country of Germany. Re-exports of the technology to contractors and subcontractors, and Bidders for such contracts, involved in the design, construction, building, maintenance and modification of the ships from the following countries do not require any approval of BAFA.

Australia Germany Luxembourg Spain Austria Great Britain Malta Sweden Belgium Greece Netherlands Switzerland Czech Republic Hungary New Zealand United States of America

Denmark Ireland Norway Cyprus (i.e. in the areas in which the government of Republic Cyprus Exercises control

Estonia Italy Poland Finland France

Japan Portugal Latvia Slovak Republic Lithuania Slovenia

The technology will only be delivered to a third person/company, including Bidders for contracts, on condition that this third person/company accepts the commitments of the above declaration as binding for itself and on condition that this third person/company is known to be trustworthy and reliable in the observance of such commitments.

[City, Province/State, Country, Date]_____ [Signing authority

Place, Date Vendor signature

____________________________________ _____________________________________ If possible Company (Vendor) stamp/official seal Name and title of signer in block letters

Letter Certificate Rev 1


Template ref: DID SEC205 Letter Certificate Unclassified Page 1 of 3 Purchaser’s initials: _____ Uncontrolled when Printed Supplier’s initials: _____ VSY Proprietary / Commercial Sensitive


Title: Letter Certificate Ship applicability: All

Master Template Ref: DID SEC205 Letter Certificate Project: All




Letter Certificate

SEC205



.




Letter Certificate DID SEC205

Purpose

The purpose of the Letter Certificate is to certify the Confidential Information, as defined in the Non-Disclosure Agreement (NDA) between the Supplier, Canada and TKMS has been returned in accordance with the provisions of the NDA.

References




Format and Content

1 Complete attachment A to this DID (pro forma Letter Certificate).

2 The Letter Certificate must be on the Supplier’s formal company letterhead.




Attachment A – Letter Certificate

[* Letter to be sent on Supplier Letterhead]

[* DDMMMYY]

Your reference: [* insert VSY RFP #] Our reference: [* insert Supplier’s reference number]

Vancouver Shipyards Co. Ltd. 50 Pemberton Avenue North Vancouver, British Columbia Canada, V7P 2R2

Attention: [* insert name of Subcontract Authority], [* inset title]

SUBJECT JSS Project - Return of Confidential Information

References: A. Request for Proposal # [*insert VSY RFP number] dated [* insert DDMMMYY] B. Non-Disclosure Agreement (between Vancouver Shipyards Co. Ltd. and [* insert name of Supplier],

dated [*insert DDMMMYY] (NDA)

Dear Sirs,

Further to the above captioned NDA (Ref. B) and Request for Proposal (Ref. A), we hereby warrant and certify (in accordance with paragraph 3(h) of the NDA) the following:

o all Confidential Information, as defined by the NDA, has been returned to Vancouver Shipyards Co. Ltd.;

o every draft, working paper and note that contains Confidential Information or any information related to the Confidential Information has been returned to Vancouver Shipyards Co. Ltd.;

o all electronic records (except for back-up computer records) of any Confidential Information including every draft, working paper and note that contains Confidential Information or any information related to the Confidential Information has been deleted. We further covenant and agree that we will make no attempt to retrieve Confidential Information including drafts, working papers and notes, contained within back-up computer records.

I, the undersigned, herby certify that I am authorised to make the above statements for and on the behalf of [* insert name of Supplier].

Sincerely,

[* Signed] [* name and title of signatory]

Method Statement, Rev 0





Method Statement

HSE201



Method Statement, Rev 0




Method Statement HSE201

Purpose

The purpose of the Method Statement is to make the Purchaser aware of any method statement or risk assessment required by law prior to setting the Equipment to work.

References



This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 10 (Health, Safety and the Environment) of the SOW.

Format and Content


2 Content as required by law.

Canadian Content Value Form, Rev 0





Canadian Content Value Form

IRB201






Unclassified Page 2 of 5 Purchaser’s initials: _____ Uncontrolled when printed Supplier’s initials: _____ See disclosure statement on front page.

Canadian Content Value Form IRB201

Purpose

The Canadian Content Value Form advises the Purchaser of the Canadian content of the Work undertaken by the Supplier under the Subcontract.

References




Format and Content

Complete the CCV form attached as Attachment A to this DID.





Attachment A

CCV Form

1 GENERAL

The product and/or service (i.e. the Deliverables under the Subcontract) you have and/or may supply to Vancouver Shipyards Co. Ltd. (i.e. the Purchaser under the Subcontract) may be subject to compliance with the Government of Canada’s Industrial and Regional Benefits (IRB) Program, in which Canadian Content Value (CCV) information is requested by the Government of Canada. CCV is measured in Canadian dollars ($CAD).

In an effort to remain compliant with the Canadian Government’s IRB program, please complete the following form in accordance with the instructions set out below:

Company Name (Legal Name) Primary Contact

Phone

Fax Email

Street Address Additional Comments, if any:

Province Postal Code

"Small and Medium Business" or "SMB" means a Canadian‐based, independently‐owned and operated manufacturer or service company with fewer than 250 full‐time personnel as of the date of entering into an eligible IRB Transaction. Agents and distributors of foreign goods and services as well as subsidiaries of large firms do not qualify as Small and Medium Business.

Based on the above definition, is your business SMB?

Yes No

Number of full-time employees:

What is the Canadian Content Value (CCV) of your supplied products/services?

Please state your CCV in percentage: % (Please refer to the information provided below on how to

Signature: Date:

2 CANADIAN CONTENT VALUE (CCV)

The CCV shall be determined by the Net Selling Price Method or the Cost Aggregate Method.

2.1. Net Selling Price Method: A product or service which bears a substantiated selling price may have its CCV calculated as follows:

2.1.1 begin with the total selling price of the product or service; and

2.1.2 subtract any costs incurred as set out in section 2.3.

2.2 Cost Aggregate Method: Any product or service that cannot be assigned a substantiated selling price may have its CCV calculated as the aggregate of the following:





2.2.1 the cost of parts produced in Canada, and the cost of materials to the extent that they are of Canadian origin, that are incorporated in the Equipment or Software Deliverable in the factory of the manufacturer in Canada;

2.2.2 the cost of parts or materials which the IRB Authority can verify as being of Canadian origin, in that they have been exported from Canada and subsequently imported into Canada as parts or finished goods;

2.2.3 transportation costs, including insurance charges incurred in transporting parts and materials from a Canadian supplier or frontier port of entry to the factory of the manufacturer in Canada for incorporation in the equipment, to the extent that such costs are not included in the foregoing paragraph; and

2.2.4 such part of the following costs (not including GST, HST, all provincial sales taxes, excise taxes, royalties and license fees paid outside of Canada) as are reasonably attributable to the production or implementation of the equipment, service or activity:

2.2.4.1 wages and salaries paid for direct and indirect production and non‐production labour in Canada paid to Canadians or to permanent residents as defined in the Immigration and Refugee Protection Act 2001, c.27;

2.2.4.2 materials used in the Work but not incorporated in the final products;

2.2.4.3 light, heat, power and water;

2.2.4.4 Workers’ compensation, employment insurance and group insurance premiums, pension contributions and similar expenses incurred with respect to labour referred to above in 2.2.4.1;

2.2.4.5 taxes on land and buildings in Canada;

2.2.4.6 fire and other insurance premiums relative to production inventories and the production plant and its equipment, paid to a company authorized by the laws of Canada or any province to carry on business in Canada or such province;

2.2.4.7 insurance purchased specifically from a company authorized by the laws of Canada or any province to carry on business in Canada or such province;

2.2.4.8 rent of factory or office premises paid to a registered owner in Canada;

2.2.4.9 maintenance and repairs to buildings, machinery and equipment used for production purposes that is executed in Canada;

2.2.4.10 tools, dies, jigs, fixtures and other similar plant equipment items of a non-permanent nature that have been designed, developed or manufactured in Canada;

2.2.4.11 engineering and professional services, experimental work and product or process development work executed and completed in Canada;

2.2.4.12 pertinent miscellaneous factory and office expenses, such as: administrative and general expenses; depreciation with respect to production machinery and permanent plant equipment and the installation costs of such machinery and equipment; and, a capital allowance not exceeding five (5) % of the total capital outlay incurred for buildings in Canada owned by the producer of the work;

2.2.4.13 personal travel expenses, including Canadian carriers, accommodations and meals, for





travel associated with Direct IRB activities in this (insert project name) Contract;

2.2.4.14 fees paid for services not elsewhere specified; and

2.2.4.15 pre-tax net profit upon which Canadian taxes are paid or are payable.

2.3 Costs or Business Activities that are Ineligible for IRB Credit

2.3.1 the value of materials, labour and services imported into Canada;

2.3.2 in the case of Indirect IRB, the value of raw materials and semi-processed goods exported from Canada;

2.3.3 the value of any living, relocation costs and remuneration paid to non-Canadians for work on the Project;

2.3.4 the amount of all Canadian Excise Taxes, Import Duties, Federal and Provincial Sales Taxes, Goods and Services Taxes, Harmonized Sales Taxes and other Canadian duties;

2.3.5 the value of goods and services with respect to which IRB Credit has been received or is being claimed by the Supplier or its Eligible Parties as an IRB to Canada under any other IRB Obligation or agreement;

2.3.6 any proposal or bid preparations costs;

2.3.7 all transportation or travel costs not covered under 2.2.3 or 2.2.4.13;

2.3.8 obligations of the Federal Government (e.g. government furnished equipment (CFX under the Subcontract);

2.3.9 license fees paid by the Canadian IRB Recipient and any on-going royalty payments;

2.3.10 IRB Transactions claimed by a Supplier that pertains to its influence or that of one of its Eligible Parties over any country's purchasing agent/department;

2.3.11 interest costs associated with letters of credit or other financial instruments to support IRB Transactions;

2.3.12 fees paid to lobbyists (as per Canada’s Lobbying Act); and

2.3.13 fees paid to third-party consultants or agents for work related to obtaining IRB Credit against this Subcontract. This includes, but is not limited to, providing advice on the IRB Policy, preparation of IRB Transactions and/or reports, representing the interests of the Supplier to the IRB Authority, and/or searching for potential recipient firms.

PROTECTIVELY MARKED

IRB Transaction Sheet, Rev 0


Agreement #: N/A


Unclassified

Page 1 of 5 Purchaser’s initials: _____ Uncontrolled when printed Supplier’s initials: _____ See disclosure statement on the front of the Subcontract


Transaction Sheet

IRB210



PROTECTIVELY MARKED



Agreement #: N/A


Unclassified


IRB Transaction Sheet IRB210

Purpose

The IRB Transaction Sheet advises the Purchaser of the Direct and/or Indirect IRB Transactions undertaken by the Supplier in fulfilment of its IRB obligations under the Subcontract in order to fulfil the IRB obligations of the Supplier.

References

This DID must be read in conjunction with Schedule A (General Conditions) and Part 11 (IRB) of Schedule D1 (SOW).


This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 11 (Industrial Regional Benefits) of the SOW.

Format and Content

Complete the IRB Transaction Sheet attached as Attachment A to this DID.

PROTECTIVELY MARKED



Agreement #: N/A


Unclassified


Attachment A

IRB Transaction Sheet

0. GENERAL

a. Agreement number b. Supplier Name c. SWBS d. Description of the Work

1. IRB OBLIGOR INFORMATION

Canadian Procurement Project:

Company Name:

IRB Contact Name:

Email:

Telephone:

Address:

City:

Province/State:

Country:

Postal Code:

2. TRANSACTION DETAILS

Title: Number: Date of Submission: Tranche: □ 1 □ 2 □ 3 IRB Transaction Type:

□ Direct □ Indirect

IRB Activity Type: □ Purchase □ Consortium □ University Investment □ Investment Framework □ General Investment □ Technology Transfer □ VCF

Business Activity Type: □ Aircraft □ C4ISR □ CBRNE □ Castings/Mach

ining □ Cyber Security □ Electronics

□ ISS □ IT □ Manufact- uring

□ Munitions □ Power/ Propulsion/

Transmission

□ Prof. Services

□ Ships □ Space □ Soldier Systems

□ Steering/ Navigation

□ Systems/ Integration

□ Training/ Simulation

□ Vehicles □ Weapons Other: Federal Supply Class (FSC) Code:

(see FSC Website: http://www.dispositionservices.dla.mil/asset/fsclist.html) Global Value Chain (GVC):

□ Yes □ No

If yes, provide name of GVC platform and description of eligibility:

http://www.dispositionservices.dla.mil/asset/fsclist.html

PROTECTIVELY MARKED



Agreement #: N/A


Unclassified


3. TRANSACTION DONOR

Company Name IRB Contact Name

Email Telephone Address City Province/State Country Postal Code

NAISC code (See NAISC website - http://www23.statcan.gc.ca/imdb/p3VD.pl?Function=getVDPage1&TVD=118464) Description of Core Capabilities

Tier Level

4. TRANSACTION RECIPIENT


Email Telephone Address City Province Country Postal Code

NAISC code Description of company and core capabilities

Description of impact on recipient

Number of Employees Small and Medium Business? Tier Level

Government Assistance or Participation in Transaction:

Description of Transaction:

http://www23.statcan.gc.ca/imdb/p3VD.pl?Function=getVDPage1&TVD=118464)

PROTECTIVELY MARKED



Agreement #: N/A


Unclassified


5. CONSORTIUM MEMBER (if applicable)


Email Telephone Address City Province/State Country Postal Code

6. IRB ELIGIBILITY CRITERIA

Causality

Eligible Party

Incrementality

Timing

Other – CCV Overview

Other – Level of Technology (Indirect)

8. LIST OF SUPPORTING DOCUMENTATION

Nature of Document Relevance

9. VALUATION AND TIME PHASING

Total Value of Transaction Cdn Content Value (CCV) % of Recipient Estimated Future Sales, if applicable Multiplier, if applicable Total CCV $ of Transaction

(CCV$) Period Direct Indirect SMB Atl Que NOnt Ont West Total CCV

1 2 3 4 5 6 7 8

Totals

7. QUALITY OF TRANSACTION

IRB Report, Rev 0





IRB Report

IRB211




IRB Report, Rev 0

Document #: N/A

Agreement #: N/A


Unclassified Page 2 of 6 Purchaser’s initials: _____ Uncontrolled when printed Supplier’s initials: _____ See disclosure statement on front page

IRB Report IRB211

Purpose

The Industrial and Regional Benefits Report advises the Purchaser of the Supplier’s IRB achievements under the Subcontract.

References

This DID must be read in conjunction with Schedule A (General Conditions) and Part 11 (IRB) of Schedule D1 (SOW).


This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 11 (Industrial Regional Benefits) of the SOW.

Format and Content

Complete the IRB Report attached as Attachment A to this DID.

IRB Report, Rev 0

Document #: N/A

Agreement #: N/A



Attachment A

TEMPLATE – IRB REPORT

GENERAL INFORMATION Project Name:

Subcontractor Name:

VSY Supplier Code:

SWBS number:

Reporting Period:

Date of Report

IC IRB Manager:

PART A

Overview and Status of Work on the Project: Progress Payments: (list all invoices to date, the amount, the date submitted and the status of payment) Changes to the IRB Management Plan:

PART B - For each transaction being reported, describe:

Any changes to the transaction details (such as CCV % or company contact info) Significant achievements and activities

IRB Report, Rev 0

Document #: N/A

Agreement #: N/A



Any delays, problems or achievements shortfalls, with a plan of action to resolve

PART C – For each transaction being reported, include:

The IRB achievement claims for the CURRENT reporting period, with appropriate totals and subtotals for Direct, Indirect, SMB, and each of the Designated Regions. The Subcontractor may use the chart format of their choice.

PART D – For each transaction reported, include:

The IRB achievement claims SINCE THE START OF THE IRB ACHIEVEMENT PERIOD, with appropriate totals and subtotals for Direct, Indirect, SMB, and each of the Designated Regions. The Subcontractor may use the chart format of their choice.

PART E

Description of activities undertaken related to SMB and regional development List of IRB Transactions that have been cancelled or substantially altered (with previous IRB Authority approval) Certificate of Compliance for IRB Achievements (template attached) Certificate of Compliance for the Lobbying Act (template attached)

IRB Report, Rev 0

Document #: N/A

Agreement #: N/A



CERTIFICATE OF COMPLIANCE For IRB Reporting Purposes

WHEREAS Vancouver Shipyards Co. Ltd. (referred to herein as VSY) on the ____ day of _____ has entered into subcontract number ▼[Insert Subcontract Number] (the “Subcontract”) with _________________________ (the “Supplier” or “Subcontractor”).

AND WHEREAS such Subcontract requires that, as evidence of the achievement of Canadian Content Value of Industrial and Regional Benefits Transactions and Commitments, the Supplier shall submit a Certificate of Compliance to that effect to the VSY IRB Official (defined in the Subcontract);

NOW THEREFORE, the Subcontractor declares and certifies as follows:

i) the information contained in the documents appended herewith, which applies to the reporting of the IRB Achievement Periods is to the best of our knowledge and ability complete, true and correct;

ii) the information contained in the documents appended herewith is compliant with information contained in Certificates of Compliance submitted to the Supplier by other Eligible Parties;

iii) The Canadian Content Values shown in documents appended herewith have been determined in accordance with Article 6 (Canadian Content Value) of the Subcontract;

IN WITNESS THEREOF THIS CERTIFICATE OF COMPLIANCE HAS BEEN SIGNED THIS ______________ DAY OF _______________ BY THE SENIOR COMPTROLLER WHO IS DULY AUTHORIZED IN THAT BEHALF.

_______________________________

SIGNATURE

__________________________________________________________

NAME AND TITLE OF SENIOR COMPTROLLER

AT:________________________________

IRB Report, Rev 0

Document #: N/A

Agreement #: N/A



Certificate of Compliance - Lobbying Act for IRB Reporting Purposes

WHEREAS Vancouver Shipyards Co. Ltd. (referred to herein as VSY) on the ____ day of _____ has entered into subcontract number ▼[Insert Subcontract Number] (the “Subcontract”) with _________________________ (the “Supplier” or “Subcontractor”).

AND WHEREAS such Subcontract requires that, as evidence of the Supplier’s compliance with the Lobbying Act, the Supplier shall submit a Certificate of Compliance to that effect to the VSY IRB Official (defined in the Subcontract);

NOW THEREFORE, the Supplier declares and certifies, to the best of its knowledge and ability, as follows:

i) that it has filed all Lobbying Act returns to be filed in respect of persons employed by it who communicate and/or arrange meetings with public office holders as part of their employment duties in respect of the Subcontract, and that it will continue to do so;

ii) that it has not contracted with any person to communicate and/or arrange meetings with public office holders for remuneration that is or would be contingent in any way upon the success of such person arranging meetings with public office holders, or upon the approval and granting of IRB Credit under the Subcontract;

iii) that it will not contract with any person to communicate and/or arrange meetings with public office holders for remuneration that is or would be contingent upon the success of such person arranging meetings with public office holders, or upon the approval and granting of IRB Credit under the Subcontract;

iv) that all persons who are or have been contracted by it to communicate and/or arrange meetings with public office holders in respect to the Subcontract are in full compliance with the registration and other requirements of the Lobbying Act;

v) that it shall at all times ensure that any persons contracted by it to communicate and/or arrange meetings with public office holders in respect of the Subcontract are in full compliance with the requirements of the Lobbying Act; and

vi) that it shall not make or agree to make any payment to an individual, company or entity that is contingent on the approval of IRB Credit by the IRB Authority under the Subcontract or upon the entity’s success in arranging meetings with public office holders.

IN WITNESS THEREOF THIS CERTIFICATE OF COMPLIANCE HAS BEEN SIGNED THIS ______________ DAY OF _______________ BY THE SENIOR OFFICIAL WHO IS DULY AUTHORIZED IN THAT BEHALF. _________________________________ SIGNATURE __________________________________________ NAME AND TITLE OF SENIOR OFFICIAL AT:________________________________

Packaging, Handling and Transportation Plan, Rev 0





Packaging, Handling and Transportation Plan

LOG201



Packaging, Handling and Transportation Plan, Rev 0




Packaging, Handling and Transportation Plan

LOG201

Purpose

The purpose of a Packaging, Handling and Transportation Plan (PHTP), is to make the Purchaser aware of the Supplier’s intentions to facilitate the preservation, safe arrival, acceptability for storage and if applicable, expeditious importation clearance of the Goods. The PHTP also outlines estimated volumes of Packages to be transported and if applicable, special handling requirements during transport and offloading.

References



This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 12 (Logistics) of the SOW.

Format and Content

1 The PHTP shall address how the Supplier intends to preserve, pack and label the Goods for transportation.

2 The PHTP shall, as a minimum, address the following:

(a) if applicable, controlled goods, as defined in the Defence Production Act (the Supplier must identify any controlled goods to the Purchaser and inform the Purchaser of the classification (e.g. ECCN, etc…);

(b) if applicable, Point of Pick Up as defined in the Articles of Agreement;

(c) estimated number of crates/pallets, with individual weights and dimensions (see Schedule E);

(d) protective measures and special handling requirements during transportation for each Item of Equipment;

(e) any special handling/lifting arrangements during unloading at the Purchaser’s Premises (including a Ship); and

(f) full details for items of the Goods, if any, classified as Dangerous Goods.

In Storage Maintenance Plan, Rev 0





In Storage Maintenance Plan

LOG202



In Storage Maintenance Plan, Rev 0




In Storage Maintenance Plan LOG202

Purpose

The purpose of the In Storage Maintenance Plan (ISMP) is for the Supplier to advise the Purchaser of the activities to be undertaken by the Purchaser in order to preserve and maintain the Equipment and SPT while it is stored in the Purchaser’s Warehouse.

References



This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 12 (Logistics) of the SOW.

Format and Content

1 The ISMP shall address the following topics:

(a) the protective measures to be taken for the Equipment and SPT while stored in the Purchaser’s Warehouse; and

(b) measures to be taken in protect assent corrosion, damage, wear and other deterioration including special care to preclude contamination of hydraulic, pneumatic and fluid systems.

2 The ISMP shall provide details of any special storage requirements for the Equipment and/or SPT.

Document Deliverable List, Rev 0

Document #: VSY-A08.22-0126 Agreement #:




Document Deliverable List

CM201




Document Deliverable List, Rev 0

Document #: VSY-A08.22-0126 Agreement #:



Document Deliverable List CM201

Purpose

The Document Deliverable List is intended to provide a list of document deliverables to the Purchaser’s CMDM department so that they can be assigned document numbers as outlined in the Part 13 (CMDM) of the SOW.

References



This Data Item shall comply with the general format, content and preparation instructions set out in Part 1 (Introduction) and Part 13 (Configuration Management / Data Management) of the SOW.

Format and Content

1. The Document Deliverable List shall be prepared in the format and contain the information as outlined in the table below. In the event that multiple documents being submitted for a single Data Item, add each document to this list as a single line.

SDRL ID # Document Title SWBS (if Technical Deliverable)

[*Insert SDRL ID # Reference]

[* Insert name of First Document Deliverable] [* Insert SWBS if a Technical Deliverable ]

[*Insert SDRL ID # Reference]

[* Insert name of Second Document Deliverable] [* Insert SWBS if a Technical Deliverable ]

Etc…

2. The Document Deliverable List shall be submitted with the file naming convention “CM001 – Document Delivery List – Rev0”,

as an exception to file naming convention outlined in Part 13 (CMDM) of the SOW.