Work range system and method of using work range system

Abstract

A system for work scope definition for an asset is provided. The system includes a processor and a memory including instructions that, when executed by the processor, cause the processor to perform operations including obtaining information indicative of a service announcement and associating the information with a module of the asset.

Description

[0001] This application is a divisional application of the invention patent application filed on June 12, 2018, with application number 201880038685.5 and the invention title "Working Range System and Method of Using Working Range System". Cross-reference to related applications

[0002] This disclosure claims the benefit of U.S. Provisional Patent Application No. 62 / 518,332, filed June 12, 2017, the entire contents of which are incorporated herein by reference. Background Technology

[0003] Managing a large fleet of industrial assets typically requires scheduling and executing maintenance tasks to repair faulty equipment, prevent future failures, and / or comply with regulatory requirements. Typically, when assets arrive at the maintenance shop, a management system is used to plan, execute, and track various tasks. Given the complexity of the tasks to be performed and the technical complexity of the assets to be repaired, these typical management systems require significant human resources and decision-making. Furthermore, there is currently no standardized methodology for storing and retrieving work scope information for use and tracking. Therefore, maintenance shops store work scope information in different formats without standardization. This results in the shop spending considerable time searching for work scope-related information in different locations, further reducing productivity. In addition, the rate of work scope upgrades may be higher than expected, and the number of upgrades can have significant financial implications. Summary of the Invention

[0004] One embodiment provides a system for defining the scope of work for an asset. The system includes a processor and a memory, the memory including instructions that, when executed by the processor, cause the processor to perform operations including retrieving information indicating a service notification and associating that information with the asset.

[0005] Another embodiment provides a system for delimiting the scope of an asset. The system includes a processor and memory containing instructions that, when executed by the processor, cause the processor to perform certain operations. These operations include mapping service announcements to modules of the asset.

[0006] Another embodiment provides a system for defining the scope of work for an asset. The system includes a processor and memory, the memory including instructions that, when executed by the processor, cause the processor to perform certain operations. These operations may include: determining service announcements for modules applicable to the asset based on the identity of the asset or module; mapping service announcements to modules; and associating disassembly levels with service announcements. The operations may further include adding a set of modules to the service announcement. Attached Figure Description

[0007] Figure 1 A controller according to one embodiment is shown.

[0008] Figure 2 A screenshot according to one embodiment is shown.

[0009] Figure 3 A screenshot according to one embodiment is shown.

[0010] Figure 4 A screenshot according to one embodiment is shown. Detailed Implementation

[0011] Illustrative embodiments may take the form of various components and arrangements of components. Illustrative embodiments are shown in the accompanying drawings, and similar reference numerals may indicate corresponding or similar portions in the various drawings throughout. The drawings are for illustrative purposes only and should not be construed as limiting this disclosure. The novel aspects of this disclosure will become apparent to those skilled in the art from the following description of the accompanying drawings.

[0012] As mentioned above, maintenance workshops typically store work scope information in different formats without standardization. This can lead to workshop personnel spending significant time searching for work scope-related information in different locations, thus reducing productivity. Furthermore, work scope upgrades may occur more frequently than expected, and the number of upgrades can significantly increase costs.

[0013] Thus, exemplary embodiments provide tangible data associated with the reasons for work scope upgrades, and these enable processes to determine when an upgrade will occur, associate costs with the upgrade, and prevent the upgrade, thereby enabling the execution of an optimal work scope that maximizes the field usage time of the asset. For example, when the asset is an aircraft engine, field usage time corresponds to the time the engine spends on the wing without requiring maintenance.

[0014] The exemplary scope of work tool according to the embodiments enables the intelligent mapping of Service Notices (SBs) to specific modules (i.e., ATAs). Specifically, within an asset, there are modules that define the entire asset, and these modules perform different functions and / or have different uses. For example, for an engine, modules may be, but are not limited to, fans, compressors, burners, and HPTs. Therefore, in the exemplary scope of work tool, SBs can be mapped to modules via a pre-existing or predetermined set of criteria or via a mapping table. Additionally or alternatively, SBs can be dynamically mapped to modules. For example, optical character recognition, machine learning, and / or artificial intelligence can be used to map SBs to modules.

[0015] Furthermore, the exemplary embodiments described herein provide a method for mapping a Service Scope (SB) to a corresponding work scope level based on the level of disassembly, so that the module of the asset can perform the maintenance indicated or required in the SB. For example, a given module may have four progressively escalating disassembly levels, where the first disassembly level (e.g., 1) requires the shop or technician to hold the module without disassembly and perform no repairs, while the fourth disassembly level requires the shop or technician to completely disassemble the module down to the component level. In this case, the exemplary work scope tool can map the SB to a module at one of the four disassembly levels based on the needs of the SB. Mapping can be done based on a pre-existing or predetermined set of criteria or via a mapping table. Alternatively or alternatively, mapping can be done dynamically. For example, mapping can be done via machine learning and / or artificial intelligence.

[0016] Furthermore, the embodiments described herein can provide the ability to add multiple modules to the SB. For example, a part contained in the SB as a first module may affect multiple other modules. Therefore, the exemplary work scope tool is capable of adding multiple other modules to the SB. Other modules can be added to the SB dynamically. For example, the work scope tool can analyze the SB and the components or parts contained in the notification, and based on the analysis, identify other modules affected by the components or parts; furthermore, the work scope tool can add other modules to the work scope or the SB.

[0017] Embodiments of the features described herein also provide the ability to automatically drive work scope dismantling levels based on Service Scope (SB). If a module has multiple SBs, the exemplary work scope tool can analyze the multiple SBs and determine or drive the dismantling level for that module. For example, if a module has three SBs, where the first SB requires dismantling level 1, the second SB requires dismantling level 2, and the third SB requires dismantling level 4, the work scope tool can determine that the appropriate or required dismantling level to complete or satisfy all SBs is 4. Similarly, given a current dismantling level for a module, the work scope tool can identify conflicts and determine new dismantling levels, thereby allowing the shop floor or technicians to determine the need for or desire of additional services beyond the service bulletin. For example, if a module's current dismantling level is 2, and a technician desires additional services for that module, the work scope tool can determine that the additional service would escalate the module's dismantling level and identify the costs associated with the upgrade to a dismantling level.

[0018] Furthermore, exemplary work scope tools can provide the ability to determine the SB (Solution Requirement) for a specific asset applicable to a module based on the identity of the asset or module. For example, an exemplary work scope tool can determine the SB applicable to a specific engine based on the engine's serial number. For example, an exemplary work scope tool can identify an engine based on its serial number, determine and subtract SBs previously completed for the engine, and determine and add unresolved SBs.

[0019] Figure 1 A block diagram of controller 100 is shown, which may include a processor 114 with a specific architecture. Controller 100 may be part of the exemplary working scope tool described above, endowed with the specific features discussed. The specific architecture of processor 114 may be endowed by instructions stored in memory 102 included (or accessible) in controller 100 and / or by instructions 118 that can be retrieved by processor 114 from storage medium 120. Storage medium 120 may be located in the same location as controller 100 as shown, or it may be located elsewhere and communicatively coupled to controller 100.

[0020] Controller 100 may be a standalone programmable system or a programmable module within a larger system. The controller may include one or more hardware and / or software components configured to acquire, decode, execute, store, analyze, distribute, evaluate, and / or classify information. Furthermore, controller 100 may include an input / output (I / O) module 112, which may be configured to interact with multiple databases (e.g., databases 122, 124, and 126). These databases may include information relating to a specific module's SB to be applied to the asset under test, depending on instructions 118 or instructions retrieved from memory 102.

[0021] Processor 114 may include one or more processing devices or cores (not shown). In some embodiments, processor 114 may be a plurality of processors, each having one or more cores. Processor 114 may be configured to execute instructions fetched from memory 102 (i.e., from one of memory blocks 104, 106, 108 or 110), or from storage medium 120 or from a remote device connected to controller 100 via communication interface 116.

[0022] Without loss of generality, storage medium 120 and / or memory 102 may include volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, non-removable, read-only, random access, or any type of non-transitory computer-readable computer medium. Storage medium 120 and / or memory 102 may include programs and / or other information that can be used by processor 114. Furthermore, storage medium 120 may be configured to record data processed, recorded, or collected during operation of controller 100. Data may be timestamped, location-stamped, cataloged, indexed, or organized in various ways consistent with data storage practices.

[0023] In one embodiment, for example, storage blocks 106, 108, or 110 may include instructions that, when executed by processor 114, cause processor 114 to perform certain operations. These operations may include determining, based on the identity of the asset or module, which service announcements retrieved from one of databases 122, 124, and 126 are applicable to the module of the asset. The identity of the asset or module may be received via I / O module 112. The operations may further include mapping specific service announcements to assets or modules, and they may further include associating disassembly levels with service announcements. The operations may also include adding a set of modules to the service announcement, thereby updating the service announcement and saving it back to one of databases 122, 124, and 126. After completing the above operations, controller 100 may output a working scope template 128.

[0024] Figure 2 Example screenshot 200 of the updated work scope template 128 is shown. Work scope template 128 may include field 202 indicating all SBs that have been acquired by processor 114. Field 204 may indicate the date the work scope was performed. Field 206 indicates the module associated with each acquired SB, while field 208 may include descriptive information related to each SB. Field 210 may indicate an identifier for a specific manufacturer or asset. Work scope template 128 may further include field 212 indicating the number of revisions associated with each SB. Work scope template 128 also includes fields 214, 216, and 218, which respectively indicate the disassembly level determined for each module based on its applicable SB, for deriving the interactive features of work scope template 128, and compliance information associated with that SB. Note that screenshot 200 represents an exemplary configuration, and the structure of work scope template 128 may differ from that shown without departing from the scope of this disclosure.

[0025] Figure 3Screenshot 300 illustrates additional features of the work scope template 128. For example, the work scope template 128 may include a field 302 indicating a specific module and a field 304 for selecting a specific SB that has been mapped. Screenshot 300 also includes the disassembly level indicated by field 306 and additional work scope information shown in field 308. Field 310 can be used to enter comments for future reference.

[0026] All possible Service Scopes (SBs) mapped to the modules identified in field 302 can be tabulated in field 312. When a user selects a specific SB, such as in field 314, the exemplary work scope tool can prompt the user that the selected SB will increase the disassembly level of the modules listed in field 306. At this point, the user can either stop and select another SB, or override the notification and continue with the increased disassembly level.

[0027] like Figure 4 As shown in screenshot 400, the work scope template 128 can be updated to indicate that the selected SB is associated with a specific module. The SB mapping feature of the exemplary work scope tool brings SB applicability to each asset (e.g., each engine). SBs and their impact on work scope breakdown levels are provided for the work scope level logic. Furthermore, the exemplary work scope tool makes the work scope breakdown levels and costs visible (field 402). Additionally, the exemplary work scope tool provides visibility into how it affects multiple modules and breakdown levels. Thus, the exemplary work scope tool has many advantages over typical work scope tools. For example, typical tools attempt to find all SBs in a non-standardized manner from customer and store records. Therefore, it is impossible to understand how SBs drive work scope levels using typical tools. Furthermore, typical tools cannot understand the impact of SB driving costs, nor can they understand the impact of an SB on multiple modules and the breakdown levels it drives.

[0028] Those skilled in the art will understand that various modifications and variations of the above embodiments can be configured without departing from the scope and spirit of this disclosure. Therefore, it is to be understood that the teachings of this document can be practiced in ways different from those specifically described herein, within the scope of the appended claims.

Claims

1. A system for defining the scope of work for assets, characterized in that, The system includes: The controller includes an input / output module and a processor; The memory contains instructions that, when executed by the processor, cause the processor to perform operations, the operations including: Obtain information from the instruction service notification; Dynamically execute smart mapping of the service announcement to one or more modules of the asset; Based on (i) the requirements of the service announcement and (ii) one or more additional factors affecting the determined scope of work, the breakdown level of each of the one or more modules is dynamically determined; and Based on the dynamically determined disassembly level, the predetermined disassembly level of the service announcement is changed; The controller is configured to output a working range template via the input / output module, wherein the working range template displays (i) identity information associated with each of the one or more modules, and (ii) a graphical representation of the disassembly level determined for each of the one or more modules in a first part of the working range template; The work scope template displays (i) the acquired service announcement and (ii) at least one selectable service announcement in its second part, wherein the acquired service announcement is indicated along with one or more corresponding modules; and When a user selects an optional service announcement from the second part of the work scope template, the system is configured to notify the user whether the service announcement will increase the disassembly level of one or more modules by updating the graphical representation of the disassembly level displayed in the first part of the work scope template.

2. The system according to claim 1, characterized in that, The operation further includes determining a set of service announcements applicable to the module based on the module's identity.

3. The system according to claim 1, characterized in that, The operation further includes identifying and subtracting previously completed service notifications, and identifying and adding unresolved service notifications.

4. The system according to claim 1, characterized in that, The one or more additional factors mentioned include conflicts between the service announcement and one or more additional service announcements.

5. The system according to claim 4, characterized in that, The operation further includes: identifying conflicts and determining a new disassembly level for the module.

6. A system for defining the scope of work for assets, characterized in that, The system includes: processor; The memory contains instructions that, when executed by the processor, cause the processor to perform operations, the operations including: Based on the identity of the asset or the module, determine the service announcement applicable to the first module of the asset; Map the service announcement to the first module; The dismantling level is associated with the service notice based on (i) the requirements of the service notice and (ii) one or more additional factors that affect the determined scope of work level; Based on a dynamically determined disassembly level, the predetermined disassembly level of the service announcement is changed; and Based on the impact of the service announcement on the first module, one or more additional modules are dynamically added to the service announcement; The controller containing the memory is configured to output a working range template via an input / output module, wherein the working range template displays (i) identity information associated with the first module and (ii) a graphical representation of the disassembly level determined for the first module in a first portion of the working range template; The work scope template displays (i) the acquired service announcement and (ii) at least one selectable service announcement in its second part, wherein the acquired service announcement is indicated together with the first module; and When a user selects an optional service announcement from the second part of the work scope template, the system is configured to notify the user whether the service announcement will increase the disassembly level of the first module and the one or more additional modules by updating the graphical representation of the disassembly level displayed in the first part of the work scope template.

7. The system according to claim 6, characterized in that, The operation further includes automatically determining a scope of work breakdown level based on the service announcement, analyzing the service announcements determined to be applicable to the module, and automatically modifying the scope of work breakdown level to resolve all the service announcements for the module.

8. The system according to claim 6, characterized in that, The one or more additional factors mentioned include conflicts between the service announcement and one or more additional service announcements.

9. A system for defining the scope of work for assets, characterized in that, The system includes: The controller includes an input / output module and a processor; The memory contains instructions that, when executed by the processor, cause the processor to perform operations, the operations including: Dynamically execute smart mapping of the service announcement to one or more modules of the asset; Based on (i) the requirements of the service announcement and (ii) one or more additional factors affecting the determined scope of work level, the breakdown level of each of the one or more modules is dynamically determined; Based on the determined disassembly level, change the predetermined disassembly level of the one or more service announcements; The controller is configured to output a working range template via the input / output module, wherein the working range template displays (i) identity information associated with each of the one or more modules, and (ii) a graphical representation of the disassembly level determined for each of the one or more modules in a first part of the working range template; The work scope template displays (i) the acquired service announcement and (ii) at least one selectable service announcement in the second part of the work scope template, wherein the acquired service announcement is indicated together with the one or more modules; Wherein, when a user selects an optional service announcement from the second part of the work scope template, the system is configured to notify the user whether the service announcement will increase the disassembly level of one or more modules by updating the graphical representation of the disassembly level displayed in the first part of the work scope template; and The mapping is based on a predetermined or pre-existing set of criteria.

10. The system according to claim 9, characterized in that, The mapping mentioned therein includes a mapping table.

Images