Methods and systems for advanced spaceport information management

• US 20060038084A1
• Filed: 03/17/2005
• Published: 02/23/2006
• Est. Priority Date: 07/30/2004
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Fussell, Ronald M., Meier, Gary M., Meade, Phillip T., Halpin, Paul C., Blackwell-Thompson, Charlie, Ely, Donald W., Jacobson, Craig A.
• Granted Patent: US 7,302,364 B2
• Time in Patent Office: Days
• US Class Current: 244/173.100
• CPC Class Codes: B64G 1/52 Protection, safety or emergency devices; Survival aids
• CPC Class Codes: B64G 5/00 Ground equipment for vehicles, e.g. starting towers, fuelling arrangements B64G3/00 takes precedence
• CPC Class Codes: G01R 31/008 on air- or spacecraft, railway rolling stock or sea-going vessels

Abstract

Advanced spaceport information management methods and systems are disclosed. In one embodiment, a method includes coupling a test system to the payload and transmitting one or more test signals that emulate an anticipated condition from the test system to the payload. One or more responsive signals are received from the payload into the test system and are analyzed to determine whether one or more of the responsive signals comprises an anomalous signal. At least one of the steps of transmitting, receiving, analyzing and determining includes transmitting at least one of the test signals and the responsive signals via a communications link from a payload processing facility to a remotely located facility. In one particular embodiment, the communications link is an Internet link from a payload processing facility to a remotely located facility (e.g. a launch facility, university, etc.).

Claims

1. A system for testing a payload, comprising:

a front end adapted to be operatively coupled to and communicate with the payload;

a back end operatively coupled to the front end; and

a data repository operatively coupled to at least one of the back end and the front end,

wherein at least one of the operative couplings between the front end and the payload, and the back end and the front end, and the data repository and the at least one of the back end and the front end is adapted to include a communications link from a payload processing facility to a remotely located facility.

2. The system of claim 1, wherein the communications link comprises an Internet link.

3. The system of claim 1, further comprising a user interface adapted to be operatively coupled to the back end via a second communications link, the user interface being adapted to enable a user to provide inputs to and receive outputs from the back end.

4. The system of claim 3, wherein the second communications link comprises an Internet link.

5. The system of claim 1, further comprising a system management feature integrated into at least one of the front end, the back end, and the data repository.

6. The system of claim 1, wherein at least one of the front end, the back end, and the data repository are further adapted to provide notifications for the completion of predetermined test activities.

7. The system of claim 1, wherein at least one of the front end, the back end, and the data repository are further adapted to store data generated during testing during a period when the communication link is interrupted, and to transmit the stored data via the communication link when the communication link is re-connected.

8. The system of claim 1, wherein at least one of the front end, the back end, and the payload data repository are further adapted to execute a software routine that includes a software wizard for at least one of planning a test configuration, identifying test configuration requirements, posting test event milestones, generating a schedule, and generating a report.

9. The system of claim 1, wherein at least one of the front end, the back end, and the data repository are further adapted to perform a monitoring function through a display device.

10. A method of testing a payload, comprising:

coupling a test system to the payload;

transmitting one or more test signals that at least one of emulate and enable an anticipated condition from the test system to the payload;

receiving one or more responsive signals from the payload into the test system;

analyzing one or more responsive signals; and

determining whether one or more of the responsive signals comprises an anomalous signal,

wherein at least one of the transmitting one or more test signals, receiving one or more responsive signals, analyzing one or more responsive signals, and determining whether one or more of the responsive signals comprises an anomalous signal includes transmitting at least one of the test signals and the responsive signals via a communications link from a payload processing facility to a remotely located facility.

11. The method of claim 10, wherein the transmitting at least one of the test signals and the responsive signals via a communications link from a payload processing facility to a remotely located facility includes transmitting at least one of the test signals and the responsive signals via an Internet link from a payload processing facility to a remotely located facility.

12. The method of claim 10, wherein the transmitting at least one of the test signals and the responsive signals via a communications link from a payload processing facility to a remotely located facility includes transmitting at least one of the test signals and the responsive signals via a communications link from a payload processing facility to a launch facility.

13. The method of claim 10, wherein the transmitting at least one of the test signals and the responsive signals via a communications link from a payload processing facility to a remotely located facility includes transmitting at least one of the test signals and the responsive signals via a communications link from at least one of a first city to a second city, a first state to a second state, and a first country to a second country.

14. The method of claim 10, wherein coupling a test system to the payload includes coupling a test system to the payload wherein the test system and the payload are located at different remote facilities.

15. The method of claim 10, wherein transmitting one or more test signals includes transmitting at least one of a command signal and a test data signal.

16. The method of claim 10, further comprising identifying the occurrence of an anomalous condition to a system operator via a display.

17. The method of claim 10, further comprising querying a system operator whether to generate a nonconformance report.

18. The method of claim 10, further comprising transmitting a nonconformance report to a remotely located data storage facility.

19. The method of claim 10, further comprising querying a system operator whether to retest a nonconforming condition.

20. The method of claim 10, further comprising troubleshooting a nonconforming condition via the communication link between the payload processing facility to the remotely located facility.

21. A computer-readable medium having stored thereon instructions for testing a payload, the computer-readable medium comprising:

a first computer program portion adapted to transmit one or more test signals that emulate an anticipated condition from a test system to the payload;

a second computer program portion adapted to receive one or more responsive signals from the payload into the test system;

a third computer program portion adapted to analyze one or more responsive signals; and

a fourth computer program portion adapted to determine whether one or more of the responsive signals comprises an anomalous signal,

wherein at least one of the first, second, third, and fourth computer program portions is further adapted to communicate via a communications link from a payload processing facility to a remotely located facility.

22. The computer-readable medium of claim 21, wherein at least one of the first, second, third, and fourth computer program portions is further adapted to communicate via an Internet link from a payload processing facility to a remotely located facility.

23. The computer-readable medium of claim 21, wherein at least one of the first, second, third, and fourth computer program portions is further adapted to communicate via a communications link from a payload processing facility to a launch facility.

24. The computer-readable medium of claim 21, wherein at least one of the first, second, third, and fourth computer program portions is further adapted to communicate via a communications link from at least one of a first city to a second city, a first state to a second state, and a first country to a second country.

25. The computer-readable medium of claim 21, further comprising a fifth computer program portion adapted to at least one of identify an occurrence of an anomalous condition to a system operator via a display, query a system operator whether to generate a nonconformance report, transmit a nonconformance report to a remotely located data storage facility, query a system operator whether to retest a nonconforming condition, and troubleshoot a nonconforming condition via the communication link between the payload processing facility to the remotely located facility.

26. An avionics software tasking model for testing a payload, comprising:

a hardware driver layer; and

a payload test system operatively coupled to the hardware driver layer, the payload test system including;

a front end adapted to be operatively coupled to and communicate with the payload;

a back end operatively coupled to the front end; and

a payload data repository operatively coupled to at least one of the back end and the front end,

wherein at least one of the operative couplings between the front end and the payload, and the back end and the front end, and the payload data repository and the at least one of the back end and the front end is adapted to include a communications link from a payload processing facility to a remotely located facility.

27. The avionics software tasking model of claim 26, wherein the communications link comprises an Internet link.

28. The avionics software tasking model of claim 26, further comprising a user interface adapted to be operatively coupled to the back end via a second communications link, the user interface being adapted to enable a user to provide inputs to and receive outputs from the back end.

29. The avionics software tasking model of claim 26, wherein at least one of the front end, the back end, and the payload data repository are further adapted to provide notifications for the completion of predetermined test activities.

30. The avionics software tasking model of claim 26, wherein at least one of the front end, the back end, and the payload data repository are further adapted to store data generated during testing during a period when the communication link is interrupted, and to transmit the stored data via the communication link when the communication link is re-connected.

31. The avionics software tasking model of claim 26, wherein at least one of the front end, the back end, and the data repository are further adapted to execute a software routine that includes a software wizard for at least one of planning a test configuration, identifying test configuration requirements, posting test event milestones, generating a schedule, and generating a report.

32. A payload life cycle, comprising:

a preflight operations portion that includes a payload test procedure, the payload test procedure including;

transmitting one or more test signals that emulate an anticipated condition from a test system to the payload;

receiving one or more responsive signals from the payload into the test system;

analyzing one or more responsive signals; and

determining whether one or more of the responsive signals comprises an anomalous signal,

wherein at least one of the transmitting, receiving, analyzing, and determining comprises communicating via a communications link from a payload processing facility to a remotely located facility;

a flight system integration portion that includes integration of the payload within a launch vehicle; and

a desired mission portion.

33. The payload life cycle of claim 32, wherein the payload test procedure is further adapted to communicate via an Internet link from a payload processing facility to a remotely located facility.

34. The payload life cycle of claim 32, wherein the payload test procedure is further adapted to communicate via a communications link from a payload processing facility to a launch facility.

35. The payload life cycle of claim 32, wherein the payload test procedure is further adapted to communicate via a communications link from at least one of a first city to a second city, a first state to a second state, and a first country to a second country.

36. The payload life cycle of claim 32, wherein the payload test procedure is further adapted to at least one of identify an occurrence of an anomalous condition to a system operator via a display, query a system operator whether to generate a nonconformance report, transmit a nonconformance report to a remotely located data storage facility, query a system operator whether to retest a nonconforming condition, and troubleshoot a nonconforming condition via the communication link between the payload processing facility to the remotely located facility.

37. The payload life cycle of claim 32, wherein the preflight operations portion further includes a preparation procedure associated with a launch vehicle.

38. The payload life cycle of claim 32, further comprising a servicing and departure portion.

39. The payload life cycle of claim 32, further comprising at least one of a landing and recovery portion, a turnaround preparations portion, and a providing deliverables to a payload customer portion.

40. The payload life cycle of claim 32, wherein the preflight operations portion includes a spaceport application having a plurality of preflight subportions, each preflight subportion supporting at least one of a plurality of spacecraft configurations and a plurality of payload configurations.

41. The payload life cycle of claim 32, wherein the payload test procedure includes testing of at least one payload element autonomously by a payload developer at the remotely located facility via the communications link.

42. The payload life cycle of claim 32, wherein the payload test procedure includes transitioning of an individual payload test procedure to a payload developer at the remotely located facility via an autonomous communications link controlled by the payload developer.

43. The payload life cycle of claim 32, wherein the desired mission portion includes autonomously providing at least one mission operation from the payload integrated with the launch vehicle by the payload developer via at least one of a mission communications link, a software portion, and an artificially derived knowledge.

44. A data management architecture adapted for testing a payload, comprising:

a common infrastructure adapted to perform at least one core function;

one or more modules operatively interfaced with the common infrastructure, the one or more modules including at least one of;

an input module adapted to receive input data;

a test script generation module adapted to generate a test script for testing the payload; and

an integration simulator module adapted to provide simulation data to the payload; and

a communications link operatively coupled to at least one of the common infrastructure and the one or more modules, the communications link being adapted to enable a payload developer at a remotely located facility to autonomously perform a payload test procedure of the payload.

45. The data management architecture of claim 44, wherein the payload test procedure includes:

transmitting one or more test signals that emulate an anticipated condition from a test system to the payload;

receiving one or more responsive signals from the payload into the test system;

analyzing one or more responsive signals; and

determining whether one or more of the responsive signals comprises an anomalous signal,

wherein at least one of the transmitting, receiving, analyzing, and determining comprises communicating via the communications link from a payload processing facility to the remotely located facility.

46. The data management architecture of claim 45, wherein the payload test procedure is further adapted to communicate via an Internet link from a payload processing facility to the remotely located facility.

47. The data management architecture of claim 45, wherein the payload test procedure is further adapted to communicate via the communications link from a payload processing facility to a launch facility.

48. The data management architecture of claim 45, wherein the payload test procedure is further adapted to communicate via the communications link from at least one of a first city to a second city, a first state to a second state, and a first country to a second country.

49. The data management architecture of claim 45, wherein the payload test procedure is further adapted to at least one of identify an occurrence of an anomalous condition to a system operator via a display, query a system operator whether to generate a nonconformance report, transmit a nonconformance report to a remotely located data storage facility, query a system operator whether to retest a nonconforming condition, and troubleshoot a nonconforming condition via the communication link between the payload processing facility to the remotely located facility.

50. The data management architecture of claim 44, wherein the one or more modules includes an input module operatively coupled to a set of planning modules having at least one of a scheduling module, a requirement module, a procedure development module, a financial properties module, and a logistics planning module.

51. The data management architecture of claim 44, wherein the test script generation module is adapted to receive requirements satisfaction information and to generate test scripts accordingly.

52. The data management architecture of claim 44, wherein the one or more modules includes a configuration control module adapted to perform at least one of automated acceptance data package management, automated weight balance calculations, and generation of flight certification information.

53. The data management architecture of claim 44, wherein the one or more modules includes an artificial intelligence module adapted to utilize at least one of inspection information, decision-support information, and environmental support information and to perform at least one of artificial vision functions and decision-support functions.