As 7718-2017

AS 7718:2017
Signal Design Process

Management
Train Control Systems Standard

AS 7718:2017
Management
This Australian Standard® AS 7718 Signal Design Process Management was prepared by a RISSB Development
Group consisting of representatives from the following organisations:
ARTC ASA AECOM
Brookfield Rail Rio Tinto QR
ARTC
The Standard was approved by the Development Group and the Train Control Standing Committee in December,
2016. On January 25, 2017 the RISSB Board approved the Standard for release.
This standard was issued for public consultation and was independently validated before being approved.
Development of the standard was undertaken in accordance with RISSB’s accredited process. As part of the
approval process, the Standing Committee verified that proper process was followed in developing the standard.
RISSB wishes to acknowledge the positive contribution of subject matter experts in the development of this standard.
Their efforts ranged from membership of the Development Group through to individuals providing comment on a draft
of the standard during the open review.
I commend this standard to the Australasian Rail Industry as it represents industry good practice and has been
developed through a rigorous process.
Paul Daly
Chief Executive Officer
Rail Industry Safety and Standards Board
Keeping Standards up-to-date

Australian Standards developed by RISSB are living documents that reflect progress in science, technology and
systems. To maintain their currency, Standards are reviewed every seven years, and new editions are published.
Between editions, amendments may be issued. Australian Standards developed by RISSB may also be withdrawn.
It is important that readers assure themselves they are using a current RISSB Standard, which should include any
amendments that may have been issued since the Standard was published. Information about Australian Standards
developed by RISSB, including amendments, can be found by visiting www.rissb.com.au
RISSB welcomes suggestions for improvements, and asks readers to notify us immediately of any apparent
inaccuracies or ambiguities. Members are encouraged to use the change request feature of the RISSB website at:
http://www.rissb.com.au/products/. Otherwise, please contact us via email at info@rissb.com.au or write to Rail
Industry Safety and Standards Board, PO Box 4271, Kingston, ACT 2604.
RISSB ABN 58 105 001 465 Page 1

Accredited Standards Development Organisation
AS 7718:2017
Management
AS 7718:2017
Signal Design Process Management
Document Details
First published as: AS 7718:2017 Signal Design Process Management
ISBN 978-1-76035-852-5
Published by Rail Industry Safety and Standards Board (RISSB) ABN: 58 105 001 465
PO Box 4271, Kingston, ACT, Australia 2604
Copyright
©RISSB
All rights are reserved. No part of this work may be reproduced or copied in any form or by any means, electronic or
mechanical, including photocopying, without the written permission of RISSB, unless otherwise permitted under the
Copyright Act 1968.
Notice to Users
This RISSB product has been developed using input from rail experts from across the rail industry and represents
good practice for the industry. The reliance upon or manner of use of this RISSB product is the sole responsibility of
the user who is to assess whether it meets their organisation’s operational environment and risk profile.
RISSB ABN 58 105 001 465 Page 2

AS 7718:2017
Management
Document Control
Identification
Document Title
AS 7718:2017 Signal Design Process Management
Document History
Publication Version Effective Date Reason for and Extent of Change(s)
2017 January 25, 2017 First publication
Approval
Name Date
Rail Industry Safety and Standards Board (RISSB) 25/01/2017
RISSB ABN 58 105 001 465 Page 3

AS 7718:2017
Management
Contents
1 Introduction......................................................................................................................7
1.1 Purpose .............................................................................................................7
1.2 Scope ................................................................................................................7
1.3 Exclusions .........................................................................................................7
1.4 Compliance........................................................................................................7
1.5 Referenced documents .....................................................................................8
1.6 Definitions ..........................................................................................................8
2 Stakeholder requirements definition ..............................................................................10
2.1 Purpose ...........................................................................................................10
2.2 Outcomes/deliverables ....................................................................................10
2.3 Activities and tasks ..........................................................................................11
2.4 Stakeholder requirements report .....................................................................12
3 Requirements analysis process ....................................................................................12
3.1 Purpose ...........................................................................................................12
4 Concept design process ................................................................................................13
4.1 Purpose ...........................................................................................................13
5 Detailed design process ................................................................................................16
5.1 Purpose ...........................................................................................................16
5.1.1 The detailed design process............................................................................16
5.1.2 Base design .....................................................................................................17
5.1.3 System requirements specification ..................................................................17
5.2.1 The detailed design process (implementation) ................................................18
5.2.2 Interfaces .........................................................................................................18
5.2.3 The detailed design process............................................................................18
5.2.4 Procedures and manuals.................................................................................18
5.2.5 Design management plan................................................................................19
5.3.1 Detailed design process ..................................................................................19
5.3.2 Parallel processes ...........................................................................................20
5.3.3 Parallel alterations ...........................................................................................21
5.3.4 Design management plan................................................................................21
5.3.5 Checking inputs ...............................................................................................21
5.3.6 Design deliverable plan ...................................................................................21
5.3.7 Design considerations .....................................................................................21
RISSB ABN 58 105 001 465 Page 4

AS 7718:2017
Management
5.3.8 Design outputs.................................................................................................22

5.3.9 Method of documentation ................................................................................22
6 Independent checking process ......................................................................................22
6.1 Purpose ...........................................................................................................22
6.2.1 Checking process ............................................................................................23
6.3.1 Independent check process.............................................................................24
6.3.2 Design/ technical requirements .......................................................................24
6.3.3 Rework ............................................................................................................25
6.3.4 Independent checking guide............................................................................25
6.4 Validation purpose ...........................................................................................25
7 Approvals and responsibilities .......................................................................................25
7.1 Purpose ...........................................................................................................25
7.1.1 Interface management.....................................................................................25
7.1.2 Construction management ..............................................................................25
7.2.1 Design approval levels and definitions ............................................................25
7.2.2 Responsibilities................................................................................................26
7.3.1 Design approval process .................................................................................26
7.3.2 Production, updating and distribution of commissioning copies ......................26
7.3.3 Delivery of as-built documentation ..................................................................26
8 Design processes - general ...........................................................................................26
8.1 Competency ....................................................................................................26
8.2 Responsibilities................................................................................................27
9 Design changes and configuration management ..........................................................27
9.1 Purpose ...........................................................................................................27
9.3.1 Modification to approved design and engineering details ................................28
9.3.2 Modification sheets- method............................................................................28
9.3.3 Other document update for modifications........................................................28
RISSB ABN 58 105 001 465 Page 5

AS 7718:2017
Management
Appendix Contents
Appendix A System design process overview ....................................................................29
Appendix B Signaling design management standard lifecycle ...........................................30
Appendix C Safety in design ...............................................................................................31
C.1 Purpose ...........................................................................................................31
C.2 Outcomes/deliverables ....................................................................................31
C.3 Activities and tasks ..........................................................................................31
RISSB ABN 58 105 001 465 Page 6

AS 7718:2017
Management
1 Introduction
1.1 Purpose
The objective of this standard is to provide the Australian rail industry with a set of mandatory
and recommended requirements for the signalling design management process. The main
purpose is to promote a consistent approach to the signalling design process across the
Australian rail industry.
This comprehensive process, if well implemented will substantially reduce the issues when
developing the design as all aspects are considered in this process which will lead to –
(a) shortening of the implementation period;
(b) reduce the need for redesign;
(c) enable transferability of people;
(d) having a standard process;
(e) reduction in errors;
(f) potential reduction in costs.
The standard is intended to –
(a) provide a uniform basis for compliance with AS 7702 Railway Safety
Management;
(b) be able to cover differing rail operations across Australia;
(c) identify the risks (hazards) being controlled;
(d) ensure that the standards survive a change in RIM.
1.2 Scope
This Standard specifies the process for the production of signalling designs for use on the rail
networks. This document describes the process for complete signalling system design from
concept through detailed design, construction, installation, test and commissioning and final as-
built documentation. It describes a process which can be part of a wider engineering project, or
which can be implemented as a stand-alone signalling engineering activity.
An overview of the system design process is provided in Appendix A.
This Standard is intended to be used by Infrastructure Managers, Operators and Suppliers of
railway systems.
1.3 Exclusions
The standard includes all processes although some projects will not require every process. This
will be subject to agreement between RIM, client and standards authority.
1.4 Compliance
There are two types of control contained within RISSB Standards:
(a) Mandatory requirements.
(b) Recommended requirements.
Each of these types of control address hazards that are deemed to require controls on the basis
of existing Australian and international Codes of Practice and Standards.
RISSB ABN 58 105 001 465 Page 7

AS 7718:2017
Management
A mandatory requirement is a requirement that the standard provides as the only way of
treating the hazard.
Mandatory requirements are identified within the text by the term shall.
A recommended requirement is one where the standard recognises that there are limitations to
the universal application of the requirement and that there may be circumstances where the
control cannot be applied or that other controls may be appropriate or satisfactory, subject to
agreement with the Rolling Stock Operator, Rail Infrastructure Manager and/or Rail Safety
Regulator.
Recommended clauses are mandatory unless the RIM or RSO can demonstrate a better
method of controlling the risk.
Recommended requirements are to be considered when compliance with the standards is being
assessed.
Recommended requirements are identified within the text by the term should.
Hazards addressed by this standard are included in an appendix. Refer to the RISSB website
for the latest Hazard Register Guideline: www.rissb.com.au
1.5 Referenced documents

The following referenced documents are indispensable for the application of this Standard:
ISO 9241-11 Ergonomic requirements for office work with visual display terminals (vdts) — Part
11: Guidance on usability
ISO 13407 Ergonomics — Ergonomics of human-system interaction — Human-centred design
process for interactive systems.
AS 7702 Rail Equipment Type Approval
EN50126 Railway Applications - The specification and Demonstration of Reliability, Availability,
Maintainability and Safety (RAMS)
EN50128 Railway Applications - Communication, Signalling and Processing Systems - Software
for Railway Control and Protection Systems
EN50129 Railway Applications Communication, Signalling and Processing Systems - Safety
Related Electronic Systems for Signalling
1.6 Definitions
As-built drawings: a revised set of drawings and design documentation including system data
submitted by the constructor upon completion of a particular design job. They reflect all changes
undertaken during the implementation. These should also reference existing drawings that were
not changed.
Derogation: Concession; waiver.
Design Authority: Any organisation with the authority to undertake design, testing,
commissioning, construction, maintenance of signalling plans.
Design Checker: A suitably experienced and competent Signalling Designer who is
responsible for checking that the prepared signalling design is safe and reliable and in
accordance with standard signalling principles and practices, and is operationally functional as
specified. Also, referred to as Design Reviewer.
RISSB ABN 58 105 001 465 Page 8

AS 7718:2017
Management
Design Management Plan (DMP): (Design Development Plan; Design Package Brief; Detailed
Design Plan) A DMP is be used to co-ordinate, monitor and control design activities such as
design responsibility, schedule of drawings, design program, design estimate, procedures for
design changes.
Designer: A suitably experienced and competent person who is responsible for preparing
signalling design that is safe, reliable and in accordance with standard signalling principles and
practices and operationally functional as specified.
Drawings: Drawings shall be defined in this context as site specific or standard documented
layouts, plans, diagrams, tables, schematics, final arrangements and the like that set out the
design and/or configuration of signalling infrastructure assets (e.g. Physical dimensions and
compositions, temporal and/or spatial arrangements, physical and/or logical interconnections)
either existing, pre-existing, or proposed.
Overlapping Design or Alteration: A special case of parallel design, involving activities
relating to more than one alteration or design group. This is only permitted where one engineer
is identified as having overall responsibility for the interface between the successive design
alterations.
Parallel Design: Design, in which activities that would usually be undertaken sequentially, are
undertaken concurrently - (Also see Overlapping Design) or Design undertaken in a
compressed timescale such that activities relating to the same alteration which would usually be
undertaken sequentially are undertaken concurrently.
Project Manager: Is the person who is responsible for planning and monitoring, administration
and control of a project works.
RAM: Reliability, Availability, Maintainability and Safety
Signalling Plan: A longitudinally scaled or dimensioned track layout plan showing the Signalling
Functions with their identities. It generally relates to a specific Interlocking control area(s). May
also be known as a Signalling Arrangement Plan.
SFAIRP: So far As Is Reasonably Practicable
System Requirements Specification: (Term used for Signalling Requirements Specification or
Signalling Functional Specification or Scope of Works) shall specify track infrastructure, train
operations, Maintenance Requirements, Speed Signs, Signalling Equipment, Signalling
Configuration, ATP Systems (if any), Headway analysis, Power reticulation and AIR systems
etc.
The Rail Safety National Law: A National Rail Safety Legislation administered by the Office of
the National Rail Safety Regulator
Train Control System: One or more microprocessor based operator interface stations with the
processing capacity to handle route setting, automatic route setting, train tracking, train
describing, train reporting, event logging and all similar functionality.
Validation: Validation is a process. It uses objective evidence to confirm that the system
operational performance meets the user requirements specified. Whenever the specified
requirements have been met, a verified status is achieved.
Verification: Verification is a process. It uses objective evidence to confirm that the system
design meets the scope and design inputs specified. Whenever the specified requirements have
been met, a verified status is achieved.
WHS: Work Health and Safety
RISSB ABN 58 105 001 465 Page 9

AS 7718:2017
Management
2 Stakeholder requirements definition

2.1 Purpose
The purpose of the stakeholder requirements definition phase is to –
(a) define what the operational requirements are;
(b) define what the interfaces are (system boundary);
(c) establish the application conditions and constraints;
(d) identify the relevant RIM standards applicable.
Alternatively, or additionally –
(a) define the scope of the hazard analysis;
(b) establish the RAMS policy for the system;
(c) establish the safety plan for the system.
2.2 Outcomes/deliverables
The stakeholder requirements definition shall –
(a) define the scope of the hazard analysis;
(b) establish the RAMS policy for the system;
(c) establish the safety plan for the system;
(d) specify required characteristics and context of use of train services,
operational concepts and dependability;
(e) define the constraints on a system solution;
(f) ensure all requirements can be traced to at least one stakeholder, and
(g) define stakeholder requirements (including validation).
Stakeholder requirements shall clearly define what the system should do and avoid.
So far as is possible, stakeholder requirements should define how those requirements are to be
achieved
The stakeholder requirements definition shall specify –
(a) operations relating to human factors;
(b) method of train operations;
(c) traffic levels at time of commissioning;
(d) future changes to traffic levels;
(e) train types;
(f) track design parameters;
(g) special /exceptional /out of course train operations;
(h) level crossings (for each level crossing);
(i) train / wagon stabling;
(j) staging of construction and commissioning;
RISSB ABN 58 105 001 465 Page 10

AS 7718:2017
Management
(k) infrastructure;
(l) specific train operation hazards (e.g. flammable loads);
(m) specific infrastructure hazards (e.g. Gas pipeline);
(n) environmental;
(o) WHS.
2.3 Activities and tasks

The RIM shall identify each stakeholder and their representatives for the purposes of defining
their requirements.
The RIM shall define stakeholder requirements from the identified stakeholders:
The RIM shall ensure that the system of interest is carefully defined and that all interfaces are
identified for interdisciplinary design checks.
The RIM shall create an engineering management plan to define the engineering processes that
will be used to identify, document, trace and assure that all requirements allocated to the
signalling system are realised in the commissioned system.
The RIM shall identify the interaction between users and the system in relation to:
(a) Physical, mental, and knowledge capabilities.
(b) Work place, environment and facilities, including other equipment in the
context of use.
(c) Normal, unusual, and emergency conditions.
(d) Operator and user recruitment, training and culture.
If usability is important, usability requirements should be planned, specified, and implemented
through the life cycle processes. The following standards or technical reports may be applicable:
(a) ISO 9241-11:1998, ergonomic requirements for office work with visual display
terminals (vdts) — part 11: guidance on usability
(b) ISO 13407:1999, ergonomics — ergonomics of human-system interaction —
human-centred design process for interactive systems.
The RIM shall ensure that all hazards so far as is reasonably practicable have been identified
and the associated controls that are allocated to the system are defined as stakeholder
requirements from which system requirements can be derived.
The RIM shall ensure that there is a complete and maintained set of stakeholder functional
requirements and constraints.
The RIM shall feed back the analysed requirements to applicable stakeholders to ensure that
the needs and expectations have been adequately captured and expressed.
The RIM shall maintain and record the stakeholder requirements in a form suitable for
requirements management through the life cycle and beyond.
The stakeholder requirements shall be documented in a way that facilitates full traceability to
the system requirements
The stakeholder requirements shall be prepared by a suitably competent person(s) with
understanding of the railway operations and signalling systems.
RISSB ABN 58 105 001 465 Page 11

AS 7718:2017
Management
The stakeholder requirements shall stipulate the assurance of competent and adequately
resourced personnel.
The stakeholder requirements shall define the relationships between design authorities, as well
as interfaces with other authorities, disciplines, functions and RIMs.
The stakeholder requirements shall define the responsibilities for collating documentation to be
submitted for RIM approval and statutory approval.
The RIM shall mandate the process for assessment and approval of proposed changes to the
stakeholder requirements such as to assure that all safety, delivery and cost impacts are
identified.
The stakeholder requirements should state if the system has any direct or indirect interfaces
with existing operating systems
2.4 Stakeholder requirements report

The stakeholder requirements determined through the above process shall be documented for
use in the development of the system requirements.
3 Requirements analysis process

3.1 Purpose
The purpose of the requirements analysis is to transform the stakeholder requirements into a
system requirements specification that will deliver the required operational and safety functions
within the defined performance parameters
This process builds a representation of a future system that will meet stakeholder requirements
and that, as far as constraints permit, does not imply any specific implementation.
It results in measurable system requirements that specify, from the supplier’s perspective, what
characteristics it is to possess and with what magnitude in order to satisfy stakeholder
requirements.
The requirements analysis process needs to consider all elements of reliability, availability,
maintainability and safety (RAMS).
The successful implementation of the requirements analysis process shall -
(a) define a system requirements specification;
(b) specify constraints that will affect the concept design of a system and the
means to realize those constraints;
(c) achieve the integrity and traceability of system requirements to the
stakeholder requirements report;
(d) Define the criteria for acceptance of a requirement
The requirements analysis shall include requirements associated with –
(a) intended use;
(b) self-testing and diagnosis;
(c) all interfaces;
RISSB ABN 58 105 001 465 Page 12

AS 7718:2017
Management
(d) reliability, availability, maintainability and integrated support requirements;

(e) other regulatory requirements.
The high-level system requirement specification shall include but not be limited to –
(a) track infrastructure;
(b) train operations;
(c) maintenance requirements;
(d) line speed requirements;
(e) signalling equipment and type approval;
(f) existing signalling configuration;
(g) train protection systems;
(h) headway analysis;
(i) power reticulation;
(j) level crossing systems;
(k) train control systems;
(l) staging and parallel works system requirement specification (high level);
(m) environmental requirements;
(n) noise considerations;
(o) vandalism consideration;
(p) flora, fauna and vermin considerations.

The requirements analysis process shall include the following activities:
(a) Analyse stakeholder requirements.
(b) Define system requirements.
(c) Trace systems requirements to stakeholder requirements.
(d) Define acceptance criteria.
4 Concept design process

4.1 Purpose
The purpose of the concept design process is to synthesize a solution that satisfies system
requirements.
This process encapsulates and defines areas of solution expressed as a set of separate
problems of manageable, conceptual and, ultimately, realizable proportions.
It identifies and explores one or more implementation strategies at a level of detail consistent
with the system’s technical and commercial requirements and risks.
A concept design solution is defined in terms of the requirements for the set of system elements
from which the system is configured and links the V&V (verification and validation) plan.
RISSB ABN 58 105 001 465 Page 13

AS 7718:2017
Management
The system element is constructed or adapted by processing the information appropriate to the
selected implementation technology and by employing appropriate technical specialties or
disciplines.
The concept design process will ensure that the integrity and traceability of the RAMS
requirements in the design are managed in accordance with the assurance processes defined
in en50126, en50128 and en50129.
The concept design process shall be developed from a defined and agreed set of system
requirements.
The concept design process shall deliver the following:
(a) An agreed concept design baseline.
(b) The set of system element descriptions.
(c) The interface requirements to external systems.
(d) Traceability of concept design to system requirements.
(e) A basis for verifying the system elements.
(f) A basis for the integration of system elements.
The design should capture a trigger point for concept design completion (%).
The concept design process shall –
(a) provide clear, accurate, consistent and unambiguous presentation;
(b) comply with the referenced standards;
(c) comply with the client’s requirements, as reflected in the system requirements
specification;
(d) specify an appropriate level of safety;
(e) confirm that the system design will realise the complete set of all allocated
requirements;
(f) facilitate construction (including stagework) and testing;
(g) develop a functional design that is fit for purpose.
In providing the concept design the design authority shall –
(a) be competent and hold engineering competencies relevant to the RIM;
(b) prepare, supervise and manage the design in accordance with the RIM
signalling standards and procedures;
(c) prepare, review and verify the design;
(d) independently check the concept design against the SRS in accordance with
the RIM standards and procedures, and
(e) produce all design information, data, drawings and other documentation in
accordance with the RIM's standards and procedures.
The concept design process shall deliver the signalling plan.
RISSB ABN 58 105 001 465 Page 14

AS 7718:2017
Management
Where sequential commissionings are required, derivative staged signalling plans shall be
produced.
The signalling plan produced shall demonstrate that allocated requirements have been
addressed and the plan is readily understood by operations, signalling and other stakeholders.
Where required, the concept design process should deliver a signalling equipment system
configuration.

The project shall implement the following activities and tasks in accordance with applicable
organisation policies and procedures with respect to the concept design process.
The concept shall be defined, including the following tasks:
(a) Define signal design elements and documents which support the detailed
design phase, including the signal plan and where appropriate: the concept of
operations, control tables and system architecture description.
(b) Apportion the system functions identified in requirements analysis and allocate
them to elements of system architecture while maintaining traceability. Where
the signal design follows existing signal design standards of the RIM then
reference to this can be used to apportion the requirements.
The system design shall clearly define interfaces and develop interface requirements
specification to assure the system functions are achieved within the system of interest and for
interfaces external to the system of interest. The following are some of the considerations that
may be relevant when defining an interface:
(a) Typical functions passing in each direction.
(b) Method of checking the validity of each function.
(c) Protocols.
(d) Method of design checking.
(e) Interlockings.
(f) Geographical areas.
(g) Track interface.
(h) Overhead interface (optional).
(i) Tram interface (optional).
(j) RIM’s provision at the interface.
The listing and descriptions need to be sufficiently detailed to ensure that the approach and
detailed design of each function passing is clearly understood, ensuring a safe and accurate
operation of the interface.
The concept shall be documented and maintained by —
(a) specifying the selected physical design solution as a concept design baseline,
in terms of its functions, performance, behaviour, interfaces and unavoidable
implementation constraints;
(b) recording the concept design information, and
RISSB ABN 58 105 001 465 Page 15

AS 7718:2017
Management
(c) maintaining mutual traceability between specified design and system

requirements.
Where applicable, stage concept signalling plans should be derived from the approved concept
signalling plan before producing the engineering details, and, where required for approval, shall
be submitted at a subsequent phase.
Guidelines on the minimum content of the concept signalling plan and considerations
associated with stage signalling plans should be in accordance with the RIM standards and
procedures.
A recent kilometre post or reference survey point shall be obtained as a basis for the signalling
plan.
A recent gradient site survey plan shall be included on the signalling plan for braking analysis,
runaway trains and stopping position of trains.
The sighting of lineside signals, signs and indicators shall be undertaken as soon as practicable
following signalling plan approval.
Where possible, components to make up the system to provide the required functionality and
constraints apportioned from the SRS, should be selected from those already type approved for
that function by the RIM.
If there are no suitable type approved products, the selection of the product shall consider
whether the product/system will achieve the defined acceptance criteria for the function(s) it will
provide.
Alternative design solutions shall be evaluated, modelling them to a level of detail that permits
comparison against the specifications expressed in the system requirements, performance,
costs, time scales and risks expressed in the stakeholder requirements. This shall include-
(a) assessing and communicating the emergence of adverse system properties
resulting from the interaction of candidate system elements or from changes in
a system element;
(b) ensuring that the constraints of enabling systems are taken account of in the
design;
(c) performing effectiveness assessments, trade-off analyses and risk analyses
that lead toward realizing a feasible, effective, stable and optimized design.
A system capable of being verified against the specified requirements from concept design shall
be assembled and integrated.
Drawings and documents produced at this phase shall be configuration managed in accordance
with the RIM standards and procedures.
5 Detailed design process

5.1 Purpose
5.1.1 The detailed design process
The purpose of the detailed design process is to convert the signalling concept design into
detailed hardware and software configuration that will provide the required functionality and
performance of the signalling system for the specific application.
RISSB ABN 58 105 001 465 Page 16

AS 7718:2017
Management
The process will support development of a detailed design that is completely compliant with
agreed system requirements and that all requirements are verified as being traced from the
previous phase and all functionality and performance is validated.
Designs will be in accordance with the RIM’s standards and procedures to assure that the
safety integrity is achieved. Alternatively, for novel designs that are not covered by existing RIM
standards, the design may consider the requirements of EN50126, EN50128 and EN50129 to
ensure that the safety integrity is defined and achieved.
This process combines system elements to form complete or partial system configurations in
order to create a product specified in the system requirements.
The development of the signalling plan fulfils the following purposes, as necessary:
(a) Submission for approval in principle by the RIM.
(b) Checking interdisciplinary details associated with train operating, permanent
way, civil engineering, electrification infrastructure, plant and
telecommunications requirements.
(c) Estimating and contract tendering, where applicable.
(d) Compiling control tables and other design details.
(e) Providing a derivative for the production of a signalling bonding plan.
(f) Deriving drivers diagrams, panel faceplates and VDU maps.
(g) Signal sighting.
(h) Control table testing.
(i) Layout of new equipment on site and identifying recoveries.
(j) In the case of multiple stage schemes, deriving stage signalling arrangement
plans for each commissioning.
5.1.2 Base design

The base design is an intermediate step to assist in the development of the detailed signalling
design.it describes the specific documentation and procedures applicable to signalling design
activities to ensure –
(a) safe development and design of new and altered signalling systems impacting
on the RIM's controlled infrastructure;
(b) safe interfaces between all parties and systems;
(c) design details are prepared and presented clearly, accurately, consistently
and unambiguously;
(d) an auditable design process is carried out;
(e) client’s specified requirements are met and the design is fit for purpose.
The design delivery strategy will need to consider the requirements associated with
implementation, interface and access constraints
5.1.3 System requirements specification

The system requirement specification provides a basis for change control during the detailed
design phase. Clear tracking of changes to scope, designs and version control of the outputs is
useful.
RISSB ABN 58 105 001 465 Page 17

AS 7718:2017
Management
The design management plan is also updated with these changes.
5.2.1 The detailed design process (implementation)
As a result of the successful implementation process —
(a) an implementation strategy shall be defined;
(b) implementation technology constraints on the design shall be identified;
(c) the design of a system element shall be completed with all supporting
documentation and under version control;
(d) a system element shall be packaged and stored in accordance with an
agreement for its supply;
(e) the deliverables (design outputs) shall be be detailed within the project
management plan and the design management plan;
(f) if required a safety case should be completed prior to the implementation
process.
5.2.2 Interfaces
All interfaces shall be identified from the system architecture and documented in an interface
control document. Each interface shall have a defined interface requirement specification to
ensure an effective interface is designed
For every design output where there is an interface with another discipline, eg civil, ole, track
there shall be an interdisciplinary design check to ensure that the interface does not have any
impact on the integrity of another rail system
5.2.3 The detailed design process

As a result of the successful implementation of the process –
(a) a system integration strategy shall be defined;
(b) unavoidable constraints of integration that influence requirements shall be
defined;
(c) non-conformances due to integration actions shall be recorded;
(d) all changes to requirements shall be assessed, recorded, approved and traced
into the detailed design.
5.2.4 Procedures and manuals

A list of the agreed subset of procedures and manuals shall be used in the design along with
any site-specific exceptions.
The base design shall be included in a suitable plan and shall describe, in an appropriate form,
the following requirements as an input into the detailed design stage. The base design
documents shall include –
(a) the verified signalling plan
(b) signal sighting details
(c) control tables if considered necessary
RISSB ABN 58 105 001 465 Page 18

AS 7718:2017
Management
(d) detailed site survey

(e) other information where it is deemed appropriate to assist in the preparation of
the detailed design.
5.2.5 Design management plan

The design management plan shall describe in detail how the works are to be managed,
including how they —
(a) are derived from, and align with, the timescales, resources and activities in the
approved project programme;
(b) are approved by the RIM based upon correct and complete conformance to
the minuted outcome of the design planning meeting, and
(c) address the design control chart, design resource plan, design responsibilities,
interfaces and the use of procedures and manuals.
Example designs on the contract/project as per reference baseline should be included in the
design management plan.
Where the introduction of new or altered, signalling is divided into sequential commissionings,
derivative stage signalling arrangement plans shall be created for each commissioning.
All proposed stages of the design shall be detailed and all configuration changes clearly listed.
Maintenance facilities shall be provided as required to meet the specified maintainability and
availability performance.
The design authority shall ensure all deliverables are produced to the RIM 's standard, meet the
approved operations requirements and approved system requirement specification.

5.3.1 Detailed design process
The project shall implement the following activities and tasks in accordance with applicable
organization policies and procedures.
Production of alterations shall generally be undertaken on the medium for production, which is
either the source record, or a copy of the source record.
Implementation shall only commence when:
The design authority shall confirm that no other design works are being undertaken on any of
the system that may invalidate the assumption of the existing system design. If another design
authority is in possession of the same source records. Then a lead design authority must be
appointed by the RIM to manage the coordination of those designs and associated risk. The risk
of parallel design must be assessed and controls defined in the design management plan
specific to the application and extent of the parallel design.
A copy of all drawings and design information of the current state of the infrastructure shall be
held under configuration management during design, construction and commissioning of new
works. This copy should be retained as a record after the new works have been completed.
The source record itself shall only be altered when approval in principle has been received and
there is an assurance that the commissioning will take place.
Projects shall be designed so that where a commissioning is suspended or cancelled, the
design changes can be suitably managed to put back the previous version.
RISSB ABN 58 105 001 465 Page 19

AS 7718:2017
Management
There shall be no restriction on the creation of source records for new work, as distinct from
alterations to existing installations.
Implementation, updating and version control (also known as baselining detailed design) shall
be strictly applied –
(a) except where the implementation of a subsequent alteration is commenced as
soon as any common source records have been updated in anticipation of the
previous commissioning; and
(b) provided that the same responsible design engineer has been appointed to
oversee all overlapping alterations; and
(c) except where the implementation of a subsequent alteration is commenced as
soon as any common source records have been updated in anticipation of the
previous commissioning,
(d) security copies have been taken where necessary for record purposes.
Source records shall be updated as soon as an alteration has been checked, provided that the
same responsible design engineer has been appointed to oversee all overlapping alterations
and security copies have been taken where necessary for production purposes.
Design implementation showing new designs, alterations to existing designs and deletions of
existing systems shall clearly and unambiguously show: new works, deleted works and
amended works in accordance with the RIM requirements. This includes: drawings, system
data, design documents, design calculations and any other supporting documents for the
design.
Data approval form(s) shall be in accordance with the RIM guidelines designed to suit the types
of electronic data-driven equipment to be used on the project.
The responsible design engineer shall be appointed by the design authority before the design of
the first alteration is commenced.
If commissioning dates have not already been defined, the responsible signal designer shall
nominate an assumed order in which the commissionings are to be treated, with reference to
the draft staging and testing strategy, and tester in charge, if appointed.
Commissioning dates shall also be agreed between all affected disciplines and parties,
including the design authority and RIM.
If the nomination proves incorrect, each alteration shall be modified as necessary to allow for
the new commissioning order.
This process will be facilitated by arranging simple interfaces between each alteration and
agreeing the usage of spare fuses, cable cores and relay bases, etc.
5.3.2 Parallel processes

Where it is desired to run stages of a project(s) concurrently rather than consecutively, in order
to meet compressed timescales, special controls shall be implemented by the responsible signal
designer to ensure the integrity of the process(es).
A risk assessment shall be used to determine suitable and sufficient control measures to reduce
risks so far as is reasonably practicable.
RISSB ABN 58 105 001 465 Page 20

AS 7718:2017
Management
5.3.3 Parallel alterations

Special controls should be implemented where it is necessary to relax the design process to
allow successive stages or alterations to follow in close succession, in the same signal control
area. All parallel arrangements shall be documented in a formal manner between all parties.
Examples of processes associated with a single alteration that could be run in parallel, with
appropriate control measures, as below:
(a) The production of control tables before signalling plan approval.
(b) The production of engineering details before the control tables are approved.
(c) The production of engineering details before site surveys are undertaken.
(d) Correlation to production copies (where required) whilst work is in progress
(e) pre-wiring apparatus housings before the engineering details are approved for
construction without interfacing to existing equipment.
(f) Commencing work on site before an approval for construction to proposals' is
received.
5.3.4 Design management plan

A design management plan (DMP) is a live document and shall be updated as necessary during
the course of the project to reflect changes to scope, organisation, responsibilities, standards or
corrective actions.
The appropriate project manager or design authority shall ensure that amendments or updates
to the design management plan or the system requirements specification are updated in all
other concurrent design processes and outputs.
5.3.5 Checking inputs

The output of the detailed design process shall include collation of the design inputs and the
presentation of these for design checking.
5.3.6 Design deliverable plan

The design control chart, listing all design items to be prepared with their scheduled date for
submission for approval, approval party, shall be included in the detailed design plan.
The design control chart shall include an entry for each type of submission submittable design
items for each stage of the works, for each control area and for each phase of design.
The design control chart shall be extracted from the design activity in the approved contract
program.
The design control chart shall include an allowance for an approval period for each submission
and for each resubmission of designs.
The design control chart shall be used for prioritising and programming design checking and
approval activities and for monitoring each RIM ’s design progress.
5.3.7 Design considerations

Any detailed design works produced for a RIM should take into account the below
considerations as a minimum.
The integrity of the as-built records should be investigated and appropriate measures defined to
confirm the integrity where there is perceived that there may be a discrepancy between records
RISSB ABN 58 105 001 465 Page 21

AS 7718:2017
Management
and the actual design as functioning. If correlation is required, the condition of the asset to be
disturbed must be considered when defining the actions relating to confirming the accuracy of
the records.
Equipment likely to be affected by the proposed work shall be examined by a competent signal
engineer who shall make an assessment of any factors which might introduce special risks
during the execution of the work.
The design authority shall have the relevant competencies to undertake the task of managing
signalling works.
5.3.8 Design outputs

Many documents shall start out as inputs to the design process; as the project progresses these
documents become further refined to eventually become the final design documentation.
Below details the minimum work order flow that shall be undertaken prior to starting detailed
design.
The designer shall follow the RIM standards and procedures.
The designer shall conduct a production check prior to hand over of the design to the design
checker.
The designer shall endorse the design when satisfied that —
(a) following production check that all necessary corrections have been
incorporated;
(b) the design meets the requirements specification;
(c) the design meets applicable standards;
(d) the design is fit for purpose, and
(e) the design is safe.
5.3.9 Method of documentation

Version control of design items shall be in accordance with processes nominated by the design
authority.
Tracking and control of signalling documentation to the RIM shall be followed.
The method of production for each project shall be determined by the complexity of the design
to be carried out.
Designs should always follow the RIM standard; on occasions where a design innovation is
possible a derogation should be sought from the RIM as to its use following an assessment of
the innovation.
A production copy, also known as production design file shall show all design, new and
alterations of the altered source record/master record.
6 Independent checking process

6.1 Purpose
The purpose of the independent checking process is to confirm that the specified system
requirements are fulfilled by the system including any safety requirements.
RISSB ABN 58 105 001 465 Page 22

AS 7718:2017
Management
The independent checking (verification) of a design concentrates on safety, functionality,

operational requirements, agreed scope of work (with customer), completeness, fit for purpose
and compliance with applicable RIM signalling principles and standards.
The independent checking (verification) process needs to consider all elements of reliability,
availability, maintainability and safety.
The independent checking shall provide the verification evidence as required by the verification
and validation plan for the system:
(a) The design output shall conform to specified requirements.
(b) The design option chosen shall be feasible, fit for purpose and safe.
(c) The design of the signalling system shall meet all the dependability criteria.
(d) The system being designed shall be constructed, tested, commissioned,
operated and maintained efficiently and effectively.
(e) The design shall have taken in to account all applicable aspects listed in the
design checklists and/or the proceedings of a technical review, including test
results where appropriate.
(f) Supporting calculations and decisions for defined critical systems shall have
been independently checked and verified in accordance with RIM standards
and specifications.
(g) The requisite approvals shall have been obtained from regulatory authorities.
(h) The design shall have been documented as per each RIM requirements.
These documents and records shall form part of the evidence supporting
systems and safety assurance.
As a result of the successful implementation of the independent checking (verification)
process –
(a) a list of items for corrective actions shall be recorded; and
(b) confirmation design shall satisfy the system requirements and concept design.
If independent verification is required by the RIM, the independent checker shall issue to the
design authority —
(a) a signed copy of their check copy (including all mark ups) as a minimum
requirement for verification;
(b) an updated list providing information for corrective action is reported,
containing all errors and/or queries, and
(c) an updated independent checking record with all relevant fields filled out.
6.2.1 Checking process

On completion of the design the designer shall forward to the independent checker all the
information that the checker will require to complete the independent checking (verification)
task.
The independent checker (verification) shall not propose a design solution as this will void the
independence when the redesign is checked.
RISSB ABN 58 105 001 465 Page 23

AS 7718:2017
Management
The independent checker shall review the specific design item in consideration of all other
design items even if they are not the independent checker for other items.
Individual people should be separately used to perform independent check for different design
items. One of the independent checkers should take overall responsibility for the complete
independent design check.
6.2.2 Marking of check copies

As a minimum, each sheet shall be stamped checked/certified with the date, signature, name of
the independent checker.

6.3.1 Independent check process
The independent checker shall adopt a systematic approach to the checking process, so as to
ensure that the design objectives are achieved.
The independent check shall be rigorous and comprehensive, and place no reliance on the
testing process revealing any residual errors.
The verification process shall include the following:
(a) RIM signalling principles shall be the basis of the check.
(b) Any assumptions shall be documented in an independent checking report (or
equivalent).
(c) Calculations and/or functional safety analysis shall be performed where
appropriate.
(d) Appropriate check and/or error recording processes shall be followed.
(e) New work and interfaces shall be 100% independently checked.
(f) Existing installations shall be 100% independently checked in the relevant
areas of circuitry or data altered.
(g) Any copying of earlier designs, or use of standard computer aided design
cells, shall be treated as new work.
(h) Independent check shall take place either at the completion of each design
stage for major projects or at the completion of the design task for minor
projects.
(i) The independent check shall establish the exact scope, become familiar with
the site information, establish validity of standards declared, establish that any
correlation processes have been carried out, establish that the designer has
achieved the design objectives, and become familiar with the pertinent
contract documents with local site information, impact on adjacent or
dependent work and other relevant correspondence.
6.3.2 Design/ technical requirements

The independent checker shall confirm that the design is consistent with the latest version of the
input design items.
RISSB ABN 58 105 001 465 Page 24

AS 7718:2017
Management
6.3.3 Rework
Errors found by the independent checker shall be returned to the designer for review and
correction. They resultant designs are then returned to the independent checker for checking.
The designer should respond to each error report stating their action including responses where
the item raised is confirmed as not an error, stating why so that it can be closed out.
6.3.4 Independent checking guide

The detail of all verification checks should be in accordance with the verification plans and in all
cases a plan of the evaluation criteria should be defined prior to the check taking place with
reference to all requirements, signalling system and quality. Typically, this will be documented in
an independent checking checklist.
6.4 Validation purpose

The purpose of the validation process is to provide objective evidence that the services
provided by a system (a system element, a system, a document, a service, a task, a system
requirement, etc.) When in use comply with stakeholders’ requirements, achieving its intended
use in its intended operational environment and that the requirement(s) for a specific intended
use have been fulfilled. This may cover: functional requirements, safety requirements and
performance requirements. When required, this may be outlined in the V&V plan.
The signalling design is typically against the RIM standards for the function. In these cases,
validation has previously been undertaken of the standards against principles and external
standards. Generally, validation is not required in these cases.
7 Approvals and responsibilities

7.1 Purpose
The approval process is for progressive acceptance of project decisions. Based on assurances
that the safety and integrity of the network is maintained throughout the change process and the
design intent is met by proposed changes.
The RIMs will nominate the authorised approvers for design outcome.
Approvals and responsibilities need to consider all elements of reliability, availability,
maintainability and safety.
7.1.1 Interface management

For purpose of approvals each RIM should manage interfaces between design authorities.
7.1.2 Construction management

The approval for construction process shall confirm that the appropriate checks have been
undertaken. The RIM should define checking processes for designs that would be issued as
approved for construction
7.2.1 Design approval levels and definitions
The RIM shall define the level of approval for each design. The following levels of design
approval are applicable:
RISSB ABN 58 105 001 465 Page 25

AS 7718:2017
Management
(a) Approved in principle: the design proposal is generally satisfactory but some
areas of the submission require correction, alteration or clarification. Design
proposal is generally consistent with scope, applicable standards and follow
the require processes.
(b) Approved for construction: the design output should be used for determining
bill of materials and for undertaking construction activities.
(c) Approved: complete design shall meet the agreed scope, applicable standards
and processes and safety in design obligations and is SFAIRP.
The RIM should define gateways for the design approval process to mitigate project risk and to
ensure the design will meet the applicable requirements to reduce the risk of not meeting final
approval.
All designs, drawings supporting documents shall be submitted to the RIM and acceptance
obtained before any work covered thereby is commissioned into service.
7.2.2 Responsibilities
The design authority shall be responsible for demonstration that all requirements allocated to
the signalling and system design have been met
Each RIM shall be satisfied that the design authority is competent and will allocate adequate
resources to perform its responsibilities.

7.3.1 Design approval process
The RIM shall define the process for approval of designs for the signalling systems and sub
system elements. This shall include the requirements for supporting infrastructure and review
activities for the designs.
Where applicable, this shall include the requirements criteria for –
(a) approved in principle, and
(b) approved for construction
Where applicable this shall include the requirements criteria for staged approvals and/or sub
system approval.
7.3.2 Production, updating and distribution of commissioning copies

The standard for testing and commissioning is to be used to create these documents.
7.3.3 Delivery of as-built documentation

After successful commission of the signal infrastructure the design drawings shall be updated to
as built status and submitted to the RIM for acceptance.
8 Design processes - general

8.1 Competency
All personnel undertaking tasks for the signalling and system design shall meet the competency
requirements of the RIM.
RISSB ABN 58 105 001 465 Page 26

AS 7718:2017
Management
Where the RIM does not have a specific requirement for competency for a design task, the
personnel shall be able to demonstrate that they have the competency to undertake the task.
Where there are legislative requirements for accreditation for engineering work or other tasks,
then these shall be addressed in the design management plan and personnel meeting the
requirements allocated accordingly.
Where permitted by the RIM competency requirements, a person without competency should
undertake tasks under supervision and mentorship of a competent person.
Records of the competence of personnel undertaking design tasks shall form part of the design
management plan.
Personnel undertaking supporting tasks for the design process shall also be competent and
have records of competence.
8.2 Responsibilities
The design authority should be responsible for managing the design process.
The manager of personnel undertaking design tasks should ensure that the personnel allocated
to a task are competent to perform the task.
The organisation applying this standard should have in place a quality system to ensure that the
design work is carried out in a planned and systematic way and that there is appropriate
documentation as evidence of this.
The quality system should be accredited to AS/NZS ISO 9001 - quality systems for
design/development, production, installation and servicing, or an equivalent acceptable to the
RIM
9 Design changes and configuration management

9.1 Purpose
The purpose of the design changes and configuration management is to safely manage, control
and document a process for design changes at any point in the life cycle.
The purpose of configuration management is to assure that at all points for throughout the
lifecycle of the system design the most current version is known and documented for use by
those in following stages of the system realisation and operation
Documentation of design changes cover the impact on the design outcomes of the project.
The design authority shall have a RIM approved process in place for assessment and
management of change, this will ensure –
(a) the lifecycle change and the complexities associated with making that change
in the current stage are assessed and appropriate controls defined;
(b) unique identification of each modification to design drawings or documents;
(c) full traceability of each change;
(d) updating of affected records.
RISSB ABN 58 105 001 465 Page 27

AS 7718:2017
Management
The design authority shall have in place a configuration management system that provides
traceability between all configuration items so that when it a change is approved for
implementation all affected configuration items can be identified and updated.
Any configuration item shall require preapproval if any change is made to that item outside of
the scope of the defined conditions of approval.

9.3.1 Modification to approved design and engineering details
Modification to the approved designs after issue of the approved for construction status and
shall be controlled in accordance with RIM and/or design authority processes.
Changes shall be recorded and certified in the approval and version panel for each design
(drawing or document). In accordance with RIM requirements.
The reasons for each change shall be recorded in accordance with RIM requirements.
Any change(s) to the system requirement specification documentation after approval of the
design inputs shall require the review of signalling documentation. Changes may be required to
previously approved design input documentation.
A log of changes or variations to the project shall be appended to the system requirement
specification documentation and accepted in accordance with RIM processes
Once the system requirement specification documentation has received formal acceptance, any
changes required to design inputs shall be managed under an agreed control process.
9.3.2 Modification sheets- method

Modification sheets shall be used in accordance with RIMs procedures
When modification sheets are issued from the design office, they shall be sent with an issue
document and new version of the index showing the affected sheet.
9.3.3 Other document update for modifications

Design changes or modifications shall be updated to approved for construction drawings and/or
testing copies and commissioning copies in accordance with RIM procedures.
The process shall include a register of all modifications issued for construction and the
sequence they are to be addressed
RISSB ABN 58 105 001 465 Page 28

AS 7718:2017
Appendix A System design process overview
RISSB ABN 58 105 001 465 Page 29
AS 7718:2017
Appendix B Signaling design management standard lifecycle
RISSB ABN 58 105 001 465 Page 30
AS 7718:2017
Management
Appendix C Safety in design
C.1 Purpose
Each RIM has statutory obligations under the rail safety national law, the relevant state rail
safety act and the WHS acts to ensure safety in design.
Risk assessment is an effective tool for determining which engineering control measures are
likely to give the greatest safety benefit in terms of the cost incurred, and demonstrating that
sufficient mitigation has been applied for the residual risk to be acceptable to each RIM.
Designing for safety requires identifying hazards and risks and eliminating or minimising risks to
SFAIRP through design.
ease of maintenance and low maintenance systems will maximise operational availability by
reducing recovery times after failure and minimise the lifecycle cost of the system.
C.2 Outcomes/deliverables
Systems of work necessary for the safe use of the asset.
Knowledge, training or skills necessary for persons installing, operating or maintaining the
asset.
Spares support requirements.
In the design of signalling systems, provision shall be made for the health and safety of
personnel at risk (e.g. Installers, testers, maintainers and operators) by means of a systematic
approach to task risk assessment.
The following categories of risk based safety analysis are applicable:
(a) Specific application safety argument (risk based) for the design and
implementation of a whole system at a particular installation.
(b) Generic application safety argument (risk based) for a particular architecture
of sub-systems with a wide application, for systems approval.
(c) Generic product risk based safety argument for a particular item of equipment
with a wide application, for type approval.
C.3 Activities and tasks

The design records, together with explanations of unusual design features
Operating manuals and procedures
Maintenance manuals and procedures
Any other information on risks to be managed during operation, maintenance, or future works
on the completed infrastructure.
The design should review and include previous functional specifications
Three options are available for each identified hazard to reduce the risk so far as is reasonably
practicable (SFAIRP).
The following are in order of effectiveness:
(a) Eliminate the hazard by design
RISSB ABN 58 105 001 465 Page 31

AS 7718:2017
Management
(b) General control by isolating from, or minimising the risk within the design
(c) Individual control by procedures, training and provision of personal protective
equipment.
Where risks cannot be eliminated at source, additional information shall be provided in health
and safety plans, and/or noted on design details to help staff manage the risks.
At appropriate phases of the design, the design authority shall contribute to a health and safety
plan and retained for the life of the installation.
The means of demonstrating safety shall be stated in the system specification, and shall include
the following processes:
When applying, or interfacing, established circuit and system principles in a manner which has
not been catered for in those circuits or systems, due note shall be taken of the effect.
Where the issues are sufficiently complex to warrant it, a risk assessment shall be undertaken
as per RIM standards.
Documentation (as per RIM standards) shall be prepared, recording these effects (with
supporting calculations, where necessary) which will provide an audit trail of the designer's
conversion of the plans (e.g. Signalling plan and control tables) into engineering details.
Risk assessment shall be preceded by a process of hazard identification that systematically
considers all possible system interactions (both internal and external) and is commensurate with
the degree to which the system has changed and with the degree to which the system is
already proven in operation.
Novel systems, applications or environments require a team-based approach, such as a hazard
and operability study (HAZOP).
Significant changes or modifications shall be controlled in a similar manner to the original
design, such as:
Non-significant changes need only follow a reduced process to be determined by the RIM.
Design features that assist preventive and corrective maintenance shall be considered with the
infrastructure controller, in conjunction with the forming of their future maintenance policy.
These features shall be addressed at the concept phase of the design.
RISSB ABN 58 105 001 465 Page 32

AS 7718:20162017
Management
About Rail Industry Safety and Standards Board

The Rail Industry Safety and Standards Board (RISSB) is a not for profit company limited by guarantee. Wholly
owned by its funding members, RISSB is required to apply the whole of its income and assets to achieving the
objects listed in its Constitution.
RISSB is responsible for the development and management of standards, rules, codes of practice and guidelines for
the Australian rail industry.
For further information visit www.rissb.com.au
RISSB Australian Standards Development Process

The Standards development process is rigorous and transparent.
Authors work with RISSB's Project Managers and Development Groups to ensure that products are acceptable to
industry. Standing Committees oversee this work and ensure that proper governance and process is followed. The
products are exposed to the public and industry for comment, and validated by an independent validator.
Once agreed by the Development Groups, Standing Committees and Validator, the drafts are passed to the RISSB
Board for approval.
The same process is used in developing other RISSB products, although Guidelines are not exposed to the public for
comment or validated, given their non-binding nature.
Standards Development and Accreditation Committee

RISSB is accredited by the Standards Development and Accreditation Committee (SDAC), and all Standards
produced by RISSB since 31 July 2007 are published as Australian Standards.
The Standards Development and Accreditation Committee audits RISSB annually to ensure that RISSB’s processes
are in accordance with SDAC accreditation requirements.
Sales and Distribution

Australian Standards developed by RISSB are sold and marketed through SAI Global. For further information, please
visit www.saiglobal.com
Financial members of RISSB are granted access with membership.
RISSB ABN 58 105 001 465 Page 33

ABN 58 105 001 465
For information regarding an Australian Standard® developed by

RISSB, contact:
Rail Industry Safety and Standards Board

Suite 4, Level 4, Plaza Offices (East)
Terminal Complex, Canberra Airport
ACT 2609 Australia
PO Box 4271
Kingston ACT 2604
T +61 6270 4523

F +61 6270 4516
E info@rissb.com.au
For information regarding the sale and distribution of RISSB

Standards, contact:
SAI Global Limited

Phone: 13 12 42
Fax: 1300 65 49 49
Email: sales@saiglobal.com
http://infostore.saiglobal.com/store
ISBN Enter ISBN.
ISBN: 978-1-76035-852-5
This page has been left intentionally blank.

As 7718-2017

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

As 7718-2017

Uploaded by

Copyright:

Available Formats

AS 7718:2017

Signal Design Process

Train Control Systems Standard

Keeping Standards up-to-date

RISSB ABN 58 105 001 465 Page 1

Signal Design Process Management

RISSB ABN 58 105 001 465 Page 2

AS 7718:2017 Signal Design Process Management

2017 January 25, 2017 First publication

Rail Industry Safety and Standards Board (RISSB) 25/01/2017

RISSB ABN 58 105 001 465 Page 3

RISSB ABN 58 105 001 465 Page 4

5.3.8 Design outputs.................................................................................................22

RISSB ABN 58 105 001 465 Page 5

RISSB ABN 58 105 001 465 Page 6

RISSB ABN 58 105 001 465 Page 7

1.5 Referenced documents

RISSB ABN 58 105 001 465 Page 8

RISSB ABN 58 105 001 465 Page 9

2 Stakeholder requirements definition

RISSB ABN 58 105 001 465 Page 10

2.3 Activities and tasks

RISSB ABN 58 105 001 465 Page 11

2.4 Stakeholder requirements report

3 Requirements analysis process

RISSB ABN 58 105 001 465 Page 12

(d) reliability, availability, maintainability and integrated support requirements;

3.3 Activities and tasks

4 Concept design process

RISSB ABN 58 105 001 465 Page 13

RISSB ABN 58 105 001 465 Page 14

4.3 Activities and tasks

RISSB ABN 58 105 001 465 Page 15

(c) maintaining mutual traceability between specified design and system

5 Detailed design process

RISSB ABN 58 105 001 465 Page 16

5.1.2 Base design

5.1.3 System requirements specification

RISSB ABN 58 105 001 465 Page 17

The design management plan is also updated with these changes.

5.2.3 The detailed design process

5.2.4 Procedures and manuals

RISSB ABN 58 105 001 465 Page 18

(d) detailed site survey

5.2.5 Design management plan

5.3 Activities and tasks

RISSB ABN 58 105 001 465 Page 19

5.3.2 Parallel processes

RISSB ABN 58 105 001 465 Page 20

5.3.3 Parallel alterations

5.3.4 Design management plan

5.3.5 Checking inputs

5.3.6 Design deliverable plan

5.3.7 Design considerations

RISSB ABN 58 105 001 465 Page 21

5.3.8 Design outputs

5.3.9 Method of documentation

6 Independent checking process

RISSB ABN 58 105 001 465 Page 22

The independent checking (verification) of a design concentrates on safety, functionality,

6.2.1 Checking process

RISSB ABN 58 105 001 465 Page 23

6.2.2 Marking of check copies