Methods and systems for generating a financial report
First Claim
1. A network based system for maintaining at least one component, said system comprising:
- a client system;
a centralized database for storing information;
a server system configured to be coupled to said client system and said database, said server system further configured to;
receive, at the database, component operational history data and component inspection data from a user for a pre-identified component;
receive, at the database, a customer expectation of contingency fees and service prices from a user;
receive, at the database, costs comprising at least one of component replacement part costs, component part repair costs, and vendor service costs, the costs are associated with the pre-identified component and are determined using pre-stored costs related to the pre-identified component;
prompt a user to input a pre-determined component operational forecast into the database;
receive, from the user, a number of inspection intervals for component parts, and based on the number of inspection intervals for each component part, adjust a quantity of input entries for repair work for each component part;
determine whether the user input all information necessary to generate a financial report;
present an error message to the user and halt execution if it is determined that not all information necessary to generate a financial report was input;
analyze component maintenance information including component inspection data and at least one of component operational history data, customer expectation of contingency fees and service prices, replacement part costs, part repair costs, vendor service costs, and component operational forecast; and
automatically generate a financial report including at least one schedule of component maintenance events and costs associated with each event based on the component maintenance information analysis.
1 Assignment
0 Petitions
Accused Products
Abstract
A method for generating a financial report indicative of estimated turbine maintenance costs is provided. The method includes receiving, at a database, turbine operational history data and turbine inspection data from a user for a pre-identified turbine, receiving, at the database, turbine replacement part costs, turbine part repair costs, and vendor service costs associated with the pre-identified turbine, inputting a pre-determined turbine operational forecast into the database, analyzing turbine maintenance information including at least one of turbine operational history data, turbine inspection data, replacement part costs, part repair costs, vendor service costs, and turbine operational forecast, and automatically generating a financial report including at least one schedule of turbine maintenance events and costs associated with each event based on the turbine maintenance information analysis.
17 Citations
18 Claims
-
1. A network based system for maintaining at least one component, said system comprising:
-
a client system; a centralized database for storing information; a server system configured to be coupled to said client system and said database, said server system further configured to; receive, at the database, component operational history data and component inspection data from a user for a pre-identified component; receive, at the database, a customer expectation of contingency fees and service prices from a user; receive, at the database, costs comprising at least one of component replacement part costs, component part repair costs, and vendor service costs, the costs are associated with the pre-identified component and are determined using pre-stored costs related to the pre-identified component; prompt a user to input a pre-determined component operational forecast into the database; receive, from the user, a number of inspection intervals for component parts, and based on the number of inspection intervals for each component part, adjust a quantity of input entries for repair work for each component part; determine whether the user input all information necessary to generate a financial report; present an error message to the user and halt execution if it is determined that not all information necessary to generate a financial report was input; analyze component maintenance information including component inspection data and at least one of component operational history data, customer expectation of contingency fees and service prices, replacement part costs, part repair costs, vendor service costs, and component operational forecast; and automatically generate a financial report including at least one schedule of component maintenance events and costs associated with each event based on the component maintenance information analysis. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A computer program embodied on a non-transitory computer readable medium for maintaining at least one component, said program comprising a code segment that receives, at a database, component operational history data and component inspection data from a user for a pre-identified component and then:
-
receives, at the database, a customer expectation of contingency fees and service prices from a user; receives, at the database, costs comprising at least one of component replacement part costs, component part repair costs, and vendor service costs, the costs are associated with the pre-identified component and are determined using pre-stored costs related to the pre-identified component; prompts a user to input a pre-determined component operational forecast into the database; receives, from the user, a number of inspection intervals for component parts, and based on the number of inspection intervals for each component part, adjust a quantity of input entries for repair work for each component part; determines whether the user has input all necessary information in order to generate a financial report; presents an error message to the user and halts execution if it is determined that not all necessary information to generate a financial report was input; analyzes component maintenance information including component inspection data and at least one of component operational history data, customer expectation of contingency fees and service prices, replacement part costs, part repair costs, vendor service costs, and component operational forecast; and automatically generates a financial report including at least one schedule of component maintenance events and costs associated with each event based on the component maintenance information analysis. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18)
-
Specification