• No results found

Engineering management methods

In document AEO Guide to Engineering Management (Page 58-67)

Engineering management methods form a framework that TfNSW and its engaged AEOs should follow to appropriately manage the engineering content and ensure the engineering integrity of a program across the system life cycle.

The system life cycle phases include:

 the identification of the stakeholder and user needs

 capability requirements and options

 feasibility studies

 preliminary design

 critical design

 fabrication and manufacture

 construction and installation

 inspection and test

 commissioning and handover

 operations and maintenance

 decommission and disposal

TfNSW programs shall comply with procedures for the management of engineering at each system life cycle phase.

Related topics:

Life cycle model, section 7.2

19.1 Stakeholder and user needs activities

Activities that should be incorporated in the 'stakeholder & user needs' phase of the system life cycle include the following:

 identifying business need statements for new or modified assets and capabilities as directed from TfNSW strategic planning, systems development, and through-life support teams

 the identification and application of relevant policy and strategic directives from TfNSW on the matters of TAM, excellence in design, and sustainability in design

 development of the business need statements into the initiation of a new project (system-of-interest), with an evaluation of these needs in relation to the present generation of systems, enabling technologies, and capabilities

 identifying applicable new ideas, enabling technologies, and capabilities to support the innovation of solutions for the system-of-interest

 identifying key stakeholders with either vested interests or future responsibilities, through the systems life cycle, in the development, delivery, and utilisation of the system-of-interest

 engagement with the stakeholders and users to reach a consensus on a set of business and capability requirements for the system-of-interest

 recording business needs and stakeholder and user requirements, to be carried forward for system-of-interest development, with the endorsement of all representative parties

 completion of a business case for the system-of-interest which clearly articulates the enterprise evaluations of cost versus benefit, risk versus opportunity, and similar factors of the capability and performance options under consideration, in accordance with TfNSW content standard

Related topics

Exploratory baseline gateway, section 7.4.1 Stakeholder briefs, section 12

Requirements management, section 8.1

19.2 Capability requirements and options activities

Activities that should be applied in the 'capability requirements & options' phase of the system life cycle include:

 analysis of the endorsed set of business needs and stakeholder and user requirements, with the relevant policy and strategic directives to confirm that a complete statement of capability requirements is stated for the system-of-interest

 development of conceptual options for solution architectures that address the capability requirements for the system-of-interest, within the bounds of available or innovated enabling technologies and capabilities

 performing trade study (risk and benefit) evaluations of the developed conceptual options in business enterprise and engineering categories. Identify the preferred conceptual option for solution architecture to carry forward into feasibility study activities.

 identifying the operational concepts for the utilisation of the system-of-interest with the engagement of the stakeholder and the user group

 identifying the maintenance concepts for the utilisation of the system-of-interest with the engagement of the stakeholder and the user group

 gaining stakeholder and user endorsement of those operational concepts relative to the preferred conceptual option, in documented form

 the completion of a BRS for the system-of-interest, inclusive of the articulation of the stakeholder group's reference concept and their reference architecture bases. This should include business, operational concept, maintenance concept, and test concept content in accordance with the TfNSW BRS content standard. Formalise endorsement of the BRS release from all system-of-interest stakeholders and user group members.

Related topics

Exploratory baseline gateway, section 7.4.1 Stakeholder briefs, section 12

19.3 Feasibility studies activities

Activities that should be applied in the 'feasibility studies' phase of the system life cycle include:

 performance of a feasibility study assessment on the preferred conceptual option in accordance with TfNSW guidelines. As part of this evaluation, engineering models and simulations may be executed to verify the feasibility of concepts, to aid the understanding of user needs, and to explore risks and opportunities.

 reporting the feasibility study conclusions for the reference concept, covering both business and enterprise streams as well as the engineering and technical streams of evaluation, in a feasibility study report. The report should be produced in accordance with TfNSW content standards.

Related topics

Concept baseline gateway, section 7.4.2 Stakeholder briefs, section 12

Engineering specifications, section 13

19.4 Systems requirements and concept design activities

Activities that should be applied in the 'system requirements & concept' phase of the system life cycle include:

 identification of a reference architecture for the concept, then document the reference bases as the 'concept design' for development of the systems requirements set

 development the functional and performance requirements, interface requirements, and constraints for the system-of-interest based on the 'concept design', derived from and referenced to stakeholder briefs in the URD

 identifying the test concepts for the inspection, test and commissioning of the system-of-interest with the engagement of the stakeholder and the user group. Gain stakeholder and user endorsement of those test concepts and the related possession demands relative to the preferred conceptual option, in documented form.

 identifying the maintenance concepts for the maintenance of the system-of-interest with the engagement of the stakeholder and the user group. Gain stakeholder and user endorsement of those maintenance concepts and related support infrastructure, support personnel, and possession demands relative to the preferred conceptual option, in documented form.

 completing an SRS for the system-of-interest. Formalise endorsement of the SRS release from all of the system-of-interest stakeholders and users.

 completing a scope-of-work appraisal and an acquisition or procurement plan for the system-of-interest in line with the reference concept and the reference architecture bases

 providing all required engineering artefacts to support the TfNSW transport projects division 'Invitation to Tender' (ITT) development process

Related topics

Concept baseline gateway, section 7.4.2 Engineering specifications, section 13

19.5 Preliminary design activities

Activities that should be applied in the 'preliminary design' phase of the system life cycle include:

 establishing a definition of the system-of-interest with a focus on the systems products required to satisfy system requirements

 completing sub-system specifications, systems interface specifications, and a preliminary definition of system elements

 applying systems engineering practices to break down system element functions into component (lower) level functions

 applying systems engineering practices in allocating function and performance requirements to component level architectures

 planning the test and acceptance program for the system-of-interest, based on the developing design of systems elements and their allocated requirements

Related topics

Preliminary baseline gateway, section 7.4.3 Engineering specifications, section 13 Engineering standards, section 14

19.6 Critical design activities

Activities that should be applied in the 'critical design', also known as 'detail design' phase of the system life cycle, include:

 completing systems design, down to the lowest component level, creating the component specifications and 'build to component baselines' for each of the components in the design solution

 providing detailed design drawings and parts lists, and component schedules for the design solution

 issue a critical (detail) design package for the specification of material procurement, fabrication procurement, and build procurement activities

Related topics

Build baseline gateway, section 7.4.4 Engineering standards, section 14 Configuration management, section 15

19.7 Fabrication and manufacture activities

Activities that should be applied in the 'fabrication / manufacture' phase of the system life cycle include:

 procuring systems-of-interest components in accordance with the critical design data

 manufacture of system-of-interest components in accordance with the critical design data, generally off-site at a supplier's factory

 modification of products to resolve production problems, reduce production costs, or to meet component requirements

Related topics

Post-build baseline gateway, section 7.4.5 Configuration management, section 15

19.8 Construction and installation activities

Activities that should be applied in the 'construction / installation' phase of the system life cycle include:

 building and fit-out of equipment at final site locations

 modification of constructions and installations to resolve build problems, reduce build costs, or to enhance installation efficiencies

Related topics

Post-build baseline gateway, section 7.4.5 Configuration management, section 15

19.9 Inspection and test activities

Activities that should be applied in the 'inspection & test' phase of the system life cycle include:

 combining lower-level elements in a system solution to create a fully functioning and unified higher-level element, with all logical and design interfaces satisfied

 progressive assembly and integration of components into assemblies, the assembly of system elements, and elements into systems-of-interest

 verification by inspections and tests that the system progressively meets build configuration and system and element specification requirements

Related topics

Validation baseline gateway, section 7.4.6 Verification and validation, section 8.7

19.10 Commissioning activities

Activities that should be applied in the 'commissioning' phase of the system life cycle include:

 validation of the final complete system-of-interest to the specified baseline of stakeholder and user requirements

 authorisation of the final complete system-of-interest for operational use

Related topics

Operating baseline gateway, section 7.4.7 Testing and commissioning, section 8.8

19.11 Operations and maintenance activities

Operations and maintenance activities include procedures that are created to support configuration updates. Activities that should be applied in the 'operations & maintenance' phase of the system life cycle include:

 operating the system-of-interest in accordance with the current baseline of system and asset operating procedures

 maintaining physical and functional configuration of the system-of-interest in accordance with the current baseline of system and asset maintenance procedures

 performing ongoing logistics engineering analysis on the present reliability, availability, maintainability, and safety performances of the operating system-of-interest to identify significant or problematic deviations from the design configuration basis

 managing minor configuration changes, waivers, and concessions and undertake minor design tasks as system maintainer, that address operations and maintenance issues, in accordance with the scope of an AEO's authority

 identifying and referring cases of major configuration changes, waivers, and concessions that lie outside an AEO's remit, to TfNSW

 referring major design issues that lie outside an AEO's remit to TfNSW for resolution Related topics

Retirement baseline gateway, section 7.4.8 Engineering standards, section 14

Configuration management, section 15

19.12 Decommissioning and disposal activities

Activities that should be applied in the 'decommission & disposal' phase of the system life cycle include:

 identifying the legacy plans for decommissioning and disposal for the system-of-interest from the original system definition artefacts and SRS

 identifying any system-of-interest modifications in the configuration records which would impact the existing decommission and disposal plan

 identifying the elements of the system-of-interest which will be completely or selectively decommissioned and disposed of, as directed by TfNSW. Identification also involves noting that elements of the system-of-interest at the end of its service life may be redeveloped in a new project, retained in a modified service role, or redeployed for alternative roles.

 formulating updated decommissioning and disposal plans, with the input of the relevant stakeholders

 undertaking approval of the updated plans and the scope of work within TfNSW

 decommissioning the relevant elements of the system-of-interest in accordance with updated plans and the TfNSW scope of works and terms of contract

 disposal of the relevant decommissioned elements of the system-of-interest in accordance with updated plans and the TfNSW scope of works and terms of contract Related topics

Engineering standards, section 14 Configuration management, section 15

In document AEO Guide to Engineering Management (Page 58-67)

Related documents