PROCESS OF BIM ENABLED FM FOR METRO RAIL STATION FACILITIES

Abstract

The present disclosure introduces a system and method for an intelligent facility management engine, designed to enhance the conventional Building Information Modeling (BIM) enabled facility management (FM) processes for metro rail projects. The system (100) comprises a user device (102) that receives various inputs, including facility details, maintenance schedules, and operational information, and a facility management engine (104) that processes this data through a processor (114). The processor (114) performs key functions, such as categorizing data into structured and unstructured formats, linking documents for enhanced context, and generating maintenance action plans. Additionally, the system (100) tracks the real-time progress of maintenance tasks and updates the facility management database accordingly. The integration of OpenBIM standards facilitates seamless data exchange with third-party tools, enhancing interoperability. Furthermore, the system (100) provides graphical visualizations of the facility’s status and maintenance history, significantly improving operational efficiency and decision-making capabilities within metro rail facilities. Figure 1 will be the reference.

Specification

Description:TECHNICAL FIELD
The present disclosure relates to the field of Building Information Modeling (BIM) and Facility Management (FM) systems. More particularly, the present disclosure relates to a process of BIM enabled FM for metro rail station facilities that utilizes Open BIM standards for managing and optimizing the operation and maintenance of metro rail projects.
BACKGROUND
The integration of Building Information Modeling (BIM) with Facility Management (FM) has gained significant traction across various infrastructure sectors. In metro rail projects, BIM has traditionally been implemented for design and construction purposes, but its application in facility management remains limited. Existing approaches primarily focus on managing geometric and structured data, such as the physical properties of assets, including tracks, rails, and stations. However, these methods fail to address the management of unstructured data, such as maintenance schedules, operational manuals, and documentation, which are critical for efficient facility management.
While previous research has explored the use of BIM in rail project management, it has predominantly focused on the design and construction phases, with limited application to the operation and maintenance stages. Current technologies, including open BIM standards such as the Industry Foundation Class (IFC), are primarily used for geometric data representation, but they seldom incorporate unstructured information that is essential for comprehensive facility management.
There are several limitations in existing technologies. First, there is minimal integration of unstructured information, such as maintenance plans and documentation, into the BIM-FM process. Second, current systems do not adequately support the real-time tracking of facility information in metro rail stations. Therefore, a solution that enhances interoperability, communication, and collaboration among stakeholders, while incorporating both structured and unstructured data is required.
The current method of handling information primarily uses traditional 2D-based formats like COBie sheets and unstructured data, which limits collaboration and coordination among project teams. This outdated approach hinders seamless information transfer and effective communication between teams, leading to inefficiencies in project workflows.
This invention addresses these limitations by developing a BIM-enabled FM process that leverages Open BIM standards to streamline the operation and maintenance of metro rail projects.
SUMMARY
In one aspect of the present disclosure, a BIM enabled FM process for metro rail project system is provided.
In some aspects of the present disclosure, a system is provided, comprising a user device that is adapted to receive one or more inputs, wherein the inputs include facility details, maintenance schedules, and operational information The system further comprises a facility management engine communicatively coupled with the user device through a communication network. The facility management engine includes a processor that is configured to process the input data. The processor is adapted to receive one or more inputs via the user device; extract details representing each parameter of the one or more inputs; categorize the extracted parameters into structured and unstructured information for facility management tasks; link unstructured documents to specific parameters to enhance context and accessibility; generate a maintenance action plan based on the categorized data; track the progress of maintenance tasks in real-time; update the facility management database with the status of the maintenance tasks and operational data; and provide visualization of the facility status and maintenance history through a graphical user interface.
In some aspects of the present disclosure, the processor further adapted to classify unstructured data into predefined categories linked to specific assets.
In some aspects of the present disclosure, the processor further adapted to automatically send alerts to facility management personnel for any maintenance tasks based on real-time monitoring.
In some aspects of the present disclosure, the processor further adapted generates operational reports that include maintenance history and asset performance analytics.
In some aspects of the present disclosure, the processor further adopted to Open BIM standards to ensure seamless data exchange between a facility management engine and third-party facility management tools, enhancing interoperability.
In some aspects of the present disclosure, the input data includes facility details, maintenance schedules, operational information, and unstructured data.
In some aspects of the present disclosure, an output interface that is configured to graphical representations of a Building Information Model (BIM) of the metro rail facility, including geometric and structural details of various components such as stations, tracks, and equipment.
In some aspects of the present disclosure, wherein the structured information includes geometric data related to facility components such as escalators, elevators, tracks, and telecommunication systems.
In some aspects of the present disclosure, a method of operating a system is provided. The method includes receiving one or more inputs via a user device, wherein the inputs include facility details, maintenance schedules, and operational information. The method further includes extracting details representing each parameter from the received inputs by a processor. Categorizing the extracted parameters into structured information for maintenance tasks and unstructured information by a classifying engine. Linking unstructured documents to specific parameters to enhance context and accessibility by integration engine. Generating a maintenance action plan based on the categorized data by a maintenance scheduling engine. Tracking the progress of maintenance tasks in real-time by a reporting and feedback engine. Updating a facility management database with the status of the maintenance tasks and operational data by the processor. And providing visualization of the facility status and maintenance history through a graphical user interface by the processor.
BRIEF DESCRIPTION OF DRAWINGS
The accompanying drawings, which are incorporated in and constitute a part of this specification, show certain aspects of the subject matter disclosed herein and together with the description, help explain some of the principles associated with the disclosed implementations. In the drawing,
Figure 1 illustrates a BIM enabled FM process for metro rail project system, in accordance with an aspect of the present disclosure; and
Figure 2 illustrates a method of BIM enabled FM process for metro rail project system, in accordance with an aspect of the present disclosure.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the disclosure. Thus, the following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, known details are not described in order to avoid obscuring the description.
References to one or an embodiment in the present disclosure can be references to the same embodiment or any embodiment; and such references mean at least one of the embodiments.
Reference to "one embodiment", "an embodiment", "one aspect", "some aspects", "an aspect" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others.
The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Alternative language and synonyms may be used for any one or more of the terms discussed herein, and no special significance should be placed upon whether or not a term is elaborated or discussed herein. In some cases, synonyms for certain terms are provided.
A recital of one or more synonyms does not exclude the use of other synonyms.
The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only and is not intended to further limit the scope and meaning of the disclosure or of any example term. Likewise, the disclosure is not limited to various embodiments given in this specification. Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, technical and scientific terms used herein have the meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control.
Additional features and advantages of the disclosure will be set forth in the description which follows, and in part will be obvious from the description, or can be learned by practice of the herein disclosed principles. The features and advantages of the disclosure can be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features of the disclosure will become more fully apparent from the following description and appended claims or can be learned by the practice of the principles set forth herein.
The terms "system 100" and "BIM enabled FM process for metro rail project system 100" are interchangeably used across the context.
As mentioned before, there is a need for technology that overcomes these drawbacks. The present disclosure, therefore, introduces a system and method for an intelligent facility management engine that addresses the limitations of conventional BIM enabled FM process for metro rail project. The facility management engine described herein is communicatively coupled with a user device, enabling the receipt of input data. The facility management engine is designed to extract details representing each parameter of the one or more inputs; categorize the extracted parameters into structured and unstructured information for facility management tasks; link unstructured documents to specific parameters to enhance context and accessibility; generate a maintenance action plan based on the categorized data; track the progress of maintenance tasks in real-time; update the facility management database with the status of the maintenance tasks and operational data; and provide visualization of facility status and maintenance history through a graphical user interface.
Figure 1 illustrates a BIM enabled FM process for metro rail project system 100, in accordance with an aspect of the present disclosure. The system 100 includes a user device 102 and a facility management engine 104. The user device 102 and the facility management engine 104 are coupled with each other by way of a communication network 106. In some other aspects of the present disclosure, the user device 102 and the facility management engine 104 are communicably coupled through separate communication networks established therebetween.
In some aspects of the present disclosure, the communication network 106 may include suitable logic, circuitry, and interfaces that may be configured to provide a plurality of network ports and a plurality of communication channels for transmission and reception of data related to operations of various entities (such as the user device 102 and the facility management engine 104) of the system 100. Each network port may correspond to a virtual address (or a physical machine address) for the transmission and reception of the communication data. For example, the virtual address may be an Internet Protocol Version 4 (IPV4) (or an IPV6 address), and the physical address may be a Media Access Control (MAC) address. The communication network 106 may be associated with an application layer for implementation of communication protocols based on one or more communication requests from the user device 102 and the facility management engine 104. The communication data may be transmitted or received via the communication protocols. Examples of the communication protocols may include, but are not limited to, Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP), Domain Network System (DNS) protocol, Common Management Interface Protocol (CMIP), Transmission Control Protocol and Internet Protocol (TCP/IP), User Datagram Protocol (UDP), Long Term Evolution (LTE) communication protocols, or any combination thereof. In some aspects of the present disclosure, the communication data may be transmitted or received via at least one communication channel of a plurality of communication channels in the communication network 106. The communication channels may include but are not limited to, a wireless channel, a wired channel, or a combination of wireless and wired channel thereof. The wireless or wired channel may be associated with data standards which may be defined by one of a Local Area Network (LAN), a Personal Area Network (PAN), a Wireless Local Area Network (WLAN), a Wireless Sensor Network (WSN), Wireless Area Network (WAN), Wireless Wide Area Network (WWAN), a metropolitan area network (MAN), a satellite network, the Internet, a fiber optic network, a coaxial cable network, an infrared (IR) network, a radio frequency (RF) network, and a combination thereof. Aspects of the present disclosure are intended to include or otherwise cover any type of communication channel, including known, related art, and/or later developed technologies.
The user device 102 may be capable of facilitating a user to provide input data (this data includes facility details, such as building geometry, maintenance schedules, and operational information related to the metro rail infrastructure and the like), share one or more results, and/or transmit data within the system 100.
In some aspects of the present disclosure, the one or more input parameters may be associated with a subject. In some aspects of the present disclosure, the one or more input data may include, but are not limited to, details representing facility details, such as building geometry, maintenance schedules, and operational information related to the metro rail infrastructure and the like. It will be apparent to a person of ordinary skill in the art that the user may be any person using or operating the system 100, without deviating from scope of the disclosure. Examples of the user device 102 may include but are not limited to, a desktop, a notebook, a laptop, a handheld computer, a touch-sensitive device, a keyboard, a microphone, a mouse, a joystick, a computing device, a smart-phone, and/or a smartwatch. It may be apparent to a person of ordinary skill in the art that the user device 102 may include any device/apparatus that is capable of manipulation by the user.
The user device 102 may include an input interface 108 and an output interface 110.
The input interface 108 may be adapted for receiving input data provided by the user. The user may be operational staff , data analysts , project engineers and the like. In some aspects of the present disclosure, the input interface may include but is not limited to, a touch interface, a mouse, a keyboard, a motion recognition unit, a gesture recognition unit, a voice recognition unit, or the like. Aspects of the present disclosure are intended to include and/or otherwise cover any type of interface, including known, related, and later developed interfaces.
The output interface 110 may be adapted for displaying (or presenting) an output to the user. In some aspects of the present disclosure, the output interface may include but is not limited to, a display device, a printer, a projection device, and/or a speaker. In some other aspects of the present disclosure, the output interface may include but is not limited to, a digital display, an analog display, a touch screen display, a graphical user interface, a website, a webpage, a keyboard, a mouse, a light pen, an appearance of a desktop, and/or illuminated characters.
The facility management engine 104 may be communicatively coupled with the user device 102. The facility management engine 104 may be configured to receive one or more input data provided by the user device 102. The facility management engine 104 may be configured to extract details representing each parameter of the input data. The facility management engine 104 may be configured to categorize the parameters into structured and unstructured from the input data. Upon categorizing the parameters, the facility management engine 104 may be configured to link unstructured documents to specific parameters to enhance context and accessibility. Additionally, the facility management engine 104 may further be configured to generate a maintenance action plan based on the categorized data, track the progress of maintenance tasks in real-time; update the facility management database with the status of the maintenance tasks and operational data; and provide visualization of the facility status and maintenance history through a graphical user interface.
The facility management engine 104 may include a network interface 108, an I/O interface 110, a storage unit 112, and a processor 114. The network interface 108, the I/O interface 110, the storage unit 112, and the processor 114 may be communicatively coupled with each other by way of a first communication bus 116.
The network interface 108 may include suitable logic, circuitry, and interfaces that may be configured to establish and enable a communication between the user device 102 and different components of the system 100. The network interface 108 may be implemented by way of various known technologies to support wired or wireless communication of the processor 114 with the communication network 106. The network interface 108 may include, but is not limited to, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and a local buffer circuit.
The I/O interface 110 may include suitable logic, circuitry, interfaces, and/or code that may be configured to receive inputs (e.g., orders) and transmit server outputs via a plurality of data ports in the facility management engine 104. The I/O interface 110 may include various input and output data ports for different I/O devices. Examples of such I/O devices may include but are not limited to, a touch screen, a keyboard, a mouse, a joystick, a projector audio output, a microphone, an image- capture device, a liquid crystal display (LCD) screen, and/or a speaker.
The storage unit 112 may be configured to store logic, instructions, circuitry, interfaces, and/or codes of the processor 114 to enable the processor 114 to execute the one or more operations associated with the system 100. The storage unit 112 may be further configured to store therein, data associated with the system 100, and the like. It will be apparent to a person having ordinary skill in the art that the storage unit 112 may be configured to store various types of data associated with the system 100, without deviating from the scope of the present disclosure. Examples of the storage unit 112 may include but are not limited to, a Relational database, a NoSQL database, a Cloud database, an Object-oriented database, and the like. Further, the storage unit 112 may include associated memories that may include, but is not limited to, a Read-Only Memory (ROM), a Random Access Memory (RAM), a flash memory, a removable storage drive, a hard disk drive (HDD), a solid-state memory, a magnetic storage drive, a Programmable Read Only Memory (PROM), an Erasable PROM (EPROM), and/or an Electrically EPROM (EEPROM). Embodiments of the present disclosure are intended to include or otherwise cover any type of the storage unit 112 including known, related art, and/or later developed technologies. In some embodiments of the present disclosure, a set of centralized or distributed networks of peripheral memory devices may be interfaced with the facility management engine 104, as an example, on a cloud server or a user device 102. The storage unit 112 contains both structured data (such as 3D models, facility layouts, sensor readings and the like) and unstructured data (such as PDF maintenance manuals, spreadsheets, other documents and the like).
The processor 114 may be configured to execute various operations associated with the system 100. Specifically, the processor 114 may be configured to execute the one or more operations associated with the system 100 by communicating one or more commands and/or instructions to the user device 102. Examples of the processor 114 may include, but are not limited to, an application-specific integrated circuit (ASIC) processor, a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a field-programmable gate array (FPGA), a Programmable Logic Control unit (PLC), and the like. Embodiments of the present disclosure are intended to include and/or otherwise cover any type of the processor 114 including known, related art, and/or later developed technologies.
The processor 114 may include a classifying engine 118, an integration engine 120, a maintenance scheduling engine 122, and a reporting and feedback engine 124. The classifying engine 118, the integration engine 120, the maintenance scheduling engine 122, and the reporting and feedback engine 124 may be coupled with each other by way of a second communication bus 126.
The classifying engine 118 may be configured to receive one or more input data provided by the user by way of the user device 102.
The classifying engine 118 may further be configured to extract details representing each parameter in the input data. The classifying engine 118 may further be configured to classify the parameters into structured and unstructured parameters from the input data.
In some aspects of the present disclosure, structured information includes geometric or numeric in nature, such as facility layouts, equipment dimensions, and maintenance schedules. This type of information is organized in a defined format, enabling easy access and analysis. In contrast, unstructured information consists of documents such as PDFs, manuals, and other non-structured formats that are essential for facility management but do not conform to a specific organizational schema.
In some aspects of the present disclosure, upon classifying the unstructured parameters, the integration engine 120 may be configured to link the unstructured data with its corresponding structured data. For instance, if a specific piece of equipment requires maintenance, the system links the PDF manual for that equipment with geometric data (such as its location in the facility) to ensure all relevant information is easily accessible. This integration ensures that the system provides context to each piece of data, enabling facility managers to retrieve documents directly linked to the task.
Another example is, when maintenance is required for an escalator; the integration engine 120 retrieves both the geometric specifications and the associated maintenance manual from the storage unit 112. This interconnected access enables technicians to efficiently review technical details alongside relevant procedures, enhancing informed decision-making and streamlining maintenance actions within the facility management process.
The maintenance scheduling engine 122 may be configured to generate a maintenance action plan based on the categorized data. The maintenance scheduling engine 122 may further be configured to automate and optimize the scheduling of maintenance tasks within the BIM-enabled Facility Management system. Utilizing categorized data from the classifying engine 118, that includes structured information such as maintenance schedules and unstructured data like historical reports, to generate detailed maintenance action plans. These plans prioritize tasks, allocate resources, and establish timelines to ensure the efficient execution of maintenance activities. The maintenance scheduling engine 122 dynamically adjusts schedules based on real-time feedback from the reporting and feedback engine 124, enabling task reallocation in response to delays or unforeseen issues. This automation significantly reduces downtime, enhances operational efficiency, and ensures timely maintenance across metro rail facilities, ultimately contributing to improved performance and reliability.
The reporting and feedback engine 122 may be configured to track the progress of maintenance tasks in real-time. The reporting and feedback engine 122 may further be configured to update the facility management database with the status of the maintenance tasks and operational data.
In some aspects of the present disclosure, the reporting and feedback engine 122 tracks the progress of ongoing maintenance tasks in real time. It monitors various factors, such as task completion status, delays, or any unexpected issues that arise during maintenance. This real-time monitoring provides facility managers with instant feedback, enabling them to make quick decisions or adjustments to the plan if necessary.
In some aspects of the present disclosure, the system 100 continuously updates the status of each task and logs all relevant details in the facility management database, which is stored in the storage unit 112. The database is updated with real-time operational data, ensuring that the facility's records are always current and accurate.
In some aspects of the present disclosure, once the tasks are being tracked and updated, the system 100 provides facility managers with an intuitive Graphical User Interface (GUI) via the user device 102. This interface offers a comprehensive view of the facility's current status, including a visual representation of ongoing tasks, completed tasks, and any pending actions. The GUI allows managers to monitor facility status at a glance, making it easier to manage operations and ensure that all maintenance activities are running smoothly.
In some aspects of the present disclosure, through the GUI, managers can also access the system's historical data, including maintenance history, equipment performance, and past issues. This information is crucial for long-term planning and ensuring that facility management is proactive rather than reactive.
In some aspects of the present disclosure, further comprise the step of using a cloud-based platform for the digital transfer of project information between different stakeholders.
In some aspects of the present disclosure, the user device is configured to allow remote access to the facility management system via the cloud.
Figure 2 illustrates a method of a BIM enabled FM process for metro rail project system, in accordance with an aspect of the present disclosure. The present method 200 relates to the working of a system 100 designed to create an integrated system for facility management in metro rail projects using Building Information Modeling (BIM) and Open BIM standards. The method 200 is designed to enhance data integration, automate maintenance processes, facilitate real-time tracking, improve communication among stakeholders, and provide effective visualization for efficient management.
At step 202, the system 100 involves receiving one or more inputs through a user device 102. The input data includes facility details, maintenance schedules, and operational information.
At step 204, the system 100 is configured to extract relevant details from the input data which may include data related to facility management and maintenance by utilizing a processor 114.
At step 206, the system 100 is configured to classify the extracted parameters into different categories by a classifying engine 118 based on their relevance. The classifying engine 118 categorizes the extracted parameters into structured information, primarily used for maintenance tasks, and unstructured information, such as documents and other related data.
At step 208, the system 100 is configured to link unstructured documents, such as PDFs or spreadsheets, to specific parameters, enhancing context and accessibility for maintenance tasks by an integration engine 120.
At step 210, the System 100 is configured to generate a detailed maintenance action by maintenance scheduling engine 122 plan based on the categorized structured and unstructured data, enabling efficient scheduling of tasks.
At step 212, the system 100 is configured to continuously track the progress of maintenance tasks in real-time, ensuring that updates are captured and reported promptly by reporting and feedback engine 124.
At step 214, the system 100 is configured to update a facility management database with the status of ongoing maintenance tasks and operational data, ensuring that the system remains current.
At step 216, the System 100 is configured to provide a graphical user interface that visualizes the status of the facility, as well as the maintenance history, allowing users to view and manage tasks effectively.
Advantages:
• The present disclosure provides a combination of structured and unstructured data, improving accessibility and streamlining facility management tasks.
• The present disclosure introduces the automated generation of maintenance action plans, optimizing task scheduling and reducing downtime.
• The present disclosure enables continuous tracking of maintenance progress, facilitating faster decision-making and ensuring timely updates.
• The present disclosure ensures that linking documents to specific tasks enhances communication and coordination among stakeholders.
• The present disclosure provides a graphical interface that offers a comprehensive view of facility status and maintenance history for easier management.
• The present disclosure continuously updates the facility management database, ensuring reliable and centralized data storage.
The implementation set forth in the foregoing description does not represent all implementations consistent with the subject matter described herein. Instead, they are merely some examples consistent with aspects related to the described subject matter. Although a few variations have been described in detail above, other modifications or additions are possible. In particular, further features and/or variations can be provided in addition to those set forth herein. For example, the implementation described can be directed to various combinations and sub combinations of the disclosed features and/or combinations and sub combinations of the several further features disclosed above. In addition, the logic flows depicted in the accompanying figures and/or described herein do not necessarily require the particular order shown, or sequential order, to achieve desirable results. Other implementations may be within the scope of the following claims.
, Claims:1. A system (100) comprising:
a user device (102) that is adapted to receive one or more inputs, wherein the inputs include facility details, maintenance schedules, and operational information;
a facility management engine (104) communicatively coupled with the user device (102) through a communication network (106); the facility management engine (104) including:
a processor (114) that is configured to process the input data; and the processor (114) is adapted to:
(i) ) receive one or more inputs via the user device (102);
(ii) extract details representing each parameter of the one or more inputs;
(iii) categorize the extracted parameters into structured and unstructured information for facility management tasks;
(iv) link unstructured documents to specific parameters to enhance context and accessibility;
(v) generate a maintenance action plan based on the categorized data;
(vi) track the progress of maintenance tasks in real-time;
(vii) update the facility management database with the status of the maintenance tasks and operational data; and
(viii) provide visualization of the facility status and maintenance history through a graphical user interface.
2. The system (100) as claimed in claim 1, wherein the processor (114) further adapted to classify unstructured data into predefined categories linked to specific assets.
3. The system (100) as claimed in claim 1, wherein the processor (114) further adapted to automatically send alerts to facility management personnel for any maintenance tasks based on real-time monitoring.
4. The system (100) as claimed in claim 1, wherein the processor (114) further adapted generates operational reports that include maintenance history and asset performance analytics.
5. The system (100) as claimed in claim 1, wherein the processor (114) further adopted to Open BIM standards to ensure seamless data exchange between a facility management engine 104 and third-party facility management tools, enhancing interoperability.
6. The system (100) as claimed claim 1, wherein the input data includes facility details, maintenance schedules, operational information, and unstructured data.
7. The system (100) as claimed in claim 1, wherein an output interface (110) that is configured to graphical representations of a Building Information Model (BIM) of the metro rail facility, including geometric and structural details of various components such as stations, tracks, and equipment.
8. The system (100) as claimed in claim 1, wherein the structured information includes geometric data related to facility components such as escalators, elevators, tracks, and telecommunication systems.
9. The system (100) as claimed in claim 1, wherein the unstructured information includes maintenance manuals, operational instructions, and historical reports.
10. A method (200) of working system (100), comprising the steps of:
(a) receiving (202) one or more inputs via a user device (102), wherein the inputs include facility details, maintenance schedules, and operational information;
(b) extracting (204) details representing each parameter from the received inputs by a processor (114);
(c) categorizing (206) the extracted parameters into structured information for maintenance tasks and unstructured information by a classifying engine (118);
(d) linking (208) unstructured documents to specific parameters to enhance context and accessibility by integration engine (120);
(e) generating (210) a maintenance action plan based on the categorized data by a maintenance scheduling engine (122);
(f) tracking (212) the progress of maintenance tasks in real-time by a reporting and feedback engine (124);
(g) updating (214) a facility management database with the status of the maintenance tasks and operational data by the processor (114); and
(h) providing (216) visualization of the facility status and maintenance history through a graphical user interface by the processor (114).

Documents