Dataset Card for Metro System Requirements in Design

Summary

This dataset provides detailed requirements for systems used in metro network design, collected from Chapter 18-22 of the Code for Design of Metro (GB 50157-2013). The dataset is annotated using a description, categories format, aimed at facilitating the training and fine-tuning of large language models (LLMs) for information extraction tasks in complex product systems, particularly within metro transit networks. The creation of this dataset serves two primary purposes:

To provide an open-source dataset for the requirements of complex product systems, which are typically proprietary and not readily available.
To offer a fine-tuned language model for extracting requirement information from the specific domain of complex product systems in metro network design.

The dataset includes requirements from various systems within metro design, including the Automatic Fare Collection (AFC) system, Fire Alarm Systems, Integrated Monitoring Systems, Environmental and Equipment Monitoring Systems, and Passenger Information Systems.

Dataset Details

Dataset Description

The dataset consists of 516 requirement data entries, which were sourced from the Code for Design of Metro (GB 50157-2013), specifically from Chapters 18-22. The dataset includes the following systems:

Chapter 18 - Automatic Ticketing System (AFC): Requirements for automating the fare collection in metro networks.
Chapter 19 - Fire Automatic Alarm System: Functional and performance requirements for an automated fire alarm system.
Chapter 20 - Integrated Monitoring System: Specifications for a centralized system that monitors various aspects of the metro network.
Chapter 21 - Environmental and Equipment Monitoring System: Describes the system's requirements for monitoring environmental conditions and equipment status.
Chapter 22 - Passenger Information System: Details requirements for systems providing real-time passenger information.

Data Distribution:

A total of 516 requirement data entries were collected, with the following distribution:
- 198 (38.37%) labeled as Functional Requirements
- 50 (9.69%) labeled as Interface Requirements
- 57 (11.05%) labeled as Performance Requirements
- 109 (21.12%) labeled as Physical Requirements
- 102 (19.33%) labeled as Design Constraints
Language (NLP): Chinese
License: Apache-2.0

Uses

Direct Use

This dataset is primarily used for training or fine-tuning large language models (LLMs) for information extraction tasks in the metro system design domain. It is useful for tasks such as:

Requirement classification
Extracting information from technical specifications
Automatic summarization of requirements
Categorizing requirements into their relevant types (Functional, Interface, Performance, etc.)

By fine-tuning a language model using this dataset, users can develop systems capable of understanding and categorizing requirements from similar documents in the metro system design field.

Out-of-Scope Use

This dataset is not suitable for use in non-metro-related fields or simpler systems with lower reliability and performance needs. It should not be used for systems that do not require sophisticated monitoring, automation, or security functionalities typical of metro transit systems.

Dataset Structure

This dataset contains two main components:

Content: Describes the specific requirement or design specification.
Label: Categorizes the requirement into one of the following five types:
- 0 Functional Requirement
- 1 Interface Requirement
- 2 Performance Requirement
- 3 Physical Requirement
- 4 Design Constraint

Data Definitions:

Requirement Type	Description	Example
Functional Requirements	Describes the functions or behaviors that the system must have, necessary to meet user needs.	The automatic ticketing system should have user permission management functionality.
Interface Requirements	Defines the interaction methods between the system and external systems or components.	The automatic ticketing system should implement interfaces with relevant systems.
Performance Requirements	Defines the performance metrics the system should achieve when performing functions.	The automatic ticketing system equipment should be capable of continuous 24-hour operation.
Physical Requirements	Describes the physical properties and components of the system, such as size, materials, etc.	The station control room shall be equipped with an emergency control button.
Design Constraints	Specifies the rules and restrictions that must be followed in the system design.	The metro should set different levels of AFC systems according to construction and economic development conditions.

Example:

Content	Label
The metro should set different levels of AFC systems according to construction and economic development conditions.	4 Design Constraint
The station control room shall be equipped with an emergency control button.	3 Physical Requirement
The automatic ticketing and fare collection system shall implement interfaces with related systems.	1 Interface Requirement
The central computer system of the line shall receive and send ticket allocation information.	0 Functional Requirement
The automatic ticketing and fare collection system equipment shall be capable of continuous 24-hour operation.	2 Performance Requirement

Dataset Creation

Curation Rationale

The purpose of creating this dataset is to fill the gap in open-source datasets for requirements in complex metro system designs. These data are typically proprietary and not easily accessible, and this dataset aims to provide a publicly available resource for training machine learning models on extracting technical requirements in this domain.

Source Data

The source data comes from the Code for Design of Metro (GB 50157-2013), particularly from Chapters 18-22, which describe requirements for the AFC system, fire alarms, integrated monitoring systems, and other key components of metro networks.

Data Collection and Processing

Data was collected from technical documentation of metro systems, which describe the requirements for various subsystems within metro networks. This data was carefully categorized based on their type (Functional, Interface, Performance, etc.).

Data Producers

The data producers are experts and engineers involved in metro system design, particularly in AFC systems, fire alarms, monitoring systems, and related infrastructure.

Annotations [Optional]

There were no additional annotations performed on this dataset other than categorizing the requirements into the five types listed above.

Annotation Process

The annotation process was carried out by experts familiar with metro system design, ensuring the correct classification of each requirement.

Who Are the Annotators?

The annotators are engineers and technical experts with experience in metro system design and AFC technology.

Personal and Sensitive Information

This dataset does not contain any personal, sensitive, or private information.

Bias, Risks, and Limitations

This dataset is specifically designed for metro network systems, and it may not be applicable to other types of transit or large-scale systems. Additionally, the data may not account for future technological developments or region-specific variations.

Recommendations

Users should be aware that the dataset is focused on metro networks and may not be directly applicable to other industries. It is also important to consider the evolving standards in the field of metro system design when using the dataset.