Brescia Driverless Metro System: A Functional Analysis Approach

This case study explores the application of functional analysis and allocation (FA&A) in the Brescia driverless metro system, a 13.7-kilometer railway network designed to alleviate traffic congestion in Brescia, Italy. The project faced delays due to archaeological discoveries, necessitating revisions to the original plans. The paper details the FA&A process used, including the identification of lower-level functions, requirement allocation, and the development of a functional architecture. It discusses the purpose of FA&A in transforming project requirements into clear system functions, the inputs and outputs of the FA&A process, and the various stages of functional analysis, such as defining project goals and assessing the impact of project subdivisions. The study also examines different functional analysis methods, including the spiral, waterfall, and prototyping models, and their suitability for the project. Furthermore, it touches upon function allocation methods, functional flow block diagrams, and the importance of representing functional relationships and time in project activity allocation. The document highlights the challenges and advancements in functional allocation, providing a comprehensive overview of the system engineering approach used in the Brescia metro project. Desklib provides a platform to access similar solved assignments and study resources.

Surname 1
Brescia driverless metro system
Student’s Name
Subject
Date

Surname 2
Introduction
Brescia driverless metro system is a rapid driverless railway network that serves Brescia and
Lombardy towns of Italy. It covers a general length of 13.7 kilometres. This is a project that was
initiated to reduce the traffic that was being witnessed in Brescia and its surrounding, (Powell et
al., 2016. Pp. 123). In 2004, archaeological discoveries halted the construction of the railway as
the sites discovered were deemed very important. This delayed the whole project with the first
line being completed and opened in 2013. This paper will focus on the use of Functional analysis
and allocation in Brescia driverless metro system.
Functional analysis and allocation
FA and A is a top-down allocation process that is used to translate system requirements into finer
functional and performance-based criteria. The system helps in bridging the wider gap between
system requirements and the present constraints, requirements analysis, and the much needed
detailed set, (synthesis) to develop a system and program implementation, (IJtsma et al, 2019.
Pp. 9). Therefore, FA and A is an important variable for both the design loop and requirement
loop. During the construction of Brescia driverless metro system, FA and A was utilised
throughout the project life, (Hoda and Murugesan, 2016. Pp. 256). The construction process of
the railway was halted so as new plans will be set that will support the solutions being
synthesized in regards to products, people and the processes being carried out. This was after the
discovery of archaeological sites was made along the construction line, (Ghiggi, 2005). It also
allows the identification of risks as a result of management attendance. FA and A is an iterative
process, reacting and interacting to the activities being carried in both the loops.

Surname 3
FA and A Process
The first step in the process is the identification of the lower-level function that is needed to
carry out different system functions. After the identification of the lower-level function, the
requirement is allocated leading to the development of the functional architecture, (Kerzner and
Kerzner, 2017). The activities interact with each other evolving the details which are validated
against them. In case of any normality, alternative architecture functions are run during the initial
stages until the desired approach becomes clear. With the discovery of archaeological sites along
the line, there was need for a fresh system analysis of the entire project. It was clear that a new
project plan was required to take into account the identified sites.it involve the use of the
fictional interface of the program.
Purpose of FA and A
The purpose of functional analysis and allocation in an engineering activity is to help in the
transformation of performance, requirements, functions and project interfaces which were
identified by analyzing the results to a more clear description of various system functions which
in turn will be useful in guiding design system activities, (IJtsma et al, 2017. Pp. 554). After the
award of contract to Ansaldo STS which was made up of AnsaldoBreda, Astaldi and Acciona,
they subdivided the activities of the project amongst themselves. Project’s civil engineering
activities were put in charge of Astaldi; this included the installation of mechanical systems
required and the electrical needs. AnsaldoBreda was in charge of the manufacturing of the
rolling stock.
Inputs

Surname 4
Function analysis and allocation require project inputs for a clear analysis of the project can be
done enabling it to be broken down into smaller interrelated manageable units. The following are
some of the inputs; Specific standards, functional requirements, commitments, regulatory
requirements, mechanical and electrical equipment as well as the rolling stock.
Output
Functional analysis and allocation have two sets of outputs; design output document and the
design output requirements, (Wiskerke et al, 2016. Pp. 73). The following are design output
documents; Specifications, component lists, description of system design, functional
requirements, system performance criteria, list of components and the set points. The design
output requirement consists of the following; system mission requirement, environmental
requirement, and system safety requirement.
Function analysis stages
There are four main stages in the analysis of a project; definition of the project goals, analysis of
the inventory, and assessment of the impact it will have on the product, and result in
interpretation.
i. Definition of goals; in this stage, aims of the analysis and allocation are determined.
The idea behind the construction of Brescia driverless metro system was to have a
similar model to that of Copenhagen that will lead to traffic decongestion in the area,
(Fraszczyk et al., 2014). The goal of the project was to create a locomotive function
that will reduce traffic.

Surname 5
ii. Inventory analysis; system inputs that will facilitate the analysis of the project are
carefully scrutinized to allow the generation of the desired outcome, (Hogenboom et
al., 2018). Brescia driverless metro system required inputs that will enable smooth
running of the project overtime.
iii. Assessment of the impact; repercussions of the subdivision of the project is done. It
was evident when the archaeological sites were discovered.
iv. Result in interpretation; after running the necessary information through the system,
the outcome is scrutinized to determine the accuracy and creditability.
Support processes
In order to conduct functional analysis and allocation successfully, the following support
processes are crucial. Definition of the problem to be solved, Review of the historical data,
Conduct the functional assessment, Development of a functional hypothesis, Designing of the
functional analysis, ethical issue identification, Testing the develop hypothesis and Plot the
collected data into a graph and interpretation of the data is done.
.
Functional analysis methods
The main reason why functional analysis is done is to help in the division of complex projects
into understandable simpler units. This will make it easier to design these smaller units, (Siyam
et al., 2017). Functional analysis can be implemented using the following models;

Surname 6
Spiral model
It is a representation of the iterative model and the waterfall model. Each phase of the project
starts when the design goal is set, (Camilleri, 2016). The spiral ends when the project progress
review is carried out. This model requires the owners of the project to start with the basic steps
of project management. Brescia driverless system tender process began in 2000. Contracts were
awarded in 2003 to three competing contractors; AnsaldoBreda, Ansaldo STS and Astaldi,
(Chapman, 2018). Additional requirements to the program lead to functionality added to the
spiral model until the model are ready for production.
The spiral model functional analysis involves various phases;
i. Project planning, this where project cost estimation, scheduling of resources and a
greater understanding of the system is done. This allows efficient and continuous
communication between the system users and the analyst running the system
ii. Risk analysis, likely risk in the projects is identified and mitigations are put in place
for it.
iii. Project engineering, it caters for the deployment of the system at the project site as
well as the required coding.
iv. Project evaluation, allows the contractor to thoroughly evaluate the effectiveness of
the system.
The figure below shows the stages of the spiral model

Surname 7
Benefits
a. Allows changes to be made in a later stage
b. Budget estimation for the project is easy as prototyping is done step by step
c. A repeated development activity minimizes the risk faced in the project
d. Project development is quick and more project features added systematically
e. It allows customer feedback
Demerits

Surname 8
a. Poses risk on budgetary allocation and scheduled project completion time
b. Majorly used for large projects
c. Requires documentation as it is made up of many phases
Waterfall model
This model subdivides project software and stages into several stages. Each stage is meant to
perform a specified project activity, (Tonchia et al., 2018). It is made up of the following phases;
i. Collection of requirements, detailed system requirements are obtained from the
stakeholders
ii. System design stage, technical project details are designed here. This may include
system coding
iii. Built stage, this is where software coding is carried out
iv. Test stage, software testing to determine if it meets the specification
v. System deployment phase, the system is taken to the project management site
vi. System maintenance stage, changes required are made as per the project requirements

Surname 9
Benefits
a. Makers sure that a phase is completed before starting the next one
b. Suitable for smaller projects with well-defined needs
c. The project is completed with no interruptions from the owner
Demerits
a. Identified errors can only be rectified during the phase it’s affecting
b. System testing takes time
c. Not suitable for large and complex projects
Prototyping model

Surname 10
In this system, a prototype is built, reworked until the needed prototype is obtained. It is best
suited where project requirement is not clear, (Turner, 2016). It has the following six stages;
i. Gathering and requirement analysis, the definition of the system requirements is
done.
ii. Quick system design, from the defined data, a basic system is designed.
iii. Prototyping, a prototype is created from the available data
iv. User evaluation, the system is taken to the user for examination
v. Redefining prototypes, if the created prototype does not please the user, it is defined
as per the user’s comments
vi. System implementation and maintenance; when the desired prototype is designed, it
is deployed for mass production.
Benefits
a. Minimal chances of system rejection
b. System users are involved in the development process
c. Prototypes are used as project operational specifications

Surname 11
d. Encourages effective communication
e. Helps in missing functionality in the system
f. Promotes innovation and system designing
Demerits
a. It is slow and time-consuming
b. Difficult to take into account changes if it is required
c. It may require so many changes required.
Given the magnitude of Brescia driverless system, spiral model is suitable in project analysis
given the ease in which new changes can be in cooperate into the system, (Wiskerke et al., 2016.
Pp. 73). Budgetary allocation can be determined during system development.
Function allocation methods
System designers have always got a sense of satisfaction whenever they develop a formal
function allocation method. From the proposal of Fitts in 1951, there is a comparison of human
and machine characteristics when projects need allocation. Hence the project is allocated to the
most appropriate resource. In the modern world, the allocation has been automated by the use of
more pragmatic actions, (Nicholas, and Steyn, 2017). Human resource is therefore allocated the
functions that are not automated. Both methods do the allocation in an isolated mode without
considering how the same function will be undertaken in the future. The project activity
allocation can be done using functional architecture method. This will show both the activities to
be performed as well as the activity sequencing.

Surname 12
Functional flow block diagram
It is useful in the determination of tools that will be useful during task allocation processes. It
shows multi-tier diagrams of activities and how they are interconnected with each other.
Functional relationship representation
During the process of functional analysis, it is critical to determine the relationship that belongs
between the tasks and also the existing relationship that exists among the projects inputs. This
will enable proper planning and allocation of the tasks.