TECHNICAL REVIEWS MANUAL

https://drive.google.com/open?id=1VG3AXKkhL-MIoBrOJazfOSwpbvxu-NfD

System and Subsystem Reviews

Technical reviews may take place at either the system or the sub-system level,

dependent on the structure of the project and the timing of specific elements of the task.

The initial reviews, covering the SCR and the SDR, should take place at system level if

they are to be effective in ensuring that the project definition properly recognises the total

set of requirements, as well as the integration and interfaces between elements of the

task. The SDR may be preceded by sub-system level reviews if this is necessary due to

the complexity of the task.

System Concept Review

The System Concept Review (SCR) is carried out during feasibility stage after the

preparation of a detailed statement of requirement for the project, but prior to a Request

for Tender (RFT) being released. It is normally only applicable for large-scale high

complexity projects such as a new line or major reconfiguration of existing infrastructure.

The primary purpose of the SCR is to determine whether the operational, engineering

and support requirements for the asset have been fully defined and that the requirements

of the proposed RFT provide a sound and comprehensive statement of the product and

services required within a contract.

Purpose

The purpose of the System Concept Review (SCR) is to determine whether the

operational, engineering and support requirements for the proposed acquisition project

have been fully defined and that the resultant specifications and Request for Tender

(RFT) provide a sound basis for ensuring that customer requirements can be met.

The specifications and the requirements of the contract arising from an RFT form the

primary basis for all technical review activity carried out as part of the project. It follows

that the success of the review process depends directly on the effort invested in bringing

these documents to a high standard prior to letting a contract.

13.2 Scheduling the review

Review of the requirements to be included in the SCR may take place progressively as

part of the lead-up effort to preparing a final version of the RFT. However it is important

that a final, formal, SCR should take place, to provide the opportunity for multi-disciplinary

review of the final requirements and the structure of the total contract task. This review

often reveals inconsistencies in the requirement which may not be evident from

independent “small group” reviews.

Scheduling of the formal SCR should provide sufficient time for corrective action to be

taken and for changes to be made to the documentation prior to final release. There is

little purpose in conducting the review unless this outcome can be assured.

Ideally the review should be scheduled two to three weeks ahead of the planned release

date for the RFT and at the stage where the specification and technical requirements of

the Statement of Work exist in at least advanced draft form. Any shorter period imposes

major constraints on the process and planning for the preparation and release of the RFT

should include a firm milestone for conduct of the SCR.

General guidelines

The primary focus of the SCR is to ensure that the requirements specified for the

proposed acquisition are realistic, complete and cohesive.

In most cases this does not require minute examination of specification requirements but

rather assurance that the total set of requirements has been specified in a way which

meets operating and performance needs by the most efficient means.

Most importantly, the SCR provides a final opportunity to review and assess the

statement of requirement which represents the performance requirement for a binding

contract. Decisions taken at this point have the potential to lead to a contract which

provides a sound basis for contractor performance and customer satisfaction, or one

which leads to an inferior product and/or to a large number of variations and the attendant

increase in total project cost.

System Definition Review

14.1 Purpose

The purpose of the System Definition Review (SDR) is to verify that the requirements of

the contract task have been assessed and understood by the contractor, subsequent to

contract award. The review is carried out to ensure that possible uncertainties and

misunderstandings are resolved as early as possible in the contract and before work

commences on the detail design process.

Celem przeglądu definicji systemu (SDR) jest sprawdzenie, czy wymagania zadania kontraktowego zostały ocenione i zrozumiane przez wykonawcę po udzieleniu zamówienia. Przegląd przeprowadza się w celu zapewnienia możliwych niepewności i

nieporozumienia są rozwiązywane jak najwcześniej w umowie i przed rozpoczęciem prac nad procesem projektowania szczegółowego.

14.2 Scheduling

The SDR should be scheduled as soon as practicable after the contract has started, but after a sufficient time to permit the contractor to have completed a preliminary design synthesis. This period varies between projects and the actual time should be set by

agreement with the contractor.

14.2 Planowanie

SDR powinien być zaplanowany tak szybko, jak to możliwe po rozpoczęciu umowy, ale po upływie wystarczającego czasu, aby umożliwić wykonawcy wykonanie wstępnej syntezy projektu. Okres ten różni się w zależności od projektu, a rzeczywisty czas powinien zostać ustalony w porozumieniu z wykonawcą.

14.3 Responsibilities

The Project Manager is responsible for arranging the SDR and for establishing the agenda for the meeting. The SDR meeting should be chaired by the Project Manager. Agenda items raised by the contractor should be advised to participants in advance of the meeting, to allow time for review and internal resolution of any requirements.

14.4 Participants

Participants in the SDR are nominated by the Project Manager or Principal Engineer as appropriate and should be selected on the basis of their responsibility for some aspect of the project task.

Potencjalni czytelnicy (Uczestnicy)

Uczestnicy SDR są odpowiednio wyznaczani przez kierownika projektu lub głównego inżyniera i powinni być wybierani na podstawie ich odpowiedzialności za niektóre aspekty zadania projektowego.

14.5 Prerequisites

The prerequisite for the review is the delivery of design and documentation as required by

the contract (refer EPD 0013 Appendix A).

14.6 Exit criteria and objectives

Exit criteria should be established by the Project Manager in advance of the SDR, to

reflect specific circumstances of the contract.

14.7 Specific outcomes

Specific outcomes of the SDR are a direct function of the issues raised at the review.

Under normal circumstances the review identifies a number of aspects requiring

clarification which should be accepted as action items, either by the Project Manager or

the contractor.

A specific target date should be agreed for completion of each action item, to ensure that

the project is not delayed and to avoid any potential for later claims for excusable delay,

due to lack of clarity in the requirement.

The SDR should establish the preliminary Functional Baseline for the project, for

confirmation at the PDR.

General guidelines

The SDR process is intended primarily as an opportunity to review, discuss and resolve

any aspect which may lead to unnecessary conflict and delays in the development

process later in the project.

Proces SDR ma przede wszystkim być okazją do przeglądu, omówienia i rozwiązania wszelkich aspektów, które mogą prowadzić do niepotrzebnego konfliktu i opóźnień w procesie rozwoju w późniejszym okresie projektu.

Operational Requirement

Wymagania operacyjne

Functional Requirement

Wymagania funkcjonalne

Operating Concept

Koncepcja operacyjna

Maintenance and Support Concept

Koncepcja konserwacji i wsparcia

Service Life

Environmental Specification

Specyfikacja środowiskowa

Operational Interfaces

Interfejsy operacyjne

Program Requirements

Wymagania programowe

Program Schedule

Harmonogram programu

Designed Reviews

Specific Reviews Nominated

Defined Scope 

Responsibilities

Contract Milestones

Kamienie milowe umowy

Quality Assurance

Zapewnienie jakości

Specified Standard

Test Articles

Alignment with

Configuration Management

Zarządzanie konfiguracją

• Review initial proposals for designation of configuration items.

• Review initial proposals for specification hierarchy, if appropriate for the program.

• Agree basis for establishing the Functional Baseline. 

NOTE: The above aspects are closely associated with discussion of the status of the functional specification and also preliminary design synthesis. These are covered under systems engineering and may be combined in a single topic.

• Przejrzyj wstępne propozycje wyznaczenia elementów konfiguracji.

• Przejrzyj wstępne propozycje hierarchii specyfikacji, jeśli jest to właściwe dla programu.

• Zgadzam się z podstawą do ustalenia funkcjonalnej linii bazowej.

UWAGA: Powyższe aspekty są ściśle związane z omówieniem statusu specyfikacji funkcjonalnej, a także wstępnej syntezy projektu. Są one objęte inżynierią systemów i mogą być połączone w jednym temacie.

Documentation

Dokumentacja

Specified Requirement (General)

Określone wymagania (ogólne)

Systems Engineering

Inżynieria systemowa

Design Specification

Specyfikacja projektowania 

Design Standards

Standardy projektowania

Requirements Traceability

Design Synthesis

Status of Development Task

Synteza konstrukcyjne

Status zadania rozwojowego

Standardisation

standaryzacja

Interface Definition and Management ?

Review contractors understanding and assessment of defined interface specifications and documents.

• Review proposed means of interface control, particularly where major subcontractors are involved in the project.

Definicja interfejsu i zarządzanie

Przejrzyj zrozumienie kontrahentów i ocenę określonych specyfikacji interfejsów i dokumentów.

• Przegląd proponowanych środków kontroli interfejsu, w szczególności w przypadku, gdy w projekt zaangażowani są główni podwykonawcy.

Drawings and Documentation

Standards Delivered Documents ?

Rysunki i dokumentacja

Software

Oprogramowanie

Integrated Support Concept

Koncepcja Zintegrowanego Wsparcia

Maintenance / Inspection Requirements

Wymagania Konserwacja / inspekcyjne

Spares Support

Części zamienne Wsparcie

Training

Szkolenie

Support Equipment

Sprzęt pomocniczy

Facilities

Udogodnienia

Operating and Support Documentation

Dokumentacja obsługi i wsparcia

Packaging

Opakowanie

Verification and Test

Planning Verification and Test

Planowanie weryfikacji i testów

Integration

Integracja

Qualification

Kwalifikacja

First article inspection

https://en.wikipedia.org/wiki/First_article_inspection

Commissioning

Uruchomienie