Method and system for processing work requests

• US 8,380,551 B2
• Filed: 11/05/2008
• Issued: 02/19/2013
• Est. Priority Date: 11/05/2008
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Coffman, Mathew A., Purcell, Timothi A., Estes, Steven R., Gerardi, John M.
• Primary Examiner(s): LOFTIS, JOHNNA RONEE
• Application Number:
  US12/265,010
• Publication Number:
  US 20100114641A1
• Time in Patent Office: 1,567 Days
• Field of Search: 705/7.12, 705/7.26
• US Class Current: 705/7.12
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06312 Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work

Abstract

The disclosure is directed to a method and system for processing work requests, preferably prototype operations work requests (POWR). In one of the embodiments the method is an automated method to be performed in a computing environment for processing a work request. The method comprises the steps of receiving the work request, inputting the work request into an electronic database, creating electronic work request instructions, linking the electronic work request instructions to multiple networked computers, transmitting between the networked computers electronic notifications relating to the work request instructions, and providing service reports filtered on specific data of interest relating to history and completion of the work request.

Claims

1. An automated method to be performed in a computing environment for processing a work request, the method comprising the steps of:

receiving the work request;

inputting the work request into an electronic database;

tailoring the work request, by a user, based on complexity of a product or a service;

creating automated electronic work request instructions that incorporate an approval/disapproval feature based on estimated hours for the work request and a charge estimate threshold for the work request, the charge estimate threshold set by one with approval authority prior to creation of the work request;

approving or disapproving the work request based on previously set approval authority within the approval/disapproval feature prior to incurring any costs, wherein if an approval type is “

approve”

, a default authority allows an approver to identify and approve unless a charge is below the charge estimate threshold, wherein if the approval type is “

notify”

, the approver is notified no matter what the charge, and wherein if the approval type is “

N/A”

(not applicable), no approver is notified and a general approval account can approve the charge;

linking the electronic work request instructions to multiple networked computers; and

,

transmitting between the networked computers electronic notifications relating to the work request instructions.

2. The method of claim 1 wherein the work request is a prototype operations work request (POWR) selected from the group comprising a service request, a hardware request, a manufacturing request, build instructions, general labor activities, archived records of requests, or a combination thereof.

3. The method of claim 1 wherein the electronic database comprises a shared server having a front-end database, a back-end database, and an attachment storage device.

4. The method of claim 1 wherein the step of creating electronic work request instructions further comprises creating a sequenced series of tasks to be worked sequentially for accomplishing the work request.

5. The method of claim 1 wherein the work request comprises data selected from the group comprising title of the request, description of the work requested, project, program, work provider type, work provider location, work provider point of contact, requesting point of contact, associated reference number, background information for work requested, supporting information for work requested, overhead approver, hours for work request, charge number, estimated hours to complete work requested, task materials needed for the work requested, location of materials, material certification, work tasks, task number, requester department, quantity of requested materials, estimated completion date, task description, assign material, identification of requester, date of work request, identification of approver, date of approval of work request, date work started on work request, date work request closed, identification of closer of work request, delivery contact, reference numbers to interface with other systems, work instructions including sign-off authorization, and nomenclature of requested hardware or service and references.

6. The method of claim 1 further comprising the step of inputting and storing into the electronic database one or more attachments to the work request, wherein the attachments are created by computer software.

7. The method of claim 1 wherein the multiple networked computers are personal computers.

8. The method of claim 1 further comprising providing automated service reports filtered on specific data of interest relating to history and completion of the work request, wherein the service reports are in a format selected from the group comprising electronic format and print format.

9. The method of claim 1 wherein the work request is documented in a format selected from the group comprising a high level abbreviated format and a detailed format tailored to the complexities of work requested.

10. The method of claim 1 wherein the method is web-based on a global computer network.

11. The method of claim 1 wherein the electronic notifications relating to the work request instructions are selected from the group comprising approval authority, authority to proceed, approval of the work request, revisions to the work request, updates to the work request, instructions for building, cancellation of the work request, completion of the work request, changes in quantity of items requested, and revised estimated hours to complete the request.

12. The method of claim 1 wherein the work request at any given time comprises a status selected from the group comprising opened status, in-review status, approved status, in-work status, worked status, completed status, and cancelled status.

13. The method of claim 1 for processing work requests for building parts for spacecraft, aircraft, automobiles, watercraft, and military vehicles.

14. An automated method to be performed in a computing environment for processing a prototype operations work request (POWR), the method comprising the steps of:

receiving the POWR selected from the group comprising a service request, a hardware request, a manufacturing request, build instructions, general labor activities, archived records of requests, or a combination thereof;

inputting the POWR into an electronic database comprising a shared server having a front-end database, a back-end database, and an attachment storage device;

tailoring the POWR, by a user, based on complexity of a product or a service;

creating automated electronic POWR instructions that incorporate an approval/disapproval feature based on estimated hours for the POWR and a charge estimate threshold for the POWR, the charge estimate threshold set by one with approval authority prior to creation of the POWR;

approving or disapproving the POWR based on previously set approval authority within the approval/disapproval feature prior to incurring any costs, wherein if an approval type is “

approve”

, a default authority allows an approver to identify and approve unless a charge is below the charge estimate threshold, wherein if the approval type is “

notify”

, the approver is notified no matter what the charge, and wherein if the approval type is “

N/A”

(not applicable), no approver is notified and a general approval account can approve the charge;

creating a sequenced series of tasks to be worked sequentially for accomplishing the POWR;

inputting and storing into the electronic database one or more attachments to the POWR, wherein the attachments are created by computer software;

linking the electronic POWR instructions and tasks to multiple networked computers comprising personal computers;

transmitting between the networked computers electronic notifications relating to the POWR instructions and tasks; and

,

providing automated service reports filtered on specific data of interest relating to history and completion of the POWR.

15. The method of claim 14 wherein the method is web-based on a global computer network.

16. An automated method to be performed in a computing environment for processing a prototype operations work request (POWR), the method comprising the steps of:

receiving a POWR;

inputting POWR data and instructions into an electronic database;

tailoring the POWR, by a user, based on complexity of a product or a service, the POWR data and instructions being automated and incorporating an approval/disapproval feature based on estimated hours for the POWR and a charge estimate threshold for the POWR, the charge estimate threshold set by one with approval authority prior to creation of the POWR;

approving or disapproving the POWR based on previously set approval authority within the approval/disapproval feature prior to incurring any costs, wherein if an approval type is “

approve”

, a default authority allows an approver to identify and approve unless a charge is below the charge estimate threshold, wherein if the approval type is “

notify”

, the approver is notified no matter what the charge, and wherein if the approval type is “

N/A”

(not applicable), no approver is notified and a general approval account can approve the charge;

inputting a sequenced series of POWR tasks to be worked sequentially for accomplishing the POWR and storing the POWR in the database;

linking the POWR to multiple networked computers; and

,

transmitting between the multiple networked computers electronic notifications relating to revising, approving, building, and completing the POWR.

17. The method of claim 16 wherein the POWR is selected from the group comprising a service request, a hardware request, a manufacturing request, build instructions, general labor activities, archived records of requests, or a combination thereof.

18. The method of claim 16 wherein the electronic database comprises a shared server having a front-end database, a back-end database, and an attachment storage device.

19. The method of claim 16 wherein the POWR comprises data selected from the group comprising title of the request, description of the work requested, project, program, work provider type, work provider location, work provider point of contact, requesting point of contact, associated reference number, background information for work requested, supporting information for work requested, overhead approver, hours for work request, charge number, estimated hours to complete work requested, task materials needed for the work requested, location of materials, material certification, work tasks, task number, requester department, quantity of requested materials, estimated completion date, task description, assign material, identification of requester, date of work request, identification of approver, date of approval of work request, date work started on work request, date work request closed, identification of closer of work request, delivery contact, reference numbers to interface with other systems, work instructions including sign-off authorization, and nomenclature of requested hardware or service and references.

20. The method of claim 16 further comprising the step of inputting and storing into the electronic database one or more attachments to the POWR, wherein the attachments are created by computer software.

21. The method of claim 16 wherein the multiple networked computers are personal computers.

22. The method of claim 16 further comprising generating automated electronic service reports filtered on specific data of interest relating to history and completion of the POWR, wherein the service reports are in a format selected from the group comprising electronic format and print format.

23. The method of claim 16 wherein the POWR is documented in a format selected from the group comprising a high level abbreviated format and a detailed format tailored to the complexities of work requested.

24. The method of claim 16 wherein the method is web-based on a global computer network.

25. The method of claim 16 wherein the POWR at any given time comprises a status selected from the group comprising opened status, in-review status, approved status, in-work status, worked status, completed status, and cancelled status.

26. The method of claim 16 for processing work requests for building parts for spacecraft, aircraft, automobiles, watercraft, and military vehicles.

27. The method of claim 16 wherein the electronic notifications comprise electronic approval notifications for revising and updating the POWR and the POWR is in an in-review status.

28. The method of claim 16 wherein the electronic notifications comprise electronic approval notifications for approving the POWR and the POWR is in an approved status.

29. The method of claim 16 wherein the electronic notifications comprise electronic notifications for instructions for building or aborting the POWR and the POWR is in an in-work status.

30. The method of claim 16 wherein the electronic notifications comprise electronic notifications for building the POWR and the POWR is in a worked status.

31. The method of claim 16 wherein the electronic notifications comprise electronic notifications for providing real-time completion status of the POWR and the POWR is in a completed status.

32. An automated method for processing a prototype operations work request (POWR), the method to be performed in a computing environment comprising one or more computer communications and networking devices linking a shared server with multiple user terminals, the method comprising the steps of:

receiving a POWR selected from the group comprising a service request, a hardware request, a manufacturing request, build instructions, general labor activities, archived records of requests, or a combination thereof;

inputting POWR data and instructions into an electronic database comprising the shared server having a front-end database, a back-end database, and an attachment storage device;

tailoring the POWR, by a user, based on complexity of a product or a service, the POWR data and instructions being automated and the POWR incorporating an approval/disapproval feature based on estimated hours for the work request and a charge estimate threshold for the POWR, the charge estimate threshold set by one with approval authority prior to creation of the POWR;

approving or disapproving the POWR based on previously set approval authority within the approval/disapproval feature prior to incurring any costs, wherein if an approval type is “

approve”

, a default authority allows an approver to identify and approve unless a charge is below the charge estimate threshold, wherein if the approval type is “

notify”

, the approver is notified no matter what the charge, and wherein if the approval type is “

N/A”

(not applicable), no approver is notified and a general approval account can approve the charge;

inputting a sequenced series of POWR tasks to be worked sequentially for accomplishing the POWR and storing the POWR in the database, wherein the POWR is in an opened status;

inputting and storing into the electronic database one or more attachments to the POWR, wherein the attachments are created by computer software;

linking the opened POWR to multiple networked computers comprising personal computers;

transmitting between the multiple networked computers electronic notifications relating to the POWR, wherein the electronic notifications comprise,

(a) electronic approval notifications for revising and updating the POWR, wherein the POWR is in an in-review status;

(b) electronic approval notifications for approving the POWR, wherein the POWR is in an approved status;

(c) electronic notifications for instructions for building or aborting the POWR, wherein the POWR is in an in-work status;

(d) electronic notifications for building the POWR, wherein the POWR is in a worked status; and

,

(e) electronic notifications for providing real-time completion status of the POWR, wherein the POWR is in a completed status;

generating automated electronic service reports at any POWR status filtered on specific data of interest relating to history and completion of the POWR, wherein the service reports are in a format selected from the group comprising electronic format and print format.

33. The method of claim 32 for processing the POWR for building parts for spacecraft, aircraft, automobiles, watercraft, and military vehicles.

34. The method of claim 32 wherein the method is web-based on a global computer network.

35. An automated system for use in a computing environment for processing a work request, the system comprising:

a shared server comprising a front-end database, a back-end database, and an attachment storage device, wherein the shared server saves and retains a work request that is input into the server, wherein the work request is tailored by a user based on complexity of a product or a service, and the work request incorporates an automated approval/disapproval feature based on estimated hours for the work request and a charge estimate threshold for the work request, the charge estimate threshold set by one with approval authority prior to creation of the work request, the approval/disapproval feature deciding to either approve or disapprove the work request based on previously set approval authority prior to incurring any costs, wherein if an approval type is “

approve”

, a default authority allows an approver to identify and approve unless a charge is below the charge estimate threshold, wherein if the approval type is “

notify”

, the approver is notified no matter what the charge, and wherein if the approval type is “

N/A”

(not applicable), no approver is notified and a general approval account can approve the charge,

one or more computer communications and networking devices for linking the shared server with multiple user terminals, wherein the multiple user terminals comprise personal computers having network access for accessing the work request and sending and receiving automated information relating to the processing and completion of the work request; and

,

supporting electronics devices to assist the multiple user terminals in accessing the work request and sending and receiving the automated information relating to the processing and completion of the work request.

36. The system of claim 35 wherein the work request is a prototype operations work request (POWR) selected from the group comprising a service request, a hardware request, a manufacturing request, build instructions, general labor activities, archived records of requests, or a combination thereof.

37. The system of claim 35 wherein the attachment storage device saves and stores one or more attachments to the work request, and wherein the attachments are created by computer software.

38. The system of claim 35 wherein the computer communications and networking device comprises a network server.

39. The system of claim 35 wherein the multiple user terminals comprise a start work request database link, a copy or update from front-end database feature, and a run front-end on local terminal feature.

40. The system of claim 35 wherein the supporting electronics devices comprise input devices and output devices.

41. The system of claim 40 wherein the input devices comprise scanners, bar code readers, and cameras.

42. The system of claim 40 wherein the output devices comprise printers and displays.

43. The system of claim 35 wherein the system is web-based on a global computer network.

44. An automated system for use in a computing environment for processing a prototype operations work request (POWR), the POWR selected from the group comprising a service request, a hardware request, a manufacturing request, build instructions, general labor activities, archived records of requests, or a combination thereof, the system comprising:

a shared server comprising a front-end database, a back-end database, and an attachment storage device, wherein the shared server saves and retains the POWR that is input into the server, the POWR being tailored by the user based on complexity of a product or a service, and further wherein the attachment storage device saves and stores one or more attachments created by computer software to the POWR, wherein the POWR incorporates an automated approval/disapproval feature based on estimated hours for the work request and a charge estimate threshold for the work request, the charge estimate threshold set by one with approval authority prior to creation of the POWR, the approval/disapproval feature deciding to either approve or disapprove the work request based on previously set approval authority prior to incurring any costs, wherein if an approval type is “

approve”

, a default authority allows an approver to identify and approve unless a charge is below the charge estimate threshold, wherein if the approval type is “

notify”

, the approver is notified no matter what the charge, and wherein if the approval type is “

N/A”

(not applicable), no approver is notified and a general approval account can approve the charge;

one or more computer communications and networking devices for linking the shared server with multiple user terminals, wherein the multiple user terminals comprise personal computers having network access for accessing the POWR and sending and receiving automated information relating to the processing and completion of the POWR, and further wherein the multiple user terminals comprise a start POWR database link, a copy or update from front-end database feature, and a run front-end on local terminal feature; and

,

supporting electronics devices to assist the multiple user terminals in accessing the POWR and sending and receiving the automated information relating to the processing and completion of the POWR, wherein the supporting electronics devices comprise input devices selected from the group comprising scanners, bar code readers, and cameras, and further comprise output devices selected from the group comprising printers and displays.

45. The system of claim 44 wherein the system is web-based on a global computer network.