(2010-01-11)
"The Department shall operate as a common service agency for the Government of Canada, and its activities as a common service agency shall be directed mainly toward providing the departments, boards and agencies of the Government of Canada with services in support of their programs."
(2010-01-11)
(2010-01-11)
The Manual generally follows the sequence of a typical procurement process. The structure is as follows:
(2010-01-11)
(2010-01-11)
There is one over-arching principle for all PWGSC procurement activities: Integrity. Subordinate to this are guiding principles, which provide the framework for PWGSC procurement process. Contracting officers must always respect these principles, regardless of whether or not the actions are clearly set out in this manual.
(2010-01-11)
PWGSC procurement processes will be open, fair and honest.
(2010-01-11)
All those involved in the procurement process must apply prudence, probity and transparency at each stage of the process.
PWGSC will make every reasonable effort to satisfy the operational requirements of its clients, while obtaining the best value in each procurement process.
PWGSC procurement activities will advance established government policies, within the limits imposed by international trade obligations.
PWGSC procurement will be competitive, with specific exceptions.
PWGSC will ensure that all potential bidders of a particular requirement are subject to the same conditions.
PWGSC is accountable for the integrity of the contracting process. Clients are responsible to ensure that all information relating to their requirements, which is provided to PWGSC, is complete and accurate. (See Annex 1.1.)
(2010-08-16)
Contracting officers must ensure the integrity of the procurement process. If there is any doubt that what is being done (or asked by the client to be done) might bring the integrity of the process into question, the contracting officer should consider suspending the procurement process until the issue is resolved. Issues that cannot be resolved satisfactorily at the contracting officer level must be referred to a higher authority within PWGSC.
The procurement process can be facilitated by advance work being done with clients. This includes helping with needs identification and requirement definition, procurement strategy development, and drafting of solicitation documents before a requisition is actually received. This can be accomplished through ongoing liaison with the client or a review of procurement patterns. These methods can be initiated by a client request for assistance, or by a more formal process of regular consultation.
Contracting officers should consult with colleagues, particularly when working with an unfamiliar situation, such as a new commodity. Their experience and advice may help to arrive at a sound decision. Referring to previous files can also be instructive, particularly for estimating things like business volume under a new contract where there is a current contract covering substantially the same activities.
The contracting officer should keep clients informed and involved, and in order to develop responsive, creative and flexible procurement strategies, their departmental needs must be understood, as well as their specific technical requirement. When consulting the client, make the purpose plain, so that if there is a problem with a proposed approach a solution that achieves the purpose can be developed. The contracting officer must work with the client towards their operational objectives.
The contracting officer should seek advice from the following specialists: Legal Services, policy advisors, Access to Information and Privacy officers, quality control officers, cost analysts and risk management advisors. Specialists are available to provide guidance and recommendations in their areas of expertise.
Contracting officers should be very clear in communications. Written instructions accompanying each bid solicitation, for example, should be clear with no ambiguity, and be easily understood by all parties.
The contracting officer must treat all information of a confidential or personal nature, including bid information, in a secure and confidential manner. This ensures the integrity of the contracting process, and protects the interests of suppliers and clients.
The contracting officer should obtain written confirmation of significant information, agreements and discussions, such as confirmation of an unusually low price, or extension of a bid validity period by the bidder.
Contracting officers should develop their understanding of their commodity's industry, the market conditions, and the pertinent factors of each commodity, which then affects the choices made by contracting officers in determining, for example, such things as the basis of payment and the selection methodology. Clients should also use their understanding of the commodity when defining their technical requirements and scope.
Contracting officers should also keep themselves informed about such things as the proposed contractor's performance history, financial situation and practices, before recommending a contract award. It also means keeping up to date with a contractor during the performance of a contract.
Life Cycle Management of Assets (LCMA) is an integrated approach to materiel management that looks at the process as a complete system rather than separate activities. While this process is primarily the responsibility of materiel managers within client departments, procurement and disposal are a part of this process so contracting officers should discuss with the client the implications of the life cycle management process for each procurement.
Contracting officers should keep files up to date for reasons of good management, access to information requests as well as for audit purposes. Current files should be kept up to date for anyone who may have to consult the file or assume responsibility for it at a later date. See Annex 8.1 for further details.
Contracting officers should use only the templates available on the Departmental Standard Procurement Documents Web site in the procurement process (see 4.15.1.) Contracting officers should obtain from their supervisor the most current standard documents within their respective areas that have been developed in accordance with these templates. Directorates needing assistance in developing documents based on these templates should contact the Procurement Process Tools Division of the Policy, Risk, Integrity and Strategic Management Sector, by e-mail at: outilsapprov.proctools@tpsgc-pwgsc.gc.ca.
(2010-01-11)
The legal framework is comprised of:
They are described in sections 1.20 to 1.35.
(2010-01-11)
(2010-01-11)
(2010-01-11)
(2010-01-11)
(2010-08-16)
(2010-01-11)
In addition to the above statutes, examples of other acts which also apply to contracting for goods and services are as follows:
(2010-01-11)
For all trade agreements, PWGSC is required to comply with specific procedures when completing certain procurements. Therefore a decision must be made as to whether or not the requisition is subject to a particular agreement, or a combination of agreements. To determine coverage under the various trade agreements, the estimated procurement value (including the estimated amount of the Goods and Services Tax or the Harmonized Sales Tax), the client, the type of good or service or construction, and any exceptions or exclusions must be reviewed. Contracting officers should note that when the procurement is covered by more than one agreement, all agreements must be complied with at the same time. In order to accomplish this, the procedures to be followed are the procedures that are considered the most rigorous. For example, for limited tendering reasons, procurement covered by NAFTA, WTO-AGP and AIT, only the limited tendering reasons that are common to all three agreements are available as options.
based on the one that represents more than 50 percent of the estimated value of the requisition.
A procurement may be subject to NAFTA if the requisition value, in Canadian dollars, is as follows:
A procurement may be subject to WTO-AGP if the requisition value in Canadian dollars (including taxes) is as follows for the period January 1, 2010, to December 31, 2011:
(2010-01-11)
(2010-01-11)
Contracting officers should also be aware that a number of National Park Agreements and Department of National Defence Co-operation Agreements have been signed between individual departments and certain aboriginal groups. Reference to these agreements can be found in sections 7 to 10 of Treasury Board Secretariat Contracting Policy Notice 1997-8.
(2010-01-11)
(2010-01-11)
(2010-01-11)
The objective of the Common Services Policy is to ensure that departments and agencies can acquire responsive, cost-effective support for their program delivery. It further provides that client service organizations will offer services to client departments in a manner that is most supportive of timely, effective and economical delivery of programs to the public. PWGSC is identified both as a provider of mandatory common services under Appendix E of the policy, and of optional common services under Appendix F of the policy.
(2010-01-11)
The TB Contracts Directive, issued pursuant to section 10 and paragraph 41(1)(a) of the FAA, sets basic contracting limits for contracting authorities, and provides specific contracting limits for specific ministers. The TB Contracts Directive sets out the limits above which departments must obtain TB approval. The application of the Directive to PWGSC is set out in Chapter 6.
(2010-01-11)
The objective of the Procurement Review Policy is to enhance the use of procurement in support of industrial and regional development and other national objectives in a manner that is fully consistent with the government's approved procurement objectives, and with Canada's international commitments within the General Agreement on Tariffs and Trade, NAFTA or other trade rights and obligations. See 3.70 for further details.
(2010-08-16)
"To comply with the Code of Conduct for Procurement, bidders must respond to bid solicitations in an honest, fair and comprehensive manner, accurately reflect their capacity to satisfy the requirements stipulated in the bid solicitation and resulting contract, submit bids and enter into contracts only if they will fulfill all obligations of the contract. To ensure fairness, openness and transparency in the bidding process, the following activities are prohibited:
By submitting a bid, the Bidder certifies that it meets the above requirements.
Bidders further understand that the commission of certain offences may render them ineligible to be awarded a contract. By submitting a bid, the Bidder declares that it has never been convicted of an offence under Section 121 (Frauds on the government and Contractor subscribing to election fund), Section 124 (Selling or Purchasing Office), Section 380 (Fraud committed against Her Majesty) or Section 418 (Selling defective stores to Her Majesty) of the Criminal Code of Canada, or under paragraph 80(1)(d) (False entry, certificate or return) subsection 80(2) (Fraud against Her Majesty) or Section 154.01 (Fraud against Her Majesty) of the Financial Administration Act."
(2010-01-11)
(2010-01-11)
For assistance with respect to OPO related activities or potential complaints, contracting officers may contact the OPO Coordination Office, by telephone at 819-956-0912.
(2010-01-11)
(2010-01-11)
Contracting officers are delegated authorities from the Minister of Public Works and Government Services Canada (PWGSC) to provide procurement and acquisitions-related services to departments and agencies. See Chapter 6 for further details.
(2010-01-11)
(2010-01-11)
(2010-01-11)
Commodity management is defined by a framework of governance and processes used to review, plan, acquire and control the total life cycle activities of a distinct group of goods and/or services. Use of the commodity management framework results in the award of Pre-competed Procurement Instrument(s), which should meet operational requirements of government departments while providing the optimal cost of ownership and disposal and achieving the best value for Canada. This is in keeping with Canada's commitment to deliver services smarter, faster and at a reduced cost.
(2010-01-11)
Commodity management provides the following:
(2010-01-11)
(2010-01-11)
(2010-01-11)
(2010-01-11)
The Office of Greening Government Operations (OGGO) was created in April 2005 within Public Works and Government Services Canada (PWGSC). OGGO's mandate is to accelerate the greening of the government's operations by working with other federal departments, particularly Treasury Board Secretariat and Environment Canada. OGGO works in conjunction with the Green Procurement Team in Acquisitions Branch (AB), to establish procedures to enhance green procurement within AB and throughout the government.
(2010-01-11)
Note that contracts may still have a security requirement, even though the contractual documents themselves are not designated as PROTECTED/CLASSIFIED.
(2010-08-16)
(2010-01-11)
Note: The matrix does not represent a delegation of procurement authority by the Minister of PWGSC, and it does not remove from contracting officers their overall contracting responsibilities.
L: Lead
C: Contributing
S: Shared
| No. | Activities | Responsibility | |
|---|---|---|---|
| Client | PWGSC | ||
| 1 - Requirements Definition | |||
| 1.1 | Define client's operational requirements: | ||
| 1.1.1 | Define essential characteristics (i.e., Statement of Requirements) | L | C |
| 1.1.2 | Consider all feasible solutions to meet client's operational needs | L | C |
| 1.1.3 | Develop preliminary project cost estimates and schedule | L | |
| 1.1.4 | Conduct cost benefit analysis of alternatives (including life cycle costing analysis) | L | C |
| 1.1.5 | Determine the total resource requirements and implications; for example, training, priority of allocation amongst operational needs and security requirements | L | |
| 1.1.6 | Obtain approval-in-principle to continue with project | L | |
| 1.1.7 | Develop Total Project Plan, including substantive cost estimates and schedules, special project management needs, project phasing, maintenance support requirements, etc. | L | |
| 1.2 | Define client's technical requirements: | ||
| 1.2.1 | Develop Statement of Work (SOW) and/or performance specifications or standards, as appropriate, for the goods/services required in order to meet the operational needs. | L | |
| 1.2.2 | Define the technical requirements for quality assurance, acceptance, warranty, training, documentation, packaging, transportation, initial provisioning, etc. | L | |
| 1.3 | Raise the requisition (form PWGSC-TPSGC 9200): | ||
| 1.3.1 | Prepare the funded requisition for goods/services to be forwarded to PWGSC. Include the Security Requirements Checklist (SRCL), if applicable. | L | C |
| 2 - PWGSC Procurement Plan | |||
| 2.1 | Assess potential sources of supply (Canadian vs. offshore, etc.) | C | L |
| 2.2 | Identify applicable major contracting policy issues/ considerations, which must be resolved to accomplish the procurement. | C | L |
| 2.3 | Examine potential problems in relation to patents, licencing, royalties and technology transfer. | C | L |
| 2.4 | Develop Procurement Plan including: | ||
| 2.4.1 | Delivery schedule and acceptance requirement | L | C |
| 2.4.2 | Contracting approach (including sourcing strategy) | C | L |
| 2.4.3 | Target cost and cash flow plan | C | L |
| 2.4.4 | Statement of appropriate quality and inspection system standards and qualification approvals | L | C |
| 2.4.5 | Communications strategy | C | L |
| 2.4.6 | Contractual risk management | C | L |
| 2.4.7 | Evaluation methodology and selection method | C | L |
| 2.4.8 | Industrial Benefits (IBs), where appropriate | C | L |
| 2.4.9 | Interdepartmental and international agreements related to procurement plan | L | C |
| 2.5 | Obtain Procurement Plan approval. | L | |
| 3 - Contracting Process | |||
| 3.1 | Prepare the translation of procurement documents (the client is responsible for the translation of the SOW and/or performance specifications or standards and technical evaluation criteria) | C | L |
| 3.2 | Prepare and distribute/post procurement notice on GETS (Government Electronic Tendering Service) and the bid solicitation package. | L | |
| 3.3 | Prepare and distribute technical data packages, as required. | L | C |
| 3.4 | Receipt of bids on bid closing. | L | |
| 3.5 | Evaluate technical elements of bids. | L | C |
| 3.6 | Evaluate time, cost and other contractual elements of bids. | L | |
| 3.7 | Prepare consolidated evaluation and selection of the bidder. | C | L |
| 3.8 | Negotiate the contract, where applicable. | C | L |
| 3.9 | Obtain the contract approval. | C | L |
| 3.10 | Prepare and issue the contract. | L | |
| 3.11 | Debrief unsuccessful bidders. | C | L |
| 4 - Contract Administration | |||
| 4.1 | General: | ||
| 4.1.1 | Monitor work of the contractor; and receive the contract deliverables. | L | C |
| 4.1.2 | Monitor the cash flow. | L | C |
| 4.1.3 | Report any problems to the contracting authority. | L | |
| 4.1.4 | Resolve any contractual problems. | C | L |
| 4.1.5 | Monitor compliance with the terms and conditions of the contract. | S | S |
| 4.1.6 | Determine that goods and services received are in accordance with the requirement. | L | C |
| 4.1.7 | Determine that goods and services received are in accordance with the contract. | C | L |
| 4.1.8 | Process the claims for payment. | L | C |
| 4.2 | Contract Amendments: | ||
| 4.2.1 | Identify the need for additional work or revisions; confirm the funding. | L | |
| 4.2.2 | Confirm that the contract amendment is the appropriate vehicle. | L | |
| 4.2.3 | Negotiate the contract amendment. | C | L |
| 4.2.4 | Obtain an approval for amendment/change order. | L | |
| 4.2.5 | Prepare and issue the contract amendment. | L | |
| 5 - Contract Close-out | |||
| 5.1 | Settle the outstanding claims for payment. | C | L |
| 5.2 | Issue the contract closing amendment. | L | |
| 5.3 | Finalize the disposition of Crown assets. | L | |
(2010-01-11)
| CODE | DETAIL | RESPONSIBILITY | |||
|---|---|---|---|---|---|
| PO (Procurement Officer) PM (Project Manager) TA (Technical Authority - includes LCMM) PD (Project Director) M (denotes for MCP or MCP-like projects where role is defined in the PMP) PM/TA - usually the PM for Capital/NP project procurement and the TA for in-service procurement |
PWGSC | DND | PWGSC Normally Participates | DND Normally Participates | |
| 1 - DEFINE DND OPERATIONAL REQUIREMENTS | |||||
| 1.1 | Define essential characteristics - Statement of Capability Deficiency or Statement of Requirement | PD | |||
| 1.2 | Seek procurement input/ advice from DND procurement authority | PO | |||
| 1.3 | Delineate all feasible solutions, within government policy, to meet operational needs (ROM costs) | PD | M | ||
| 1.4 | Identify Total ROM project cost and schedule estimates for SSID | PO | |||
| 1.5 | Obtain operational approval to continue with project (SSID) | PD | |||
| 1.6 | Preparation of cost benefit analysis including life cycle costing analysis of alternatives and uncertainties | PD | |||
| 1.7 | Determine requirement for cooperation & involvement of other Departments/Countries (excluding 3.5.9) | PD | |||
| 1.8 | Determine national and international obligations applicable to operational need | PD | |||
| 1.9 | Determine requirement for phased cycles for project implementation | PM | X | ||
| 1.10 | Determine maintenance and support requirements | PM/TA | X | ||
| 1.11 | Determine total resource requirement for the project | PM | X | ||
| 1.12 | Identify Total Project cost (substantive) and schedule estimates | ||||
| 1.12.1 | Obtain and collate cost and schedule information |
PD/PO | X | ||
| 1.12.2 | Develop Total Project cost and schedule estimates |
PO | |||
| 1.13 | Initiate a PMP (formerly PIP) for project (Responsibility Assignment Matrix) | PM | X | ||
| 1.14 | Develop DND's Procurement Master Plan | PO | |||
| 1.15 | Obtain approval (SRB and PRC/SPAC) | PM | X | ||
| 1.16 | Prepare project submission and obtain approval (PMB, SS PPA and SS EPA, and Project Briefs) | PD/PM & PO | |||
| 1.17 | Prepare Memorandum to Cabinet (for MCP's only) | M | M | ||
| 1.18 | Execute DND's Procurement Master Plan | PO | |||
| 2 - DEFINE TECHNICAL REQUIREMENTS AND RAISE PROCUREMENT INSTRUMENT | |||||
| 2.1 | Establish team (formal or informal as appropriate) for an individual procurement instrument, including required stakeholder | PO | X | ||
| 2.2 | Identify appropriate DND authorities in the PI (e.g. requisition, technical, QA) | PO | |||
| 2.3 | Statement of Work (SOW) | ||||
| 2.3.1 | Define SOW and/or Performance Specifications in support of the operational need |
PM/TA | |||
| 2.3.2 | Identify Earned Value requirements (for MCP's or MCP-like projects) |
M | |||
2.3.3 |
Review and Refine SOW | PO | X | ||
| 2.4 | Define Government Furnished Resources (e.g. tools, test equipment) | PM/TA | |||
| 2.5 | Define Quality Assurance and Acceptance requirements | PM/TA | |||
| 2.6 | Define other technical requirements (e.g. warranty, training, documentation, Initial Provisioning, etc.) | PM/TA | |||
| 2.7 | Define Technical Evaluation Criteria | PM/TA | |||
| 2.8 | Prepare Procurement Instrument and Associated Documents | ||||
| 2.8.1 | Validate cost estimate and secure funding for this PI |
PO | |||
| 2.8.2 | Develop Technical Bid Evaluation Plan |
PM/TA | X | ||
| 2.8.3 | Establish Technical Bid Evaluation Team |
PM/TA | X | ||
| 2.8.4 | Develop proposed procurement schedule (activities and timeline) for this PI |
PM/TA | |||
| 2.8.5 | Identify and mitigate DND risks associated with this PI |
PO | |||
| 2.8.6 | Develop Content of Procurement Instrument |
PO | |||
| 2.8.7 | Review Draft Procurement Instrument |
PO | X | ||
| 2.9 | Approve Procurement Instrument (Requisition) | PO | |||
| 3 - DEVELOP PWGSC PROCUREMENT PLAN (*based on DND Procurement Instrument) | |||||
| 3.1 | Assess the industrial capability* | X | |||
| 3.2 | Identify applicable major contracting policy which must be considered to accomplish procurement* | X | |||
| 3.3 | Review applicable CITT cases and Federal Court Rulings of Procurement | X | PO | ||
| 3.4 | Examine potential problems in relation to patents, licensing, royalties, and technology transfer | X | PM/TA | ||
| 3.5 | Develop Procurement Plan including: | ||||
| 3.5.1 | Delivery schedule and acceptance requirement |
PO | X | ||
| 3.5.2 | Contracting approach* |
X | |||
| 3.5.3 | Target cost and cash flow plan |
PO | |||
| 3.5.4 | Stating of appropriate quality control and inspection system standards and qualification approvals |
PM/TA | |||
| 3.5.5 | Communications Strategy (e.g. press release, etc.) |
X | PM/TA | ||
| 3.5.6 | Risk Management* |
X | |||
| 3.5.7 | Evaluation Methodology* |
X | |||
| 3.5.8 | Industrial and Regional Benefits |
X | PM/TA | ||
| 3.5.9 | Interdepartmental and international agreements related to Procurement Plan (excluding DND/PWGSC) |
PM/TA | X | ||
| 3.6 | Obtain approval of procurement plan | X | |||
| 4 - CONTRACTING PROCESS | |||||
| 4.1 | Review requisition or procurement instrument | X | PO | ||
| 4.2 | Review SOW and Technical Evaluation Criteria for its contractibility | X | PO | ||
| 4.3 | Prepare Solicitation Bid Package | ||||
| 4.3.1 | Identify Applicable Terms and Conditions (including Basis of Payment) |
X | PO | ||
| 4.3.2 | Develop Contractual Evaluation Criteria (time, finance incl. transition, contractual & consolidated evaluation plan) |
X | PO | ||
| 4.3.3 | State appropriate authorities (e.g. requisition, technical, contract, quality, etc., as applicable) |
X | |||
| 4.4 | Dispatch "Solicitation - Bid" (RFP/ITT) documentation to Industry and DND | X | |||
| 4.5 | Distribute technical data packages to suppliers as required and as applicable | PM/TA | X | ||
| 4.6 | If competitive (RFP, ITT or equivalent process), Evaluate Bids and Recommend Supplier | ||||
| 4.6.1 | Carry out Technical evaluation (SOW and associated t's & c's) in accordance with the Evaluation Plan |
PM/TA | X | ||
| 4.6.2 | Carry out Contractual evaluation (including contract t's & c's) in accordance with the Evaluation Plan |
X | M | ||
| 4.6.3 | Consolidate evaluation and recommend supplier |
X | PO | ||
| 4.7 | If sole-source, Negotiate contract | X | PO&PM/TA | ||
| 4.8 | Review draft contract documentation | PO | |||
| 4.9 | Obtain TB or Departmental contract approval, as required | X | M | ||
| 5 - CONTRACT ADMINISTRATION | |||||
| 5.1 | Initiate Contract Administration | ||||
| 5.1.1 | Implement Tools and Processes for Administration |
X | PO | ||
| 5.1.2 | Kick-Off Meetings with Parties, Stakeholders |
X | PO&PM/TA | ||
| 5.2 | Provide Government Furnished Resources (GFR) in Support of Contract Work | PO | X | ||
| 5.3 | Ascertain Contract Performance | ||||
| 5.3.1 | Technical and Quality of the Deliverables |
PM/TA | |||
| 5.3.2 | Contractor's Engineering, Production and Quality Systems |
PM/TA | |||
| 5.3.3 | Contractor's Financial and Management Systems |
X | |||
| 5.3.4 | Contract Cash Phasing/ Cash Flow |
||||
| 5.3.4.1 | Cash Flow Actual versus Contracted Cash Flow |
X | M | ||
| 5.3.4.2 | Cash Flow Actual versus DND Planned Cash Flow for Financial Forecast |
PO | |||
| 5.3.4.3 | Earned Value (monitor progress of work versus planned work and associated cost) for MCP's |
X | M | ||
| 5.3.5 | Delivery |
||||
| 5.3.5.1 | Monitor materiel and services delivery date |
PO | |||
| 5.3.5.2 | Acceptance Trials and Tests |
PM/TA | |||
| 5.3.5.3 | Schedule compliance |
X | M | ||
| 5.3.6 | Progress Review Meetings |
||||
| 5.3.6.1 | Requirements/Technical Work Group Meetings |
PM/TA | X | ||
| 5.3.6.2 | Contract Progress Review Meetings with Contractor |
X | PO&PM/TA | ||
| 5.4 | Apply Contract Provisions and Processes | ||||
| 5.4.1 | Interpretation and Notifications |
X | |||
| 5.4.2 | Change Control |
||||
| 5.4.2.1 | Technical (Engineering Change Notices/Proposals) |
PM/TA | |||
| 5.4.2.2 | Contract Amendments |
X | PO | ||
| 5.4.3 | Warranty Provisions |
||||
| 5.4.3.1 | Invoke Warranty |
PM/TA | |||
| 5.4.3.2 | Enforce Warranty |
X | |||
| 5.4.4 | Contractual Issues |
||||
| 5.4.4.1 | Identify contractual issues |
X | PO | ||
| 5.4.4.2 | Enforce contractual issues |
X | |||
| 5.4.5 | Accept Contract Deliverables |
PM/TA | |||
| 5.4.6 | Certify and Process Payments |
X | PO | ||
| 5.5 | Close Out Contract | ||||
| 5.5.1 | Crown Asset Disposition |
PO | X | ||
| 5.5.2 | Final Contract Audit |
X | |||
| 5.5.3 | Final Payment and Amendment |
X | PO | ||
It does not deal with materiel and services to non-military specifications (see Section A) or with the division of responsibilities for materiel and services managed by an interdepartmental project management office, which are the subject of a separate agreement.
Materiel and services to military specifications: Includes all materiel and services, including repair and overhaul, as well as research and development for which a military or other DND specification or requirement is included in procurement documents. Also included in this category are materiel and services which are not covered by DND or military specifications but which are of sufficiently significant concern to DND as to require the division of responsibilities annotated under this heading.
Where participation by the other department is indicated, the responsible department is expected to initiate the consultation. However, it does not preclude either department from requesting participation in, or consultation on, any given subactivity relative to an established program.
Quality assurance services which support achievement of the quality of design, its practicality for manufacture and the means by which conformance will be demonstrated. The tasks involve participation in:
A.1
The evaluation with DND of technical data for completeness, clarity, freedom from irrational or excessive tolerances, contradictions, over stipulation of quality requirements, ability to meet interface requirement, etc.
A.2
Review of design to determine completeness of definition, the methods for demonstrating conformance and analysis of system effectiveness of such major elements as:
A.3
Establishment and definition of test methods with respect to practicality, suitability and cost as related to:
Responsibility for Sub-activity - DND
Normally Participates in Sub-activity - PWGSC
A.4
Applicability of technical data to current programs of maintenance, repair and overhaul and reprovisioning.
Responsibility for Sub-activity - DND
A.5
Selection of parts, components or process, with avoidance of those which are difficult to control, subject to excessive variation or high failure rate, etc.
Responsibility for Sub-activity - DND
Normally Participates in Sub-activity - PWGSC
A.6
Classification of quality characteristics with respect to their importance to design objectives.
A.7
Designation of quality control and inspection system standards.
A.8
Definition of preferred warranty requirements.
A.9
Establishment of requirements for technical reports from suppliers.
Responsibility for Sub-activity - DND
Develop, support and maintain programs conducive to efficient procurement and quality assurance which includes such tasks as:
B.1
Development as appropriate of contractor quality system standards/specifications for contract use.
B.2
Maintenance of qualified/approved product programs.
B.3
Evaluation of the acceptability of suppliers' quality control/inspection systems, commercial test, laboratory and calibration facilities.
Responsibility for Sub-activity - DND
Normally Participates in Sub-activity - PWGSC
B.4
Selection of suppliers with acceptable quality control/inspection systems, commercial test, laboratory and calibration facilities.
Responsibility for Sub-activity - PWGSC
Normally Participates in Sub-activity - DND
Quality assurance tasks associated with requisitioning (contract demands, local purchase orders).
C.1
Review of the requisition with DND for applicability of the technical data.
Responsibility for Sub-activity - DND
Normally Participates in Sub-activity - PWGSC
C.2
Development of Quality Assurance Plan.
C.3
Assurance that workmanship standards are established.
C.4
Determine which contractor quality control/inspection requirements are applicable.
C.5
Responsibility for Sub-activity - DND
C.6
Develop and include special clauses of significance to the assurance of quality.
Responsibility for Sub-activity - DND
Normally Participates in Sub-activity - PWGSC
Quality assurance tasks associated with the preparation of bid solicitations.
D.1
Review of quality requirements on the requisition for completeness and clarity.
Responsibility for Sub-activity - DND
D.2
Establishment of criteria for the evaluation of bids/proposals for compliance with quality requirements.
D.3
Review of past performance of potential bidders in respect of their quality history, to determine potential suppliers.
D.4
Explanation of quality requirements at the prebidders' conference.
Responsibility for Sub-activity - PWGSC
Normally Participates in Sub-activity - DND
Quality assurance tasks associated with evaluation and supplier selection in relation to:
E.1
Evaluation of bidders' quality capabilities based upon their quality history and pre-award survey of their quality control/inspection systems.
E.2
Evaluation with DND of the quality/quality assurance implications of selecting alternative products.
E.3
Trade-off analysis of performance cost and schedule.
Responsibility for Sub-activity - DND
Normally Participates in Sub-activity - PWGSC
Quality assurance tasks associated with contract preparation and final award in relation to:
F.1
Resolution of negotiations with contractor on quality-cost matter not finalized at the bid evaluation stages and review of contract quality requirements to ensure mutual understanding
F.2
Verification with DND that the contract includes the required quality system requirements.
Responsibility for Sub-activity - PWGSC
Normally Participates in Sub-activity - DND
Performance of the following activities in support of PWGSC contract administration throughout the duration of the contract, as applicable:
G.1
Quality Assurance Verification of the continuing effectiveness of the contractor's methods for controlling his product quality. These elements are:
G.2
G.3
Quality assurance action in technical change procedures such as initiation, and recommendation.
G.4
Review of contract quality requirement with contractor to ensure mutual understanding.
Responsibility for Sub-activity - DND
Normally Participates in Sub-activity - PWGSC
Quality assurance tasks performed during contract close-out and clean-up:
H.1
Verification from DND of the condition and disposition of Crown-owned production tooling, inspection and test equipment
H.2
Verification from DND of the completeness, suitability and proper disposition of technical data and documentation.
Responsibility for Sub-activity - DND
Normally Participates in Sub-activity - PWGSC
Quality assurance tasks arising during the life of the product in relation to:
I.1
Quality History
I.2
Unsatisfactory Condition Report/Complaints
Responsibility for Sub-activity - DND
Normally Participates in Sub-activity - PWGSC
Quality assurance tasks related to the disposal of equipment and data.
Quality assurance tasks associated with the development of a quality program which, will assure product quality on receipt, during storage and on issue, including such elements as:
K.1
Preparation of Inspection Plans, including inspection on receipt, during storage, on issue and after repair.
K.2
Control of technical data.
K.3
Control of adequacy of inspection equipment.
K.4
Incoming inspection.
K.5
Identification of defective material.
K.6
Procedures for material handling.
K.7
Packaging and shipping.
K.8
Inspection records.
K.9
Quality audit.
K.10
Corrective action.
Responsibility for Sub-activity – DND
1 The matrix does not represent delegation of procurement authority by the Minister of PWGSC, and does not affect the responsibility of the contracting officer as defined in Treasury Board Contracting Policy.
Legislation, regulations and policy will take precedence over this matrix in the case of any ambiguity. (Back)