Systems and methods are described herein for actively managing the knowledge of a group of people, such as an organization's employees. The systems and methods are implemented in one or more software modules that receive a current alarm event and identify historical information associated with a similar previous alarm event. The historical information associated with a similar previous alarm event can be presented to a user to assist the user in resolving the current alarm event. The software modules can collect new information associated with resolving the current alarm event and store the new information in a manner so that it can be identified easily in the future.
|
1. An active knowledge management computing apparatus comprising a memory coupled to a processor which is configured to execute programmed instructions stored in the memory comprising:
identifying an alarm event based on received device data concerning operation of a monitored device;
determining a relevance of one or more historical resolutions for the identified alarm event for the monitored device based on a ranking function, an aggregate data set relevance, and one or more weights applied to each of the ranking function and the aggregate data set relevance, wherein the aggregate data set relevance is based on one or more distance functions and a distance weighting factor applied to each of the one or more distance functions;
identifying and providing at least a subset of the one or more historical resolutions for the identified alarm event to a client computing device based on the determined relevance; and
receiving and storing a current resolution of the identified alarm event and a ranking of one or more of the provided historical resolutions from the client computing device.
10. A non-transitory computer readable medium having stored thereon instructions for actively managing knowledge comprising machine executable code which when executed by at least one processor, causes the processor to perform steps comprising:
identifying an alarm event based on received device data concerning operation of a monitored device;
determining a relevance of one or more historical resolutions for the identified alarm event for the monitored device based on a ranking function, an aggregate data set relevance, and one or more weights applied to each of the ranking function and the aggregate data set relevance, wherein the aggregate data set relevance is based on one or more distance functions and a distance weighting factor applied to each of the one or more distance functions;
identifying and providing at least a subset of the one or more historical resolutions for the identified alarm event to a client computing device based on the determined relevance; and
receiving and storing a current resolution of the identified alarm event and a ranking of one or more of the provided historical resolutions from the client computing device.
19. A method for actively managing knowledge, the method comprising:
identifying by an active knowledge management computing device an alarm event based on received device data concerning operation of a monitored device;
determining by the active knowledge management computing device a relevance of one or more historical resolutions for the identified alarm event for the monitored device based on a ranking function, an aggregate data set relevance, and one or more weights applied to each of the ranking function and the aggregate data set relevance, wherein the aggregate data set relevance is based on one or more distance functions and a distance weighting factor applied to each of the one or more distance functions;
identifying and providing by the active knowledge management computing device at least a subset of the one or more historical resolutions for the identified alarm event to a client computing device based on the determined relevance; and
receiving and storing by the active knowledge management computing device a current resolution of the identified alarm event and a ranking of one or more of the provided historical resolutions from the client computing device.
3. The apparatus of
4. The apparatus of
5. The apparatus as set forth in
6. The apparatus of
7. The apparatus of
9. The apparatus of
12. The medium of
13. The medium of
14. The medium as set forth in
15. The medium of
16. The medium of
18. The medium of
21. The method of
22. The method of
23. The method as set forth in
24. The method of
25. The method of
27. The method of
|
1. Field of the Invention
The present invention relates generally to the field of knowledge management and more particularly to techniques for capturing and managing the knowledge of employees and other people.
2. Description of the Related Art
Knowledge management systems are systems that collect and manage the knowledge of a group of people, such as the employees of an organization. Knowledge management systems are often implemented using software and computing devices. For example, conventional knowledge management tools and systems include wikis, blogs, filing systems, and document management systems.
Knowledge management systems are critical to maintaining the knowledge of an organization while its employees change over time. An effective knowledge management system will retain and organize the knowledge of an organization so that as existing employees leave the organization and new employees join the organization, the new employees will be able to locate and use the knowledge of the organization and that knowledge will not be lost with the departure of existing employees.
Conventional knowledge management tools and systems are limited in that they can be characterized as passive. In other words, conventional knowledge management tools and systems are dependent on users making a concerted effort to enter information properly so that later users can find relevant information. Users often use conventional knowledge management tools and systems inconsistently so that the organization's knowledge is not captured adequately and is not organized in a manner that makes the information easily accessible in the future.
There is a need for a method and system that actively manages the knowledge of an organization. In other words, a need exists for an improved method and system for gathering and organizing an organization's knowledge that is less dependent on the user's willingness to use the method and system.
The embodiments of the present invention facilitate the active gathering and management of the knowledge of an organization. The embodiments of the present invention provide a method and system for identifying a current alarm event and identifying information associated with a previous alarm event. The information associated with the previous alarm event can be used to resolve the current alarm event. An alarm event can be any indication of an abnormal operating condition.
In a first exemplary embodiment, a system for actively managing the knowledge of an organization is described. The exemplary system comprises an active knowledge management software module that can be installed on a computing device, such as a server computer. The active knowledge management module can receive alarm events from either an alarm system module or a predictive analytics module. The alarm system module and the predictive analytics module can identify alarm events from real time data collected by monitoring devices. The active knowledge management module can receive an alarm selection from a user and display default data associated with the selected alarm. The active knowledge management module can comprise a relevance module that calculates a relevance value for historical resolutions with respect to the selected alarm. The active knowledge management module can display a relevant historical resolution to assist a user in resolving the current alarm. The active knowledge management module collects data from the user about the resolution of the current alarm and can store the data in a historical resolutions data store for future use.
In a second exemplary embodiment, a computer-implemented method for actively managing the knowledge of an organization is described. The exemplary method comprises an active knowledge management software module receiving alarm events from either an alarm system module or a predictive analytics module. The alarm system module and the predictive analytics module can identify alarm events from real time data collected by monitoring devices. The active knowledge management module can receive an alarm selection from a user and display default data associated with the selected alarm. The active knowledge management module can comprise a relevance module that calculates a relevance value for historical resolutions with respect to the selected alarm. The active knowledge management module can display a relevant historical resolution to assist a user in resolving the current alarm. The active knowledge management module collects data from the user about the resolution of the current alarm and can store the data in a historical resolutions data store for future use.
In a third exemplary embodiment, a computer-readable storage medium comprising instructions for actively managing the knowledge of an organization is described. The instructions of the computer-readable storage medium can control the operation of an active knowledge management software module. The instructions can comprise the active knowledge management software module receiving alarm events from either an alarm system module or a predictive analytics module. The alarm system module and the predictive analytics module can identify alarm events from real time data collected by monitoring devices. The instructions can further comprise the active knowledge management module receiving an alarm selection from a user and displaying default data associated with the selected alarm. The instructions can further comprise a relevance module of the active knowledge management module calculating a relevance value for historical resolutions with respect to the selected alarm. The instructions can direct the active knowledge management module to display a relevant historical resolution to assist a user in resolving the current alarm. Finally, the instructions can direct the active knowledge management module to collect data from the user about the resolution of the current alarm and to store the data in a historical resolutions data store for future use.
These and other embodiments are described in the detailed description that follows and the associated drawings.
The preferred embodiments of the present invention are illustrated by way of example and are not limited to the following figures:
The invention is directed to systems and methods using software modules to actively manage knowledge for an organization. Although the exemplary embodiments will be generally described in the context of software modules running in a distributed computing environment, those skilled in the art will recognize that the present invention also can be implemented in conjunction with other program modules in a variety of other types of distributed or stand-alone computing environments. For example, in different distributed computing environments, program modules may be physically located in different local and remote memory storage devices. Execution of the program modules may occur locally in a stand-alone manner or remotely in a client/server manner. Examples of distributed computing environments include local area networks of an office, enterprise-wide computer networks, and the global Internet.
The detailed description that follows is represented largely in terms of processes and symbolic representations of operations in a computing environment by conventional computer components, which can include database servers, application servers, mail servers, routers, security devices, firewalls, clients, workstations, memory storage devices, display devices and input devices. Each of these conventional distributed computing components is accessible via a communications network, such as a wide area network or local area network.
The invention comprises computer programs that embody the functions described herein and that are illustrated in the appended flow charts. However, it should be apparent that there could be many different ways of implementing the invention in computer programming, and the invention should not be construed as limited to any one set of computer program instructions. Further, a skilled programmer would be able to write such a computer program to implement an exemplary embodiment based on the flow charts and associated description in the application text. Therefore, disclosure of a particular set of program code instructions is not considered necessary for an adequate understanding of how to make and use the invention. The inventive functionality of the claimed computer program will be explained in more detail in the following description read in conjunction with the figures illustrating the program flow.
Turning to the drawings, in which like numerals indicate like elements throughout the figures, exemplary embodiments of the invention are described in detail. Referring to
Referring to
The exemplary system illustrated in
As shown in the exemplary system illustrated in
The active knowledge management module 132 installed on server 120 can comprise a variety of software modules as illustrated in
The active knowledge management module 132 can also comprise a workbench selector module 135. The workbench selector module 135 allows a user to browse other data such as unstructured data or data items associated with particular historical resolutions. The workbench selector module 135 can provide a user with additional tools for displaying and analyzing data accessible through the data access layer 124.
The active knowledge management module 132 can comprise an alarm selector module 137. The alarm selector module 137 can receive a user's selection of an alarm from a list of alarms in a display. The alarm selector module 137 and the active knowledge management module 132 can use the selected alarm to retrieve and display default data associated with the alarm and provide the selected alarm to the relevance module 133 for identifying a relevant historical solution.
The relevance module 133 of the active knowledge management module 132 can identify one or more historical resolutions that are relevant to the selected alarm. The relevance module 133 assists the user by identifying historical resolutions in the historical resolution data store 150 that are most likely to be of assistance in resolving the current selected alarm. The relevance module 133 can be designed in a variety of ways to identify similarities between the current selected alarm and historical resolutions of previous alarms. For example, the relevance module 133 can compare the location, equipment type and application type of the equipment associated with the current selected alarm and that of the historical resolution. In other embodiments of the invention only certain of these factors may be compared or other factors may be compared. Furthermore, the relevance module 133 can assign weightings to certain factors that are more or less relevant to a particular type of equipment or a particular type of alarm. One example of an algorithm for determining relevance is the following:
Where, Ri=YA*f1(AppCi, AppH)+ZA*f2(EquipCi, EquipH)+PA*f3 (LocCi, LocH)+ . . .
In the foregoing example, Rank(H) is the ranking function for the historical resolution. A and B are the weights for the ranking and aggregate data set relevance. YA, ZA, and PA are the alarm-specific distance weighting factors. f1 (AppCi, AppH) is the distance function for the application type. f2 (EquipCi, EquipH) is the distance function for the equipment type. f3 (LocCi, LocH) is the distance function for the physical location of the equipment.
Ranking Function Rank(H).
The ranking function returns a summary measure of end user-assessed usefulness. This function is analogous to the ranking functions widely used in Internet commerce, e.g., Netflix user ratings of films, Amazon.com user rating of books, and more specifically the “did you find this article” helpful functionality in technical support websites such as Microsoft Knowledge Base. The purpose of the ranking function in the relevance module is to raise the calculated relevance R(C,H) of historical cases that are highly useful but may be tagged inappropriately for their applicability. Inappropriate tagging occurs when a resolution is associated with an alarm that is not proximate to the root cause of the problem; this occurs with some regularity because the alarm arriving first for triage is frequently the alarm with the tightest control bounds rather than the alarm closest to the problem. For example, a blockage in a platform onboarding valve may trigger a downhole pressure alarm in the related well before triggering the more proximate differential pressure alarm simply because the well's drawdown is being watched closely and therefore tight control bounds have been set on downhole pressure while the differential pressure bounds have remained unchanged. If such a blockage problem is worked through to resolution on the basis of the downhole pressure alarm, it will be incorrectly tagged as a downhole pressure solution if the same type of blockage occurs in the future. This incorrect tagging will substantially lower it's calculated relevance based on distance functions; the ranking function Rank(H) allows for compensation of this type of tagging error.
A and B Weights.
The A and B weights mitigate the bootstrap problem with the ranking function. During the early phases following deployment of the active knowledge management module at a new asset, the relatively sparse set of user rankings can cause a distorted estimate of relevance to be returned by the Rank(H) function (in a similar way that, e.g., an Amazon.com book ranking with 500 responses is more reliably reflective of end user sentiment than one with only two or three responses). The use of A and B weights allows the relative contribution of the ranking function to be given little weight when few user rankings exist and increasing weight as more rankings are applied. For example, the A weight can be initially set to be a small non-zero number and increased as a logarithmic function of the number of user-supplied rankings of (H), i.e., it increases rapidly with the first few rankings and shows diminishing increases as the number of rankings grows large, asymptotically approaching a fixed limit. B is a weighted inverse. The specific logarithmic functions and inverse weighting can be calculated based on the scope and size of the deployment; the number of rankings that can reasonably be expected for each historical resolution is obviously heavily dependent on the size and scope of each particular deployment.
YA, ZA, and PA Distance Weighting Factors.
These factors allow adjustment to the relative importance of application type, equipment type, and location, respectively, when calculating the aggregate data set relevance. These are set per alarm type and are necessary simply because not all distance functions are relevant for all alarm types. As a simple example, consider a choke position alarm. Sudden choke changes can be a problem, and root cause and resolution of the problem are likely to be strongly related to both the equipment type of the choke and the location in which it is installed. Application type, however, makes little sense here—to the extent that e.g., a choke in an onshore tight gas well might have different problems than one in a deepwater oil well, this is already captured by the equipment type and location factors. In this case, YA would be set to zero to discount the relevance of application type. On the other hand, a platform using identical compressors to handle widely varying gas hydration levels might find that problems with a wet gas compressor have more in common with wet gas compressors on other platforms than with the dry gas compressor that is 50 feet away. In this case, the application type is highly relevant and would be adjusted accordingly. As such, the YA, ZA, and PA distance weights typically are established on a case by case basis as part of the alarm development process.
Distance Functions (f1, f2, f3).
The distance functions (f1, f2, f3) assume the existence or creation of partially ordered sets describing a hierarchical relationship between the relevant set members. In practical application, both the members and ordering of these sets will be specific to the industrial particulars of the knowledge to be captured. Generally this information will be present within the data models of existing applications in use for the knowledge capture asset. For example, within the domain of deepwater oil and gas production, the function f2 which defines the distance between two types of equipment would be based on an equipment model hierarchy such as would normally be found in an existing supply chain or preventive maintenance application (e.g., SAP). In such a hierarchy two, e.g., compressors of identical capacity, model, and application would reside in the same part of the hierarchy and have a distance of zero. Compressors with similar capacity and application with a different model type or with similar model type and application but differing capacities would have a small but non-zero distance, and compressors differing in all respects would have a larger distance. This would be equally true for the other functions, for example, the f3 distance function for physical location would use existing production train modeling applications and/or process and instrumentation diagram (P&ID) models as the foundational set for the distance calculation.
Clearly, in a different domain—such as crude refining—the hierarchies would be completely different; both the equipment types and physical locations would be radically different than is the norm in the deepwater production domain. In the particular case of this example, the industrial particulars of the refining domain involve processes and process trains with a much higher degree of complexity than that of deepwater, leading to more complex equipment hierarchies and correspondingly larger distances between related equipment items. Without some type of weighting factor, the higher raw distance values produced by this domain change would tend to weight the equipment distance relatively higher than other distance functions and consequently weight the overall aggregate data set relevance higher than the ranking factor. The weighting factors YA, ZA, and PA address these differences in the range of values returned by the raw distance functions. It should be noted that these factors are alarm-specific; the weights which apply for one alarm type may not apply for all others (even within a similar domain) as for each alarm type the relevance of each distance type will vary.
The foregoing exemplary algorithm is designed to be used as a framework within the relevance module 133. In other words, the weighting factors and distance functions can be modified or tuned for each particular implementation. With each implementation of the relevance module 133, the weighting factors and distance functions can vary in importance and be adjusted accordingly.
Those of skill in the art will recognize that the foregoing algorithm is merely one example for implementing the relevance module 133 and that other methods and techniques can be used in implementing relevance modules for other embodiments of the invention.
The active knowledge management module 132 can further comprise a collaboration cart module 134. The collaboration cart module 134 can allow sharing of data associated with an alarm resolution with another user. For example, in the embodiment illustrated in
The foregoing components of the active knowledge management module 132 are merely examples. Other embodiments of the active knowledge management module 132 may include different features and may comprise different software modules organized in different designs. Furthermore, although the active knowledge management module 132 is shown installed on server 120, in alternate embodiments it may be installed in other computing environments.
The computing device 220 includes a processing unit 221, such as “PENTIUM” microprocessors manufactured by Intel Corporation of Santa Clara, Calif. The computing device 220 also includes system memory 222, including read only memory (ROM) 224 and random access memory (RAM) 225, which is connected to the processor 221 by a system bus 223. The preferred computing device 220 utilizes a BIOS 226, which is stored in ROM 224. Those skilled in the art will recognize that the BIOS 226 is a set of basic routines that helps to transfer information between elements within the computing device 220. Those skilled in the art will also appreciate that the present invention may be implemented on computers having other architectures, such as computers that do not use a BIOS, and those that utilize other microprocessors.
Within the computing device 220, a local hard disk drive 227 is connected to the system bus 223 via a hard disk drive interface 232. A CD-ROM or DVD drive 230, which is used to read a CD-ROM or DVD disk 231, is connected to the system bus 223 via a CD-ROM or DVD interface 234. In other embodiments, other types of storage devices such as external hard disk drives and USB thumb drives can be used. A user enters commands and information into the computing device 220 by using input devices, such as a keyboard 240 and/or pointing device, such as a mouse 242, which are connected to the system bus 223 via a serial port interface 246. Other types of pointing devices (not shown in
The remote computer 211 in this networked environment is connected to a remote memory storage device 250. This remote memory storage device 250 is typically a large capacity device such as a hard disk drive, CD-ROM or DVD drive, magneto-optical drive or the like. Those skilled in the art will understand that software modules are provided to the remote computer 211 via computer-readable media. The computing device 220 is connected to the remote computer by a network interface 153, which is used to communicate over the local area network 173.
In an alternative embodiment, the computing device 220 is also connected to the remote computer 211 by a modem 254, which is used to communicate over the wide area network 252, such as the Internet. The modem 254 is connected to the system bus 223 via the serial port interface 246. The modem 254 also can be connected to the public switched telephone network (PSTN) or community antenna television (CATV) network. Although illustrated in
Although other internal components of the computing device 220 are not shown, those of ordinary skill in the art will appreciate that such components and the interconnection between them are well known. Accordingly, additional details concerning the internal construction of the computing device 220 need not be disclosed in connection with the present invention.
Those skilled in the art will understand that program modules, such as an operating system 235 and other software modules 260a, 263a and 266a, and data are provided to the computing device 220 via computer-readable media. In the preferred computing device, the computer-readable media include local or remote memory storage devices, which may include the local hard disk drive 227, CD-ROM or DVD 231, RAM 225, ROM 224, and the remote memory storage device 250.
Referring to
Turning now to step 302, device monitor 155 collects data from a piece of equipment and provides the data to the real time data store 140. The real time data store 140 can store data for access by various components of the exemplary system shown in
In step 308 of exemplary process 300, the active knowledge management module 132 receives alarm events from the alarm system module 129 and the predictive analytics module 130 and populates an alarm list with the received alarm events. The engineer's workbench module 136 can display the alarm list for a user and the user can select an alarm on which to work. In step 310, the active knowledge management module 132 receives the user's selection from the list of alarms and presents default data relevant to the selected alarm. The default data may be retrieved by the active knowledge management module 132 from any of the data storage modules in the data layer. For example, default data can be retrieved from the real time data store 140, the unstructured data 145, or data items associated with resolutions stored in the historical resolutions data store 150. Examples of default data include specifications for the equipment associated with the alarm event and related data collected by the device monitor 155.
In step 312, the relevance module 133 analyzes resolutions stored in the historical resolutions data store 150 to identify prior resolutions that are relevant to the current alarm selected by the user. As illustrated in
A user working with the engineer's workbench module 136 can review the default data presented in step 310 and the list of relevant historical resolutions presented in step 314 in connection with working on a resolution for the current selected alarm. For example, in step 316, the active knowledge management module 132 can receive a selection from a user of a historical resolution and present data items and contacts associated with the selected historical resolution. While the user would typically select a resolution from the list of related resolutions, as shown in the example in
Referring to step 320 of exemplary process 300, the user can use the collaboration cart module 134 for sharing data items associated with the current solution with other users. The collaboration cart module 134 provides a tool for the user to easily share and discuss the resolution for the current selected alarm with other people. Once the user has decided on a resolution for the current selected alarm, in step 324, the user adopts the data items associated with the resolution for the current selected alarm. In step 326, the active knowledge management module 132 can receive annotations from the user explaining the resolution of the current alarm. In step 328, the active knowledge management module 132 prompts the user to rank the historical resolutions to reflect which were most helpful in reaching the current resolution. In step 330, the active knowledge management module 132 stores the rankings and the resolution of the current selected alarm in the historical resolutions data store 150. The stored resolution can include the annotations received from the user, contact information for people associated with the resolution, and data items associated with the resolution.
Steps 326 through 330 involve capturing the knowledge of the current user in reaching the resolution. By making the knowledge capture part of the process of resolving an alarm, the exemplary method 300 mitigates the loss of knowledge that occurs when individuals leave an organization. Alternate embodiments of the invention may perform variations of steps 326 through 330. However, by incorporating knowledge capture into the process of resolving an alarm, the present invention improves conventional knowledge management approaches. Furthermore, those skilled in the art will appreciate that method 300 illustrated in
Turning to
Referring to
Referring to
In conclusion, the invention, as represented in the foregoing exemplary embodiments, provides systems and methods for actively managing the knowledge of an organization. As described in the foregoing exemplary embodiments, an active knowledge management module can receive current alarm events and provide a user with access to historical data that can assist in resolving the alarm event. The active knowledge management module also can analyze the historical data and identify for the user historical data that is relevant to the current alarm. The user can adopt various elements of historical resolutions is identifying a resolution to the current alarm. The active knowledge management module captures the resolution for the current alarm and any data associated with the resolution of the current alarm so that the information is available for future users. The active knowledge management module also solicits feedback from the user as to which, if any, of the historical resolutions were helpful in resolving the current alarm.
The embodiments set forth herein are intended to be exemplary. From the description of the exemplary embodiments, equivalents of the elements shown herein and ways of constructing other embodiments of the invention will be apparent to practitioners of the art. For example, the exemplary methods for capturing the resolution of the current selected alarm and the user's knowledge associated with that resolution may be modified but remain within the scope of the invention. Similarly, while representative software modules are described as performing the methods of the invention, variations of these software modules can also be used to execute the invention. Moreover, while the exemplary embodiments herein are described as applied to capturing knowledge associated with managing engineering problems, the invention can also be applied to capturing the knowledge associated with other tasks in fields such as information technology services or financial services. Many other modifications, features and embodiments of the invention will become evident to those of skill in the art. It should be appreciated, therefore, that many aspects of the invention were described above by way of example only and are not intended as required or essential elements of the invention unless explicitly stated otherwise. Accordingly, it should be understood that the foregoing relates only to certain embodiments of the invention and that numerous changes can be made therein without departing from the spirit and scope of the invention.
Wright, Carol, Forrester, Dean, Jones, James Wesley, Keleher, William Ronald Albert
Patent | Priority | Assignee | Title |
11212161, | May 11 2020 | AT&T Intellectual Property I, L P | Management and resolution of alarms based on historical alarms |
9933919, | Mar 10 2011 | Landmark Graphics Corporation | Systems and methods for monitoring operations data for multiple wells in real-time |
Patent | Priority | Assignee | Title |
7856498, | Jun 26 2008 | SYBASE, Inc. | Collaborative alert management and monitoring |
7894721, | Jun 27 2001 | CIENA LUXEMBOURG S A R L ; Ciena Corporation | Control of parameters in a global optical controller |
8155908, | Feb 14 2006 | Bentley Systems, Incorporated | Systems and methods for real-time system monitoring and predictive analysis |
20070222576, | |||
20080313121, | |||
20090254572, | |||
20090287628, | |||
20110254680, | |||
20120166373, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Sep 07 2010 | KELEHER, WILLIAM RONALD ALBERT | Science Applications International Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 025037 | /0434 | |
Sep 09 2010 | JONES, JAMES WESLEY | Science Applications International Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 025037 | /0434 | |
Sep 13 2010 | FORRESTER, DEAN | Science Applications International Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 025037 | /0434 | |
Sep 16 2010 | WRIGHT, CAROL | Science Applications International Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 025037 | /0434 | |
Sep 24 2010 | WIPRO LIMITED | (assignment on the face of the patent) | / | |||
Jun 10 2011 | Science Applications International Corporation | WIPRO LIMITED | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 026952 | /0744 |
Date | Maintenance Fee Events |
Aug 09 2018 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Aug 10 2022 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Date | Maintenance Schedule |
Feb 24 2018 | 4 years fee payment window open |
Aug 24 2018 | 6 months grace period start (w surcharge) |
Feb 24 2019 | patent expiry (for year 4) |
Feb 24 2021 | 2 years to revive unintentionally abandoned end. (for year 4) |
Feb 24 2022 | 8 years fee payment window open |
Aug 24 2022 | 6 months grace period start (w surcharge) |
Feb 24 2023 | patent expiry (for year 8) |
Feb 24 2025 | 2 years to revive unintentionally abandoned end. (for year 8) |
Feb 24 2026 | 12 years fee payment window open |
Aug 24 2026 | 6 months grace period start (w surcharge) |
Feb 24 2027 | patent expiry (for year 12) |
Feb 24 2029 | 2 years to revive unintentionally abandoned end. (for year 12) |