Preliminary Design Review [Tuesday 2pm]

UNIVERSITY OF SOUTH AUSTRALIA

SCHOOL OF ELECTRICAL AND INFORMATION ENGINEERING

ELECTRICAL AND INFORMATION ENGINEERING PROJECT 2005

Joyride to “Space”

System Specification Report

TEAMS

System Aspects: Teo, Check Kai Edwin - TEOCK001; Ramakrishnan, Sujatha - RAMSY009; Chang, Shi Hao - CHASH007; Diep, William - DIEWY001; Ling, Sien Tong - linst001;

Technical: Saddlier, Timothy Stuart - SADTS001; Lim, Ted Cheng - LIMTC002; Tiong, Sie King - TIOSK001; Wong, Sze Meu - wonsm012; Mares, Lachlan Lenard - MARLL002;

Non-technical: Belperio, Michael - BELMY006; Bailes, Serge - BAISY008; Cheang, Sim Meng - CHESM012; Wallis, Adam - WALAY010;

Safety: Nguyen, Thuan Quoc - NGUTK001; Gopal Pathi, Premkumar - GOPPY001; Tiwari, Ullash - tiwuy001;England, Samuel Gordon - ENGSG002

Supervisor: Paul Bunnik

Tutorial Time: Tuesday, 14:00 hrs

SYSTEM SPECIFICATION REPORT:The System Specification Report is the proposal that our team, has consolidated to SeaLink, for the complete system that would offer joy flights to ‘Space’.

Contents:This report consists of the following sections:

PART 1: Project Plan ReportPART 2: Needs and System Requirement Specification ReportPART 3: Feasibility Study ReportPART 4: Functional Analysis and Design ReportPART 5: System Test Plan ReportPART 6: Subsystem Requirement Specification ReportPART 7: Subsystem Test Plan ReportPART 8: Subsystem Analysis ReportPART 9: Portfolio of Teams ReportPART 10: Conclusion

3

University ofSouth Australia

School of Electrical and Information Engineering

EEET 2025 (013398) System Engineering 2

Study Period 6, 2005

Joyride to Space

Project PlanVersion 3.0

Project Plan Contents

1. Statement of Work.................................................................................................42. Statement of Needs................................................................................................53. Work Breakdown Structure...................................................................................64. Gantt Chart.............................................................................................................95. Program Management..........................................................................................106. Risk Management................................................................................................107. Resource Required...............................................................................................148. Deliverables.........................................................................................................159. Organisational Structure......................................................................................15

1. Statement of Work

SeaLink is a South Australian company and have been providing primary sea transportation for over 13 years. In an effort to provide new adventure for customers, SeaLink has expressed interest in diversifying its services by providing joy flights to space. Our project group consist of 22 people, who have been chosen to respond to the request. An investigation will be conducted on space travel methods and aerospace technologies, but the main investigation of this project will entail investigating commercial space travel for the application of allowing people who would like to experience space travel. The project will conclude by delivering a report and a recommendation on the method where customers can enjoy the experience of space in a safe and comfortable environment.

4

2. Statement of NeedsOur customer, SeaLink, has expressed their interest in a system capable of providing joy flights to, “Space”. The needs statement provided by the Customer is as follows:

“Following the discovery that the sea bed near Victor Harbour is not interesting for undersea tours, SeaLink have decided to diversify into offering joy flights to, “Space”. They require a complete system to provide this service, based within four hours driving time of Adelaide.”

The following needs were derived from the initial statement provided by the customer in consultation with the customer’s agent.

Need Description

SLINK 1.0

SLINK 1.1

SLINK 1.2

SLINK 1.3

SLINK 1.4

SLINK 1.5

SLINK 1.6

SLINK 1.7

SLINK 1.8

SLINK 1.9

The system needs to be geographically located within 4 hours drive from the Adelaide Central Business District (CBD).

The system needs to be capable of flying customers into space.

The system needs to be capable of returning customers from space.

The system needs to provide a means of transporting customers back to the starting point after the flight.

The system needs to be capable of providing an environment for customers to enjoy their flight to and from space.

The system needs to be compliant with government regulations and policies.

The system needs to be maintainable throughout its intended life cycle.

The system needs to be reliable.

The system needs to be able to operate under normal weather conditions

The system needs to be commercial viable.

5

3. Work Breakdown Structure

This project comprises of 8 work packages which is scheduled to be completed within 12 weeks, starting from 30th August, 2005 and ending on the 1st November, 2005. Below, are a list of work packages and its details, start and finish dates, the team responsible for the package, description, the cost involved, and the test method/s for reviewing the quality of each work package.

WP1 - Project Plan: • Start: 23rd August, 2005.• Due: 2pm, 30th August, 2005. • Team: System Aspect• Description: Documentation outlining the project’s goals, the project’s

schedule, description, statement of work involved, the risks related, and a list of resources required for completing the project.

• Cost: Nil• Deliverables: Draft Project Plan• Test Method/s: Submitting the documentation to other teams within the project

group.

WP2 – Statement of Needs: • Start: 30th August, 2005.• Due: 2pm, 6th September, 2005. • Team: Non-Technical• Description: Documentation providing the bases for the project, where the

project exists to fulfil the identified needs.• Cost: Nil• Deliverables: Draft Project Plan• Test Method/s: Submitting the documentation to other teams within the project

group.

WP3 – Requirements Specification: • Start: 6th September, 2005.• Due: 2pm, 13th September, 2005. • Team: Non-Technical• Description: Documentation on the system's functional requirements from the

identified needs. • Cost: Nil • Deliverables: Draft Requirement Analysis• Test Method/s: Submitting the documentation to other teams within the project

group.

6

WP4 – Feasibility Study: • Start: 13th September, 2005.• Due: 2pm, 4th October, 2005. • Team: Technical• Description: Documentation on the analysis of all possible solutions to the

project and a recommendation on the best solution. • Cost: **********Please Fill In********** • Deliverables: Draft Feasibility Study • Test Method/s: Submitting the documentation to other teams within the project

group.

WP5 – Functional Analysis: • Start: 13th September, 2005.• Due: 2pm, 4th October, 2005. • Team: Technical• Description: Documentation on the break down of requirements at the

subsystem level and below to identify specific resources and components of the system.

• Cost: Nil • Deliverables: Draft Functional Analysis • Test Method/s: Submitting the documentation to other teams within the project

group.

WP6 – Subsystem Analysis: • Start: 27th September, 2005.• Due: 2pm, 4th October, 2005. • Team: Safety• Description: Documentation on the tests that can be conducted on each

subsystem level. • Cost: **********Please Fill In********** • Deliverables: Subsystem Analysis • Test Method/s: Submitting the documentation to other teams within the project

group.

WP7 – Test Plan: • Start: 4th October, 2005• Due: 2pm, 11th October, 2005. • Team: Safety• Description: Documentation reporting all the tests that have been conducted on

the system prototype, as specified in the subsystem analysis document. • Cost: **********Please Fill In********** • Deliverables: Test Plan • Test Method/s: Submitting the documentation to other teams within the project

group.

7

WP8 – Report of Portfolio: • Start: 11th October, 2005.• Due: 2pm, 18th October, 2005. • Team: System Aspect• Description: Documentation reviewing the system that meets the requirements

in the requirements analysis document, and functional components in the functional analysis document.

• Cost: **********Please Fill In********** • Deliverables: Draft Report of Portfolio • Test Method/s: Submitting the documentation to other teams within the project

group.

WP9 – Final Report: • Start: 11th October, 2005.• Due: 2pm, 18th October, 2005. • Team: System Aspect• Description: Documentation reviewing the system that meets the requirements

in the requirements analysis document, and functional components in the functional analysis document.

• Cost: **********Please Fill In********** • Deliverables: Draft Report of Portfolio • Test Method/s: Submitting the documentation to Paul Bunnik.

8

4. Gantt Chart

9

5. Program Management

Communications: This is a 10 week project, and communication will be very important. For the project to be successful, each member in their assigned groups must be able to communicate with each other and during the 10 weeks. The main means of communication within each group will be E-mail and the main means of communication between the four groups will be the discussion forum.

Meetings:The whole team attends a compulsory meeting which is held on Tuesday at 2pm and will be monitored by a supervisor. The Tuesday meeting allows the groups to discuss any type of issues as a team, and during this session work packages will be submitted to other groups. Extra meeting times will be organised through email, phone, or discussion forum if need be.

Data Management: All work packages in relation to the project will be stored in hardcopy and softcopy format. In softcopy format the work packages will be stored in a folder in the school network ‘EIE 215182\ D: SE2’ where anybody within the team can access it, and each group will keep a copy of their documentation. All changes will be documented and saved as a different copy to the version before.

6. Risk Management

Risk Identifier: RM-PP-01Risk Description: Data corruption with softcopy format.Impact Description:

Stops the project at the point of corruption if document can not be recovered.Probability: MediumImpact: HighPreventative measures:

Back up document on multiple storage medium. Copy documentation to disk as well as sending by email. Regularly scan documents and storage devices with update anti-virus software.

Risk Identifier: RM-PP-02Risk Description: Incompatibility between different versions of softwareImpact Description:

A document produced with a higher version of software may not be able to access the document with a lower version of software.

Probability: MediumImpact: LowPreventative measures:

Agree on a specific version of software. Agree on a specific type of file to save as.

Risk Identifier: RM-PP-03Risk Description: University’s computer crashes.Impact Description:

Unable able to do work at University.Probability: LowImpact: MediumPreventative measures:

Identify places where computer can be accessed.

10

Risk Identifier: RM-PP-04Risk Description: Personal computer hardware components damaged.Impact Description:

Unable able to do work for a period of time. Time wasted on recovering work. All work will be lost if work cannot be recovered. Deadline may not be met.

Probability: LowImpact: HighPreventative measures:

Work should be distributed to other team member as soon as possible.

Risk Identifier: RM-PP-05Risk Description: Withdrawal of a team member.Impact Description:

Loss of team morale. Increase workload for the rest of the team.

Probability: MediumImpact: LowPreventative measures:

Discuss within the team to reorganise workload and structure. Discuss the situation with other teams in the project group.

Risk Identifier: RM-PP-06Risk Description: Behind schedule.Impact Description:

Pushes deadline back for the work package/s.Probability: HighImpact: HighPreventative measures:

Ensure all members are on schedule with the help of a Gantt chart.

Risk Identifier: RM-PP-07Risk Description: Late for team or group meeting/s.Impact Description:

Delay with work in waiting for team member. Timed wasted in repeating what happened in the group or team meeting/s.

Probability: HighImpact: LowPreventative measures:

Inform other team member before meeting. Someone takes notes on what happened in the meeting/s and produce a softcopy and send it through

email to team or group member/s.

11

Risk Identifier: RM-PP-08Risk Description: Miss team or group meeting/s.Impact Description:

Delay with work in waiting for team member and work cannot be allocated to due missing team member/s.

Probability: HighImpact: MediumPreventative measures:

Inform other team members before meeting. Remind team members of team meeting. Someone takes notes on what happened in the meeting/s.

Risk Identifier: RM-PP-09Risk Description: Transportation problems (e.g. bus strike or car broken down).Impact Description:

Cannot attend or late for team or group meeting/s. Cannot access resources to do the project.

Probability: lowImpact: MediumPreventative measures:

Inform other team member before meeting/s.

Risk Identifier: RM-PP-10Risk Description: Conflict/s between team member/s.Impact Description:

Disagreements affect the outcome of the project. Time wasted in arguments.

Probability: lowImpact: MediumPreventative measures:

Other team members should help solve the problem/s before continuing the project. Discuss with project group to swap team members.

Risk Identifier: RM-PP-11Risk Description: Insufficient References.Impact Description:

Affects the quality of the report.Probability: HighImpact: MediumPreventative measures:

Seek online references. Seek reference books. Seek newspapers and magazines articles.

Risk Identifier: RM-PP-12Risk Description: Insufficient data.Impact Description:

Affects the accuracy of the report.Probability: HighImpact: MediumPreventative measures:

Seek alternative resources. Compare data from different resources.

12

Risk Identifier: RM-PP-13Risk Description: Reliability of resources.Impact Description:

Report contains errors and useless data and materials.Probability: HighImpact: HighPreventative measures:

Compare information with different resources. Compare data from different resources.

Risk Identifier: RM-PP-14Risk Description: Reliability of resources.Impact Description:

Report contains errors and useless data and materials.Probability: HighImpact: HighPreventative measures:

Compare information with different resources. Compare data from different resources.

Risk Identifier: RM-PP-15Risk Description: Misconceptions.Impact Description:

Effort and time is wasted in producing a useless document.Probability: MediumImpact: HighPreventative measures:

Project group discuss on details before work is carried out by individual teams. Project group should read and understand the notes given.

13

7. Resource Required

Office SpaceA place enough for 20 people to work on the project proposal.

Personal Computer [Quantity - 4]Hardware Requirements Intel Pentium 4 630 3.00GHz (800FSB) 1GB (400MHz) DDR-RAM PC-3200 80Gb 8MB Cache 7200rpm ATA100 Hard Disk Drive Video, Sound & 10/100 LAN onboard 1.44Mb Floppy Disk Drive 52x32x52 IDE CD-RW 56K V.92 PCI Internal Modem 17-inch Flat screen Monitor PS/2 Keyboard & Optical Wheel Mouse USB2.0 Port Interface 56K V.92 PCI Internal Modem

Software Requirements Microsoft Word Professional Version 2003(11.5608.5606) Microsoft Excel Professional Version 2003(11.5608.5606) Microsoft Windows XP Operating System Microsoft Windows Internet Explorer (version 6.0.2800.1106) Microsoft Office Outlook Version 2003 (11.5608.5606) Microsoft Project Core

Printer/Fax/Scanner/Copier [Quantity - 1] Digital copier, laser printer and fax all-in-one Laser copy quality (12cpm, 600 x 600 dpi / up to 1200 x 600 dpi enhanced) Huge fax memory of 79 pages High print resolution (12 ppm 600 x 600 dpi / up to 2400 x 600 dpi enhanced) All-in-one cartridge: no maintenance Electronic sorting of copies Network printing with optional network adaptor 30-sheet Auto Document Feeder

External Storage DevicesFloppy disks, thumb drives, CD-RW disks and external hard disk are used for any backups.

14

8. Deliverables

1. Project plan Softcopy submitted to Project Group by 2:00pm Tuesday, August 31st 2005.

2. Statement of NeedsSoftcopy submitted to Project Group by 2:00pm Tuesday, September 6th 2005.

3. Requirements SpecificationSoftcopy submitted to Project Group by 2:00pm Tuesday, September 13th 2005.

4. Feasibility Study Softcopy submitted to Project Group by 2:00pm Tuesday, October 4th 2005.

5. Functional Analysis Softcopy submitted to Project Group by 2:00pm Tuesday, October 4th 2005.

6. Subsystem Analysis Softcopy submitted to Project Group by 2:00pm Tuesday, October 4th 2005.

7. Test Plan Softcopy submitted to Project Group by 2:00pm Tuesday, October 11th 2005.

8. Report of Portfolio Softcopy submitted to Project Group by 2:00pm Tuesday, October 18th 2005.

9. Final ReportSoftcopy submitted to Paul Bunnik by 2:00pm Tuesday, November 1st 2005.

9. Organisational StructureThe project group has decided to use a simplified project organisation structure. The project group consists of 18 people and will be broken into 4 teams. The project group will adopt a democratic approach, so every team will be able to participate in the discussions and brain storming for each work package. Each team is responsible for gathering of information and ideas, and the compilation of the documents of 2 work packages.

15

System Aspect TeamThe system aspect team, concerns the overall understanding of the system, and the responsibility to bring together and coordinate the work of the various portfolio concerns to ensure the resulting documentation and design is of a single unified whole entity.

Technical TeamThe technical team is responsible for ensuring that the final system is capable of the operational needs. It is also responsible for ensuring that the system is a feasible option for SeaLink to undertake.

Non-Technical TeamThe non-technical team is responsible for ensuring that the final system satisfies the customer’s needs. It is also responsible for ensuring that the system is a viable option for SeaLink.

Safety TeamThe safety team assures that the systems cannot cause harm, and the responsibility of ensuring the resulting documentation and design plans can cope with failures.

Team 2: Technical

Saddlier, Timothy Stuart Lim, Ted Cheng Tiong, Sie King Wong, Sze Meu Mares, Lachlan Lenard

Team 3: Non-Technical

Belperio, Michael Bailes, Serge Cheang, Sim Meng Wallis, Adam

Team 1: System Aspect

Teo, Check Kai Edwin Ramakrishnan, SujathaChang, Shi HaoDiep, WilliamLing, Sien Tong

Team 4: Safety

Thuan Quoc Gopal Pathi, Premkumar Tiwari, Ullash England, Samuel Gordon

Project Consultant

Paul Bunnik

16





Joyride to Space

Requirements Analysis DocumentVersion 1.6

17

Needs & Requirements Contents

1. Statement of Needs..............................................................................................................191.1. Section Overview..............................................................................................19

2. Scope....................................................................................................................................202.1. Document Overview.........................................................................................202.2. Privacy Statement.............................................................................................202.3. Definitions of keywords....................................................................................202.4. Requirements Specification..............................................................................22

2.3.1. Ground terminal...................................................................................................................222.4.1.1 Customer Service.......................................................................................................................................222.4.1.2 Training Capability....................................................................................................................................232.4.1.3 Launch Facility..........................................................................................................................................232.4.1.4 Control Capability.....................................................................................................................................242.4.1.5 Storage Capability.....................................................................................................................................252.4.1.6 Maintenance Capability.............................................................................................................................272.4.1.7 Geographical Location..............................................................................................................................282.4.1.8 Regulations.........................................................................................................282.3.1.9 Security Capability.....................................................................................................................................292.3.1.9 Disposal Capability...................................................................................................................................302.3.1.10 General Requirements.............................................................................................................................312.4.2. Space Transport Unit...........................................................................................................312.4.2.1 Carrying Capability...................................................................................................................................312.4.2.2 Safety Capability........................................................................................................................................312.4.2.3 Comfort & Entertainment Capability........................................................................................................332.4.2.4 Operational Capability..............................................................................................................................352.4.2.5 Security Capability.....................................................................................................................................372.4.2.6 Maintenance & Reliability.........................................................................................................................372.4.2.7 Regulations................................................................................................................................................38

18

1. Statement of Needs

1.1. Section OverviewOur customer, SeaLink, has expressed their interest in a system capable of providing joy flights to, “Space”. The needs statement provided by the Customer is as follows:

“Following the discovery that the sea bed near Victor Harbour is not interesting for undersea tours, SeaLink have decided to diversify into offering joy flights to, “Space”. They require a complete system to provide this service, based within four hours driving time of Adelaide.”

The following needs were derived from the initial statement provided by the customer in consultation with the customer’s agent.

Need Description

SLINK 1.0

SLINK 1.1

SLINK 1.2

SLINK 1.3

SLINK 1.4

SLINK 1.5

SLINK 1.6

SLINK 1.7

SLINK 1.8

SLINK 1.9

The system needs to be geographically located within 4 hours drive from the Adelaide Central Business District (CBD).

The system needs to be capable of flying customers into space.

The system needs to be capable of returning customers from space.

The system needs to provide a means of transporting customers back to the starting point after the flight.

The system needs to be capable of providing an environment for customers to enjoy their flight to and from space.

The system needs to be compliant with government regulations and policies.

The system needs to be maintainable throughout its intended life cycle.

The system needs to be reliable.

The system needs to be able to operate under normal weather conditions

The system needs to be commercial viable.

19

2. Scope

2.1. Document OverviewThis document is to identify and specify the requirements necessary to fulfil the needs of the project. The needs of the project have been derived from the user. By breaking down the needs, a list of requirements was formed. This document also contains the description and details including priority, traceability and various verification methods associated with that requirement in meeting the user’s need(s).

2.2. Privacy StatementThis document is for use with the SeaLink Space Tour project only; no other persons shall view this material, for security and privacy purposes.

2.3. Definitions of keywords

Acronyms

MTBF: Mean time between failures refers to the average duration between failures of the device or system.

MTBM: Mean time between maintenance.

MTBR: Mean time between repairs.

Foot Candle: A measurement unit for illumination levels. 1 foot candle is equivalent to the amount of light provided by a single candle at a distance of 1 foot.

Pa: Pascal. It is a unit for measuring pressure. 1Pa is equivalent to 1 Newton per square meter

20

Maintenance Levels Definition:

Basic maintenance – refers to the maintenance which can be carried out on site without the need for specialised equipment by personnel with low maintenance skills, such as system operator. The maintenance tasks included in this level of maintenance are as follows:

1. Visual inspection of system.2. Operational check of system.3. Minor servicing.4. Adjustment, removal and replacement of non critical system components.5. Cleaning and washing of system or device.

Intermediate maintenance – Refers to the maintenance tasks which needs to be performed by maintenance personnel with intermediate maintenance skills. These maintenance tasks can usually be performed on site while in the presence of mobile maintenance units, such as a repair truck or van. Otherwise, these maintenance tasks will need to be performed at a specialised repair facility. The tasks included in this level of maintenance are as follows:

1. Detail inspection and system checkout.2. Major servicing.3. Major equipment repair and modification.4. Complicated adjustments.5. Limited calibration.6. Any overload from the basic maintenance level.

Advance maintenance – Refers to the maintenance tasks which needs to be performed by maintenance personnel with high skill level in a specialised maintenance depot or with the use of specialised tools. The tasks included in this level of maintenance are listed below:

1. Complicated adjustments of critical components.2. Complex equipment repairs and modifications.3. Overhaul and rebuild of equipment.4. Detail calibration of system.5. Overload maintenance tasks from intermediate maintenance level.

21

2.4. Requirements Specification

2.3.1. Ground terminal

2.4.1.1 Customer Service

Requirement Identifier: GT_CS01 Type: PhysicalRequirement: Ground terminal shall be capable of accommodating no less than 250 personnel.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.4, SLINK 1.9Verification Method: Analysis.

Requirement Identifier: GT_CS02 Type: FunctionalRequirement: Ground terminal shall be capable of performing customer registration for no less than 200 patronsPriority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.4, SLINK 1.9Verification Method: Analysis.

Requirement Identifier: GT_CS03 Type: FunctionalRequirement: Customer registration shall be completed in no greater than 2 hoursPriority: HighTraceability: SLINK1.4Verification Method: Analysis.

Requirement Identifier: GT_CS04 Type: PhysicalRequirement: Ground terminal shall be capable of providing luggage storage spaces for no less than 200 patronsPriority: HighTraceability: SLINK 1.1Verification Method: Analysis.

Requirement Identifier: GT_CS05 Type: PhysicalRequirement: Storage space provided for each patron shall have a volume of no less than 0.4 meters cube.Priority: HighTraceability: SLINK 1.1Verification Method: Analysis.

Requirement Identifier: GT_CS06 Type: FunctionalRequirement: Ground terminal shall provide patrons with vehicle parking areasPriority: HighTraceability: SLINK1.4, SLINK 1.9Verification Method: Analysis.

Requirement Identifier: GT_CS07 Type: PhysicalRequirement: Vehicle parking area shall accommodate no less than 250 class C vehiclesPriority: MediumTraceability: SLINK1.4, SLINK 1.9Verification Method: Analysis.

22

Requirement Identifier: GT_CS08 Type: FunctionalRequirement: Ground terminal shall be capable of providing meals for no less than 300 people per day.Priority: HighTraceability: SLINK1.4, SLINK 1.9Verification Method: Analysis.

Requirement Identifier: GT_CS09 Type: FunctionalRequirement: Ground terminal shall be capable of providing internet connection for no less than 200 patronsPriority: HighTraceability: SLINK1.4, SLINK 1.9Verification Method: Analysis.

Requirement Identifier: GT_CS10 Type: Functional Requirement: Ground terminal shall be capable of providing telephone service for no less than 200 patrons.Priority: HighTraceability: SLINK1.4, SLINK 1.9Verification Method: Analysis.

Requirement Identifier: GT_CS11 Type: FunctionalRequirement: Ground terminal shall provide sanitary services for no less than 200 patronsPriority: HighTraceability: SLINK1.4, SLINK 1.9Verification Method: Analysis.

2.4.1.2 Training Capability

Requirement Identifier: GT_TC01 Type: FunctionalRequirement: Ground terminal shall be capable of conducting space training for no less than 200 peoplePriority: HighTraceability: SLINK1.5, SLINK1.14Verification Method: Analysis.

Requirement Identifier: GT_TC02 Type: FunctionalRequirement: Ground terminal shall be capable of conducting pre-launch briefing for no less than 200 peoplePriority: HighTraceability: SLINK1.5, SLINK1.14Verification Method: Analysis.

2.4.1.3 Launch Facility

Requirement Identifier: GT_LF01 Type: FunctionalRequirement: Ground terminal shall be capable of performing launch sequencePriority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Simulation

Requirement Identifier: GT_LF02 Type: FunctionalRequirement: Each launch sequence shall be capable of launching no less than 1 Space Transport Units into space. Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Simulation.

23

Requirement Identifier: GT_LF03 Type: PerformanceRequirement: Ground terminal shall be capable performing launch sequences at an interval of no greater than 48 hoursPriority: HighTraceability: SLINK 1.7Verification Method: Analysis.

Requirement Identifier: GT_LF04 Type: FunctionalRequirement: Ground terminal shall be capable of providing Pre-launch maintenance on all active Space Transport UnitsPriority: HighTraceability: SLINK 1.6, SLINK 1.7, SLINK 1.5,Verification Method: Demonstration.

Requirement Identifier: GT_LF05 Type: PerformanceRequirement: Ground terminal shall be capable completing all Pre-launch maintenance in no greater than 24 hours Priority: HighTraceability: SLINK 1.7Verification Method: Demonstration.

Requirement Identifier: GT_LF06 Type: FunctionalRequirement: Ground terminal shall be capable of refuelling all active Space Transports UnitsPriority: HighTraceability: SLINK1.1, SLINK1.2, SLINK 1.6Verification Method: Demonstration.

2.4.1.4 Control Capability

Requirement Identifier: GT_CF01 Type: FunctionalRequirement: Ground terminal shall be capable of initiating the launch sequence Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration.

Requirement Identifier: GT_CF02 Type: FunctionalRequirement: Ground terminal shall be capable of monitoring the activity of all Space Transport Units in launch sequencePriority: HighTraceability: SLINK1.1, SLINK1.2, SLINK 1.5Verification Method: Simulation.

Requirement Identifier: GT_CF03 Type: FunctionalRequirement: Ground terminal shall be capable of aborting launch sequences Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK 1.5Verification Method: Simulation.

24

Requirement Identifier: GT_CF04 Type: FunctionalRequirement: Ground terminal shall be capable of monitoring telemetry of all Space Transport Units in operation.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: GT_CF05 Type: FunctionalRequirement: Ground terminal shall be capable of monitoring weather conditions in a radius of no less than 250 kilometres from the ground terminal.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK 1.5Verification Method: Demonstration, Simulation.

Requirement Identifier: GT_CF06 Type: FunctionalRequirement: Ground terminal shall be capable of monitoring air traffic in a radius of no less than 250 kilometres from the ground terminal.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK 1.5Verification Method: Demonstration, Simulation.

Requirement Identifier: GT_CF07 Type: FunctionalRequirement: Ground terminal shall be able to communicate with all space transport units in operation.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: GT_CF08 Type: FunctionalRequirement: Ground terminal shall be capable of aborting a mission in progress.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK 1.5Verification Method: Simulation.

Requirement Identifier: GT_CF09 Type: FunctionalRequirement: Ground terminal shall be capable of coordinating the return of the passengers to the ground terminal.Priority: HighTraceability: SLINK1.3Verification Method: Simulation.

2.4.1.5 Storage Capability

Requirement Identifier: GT_SC01 Type: FunctionalRequirement: Ground terminal shall be capable of storing no less than 5 Space Transport Units.Priority: HighTraceability: SLINK1.9Verification Method: Analysis.

25

Requirement Identifier: GT_SC02 Type: FunctionalRequirement: Ground terminal shall ensure that Space Transport Units under storage are not exposed to temperature greater than 30 degrees Celsius.Priority: HighTraceability: SLINK1.9Verification Method: Demonstration.

Requirement Identifier: GT_SC03 Type: FunctionalRequirement: Ground terminal shall ensure that Space Transport Units under storage are not exposed wind speeds greater than 10 kilometres an hour.Priority: HighTraceability: SLINK1.9Verification Method: Demonstration.

Requirement Identifier: GT_SC04 Type: FunctionalRequirement: Ground terminal shall ensure that Space Transport Units under storage are not exposed to precipitation. Priority: HighTraceability: SLINK1.9Verification Method: Demonstration.

Requirement Identifier: GT_SC05 Type: FunctionalRequirement: Ground terminal shall ensure that access to Space Transport Units under storage is restricted to authorised personnel only.Priority: HighTraceability: SLINK1.9, SLINK1.5Verification Method: Demonstration.

Requirement Identifier: GT_SC06 Type: FunctionalRequirement: Ground terminal shall provide storage space for Space Transport Unit maintenance equipment.Priority: HighTraceability: SLINK1.9, SLINK 1.6Verification Method: Analysis.

Requirement Identifier: GT_SC07 Type: FunctionalRequirement: Ground terminal shall provide storage space for Ground terminal maintenance equipment.Priority: HighTraceability: SLINK1.9, SLINK 1.6Verification Method: Demonstration.

Requirement Identifier: GT_SC08 Type: FunctionalRequirement: Ground terminal shall provide storage space for no less than 20 sets of parts necessary for performing basic maintenance on Space Transport UnitsPriority: HighTraceability: SLINK1.9, SLINK 1.6Verification Method: Analysis.

Requirement Identifier: GT_SC09 Type: FunctionalRequirement Ground terminal shall provide storage space for no less than 10 sets of parts necessary for performing Intermediate maintenance on Space Transport Units Priority: HighTraceability: SLINK1.9, SLINK 1.6Verification Method: Analysis.

26

Requirement Identifier: GT_SC10 Type: FunctionalRequirement: Ground terminal shall provide storage space for no less than 2 sets of parts necessary for performing Advance maintenance on Space Transport Units Priority: HighTraceability: SLINK1.9, SLINK 1.6Verification Method: Analysis

Requirement Identifier: GT_SC11 Type: PhysicalRequirement: Ground terminal shall have fuel storage for no less than 20 space flights.Priority: HighTraceability: SLINK1.9, SLINK 1.6Verification Method: Analysis

2.4.1.6 Maintenance Capability

Requirement Identifier: GT_MC01 Type: FunctionalRequirement: Ground terminal shall be capable of performing basic maintenance on no less than 5 Space Transport UnitsPriority: HighTraceability: SLINK 1.6Verification Method: Demonstration.

Requirement Identifier: GT_MC02 Type: FunctionalRequirement: Ground terminal shall be capable of performing Intermediate maintenance on no less than 2 Space Transport Units.Priority: HighTraceability: SLINK 1.6Verification Method: Demonstration.

Requirement Identifier: GT_MC03 Type: FunctionalRequirement: Ground terminal shall be capable of performing Advance maintenance no less than 1 Space Transport Unit.Priority: HighTraceability: SLINK 1.6Verification Method: Demonstration.

Requirement Identifier: GT_MC04 Type: PerformanceRequirement: Ground terminal shall have a MTBF of no less than 2000 hoursPriority: HighTraceability: SLINK 1.6, SLINK 1.7Verification Method: Analysis.

Requirement Identifier: GT_MC05 Type: PerformanceRequirement: Ground terminal shall have a MTBM of no less than 24 hoursPriority: HighTraceability: SLINK 1.6, SLINK 1.7Verification Method: Analysis.

27

Requirement Identifier: GT_MC06 Type: PerformanceRequirement: Ground terminal shall have a MTBR of no less than 500 hoursPriority: HighTraceability: SLINK 1.6, SLINK 1.7Verification Method: Analysis.

Requirement Identifier: GT_MC07 Type: FunctionalRequirement: Ground terminal shall be capable of performing basic maintenance on all Ground based systemsPriority: HighTraceability: SLINK 1.6Verification Method: Demonstration.

Requirement Identifier: GT_MC08 Type: FunctionalRequirement: Ground terminal shall be capable of performing Intermediate maintenance on all Ground based systemsPriority: HighTraceability: SLINK 1.6Verification Method: Demonstration.

Requirement Identifier: GT_MC09 Type: FunctionalRequirement: Ground terminal shall be capable of performing Advance maintenance all Ground based systems.Priority: HighTraceability: SLINK 1.6Verification Method: Demonstration.

2.4.1.7 Geographical Location

Requirement Identifier: GT_GL01 Type: PhysicalRequirement: Ground terminal shall be geographically located no greater than 320 km from Adelaide CBD.Priority: HighTraceability: SLINK1.0Verification Method: Demonstration.

2.4.1.8 Regulations

Requirement Identifier: GT_GL01 Type: ConstrainRequirement: Ground terminal structures shall conform to Building Code of Australia 2005Priority: HighTraceability: SLINK1.5Verification Method: Demonstration, Analysis, Simulation

Requirement Identifier: GT_GL02 Type: ConstrainRequirement: The system shall conform to space vehicle launch standards ISO 14620-3:2005 Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: GT_GL03 Type: ConstrainRequirement: The system shall conform to space system cleanliness standard ISO 14952-2:2003 Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

28

Requirement Identifier: GT_GL04 Type: ConstrainThe system shall conform to spacecraft communication standard ISO 13419:2003 Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: GT_GL05 Type: ConstrainRequirement: The system shall conform to space systems safety standard ISO 14620-2:2000 Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: GT_GL06 Type: ConstrainRequirement: The system shall conform to emergency remote control standard ISO 14950:2003.Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: GT_GL07 Type: ConstrainRequirement: The system shall conform to Civil Aviation Safety Regulations 1998Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

2.3.1.9 Security Capability

Requirement Identifier: GT_SC01 Type: FunctionalRequirement: Ground terminal shall be capable of performing surveillance on areas within the ground terminal which are accessible to the public Priority: HighTraceability: SLINK1.5Verification Method: Demonstration, Analysis

Requirement Identifier: GT_SC02 Type: FunctionalRequirement: Ground terminal shall be capable of maintaining surveillance on all restricted areas within the ground terminalPriority: HighTraceability: SLINK1.5Verification Method: Demonstration, Analysis

Requirement Identifier: GT_SC03 Type: PhysicalRequirement: All restricted areas within ground terminal shall be labelled with no less than 1 signPriority: MediumTraceability: SLINK1.5Verification Method: Demonstration

Requirement Identifier: GT_SC04 Type: FunctionalRequirement: Ground terminal shall be capable of detecting the presence of firearms on all customers entering the ground terminalPriority: HighTraceability: SLINK1.5Verification Method: Demonstration

29

Requirement Identifier: GT_SC05 Type: FunctionalRequirement: Ground terminal shall be capable of detecting the presence of explosives on all customers entering the ground terminalPriority: HighTraceability: SLINK1.5Verification Method: Demonstration

Requirement Identifier: GT_SC06 Type: FunctionalRequirement: Ground terminal shall be capable of detecting the presence of firearms on all employees entering the ground terminalPriority: HighTraceability: SLINK1.5Verification Method: Demonstration

Requirement Identifier: GT_SC07 Type: FunctionalRequirement: Ground terminal shall be capable of detecting the presence of explosives on all employees entering the ground terminalPriority: HighTraceability: SLINK1.5Verification Method: Demonstration

Requirement Identifier: GT_SC08 Type: PhysicalRequirement: Ground terminal shall be capable of accommodating no less than 30 security officersPriority: MediumTraceability: SLINK1.5Verification Method: Analysis

Requirement Identifier: GT_SC09 Type: PerformanceRequirement: Ground terminal shall be capable of recording surveillance imagesPriority: MediumTraceability: SLINK1.5Verification Method: Analysis

Requirement Identifier: GT_SC10 Type: PerformanceRequirement: Ground terminal shall be capable of maintaining no less than 48 hours of surveillance recordingPriority: MediumTraceability: SLINK1.5Verification Method: Demonstration, Analysis

2.3.1.9 Disposal Capability

Requirement Identifier: GT_DC01 Type: FunctionalRequirement: Ground terminal shall be capable of discarding faulty equipmentPriority: HighTraceability: SLINK1.06Verification Method: Analysis

Requirement Identifier: GT_DC02 Type: FunctionalRequirement: Ground terminal shall be capable of discarding Space transport units at the end of the life cyclePriority: HighTraceability: SLINK1.06Verification Method: Analysis

30

2.3.1.10 General Requirements

Requirement Identifier: GT_RT01 Type: FunctionalRequirement: Ground terminal shall provide the operator with no less than 1 means of starting the systemPriority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration

2.4.2. Space Transport Unit

2.4.2.1 Carrying Capability

Requirement Identifier: STU_CC01 Type: FunctionalRequirement: Space transport unit shall be capable of carrying no less than 20 peoplePriority: HighTraceability: SLINK1.9, SLINK1.1, SLINK1.2Verification Method: Demonstration

Requirement Identifier: STU_CC02 Type: FunctionalRequirement: Space Transport unit shall be capable of carrying a weight of no less than 1 tonne Priority: MediumTraceability: SLINK1.9, SLINK1.1, SLINK1.2Verification Method: Simulation.

Requirement Identifier: STU_CC03 Type: PhysicalRequirement: Space Transport unit shall provide each passenger with no less than 1 means of storing belongingsPriority: MediumTraceability: SLINK1.9Verification Method: Analysis.

Requirement Identifier: STU_CC04 Type: FunctionalRequirement: Space Transport unit shall provide no less than 1 means for entering the unitPriority: HighTraceability: SLINK1.9Verification Method: Demonstration

Requirement Identifier: STU_CC05 Type: FunctionalRequirement: Space Transport unit shall provide no less than 1 means of exiting the unitPriority: HighTraceability: SLINK1.9Verification Method: Demonstration

2.4.2.2 Safety Capability

Requirement Identifier: STU_SC01 Type: FunctionalRequirement: Space Transport unit shall provide no less than 1 means of securing passengers during flightPriority: HighTraceability: SLINK1.5Verification Method: Demonstration.

31

Requirement Identifier: STU_SC02 Type: FunctionalRequirement: Space Transport unit shall provide no less than 1 means of securing passengers’ belongings during flightPriority: HighTraceability: SLINK1.5Verification Method: Demonstration.

Requirement Identifier: STU_SC03 Type: FunctionalRequirement: Space transport unit shall have no less than 1 means of evacuating the passengers over landPriority: HighTraceability: SLINK1.5Verification Method: Demonstration

Requirement Identifier: STU_SC04 Type: FunctionalRequirement: Space transport unit shall have no less than 1 means of evacuating the passengers over waterPriority: HighTraceability: SLINK1.5Verification Method: Demonstration

Requirement Identifier: STU_SC05 Type: FunctionalRequirement: Space transport unit shall have no less than 1 means of evacuating the passengers in spacePriority: HighTraceability: SLINK1.5Verification Method: Demonstration

Requirement Identifier: STU_SC06 Type: PhysicalRequirement: Space transport unit shall have medical equipment necessary for performing first aid on no less than 20 peoplePriority: HighTraceability: SLINK1.5Verification Method: Demonstration

Requirement Identifier: STU_SC07 Type: PhysicalRequirement: Space transport unit’s interior shall be non-flammable Priority: HighTraceability: SLINK1.5Verification Method: Demonstration

Requirement Identifier: STU_SC08 Type: PhysicalRequirement: Space transport unit shall provide no less than 5 fire extinguishersPriority: HighTraceability: SLINK1.5Verification Method: Demonstration

Requirement Identifier: STU_SC09 Type: PhysicalRequirement: Fire extinguisher shall be accessible by all passengers Priority: HighTraceability: SLINK1.5Verification Method: Demonstration

32

2.4.2.3 Comfort & Entertainment Capability

Requirement Identifier: STU_CEC01 Type: PhysicalRequirement: Space transport unit shall have no less than 1 mounted video recording camera every 4 passengers.Priority: HighTraceability: SLINK1.4Verification Method: Demonstration.

Requirement Identifier: STU_CEC02 Type: PhysicalRequirement: Space transport unit shall have no less than 1 information device Priority: MediumTraceability: SLINK1.4, SLINK1.11Verification Method: Customer feedback, Demonstration.

Requirement Identifier: STU_CEC03 Type: FunctionalRequirement: Information device shall be accessible by all passengersPriority: MediumTraceability: SLINK1.4, SLINK1.11Verification Method: Demonstration

Requirement Identifier: STU_CEC04 Type: PhysicalRequirement: Space transport unit shall have a separation of no less than 0.1 metre between passengersPriority: MediumTraceability: SLINK1.4Verification Method: Analysis

Requirement Identifier: STU_CEC05 Type: PhysicalRequirement: Storage for passengers’ belongings shall be no greater than 1 metre from the passenger Priority: MediumTraceability: SLINK1.4Verification Method: Demonstration

Requirement Identifier: STU_CEC06 Type: PhysicalRequirement: Space transport unit shall provide all passengers with no less than 1 means of observing the vessel’s exterior environmentPriority: HighTraceability: SLINK1.4Verification Method: Demonstration

Requirement Identifier: STU_CEC07 Type: PhysicalRequirement: Space transport unit shall have no less than 1 entertainment systemPriority: HighTraceability: SLINK1.4Verification Method: Demonstration

Requirement Identifier: STU_CEC08 Type: FunctionalRequirement: Entertainment system shall be accessible by all passengers Priority: HighTraceability: SLINK1.4Verification Method: Demonstration

33

Requirement Identifier: STU_CEC09 Type: FunctionalRequirement: Space transport unit shall be capable of providing an interior illumination level of no less than 30 foot candles.Priority: MediumTraceability: SLINK1.4Verification Method: Demonstration.

Requirement Identifier: STU_CEC10 Type: FunctionalRequirement: Space transport unit shall be capable of providing an interior illumination level of no greater than 80 foot candles Priority: HighTraceability: SLINK1.4Verification Method: Demonstration.

Requirement Identifier: STU_CEC11 Type: FunctionalRequirement: The space transport unit shall be capable of controlling internal atmospherePriority: HighTraceability: SLINK1.4, SLINK1.1, SLINK1.2Verification Method: Demonstration

Requirement Identifier: STU_ CEC12 Type: Functional lRequirement: Space transport unit shall have an internal humidity of no less than 20%.Priority: HighTraceability: SLINK1.4, SLINK1.1, SLINK1.2Verification Method: Demonstration.

Requirement Identifier: STU_ CEC13 Type: FunctionalRequirement: Space transport unit shall have an internal humidity of no greater than 40%.Priority: HighTraceability: SLINK1.4, SLINK1.1, SLINK1.2Verification Method: Demonstration.

Requirement Identifier: STU_ CEC14 Type: FunctionalRequirement: The space transport unit shall have an interior temperature of no greater than 24 degrees Celsius.Priority: HighTraceability: SLINK1.4, SLINK1.1, SLINK1.2Verification Method: Demonstration.

Requirement Identifier: STU_ CEC15 Type: FunctionalRequirement: The space transport unit shall have an interior temperature of no less than 16 degrees Celsius.Priority: HighTraceability: SLINK1.4, SLINK1.1, SLINK1.2Verification Method: Demonstration.

Requirement Identifier: STU_ CEC16 Type: FunctionalRequirement: The space transport unit shall have an interior pressure of no greater than 32 kPa.Priority: HighTraceability: SLINK1.4, SLINK1.1, SLINK1.2Verification Method: Demonstration.

34

Requirement Identifier: STU_ CEC17 Type: FunctionalRequirement: The space transport unit shall have an interior pressure of no less than 28 kPa.Priority: HighTraceability: SLINK1.4, SLINK1.1, SLINK1.2Verification Method: Demonstration.

Requirement Identifier: STU_CEC18 Type: ConstrainRequirement: Space transport unit shall conform to spacecraft air composition standard ISO 15859-13:2004.Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: STU_CEC19 Type: FunctionalRequirement: Space Transport unit shall impose an acceleration force of no greater than 4.7G on passengersPriority: HighTraceability: SLINK1.4, SLINK1.1, SLINK1.2Verification Method: Demonstration

Requirement Identifier: STU_CEC20 Type: PhysicalRequirement: Space Transport unit shall have no less than 1 sanitary system.Priority: HighTraceability: SLINK1.4, SLINK1.5Verification Method: Demonstration.

Requirement Identifier: STU_CEC21 Type: PhysicalRequirement: The sanitary system shall be accessible to all personnel.Priority: HighTraceability: SLINK1.4, SLINK1.5Verification Method: Demonstration.

Requirement Identifier: STU_CEC22 Type: FunctionalRequirement: The Sanitary system shall be able to operate in zero gravity.Priority: HighTraceability: SLINK1.7Verification Method: Demonstration.

2.4.2.4 Operational Capability

Requirement Identifier: STU_OC01 Type: FunctionalRequirement: Space transport unit shall have a maximum altitude capability of no less than 100 Km.

Priority: HighTraceability: SLINK1.1Verification Method: Demonstration

Requirement Identifier: STU_OC02 Type: FunctionalRequirement: Space transport unit shall be capable of re-entering the earth’s atmosphere.Priority: HighTraceability: SLINK1.2Verification Method: Demonstration, Simulation

35

Requirement Identifier: STU_OC03 Type: FunctionalRequirement: Space transport unit shall be capable of landing Priority: HighTraceability: SLINK1.2Verification Method: Demonstration, Simulation

Requirement Identifier: STU_OC04 Type: FunctionalRequirement: Space transport unit shall be capable operating continuously in zero gravity for no less than 10 minutesPriority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Simulation

Requirement Identifier: STU_OC05 Type: FunctionalRequirement: Space transport unit shall be capable of sending communications to Ground terminalPriority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration

Requirement Identifier: STU_OC06 Type: FunctionalRequirement: Space transport unit shall be capable of receiving communications from Ground terminalPriority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration

Requirement Identifier: STU_OC07 Type: FunctionalRequirement: Space transport unit shall provide operator with no less than 1 means of controlling the unitPriority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Analysis

Requirement Identifier: STU_OC08 Type: FunctionalRequirement: Space transport unit shall be capable of performing self-tests Priority: HighTraceability: SLINK1.1. SLINK1.2, SLINK1.5Verification Method: Demonstration

Requirement Identifier: STU_OC09 Type: FunctionalRequirement: Space transport unit shall provide operator with no less than 1 means of initiating self-tests Priority: HighTraceability: SLINK1.1. SLINK1.2, SLINK1.5Verification Method: Demonstration, Simulation

Requirement Identifier: STU_OC10 Type: FunctionalRequirement: Space transport unit shall provide operator with navigation capabilityPriority: HighTraceability: SLINK1.1. SLINK1.2Verification Method: Analysis

Requirement Identifier: STU_OC11 Type: FunctionalRequirement: Space transport unit shall be capable of navigating with an error of no greater than 10 metersPriority: HighTraceability: SLINK1.1. SLINK1.2Verification Method: Simulation

36

Requirement Identifier: STU_OC12 Type: FunctionalRequirement: Space transport unit shall provide the operator with no less than 1 means of controlling the unit’s functionsPriority: HighTraceability: SLINK1.1. SLINK1.2Verification Method: Analysis

Requirement Identifier: STU_OC13 Type: FunctionalRequirement: Space transport unit shall provide no less than 1 means of restricting personnel access to control equipmentPriority: HighTraceability: SLINK1.1. SLINK1.2Verification Method: Demonstration

Requirement Identifier: STU_OC14 Type: PhysicalRequirement: Space transport unit shall be capable of withstanding a maximum exterior temperature of no less than 648.8 degrees Celsius.Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Simulation, Demonstration

Requirement Identifier: STU_OC15 Type: FunctionalRequirement: Space transport unit shall be capable of operating in ground winds no greater than 30km/hPriority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Simulation, Demonstration

2.4.2.5 Security Capability

Requirement Identifier: STU_SuC01 Type: FunctionalRequirement: Space transport unit shall be capable of maintaining surveillance of passenger compartmentPriority: HighTraceability: SLINK1.5Verification Method: Demonstration

Requirement Identifier: STU_SuC02 Type: PerformanceRequirement: Space transport unit shall be capable of retaining no less than 24 hours of surveillance dataPriority: HighTraceability: SLINK1.5Verification Method: Demonstration

2.4.2.6 Maintenance & Reliability

Requirement Identifier: STU_MR01 Type: PerformanceRequirement: Space transport unit shall have a MTBF of no less than 1800 hoursPriority: HighTraceability: SLINK 1.6, SLINK 1.7Verification Method: Analysis

37

Requirement Identifier: STU_MR02 Type: PerformanceRequirement: Space transport unit shall have a MTBR of no less than 72 hoursPriority: HighTraceability: SLINK 1.6, SLINK 1.7Verification Method: Analysis

Requirement Identifier: STU_MR03 Type: PerformanceRequirement: Space transport unit shall have a MTBM of no less than 24 hoursPriority: HighTraceability: SLINK 1.6, SLINK 1.7Verification Method: Analysis

Requirement Identifier: STU_MR04 Type: FunctionalRequirement: Space transport unit shall provide operator with the capability to perform basic maintenancePriority: HighTraceability: SLINK 1.6, SLINK 1.7Verification Method: Analysis

2.4.2.7 Regulations

Requirement Identifier: STU_RE01 Type: ConstrainRequirement: Space transport unit shall conform to technical safety standard ISO 14620-1:2002.Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: STU_RE02 Type: ConstrainRequirement: Space transport unit shall conform to Space Communication Protocol Standard (SCPS) ISO 15892:2000 Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: STU_RE03 Type: ConstrainRequirement: Space transport unit shall conform to Electromagnetic Compatibility Standard (EMC) ISO 14302:2002 Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: STU_RE04 Type: ConstrainRequirement: Space transport unit shall conform to aerospace electrical standard ISO 1540:1984.Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: STU_RE05 Type: ConstrainRequirement: Space transport unit shall conform to space system structural design standard ISO 14622:2000. Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

38

Requirement Identifier: STU_RE06 Type: ConstrainRequirement: Space transport unit shall conform to metallic pressured vessel composite standard ISO 14623:2003.Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: STU_RE07 Type: ConstrainRequirement: Space transport unit shall conform to manned space systems interface standard ISO 17399:2003.Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

Requirement Identifier: STU_RE08 Type: ConstrainRequirement: Space transport unit shall conform to fracture critical items standard ISO 21347:2005 Priority: HighTraceability: SLINK 1.5Verification Method: Demonstration.

39




Stud Period 6, 2005

Joyride to Space

Feasibility StudyVersion 1.2

40

Feasibility Study Contents

1.0. Introduction.......................................................................................................................421.3 Analysis of Proposals.........................................................................................46

1.3.1 VTOL Orbital Booster Rocket..............................................................................................461.3.2 VTHL Orbital Vehicle..........................................................................................................471.3.3 VTHL Sub Orbital Vehicle...................................................................................................481.3.4 Space Plane...........................................................................................................................481.3.5 2STSO Sub-Orbital Vehicle.................................................................................................491.3.6 Hybrid Jetpacks.....................................................................................................................501.3.7 Space Cable Car....................................................................................................................511.4 Performance Measure Analysis...............................................................................................53

Assigning Value Curves..........................................................................................53Table 10: Summary of Findings..............................................................................56

1.5. Conclusions.......................................................................................................................56

41

1.0. Introduction

Travelling to space is a complicated and difficult process because there are so many problems to solve and obstacles to overcome. Some of these problems to overcome when travelling to and from space shown below greatly affect the path we follow in order to achieve our objectives:

The vacuum of space Heat management problems Re-entry into Earth’s atmosphere Orbital mechanics Micrometeorites and space debris Cosmic and solar radiation

The following is a list of the possible transportation vehicles based on today’s available technologies, as well as some technologies that require periods of development. A brief list is given here, with short descriptions. The list is categorised into the following sections:

Conventional Vehicles Alternate Vehicle

Conventional Vehicles

Rockets o VTOL Orbital Booster

Conventional vertical take-off and vertical landing rocket engine booster with crew compartment on top of the rocket stack. Similar to boosters used in the Apollo, Mercury, and Gemini programs, and currently in the Soyuz program. This configuration is capable of achieving full orbital insertion with significant G-forces being felt by the passengers. The picture below in figure 3.6 is the Soyuz V rocket from Russia

Courtesy: http://www.space.com/businesstechnology/technology/

o VTHL Orbital ConfigurationConventional vertical take-off and horizontal landing rocket engine powered system similar to the dual-booster arrangement of the American shuttle orbiters. This configuration is capable of achieving a stable orbital insertion, as opposed to a sub-orbital trajectory.

o VTHL Sub-Orbital ConfigurationVertical take-off and horizontal landing rocket engine powered system. This vertical take off vehicle is designed only for sub-orbital flight, and hence as we have discussed has simplified requirements with regard to heat shielding, propulsion, and overall cost.

Space Plane The Space Plane is a HTOL1 configuration incorporating dual propulsion systems. Jet engines are used to bring the craft to ceiling height, at which point a rocket engine is ignited, boosting the craft out of the atmosphere. Current technology allows for only sub-orbital flights. That is, the booster can only provide enough energy to push the craft outside the atmosphere for a matter of minutes before it falls back to Earth. This restriction is related to the amount of fuel on board, as well as the weight of the craft.The picture below is the Space-Plane X33 which is based on horizontal HTOL take-off.

1 HTOL = Horizontal take-off and landing42

http://www.space.com/businesstechnology/technology/

Courtesy: http://www.space.com/businesstechnology/technology/x-33_update_000612.html

2STO Sub-Orbital Vehicle Two-stage to sub-orbit vehicle. Scaled Composite’s SpaceShipOne is an example of such a system.

The space vehicle is attached to an advanced jet aircraft, capable of climbing to ceiling height with the vehicle attached. At this height, the space vehicle is released, and its own propulsion system is activated for a duration long enough to allow the craft to climb above 100km. It then follows a ballistic trajectory, incorporating aero-braking to facilitate a horizontal landing on a normal landing strip. The 2STO configuration has the advantage of requiring less fuel and weight onboard the space vehicle, as it ‘hitches a ride’ with the jet aircraft to ceiling height.

43

http://www.space.com/businesstechnology/technology/x-33_update_000612.html

Alternative Vehicles

Hybrid Jetpacks The use of jetpacks is proposed as a dual-craft configuration where passengers in Jetpacks are released from a Jet plane cruising at ceiling height. Rocket engines fitted to each jetpack then boost the passengers into a suborbital trajectory. The small size and weight reduces the requirements placed upon the boost rocket engine. This vehicle requires significant technological development in the form of initial investment to be successful. The inclusion of this vehicle type is for discussion purposes only, as it has a relatively low predicted viability.

Space Cable Car The cable car is a novel technology that is not yet fully functional. Considerable initial investment would be required in order to utilise this technology in a space tourism application. It involves a cable link between the surface of the Earth and a satellite in geostationary orbit. The cable needs to have extreme structural integrity to withstand the large forces that are placed upon it. Passengers and cargo board a passenger transport on the Earth’s surface and the transport is then lifted into space along the cable.

1.2 Analysis Criteria for the Proposals

Performance Measure: SafetyRelative Importance: 1

This performance measure is defined as the public’s perception of the safety of a particular transportation method. Since the space excursion itself carries the same risks in the case of any space transportation vehicle, this performance measure is mostly effected by the launch and landing characteristics of the vehicle. Conventional systems such as vertical take-off and horizontal take-off2 craft score well due to the practiced nature of the technology. Since safety is a subjective measure that depends on the customer’s perception, the safety rank is simply assigned as a number from 1 to 9, with 1 indicating a less safe perception and 9 indicating the safest perception.

Performance Measure: Flight EnjoymentRelative Importance: 2

Enjoyment is an important performance characteristic as on of the customer’s needs is for a ‘joyride’ into space, and hence the flight needs to be as enjoyable as possible. The nature of space flight dictates that the craft needs to be accelerated away from the Earth, perform on-orbit operations, and then return to the Earth. The forces exerted on the passengers during the return trip are proportional to the initial force that is exerted on the passengers during their acceleration to space. Therefore, the enjoyment index is calculated as a combination of the relative ascent time spent under acceleration, and the force exerted on the passengers during that acceleration.

Flight enjoyment index = Ascent time under acceleration / Average force exerted on passengers during acceleration

Performance Measure: On-Orbit EnjoymentRelative Importance: 3

The second part of determining the enjoyment of the flight is the state of facilities available during on-orbit operations. This is related to the size of the transportation vehicle, which determines the amount of space available for such facilities as windows. Small capsule-like craft score poorly, while larger airline-style variants score well. It is also related to the maximum amount of people that the vehicle is capable of supporting at one time.

2 VTOL = Vertical take-off and Vertical Landing, HOTOL = horizontal take-off and horizontal landing44

On-orbit enjoyment index = Size of crew compartment of vehicle / Maximum number of passengers that are to be accommodated in that compartment

Performance Measure: Initial CostRelative Importance: 4

The predicted initial cost is the cost in $AUD required for the complete design and development of the transportation vehicle. This includes engineering design, review, prototype construction, subsystem testing, and final construction and testing.

Performance Measure: Time Provided In SpaceRelative Importance: 5

The time duration of the flight will determine if the passengers will experience the symptoms of being in space. It is related to the enjoyment measure, as higher levels of thrust will result in greater discomfort for the passengers, but will allow them to experience space for a longer period of time. This relationship saturates once sufficient energy to achieve orbital insertion has been achieved.

Performance Measure: Cost to the End-User

Relative Importance: 6The predicted cost in $AUD per seat per passenger for one trip into space. The pioneering flights of Tito, Shuttleworth and Olsen came with a price tag of USD $20 million dollars, however current plans for sub orbital space trips come with predicted costs as low as $USD 20,000.

Performance Measure: Operational CostRelative Importance: 7

This is the predicted cost to SeaLink Inc. for conducting one mission. It includes the cost of fuel, post flight repairs, and other vehicle-specific attributes.

Performance Measure: Operational LifetimeRelative Importance: 8

This measure incorporates the predicted MTTF and the entire operational lifetime of the vehicle from the time of commissioning to decommissioning.

45

1.3 Analysis of ProposalsThe proposals introduced in section 1.1 would be analysed in detail with the analysis criteria specified in section 1.2

1.3.1 VTOL Orbital Booster Rocket

Description:VTOL systems are currently implemented in the Russian Soyuz class spacecraft with excellent success. The Mercury, Gemini, and Apollo missions all used VTOL class launch vehicles. Since 1966 the most successful VTOL booster, Soyuz, has launched 750 times with a success rate of more than 97% [17].

Propulsion Type ScoreThe VTOL system utilises a standard rocket engine possessing enough thrust to put the cargo into Earth orbit. The propulsion system consists of a liquid fuel that is ignited by an oxidiser, subsequently initiating a controlled explosion that releases enough energy to push the craft into orbit. Although such technologies are well developed in today’s space industry, the incredibly dangerous nature of the propellants is a severe safety concern. For this reason, we assign the VTOL rocket a Propulsion system score of 1.

Launch Fuel ScoreThe amount of fuel in a VTOL configuration at launch is the most out of any of the proposed vehicle types. The Soyuz rocket requires, on average, 160,000 kg of highly volatile kerosene and liquid oxygen propellant [20]. For this reason, we assign this launch vehicle with a fuel score of 0.

Mission Goal ScoreThe mission goal of an orbital VTOL configuration is Earth orbit. This makes the flight less safe as compared to a suborbital excursion as the spacecraft is subject to higher stress levels, as well as the challenge of re-entry [10]. For this reason we assign a mission goal score of zero.

Physical Protection ScoreThe physical protection provided by a VTOL configuration is relatively good. A capsule can be used to safely accommodate the passengers, as well as provide the required shielding to protect from cosmic radiation. We therefore assign the VTOL configuration with a protection score of 2

The overall safety score for the orbital VTOL vehicle is 2+0+0+1 = 3

Entertainment factor (Figures Based on the Russian Soyuz Booster [17])Ascent Time under Acceleration = 500sAscent Thrust = 4034 kNLaunch Weight = 289,467 Kg

Flight enjoyment Measure = 500s * (4034 kN / 289, 467 kg) = 6.967

Time in Space for VTOL Orbital Booster: 40 hours (2400 minutes)Flight Enjoyment Measure = 6.97Space Experience Measure = 2400 / 6.97 = 344.3Cost factor As of 1999, the mission cost for the Soyuz spacecraft launching aboard the R-7 VTOL booster was approximately AUD $53.2 million dollars, and hence the cost per passenger would be some fraction of this number, depending on the number of passengers aboard. If we disregard profit margins, a generalised VTOL

46

launch vehicle carrying 50 passengers at approximately AUD $50 million dollars per launch would deliver a cost of approximately AUD $1 million dollars to the end-user.

1.3.2 VTHL Orbital VehicleThe VTHL configuration has been solely applied in the American space shuttle orbiter. Designed to launch like a rocket and land like an aircraft, the Shuttle has flown 114 missions with a 98.25% success rate [18]. Since its inception in 1981, several possible flaws have been identified in the VTHL configuration, including the possibility of spacecraft damage during ascent due to debris from the booster rockets.

Propulsion System ScoreThe launch requirements for a VTHL configuration typically involve the use of a space orbiter craft attached to a booster system. In the case of the American space shuttle orbiter, the spacecraft is attached to an external fuel tank, which is in turn attached to two rocket boosters on either side of the tank. Also, the craft’s heat shield (an essential part of an orbital flight) is facing the boosters during flight, allowing any debris coming off the boosters to impact the heat shield, and possibly cause damage. Such damage was found to be the cause of the Columbia disaster in 2003 [19].

In review, modification of the orientation and protective measures of this vehicle type is possible, making this configuration highly useable with the appropriate safety modifications. However, the propulsion system still shares several dangerous characteristics with the VTOL launch vehicle. Hence, we assign a score of 1 here.

Launch Fuel ScoreThe launch fuel requirements for a VTHL configuration are the same as that for a VTOL vehicle. The vehicle must be fully fuelled at launch, with an average of 700,000 kg of highly volatile liquid hydrogen and liquid oxygen propellants for the American space shuttle [19]. The potential danger of these propellants at launch is exemplified by the Challenger disaster. Hence we assign a score of 0 here.

Mission Goal ScoreThe mission goal for a VTHL configuration is the same as that for a VTOL vehicle, and requires complete orbital insertion. Hence we assign a score of 0 here.

Physical Protection ScoreThe physical protection requirements for a VTHL configuration are the same as that for a VTOL vehicle, hence we assign a score of 2 here.

The overall safety score for the orbital VTHL vehicle is 2+0+0+1 = 3

Entertainment factor

Time in Space: 2400 minutesFlight Enjoyment Measure = 5.408Space Experience Measure = 2400 / 5.408 = 443.7

Cost factor In a space tourism application with 50 passengers, a similar VTHL vehicle would be loaded with 50 passengers weighing approximately 100kg each, which is a total payload mass of 5000kg, one fifth of the standard shuttle launch mass. The launching cost would therefore be less by only a factor of approximately one tenth ($AUD 1 billion dollars), as less rocket fuel is needed, but more consumables such as oxygen are required to sustain the passengers and crew. With 50 passengers, and disregarding profit margins, the cost per passenger would therefore be approximately AUD $20 million dollars.

47

1.3.3 VTHL Sub Orbital VehiclePropulsion System ScoreThe launch requirements for a VTHL Sub Orbital configuration are the same as that for VTOL and orbital VTHL configurations, hence we assign a score of 1 here.

Launch Fuel ScoreSince this vehicle needs only attain the required speed to push itself momentarily into space, the amount of fuel required at launch is greatly reduced. A comparison of the energy required for an orbital and suborbital flight reveals that approximately 32 times less energy is required to accomplish the latter [10]. However, since the VTHL configuration is using rocket propulsion throughout the entire flight, it will still require more fuel than a Space Plane or 2STO vehicle. Hence, we assign a score of 1 here.

Mission Goal ScoreAs discussed earlier, a suborbital mission goal results in a much safer flight due to simplified requirements in terms of speed, force, and re-entry. Hence we assign a score of 2 here.

Physical Protection Score

The physical protection requirements for a VTHL Sub Orbital configuration are the same as that for a VTOL and VTHL orbital vehicle, hence we assign a score of 2 here.

The overall safety score for the VTHL suborbital vehicle is 1+1+2+2 = 6

Entertainment factor (Figures Based on the American Shuttle Orbiter [28])Ascent Acceleration Time = 530 s

Ascent Thrust = 34,000kN(This thrust is for the Space Shuttle with a 25,000 Kg payload delivery to LEO. Actual space tourism application with approximately 50 persons at 100Kg each = 5000 kg. Approximate thrust required = 10,000kN) Launch Weight = 5000 kg payload + 1,000,000 kg Weight of shuttle, boosters, and external fuel tank = 980,000 kg. Less fuel required for lighter payload is taken into consideration.

Flight Enjoyment Measure = 530s * (10,000 kN / 980,000 kg) = 5.408

Time in Space = 5 minutes

Flight Enjoyment Measure = 1.431

Space Experience Measure = 5 / 1.431 = 3.49

Cost factor Manufacturers of the ‘Ascender’ sub orbital booster are expecting to offer flights on their VTHL winged-booster rocket at a price of AUD $6500. It is a reasonable assumption that this price is indicative of most current VTHL sub orbital ventures.

1.3.4 Space PlanePropulsion System ScoreA space plane employs 2 propulsion systems. First, jet engines bring the craft to ceiling height, and then rocket engines ignite to push the craft into space. The fact that characteristically dangerous rocket propulsion is being used for only half the flight makes this approach the safest of all those we have considered. Hence, we assign a score of 2 here.

48

Launch Fuel ScoreSince rocket propulsion is only being used for half the journey, a relatively small amount of hazardous rocket fuel needs to be stored on board. However, jet engine fuel is still required in order to allow the Space Plane to reach ceiling height, and hence this takes away very slightly from the benefits created by the lack of rocket fuel. Hence, we assign a score of 1.5 here

Mission Goal ScoreAs is the case for the VTHL sub-orbital vehicle, the sub-orbital mission goal allows for a less complex and safer space flight. Hence, we assign a score of 2 here.

5.1.4.4 Physical ProtectionThe physical protection requirements for a Space Plane configuration are the same as that for VTOL, and VTHL orbital vehicles, hence we assign a score of 2 here.

The overall safety score for the Space Plane is 2+1.5+2+2 = 7.5

Entertainment factorAscent Time Under Acceleration = 97sAscent Thrust = 84.1 kNLaunch Mass = 5,700 kgFlight Enjoyment Measure = (84.1 kN / 5,700 kg) * 97s = 1.4311

Time in Space = 3.5 minutesFlight Enjoyment Measure = 1.388Space Experience Measure = 3.5 / 1.388 = 2.521

[21] 2005, ‘Suborbital Reusable Launch Vehicles and Emerging Markets’ Federal Aviation Administration and the Office of Commercial Space Transportation

Cost factorRocketplane Ltd. is planning on offering their sub orbital service aboard the Rocketplane by January 2007. The initial price per passenger for this sub orbital flight is expected to be approximately AUD $129,350 [21]. It is a reasonable assumption that this price is indicative of most current Space Plane ventures.

1.3.5 2STSO Sub-Orbital Vehicle

Propulsion System ScoreA 2-stage to sub-orbit vehicle has similar propulsion system characteristics as the previously discussed Space Plane. In a 2STSO vehicle, the space transport unit is in a parasitic configuration, attached to a jet aircraft. 2 propulsion systems are used, and hence the safety of the approach is relatively good as a rocket engine is only being used for half the flight. The propulsion system for a 2STSO vehicle differs from a Space Plane in that the rocket engine needs only push a fraction of the weight of the combined aircraft. This means that, in comparison to the Space Plane, only a fraction of rocket propellant needs to be used to accelerate a 2STSO space vehicle into orbit, as it has far less weight than a Space Plane vehicle. Hence, we assign a score of 2 here.

Launch Fuel ScoreAs stated above, the amount of rocket fuel required by a 2STSO vehicle is considerably less than that which is required by a space plane. This increases the safety aspect of the 2STSO approach slightly. Hence, we assign a score of 2 here.

49

Mission Goal ScoreThe sub-orbital mission goal allows for a less complex and safer space flight. Hence, we assign a score of 2 here.

Physical Protection ScoreThe physical protection requirements for 2STSO configuration are the same as that for VTOL, and VTHL orbital vehicles, hence we assign a score of 2 here.

The overall safety score for the 2STSO vehicle is 2+2+2+2 = 8

Entertainment factorAscent time under acceleration: 87sAscent Thrust: 74kNVehicle Weight: 3600 kgFlight Enjoyment Measure = (74 kN / 3600 kg) * 87s = 1.788

From the previous sub-orbital flights of SpaceShipOne, the average time spent in space is approximately 3.5 minutes

Time in Space = 3.5 minutesFlight Enjoyment Measure = 1.788Space Experience Measure = 1.957

CostAs we have discussed, Sir Richard Branson is entering into a venture in partnership with Scaled Composites to produce a SpaceShipOne variant for the purposes of conducting commercial sub orbital flights by 2007. The price per passenger for these initial flights is expected to be AUD $273,000 [27].

1.3.6 Hybrid Jetpacks

Propulsion System ScoreThis vehicle would use a combination rocket engine and reaction control thruster system (RCS) in order to perform a successful sub-orbital flight. A rocket engine would be required to boost the vehicle into space, and the RCS would be required for performing manoeuvres while in space. The propulsion system required here would have a high element of danger, as a fuel source of some description would be very close to the passenger. Also, it is reasonable to assume that that the rocket nozzle would be very close to the passenger also. The small size of the jet pack would necessitate the use of a relatively small rocket motor cone, and in essence would require the miniaturisation of most modern rocketry components. Even if this was completed within project schedule requirements, the proximity of the passenger to both the fuel source and the rocket nozzle makes this approach highly dangerous. Hence, we assign a score of 0 here.

Launch Fuel ScoreWhen released from the aerial ‘mother ship’, the amount of fuel required to boost into orbit is very hard to quantify. Since this application of Jet Pack technology has not been previously considered, there is no reference material that can aid in this discussion. One can deduce that the relatively light weight of the vehicle, coupled with the limited space available for fuel storage, would allow us to conclude that there would be a relatively small amount of fuel required at launch for this configuration. Hence, we assign a score of 1 here.

Mission Goal ScoreThe sub-orbital mission goal allows for a less complex and safer space flight. Hence, we assign a score of 2 here.

50

Physical Protection ScoreThis vehicle provides the least amount of physical protection from all the others we have considered. In a jetpack system, the passenger is exposed to micrometeorites and other space debris, as well as to cosmic radiation such as the Van Allen radiation belts. Since a considerable layer of shielding is required to protect against this radiation, this would considerably increase the weight and size of a jetpack system. Even with spacecraft-like shielding, there are limited provisions for the protection of vital life support systems and avionics systems. Hence, we assign a score of 0 here.

The overall safety score for the hybrid jetpack vehicle is 0+1+2+0 = 3

Entertainment factorAscent time under acceleration: 130s (similar to other sub orbital missions)Ascent Thrust = 3.5 kN (300 Kg mass overcoming the 9.81 m.s-2 acceleration of gravity)Vehicle Weight = 300 kgFlight Enjoyment Measure = (2.9 kN / 300 kg) * 130s = 1.51

Time in Space = 3.5 minutesFlight Enjoyment Measure = 1.51Space Experience Measure = 3.5 minutes / 1.51 = 2.317

CostIf we continue with our two assumptions, firstly the AUD $1billion dollar development cost, and secondly that the Jetpack design will become a miniature 2STSO vehicle, we can calculate that the cost per mission will be similar to the 2STSO cost presented above. In addition to a portion of the development cost (which, we assume, will be passes on to the end-user), the total end-user cost will be (very) approximately AUD $300,000.

1.3.7 Space Cable Car

Propulsion System Score The Cable car would utilise a revolutionary drive system to pull the car into orbit. A possible cable car configuration discussed in SPACEMART in 2001 described a Maglev system whereby the car is pushed into orbit by an advanced magnetic lift system. The propulsion system may utilise rocket technology, but on a much lower scale than the previously discussed vehicles. Hence we assign a score of 1.5 here.

Launch Fuel ScoreSince the cable car does not predominantly use rocket technology to lift itself into space, the amount of fuel required will be small. Some fuel may be required for rocket engines that provide an initial momentary lift force, and this amount of fuel will be very small in comparison to the other vehicles we have discussed. Hence, we assign a score of 2 here.

Mission Goal ScoreThe mission goal for a Space Cable Car vehicle is the same as that for a VTOL and VTHL vehicles, requiring complete orbital insertion. Hence we assign a score of 0 here.

Physical Protection ScorePassengers are relatively well protected inside the car, as it can be large enough to afford spacecraft-like shielding and other important physical protection means. The cable itself is highly vulnerable to damage that may be caused through likely collisions with space junk and other objects. A tear in the cable would be a catastrophic event, as the cable is the means by which the car is secured, and if the cable broke there is a possibility that the car would be lost. Hence, we assign a score of 0.5 here.

The overall safety score for the Space Cable Car = 1.5+2+0+0.5 = 5

51

Entertainment factorVehicle Weight: 20,000 kgFlight Enjoyment Measure = (196kN / 20000kg)*7200s = 70.56

Time in Space = 2400sFlight Enjoyment Measure = 70.56Space Experience Measure = 34.013

CostBelow are the approximate running costs for the space elevator proposed by Dr. Brad Edwards [24]:

Annual Operating Budget per year in US$MClimbers 0.2 - 2 eachTracking system 10Anchor station 10Administration 10Anchor maintenance 5Laser maintenance 20Other 30

TOTAL (50 launches) 135

The data presented quotes a USD $135 million dollars (AUD $175.5 million dollars) annual expenditure for a 50-mission year, resulting in a cost of $AUD 3.5million dollars per mission. Disregarding profit margins, and assuming a 50 passenger crew, this would result in a cost per passenger of approximately AUD $70,000.

52

1.4 Performance Measure AnalysisIn this section, a comparison of the analysis described in section 1.3 would be performed to determine a feasible solution for the joyride to space proposal based.

Summary of Safety Factors

Transportation Vehicle Safety Score RankingVTOL Orbital 3 5VTHL Orbital 3 5VTHL (Sub Orbital) 6 3Space Plane (Sub Orbital) 7.5 2

2STO (Sub Orbital) 8 1Hybrid Jetpacks (Sub Orbital) 3 5Space Cable Car (Orbital) 5 4

Table 1: Safety Rankings for Proposed Vehicles

Summary of Costing (per passenger)

Transportation Vehicle Score ($AUD) RankingVTOL (Orbital) $1,000,000 6VTHL (Orbital) $20,000,000 7VTHL (Sub Orbital) $6500 1Space Plane (Sub Orbital) $129,000 32STSO (Sub Orbital) $273,000 4Hybrid Jetpacks (Sub Orbital) $300,000 5Space Cable Car (Orbital) $70,000 2

Assigning Value CurvesValue curves allow us to define the relationship between an increase in the quality of a certain performance measure and the amount of value added to the system. The shape of each of the value curves defines a different relationship between these two quantities, and the equations describing the graphs can be used to calculate an adjusted ranking.

Vehicle SafetyAs vehicle safety is decreased, the reliability and marketability of the system is decreased. Therefore, the system value will drop exponentially, and hence the increasing RTS curve is chose, as shown below.

Increasing RTS [30]: Calculated equation = v(x) = -x0.5+1

The values for vehicle safety were computed and it is represented in table 6 below.

53

Customer’s Perception of Vehicle SafetyNORMALISED WEIGHTED v(x)

Vehicle Safety

Customer’s Perception of Vehicle Safety

Flight Enjoyment

Space Experience Enjoyment (HIB)

Development Costs

End-User Cost per Seat

Totals

VTOL Orbital Booster

0.169 0.069 .190 0.026 0.031 0.023 0.508

VTHL Orbital

0.132 0.110 0.088 0.011 0.027 0.023 0.391

VTHL Sub Orbital

0.104 0.087 0.042 0.142 0.038 0.024 0.437

Space Plane Sub Orbital

0.180 0.031 0.025 0.142 0.047 0.024 0.449

2STSO Sub Orbital

0.123 0.043 0.030 0.142 0.079 0.024 0.441

Hybrid Jetpacks Sub Orbital

0.016 0.140 0.292 0.084 0.095 0.023 0.380

Space Elevator Orbital

0.098 0.081 .190 0.046 0.095 0.024 0.244

Assigned Value Curve Equation

Increasing RTS: v(x) =

1-x^0.5

Increasing RTS: v(x) = 1-x^0.5


1-x^0.5

Increasing RTS: v(x) = 1-x^0.5

Linear RTS v(x) = x

S Curve,

v(x) =(sin((x

- 1/2)*pi) + 1)/2

Table 6: Rankings and Value Curves

This performance measure has similar behaviours to the previous measure, in that a decrease in the customer’s perception of vehicle safety will result in an exponential decrease in the system’s value. Hence we choose the increasing RTS value curve, which is shown above.

Flight EnjoymentHigh flight enjoyment will maintain the ‘joyride’ aim, and serve to keep the system viable for all customers. Undesired levels of flight enjoyment will decrease system value exponentially. Therefore we choose the increasing RTS curve

Space Experience EnjoymentThis performance measure exhibits similar behaviours as the previous Flight enjoyment measure, and hence we will use the increasing RTS curve.

Development CostsHigh development costs mean that the overall system value will be reduced. As development costs are reduced, the system value increases linearly. Hence, we use the Linear RTS value curve shown below:

Linear RTS [30]: Calculated equation: y = x54

End User Cost Per SeatThe most desired value here corresponds to the lowest end-user cost. However, if the end-user cost is too low the venture will not be viable. Also, if the end user cost is too high, then interest in the venture will be low. Hence, there exist a point in equilibrium which accomplished both these objectives, and this relationship is shown by the s-curve below:

S-Curve [30] Calculated Equation: y = (sin((x - 1/2)*pi) + 1)/2

Now, calculating v(x) for each of the proposed vehicles gives the table below:

Normalised v(x) Vehicle Safety

(Rank 1)

Customer’s Perception of Vehicle Safety (Rank 2)

Flight Enjoyment

(Rank 3)

Space Experience Enjoyment

(Rank 4)

Development Costs

(Rank 5)

End User Cost per Seat

(Rank 6)

Totals

VTOL Orbital Booster 0.4083 0.7072 0 0.8166 0.6667 0.514 3.112

VTHL Orbital 0.04 0.04 0.04 0.839 0.412 0 1.371

VTHL Sub Orbital 0.635 0.6375 0.7746 0 .5 .498 3.0426Space Plane Sub Orbital

0.2828 .8667 .8667 0 .5 .5069 3.0231

2STSO Sub Orbital .9129 .8166 .5774 0 .1667 .5047 2.9783

Hybrid Jetpacks Sub Orbital

0 0 0.505 0 0 0.1708 0.675

Space Elevator Orbital

0.6546 0.6576 0 0.756 0 0.4943 2.562

Assigned Value Curve Equation

Increasing RTS: v(x) = 1-

x^0.5


1-x^0.5


1-x^0.5


1-x^0.5

Linear RTS v(x) = x

S Curve, v(x) =(sin((x - 1/2)*pi) +

1)/2

Table 8: Rankings and Value Curves

In calculating the weightings for each performance measure, we will use the Rank Sum method as described in [30]:

This approach gives the following weightings:

Vehicle Safety = 0.2857Customer’s Perception of Vehicle Safety = 0.2380Flight Enjoyment = 0.1904Space Experience Enjoyment = 0.1428Development Costs = 0.0952End User Cost = 0.04761

55

Vehicle Totals Overall Rank

VTOL Orbital Booster 0.5081

VTHL Orbital 0.391 5VTHL Sub Orbital 0.437

4Space Plane Sub Orbital 0.449

22STSO Sub Orbital 0.441

3Hybrid Jetpacks Sub Orbital

0.380

6Space Elevator Orbital 0.244 7

Table 10: Summary of Findings

1.5. ConclusionsWe have performed a thorough analysis of several prospective vehicles, in an effort to identify those most feasible for a sub-orbital tourism venture. Our results revealed that a VTOL booster and a Space Plane were the most viable options, based on the performance characteristics identified earlier in the document.

56

References:

[1] ‘Gregory Olsen’, Wikipedia – The Free Encyclopaedia. Date Accessed: 03 October 2005URL: http://en.wikipedia.org/wiki/Gregory_Olsen

[2] ‘Dennis Tito’, Wikipedia – The Free Encyclopedia.Date Accessed: 03 October 2005URL: http://en.wikipedia.org/wiki/Dennis_Tito

[3] ‘Mark Shuttleworth, Wikipedia – The Free Encyclopedia. Date Accessed: 03 October 2005URL: http://en.wikipedia.org/wiki/Mark_Shuttleworth

[4] Collins, P 2000 ‘The Space Tourism Industry in 2030’ Proceedings of Space 2000, ASCE, pp 594-603

[5] Foust J, 2003 ‘Space tourism: managing expectations in uncertain times’ Space Review MagazineDate Accessed: 04 October 2005URL: http://www.thespacereview.com/article/13/1

[6] R Stockmans, P Collins & M Maita, 1995, "Demand for Space Tourism in America and Japan and its Implications for Future Space Activities", AAS paper no AAS 95-605, AAS Vol 91, pp 601-610

[7] David L 2005, ‘Richard Branson and Burt Rutan Form Spacecraft Building Company’, SPACE.comDate Accessed: 06 October 2005URL: http://www.space.com/news/050727_branson_rutan.html

[8] ‘Space Tourism – Personal Spaceflight to You’, HobbySpace.comDate Accessed: 05 October 2005URL: http://www.hobbyspace.com/Tourism/

[9] Than K 2005, ‘Space Adventures Offers Up the Moon for Future Tourists’, SPACE.comDate Accessed: 12 October 2005URL :http://www.space.com/news/050810_dse_alpha.html

[10] ‘Differences Between Sub-Orbital and Orbital Space Flights’, Answers.com, Date Accessed: 12 October 2005URL: http://www.answers.com/topic/difference-between-sub-orbital-and-orbital

[11] ‘Aerobraking, Answers.comDate Accessed: 12 October 2005URL: http://www.answers.com/topic/difference-between-sub-orbital-and-orbital-spaceflights

[12] 2005, ‘Suborbital Reusable Launch Vehicles and Emerging Markets’ Federal Aviation Administration, Office of Commercial Space Transportation

[13] 2002, ‘Frequently Asked Questions about Ion Drive Propulsion’ NASA Johnson Space CentreDate Accessed: 20 October 2005URL: http://nmp.jpl.nasa.gov/ds1/tech/ionpropfaq.html

[14] 2005, ‘Soyuz Launch Vehicle – Wikipedia, The Free Encyclopaedia’

57

http://nmp.jpl.nasa.gov/ds1/tech/ionpropfaq.html

http://www.answers.com/topic/difference-between-sub-orbital-and-orbital-spaceflights

http://www.answers.com/topic/difference-between-sub-orbital-and-orbital

url:http://www.space.com/news/050810_dse_alpha.html

http://www.hobbyspace.com/Tourism/

http://www.space.com/news/050727_branson_rutan.html

http://www.thespacereview.com/article/13/1

http://en.wikipedia.org/wiki/Mark_Shuttleworth

http://en.wikipedia.org/wiki/Dennis_Tito

http://en.wikipedia.org/wiki/Gregory_Olsen

Date Accessed: 03 October 2005URL: http://en.wikipedia.org/wiki/Soyuz_launch_vehicle

[15] 2003, ‘Is Space Tourism Feasible?’Date Accessed: 12 October 2005URL: http://www.wisegeek.com/is-space-tourism-feasible.htm

[16] 2005, ‘Space Elevator’Date Accessed: 20 October 2005URL:http://www.everything2.com/index.pl?node_id=589103[17] 2005, ‘Soyuz Launch Vehicle’Date Accessed: 12 October 2005URL: http://www.fas.org/spp/guide/russia/launch/soyuz.htm

[18] 2003, ‘Space Shuttle’Date Accessed: 12 October 2005URL: http://www.braeunig.us/space/specs/shuttle.htm

[19] 2005, ‘Columbia Disaster’Date Accessed: 12 October 2005URL: http://en.wikipedia.org/wiki/Space_Shuttle_Columbia_disaster

[20] 2001, ‘Space Launchers – Soyuz, Molnyia’Date Accessed: 12 October 2005URL: http://www.braeunig.us/space/specs/r7.htm

[21] 2005, ‘SubOrbital Reusable Launch Vehicles and Emerging Markets’ Federal Aviation Administration and the Office of Commercial Space Transportation

[22] 2005, ‘Scaled Composite’s SpaceShipOne – Specifications’Date Accessed: 12 October 2005URL:http://en.wikipedia.org/wiki/SpaceShipOne#Specifications_.28SpaceShipOne

[23] 2003, ‘Stairway to Heaven’Date Accessed: 12 October 2005URL: http://www.pythom.com/story/StairwaytoheavenMay42005.shtml

[24] Edwards B 2004, ‘The Space Elevator – Building our Future’Date Accessed: 12 October 2005URL: http://www.spaceelevator.com/docs/General.SE.presentation.ppt[25] Pease K 2004, ‘Why SpaceShipOne Never Did, Never Will, And None Of Its Direct Descendants Ever Will, Orbit The Earth’,Date Accessed: 24 September 2005URL: http://www.daughtersoftiresias.org/misc/ss1.html

[26] Chandler D 2004, ‘Countdown for Rocket Planes’Date Accessed: 20 September 2005URL: http://cache.technologyreview.com/articles/03/02/wo_chandler020703.0.asp

[27] 2005, ‘Virgin Galactic’, Wikipedia – The Free Encyclopaedia,Date Accessed: 20 September 2005URL: http://en.wikipedia.org/wiki/Virgin_Galactic

[28] 2003, ‘Launch Systems’

58

http://en.wikipedia.org/wiki/Virgin_Galactic

http://cache.technologyreview.com/articles/03/02/wo_chandler020703.0.asp

http://www.daughtersoftiresias.org/misc/ss1.html

http://www.spaceelevator.com/docs/General.SE.presentation.ppt

http://www.pythom.com/story/StairwaytoheavenMay42005.shtml

url:http://en.wikipedia.org/wiki/SpaceShipOne#Specifications_.28SpaceShipOne

http://www.braeunig.us/space/specs/r7.htm

http://en.wikipedia.org/wiki/Space_Shuttle_Columbia_disaster

http://www.braeunig.us/space/specs/shuttle.htm

http://www.fas.org/spp/guide/russia/launch/soyuz.htm

http://www.everything2.com/index.pl?node_id=589103

http://www.wisegeek.com/is-space-tourism-feasible.htm

http://en.wikipedia.org/wiki/Soyuz_launch_vehicle

Date Accessed: 20 September 2005URL: http://www.islandone.org/Launch

[29] BBC Health Safety and Security NetDate Accessed: 20 September 2005URL: http://www.bbc.org.uk/ohss/defaul~1.htm

[30] The Space Review: Near space: balloons, satellites, and suborbital rocketsDate Accessed: 20 September 2005URL: http://www.thespacereview.com/

[31] Should Exist: Idea exchange, news of the futureDate Accessed: 20 September 2005URL: http://www.shouldexist.org/story/

[32] The Federal Communications Commission Washington, D.C. 20554Date Accessed: 20 September 2005URL: hraunfoss.fcc.gov/edocs_public/ attachmatch/DA-01-2132A1.doc

[33] Space Daily: Space Elevators get a liftDate Accessed: 20 September 2005URL: http://www.spacedaily.com/news/

[34] Space Future: Space Elevators, Space Hotels Tourism (Nathan Wilson)Date Accessed: 20 September 2005URL: http://www.spacefuture.com/home.shtml

[35] Press Clippings: Seattle's Space Needle by Greg Varney, P.E., and Todd St. GeorgeDate Accessed: 20 September 2005URL: http://www.mccarthy.com/news/news_clippings/clip-spaceneedle.html

[36] News: Earthquake activities in 2001Date Accessed: 20 September 2005URL: http://www.globaleye.org.uk/secondary_summer/news/seattle.html

[37] Space Technology: X33 rocket plane project by Leonard David Date Accessed: 20 September 2005URL: http://www.space.com/businesstechnology/technology/

[38] Ontario Science Centre: ScizoneDate Accessed: 20 September 2005 URL: http://www.ontariosciencecentre.ca/scizone/e3/circus/cannon/default.asp

[39] Ontario Science Centre: ScizoneDate Accessed: 19 September 2005 URL: http://www.ontariosciencecentre.ca/scizone/e3/circus/cannon/default.asp

[40] Space Suits: Mark WadeDate Accessed: 19 September 2005URL:http://www.astronautix.com/craftfam/spasuits.htm

59

url:http://www.astronautix.com/craftfam/spasuits.htm

url:http://www.ontariosciencecentre.ca/scizone/e3/circus/cannon/default.asp

url:http://www.ontariosciencecentre.ca/scizone/e3/circus/cannon/default.asp

http://www.space.com/businesstechnology/technology/

http://www.globaleye.org.uk/secondary_summer/news/seattle.html

http://www.mccarthy.com/news/news_clippings/clip-spaceneedle.html

http://www.spacefuture.com/home.shtml

http://www.spacedaily.com/news/future-01f.html

http://www.shouldexist.org/story/

http://www.thespacereview.com/

http://www.bbc.org.uk/ohss/defaul~1.htm

http://www.islandone.org/Launch




Stud Period 6, 2005

Joyride to Space

Functional Analysis & Subsystem BreakdownVersion 1.2

60

Functional Analysis Contents

Functional Analysis

1.0. Provide Joyride to Space...................................................................................................631.1. Perform Ground Operation...............................................................................................661.2. Perform Pre-Launch Operation.........................................................................................691.3. Perform Failure Analysis..................................................................................................711.4. Perform Space Operation..................................................................................................721.5. Launch Space Transport...................................................................................................751.6. Perform Retrieval Operation.............................................................................................771.7. Perform Mission Control..................................................................................................781.8. Perform Maintenance Operation.......................................................................................811.8. Disposal System................................................................................................................84

Sub-system Breakdown

2.0. Joyride System Hierarchy (Top Level Breakdown).........................................................872.1. Subsystem Breakdown of Ground Facility.......................................................................872.2. Subsystem Breakdown of Customer Service Subsystem..................................................892.3. Subsystem Breakdown of Maintenance Facility...............................................................902.4. Subsystem Breakdown of Mission Control System..........................................................912.5. Subsystem Breakdown of Space Vehicle.........................................................................922.6 Subsystem Breakdown of Life Support Subsystem...........................................................932.7 Subsystem Breakdown of Shuttle Control Subsystem.......................................................942.8 Subsystem Breakdown of Life Support Subsystem...........................................................95

61

Replace with appropriate number==>2. Scope

Replace with appropriate number==>2.1. Document OverviewThe Functional Analysis and Design process uses the input of the top level requirements developed earlier to progressively identify and analyse the system functions and sub-functions. This allows for the identification of alternatives to meet the system requirements. The document contains a hierarchical breakdown of each system and a functional flow block diagram with descriptions detailing the functional identifier, function name, description, data requirement and traceability.

Replace with appropriate number==>2.2. Privacy StatementThis document is for use with the SeaLink Space Tour project only; no other persons shall view this material, for security and privacy purposes.

62

1.0. Provide Joyride to Space

Hierarchical Breakdown – Provide Joyride to Space

63

Functional Flow Block Diagram: Provide Joyride to Space (1st Level)

64

Functional Block Analysis – Provide Joyride to Space

Functional Identifier: 1.0Function Name: Start SystemDescription: This function performs the initial boot up of the system after its completion. Brings the whole system up to operational levelData Requirement: NilTraceability:

Functional Identifier: 2.0Function Name: Perform Ground OperationDescription: Specifies the operations which are required to be carried out on the ground terminal for system to operate as described in the requirements document. Data Requirement: Outputs the “system functional” data to facilitate the launch operationTraceability: GT_CS02, GT_CS03, GT_CS06, GT_CS08, GT_CS09, GT_CS10, GT_CS11, GT_TC01, GT_TC02, GT_LF01, GT_LF02, GT_LF04, GT_LF06, GT_CF03, STU_CCO4, STU_CCO5

Functional Identifier: 3.0Function Name: Perform Space OperationDescription: Outlines the necessary operations which shall be carried out by the space transport in order to fulfil its role in transporting passengers into space. Data Requirement: Requires input from both “system functional” trigger from the ground station and the “launch command” from mission control before operations in this stage can be carried.Traceability: STU_CC01, STU_CC02, STU_CC04, STU_CC05, STU_SC01, STU_SC02, STU_CEC03, STU_CEC08, STU_CEC09, STU_CEC10, STU_CEC11, STU_ CEC12, STU_ CEC13, STU_ CEC14, STU_CEC15, STU_ CEC16, STU_ CEC17, STU_CEC18, STU_CEC19, STU_CEC22, STU_OC01, STU_OC02, STU_OC03, STU_OC04, STU_OC05, STU_OC06, STU_OC07, STU_OC08, STU_OC09, STU_OC10, STU_OC11, STU_OC12, STU_OC13, STU_OC15, STU_OC16, STU_SuC01, STU_MR04, STU_SC04, STU_SC05, STU_SC06

Functional Identifier: 4.0Function Name: Perform Retrieval OperationDescription: This function outlines the necessary operations for bring customers back to the ground terminalData Requirement: Retrieval operation is coordinated by the mission control and therefore requires an “initiate retrieval” trigger before operations in this stage can be carried out.Traceability:

Functional Identifier: 5.0Function Name: Perform Mission Control OperationDescription: Operations which are necessary for the coordination and supervision of the space operation are illustrated in this function. Data Requirement: Requires mission data which is being transmitted by the space transport while in operation. Also requires equipment data provided by the ground terminalTraceability: GT_CF01, GT_CF02, GT_CF03, GT_CF04, GT_CF05, GT_CF06, GT_CF07, GT_CF08

65

Functional Identifier: 6.0Function Name: Perform Maintenance OperationDescription: This function outlines the necessary operations for maintenance both the ground terminal and the space transportData Requirement: NilTraceability: GT_SC01, GT_SC02, GT_SC03, GT_SC05, GT_SC06, GT_SC07, GT_SC08, GT_SC09, GT_SC10, GT_MC01, GT_MC02, GT_MC03, GT_MC07, GT_MC08, GT_MC09

Functional Identifier: 7.0Function Name: Disposal OperationDescription: This function spells out operations necessary for the disposal of faulty or waste material during the system’s life span and also methods for disposing the whole system at the end of its life cycle.Data Requirement: NilTraceability: GT_DC01, GT_DC02

1.1. Perform Ground Operation

Hierarchical Breakdown – Perform Ground Operation

66

Functional Flow Block Diagram: Perform Ground Operations (2nd Level)

67

Functional Block Analysis – Perform Ground OperationsFunctional Identifier: 2.1Function Name: Service CustomersDescription: Describes the operations necessary for providing customer with a comfortable and safe environment. Data Requirement: NilTraceability: GT_CS02, GT_CS03, GT_CS06, GT_CS08, GT_CS09, GT_CS10, GT_CS11

Functional Identifier: 2.2Function Name: Perform Pre-launch OperationsDescription: This function describes the operations and equipment testing necessary piror to the launching of the space transport for ensuring a safe and reliable journey to space.Data Requirement: NilTraceability: GT_LF04, GT_LF06, GT_TC01, GT_TC02

Functional Identifier: 2.3Function Name: Board PassengersDescription: Operations for moving passengers onto the space transport in an orderly and safe fashion Data Requirement: NilTraceability: STU_CC04, STU_CC05

Functional Identifier: 2.4Function Name: Perform Failure AnalysisDescription: Procedure and operations which are required to identify and remedy faulty components of the system. Data Requirement: A decision to abort shall be made at this stage based on the seriousness of the problem discovered. An “abort mission” data trigger will be issued if deemed necessaryTraceability: GT_LF04, GT_CFO3

Functional Identifier: 2.5Function Name: Prepare for LaunchDescription: Describes procedures and operations which are necessary to prepare the space transport for launch and space operations. Data Requirement: A “system functional” data trigger shall be issued if both ground and space systems are found to be in prime conditionTraceability: GT_LF01, GT_LF02

Functional Identifier: 2.6Function Name: Abort OperationDescription: Describes the procedure for evacuating passengers from the launch site and other necessary evacuation and maintenance operationsData Requirement: NilTraceability: GT_CF03

68

1.2. Perform Pre-Launch OperationFunctional Flow Block Diagram: Perform Pre-Launch Operations (3rd Level)

69

Hierarchical Breakdown – Perform Pre-Launch Operation

Functional Block Analysis – Perform Pre-Launch Operations

Functional Identifier: 2.2.1Function Name: Check Communication EquipmentDescription: Describes the operations necessary to verify the condition of communication equipments onboard the space transportData Requirement: NilTraceability: GT_LF04

Functional Identifier: 2.2.2Function Name: Check Maintenance LogDescription: Describes the operations for verifying maintenance log of the space transportData Requirement: NilTraceability: GT_LF04

Functional Identifier: 2.2.3Function Name: Check Mission Control EquipmentDescription: Describes the operations necessary to for verifying the condition of mission control equipments onboard the space transport currently prepared for launchData Requirement: NilTraceability: GT_LF04

Functional Identifier: 2.2.4Function Name: Check Space TransportDescription: Describes the operations necessary for verifying the physical condition of the space transport which is being prepared for launch.Data Requirement: NilTraceability: GT_LF04

70

1.3. Perform Failure Analysis

Hierarchical Breakdown – Perform Failure Analysis

Functional Flow Block Diagram: Perform Failure Analysis (3rd Level)

71

Functional Block Analysis – Perform Failure AnalysisFunctional Identifier: 2.4.1Function Name: Initial Fault AssessmentDescription: Describes the process of identifying and classifying the kind of fault detected. These operations performed will determine if the launch shall be aborted.Data Requirement: NilTraceability: GT_LF04

Functional Identifier: 2.4.2Function Name: Perform Minor RepairsDescription: Describes the process of performing basic level maintenance on the space transport.Data Requirement: NilTraceability: GT_LF04

Functional Identifier: 2.4.3Function Name: Retire System for MaintenanceDescription: Describes the process of removing the space transport from the launch area and the operations necessary for resolving the problem.Data Requirement: NilTraceability: GT_LF04

1.4. Perform Space Operation

Hierarchical Breakdown – Perform Space Operation

72

Functional Flow Block Diagram: Perform Space Operation (2nd Level)

73

Functional Block Analysis – Perform Space Operation

Functional Identifier: 3.1Function Name: Check Passengers’ SafetyDescription: Describes operations necessary to ensure safety of passengers onboard space transport.Data Requirement: NilTraceability: STU_SC01, STU_SC02

Functional Identifier: 3.2Function Name: Launch Space TransportDescription: Describes operations required for the space transport to lift off.Data Requirement: NilTraceability: STU_OC01, STU_CC01, STU_CC02, STU_CEC23, STU_OC09

Functional Identifier: 3.3Function Name: Flight to SpaceDescription: Describes operations required for navigating and controlling the space transport during flight.Data Requirement: NilTraceability: STU_OC01, STU_OC10, STU_OC11, STU_12, STU_CC01, STU_CC02, STU_CEC23, STU_OC07, STU_OC10, STU_OC11,

Functional Identifier: 3.4Function Name: Space FlightDescription: Describes operations required for navigating and controlling the space transport in space.Data Requirement: NilTraceability: STU_CC01, STU_CC02, STUCEC23, STU_OC04, STU_OC07, STU_OC10, STU_OC11,

Functional Identifier: 3.5Function Name: Return to GroundDescription: Describes operations required from bring the space transport back to ground from space. Data Requirement: NilTraceability: STU_OC02, STU_OC03, STU_OC09, STU_OC07, STU_OC10, STU_OC11,

Functional Identifier: 3.6Function Name: Perform Emergency ProceduresDescription: Describes procedures for evacuating passengers from the space transport in the event of an emergency.Data Requirement: Emergency procedures are performed only when instructed by either the mission control or when a problem is detected by systems onboard the space transport. This is illustrated in the Functional Flow by the “Initiate Emergency Procedure” data trigger.Traceability: STU_MR04, STU_SC04, STU_SC05, STU_SC06

Functional Identifier: 3.7Function Name: Communicate with Mission ControlDescription: Describes operations for communicating with Mission Control. Data Requirement: Receives important information from Mission Control including instruction to initiate emergency operations. This is signified by the “Abort Mission” Data trigger in the Functional Flow diagramTraceability: STU_OC05, STU_OC06

74

Functional Identifier: 3.8Function Name: Perform onboard System AnalysisDescription: Describes operations necessary for determining the functionality of the space transport’s systems during the course of the space operationData Requirement: Instructs the space transport to enter emergency mode when critical system error or fault has been detected. This is represented in the Functional Flow diagram by the “Initiate Emergency Procedure” data trigger.Traceability: STU_OC08,

Functional Identifier: 3.9Function Name: Regulate Internal AtmosphereDescription: Describes operations necessary regulating the atmosphere onboard the space transportData Requirement: Nil.Traceability: STU_CEC09, STU_CEC10, STU_CEC11. STU_CEC12, STU_CEC13, STU_CEC14, STU_CEC15 STU_CEC16, STU_CEC17, STU_OC12

1.5. Launch Space Transport

Hierarchical Breakdown – Launch Space Transport

75

Functional Flow Block Diagram: Launch Space Transport (3rd Level)

Functional Block Analysis – Launch Space Transport

Functional Identifier: 3.2.1Function Name: Pre-Startup InspectionDescription: Describes operations for inspecting physical functional of the space transport prior to launchingData Requirement: NilTraceability: STU_OC09

Functional Identifier: 3.2.2Function Name: Startup Space TransportDescription: Describes operations starting up space transport’s systemsData Requirement: NilTraceability: STU_OC01, STU_OC02

Functional Identifier: 3.2.3Function Name: Perform Launch SequenceDescription: Describes operations for lifting of the space transport from the groundData Requirement: NilTraceability: STU_OC01, STU_OC02

76

1.6. Perform Retrieval Operation

Hierarchical Breakdown – Perform Retrieval Operation

Functional Flow Block Diagram: Perform Retrieval Operation (2nd Level)

77

Functional Block Analysis – Perform Retrieval Operation

Functional Identifier: 4.1Function Name: Locate Space TransportDescription: Describes operations for locating the space transportData Requirement: NilTraceability:

Functional Identifier: 4.2Function Name: Initiate Space RetrievalDescription: Describes operations for retrieving a shuttle, and its passengers, which is diagnosed as unsafe for re-entering of earth’s atmosphere.Data Requirement: NilTraceability:

Functional Identifier: 4.3Function Name: Initiate Lad RetrievalDescription: Describes operations for bring passengers and the space transport which has landed on the ground back to the ground terminalData Requirement: NilTraceability:

Functional Identifier: 4.4Function Name: Initiate Sea RetrievalDescription: Describes operations for bring passengers and the space transport which has landed on water back to the ground terminalData Requirement: NilTraceability:

1.7. Perform Mission Control

Hierarchical Breakdown – Perform Mission Control

78

Functional Flow Block Diagram: Perform Mission Control (2nd Level)

79

Functional Block Analysis – Perform Mission Control

Functional Identifier: 5.1Function Name: Check Air TrafficDescription: Describes operations required for ensuring the airspace is cleared of traffic before commencing launch sequenceData Requirement: NilTraceability: GT_CS06,

Functional Identifier: 5.2Function Name: Check Weather ConditionDescription: Describes operations required for ensuring weather condition in along the flight path of the space transport is within limits for the space operationData Requirement: NilTraceability: GT_CF07

Functional Identifier: 5.3Function Name: Check Flight PathDescription: Describes operations required for ensuring the flight path provided to the space transport is correct and up to dateData Requirement: NilTraceability: GT_CS06

Functional Identifier: 5.4Function Name: Check Telemetry SystemDescription: Describes operations required for ensuring the telemetry system is operational prior to the launchData Requirement: NilTraceability: GT_CF04, GT_CF03

Functional Identifier: 5.5Function Name: Check Solar ActivityDescription: Describes operations required for ensuring solar activity is within acceptable limits prior to launchData Requirement: NilTraceability:

Functional Identifier: 5.6Function Name: Check Communication LinkDescription: Describes operations required for ensuring the communication link between the space transport and mission control is operationalData Requirement: NilTraceability: GT_CF04, GT_CF03, GT_CF07

Functional Identifier: 5.7Function Name: Monitor Space TransportDescription: Describes operations for monitoring the telemetry and operation of the space transport through out the course of the space operation Data Requirement: The mission control is responsible for aborting the operation when an abnormally or fault has be identified in the telemetry of the space transport. This is illustrate in the Functional flow diagram by the Abort mission data trigger Traceability: GT_CF02, GT_CF03, GT_CF04

80

Functional Identifier: 5.8Function Name: Initiate Emergency ProceduresDescription: Describes operations and procedures which are to be performed in the event of an emergency Data Requirement: Issues an “Initiate Emergency Procedure” data trigger to inform the space transport’s system to enter emergency mode. Traceability: GT_CF03, GT_CF08

Functional Identifier: 5.9Function Name: Start Retrieval OperationDescription: Describes operations for retrieving the space transport from space Data Requirement: The mission control is responsible for coordinating the return of the space transport from space to the ground terminal. This is signified by the “Start Retrieval Operation” data trigger in the functional flow diagram Traceability:

1.8. Perform Maintenance Operation

Hierarchical Breakdown – Perform Maintenance Operation

81

Functional Flow Block Diagram: Perform Maintenance Operation (2nd Level)

82

Functional Block Analysis – Perform Maintenance Operation

Functional Identifier: 6.1Function Name: Check Maintenance LogsDescription: Describes procedure for checking maintenance logs of equipments and systemsData Requirement: NilTraceability: GT_MC01, GT_MC07

Functional Identifier: 6.2Function Name: Perform Space Transport AssessmentDescription: Describes operations necessary for identifying the maintenances required by space transportsData Requirement: NilTraceability: GT_MC01, GT_MC02, GT_MC03

Functional Identifier: 6.2Function Name: Maintain Space TransportDescription: Describes operations for maintenance of space transportsData Requirement: NilTraceability: GT_MC01, GT_MC02, GT_MC03

Functional Identifier: 6.4Function Name: Perform Mission Control AssessmentDescription: Describes operations necessary for identifying the maintenance required by mission control’s equipments and systems Data Requirement: NilTraceability: GT_MC07, GT_MC08, GT_MC09

Functional Identifier: 6.5Function Name: Maintain Mission ControlDescription: Describes Operations for maintenance of mission control’s equipment and systemsData Requirement: NilTraceability: GT_MC07, GT_MC08, GT_MC09

Functional Identifier: 6.6Function Name: Perform Ground Terminal AssessmentsDescription: Describes operations necessary for identifying maintenance required my ground terminal’s equipments and systemsData Requirement: NilTraceability: GT_MC07, GT_MC08, GT_MC09

Functional Identifier: 6.6Function Name: Perform Ground Terminal MaintenanceDescription: Describes operations for maintenance of ground terminal’s equipment and systemsData Requirement: NilTraceability: GT_MC07, GT_MC08, GT_MC09

83

1.8. Disposal SystemFunctional Flow Block Diagram: Disposal System (2nd Level)

84

Hierarchical Breakdown – Disposal System

Functional Block Analysis – Disposal System

Functional Identifier: 7.1Function Name: Separate Recyclable ComponentDescription: Describes operations for separating recyclable components from other discarded wastesData Requirement: NilTraceability: GT_DC01, GT_DC02

Functional Identifier: 7.2Function Name: Store or Sell Recyclable ComponentsDescription: Describes operations for storing or sales of recyclable componentsData Requirement: NilTraceability: GT_DC01, GT_DC02

Functional Identifier: 7.3Function Name: Recycle Components AccordinglyDescription: Describes operations for Recycling of recyclable components in accordance to government laws and regulationsData Requirement: NilTraceability: GT_DC01, GT_DC02

Functional Identifier: 7.4Function Name: Separate Non-recyclable ComponentDescription: Describes operations for separating non-recyclable components from other discarded wastesData Requirement: NilTraceability: GT_DC01, GT_DC02

85

Functional Identifier: 7.5Function Name: Dispose off According to Government RegulationsDescription: Describes operations for disposing both non-recyclable and hazardous wastesData Requirement: NilTraceability: GT_DC01, GT_DC02

Functional Identifier: 7.6Function Name: Separate Hazard ComponentDescription: Describes operations for separating hazardous components from other discarded wastesData Requirement: NilTraceability: GT_DC01, GT_DC02

86

2.0. Joyride System Hierarchy (Top Level Breakdown)

2.1. Subsystem Breakdown of Ground Facility

87

Subsystem Description – Ground Facility

Sub-system Identifier: 1.0Subsystem: Ground FacilityDescription: Facility and equipment which are based on the ground for supporting space operationsPerforms: Functions 2.0, 4.0, 5.0, 6.0 and 7.0

Sub-system Identifier: 1.1Subsystem: Customer Service SubsystemDescription: Facility and equipment meant for tending to the customers’ needsPerforms: Functions 2.0, 2.1, 2.3

Sub-system Identifier: 1.2Subsystem: Disposal Sub-systemDescription: Facility and equipment for disposing of waste materials and faulty equipment componentsPerforms: Functions 7.0

Sub-system Identifier: 1.3Subsystem: Launch Sub-systemDescription: Facility and equipment for Lunching space transport into spacePerforms: Functions 2.0

Sub-system Identifier: 1.4Subsystem: Maintenance Sub-systemDescription: Facility and equipment used in maintaining both the ground terminal and space transportsPerforms: Functions 6.0

Sub-system Identifier: 1.5Subsystem: Mission Control Sub-systemDescription: Facility and equipment used in coordinating and monitoring of all space operationsPerforms: Functions 4.0, 5.0

88

2.2. Subsystem Breakdown of Customer Service Subsystem

Subsystem Description – Customer Service

Sub-system Identifier: 1.1.1Subsystem: Boarding SubsystemDescription: Facility and equipment for passengers to board the space transportPerforms: Functions 2.3

Sub-system Identifier: 1.1.2Subsystem: Entertainment SubsystemDescription: Facility and equipment for passengers to board the space transportPerforms: Functions 2.1

Sub-system Identifier: 1.1.3Subsystem: Food and Beverages SubsystemDescription: Facility and equipment for Customers and staff with food and beverages Performs: Functions 2.1

Sub-system Identifier: 1.1.4Subsystem: Sanitary SubsystemDescription: Facility and equipment catering to the sanitary needs of both customers and staffPerforms: Functions 2.1

Sub-system Identifier: 1.1.5Subsystem: Security SubsystemDescription: Facility and equipment employed in the ground terminals to provide security servicesPerforms: Functions 2.1

Sub-system Identifier: 1.1.6Subsystem: Ticketing SubsystemDescription: Facility and equipment for validation and sales of tickets to customersPerforms: Functions 2.1

89

2.3. Subsystem Breakdown of Maintenance Facility

built from built from

1.4

MaintenanceSubsystem

Component

1.4.1

ServicingSubsystem

Component

1.4.2

StorageSubsystem

Component

Date:Thursday, 27 October 2005

Author:Academic User

Number:1.4

Name:(Academic) Maintenance Subsystem

Subsystem Description – Maintenance Facility

Sub-system Identifier: 1.4.1Subsystem: Servicing SubsystemDescription: Facility and equipment for servicing both ground terminal and space transportsPerforms: Functions 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 6.7

Sub-system Identifier: 1.4.2Subsystem: Storage SubsystemDescription: Facility and equipment for storing support equipment as well as space transport unitsPerforms: Functions 6.0

90

2.4. Subsystem Breakdown of Mission Control System

Subsystem Description – Mission Control System

Sub-system Identifier: 1.5.1Subsystem: Flight Control SubsystemDescription: Facility and equipment to allow remote controlling of space transport from ground terminal in the event of an emergencyPerforms: Functions 5.8

Sub-system Identifier: 1.5.2Subsystem: Ground Communication SubsystemDescription: Facility and equipment for communicating with the space transport from the groundPerforms: Functions 5.6, 5.7, 5.8, 5.9

Sub-system Identifier: 1.5.3Subsystem: Radar SubsystemDescription: Facility and equipment for monitoring weather, solar and air traffic within the operation areaPerforms: Functions 5.1, 5.2, 5.3, 5.4, 5.5

91

2.5. Subsystem Breakdown of Space Vehicle

Subsystem Description – Space Vehicle

Sub-system Identifier: 2.0Subsystem: Space VehicleDescription: Vehicle for bringing passengers to spacePerforms: Functions 3.0

Sub-system Identifier: 2.1Subsystem: Customer Support SubsystemDescription: Equipment catering to the needs of customers in flightPerforms: Functions 3.0, 2.1

Sub-system Identifier: 2.2Subsystem: Life Support SubsystemDescription: Facility and equipment for maintaining a life sustainable atmosphere in the space transport during operationPerforms: Functions 3.9

Sub-system Identifier: 2.3Subsystem: Shuttle Control SubsystemDescription: Facility and equipment for controlling of space transportPerforms: Functions 3.2, 3.3, 3.4, 3.5, 3.6

92

2.6 Subsystem Breakdown of Life Support Subsystem

Subsystem Description – Life Support Subsystem

Sub-system Identifier: 2.2.1Subsystem: Atmosphere Regulation SubsystemDescription: Equipment for maintaining breathable atmosphere within the space transportPerforms: Functions 3.9

Sub-system Identifier: 2.2.2.Subsystem: Pressure Control SubsystemDescription: Equipment for maintaining the pressure within the space transportPerforms: Functions 3.9

Sub-system Identifier: 2.2.2Subsystem: Temperature Control SubsystemDescription: Equipment maintaining the internal temperature of the space transportPerforms: Functions 3.9

93

2.7 Subsystem Breakdown of Shuttle Control Subsystem

Subsystem Description – Shuttle Control Subsystem

Sub-system Identifier: 2.3.1Subsystem: Flight SubsystemDescription: Equipment for controlling the space transport during its flightPerforms: Functions 3.2, 3.3, 3.4, 3.5

Sub-system Identifier: 2.3.2Subsystem: Space Communication SubsystemDescription: Equipment for maintaining communication with ground terminal from space transportPerforms: Functions 3.2, 3.3, 3.4, 3.5

94

2.8 Subsystem Breakdown of Life Support Subsystem

Subsystem Description – Life Support Subsystem

Sub-system Identifier: 2.3.1.1Subsystem: Navigation SubsystemDescription: Equipment for navigating the space transport during its flightPerforms: Functions 3.2, 3.3, 3.4, 3.5

Sub-system Identifier: 2.3.4Subsystem: Propulsion SubsystemDescription: Equipment for driving the space transport during its flightPerforms: Functions 3.2, 3.3, 3.4, 3.5

95





Joyride to Space

System Test PlanVersion 1.1

96

System Test Plan Contents

1. Scope.................................................................................................................................981.1. Document Overview.........................................................................................981.2. Privacy Statement.............................................................................................98

2. Definitions of keywords....................................................................................................983. Test Identification.............................................................................................................99

3.1 General Information...........................................................................................993.1.1. Objectives...................................................................................................................993.1.2. Test Levels................................................................................................................1003.1.2. Resources Required..................................................................................................100

3.2.1. GROUND TERMINAL...............................................................................1023.2.1.1. Customer Service.............................................................................................1023.2.1.2. Training Capability..........................................................................................1043.2.1.3. Launch Capability............................................................................................1053.2.1.4. Control Capability............................................................................................1073.2.1.5. Storage Capability............................................................................................1103.2.1.5. Maintenance Capability...................................................................................1133.2.1.6. Geographical Location.....................................................................................1153.2.1.7. Regulations......................................................................................................1153.2.1.8. Security Capability...........................................................................................1173.2.1.9. Disposal Capability..........................................................................................1193.2.1.10. General Capability.........................................................................................1193.2.2. SPACE TRANSPORT UNIT...................................................................................1203.2.2.1. Carrying Capability..........................................................................................1203.2.2.2. Safety Capability..............................................................................................1213.2.2.3. Comfort & Entertainment Capability...............................................................1233.2.2.4. Operational Capability.....................................................................................1273.2.2.5. Security Capability...........................................................................................1313.2.2.6. Maintenance Capability...................................................................................1323.2.2.7. Regulations......................................................................................................133

97

1. Scope

1.1. Document OverviewThis document outlines the testing procedures which will be used for checking the design of the new Joyride to Space system. This helps to ensure the final design meets the requirements, which are being laid out in the Requirement Specification document and ultimately the needs of the customer, which in this case happens to be the SeaLink. In the sections that follow, we have listed out resources which will be employed for testing of the new system.

1.2. Privacy StatementThis document is for use with the SeaLink Space Tour project only; no other persons shall view this material, for security and privacy purposes.

2. Definitions of keywordsAcronyms

MTBF: Mean time between failures refers to the average duration between failures.

MTBM: Mean time between maintenance.

MTBR: Mean time between repairs.

Foot Candle: A measurement unit for illumination levels. 1 foot candle is equivalent to the amount of light provided by a single candle at a distance of 1 foot.

Pa: Pascal. It is a unit for measuring pressure. 1Pa is equivalent to 1 Newton per square meter

Maintenance Levels Definition:

Basic maintenance – refers to the maintenance which can be carried out on site without the need for specialised equipment by personnel with low maintenance skills, such as system operator. The maintenance tasks included in this level of maintenance are as follows:

6. Visual inspection of system.7. Operational check of system.8. Minor servicing.9. Adjustment, removal and replacement of non critical system components.10. Cleaning and washing of system or device.

98

Intermediate maintenance – Refers to the maintenance tasks which needs to be performed by maintenance personnel with intermediate maintenance skills. These maintenance tasks can usually be performed on site while in the presence of mobile maintenance units, such as a repair truck or van. Otherwise, these maintenance tasks will need to be performed at a specialised repair facility. The tasks included in this level of maintenance are as follows:

7. Detail inspection and system checkout.8. Major servicing.9. Major equipment repair and modification.10. Complicated adjustments.11. Limited calibration.12. Any overload from the basic maintenance level.

Advance maintenance – Refers to the maintenance tasks which needs to be performed by maintenance personnel with high skill level in a specialised maintenance depot or with the use of specialised tools. The tasks included in this level of maintenance are listed below:

6. Complicated adjustments of critical components.7. Complex equipment repairs and modifications.8. Overhaul and rebuild of equipment.9. Detail calibration of system.10. Overload maintenance tasks from intermediate maintenance level.

3. Test Identification

3.1 General Information

3.1.1. Objectives

This Test plan for the Joyride to Space Project supports the following objectives:

Identify existing project information and the components that needs to be performed in the systems level

Lies the recommended Test Requirements Recommend and describe the testing strategies to be employed Identify the required resources

99

3.1.2. Test Levels

There are 3 main sets of tests, which have to be carried out. The tests specified in section 3.2 of this document are designed for the alpha testing stages but can be merged into the other tests stages with slight modifications. Shown below are the different sets of tests3.2 Test Detail Specifications.

1. Development Test and Evaluation (α-testing): These sets of tests are designed to aid design and development process. Tests in this section are broken into System , Subsystem levels and Component level tests.

Component Level Testing: This describes tests which have to be done on the individual components which combined to make up the subsystems of the Joyride system. This level of testing is not describe in these sets of document

Subsystem Level Testing: This describes tests which are performed to access the functionality of the individual subsystems as specified in the subsystem requirements.

System Level Testing: This set of tests is targeted at the emergent properties of the different subsystem, which can only be tested when all its respective components have been interfaced together. There are also several testes designed to test the Joyride to Space system as a whole

2. Operational Tests and Evaluation (β-testing): These set of tests are conducted in the actual field conditions which the system is suppose to be operating in. The tests have been designed for ensuring that the final product carries out the intended functions and fulfils the requirements.

3. User Acceptance Testing: Final test before the end product is handed over to the customer. These tests are designed for the customer to verify the functions and characteristic meets the contract specification.

3.1.2. Resources Required

Outlined in this section of the test plan are the minimum recommended staffing requirements necessary for smooth operation of the Test and Evaluation Process. The number of personnel required, their skill level and the respective responsibility of the posts are specified below.

Staff: Test ManagerNumber required: 01Skill Level: High Management and Engineering SkillResponsibility:

Provide technical directions Acquire appropriate resources Management of Test Program Management reporting

100

Staff: Test DesignerNumber required: 08 Skill Level: Highly skilled in engineering fieldsResponsibility:

Generate test plan Generate test model Evaluate effectiveness of test effort

Staff: TesterNumber required: 200Skill Level: Average skilled personnelResponsibility:

Executes tests Log test results Document defects

Staff: Test supervisorNumber required: 04Skill Level: Highly skilled in administrative fields Responsibility:

Administer test management system Maintains test environment

101

3.2.1. GROUND TERMINAL

3.2.1.1. Customer Service

Level: System System Tested: Ground TerminalIdentifier of Test: T-CUS 01Test objective: To ensure the Ground Terminal is able to accommodate at least 250 people.Identifier of Requirement Tested: GT_CS01Verification Method: AnalysisData Input:

Blueprints of ground terminal Statistical data on building sizes and capacity

Expected Condition: The blueprints of the ground terminal indicate a capacity of 250 or more people.

Level: System System Tested: Ground TerminalIdentifier of Test: T-CUS 02Test objective: To ensure the ground terminal is capable of servicing 200 or more customers in under 2 hours.Identifier of Requirement Tested: GT_CS02, GT_CUS03Verification Method: AnalysisData Input:

Number of customer service counters Statistical data on rate at which customer can be served in airports Varying number of customers

Expected Condition: Analysis shows that the number of customer service counters is capable of processing 200 or more customers in a time frame of no greater than 2 hours

Level: System System Tested: Ground Terminal luggage storage systemIdentifier of Test: T-CUS 04Test objective: Ensure ground terminal has enough luggage storage space for 200 patrons with luggage of less than 0.4m cube.Identifier of Requirement Tested: GT-CUS04Verification Method: AnalysisData Input:

Blueprints of baggage storage area Design of storage compartments

Expected Condition: The ground terminal has sufficient storage spaces for 200 or more pieces of luggage with volume of at least 0.4 metres cube

102

Level: System System Tested: Ground Terminal Identifier of Test: T-CUS 08Test objective: That the ground terminal has vehicle parking area for patronsIdentifier of Requirement Tested: GT_CS06Verification Method: AnalysisData Input:

Blueprints of ground terminal Expected Condition: At least one parking facility has been allocated in the design of the ground terminal

Level: System System Tested: Ground Terminal Car ParkIdentifier of Test: T-CUS 09Test objective: Ensure the parking lots are of adequate sizesIdentifier of Requirement Tested: GT_CS07Verification Method: AnalysisData Input:

Blue Prints of Ground Terminal Car ParkExpected Condition: Ground Terminal Car Park Blue Prints can accommodate at least 250 class C vehicles

Level: System System Tested: Ground Terminal Identifier of Test: T-CUS 10Test objective: Ground terminal can provide no less than 300 meals per dayIdentifier of Requirement Tested: GT_CS08Verification Method: AnalysisData Input:

Statistical output of food and beverages facility in the ground terminal.Expected Condition: Combined output of all food and beverages facility reaches at least 300 meals per day.

Level: System System Tested: Ground TerminalIdentifier of Test: T-CUS 11Test objective: Ensure ground terminal is capable of providing internet access for patronsIdentifier of Requirement Tested: GT_CS09Verification Method: AnalysisData Input:

Statistical data on duration of internet usage by customers in airports Model of internet traffic generated from usage data Number of access points available in the ground terminal

Expected Condition: The number of internet access points should be capable of supporting 200 users based on the analytical modelling of the internet traffic from customer usage

103

Level: System System Tested: Ground TerminalIdentifier of Test: T-CUS12Test objective: Ensure ground terminal can provide telephone service for 200 peopleIdentifier of Requirement Tested: GT_CS10Verification Method: AnalysisData Input:

Statistical data on duration of public phone usage by customers in airports

Model of voice traffic generated from usage data Number of public phones available in the ground terminal

Expected Condition: The number of public phones should be capable of supporting 200 users based on the analytical modelling of the voice traffic from customer usage

Level: System System Tested: Ground TerminalIdentifier of Test: T-CUS13Test objective: Ensure Ground Terminal has sanitary services for 200 people.Identifier of Requirement Tested: GT_CS11Verification Method: AnalysisData Input:

Statistical data usage of public sanitary facility in airports Model of sanitary facility usage Number of Ground Terminal sanitary facility

Expected Condition: The number of sanitary facilities provided in the ground terminal is equivalent or more than the amount required in theoretical analysis

3.2.1.2. Training Capability

level: System System Tested: Ground Terminal Training facilityIdentifier of Test: T-TRC01Test objective: Ensure Ground terminal can provide training for 200 people.Identifier of Requirement Tested: GT_TC01Verification Method: AnalysisData Input:

Blueprints of Ground Terminal training facilities Expected Condition: The size of the training facility is adequate for accommodating 200 personnel

104

level: System System Tested: Ground Terminal Briefing RoomIdentifier of Test: T-TRC02Test objective: Ensure Ground terminal can provide pre launch briefing for no less than 200 people..Identifier of Requirement Tested: GT_TC02Verification Method: AnalysisData Input:

Blueprints of Ground Terminal briefing facility Expected Condition: Briefing Facility is large enough to accommodate 200 personnel

3.2.1.3. Launch Capability

level: System System Tested: Launch FacilityIdentifier of Test: T-LAC 01Test objective: Ensure Ground terminal can perform space transport unit launch sequence. Identifier of Requirement Tested: GT_LF01Verification Method: SimulationData Input:

Simulate launch sequence for space transportsExpected Condition: Launch Facility performs all functions and procedures required in the launch sequence

level: System System Tested: Launch FacilityIdentifier of Test: T-LAC 02Test objective: Ensure Ground terminal can launch at least 1 space transport unit. Identifier of Requirement Tested: GT_LF02Verification Method: SimulationData Input:

Simulate launch sequence for space transports Varying number space transport in simulation

Expected Condition: Launch sequence is capable of performing launch sequence for at least 1 space transport

level: System System Tested: Launch FacilityIdentifier of Test: T-LAC03Test objective: Ensure Launching sequences can be repeated at in at most 48 hoursIdentifier of Requirement Tested: GT_LF03Verification Method: AnalysisData Input:

Time required for performing launch preparations and pre-launch maintenance.

Expected Condition: Launch sequences can be repeated in at most 48 hours

level: System System Tested: Maintenance systemIdentifier of Test: T-LAC04

105

Test objective: Ensure pre-launch maintenance can be performed on space transport units in launch facility. Identifier of Requirement Tested: GT_LF04Verification Method: DemonstrationData Input:

Space transport unit Request for pre-launch maintenance Skilled maintenance personnel

Expected Condition: The launch facility has all necessary equipment necessary for performing pre-launch maintenance on space transport units

level: System System Tested: Maintenance systemIdentifier of Test: T-LAC05Test objective: Ensure Ground Terminal is capable of completing pre-launch maintenance under 24 hrs. Identifier of Requirement Tested: GT_LF05Verification Method: DemonstrationData Input:

Space transport unit Request for pre-launch maintenance Skilled maintenance personnel

Expected Condition: All pre-launch maintenance is conducted within 24 hrs

level: System System Tested: Refilling systemIdentifier of Test: T-LAC 06Test objective: Ensure Space Transport can be refilled in premises of the ground terminal. Identifier of Requirement Tested: GT_LF06Verification Method: DemonstrationData Input:

Space Transport Unit Request for space transport unit to be refilled

Expected Condition: Refilling of space transport unit can be performed in the premises of the ground terminal

106

3.2.1.4. Control Capability

level: System System Tested: Launch ControlIdentifier of Test: S-OPC 02Test objective: Ensure Ground terminal is capable of initiating a launch sequence. Identifier of Requirement Tested: GT_CF01Verification Method: SimulationData Input:

Launch control facility Issue command for staring launch sequence from ground station

Expected Condition: Launch sequence is initiated upon command

Level: System System Tested: Mission Control SystemIdentifier of Test: T-LAC01Test objective: Test if launch monitoring system can monitor all Space Transport Units being launched.Identifier of Requirement Tested: GT_CF02Verification Method: SimulationData Input:

Varying number of Space Transport Units simulated Start launch sequence Vary conditions and functions of systems on board space transports

Expected Condition: Mission control is capable of recording all changes made to the conditions and functions in the systems of all space transports tested.

Level: System System Tested: Mission Control SystemIdentifier of Test: T-LAC02Test objective: Ensure Mission control can stop Space Transport Units from launching.Identifier of Requirement Tested: GT_CF03Verification Method: SimulationData Input:

Initiate Launch Sequence Issue command for aborting launch

Expected Condition: Launch sequence is aborted

107

Level: System System Tested: Mission Control System Identifier of Test: T-COC01Test objective: Test if telemetry data sent from operating Space Transport Units can be monitored by staff at the ground terminal.Identifier of Requirement Tested: GT_CF04Verification Method: DemonstrationData Input:

Space Transport Units Vary conditions of systems onboard space transport unit Increase number of space transport units in test

Expected Condition: Telemetry data on systems of all space transports under test is recorded and displayed in a form readable by the operator

Level: System System Tested: Weather monitoring system Identifier of Test: T-COC02Test objective: Ensure Ground Terminal weather monitoring station has a range greater than 250km Identifier of Requirement Tested: GT_CF05Verification Method: DemonstrationData Input:

Operate weather monitoring system for 36 hours

Expected Condition: Variations in weather conditions in a radius of 250km or more from the ground terminal is reflected in the weather monitoring system

Level: System System Tested: Air traffic monitoring system Identifier of Test: T-COC03Test objective: Ensure Ground Terminals air traffic monitoring system has range that is greater than 250km.Identifier of Requirement Tested: GT_CF06Verification Method: DemonstrationData Input:

Operate air traffic monitoring system for 36 hours

Expected Condition: Variations in air traffic conditions in a radius of 250km or more from the ground terminal is recorded in the air traffic monitoring system

108

Level: System System Tested: Mission Control System Identifier of Test: T-COC04Test objective: Ensure Ground Terminal can communicate with all operating Space Transport units.Identifier of Requirement Tested: GT_CF07Verification Method: DemonstrationData Input:

Operating space transport unit Exchange voice and data between space transport and Mission Control

System Increase the number of space transport unit under test

Expected Condition: All voice and data exchanged are received correctly

Level: System System Tested: Mission Control System Identifier of Test: T-COC04Test objective: Ensure the ground terminal is capable of aborting a mission in progressIdentifier of Requirement Tested: GT_CF08Verification Method: SimulationData Input:

Simulate launch and flight of space transport Issue of abort command at different phases of the mission

Expected Condition: Current mission of the space transport unit is aborted

Level: System System Tested: Mission Control System Identifier of Test: T-COC04Test objective: Ensure Ground Terminal can coordinate retrieval of passengersIdentifier of Requirement Tested: GT_CF09Verification Method: SimulationData Input:

Simulate scenarios for which retrieval of passengers is required to take place

Expected Condition: Mission control system is capable of coordinating the retrieval of passengers in all the scenarios tested

109

3.2.1.5. Storage Capability

Level: System System Tested: Ground TerminalIdentifier of Test: T-STC01Test objective: Ensure Ground Terminal can store 5 or more Space Transport Units.Identifier of Requirement Tested: GT_SC01Verification Method: AnalysisData Input:

Layout of ground terminal Blueprints of Space transport unit’s storage facility Blueprints of space transport unit’s design

Expected Condition: Sufficient storage space is allocated for the storage of no less than 5 space transport units on the ground terminal

Level: System System Tested: Space Transport Unit storageIdentifier of Test: T-STC02Test objective: Ensure ground terminal’s Space Transport Unit storage area exposes the Space Transport Units to no less than the predefined amount of heat.Identifier of Requirement Tested: GT_SC02Verification Method: DemonstrationData Input:

Light meter

Expected Condition: Temperature recorded in the hanger is less than the predefined temperature

Level: System System Tested: Space Transport Unit storageIdentifier of Test: T-STC03Test objective: Ensure Ground Terminal’s Space Transport Unit storage area exposes the Space Transport Units to wind velocities greater than 10kph.Identifier of Requirement Tested: GT_SC03Verification Method: DemonstrationData Input:

Wind speed meterExpected Condition: Wind speeds recorded in the space transport unit storage area is less than predefined values

110

Level: System System Tested: Space Transport Unit storageIdentifier of Test: T-STC04Test objective: Ensure Ground Terminal’s Space Transport Unit storage area exposes the Space Transport Units to rain.Identifier of Requirement Tested: GT_SC04Verification Method: DemonstrationData Input:

Rain gaugeExpected Condition: Confirmation that the Space Transport Units in the storage area are not exposed to rain

Level: System System Tested: Space Transport Unit storage security systemIdentifier of Test: T-SEC01Test objective: Test if Ground Terminal’s Space Transport Unit storage area cannot be accessed by unauthorised personnel.Identifier of Requirement Tested: GT_SC05Verification Method: DemonstrationData Input:

Attempt to access storage facility of space transport unit without proper authorisation

Expected Condition: Confirmation that the Space Transport Units in the storage area can only be accessed by authorised personnel

Level: System System Tested: Space Transport Unit equipment storage system Identifier of Test: T-STC05Test objective: Ensure Ground Terminal’s Space Transport Unit storage area has designated space for maintenance equipment storage.Identifier of Requirement Tested: GT_SC06Verification Method: AnalysisData Input:

Blueprints of ground terminalExpected Condition: Space or facility has been allocated for the storage of maintenance equipment for space transport units

Level: System System Tested: Ground Terminal storage system Identifier of Test: T-STC06Test objective: Test if Ground Terminal has a storage area for Ground Terminal maintenance equipment.Identifier of Requirement Tested: GT_SC07Verification Method: AnalysisData Input:

Blueprints of ground terminalExpected Condition: Space or facility has been allocated for storage of Ground Terminal maintenance equipment

111

Level: System System Tested: Ground Terminal storage system Identifier of Test: T-STC07Test objective: Test if Ground Terminal can store enough parts to perform 20 basic Space Transport Unit maintenance routinesIdentifier of Requirement Tested: GT_SC08Verification Method: AnalysisData Input:

Blueprints of storage systemExpected Condition: Sufficient space has been allocated for the storage of at least 20 sets of parts for basic maintenance on space transport units

Level: System System Tested: Ground Terminal storage system Identifier of Test: T-STC08Test objective: Test if Ground Terminal can store enough parts to perform 10 intermediate Space Transport Unit maintenance routinesIdentifier of Requirement Tested: GT_SC09Verification Method: AnalysisData Input:

Blueprints of storage systemExpected Condition: Sufficient space has been allocated for the storage of at least 10 sets of parts for intermediate maintenance on space transport units

Level: System System Tested: Ground Terminal storage system Identifier of Test: T-STC09Test objective: Test if Ground Terminal can store enough parts to perform 2 advanced Space Transport Unit maintenance routinesIdentifier of Requirement Tested: GT_SC010Verification Method: AnalysisData Input:

Blueprints of storage systemExpected Condition: Sufficient space has been allocated for the storage of at least 2 sets of parts for advance maintenance on space transport units

Level: System System Tested: Ground Terminal fuel storage system Identifier of Test: T-STC08Test objective: Test if Ground Terminal can store enough fuel to fill 20 Space Transport Units Identifier of Requirement Tested: GT_SC09Verification Method: DemonstrationData Input:

Space Transport Unit’s fuel capacityExpected Condition: Ground Terminal can store enough fuel to refill 20 Space Transport Units

112

3.2.1.5. Maintenance Capability

Level: System System Tested: Maintenance SystemIdentifier of Test: T-MAC01Test objective: Test if Ground Terminal can perform a basic maintenance routine on 5 or more Space Transport Units.Identifier of Requirement Tested: GT_MC01Verification Method: DemonstrationData Input:

Random number of Space Transport Units

Expected Condition: Confirmation that the Ground Terminal can perform 5 or more basic maintenance routines

Level: System System Tested: Maintenance System Identifier of Test: T-MAC02Test objective: Test if Ground Terminal can perform an intermediate maintenance routine on 2 or more Space Transport Units.Identifier of Requirement Tested: GT_MC02Verification Method: DemonstrationData Input:

Various number of Space Transport UnitsExpected Condition: Confirmation that the Ground Terminal can perform 2 or more intermediate maintenance routines

Level: System System Tested: Maintenance System Identifier of Test: T-MAC03Test objective: Test if Ground Terminal can perform an advanced maintenance routine on 1 or more Space Transport Units.Identifier of Requirement Tested: GT_MC03Verification Method: DemonstrationData Input:

Various number of Space Transport UnitsExpected Condition: Confirmation that the Ground Terminal can perform 1 or more advanced maintenance routines

Level: System System Tested: Ground Terminal Identifier of Test: T-MAC04Test objective: Test if Ground Terminal has a MTBF greater than 2000hrsIdentifier of Requirement Tested: GT_MC04Verification Method: AnalysisData Input:

Analysis of the systems and equipment used in the ground terminal

Expected Condition: Average time between failures of the ground terminal’s system is at most 2000 hours

113

Level: System System Tested: Ground Terminal Identifier of Test: T-MAC05Test objective: Test if Ground Terminal has a MTBM greater than 80hrsIdentifier of Requirement Tested: GT_MC05Verification Method: AnalysisData Input:


Expected Condition: Average time to maintain the ground terminal’s system is at most 80 hours

Level: System System Tested: Ground Terminal Identifier of Test: T-MAC06Test objective: Test if Ground Terminal has a MTBR greater than 50hrsIdentifier of Requirement Tested: GT_MC06Verification Method: DemonstrationData Input:


Expected Condition: Average time between repairs of the ground terminal’s system is at most 50 hours

Level: System Component Tested: Maintenance SystemIdentifier of Test: T-MAC07Test objective: Ensure Ground Terminals are capable of performing basic level maintenance on all Ground based systems.Identifier of Requirement Tested: GT_MC07Verification Method: DemonstrationData Input:

Ground TerminalExpected Condition: Basic level maintenance is done on all Ground based systems.

Level: System Component Tested: Maintenance SystemIdentifier of Test: T-MAC08Test objective: Ensure Ground terminals are capable of performing intermediate level maintenance on all Ground based systems.Identifier of Requirement Tested: GT_MC08Verification Method: DemonstrationData Input:

Ground TerminalExpected Condition: Intermediate level maintenance is done on Ground based systems.

114

Level: System Component Tested: Component Tested: Maintenance SystemIdentifier of Test: T-MAC09Test objective: Ensure Ground terminals are capable of performing advance level maintenance on all Ground based systems.Identifier of Requirement Tested: GT_MC09Verification Method: DemonstrationData Input:

Ground TerminalExpected Condition: Advance levels maintenance is done on Ground based systems.

3.2.1.6. Geographical Location

Level: System Component Tested: Ground TerminalIdentifier of Test: T-GEO01Test objective: Ensure Ground terminals are located no greater than 230km from Adelaide CBD.Identifier of Requirement Tested: GT_GL01Verification Method: DemonstrationData Input:

Ground Terminal locationExpected Condition: Ground Terminal located at least 320km from CBD.

3.2.1.7. Regulations

Level: System Component Tested: Ground TerminalIdentifier of Test: T-REG01Test objective: Ensure Ground terminals are located no greater than 230km from Adelaide CBD.Identifier of Requirement Tested: GT_GL01Verification Method: Demonstration, Analysis, Simulation Data Input:

Ground Terminal structure planExpected Condition: Ground Terminal structures conform to Building Code of Australia 2005.

Level: System Component Tested: Ground TerminalIdentifier of Test: T-REG02Test objective: Ensure any organisation participating in launch activities of space vehicles shall conform to ISO 14620-3:2005.Identifier of Requirement Tested: GT_GL02Verification Method: DemonstrationData Input:

Organisation that participate in launch activities of space vehicles.Expected Condition: Organisation that participate in launch activities of space vehicles conform to ISO 14620-3:2005 standards.

115

Level: System Component Tested: Space Transport UnitIdentifier of Test: T-REG03Test objective: Ensure cleanliness level of fluid system components and equipment used in space systems are able to conform to ISO 14952-2:2003 standards. Identifier of Requirement Tested: GT_GL03Verification Method: DemonstrationData Input:

Fluid system components and equipment used in space systemsExpected Condition: Cleanliness level of fluid system components and equipment used in space systems conform to ISO 14952-2:2003 standards.

Level: System Component Tested: Ground Terminal Communications Identifier of Test: T-REG04Test objective: Ensure communication requirement for spacecraft, radio links, tracking stations, ground communication circuits and mission control centres are able to conform to ISO 14952-2:2003 standards. Identifier of Requirement Tested: GT_GL04Verification Method: DemonstrationData Input:

Spacecraft, radio links, tracking stations, ground communication circuits and mission control centres

Expected Condition: Communication requirement for spacecraft, radio links, tracking stations, ground communication circuits and mission control centres conform to ISO 14952-2:2003 standards.

Level: System Component Tested: Launch SiteIdentifier of Test: T-REG05Test objective: Ensure Space safety requirements for launch site operations are able to conform to ISO 14620-2:2000 standards. Identifier of Requirement Tested: GT_GL05Verification Method: DemonstrationData Input:

Launch site operationExpected Condition: Space safety requirements for launch site operations conform to ISO 14620-2:2000 standards.

116

Level: System Component Tested: Ground Terminal Identifier of Test: T-REG06Test objective: Ensure Requirements and guidelines for spacecraft on-board functions are able to conform to ISO 14950:2003 standards. Identifier of Requirement Tested: GT_GL06Verification Method: DemonstrationData Input:

Control FacilityExpected Condition: Requirements and guidelines for spacecraft on-board functions conform to ISO 14950:2003 standards and enable a specified ground segment to operate the spacecraft in any nominal or predefined contingency situation. Level: System Component Tested: Joyride System Identifier of Test: T-REG06Test objective: Ensure system conforms to Civil Aviation Safety Regulations 1998 Identifier of Requirement Tested: GT_GL07Verification Method: DemonstrationData Input:

Space transport unit Ground Terminal

Expected Condition: Both ground terminal and space transports meets requirement set out in the Civil Aviation Safety Regulation 1998

3.2.1.8. Security Capability

Level: System Component Tested: Ground Terminal SecurityIdentifier of Test: T-SEC01Test objective: Ensure round terminal are capable of maintaining surveillance on all publicly accessible area. Identifier of Requirement Tested: GT_SC01Verification Method: DemonstrationData Input:

Perform surveillance on all publicly accessible areas within the ground terminal

Expected Condition: Surveillance on all publicly accessible areas is maintained.

Level: System Component Tested: Ground Terminal SecurityIdentifier of Test: T-SEC02Test objective: Ensure round terminal are capable of maintaining surveillance on all restricted areas. Identifier of Requirement Tested: GT_SC02Verification Method: DemonstrationData Input:

Perform surveillance on all restricted areas within the ground terminalExpected Condition:

117

Surveillance on restricted areas is maintained.Level: System Component Tested: Ground Terminal SecurityIdentifier of Test: T-SEC03Test objective: Ensure all restricted areas are labelled with at least 1 sign.Identifier of Requirement Tested: GT_SC03Verification Method: DemonstrationData Input:

Restricted areasExpected Condition: All restricted areas are labelled with no less than 1 sign

Level: System Component Tested: Ground Terminal SecurityIdentifier of Test: T-SEC04Test objective: Ensure Ground terminals are capable of detecting the presence of firearms on customersIdentifier of Requirement Tested: GT_SC04, GT_SC06Verification Method: DemonstrationData Input:

Attempts to bring fire arms into the ground terminal by test personnelExpected Condition: Presences of firearms on test personnel are detected.

Level: System Component Tested: Ground Terminal SecurityIdentifier of Test: T-SEC05Test objective: Ensure Ground terminals are capable of detecting the presence of explosives on customersIdentifier of Requirement Tested: GT_SC05, GT_SC07Verification Method: DemonstrationData Input:

Attempts to bring explosive into the ground terminal by test personnelExpected Condition: Presences of explosive on test personnel are detected.

Level: System Component Tested: Ground Terminal SecurityIdentifier of Test: T-SEC08Test objective: Ensure Ground terminals are capable of accommodating no less than 30 security officers.Identifier of Requirement Tested: GT_SC08Verification Method: DemonstrationData Input:

Blueprints of ground terminalExpected Condition: Allocations in the design of the ground terminal have been made to include accommodation for at least 30 security personnel

118

119

Level: System Component Tested: Ground Terminal SecurityIdentifier of Test: T-SEC09Test objective: Ensure Ground terminals are capable of maintaining no less than 48 hours worth of recording from surveillance devices.Identifier of Requirement Tested: GT_SC09Verification Method: DemonstrationData Input:

Perform surveillance for 48 hoursExpected Condition: Ground terminals maintain more than 48 hours worth of recording from surveillance devices.

3.2.1.9. Disposal Capability

Level: System Component Tested: Disposal SystemIdentifier of Test: T-DIC01Test objective: Ensure Ground terminals are capable of discarding faulty equipment.Identifier of Requirement Tested: GT_DC01Verification Method: AnalysisData Input:

Design document of disposal systemExpected Condition: Disposal system had been design for the disposal of all materials and wasted produced by the ground terminal

Level: System Component Tested: Disposal SystemIdentifier of Test: T-DIC02Test objective: Ensure Ground terminals are capable of discarding Space transport units at the end of the life cycle.Identifier of Requirement Tested: GT_DC02Verification Method: AnalysisData Input:

Space transport units Expected Condition: Ground terminals are able to discard Space transport units at the end of the life cycle.

3.2.1.10. General Capability

Level: System Component Tested: Ground Terminal SecurityIdentifier of Test: T-GEC01Test objective: Ensure Ground terminals are of no less than 1 means of starting up the systemIdentifier of Requirement Tested: GT_SC08Verification Method: DemonstrationData Input:

Issue command for initial start up of all systemsExpected Condition:

120

All systems in the system boots up

121

3.2.2. SPACE TRANSPORT UNIT

3.2.2.1. Carrying Capability

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CAC01Test objective: Ensure Space transport unit is capable of carrying no less than 20 people.Identifier of Requirement Tested: STU_CC01Verification Method: DemonstrationData Input:

Test personnelExpected Condition: Space transport unit carries more than test personnel

Level: System Component Tested: Space Transport UnitIdentifier of Test: S-CAC02Test objective: Ensure Space transport unit is capable of carrying a weight of no less than 1 tonne.Identifier of Requirement Tested: STU_CC02Verification Method: SimulationData Input:

Simulate flight of space transport unit under different load conditionsExpected Condition: Simulated space transport unit is capable of performing all flights operations for all loads under 1tonne

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CAC03Test objective: Ensure there must be a storage area for each passenger.Identifier of Requirement Tested: STU_CC03Verification Method: AnalysisData Input:

Blueprints of space transport unitExpected Condition: Baggage is fitted to the storage locker.

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CAC 04Test objective: Ensure passengers are able to enter and exit the space transport unit.Identifier of Requirement Tested: STU_CC04, STU_CC05Verification Method: DemonstrationData Input:

Test personnel enter the space transportExpected Condition: Passengers are able to enter the Space Transport unit easily

122

3.2.2.2. Safety Capability

Level: System Component Tested: Space Transport Unit Identifier of Test: S-SAC 01Test objective: Ensure there have there have no less than 1 means of securing passengers during flight.Identifier of Requirement Tested: STU_SC01Verification Method: DemonstrationData Input:

Securing of test dummy on space transport unitExpected Condition: Space transport unit have 1 or more means of securing passenger

Level: System Component Tested: Space Transport Unit Identifier of Test: S-SAC 02Test objective: Ensure there have no less than 1 means of securing passenger’s belonging during flightIdentifier of Requirement Tested: STU_SC02Verification Method: DemonstrationData Input:

Secure dummy belongings on space transport unitExpected Condition: Space transport unit have 1 or more means of securing their personal belonging

Level: System Component Tested: Space Transport Unit Identifier of Test: S-SAC 03Test objective: Ensure there have no less than 1 means of evacuating the passenger over land.Identifier of Requirement Tested: STU_SC03Verification Method: DemonstrationData Input:

Test personnel activate land evacuation mechanism.Expected Condition: There are more than 1 means of evacuating the passenger over land

Level: System Component Tested: Space Transport Unit Identifier of Test: S-SAC 04Test objective: Ensure the space transport unit have no less than 1 means of evacuating the passengers over water.Identifier of Requirement Tested: STU_SC04Verification Method: DemonstrationData Input:

Test personnel activate water evacuation mechanism.Expected Condition: There are more than 1 means of evacuating the passenger over water

123

Level: System Component Tested: Space Transport Unit Identifier of Test: S-SAC 05Test objective: Ensure space transport unit have no less than 1 means of evacuating passengers while in space.Identifier of Requirement Tested: STU_SC05Verification Method: SimulationData Input:

Simulate operations of evacuation mechanism in zero gravity conditions.Expected Condition: Simulation results indicate that all mechanisms for space evacuation are performed successfully

Level: System Component Tested: Space Transport Unit Identifier of Test: S-SAC 05Test objective: Ensure space transport unit has sufficient equipment for perform first aid on 20 passengers.Identifier of Requirement Tested: STU_SC06Verification Method: DemonstrationData Input:

First aid equipment onboard the space transport unitExpected Condition: The amount of first aid equipment is sufficient for administering first aid on 20 personnel

Level: System Component Tested: Space Transport UnitIdentifier of Test: S-SAC 07Test objective: Ensure there are no flammable objects in the space transport unit.Identifier of Requirement Tested: STU_SC07Verification Method: DemonstrationData Input:

Sample of material used in construction of the hull’s interior.Expected Condition: Material tested does not catch fire when exposed to flame

Level: System Component Tested: Space Transport Unit Identifier of Test: S-SAC 08Test objective: Test the space transport unit has no less than 5 fire extinguishersIdentifier of Requirement Tested: STU_SC08Verification Method: DemonstrationData Input:

Fire extinguisher.Expected Condition: The space transport unit has more than 5 fire extinguishers

124

Level: System Component Tested: Space Transport Unit Identifier of Test: S-SAC 09Test objective: Ensure the space transport unit have fire extinguisher which can accessible by all passengersIdentifier of Requirement Tested: STU_SC09Verification Method: DemonstrationData Input:

Fire extinguisher Test personnel

Expected Condition: All test personnel onboard space transport unit is able to access the fire extinguishers

3.2.2.3. Comfort & Entertainment Capability

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 01Test objective: Ensure the space transport unit has no less than 1 mounted video recording camera per every 4 passengers.Identifier of Requirement Tested: STU_CEC01Verification Method: DemonstrationData Input:

Locations of Mounted video recording cameraExpected Condition: 1 or more video camera is mounted between every 4 passenger seats

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 02Test objective: Ensure the space transport unit has no less than 1 information deviceIdentifier of Requirement Tested: STU_CEC02Verification Method: DemonstrationData Input:

Information deviceExpected Condition: Space transport unit have more than 1 information devices

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 03Test objective: Test the information device is accessible by all passengers. Identifier of Requirement Tested: STU_CEC03Verification Method: DemonstrationData Input:

Information devicesExpected Condition: Information devices are accessible by every passenger

125

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 04Test objective: Ensure the space transport unit has a separation of no less than 0.1 meter between every passenger.Identifier of Requirement Tested: STU_CEC04Verification Method: AnalysisData Input:

Blueprint of passenger seating arrangementExpected Condition The separation between passengers’ seats is greater than 0.1 meter

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 05Test objective: Ensure the passenger’s belonging is not greater than 1 meter from the passenger.Identifier of Requirement Tested: STU_CEC05Verification Method: DemonstrationData Input:

Baggage storage compartment. Passenger seats

Expected Condition: The baggage storage compartment is less than 1 meter away from the seats

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 06Test objective: Ensure the space transport have no less than 1 means of observing the vessel’s exterior environment for each passenger.Identifier of Requirement Tested: STU_CEC06Verification Method: DemonstrationData Input:

Test personnelExpected Condition: There have more than 1 means of observing the vessel’s exterior environment

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 07Test objective: Ensure that there have no less than 1 entertainment system for passengersIdentifier of Requirement Tested: STU_CEC07Verification Method: DemonstrationData Input:

Entertainments systemExpected Condition: Space transport unit have 1 or more entertainment system for passengers

126

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 08Test objective: Ensure entertainments are accessible by all passengers.Identifier of Requirement Tested: STU_CEC08Verification Method: DemonstrationData Input:

Test Personnel Entertainment system.

Expected Condition: Entertainment system is accessible by all test personnel onboard the space transport unit

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 09Test objective: Ensure space transport unit is capable of providing an interior illumination level between 30 and 80 foot candlesIdentifier of Requirement Tested: STU_CEC09, STUCRC10Verification Method: DemonstrationData Input:

Interior illuminationExpected Condition: Interior illumination level is more than 30 foot candles

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 10Test objective: Ensure the space transport unit have an internal humidity between 20% and 40%.Identifier of Requirement Tested: STU_CRC11, STU_ CEC12, STU_CEC13Verification Method: DemonstrationData Input:

Test personnel with humidity measuring equipment Operate atmospheric controller of space transport Change exterior humidity of the space transport within operation range

Expected Condition: The humidity of the air sample is between 20 and 40 percent regardless of the humidity present in the exterior of the space transport unit

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 11Test objective: Ensure the interior temperature of the space transport unit is between 16 and 24 degrees CelsiusIdentifier of Requirement Tested: STU_CRC11, STU_ CEC14, STU_CEC15Verification Method: DemonstrationData Input:

Test personnel with temperature measuring equipment Operate atmospheric controller of space transport Change exterior temperature of the space transport within operation

rangeExpected Condition: Interior temperature of the space transport unit is between 16 and 24 degree Celsius regardless of the humidity present in the exterior of the space transport unit

127

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 12Test objective: Ensure space transport unit’s interior pressure is between 28kPa and 32 kPa.Identifier of Requirement Tested: STU_CRC11, STU_CEC16, STU_ CEC17Verification Method: DemonstrationData Input:

Test personnel with pressure measurement equipment Operate atmospheric controller of space transport Vary exterior pressure of the space transport within operation range

Expected Condition: Interior temperature of the space transport unit is between 28kPa and 32kPa regardless of the pressure exerted on the exterior of the space transport unit

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 13Test objective: Ensure air composition within space transport unit is within limits defined in the ISO 15859-13:2004 standardIdentifier of Requirement Tested: STU_CRC11, STU_ CEC18Verification Method: DemonstrationData Input:

Test personnel with air composition measurement equipment Operate atmospheric controller of space transport Vary air composition outside the space transport ISO 15859-13:2004 standard

Expected Condition: Air composition within the space transport unit stays within limits defined in the ISO 15859-13:2004 standard regardless of the changes in the exterior of the space transport unit

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 14Test objective: Ensure the acceleration force exerted on passenger is below not greater than 4.7gIdentifier of Requirement Tested: STU_CEC19Verification Method: DemonstrationData Input:

Test dummy Perform space operation using space transport unit

Expected Condition: Maximum acceleration forced measured by the test dummy should not exceed 4.7g through out the whole course of the space operation

128

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CEC 15Test objective: Ensure space Transport unit has 1 or more sanitary system.Identifier of Requirement Tested: STU_ CEC20Verification Method: DemonstrationData Input:

Sanitary systemExpected Condition: 1 or more sanitary system observed onboard the space transport

Level: System Component Tested: Space Transport UnitIdentifier of Test: S-CEC 16Test objective: Ensure sanitary system is accessible to all passengers.Identifier of Requirement Tested: STU_CEC21Verification Method: DemonstrationData Input:

Test personnel Sanitary system

Expected Condition: Sanitary system accessible by all test personnel onboard space transport unit

level: System Component Tested: Space Transport UnitIdentifier of Test: S-CEC 17Test objective: Ensure sanitary system is capable of operating in zero gravity..Identifier of Requirement Tested: STU_CEC22Verification Method: DemonstrationData Input:

Sanitary system Zero gravity environment

Expected Condition: Successful operation of sanitary system in zero gravity

3.2.2.4. Operational Capability

level: System Component Tested: Space Transport UnitIdentifier of Test: S-OPC 01Test objective: Ensure space transport unit is capable of reaching sub-orbital altitudeIdentifier of Requirement Tested: STU_OC01Verification Method: DemonstrationData Input:

Launch Space transport unitExpected Condition: Space transport unit is capable or reaching an altitude of 100 Km above sea level

129

level: System Component Tested: Space Transport UnitIdentifier of Test: S-OPC 02Test objective: Ensure space transport is capable of performing re-entry Identifier of Requirement Tested: STU_OC02Verification Method: SimulationData Input:

simulate re-entry conditions on model space transport unitExpected Condition: Space transport unit successfully completes re-entry simulation

level: System Component Tested: Space Transport UnitIdentifier of Test: S-OPC 03Test objective: Ensure space transport is capable of performing re-entry Identifier of Requirement Tested: STU_OC02Verification Method: DemonstrationData Input:

Initiate flight to sub-orbital altitude Initiate re-entry procedures

Expected Condition: Space transport unit successfully completes re-entry

Level: System Component Tested: Space Transport UnitIdentifier of Test: S-OPC 04Test objective: Ensure space transport is capable of landingIdentifier of Requirement Tested: STU_OC03Verification Method: SimulationData Input:

Simulate landing of space transport unitExpected Condition: Space transport successfully complete landing simulation

Level: System Component Tested: Space Transport UnitIdentifier of Test: S-OPC 05Test objective: Ensure space transport is capable of landingIdentifier of Requirement Tested: STU_OC03Verification Method: DemonstrationData Input:

Perform flight operation of space transport unit Initiate landing procedures

Expected Condition: Space transport successfully complete landing

Level: System Component Tested: Space Transport UnitIdentifier of Test: S-OPC 06Test objective: Ensure space transport unit is operation in zero gravityIdentifier of Requirement Tested: STU_OC04Verification Method: SimulationData Input:

Zero gravity environmentExpected Condition: All systems in the space transport unit remains operational under zero gravity

130

Level: System Component Tested: Space Transport Unit Identifier of Test: S-OPC 07Test objective: Ensure space transport unit’s capability of sending communications to Ground terminalIdentifier of Requirement Tested: STU_OC05Verification Method: DemonstrationData Input:

Transmission of data stream from space transport unit while in spaceExpected Condition: All data successfully received at ground station

level: System Component Tested: Space Transport UnitIdentifier of Test: S-OPC 08Test objective: Ensure space transport unit’s capability of receiving data from Ground Terminal.Identifier of Requirement Tested: STU_OC06Verification Method: DemonstrationData Input:

Transmission of data from ground terminal .Expected Condition: All data successfully received by space transport unit while in space

Level: System Component Tested: Space Transport UnitIdentifier of Test: S-OPC 09Test objective: Ensure system for controlling the space transport u nit is providedIdentifier of Requirement Tested: STU_OC07Verification Method: AnalysisData Input:

Blueprint of space transport unit.Expected Condition: 1 or more means of controlling space transport unit observed

Level: System Component Tested: Space Transport Unit Identifier of Test: S-OPC 10Test objective: Ensure space transport unit is capable of performing self test Identifier of Requirement Tested: STU_OC08Verification Method: DemonstrationData Input:

Issue command for space transport unit to perform self test. Expected Condition: Successful completion of self test routine

131

Level: System Component Tested: Space Transport UnitIdentifier of Test: S-OPC 11Test objective: Ensure operator is provided the capability to perform self test Identifier of Requirement Tested: STU_OC09Verification Method: DemonstrationData Input:

Test personnel initiates self test routineExpected Condition: Successful completion of self test routine

Level: System System Tested: Space Transport UnitIdentifier of Test: S-OPC 12Test objective: Ensure Space transport unit provides operator with navigation capabilityIdentifier of Requirement Tested: STU_OC10Verification Method: AnalysisData Input:

Blueprints of space transport unitExpected Condition: Presence of 1 or more navigation systems

Level: System System Tested: Space Transport UnitIdentifier of Test: S-OPC 13Test objective: Ensure Space transport unit is capable of navigating with an error less than 10 meters.Identifier of Requirement Tested: STU_OC11Verification Method: SimulationData Input:

Simulate space transport unit’s positional data on navigation systemExpected Condition: Navigation system outputs correct navigation data with respect to the simulated location of the space transport

Level: System System Tested: Flight control Identifier of Test: S-OPC 14Test objective: Ensure the space transport unit provides operators with at least 1 means of controlling the unit’s functionsIdentifier of Requirement Tested: STU_OC12Verification Method: AnalysisData Input:

Blueprints of space transport unitExpected Condition: 1 or means of controlling the space unit’s functions is found

132

Level: System System Tested: Flight control Identifier of Test: S-OPC 15Test objective: Ensure the space transport unit has means of restricting access to the unit’s control.Identifier of Requirement Tested: STU_OC13Verification Method: DemonstrationData Input:

Attempt by test personnel to gain access to control equipment of space transport unit

Expected Condition: Access is to test personnel is denied unless in the presence of proper authorisation

Level: System System Tested: Space Transport UnitIdentifier of Test: S-OPC 16Test objective: Ensure the space transport unit can withstand an exterior temperature of 648.8 degrees CelsiusIdentifier of Requirement Tested: STU_OC14Verification Method: DemonstrationData Input:

648.8 degrees Celsius temperatureExpected Condition: Space transport unit is not effected by given temperature

Level: System System Tested: Space transport unit Identifier of Test: S-OPC 17Test objective: Ensure the space transport unit can withstand exterior wind speeds greater than 30km\hIdentifier of Requirement Tested: STU_OC15Verification Method: DemonstrationData Input:

Wind speed greater than 30km\hExpected Condition: Space transport unit is not effected by given wind speeds

3.2.2.5. Security CapabilityLevel: System System Tested: Surveillance System Identifier of Test: S-SEC 01Test objective: Ensure Surveillance on the space transport unit is maintained on all passengers at all timesIdentifier of Requirement Tested: STU_SuC01Verification Method: DemonstrationData Input:

Test personnelExpected Condition: All test personnel aboard space transport unit are under surveillance at all times

133

Level: System System Tested: Surveillance System Identifier of Test: S-SEC 02Test objective: Ensure a record of surveillance on the space transport unit is kept for at least 24 hours Identifier of Requirement Tested: STU_SuC02Verification Method: DemonstrationData Input:

Operate surveillance system for 24 hoursExpected Condition: All data from the duration of the test is recorded

3.2.2.6. Maintenance CapabilityLevel: System System Tested: Maintenance System Identifier of Test: S-MAR 01Test objective: Ensure MTBF of space transport unit is at least 1800 hoursIdentifier of Requirement Tested: STU_MR01Verification Method: AnalysisData Input:

Specifications of space transport unitExpected Condition: Space transport unit has a MTBF of no less than 1800 hours

Level: System System Tested: Maintenance System Identifier of Test: S-MAR 02Test objective Ensure MTBR of space transport unit is at least 72 hoursIdentifier of Requirement Tested: STU_MR02Verification Method: AnalysisData Input:

Specifications of space transport unitExpected Condition: Space transport unit has a MTBR of no less than 72 hours

Level: System System Tested: Maintenance SystemIdentifier of Test: S-MAR 03Test objective: Ensure MTBM of space transport unit is at least 24 hoursIdentifier of Requirement Tested: STU_MR03Verification Method: AnalysisData Input:

Space transport unitExpected Condition: Space transport unit has a MTBM of no less than 24 hours

134

Level: System System Tested: Maintenance System Identifier of Test: S-MAR 04Test objective: Ensure operator of space transport is capable of making any basic repairs.Identifier of Requirement Tested: STU_MR04Verification Method: AnalysisData Input:

Blueprints of space transport unitExpected Condition: Storage facility has been allocated for basic maintenance equipment

3.2.2.7. RegulationsLevel: System System Tested: Space Transport SystemIdentifier of Test: S-SAF 01Test objective: Ensure system conforms to standard ISO 14620-1:2002 Identifier of Requirement Tested: STU_RE01Verification Method: AnalysisData Input:

Space transport unit Ground terminal

Expected Condition: System conforms to standard

Level: System System Tested: Space Transport System Identifier of Test: S-SAF 02Test objective: Ensure system conforms to standard ISO 15892:2000Identifier of Requirement Tested: STU_ RE 02Verification Method: AnalysisData Input:



Level: System System Tested: Space Transport SystemIdentifier of Test: S-SAF 03Test objective: Ensure system conforms to standard ISO 14302:2002Identifier of Requirement Tested: STU_ RE 03Verification Method: AnalysisData Input:



135







Level: System System Tested: Space Transport UnitIdentifier of Test: S-SAF 06Test objective: Ensure system conforms to standard ISO 14623:2003Identifier of Requirement Tested: STU_ RE 06Verification Method: AnalysisData Input:

Space transport unitExpected Condition: System conforms to standard




136

Level: System System Tested: Space Transport UnitIdentifier of Test: S-SAF 08Test objective: Ensure system conforms to standard ISO 15859-13:2004Identifier of Requirement Tested: STU_ RE 08Verification Method: AnalysisData Input:

Space transport unitExpected Condition: System conforms to standard




Level: System System Tested: Space Transport SystemIdentifier of Test: S-SAF 10Test objective: Ensure system conforms to standard ISO 14624-1:2003Identifier of Requirement Tested: STU_ RE 10Verification Method: AnalysisData Input:



137





Joyride to Space

Sub-system Requirements DocumentVersion 1.7

138

Document Overview

The subsystem requirements are the functional blueprint for how the joyride space program is to operate. It details what the subsystem is capable of doing, how the different systems will interact with each other, and how the subsystem components will function both independently as well as interfacing with the main system.

Sub-system Requirements Contents

1. Navigation Requirements.......................................................................................1382. Disposal Requirements...........................................................................................1393. Space Transport Communication Requirements....................................................1414. Ground Base Communication Requirements.........................................................1425. Storage Requirements.............................................................................................1446. Servicing Requirements.........................................................................................1457. Launching Requirements........................................................................................1468. Propulsion System Requirements...........................................................................1479. Atmosphere Requirements.....................................................................................14810. Temperature Requirements..................................................................................14811. Pressure Requirements.........................................................................................14812. Customer Services Requirements.........................................................................14913. Check-in terminal Requirements..........................................................................14914. Catering Requirements.........................................................................................15015. Parking Requirements..........................................................................................15016. Locker Requirements...........................................................................................15117.Entertainment/ Telecommunication services........................................................15118. Sanitary services...................................................................................................152

139

1. Navigation Requirements

Requirement Identifier: NAV_01Requirement: The system shall have a Global Positioning System (GPS) satellite system that provides two-dimensional (latitude and longitude) coverage of the space vehicle in space with at least three satellites in view, as recommended by European satellite navigation system (EADS). Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Simulation

Requirement Identifier: NAV_02Requirement: The system shall have a Global Positioning System (GPS) satellite system that provides three-dimensional altitude coverage of the space vehicle in space with at least four satellites in view, as recommended by European satellite navigation system (EADS). Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Simulation

Requirement Identifier: NAV_03Requirement: The system shall be able to determine the position of the space vehicle under weather conditions as recommended by European satellite navigation system (EADS). Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Simulation

Requirement Identifier: NAV_04Requirement: The system shall be able to determine the position of the space vehicle up to a 16 meter spherical error probability precision of a three-dimensional position as recommended by European satellite navigation system (EADS).Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Simulation

Requirement Identifier: NAV_05Requirement: The system shall be able to determine the velocity of the space vehicle up to 0.1 meter/second accuracy as recommended by European satellite navigation system (EADS).Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Simulation

140

Requirement Identifier: NAV_06Requirement: The system shall be able to have time synchronisation accuracy with the space vehicle up to 0.1 microsecond accuracy as recommended by European satellite navigation system (EADS).Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Simulation

Requirement Identifier: NAV_07Requirement: The system shall be inter-operable with at least two other global satellite navigation

systems as recommended by European satellite navigation system (EADS). Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Simulation

Requirement Identifier: NAV_08Requirement: The system shall be capable of supporting en-route navigation requirements down to and including ICAO specified Required Navigation Performance values of RNP 4, as stated under mandatory requirements M2 addressed by Australian Civil Aviation Navigation Operations.Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Simulation

Requirement Identifier: NAV_09Requirement: The system shall be capable of supporting navigation guidance to precision approach minima in accordance with ICAO Cat II and III to those locations specifically identified during the cost benefit , as stated under desirable requirements D4 addressed by Australian Civil Aviation Navigation Operations.Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Simulation

2. Disposal Requirements

Requirement Identifier: DIS_01Requirement: All hazardous materials used in design of the Space Transport Unit shall be separated at unit retirement as described by the Basel Convention on Movements of Hazardous Disposal. Priority: HighTraceability: GT_DC02Verification Method: Demonstration

Requirement Identifier: DIS_02Requirement: All hazardous materials used in design of the Space Transport Unit shall be disposed off at unit retirement as described by the Basel Convention on Movements of Hazardous Disposal. Priority: HighTraceability: GT_DC02Verification Method: Demonstration

141

Requirement Identifier: DIS_03Requirement: All recyclable materials used in design of the Space Transport Unit shall be separated at unit retirement and reprocessed in accordance with Basel Convention on Movements of Hazardous Disposal.Priority: HighTraceability: GT_DC03Verification Method: Demonstration

Requirement Identifier: DIS_04Requirement: All non recyclable materials used in design of the Space Transport Unit shall be disposed of at unit retirement in accordance with Basel Convention on Movements of Hazardous Disposal. Priority: HighTraceability: GT_DC04Verification Method: Demonstration

Requirement Identifier: DIS_05Requirement: All hazardous materials used in design of the Ground Facilities shall be separated at retirement as described by the Basel Convention on Movements of Hazardous Disposal.Priority: HighTraceability: GT_DC02Verification Method: Demonstration

Requirement Identifier: DIS_06Requirement: All hazardous materials used in design of the Ground Facilities shall be disposed of at retirement as described by the Basel Convention on Movements of Hazardous Disposal Priority: HighTraceability: GT_DC02Verification Method: DemonstrationRequirement Identifier: DIS_07Requirement: All recyclable materials used in design of the Ground Facilities shall be separated at retirement and reprocessed in accordance Basel Convention on Movements of Hazardous Disposal.Priority: HighTraceability: GT_DC03Verification Method: Demonstration

Requirement Identifier: DIS_08Requirement: All non recyclable materials used in design of the Ground Facilities shall be disposed of at retirement Basel Convention on Movements of Hazardous Disposal. Priority: HighTraceability: GT_DC04Verification Method: Demonstration

142

3. Space Transport Communication Requirements

Requirement Identifier: SGCOM001Requirement: Space transport communications system shall be capable of communicating with the ground base.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.5Verification Method: Demonstration, User feedback.

Requirement Identifier: SGCOM002Requirement: The space transport communications system shall provide communications via the UHF transmission.Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration, User feedback.

Requirement Identifier: SGCOM003Requirement: The space transport communications system shall provide communications via the HF transmission. Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration, User feedback.

Requirement Identifier: SGCOM004Requirement: The space transport shall have no less than 4 LCD screens for video communicationsPriority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration

Requirement Identifier: SGCOM005Requirement: Each LCD screen shall have a viewable size of no less than 12 inches.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.7Verification Method: Demonstration

Requirement Identifier: SGCOM006Requirement: The space transport communication system shall be able to send video images.Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration, User feedback.

Requirement Identifier: SGCOM007Requirement: Each video image shall have a transmission delay of no greater than 1 second.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.7Verification Method: Demonstration, User feedback, Timing.

143

Requirement Identifier: SGCOM008Requirement: The space transport communications system shall have no less than 2 antennas capable of space signal reception.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.7Verification Method: Demonstration

Requirement Identifier: SGCOM009Requirement: The space transport communications system shall provide telemetry transmission in real time.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.7Verification Method: Demonstration, User feedback.

Requirement Identifier: SGCOM010Requirement: The space transport communication system shall be able to transmit audio signals.Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration, User feedback.

Requirement Identifier: SGCOM011Requirement: The space transport communication system shall provide a tracking subsystem via C-band.Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration, User feedback.

Requirement Identifier: SGCOM012Requirement: The space transport communication system shall provide a tracking subsystem via S-band.Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration, User feedback.

Requirement Identifier: SGCOM013Requirement: The space transport communication system shall provide data storage facility for all recorded flight data obtained. Priority: HighTraceability: SLINK1.5, SLINK1.6Verification Method: Demonstration

4. Ground Base Communication Requirements

Requirement Identifier: GSCOM001Requirement: The ground base communications system shall be capable of communicating with the space transport.Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration, User feedback.

144

Requirement Identifier: GSCOM002Requirement: The ground base communications system shall provide digital communication technologies (modulation, coding, onboard processing and switching and network terminals). Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration, User feedback.

Requirement Identifier: GSCOM003Requirement: The ground base communications system shall have no less than 1 LCD screen for each video communication channel.Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration

Requirement Identifier: GSCOM004Requirement: Each LCD screens have a viewable size of no less than 15 inches.Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.7Verification Method: Demonstration

Requirement Identifier: GSCOM005Requirement: The ground base communication system shall be able to send audio signal to the space transport communication system.Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration, User feedback.

Requirement Identifier: GSCOM006Requirement: The ground base communications system shall provide high rate communication via S-band.Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration, User feedback.

Requirement Identifier: GSCOM007Requirement: The ground base communications system shall provide data storage facility for all recorded flight data obtained. Priority: HighTraceability: SLINK1.5, SLINK1.6, SLINK1.7Verification Method: Demonstration.

Requirement Identifier: GSCOM008Requirement: The ground base communications system shall be able to send video signals.Priority: HighTraceability: SLINK1.1, SLINK1.2Verification Method: Demonstration, User feedback.

145

5. Storage Requirements

Requirement Identifier: STO_01Requirement: The Space Transport Unit Hanger shall have a breadth of length not less than 150 m.Priority: HighTraceability: GT_SC01, GT_SC02, GT_SC03, GT_SC04Verification Method: Demonstration

Requirement Identifier: STO_02Requirement: The Space Transport Unit Hanger shall have a width of length not less than 200 m.Priority: HighTraceability: GT_SC01, GT_SC02, GT_SC03, GT_SC04Verification Method: Demonstration

Requirement Identifier: STO_03Requirement: The Space Transport Unit Hanger shall have a height of length not less than 15 m.Priority: HighTraceability: GT_SC01, GT_SC02, GT_SC03, GT_SC04Verification Method: Demonstration

Requirement Identifier: STO_04Requirement: The hanger shall have security surveillance operating at all hours.Priority: HighTraceability: GT_SC05,Verification Method: Demonstration

Requirement Identifier: STO_05Requirement: The hanger shall restrict access to unauthorised personnel. Priority: HighTraceability: GT_SC05,Verification Method: Demonstration

Requirement Identifier: STO_06Requirement: The ground terminal shall provide storage space for ground terminal maintenance equipment.Priority: HighTraceability: GT_SC07Verification Method: Demonstration

Requirement Identifier: STO_07Requirement: The Ground Terminal shall provide storage space for Space Transport Unit maintenance equipment. Priority: HighTraceability: GT_SC08, GT_SC09, GT_SC10Verification Method: Demonstration

146

Requirement Identifier: STO_08Requirement: The Ground Terminal shall have underground fuel storage facility.Priority: HighTraceability: GT_SC11Verification Method: Demonstration

Requirement Identifier: STO_09Requirement: The fuel storage facility shall be no less than 1500 metres away from surrounding buildings.Priority: HighTraceability: GT_SC11Verification Method: Demonstration

Requirement Identifier: STO_10Requirement: The fuel storage shall have the capacity to store no less than 6 million litres of fuel.Priority: HighTraceability: GT_SC11Verification Method: Demonstration

6. Servicing Requirements

Requirement Identifier: SER_01Requirement: All pre-launch maintenance tools shall be stored in the Ground Terminal Storage hangarPriority: HighTraceability: GT_LF04, STO_03Verification Method: Demonstration

Requirement Identifier: SER_02Requirement: All basic level maintenance equipment shall be stored in the Ground Terminal Storage hangarPriority: HighTraceability: GT_SC08, STO_03Verification Method: Demonstration

Requirement Identifier: SER_03Requirement: All intermediate level maintenance equipment shall be stored in the Ground Terminal Storage hangarPriority: HighTraceability: GT_SC09, STO_03Verification Method: Demonstration

Requirement Identifier: SER_04Requirement: All advanced level maintenance equipment shall be stored in the Ground Terminal Storage hangarPriority: HighTraceability: GT_SC10, STO_03Verification Method: Demonstration

147

Requirement Identifier: SER_05Requirement: All pre-launch maintenance equipment shall be located within the Ground Terminal boundariesPriority: HighTraceability: GT_LF05Verification Method: Demonstration, Analysis

7. Launching Requirements

Requirement Identifier: LNCH_01Requirement: The system shall have at least one runway for take-off and landing.Priority: HighTraceability: GT_LF01, GT_LF02Verification Method: Observation.

Requirement Identifier: LNCH_02Requirement: The runway shall be able to withstand static weights no less than 120 tonnes.Priority: HighTraceability: GT_LF01, GT_LF05, GT_LF06 Verification Method: Testing, Demonstration.

Requirement Identifier: LNCH_03Requirement: The runway shall be able to withstand impacts no less than 1.30x3 Nm within an area of 4 m2.Priority: HighTraceability: GT_LF01, GT_LF03 Verification Method: Testing, Demonstration.

Requirement Identifier: LNCH_04Requirement: The runway shall be treated with skid-resistant material (grooved or PFC) per ICAO specifications.Priority: HighTraceability: GT_LF06 Verification Method: Testing, Demonstration.

Requirement Identifier: LNCH_05Requirement: The runway shall be of length no less than 1.5 km.Priority: HighTraceability: GT_LF03, GT_LF04, GT_LF05Verification Method: Observation, Measurement.

148

8. Propulsion System Requirements

Requirement Identifier: PROP_01Requirement: The system shall have no less than one main engine.Priority: HighTraceability: STU_OC01, GT_GL01Verification Method: Demonstration.

Requirement Identifier: PROP_02Requirement: The engine(s) shall be able to provide no less than 95 thousand newtons of thrust.Priority: HighTraceability: STU_OC01, STU_OC02, STU_OC03, GT_GL02, GT_GL03Verification Method: Demonstration.

Requirement Identifier: PROP_03Requirement: The engine(s) shall be able to provide thrust for the entire duration of the take-off procedure.Priority: HighTraceability: STU_OC01, GT_GL02Verification Method: Demonstration.

Requirement Identifier: PROP_04Requirement: The system shall have no less than 5 thrusters.Priority: HighTraceability: STU_OC01, STU_OC03, GT_GL02, GT_GL03Verification Method: Demonstration.

Requirement Identifier: PROP_05Requirement: Each thruster shall provide no less than thirty thousand newtons of thrust.Priority: HighTraceability: STU_OC01, STU_OC02, GT_GL02Verification Method: Demonstration.

Requirement Identifier: PROP_06Requirement: The arrangement of thrusters shall be capable of providing trajectory corrections.Priority: HighTraceability: STU_OC02, STU_OC03, GT_GL02, GT_GL03Verification Method: Demonstration.

Requirement Identifier: PROP_07Requirement: The amount of on-board propellent shall be no less than 1.5 times the amount needed for the trip.Priority: HighTraceability: STU_OC01, GT_GL02Verification Method: Demonstration.

149

9. Atmosphere Requirements

Requirement Identifier: LSS_01Requirement: All components of the space vehicle shall be able to withstand pressure from atmospheric conditions specified by Rocket & Space Technology [8].Traceability: STU_OC10, STU_OC11Verification Method: Demonstration

10. Temperature Requirements

Requirement Identifier: TMP_01Requirement: The system shall maintain temperature control for life support within the range of 8°C to 27°C (64°-81 °F) .Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Demonstration

Requirement Identifier: TMP_02Requirement: The system shall handle no less than 3,000 degrees F (1,650 degrees C) of heat generation (for re-entry to earth).Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Demonstration

11. Pressure Requirements

Requirement Identifier: PRR_01Requirement: The exterior of the system shall handle no less than 760 millimetres of mercury pressure [2].Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Demonstration

Requirement Identifier: PRR_02Requirement: The interior of the system shall maintain an atmospheric pressure of 14.7 psi at all times according to FAA regulations.Priority: HighTraceability: STU_OC10, STU_OC11Verification Method: Demonstration

150

12. Customer Services Requirements

Requirement Identifier: CS_REQ1Requirement: Ground station shall have no less than 1 information system Priority: HighTraceability: GT_CS02, GT_CS03Verification Method: Demonstration

Requirement Identifier: CS_REQ2Requirement: Informational System shall have no less than 1 visual informational device Priority: HighTraceability: GT_CS03Verification Method: Demonstration

Requirement Identifier: CS_REQ3Requirement: Informational System shall have no less than 1 public announcement systemPriority: HighTraceability: GT_CS03Verification Method: Demonstration

Requirement Identifier: CS_REQ4Requirement Informational System shall provide departure time of all flights to space.Priority: HighTraceability: SLINK 1.1, SLINK 1.7Verification Method: Simulation

Requirement Identifier: CS_REQ5Requirement Informational System shall provide no less than 1 help desk facilityPriority: HighTraceability: SLINK 1.1Verification Method: Demonstration

13. Check-in terminal Requirements

Requirement Identifier: CH_REQ01Requirement: Check-in terminal department shall have no less than 10 countersPriority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.4Verification Method: Demonstration.

Requirement Identifier: CH_REQ02Requirement: Each counter height shall be no less than 1 metre Priority: MediumTraceability: SLINK1.1, SLINK1.2, SLINK1.4Verification Method: Demonstration.

151

Requirement Identifier: CH_REQ03Requirement: Each counter length shall be no less than 1 metre Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.4Verification Method: Demonstration.

Requirement Identifier: CH_REQ04Requirement: Each counter width shall be no less than 0.5 metre Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.4Verification Method: Demonstration

Requirement Identifier: CH_REQ05Requirement: Each counter shall have no less than 1 ticket scanner. Priority: HighTraceability: SLINK1.1, SLINK1.2, SLINK1.4Verification Method: Demonstration

14. Catering Requirements

Requirement Identifier: GT_REQ6Requirement: Catering facilities shall cater for no less than 1000 peoplePriority: HighTraceability: SLINK1.4, SLINK1.9Verification Method: Demonstration.

Requirement Identifier: GT_REQ7Requirement: Catering facilities shall have no less than 2 food outlets Priority: MediumTraceability: SLINK1.4Verification Method: Demonstration.

15. Parking Requirements

Requirement Identifier: GT_REQ1Requirement: Parking area shall have allocated space for no less than 250 vehiclesPriority: HighTraceability: SLINK1.4, SLINK1.9Verification Method: Demonstration.

Requirement Identifier: GT_REQ3Requirement: Each parking space shall have a length of no less than 4 metres Priority: HighTraceability: SLINK1.4Verification Method: Demonstration.

152

Requirement Identifier: GT_REQ4Requirement: Each parking space shall have a width of no less than 2.5 metresPriority: HighTraceability: SLINK1.4Verification Method: Demonstration.

16. Locker Requirements

Requirement Identifier: LO_REQ01Requirement: Ground terminal shall provide no less than 250 lockersPriority: HighTraceability: SLINK 1.9, GT_CS09Verification Method: Demonstration.

Requirement Identifier: LO_REQ02Requirement: Each locker height shall be no less than 0.9 metresPriority: HighTraceability: SLINK 1.9Verification Method: Demonstration.

Requirement Identifier: LO_REQ03Requirement: Each locker length shall be no less than 0.9 metres Priority: HighTraceability: SLINK 1.9Verification Method: Demonstration

Requirement Identifier: LO_REQ04Requirement: Each locker width shall be no less than 0.4 metrePriority: HighTraceability: SLINK 1.9Verification Method: Demonstration

17. Entertainment/ Telecommunication services

Requirement Identifier: ET_REQ1Requirement: Ground terminals shall have no less than 10 computers for patrons.Priority: HighTraceability: SLINK1.4Verification Method: Demonstration.

Requirement Identifier: ET_REQ2Requirement: Each computer shall be connected to the internet.Priority: HighTraceability: SLINK1.4Verification Method: Demonstration.

153

Requirement Identifier: ET_REQ4Requirement: Ground terminal shall have no less than 10 public phone booths. Priority: HighTraceability: SLINK1.4Verification Method: Demonstration.

18. Sanitary services

Requirement Identifier: SS_REQ1Requirement: Ground terminal shall have no less than 6 toilet facilities.Priority: HighTraceability: SLINK1.4Verification Method: Demonstration.

Requirement Identifier: SS_REQ1Requirement: Each toilet shall have no less than 5 sanitary cubicles.Priority: HighTraceability: SLINK1.4Verification Method: Demonstration.

Requirement Identifier: SS_REQ2Requirement: Washrooms shall provide identification for gender use.Priority: HighTraceability: SLINK1.4Verification Method: Demonstration.

154





Joyride to Space

Sub-System Test PlanVersion 1.1

155

Sub-System Test Plan Contents

1 System Level Testing........................................................................................1551.1 Safety...............................................................................................................155

2 GROUND TERMINAL....................................................................................1572.1 Storage Capability............................................................................................1572.2 Disposal Capability..........................................................................................160

3 SPACE TRANSPORT UNIT...........................................................................1603.1 Carrying Capability..........................................................................................1603.2 Safety Capability..............................................................................................1623.3 Comfort & Entertainment Capability...............................................................1643.4 Operational Capability.....................................................................................1673.5 Security Capability...........................................................................................1683.6 Maintenance & Reliability...............................................................................169

156

System Level Testing

Safety

Level: System System Tested: Space Transport SystemIdentifier of Test: S-SAF 01Test objective: Ensure system conforms to standard ISO 14620-1:2002 Identifier of Requirement Tested: STU_SF01Verification Method: AnalysisData Input:

Entire Space transport system Entire Ground terminal system

Expected Condition: All space transport and ground terminal systems conforms to safety regulations specified in ISO 14620-1:2002

Level: System System Tested: Space Transport System Identifier of Test: S-SAF 02Test objective: Ensure system conforms to standard ISO 15892:2000Identifier of Requirement Tested: STU_SF02Verification Method: AnalysisData Input:


Expected Condition: All space transport and ground terminal systems conforms to safety regulations specified in ISO 15892:2000

Level: System System Tested: Space Transport SystemIdentifier of Test: S-SAF 03Test objective: Ensure system conforms to standard ISO 14302:2002Identifier of Requirement Tested: STU_SF03Verification Method: AnalysisData Input:



157







Level: System System Tested: Space Transport Unit SystemIdentifier of Test: S-SAF 06Test objective: Ensure system conforms to standard ISO 14623:2003Identifier of Requirement Tested: STU_SF06Verification Method: AnalysisData Input:

Entire Space transport systemExpected Condition: All space transport and ground terminal systems conforms to safety regulations specified in ISO 14623:2003




158

Level: System System Tested: Space Transport Unit SystemIdentifier of Test: S-SAF 08Test objective: Ensure system conforms to standard ISO 15859-13:2004Identifier of Requirement Tested: STU_SF08Verification Method: AnalysisData Input:

Entire Space transport systemExpected Condition: All space transport systems conforms to safety regulations specified in ISO 15859-13:2004




GROUND TERMINAL

Storage Capability

Level: System System Tested: Space Transport Unit storageIdentifier of Test: T-STC01Test objective: Ensure that Ground Terminal can store 5 or more Space Transport Units.Identifier of Requirement Tested: GT_SC01Verification Method: CalculationData Input:

Space Transport Units Ground Terminal Storage Area

Expected Condition: Ground Terminal is able to store more than 5 Space Transport Units

159

Level: System System Tested: Space Transport Unit equipment storage system Identifier of Test: T-STC05Test objective: Ensure that Ground Terminal has designated space for maintenance equipment storage.Identifier of Requirement Tested: GT_SC06Verification Method: DemonstrationData Input:

Maintenance equipment storage area in Ground TerminalExpected Condition: Ground terminal has no less than 1 designated area for the storage of maintenance equipment.

Level: System System Tested: Ground Terminal fuel storage system Identifier of Test: T-STC08Test objective: Ensure that Ground Terminal can store enough fuel to fill 20 Space Transport Units Identifier of Requirement Tested: GT_SC09Verification Method: DemonstrationData Input:

Space Transport Unit’s fuel capacityExpected Condition: Ground Terminal storage area has storage facility to store enough fuel to refill 20 Space Transport Units

Level: System Component Tested: Ground TerminalIdentifier of Test: T-REG02Test objective: Ensure any organisation participating in launch activities of space vehicles shall conform to ISO 14620-3:2005.Identifier of Requirement Tested: GT_GL02Verification Method: DemonstrationData Input:

All launch activities of involving space vehicles.Expected Condition: Organisation that participates in launch activities of space vehicles conforms to ISO 14620-3:2005 standards.

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: T-REG03Test objective: Ensure cleanliness level of fluid system components and equipment used in space systems are able to conform to ISO 14952-2:2003 standards. Identifier of Requirement Tested: GT_GL03Verification Method: DemonstrationData Input:

All fluid system components in space system All equipments used in space systems

Expected Condition: Cleanliness level of fluid system components and equipment used in space systems conforms to ISO 14952-2:2003 standards.

160

Level: System Component Tested: Ground Terminal Communications Identifier of Test: T-REG04Test objective: Ensure communication requirement for spacecraft, radio links, tracking stations, ground communication circuits and mission control centres are able to conform to ISO 14952-2:2003 standards. Identifier of Requirement Tested: GT_GL04Verification Method: DemonstrationData Input:

All Spacecraft equipment All radio equipments All tracking stations All ground communication circuits All equipments in mission control centres

Expected Condition: Communication requirement for spacecraft, radio links, tracking stations, ground communication circuits and mission control centres conform to ISO 14952-2:2003 standards.

Level: System Component Tested: Launch SiteIdentifier of Test: T-REG05Test objective: Ensure Space safety requirements for launch site operations are able to conform to ISO 14620-2:2000 standards. Identifier of Requirement Tested: GT_GL05Verification Method: DemonstrationData Input:

All launch site operationsExpected Condition: Space safety requirements for launch site operations conform to ISO 14620-2:2000 standards.

Level: System Component Tested: Ground Terminal Identifier of Test: T-REG06Test objective: Ensure Requirements and guidelines for spacecraft on-board functions are able to conform to ISO 14950:2003 standards. Identifier of Requirement Tested: GT_GL06Verification Method: DemonstrationData Input:

Specified ground segmentExpected Condition: Requirements and guidelines for spacecraft on-board functions conform to ISO 14950:2003 standards and enable a specified ground segment to operate the spacecraft in any nominal or predefined contingency situation.

161

Disposal Capability

Level: System Component Tested: Disposal SystemIdentifier of Test: T-DIC01Test objective: Ensure Ground terminals are capable of discarding faulty equipment.Identifier of Requirement Tested: GT_DC01Verification Method: AnalysisData Input:

Faulty equipments in ground terminal Faulty equipments in Space Transport Unit

Expected Condition: Faulty equipment is discarded.

Level: System Component Tested: Disposal SystemIdentifier of Test: T-DIC02Test objective: Ensure Ground terminals are capable of discarding Space transport units at the end of the life cycle.Identifier of Requirement Tested: GT_DC02Verification Method: AnalysisData Input:

Faulty Space transport units Expected Condition: Ground terminals are able to discard Space transport units at the end of the life cycle.

SPACE TRANSPORT UNIT

Carrying Capability

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CAC01Test objective: Ensure Space transport unit is capable of carrying no less than 20 people.Identifier of Requirement Tested: STU_CC01Verification Method: DemonstrationData Input:

20 people Space transport unit

Expected Condition: Space transport unit can carry more than 20 people.

162

Level: System Component Tested: Space Transport UnitIdentifier of Test: S-CAC02Test objective: Ensure Space transport unit is capable of carrying a weight of no less than 1 tonne.Identifier of Requirement Tested: STU_CC02Verification Method: AnalysisData Input:

Test laden weight of 1 tonne Expected Condition: Space transport unit can carry weight of no less than 1 tonne.

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CAC03Test objective: Ensure there must be a storage area for each passenger.Identifier of Requirement Tested: STU_CC03Verification Method: DemonstrationData Input:

A bag with allowed size (56cm x 36cm x 23cm)Expected Condition: Baggage can fit to the storage locker.

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CAC 04Test objective: Ensure sure there have a door for entering the Space Transport unit.Identifier of Requirement Tested: STU_CC04Verification Method: DemonstrationData Input:

Space transport unitExpected Condition: There is no less than 1 door for passenger boarding in the space transport unit.

Level: System Component Tested: Space Transport Unit Identifier of Test: S-CAC 05Test objective: Ensure there have a door for exiting the Space Transport unit.Identifier of Requirement Tested: Verification Method: DemonstrationData Input:

Space transport unitExpected Condition: There is no less than 1 door for passenger exit in the space transport unit.

163

Safety Capability

Level: System Component Tested: Space Transport Unit Identifier of Test: S-SAC 01Test objective: Ensure there have there have no less than 1 means of securing passengers during flight.Identifier of Requirement Tested: STU_001Verification Method: DemonstrationData Input:

Equipment for securing each passenger to the seat in the Space Vehicle

Expected Condition: There have more than 1 means of securing passenger during flight.

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-SAC 02Test objective: Ensure there have no less than 1 means of securing passenger’s belonging during flightIdentifier of Requirement Tested: STU_002Verification Method: DemonstrationData Input:

Equipment for securing all passenger hand-carry luggageExpected Condition: Passengers have more than 1 means of securing their personal belongings during flight.

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-SAC 03Test objective: Ensure there have no less than 1 means of evacuating the passenger over land.Identifier of Requirement Tested: STU_003Verification Method: DemonstrationData Input:

Space transport unit.Expected Condition: There are more than 1 means of evacuating the passenger over

land.

164

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-SAC 04Test objective: Ensure the space transport unit have no less than 1 means of evacuating the passengers over water.Identifier of Requirement Tested: STU_014Verification Method: DemonstrationData Input:

Space transport unit.Expected Condition: There are more than 1 means of evacuating the passenger over water.

Level: System Component Tested: Space Transport Unit System Identifier of Test: S-SAC 05Test objective: Ensure there is medical equipment necessary for performing first aid on no less than 20 people.Identifier of Requirement Tested: STU_015Verification Method: DemonstrationData Input:

Medical equipments.Expected Condition: There are more than 20 first aid medical equipments, which is expected to 20 passengers.

Level: System Component Tested: Space Transport Unit System Identifier of Test: S-SAC 06Test objective: Ensure there are no flammable objects in the space transport unit.Identifier of Requirement Tested: STU_008Verification Method: DemonstrationData Input:

Security department at Ground Terminal.Expected Condition: All passengers are checked at the security department before entering the space transport unit.

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-SAC 08Test objective: Ensure the space transport unit have fire extinguisher which can accessible by all passengersIdentifier of Requirement Tested: STU_011Verification Method: DemonstrationData Input:

Fire extinguisher in space transport unitExpected Condition: Every fire extinguisher is accessible by each passenger.

165

Comfort & Entertainment Capability

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 01Test objective: Ensure the space transport unit has no less than 1 mounted video recording camera per every 4 passengers.Identifier of Requirement Tested: STU_CEC01Verification Method: DemonstrationData Input:

Mounted video recording camera in space transport unitExpected Condition: There is more than 1 mounted video recording camera per every 4 passengers.

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 02Test objective: Ensure the space transport unit has no less than 1 information deviceIdentifier of Requirement Tested: STU_CEC02Verification Method: DemonstrationData Input:

Information device in space transport unitExpected Condition: Space transport unit have more than 1 information devices.

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 04Test objective: Ensure the space transport unit has a separation of no less than 0.1 meter between every passenger.Identifier of Requirement Tested: STU_CEC04Verification Method: DemonstrationData Input:

Passenger’s seat between each passenger.Expected Condition: The separation between passengers is greater than 0.1 meter.

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 05Test objective: Ensure the passenger’s belonging is not greater than 1 meter from the passenger.Identifier of Requirement Tested: STU_CEC05Verification Method: DemonstrationData Input:

Passenger belonging storage and passenger seat.Expected Condition: The passenger’s belonging is less than 1 meter far from their seat.

166

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 06Test objective: Ensure the space transport have no less than 1 means of observing the vessel’s exterior environment for each passenger.Identifier of Requirement Tested: STU_CEC06Verification Method: DemonstrationData Input:

Observing vessel’s exterior environment.Expected Condition: There have more than 1 means of observing the vessel’s exterior environment for each passenger.

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 07Test objective: Ensure that there have no less than 1 means of entertainment for passengersIdentifier of Requirement Tested: STU_CEC07Verification Method: DemonstrationData Input:

EntertainmentsExpected Condition: Passengers have more than 1 means of entertainment.

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 08Test objective: Test the entertainments are accessible by all passengers.Identifier of Requirement Tested: STU_CEC08Verification Method: DemonstrationData Input:

Passenger’s entertainment.Expected Condition: Passenger’s entertainment is accessible by every passenger.

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 09Test objective: Test the space transport unit have capable of providing an interior illumination level of no less than 30 foot candlesIdentifier of Requirement Tested: STU_CEC09Verification Method: DemonstrationData Input:

Interior illumination of space transport unitExpected Condition: Interior illumination level is more than 30 foot candles.

167

Level: System Component Tested: Space Transport Unit System Identifier of Test: S-CEC 10Test objective: Test the space transport unit have capable of providing an interior illumination level of no greater than 80 foot candlesIdentifier of Requirement Tested: STU_CEC10Verification Method: DemonstrationData Input:

Interior illumination of space transport unitExpected Condition: Interior illumination level is less than 80 foot candles.

Level: System Component Tested: Space Transport Unit System Identifier of Test: S-CEC 11Test objective: Test whether the space transport unit have no less than 20% an internal humidity.Identifier of Requirement Tested: STU_CEC11Verification Method: DemonstrationData Input:

Space transport unitExpected Condition: The space transport unit has more than 20% an internal humidity

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 12Test objective: Test whether the space transport unit no greater than 40% an internal humidity.Identifier of Requirement Tested: SLINK 1.4, SLINK 1.12Verification Method: DemonstrationData Input:

Space transport unitExpected Condition: The space transport unit has less than 40% an internal humidity

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 13Test objective: Ensure that Space transport unit interior temperature no greater than 24 degrees Celsius.Identifier of Requirement Tested: STU_ CEC13Verification Method: DemonstrationData Input:

Temperature test of interior of space transport unit.Expected Condition: Interior temperature of space transport unit no greater than 24 degrees Celsius.

168

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 14Test objective: Ensure that Space transport unit interior temperature of no less than 16 degrees Celsius.Identifier of Requirement Tested: STU_ CEC14Verification Method: DemonstrationData Input:

Temperature test of interior of space transport unit.Expected Condition: Interior temperature of space transports unit no less than 16 degrees Celsius.

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-CEC 15Test objective: Space transport unit interior pressure no greater than 32 kPa.Identifier of Requirement Tested: STU_CEC15Verification Method: DemonstrationData Input:

Pressure test of Space transport unit interior pressureExpected Condition: Pressure less than 32 kPa.

Operational Capability

Level: System Component Tested: Space Transport Unit System Identifier of Test: S-OPC 05Test objective: Space transport unit capability of sending communications with Ground terminalIdentifier of Requirement Tested: STU_OC05Verification Method: DemonstrationData Input:

Space Transport Unit data Ground Terminal received data

Expected Condition: All data successfully sent from Space Transport Unit to Ground Terminal

Level: System Component Tested: Space Transport Unit SystemIdentifier of Test: S-OPC 06Test objective: Space Transport Unit capability of receiving data from Ground Terminal.Identifier of Requirement Tested: STU_OC06Verification Method: DemonstrationData Input:

Space Transport Unit Ground Terminal transmitted data

Expected Condition: All data successfully received from Ground Terminal.

169

Level: System System Tested: Space Transport Unit SystemIdentifier of Test: S-OPC 14Test objective: Ensure the space transport unit can withstand an exterior temperature of 648.8 degrees CelsiusIdentifier of Requirement Tested: STU_OC14Verification Method: DemonstrationData Input:

Space transport unitExpected Condition: Space transport unit is not effected by given temperature.

Level: System System Tested: Space transport unit Identifier of Test: S-OPC 15Test objective: Ensure the space transport unit can withstand exterior wind speeds greater than 30km\hIdentifier of Requirement Tested: STU_OC15Verification Method: DemonstrationData Input:

Space transport unit Wind speed greater than 30km\h

Expected Condition: Space transport unit is not effected by given wind speeds.

Security Capability

Level: System System Tested: Surveillance System Identifier of Test: S-SEC 01Test objective: Ensure Surveillance on the space transport unit is maintained on all passengers at all timesIdentifier of Requirement Tested: STU_SuC01Verification Method: Demonstration, AnalysisData Input:

Space transport unit Surveillance system

Expected Condition: All passengers aboard space transport unit are under surveillance at all times.

170

Level: System System Tested: Surveillance System Identifier of Test: S-SEC 02Test objective: Ensure a record of surveillance on the space transport unit is kept for at least 24 hours Identifier of Requirement Tested: STU_SuC02Verification Method: Demonstration, AnalysisData Input:

Space transport unit Surveillance system

Expected Condition: Any moment in the past 24 hours can be replayed by the surveillance system.

Maintenance & Reliability

Level: System System Tested: Maintenance System Identifier of Test: S-MAR 01Test objective: Ensure space transport does not fail less than 1800 hours after a previous failureIdentifier of Requirement Tested: STU_MR01Verification Method: AnalysisData Input:

Space transport unitExpected Condition: Space transport unit has a MTBF of no less than 1800 hours

Level: System System Tested: Maintenance System Identifier of Test: S-MAR 02Test objective: Ensure space transport does not require repair less than 72 hours after a previous repair was madeIdentifier of Requirement Tested: STU_MR02Verification Method: AnalysisData Input:

Space transport unitExpected Condition: Space transport unit has a MTBR of no less than 72 hours

171

Level: System System Tested: Maintenance SystemIdentifier of Test: S-MAR 03Test objective: Ensure space transport does not require maintenance less than 24 hours after any previous maintenance was made.Identifier of Requirement Tested: STU_MR03Verification Method: AnalysisData Input:

Space transport unitExpected Condition: Space transport unit has a MTBM of no less than 24 hours

Level: System System Tested: Maintenance System Identifier of Test: S-MAR 04Test objective: Ensure operator of space transport is capable of making any emergency repairs.Identifier of Requirement Tested: STU_MR04Verification Method: AnalysisData Input:

Space transport unit Operator

Expected Condition: Space transport unit operator capable of making emergency repairs

172





Joyride to Space

Sub-System Analysis ReportVersion 1.1

173

Sub-System Analysis Contents

1 Storage of maintenance equipment................................................................1722 Disposal System.............................................................................................1733 Space transport unit storage hangar...............................................................1734 Ground terminal maintenance hangar............................................................1765 Security of the space transport unit hangar....................................................1776 Fuel Storage...................................................................................................1797 Life Support System......................................................................................1798 Space transport unit exterior..........................................................................1819 Space Navigation...........................................................................................18210 Radio communications...............................................................................18511 Video Communications.............................................................................18512 Communications Antenna..........................................................................18613 Tracking system.........................................................................................18714 Space to ground tracking system...............................................................18715 Propulsion subsystem.................................................................................18816 Launch system runway..............................................................................19017 References:.................................................................................................191

Storage of maintenance equipment

The ground terminal maintenance hangar is used to store all equipment and facilities to be used in the maintenance of a space transport unit. This function was defined as F_6.3 in the functional analysis and includes all three levels of maintenance, those being basic level, intermediate level and advanced level maintenance services. Two feasible options were presented in regards to the storing of maintenance equipment, these were:

1) Space transport unit storage hangar

2) Ground terminal maintenance hangar

Although any space transport unit would spend the majority of its time in the space transport unit storage hangar, it was decided that the more suitable option would be to construct another hangar designated solely for maintenance. Hence the ground terminal maintenance hangar was chosen to be implemented for this reason. To have a maintenance operation that is separate to the storage system has one key advantage, this being that all maintenance operations are carried out away from space transport units which do not require maintenance which in turn reduces the likelihood of an overcrowded workplace for the maintenance staff. Although the cost of constructing two separate hangars will be larger, the advantages of applying the separation between storage and maintenance will outweigh the initial cost burden.

174

Disposal System

The system lifecycle is highly dependant on the effectiveness of the disposal system. The disposal system is not only used at retirement but also used in the sustainability of the project. The disposal system encompasses three aspects of waste from any retiring / failed equipment, these being hazardous waste, recyclable waste and non recyclable waste as defined in F_7.0. The disposal system is responsible for the separation and the eventual disposing of all products which are no longer required in their current function. The disposal system will therefore cover not only the space transport unit but also the ground terminal and all other supporting facilities. The disposal system could be operated in two ways as described below:

1) Disposal carried out internally

2) Disposal carried out by a hired company

There are obvious advantages and disadvantages to each of these solutions. Cost is of high importance in all business areas however, the hiring of an external company to remove any waste would be advantageous with regard to any government regulations. For example the employment of a professional waste removal company would eliminate the need for our system to comply with the associated government regulations which are required to be met when dealing with hazardous waste products. The recycling of useful parts however would be more easily accomplished within the system as this can include small tasks which maintenance staff employees are capable of achieving. With this in mind the solution to a choice of waste management through disposal of the system is best suited to be undertaken internally. This eliminates the cost of hiring an external company and also allows recyclable waste to be reused or sold more efficiently as described in F_7.1, F_7.2 and F_7.3.

Space transport unit storage hangar

The space transport unit must be stored in a hanger when not in use. The appropriate hanger must be used to cater for all space transport vehicles and for the weather conditions. As defined in function F_1.4.2The system requirements state that the ground terminal shall have a hangar capable of storing at least 5 space transport units. With the space transport units having the following dimensions:

Wing span: 28.4mOverall length: 37.8mTail height: 8.9m

With these dimensions the hangar must be , this gives sufficient clearance for the height of the vehicle and 2 meters of space around each vehicle for movement.

175

Hangar StyleIt is necessary to have the correct hangar style for the space transport unit, the typical styles are as follows.

-Segmental Tied HangarThe segmental tied hangar is constructed of segmental tied trusses which are able to span up to 200m or more.

-Glove HangarGlove hangars are an economic solution to aircraft storage, where economy is achieved by the hangars fitting tightly around the aircraft. This reduces the amount of materials used and inturn lower costs. The doors are customised to fit specific aircraft and the nose/fuselage section of the hangar is reduced in size. The smaller internal space also makes the building cheaper to cool or heat. This design does not cater for the space transport unit. The small dimensions only allows for one Space Transport Unit, this would mean that at least 5 hangars are to be constructed for all space transport units to be stored, it would also be difficult to perform maintenance on the space transport unit due to its fitting nature.

-Spine Truss HangarSpine truss hangars have the dimensions of very short and wide. It is a cost effective solution, however it would not be able to cater for the Space Transport Unit due to the shallow depth of the hangar.

176

-Cantilever HangarCantilever hangars are ideal mostly for long extensions. It needs a substantial office/workshop zone behind the hangar to act as a counterweight. The hangar can extend as long as one kilometre but is restricted to the length/size of the office/workshop behind the hangar. This option would seem feasible since it is cost effective and meets the required dimensions for the Space Transport Unit storage, however it is not know whether the counterweight building behind the hangar has the required length for the size of the hangar.

-Butterfly HangarThe butterfly hangar is made for time efficiency. It needs an apron on both sides, which allows fast access to the stored vehicle. This design is a possible option, however the cost of the butterfly hangar is higher than other designs.

Hangar Roofing/Wall Cladding

The material the hangar is composed of is necessary to analyse. It shields the Transport Unit from environmental effects and gives it security and protection. It is desirable for the temperature of the hangar to be kept at a constant room temperature. This will decrease expansion/contraction of the facility and will be an easier environment to work in. There are three different types of roof/wall cladding for different situations.

177

Single SkinSingle skin sheeting is the most economic material suitable for roof/wall cladding. It is composed of a single layer of metal over the steel frame, providing little insulation.The single skin is a possible option, however it lacks insulation therefore the hangar will reach high temperatures when it is hot and low temperatures when it is cold. This is an undesirable effect.

Double SkinDouble skin sheeting is a more expensive material. It is composed of an outer material made of galvanised iron with a small insulation gap and a fibre glass inner skin. It reduces condensation, temperature change and the chance of leakage. It is the most cost effective solution for insulation.

Composite Double SkinThe Composite Double Skin provides more insulation than the double skin. It is composed of a sandwich panel with a foam core for insulation. It is more expensive than the double skin but is a greater insulator.

Design Criteria for Space Transport Unit Storage System

While all hangars were analysed only the segmental tied hangar and the butterfly hangar were physically able meet the size requirements of the Space Transport System. The advantage of the segmental tied hangar is the financial cost while it may take longer to get to the runway. While the butterfly hangar has a significantly higher cost however allows efficient transport due to aprons being on both sides. The Space Transport Systems flights are not as regular as normal flights therefore time efficiency is not a great factor. Therefore the segmental tied hangar is preferred.

From the three skin materials the most effective when taking strength, insulation and cost into account is the Double Skin. It is a mid ranged material that provides adequate insulation with a U value from 0.45W/oC/m2 - 0.2W/oC/m2. The composite double skin is a more expensive alternative however the cost is significantly higher for a small difference in insulation. While the single skin provides an insignificant amount of insulation.

Ground terminal maintenance hangar

The Ground Terminal maintenance equipment must be stored in a maintenance hanger when not in use. The appropriate hanger must be used to cater for all ground terminal maintenance equipment and for the weather conditions. The system requirements state that the Ground Terminal maintenance hangar shall store all ground terminal maintenance equipment and have the dimensions of at least

. As defined in functional analysis F_1.4.2

178

The maintenance hangar must be kept at a constant temperature of 25oC this is to maintain the life of the equipment and allow for a comfortable working environment. Therefore the skin material for the roofing and wall cladding must have insulation. The room must also have air conditioning and heating to assist temperature control.

Hangar Roofing/Wall CladdingThe material the hangar is composed of is necessary to analyse. It shields the maintenance equipment from environmental effects and gives it security and protection. It is desirable for the temperature of the maintenance hangar to be kept at a constant room temperature. This will decrease expansion/contraction of the facility, prolong the equipment life and will be an easier environment to work in. There are three different types of roof/wall cladding for different situations.

Double SkinDouble skin sheeting is a more expensive material. It is composed of an outer material made of galvanised iron with a small insulation gap and a fibre glass inner skin. It reduces condensation, temperature change and the chance of leakage. It is the most cost effective solution for insulation.

Composite Double SkinThe Composite Double Skin provides more insulation than the double skin. It is composed of a sandwich panel with a foam core for insulation. It is more expensive than the double skin but is a greater insulator.

Design Criteria for Space Transport Unit Storage System

From the two skin materials the most effective when taking strength and insulation into account is the Composite Double Skin. It is provides higher insulation than the double skin but at a higher cost.

Security of the space transport unit hangar

For security surveillance of the space transport unit hangar, there are 2 kind of feasible security surveillance systems that could be considered for this application, these are:

1) The use of CCTV surveillance

2) 24 hour security guards

CCTV (Closed-circuit television) is a television system that uses surveillance cameras to do the video surveillance. The CCTV is different from broadcast television in that all components are directly linked via cables. The use of CCTV is to deter unauthorised people from entering into the space transport unit hangar at all times. However the CCTV

179

also can be placed in remote area or surround the space transport unit hangar which enables the premises to be monitored at all times. An advantageous function of the CCTV is that, it can record the entire area at all times giving us the best surveillance. We can then play back the recording to see what had happened before. With function of zoom, we can see more clearly, which can help police to identify intruder. The CCTV can provide surveillance 24 hours non-stop everyday, this will provide 24 hours safety of the space transport unit hangar.

With advances in technology nowadays, we can install a security door which can be used to restrict unauthorised person to enter to the space transport unit hangar. The security door can design to scan the person’s identification card, fingerprint, eyes, and etc. Because of the CCTV surveillance and security doors, we can leave the space transport unit hangar without the need for a security guide to keep it safe 24 hours a day.

Security guards can keep the place safe, but they couldn’t provide complete surveillance for all of the surrounding area at the same time. It is unfeasible to employ large numbers of security guards to surround the space transport unit hangar at all times, this is just wasting manpower and in turn money. The safety they provide can not be guaranteed at 100%, because the guards are capable of human error. This is why the use of CCTV is the recommended solution to security.

180

Fuel Storage

Storage of fuel for the space transport units is vital in the safety and efficiency of the entire system. Although many options for fuel storage are available we can narrow our analysis down to the use of fuel tanks and more precisely whether they are located:

1) Above ground

2) Below ground

In a similar fashion to any regular fuel station the choice was made to go ahead with the plans for below ground fuel tank construction. The fuel storage facilities consist of fuel pumps and underground tanks located under the ground terminal. The facility makes the fuelling process more convenient. It allows more space transport units to re-fuel at the same location without wasting any time.Fuel storage systems were placed underground for three primary reasons:

Reduce fire and explosion risks. Reduce evaporation losses. Reduce condensation problems

Furthermore, problems like rain or surface water accumulation in the impervious containment systems can be avoided.

Surrounding buildings to the fuel storage system could be the Ground terminal, hangars, launching base etc. Fuel is highly combustible. It can results in serious fires and explosions which will damage the surrounding buildings or cause severe injury to people. The chances of fire or explosion can be reduced by following safety precautions and by keeping fuel storage facilities in top condition.

Large amounts of fuel are needed to operate the space transport units. The storage tank should be able to store such amount in order to ensure that fuel supply is always ready for space transport unit. Hence an underground system is more appropriate than an above ground system as the large tanks are hidden as compared to taking up space on the surface where hazards could occur.

Life Support System

Atmosphere

The SiO2 Tiles: These tiles protect the spacecraft upon re-entry into earth’s atmosphere. The space shuttles are protected by special silica tiles. Silica (SiO2) is an incredible good insulator. It is possible to hold a space shuttle tile by the edge and then heat up the centre of the tile with a blow torch. The tile insulates so well that no heat makes it out to the edges [4].

181

The Silica titles are the best option to fulfil this requirement, as per they have been widely in use before, have no reliability issues and have no competition.

Temperature

Space temperatures have extremely cold weather conditions and it is constantly changing in different parts of the orbit. However, the electronic equipment generates more than enough heat for the ship. The problem is getting rid of the unwanted heat and do that we need temperature control system have to these major functions.

Distribute heat where it is needed on the orbiter (mid-fuselage and aft sections) so that vital systems do not freeze in the cold of space [10].

Electrical heaters - use electrically-heated wires like a toaster to heat various areas [10].

Active methods - more complex, use fluid to handle large heat loads, require maintenance [10].

Cold plates - metal plates that collect heat by direct contact with equipment or conduction [10].

Heat exchangers - collect heat from equipment using fluid. The equipment radiates heat to a fluid (water, ammonia) which in turn passes heat on to Freon. Both fluids are pumped and recirculated to remove heat [10].

Pumps, lines, valves - transport the collected heat from one area to another.

Radiators - located on the inside surfaces of the cargo bay doors that radiate the collected heat to outer space [10].

Heat released from the Freon causes the ammonia to boil [10].

Because these methods have been used and tested by NASA. Therefore is no other better solution of our currently technology are better and more efficiency therefore our system will use them the same way as NASA does.

Pressure

The airlock is normally located inside the mid deck of the spacecraft's pressurised crew cabin. It has an inside diameter of 63 inches, is 83 inches long and has two 40-inch- diameter D-shaped openings that are 36 inches across. It also has two pressure-sealing hatches and a complement of airlock support systems. The airlock's volume is 150 cubic feet. Airlock pressurisation is controllable from the orbiter crew cabin mid deck and from inside the airlock. It is performed by equalising the airlocks and cabin's pressure with equalisation valves mounted on the inner hatch. The airlock is depressurised from inside the airlock by venting the airlock's pressure overboard. The two D-shaped airlock hatches open toward the primary pressure source, the orbiter crew cabin, to achieve pressure-assist sealing when closed [11].

182

Due to NASA’s air-lock system already in use in most spacecraft, its seems the most logical answer to this requirement as it has been used widely before and has no reliability issues and has no competition.

Crew compartment cabin pressurisationThe cabin is pressurised to 14.7 psi, plus or minus 0.2 psi, and maintained at an average 80-percent nitrogen and 20-percent oxygen mixture by the air revitalisation system. Oxygen partial pressure is maintained between 2.95 and 3.45 psi, with sufficient nitrogen pressure of 11.5 psi added to achieve the cabin total pressure of 14.7 psi, plus or minus 0.2 psi. The pressurisation system consists of two oxygen systems and two gaseous nitrogen systems. The two oxygen systems are supplied by the PRSD oxygen system, which is the same source that supplies oxygen to the orbiter fuel cell power plants. The PRSD cryogenic supercritical oxygen storage system is controlled by electrical heaters within the tanks and supplies the oxygen to the ECLSS pressurisation control system at a pressure of 835 to 852 psi in a gaseous state. The gaseous nitrogen supply system consists of two systems with two gaseous nitrogen tanks for each system. The nitrogen storage tanks are serviced to a nominal pressure of 2,964 psi at 80 F. If the auxiliary gaseous oxygen supply tank is installed, it is serviced to 2,440 psi at 80 F and stores 67.6 pounds of gaseous oxygen to provide high flow along with gaseous nitrogen. It would maintain the crew cabin at 8 psi with oxygen partial pressure at 2 psi. For normal on-orbit operations one oxygen and nitrogen supply system is used. For launch and entry both oxygen and nitrogen supply systems are used in addition to pressurisation of the airlock [11].

Because crew compartment cabin pressurisation is the most excellent and the only pressure system that are currently been used to maintain an atmospheric pressure by NASA. Therefore is no other better solution of our currently technology are better and more efficiency therefore our system will use them the same way as NASA does.

Space transport unit exterior

Silica FibresThe silica fibres are derived from common sand and are made of high purity fibres (2 to 4 microns in diameter, as long a 1/16th inch) derived from common sand. The tile containing silica fibres is frame cast to form soft, porous blocks to which a colloidal silica binder solution is added. The blocks are then dried, sintered at 2300ûF.Machined tiles then go to ovens for baked-on coatings. These tiles experience re-entry heating up to 2300ûF and are coated with white silica compound which includes alumina to better reflect the heat of the Sun on-orbit. All tiles are treated with a waterproofing polymer [13].

High temperature reusable surface insulation tilesThis HRSI tiles are made from a low density and high purity silica 99.9% and fibres are derived from command sand of 1 to 2 mils tick. The insulation that made ridged by

183

ceramic bonding. The weigh of this tiles about 9 pounds per cubic foot. The thickness is determined by the heat load encounter during entry. HRSI tiles are vary in size and shapes in the close out areas on the orbiter. The HRSI tiles withstand on orbit cold soak condition and repeated heating and cooling thermal shock and extreme acoustic environments about 165 decibels at launch.Because HRSI tiles are small, have been used widely, and are reliable and safe, these are to be used. For the controller, because a NASA air- system has been widely used before has no reliability issues and has no competition; this system is to be used.

Space Navigation

Space vehicle navigation comprises two aspects:

(1) Knowledge and prediction of the space vehicle’s position and velocity, which is orbit determination, and

(2) Firing the rocket motor to alter the space vehicle’s velocity, this is flight path control.

The primary system used throughout the world for space-based positioning, navigation, and timing is the Global Positioning System (GPS), a constellation of satellites providing continuous civil service free of direct user charges to an unlimited number of users for peaceful purposes. Additionally, GPS is critical to a wide range of civilian activities and represents a fundamental component of the global information infrastructure [15]. Figure 1.1 below shows the locations of the existing placements of GPS systems.

To determine the orbital position of the space vehicle, the imaging instruments on board the vehicle can use them to observe the spacecraft's destination planet or other body, such as a satellite, against known landmarks. The observations are carefully planned and up linked far in advance as part of the command sequence development process. The primary body often appears in these images, which are known as opnavs, so that the background stars will be clearly visible. When the opnav images are down linked in telemetry (TLM) they are immediately processed by the navigation team. Interpretation

184

of opnavs provides a very precise data set useful for refining knowledge of a space vehicle’s trajectory as it approaches a target, or otherwise addressed as flight control.

There are several types of navigational systems that could be used for space navigation. This comprises of:

1) Galileo satellite navigation2) GLONASS navigation system

3) Quasi-Zenith Satellite System

4) Beidou satellite navigation

5) Euridis navigation

6) Multifunctional Transport Satellite (MTSAT-1R)

The Galileo satellite navigation program is a joint initiative between the European Union and the European Space Agency to build and operate a 30-satellite constellation that provides similar capabilities to GPS, but as a commercially-operated, for-profit venture, not a public good. The system will offer four distinct positioning, navigation, and timing services and one search and rescue service.

GLONASS is a Russian space-based navigation system comparable to the U.S. GPS system. The fully operational system will contain 21 satellites in 3 orbital planes, with 3 on-orbit spares. The GLONASS system is managed for the Russian Federation Government by the Russian Space Forces providing benefits to civil users through a variety of applications. The GLONASS system has two types of navigation signals: standard precision navigation signal (SP) and high precision navigation signal (HP). SP positioning and timing services are available to all GLONASS civil users on a continuous, worldwide basis. On December 10, 2003, three GLONASS spacecraft were placed into orbit in Plane 1, including one of the new generations of GLONASS-M satellites. The addition of these three satellites will bring the GLONASS constellation to a total of 11 operational satellites.

The Quasi-Zenith Satellite System [Jun-Ten-Cho in Japanese] is a constellation of at least three satellites, configured such that one of them is always positioned at a high elevation angle over Japan. RF transmission will not be obstructed by tall buildings or mountains, because one of satellites will always remain near high in the sky over Japan at all times. As a result, signal degradation caused by building blockage and multiple signal paths will be less frequent, making the whole system ideal and reliable for mobile data communication and broadcasting. The system is also expected to increase accuracy to GPS users in the eastern Asia area.

Although China has not yet established operational satellite navigation and positioning network, research for such a system has been underway for many years, and a future

185

space-based navigation capability is an acknowledged goal. Beidou ('Big Dipper') is the satellite component for the independent Chinese satellite navigation and positioning system. The Beidou satellite navigation and positioning system are consists of two satellites in geosynchronous orbit. The final Beidou constellation will include four satellites, two operational and two backups. Together with the ground stations, the Beidou system will provide navigation and positioning signals covering the East Asia region. However, to provide global signal coverage, satellites flying in other orbits around the world must complement the system.

The Euridis satellite navigation system developed by Alcatel Space, as Prime Contractor, provides France's initial contribution to the EGNOS programme, the European component in the first-generation worldwide navigation satellite system (GNSS-1). The system was ordered by CNES. In the context of the EGNOS programme, Euridis provides users with a permanent navigation signal in addition to those supplied by the GPS (American) and GLONASS (Russian) constellations. This signal significantly increases the availability and integrity of the user's position. Euridis navigation service will be available in the Inmarsat 3 AOR-E satellite footprint area [18].

The Multifunctional Transport Satellite (MTSAT-1R) multi-mission space programme comprises a space segment which will eventually consist of two geostationary satellites and an earth segment. Alcatel Space is playing a leading role in this aeronautical mission and in the production of traffic and earth control stations [18]. MTSAT-1R is being built for Japan and will be the first air navigation and telecommunications space system to meet the CNS/ATM concept adopted by the International Civil Aviation Organisation (ICAO) in 1991.

Design Criteria for Space Rocket navigational System

For the joyride to Space program, there are 2 feasible navigational systems that could be considered for this application, namely:

1) Galileo satellite navigation2) Euridis satellite navigation system

While most of the other satellite navigational systems are publicly offered, the Galileo has a 30-satellite constellation, which offers the most coverage among other satellite navigational system. The added feature making this navigational system attractive is also the ability to provide a search and rescue service, which is an added safety feature. However, the cost factor needs to be addressed when choosing this system as it is a commercial package.

The Euridis satellite navigation system takes advantage over the other two by combining both the GPS (American) and GLONASS (Russian) constellations. However, it does not provide search and rescue services.

186

Radio communications

In voice communication, space transport should provide communication via UHF and HF transmission allow to transmitting data between space transport and ground. All voice in HF frequency is in AM mode. The UHF transmission provided high transmission rate which for voice and video communication. There are some frequencies which need to consider for UHF transmission provided by Scott [19]:

a. 1831.787 - US Dept of Defence Uplink to Space Shuttle[19]b. 2085.6875 - S Band Uplink to Space Shuttle [19]c. 2106.4 - Command Uplink [19]d. 2119.8 - Space Shuttle - Payload Link Frequency [19]e. 2217.5 - TDRS Satellite link [19]f. 2250.0 - WFM - Analog Data and Telemetry during Space Shuttle Launch [19]g. 2265.0 - S Band Downlink [19]h. 2287.5 - ISS Zarya Module / Space Shuttle [19]i. 2298.8 - Payload - Space Shuttle Link Frequency [19]

We have chosen the option ‘i’ because the higher frequencies range of transmission, the more efficiency data transmission on communication. Therefore, this would be providing customers to enjoy quality and high performance of voice and video communication between ground and space transporter. However, there are some HF frequencies provided by Scott [19] which is showed below:

a. 8.364 - Morse Code heard during recovery of Russian Space Vehiclesb. 9.019 - AM - Used for Vostok 1 [19]c. 10.003 - Common Recovery Beacon frequency [19]d. 15.008 - AM - Early Salyut / Soyuz [19]e. 15.016 - AM - Mercury 7 Frequency [19]f. 15.763 - AM - Used for Vostok 2 [19]g. 17.365 - AM - Used for the Voskhod missions [19]h. 18.035 - AM - Used for Voskhod / early Soyuz missions [19]i. 18.060 - AM - Old Soyuz frequency / Used During recovery of Russian [19]

We found that the HF feasible frequencies for HF transmission are 15.016 MHz. The reason to choose this because it is been used in space craft called “Mercury 7” and we decide our space transporter is more suitable using this frequencies band which is 15.016 MHz in AM mode for voice communication.

Video Communications

The space transport should provide at least 12 inches of LCD monitors for video communication. We decided to use 12 inches of LCD screens monitors which able to send quality video images according to specification of LCD monitors provided by Caltron Industries [20]. The following specification is showed as below:

187

LCD PanelDisplay Panel 12.1" TFT LCD

Pixel Pitch 0.3075(H) x 0.3075(V) mm

Max. Resolution 800 x 600 SVGA

Contrast Ratio 500:1 (typical)

Brightness 400 cd/m2

Uniformity 80% (minimum)

Backlight MTBF 50,000 hours (minimum at 25°C)

Response Time 35 ms (typical)

Display Colours 262 thousand

Viewing Angle (typical) ±70°L/R, +65°U,-45°D

Video and PowerOSD Controls Brightness, Contrast, Phase, Clock, Colour, H&V position, Auto-

tune, RecallInput Signal RGB analog 0.7V peak to peak

Video Input Connector D-sub 15 pin analog

Scan Frequency 24-54kHz horizontal scan, 50-90 Hz vertical refresh

Power Supply AC/DC 12V power adapter, universal 100-240 Volts

Mechanical and EnvironmentOperating Temperature 0[32]-50[122] °C[°F]

Storage Temperature -20[-4]-60[140] °C[°F]

Humidity 85% (maximum)

Dimensions (WxHxD) 320[12.6] x 323[12.7] x 146[5.8] mm [inch]

Net Weight 3.8[8.4] Kg [Lb]

Figure 1: Specification for 12” LCD screens (Courtesy by Calthorn Industries) [20]

Communications Antenna

The space transport communications system should have at least 2 antennas for tracking the signal from ground to space transport. The function of antennas is to receive and transmit the data between ground and space transport. According to ATCI [21], there is specification which related to antenna on space transport:

For Simulsat 5• Most Frequently Installed Model Worldwide• Standard and High Mount Available• C and Ku-Band Capability• Performs equivalent to 4.5 m. C-Band Prime Focus Parabolic Antennas• Receives, with uniform performance, signals from all satellites within a 70° view arc.• Requires Less Space – Takes up the same space as 3 parking spaces.

188

For Simulsat 7• ATCi’s largest Simulsat model – geared toward large cable systems and teleports.• Standard and High Mount Available• More arc coverage – receives, with uniform performance, signals from all satellites within a 75° view arc.• C and Ku-Band Capability• Performs equivalent to 6 M. C-Band Prime Focus Parabolic Antennas.

We decided to use Simulsat 7 because it is more reliable and able received strong signals. Therefore, it might improve the data transmission as well.

Tracking system

The space transport communication system provides a tracking subsystem via C-band. According to Telesat [22], there is some specification which provided as following:

Option 1

C-band Channels (#) 36

Bandwidth 36 MHz

C-band Total RF Power 1.44 kW

Total Bandwidth 6 x 500 MHz

Courtesy by Telesat [22]

Option 2

C-band Channels (#) 36

Bandwidth 38 MHz

C-band Total RF Power 1.49 kW

Total Bandwidth 6 x 500 MHz

Courtesy by Telesat [2]

We have chosen option 1 because the power consumption is less and the C-band channel will be equally same as option 1. So, there might cut the cost also to build tracking system via C-band.

Space to ground tracking system

The space to ground communication provides tracking system via S-band. Paul J. Marsh [23] defined the definition of S-band is the range of frequencies from around 1.55 GHz through to 3.9 GHz. There is other more well knows devices that transmit at s-band. These include microwave ovens on 2.450 GHz, and the new breed of wireless video-senders which also operate around the 2.4 GHz mark. Other services to be found include video downlinks from police helicopters, outside broadcast events and blimp type balloons with cameras on board. The initial success of the helical antenna for L-band led me to redesign the antenna for s-band. After spending some time researching the various downlinks on s-band, a left hand circular antenna was build to feed the dish, resulting in right hand circular reception. The advantage of the helical is its wide bandwidth, having a minus 20% and plus 30% bandwidth with respect of the design frequency. The centre

189

frequency I chose is 2.25 GHz, so the antenna will be usable from 1800 MHz to 2925 MHz. This is quite wideband, but I'm using it round the 2.2 GHz mark, with about 200 MHz either side. This picture is not of a helical but of the S-band dipole used to test. [23]

Figure 3: Example photo captured by S-band satellite. (Courtesy by Paul J. Marsh )[23]

From here, our team decided to use the tracking system for S-band compared to other bands due to costly and low quality resolution of images which performed from other bands. It provides a very clear picture which captured by using S-band satellite.

Propulsion subsystem

The propulsion system is required to be able to provide at least 95kN of thrust. The TX-354-3, RL-50, Airane-HM-7B, Vinci, and Vulcain, all meet this requirement. From the specifications we have chosen to use the Vinci Engine.

VinciDesigner: Astrium. Propellants: Lox/LH2 Thrust(vac): 15,700 kgf. Isp: 467 sec. Chambers: 1. Country: Germany. Status: In Development. First Flight: 2006.

Vulcain Designer: SEP. Propellants: Lox/LH2 Thrust(vac): 109,619 kgf. Thrust(vac): 1,075.00 kN. Isp: 431 sec. Isp (sea level): 326 sec. Burn time: 605 sec. Mass Engine: 1,300 kg. Diameter: 2.00 m. Length: 3.00 m. Chambers: 1. Chamber Pressure: 102.00 bar. Area Ratio: 45. Oxidiser to Fuel Ratio: 6.2. Thrust to Weight Ratio: 84.318. Country: France. Status: In Production. First Flight: 1996. Last Flight: 1998. Flown: 4. RL-50Designer: Pratt and Whitney. Propellants: Lox/LH2 Thrust(vac): 29,500 kgf. Thrust(vac): 290.00 kN. Isp: 472 sec. Mass Engine: 500 kg. Chambers: 1. Oxidiser to Fuel Ratio: 5.5. Thrust to Weight Ratio: 59. Country: USA. Status: Development.

TX-354-3 Manufacturer Name: TX-354-3. Other Designations: Castor 2. Designer: Thiokol. Gross Mass: 4,424 kg. Empty Mass: 695 kg. Propellants: Solid Thrust(vac): 26,402 kgf. Thrust(vac): 258.90 kN. Isp: 262 sec. Isp (sea level): 232 sec. Burn time: 37 sec. Diameter: 0.79 m. Length: 6.04 m. Chambers: 1. Area Ratio: 7.45.

190

Country: USA. Status: In Production. First Flight: 1960. Last Flight: 1994. Flown: 1045. Comments: Used in Scout A; Delta E; H-1-0; Castor 2. License built in Japan for H-1.

The Vinci specification more closely matches the thrust we require 155kN compared to 200+ for the other engines. This engine will provide enough thrust to lift the Space transport unit to space and accelerate at a speed which is comfortable for the passengers. It also has an additional safety feature of being able to be restarted during flight. The Specifications for the Engines can bee seen below in Figure Engine1.

Applications Ariane 5 upper stage ESC-B

Schedule start of development in 1999, first test firings in late 2001, first flight in 2005Dry Mass 480 kgLength 420 cmMax Diameter 210 cmMounting Method gimballed for pitch/yaw controlOxidiser LO2

Fuel LH2

Mixture Ratio (O/F): 5.5:1 to 6.5:1

Turbo pumpSeparate fuel/oxidiser expander type closed cycle turbo pumps. Hydrogen turbo pump: 85,000 rpm, 1800 kW Oxygen turbo pump: 18,000 rpm, 300 kW

Isp 464 sec vacuumThrust 155 kN vacuum

Cooling MethodUpper part of nozzle is regeneratively cooled, extension made of composite material is radiatively cooled..

Combustion Chamber Pressure

60 atmospheres

Combustion Chamber Ignition

electric igniter, restartable in flight

Remarks will likely use Snecma developed nozzle extension of RL-10B-2

Table Propulsion1- Main engine Vinci Specifications

The thrusters for the propulsion system will be used to maintain the stability of the space transport unit. The Thrusters we have considered are the DOK-10 and CHT-5.

DOK-10Designer: Isayev. Propellants: Hydrazine Thrust(vac): 1 kgf. Thrust(vac): 0.010 kN. Isp: 229 sec. Burn time: 1,500 sec. Mass Engine: 1 kg. Chambers: 1. Chamber Pressure: 10.00 bar. Area Ratio: 46. Thrust to Weight Ratio: 1.7. Country: Russia. Status: In Production. CHT-5Designer: EADS. Propellants: Hydrazine Thrust(vac): 0.006 kN. Isp: 228 sec. Mass Engine: 0.22 kg. Chambers: 1. Chamber Pressure: 22.00 bar. Country: United States. Status: In Production.

Both thrusters are fuelled by Hydrazine and are able to provide the required thrust. We have chosen to use the CHT-5 thrusters as they are lighter in weight. This enables us to be more fuel efficient and decrease total running costs of the transport unit. Specifications can be seen in table Space2

191

Table Propulsion2. Thrusters Specifications CHT-5

The propellent used to fuel the Engines in Liquid Hydrogen and liquid Oxygen. The propellent used to fuel the thrusters is Hydrazine. Fuel is required to be kept storage tanks that comply with any government regulations and safety procedures relating to the handling and storage of such chemicals. These tanks are required to be large enough to accomplish 1.5 space flights.

Launch system runway

According to Simon Rowland [1], for a 200 passenger space transport, the space transporter runway should withstand 830 tonnes, Our team has decided to withstand approximately 850 tonnes on the runway.

The runway should be able to take all specifications and requirements such as runway shall at least withstand a static weight of 120 tonnes. According to Sydney airport [1], two runway surface specifications which are RWY 07-25 and RWY 16L-34R showing the following:

RWY 07-25 (Option 1)Width: 45 mLength: 2529 mPavement: Asphalt/FlexibleSubgrade: High Strength Characteristics: Grooved

RWY 16L-34R (Option2)Width: 45 mLength: 2438 mPavement: Asphalt/FlexibleSubgrade: High Strength Characteristics: Grooved

192

Refer to both runways above, our team has decided that option 2 is more reliable and easy to maintain runway. Therefore, the characteristic of runway shall be treated with groove skid resistant material and the length of the runway shall be approximately in 2.5 Km.

References:[1] ‘Space travel – essential human requirements for living in space’, ’http://www.tomatosphere.org/engmanual/space_travel2.html, 2005, accessed on 14.10.05

[2] Rod.m, ‘gauge pressure of space’, http://www.newton.dep.anl.gov/askasci/eng99/eng99149.htm, 2005, accessed on 13.10.05

[3] Rod.m, ‘d.12 what is the temperature in space?’ http://www.faqs.org/faqs/astronomy/faq/part4/section-14.html, 2005, accessed on 19.10.05

[4] How stuff works, ‘meteors burn up when they hit the earth's atmosphere. why doesn't the space shuttle?’ http://science.howstuffworks.com/question308.htm, 2005, accessed on 20.10.05

[5] Fiu, ‘flight environment’ http://www.allstar.fiu.edu/aero/fltenv2.htm, 2005, accessed on 25.10.05

[6] John f. Graham, chapter 3 – where does space begin? http://www.space.edu/projects/book/chapter3.html, 1995, accessed on 19.10.05

[7] author unknown, ‘tight control of the space shuttle/spacelab environment’, http://www.nsbri.org/humanphysspace/focus1/spaceshuttle-environment.html, 2005, accessed on 09.10.05

[8] Robert AB ‘spacecraft systems’, http://www.braeunig.us/space/systems.htm, 2005, accessed on 19.10.05

[9] TK hot tips, ‘the colombia shuttle tragedy’, www.tki.org.nz/r/hot_topics/columbia_e.php, 2002, accessed on 12.10.05

[11] Dumoulin. j, ‘ environmental control and life support system ’ http://science.ksc.nasa.gov/shuttle/technology/sts-newsref/sts_eclss.html, 1999, accessed on 19.10.05

[12] Sea-bird electronics, ‘minimising strain gauge pressure sensor errors’, www.seabird.com/application_notes/an27.htm, 2001, accessed on 19.10.05

[14] Sun Microsystems, ‘environmental requirements’, http://docs.sun.com/source/816-1613-13/chapter2.html, 2003 accessed on 12.10.05

[15] U.S Embassy in Mexico, ‘space-based positioning, navigation, and timing systems,

http://docs.sun.com/source/816-1613-13/chapter2.html

http://www.seabird.com/application_notes/AN27.htm

http://science.ksc.nasa.gov/shuttle/technology/sts-newsref/sts_eclss.html

http://science.ksc.nasa.gov/shuttle/technology/sts-newsref/stsref-toc.html#sts_eclss

http://www.tki.org.nz/r/hot_topics/columbia_e.php

http://www.braeunig.us/space/systems.htm

http://www.nsbri.org/humanphysspace/focus1/spaceshuttle-environment.html

http://www.space.edu/projects/book/chapter3.html

http://www.allstar.fiu.edu/aero/fltenv2.htm

http://science.howstuffworks.com/question308.htm

http://www.faqs.org/faqs/astronomy/faq/part4/section-14.html

http://www.newton.dep.anl.gov/askasci/eng99/eng99149.htm

http://www.tomatosphere.org/EngManual/space_travel2.html

http://www.usembassy-mexico.gov/texts/et050112gps.html, 2001, date accessed: 15 October 2005

[16] Fisher, d,’spacecraft navigation’, http://www2.jpl.nasa.gov/basics/bsf13-1.html,date accessed 15.10.05

[17] The aerospace co-operation,’ charting a course toward global navigation’, http://www.aero.org/publications/crosslink/summer2002/01.html, 2004, date accessed: 15.10.05

[18] Alcatel navigation systems, ‘navigational systems’,http://www.alcatel.com/space/programmes/nav/navsystems.htm, 2001date accessed 01.10.05

[19] Scott, ‘useful frequencies’, http://members.aol.com/k1ela/page55.html, 2005, accessed on 28.10.05

[20] Calthorn industries, ’12 inches LCD monitors’, http://www.caltronind.com/lcd_monitors/monitor_12_inch.html, 2001, accessed on 10.10.05

[21] Atci, ‘antennas’, http://www.atci.com, 2005, accessed 28.10.05

[22] telesat, ‘c band’, http://www.telesat.ca/news/speeches/speeches98-01.htm, accessed 28.10.05

[23] Marsh PJ, ‘s-band tracking system’, http://ourworld.compuserve.com/homepages/pjmarsh/sband.htm, 2005, accessed 28.10.05

[24] Rowland S, ‘analysis of air launched lunar passenger spacecraft’,http://www.eagle.ca/~simon/femts.html, 2005, accessed 28.10.05

[25] Sydney airport, ‘runway information’, http://www.acay.com.au/~willt/yssy/enthus/runways.html, 2005, accessed 28.10.05

[26] Aircraft hangars, ‘aircraft hangars - reid steel’,http://www.aircraft-hangars.com/, 2005, accessed 28.10.05

[27] author unknown, ‘venik’s aviation’, http://www.aeronautics.ru/archive/reference/russian_space_engines/russian_space_engines_4.htm, 2005, accessed 12.10.05

[28] Wade M, ‘encyclopaedia astronautica’, http://www.astronautix.com/engines/index.htm, 2005, accessed 26.10.05

[29] Zandbergen, ‘performance and operating data for typical rocket engines’ http://dutlsisa.lr.tudelft.nl/propulsion/data/rocket_motor_data.htm, 05.05.03, accessed 26.10.05

[30] Artemis society international, ‘Boeing north American rocket engines’, http://www.asi.org/adb/04/03/09/01/bna.html, 2004, accessed 27.10.05

http://www.asi.org/adb/04/03/09/01/bna.html

http://dutlsisa.lr.tudelft.nl/propulsion/data/rocket_motor_data.htm

http://www.astronautix.com/engines/index.htm

http://www.aeronautics.ru/archive/reference/russian_space_engines/russian_space_engines_4.htm

http://www.aeronautics.ru/archive/reference/russian_space_engines/russian_space_engines_4.htm

http://www.aircraft-hangars.com/

http://www.acay.com.au/~willt/yssy/enthus/runways.html

http://www.eagle.ca/~simon/femts.html

http://ourworld.compuserve.com/homepages/pjmarsh/sband.htm

http://www.telesat.ca/news/speeches/speeches98-01.htm

http://www.atci.com/

http://www.caltronind.com/lcd_monitors/monitor_12_inch.html

http://members.aol.com/k1ela/page55.html

http://www.alcatel.com/space/programmes/nav/navsystems.htm

http://www.aero.org/publications/crosslink/summer2002/01.html

http://www2.jpl.nasa.gov/basics/bsf13-1.html

http://www.usembassy-mexico.gov/texts/et050112gps.html





Joyride to Space

Portfolio ReportVersion 1.1

Portfolio Report Contents

1. INTRODUCTION..................................................................................................1942. Navigation..............................................................................................................1953. Propulsion System..................................................................................................1964. Launch System.......................................................................................................1975. Life Support............................................................................................................1996. Maintenance...........................................................................................................2017. Storage....................................................................................................................2028. Service....................................................................................................................2069. Reference................................................................................................................209

1. INTRODUCTION

A Portfolio divides teams into different aspects where each team then contributes towards the final outcome of the project. These teams contribute a collection of documents describing their perspective towards the project.

These documents describe in detail about each requirement. Taken from the requirements, it has been broken down to each sub-section and explained in more detail the purpose of the requirement from each aspect, which is the technical part, the non-technical part, the safety part and the system aspects part. A detailed explanation from each of these sections provides a clear view of the purpose of the requirement.

2. Navigation

Portfolio Identifier: PORT_01Requirement: The system shall provide two-dimensional (latitude and longitude) coverage of the space transport unit in space. Technical: Latitude measures the angle ranging from 0° at the Equator to 90° at the poles and the longitude is also measured in angles ranging from 0° at the Prime Meridian to +180° eastward and −180° westward Latitude measures the angle ranging from 0° at the Equator to 90° at the poles and the longitude is also measured in angles ranging from 0° at the Prime Meridian to +180° eastward and −180° westward The latitude and longitude coverage will provide the space transport unit’s co-ordinates to the ground station. Safety: The co-ordinates will enable the ground station to track the space transport unit’s position. Tracking the space transport unit is for safety precautions in case any incidents may occur, so emergency and rescue services could perform efficiently if the exact locations of events are known.Non-Technical: The two-dimensional co-ordinate system is required as a safety precaution.System Aspect: The two-dimensional co-ordinate system is required to be part of the navigation system, mainly for the safety of the public, customers and employees, and also as security for the space transport unit.

Portfolio Identifier: PORT_02Requirement: The system shall provide three-dimensional altitude coverage of the space transport unit in space. Technical: The three-dimensional altitude provides the location on, in, or above the Earth, the elevation, and the height position of the space transport unit. The three-dimensional coverage will provide the location, the elevation and the height position of the space transport unit to the ground station.Safety: The three-dimensional altitude coverage will enable the ground station to track the space transport unit’s altitude position. Tracking the space transport unit is for safety precautions in case any incidents may occur, so emergency and rescue services could perform efficiently if the exact locations of events are known.Non-Technical: The three-dimensional altitude system is required as a safety precaution.System Aspect: The three-dimensional altitude system is required to be part of the navigation system, mainly for the safety of the public, customers and employees, and also as security for the space transport unit.

Portfolio Identifier: PORT_03Requirement: The system shall also be able to determine the position of the space transport unit under different weather conditions.Technical: The system shall require access to satellite constellations. The satellite navigation systems should be able to interoperable with older navigation systems. With the combine systems, it can improve the overall navigation availability, because the user will be able to locate moving or stationary object with the same receiver from any of the satellites in any combination.Safety: The tracking system needs to be constantly providing the space transport unit’s position information at all time. Any long length of time of break down in communication could have severe consequences if any incidents may occur. Non-Non-Technical: The ability of changing satellite combinations will allow ground control to keep track of the space transport unit with minimising the time of break down in communication.System Aspect: The tracking system is required to operate under different weather conditions. For a reliable system, it should be part of the navigation system prerequisite, mainly for the safety of the public, customers and employees, and also as security for the space transport unit.

Portfolio Identifier: PORT_04Requirement: The system shall be able to have time synchronisation accuracy with the space vehicle up to 0.1 microseconds. Technical: The navigation system fitted with an atomic clock improves the measured accurate. This allows the system to calculate the exact position with an accuracy of up to 0.1 meter/second. Safety: Allows the space transport unit and the ground station to obtain data as quick as possible, to avoid incidents.Non-Technical: Enabling the system to obtain data in real-time. System Aspect: The navigation system providing data in real-time is required to update its system data and to improve performance.

3. Propulsion System

Portfolio Identifier: PORT_05Requirement: The system shall have at least one main engine.Technical: One main engine can provide enough thrust for the space transport unit to take off and fly safely. Too many engines would put too much weight on the transport unit. With today’s technology one engine is capable of providing enough thrust for a space transport unit.Safety: An engine weighs a lot, and too many engines may weigh the space transport unit down. If the main engine is down, there will be a secondary engine as back up.Non-Technical: Too many engines per transport unit will strain the construction and maintenance budget and the consumption of fuel will also increase. System Aspects: Technical and safety must be considered to make the decision on whether of using how many engines.

Portfolio Identifier: PORT_06Requirement: The engine shall be able to provide at least 95 kN of thrust.

Technical: This is more than enough thrust for injection for the transporter into earth orbit. This amount of thrust is obtainable using today’s rocket engine technology; with current rocket technology able to maintain this level of thrust for well over 200 seconds.Safety: Although much higher levels of thrust are capable from current rocket engine technology, higher levels of thrust will result in G-forces that are not tolerable for human passengers. Non-Technical: The amount of thrust that an engine can produce will determine the price. It is unnecessary to pick an engine and the transport unit will not use the full potential of the engine. System Aspects: All technical, non-technical and safety must be considered to make the decision on how much thrust is the best solution for the space transport unit.

4. Launch System

Portfolio Identifier: PORT_07Requirement: The system shall have at least one runway for take-off and landing.Tech: Aspects of the runway will improve efficiency and enable the Ground terminal to organise launch sequences.Safety: The runway allows for enhanced safety precautions. Emergency vehicles can be close in case they are needed urgently, Patrons and customers can be kept clear of the area. Accurate simulations can be performed in the case of an emergency.Non-tech: A runway is required for a comfortable take off [3].System Aspects:

Portfolio Identifier: PORT_08Requirement: The runway shall be able to withstand a static weight of 120 tonnes.Tech: The static weight of 120 tones will be able to withstand any space transport unit movements, and prevent damage occurringSafety: The static weight is adequate to be able to move the space transport unit with out causing damage to the space transport unit or the runway.Non-tech: The static weight of 120 tone will allow multiple take-offs and landings on the runway, which will decreases overall costs [3].System Aspects:

Portfolio Identifier: PORT_09Requirement: The runway shall be able to withstand an impact of 1.30x3 Nm. in an area of 4 m2.

Tech: The required impact pressure for damage not to occur to the runway under full thrust conditions on take off and during the landing of the space transport unit.Safety: An impact resistance of 1.30x3 Nm is more than adequate to safely land the space transport unit.Non-tech: Withstanding an impact of 1.30x3 Nm will allow multiple take-offs and landings on the runway, which will decreases overall costs [2].System Aspects:

Portfolio Identifier: PORT_10Requirement: The runway shall be treated with skid-resistant material (grooved or PFC) per FAA or ICAO specifications.Tech: This requirement allows for better mobility and increased stopping ability. By using no skid-resistant material the tyres will last longer and save on maintenanceSafety: This requirement allows for better mobility and increased stopping ability.Non-tech: Increased comfort, knowing that safety precautions are being implemented [2].System Aspects:

Portfolio Identifier: PORT_11Requirement: The runway shall be of length no less than 1.5 km.Tech: A runway of 1.5km will be sufficient to be able to take off and land the space transport unit.Non-tech: Runway costs are about $8000000US per 350m. A short runway will reduce costs but a Long runway will give a greater feeling of comfort to passengers.Safety: A runway of length of 2.5km will adequately allow the Space transport unit to abort take-off at any time during the launch sequence and stop before the runway ends. At 1.5km some additional run-off ramps will be required. These run-off ramps may be made of a slightly less grade material [3].System Aspects:

5. Life Support

Portfolio Identifier: PORT _12Requirement: The system shall maintain temperature control for life support within the range of 8°C to 27°C (64°-81 °F).Technical:Outer space is an extremely cold environment and temperatures will vary drastically in different parts of the space transport unit orbiter. The electronic equipment generates more than enough heat for the ship. The problem is getting rid of the excess heat. So the temperature control system has to carry out two major functions:

• Distribute heat where it is needed on the orbiter (mid-fuselage and other sections) so that vital systems do not freeze in the cold of space.

• Insulating materials, surface coatings are used to reduce heat loss through the walls of the various components just like your home insulation.

• Metallic plates are used to collect heat by direct contact with equipment or conduction

The cabin heat exchanger also controls the cabin temperature. It circulates cool water to remove excess heat (cabin air is also used to cool electronic equipment) and transferring heat to warm up the colder section of the space transport unit orbiter. Safety: To our knowledge these temperature controlling systems are safe. An ambient temperature range of 21 to 23oC (70 to 74oF) is optimal for system reliability and operator comfort. While most computer equipment can operate within a rather broad range, a temperature level near 22oC (72oF) is desirable because it is easier to maintain a safe associated relative humidity level at this temperature. Further, this recommended temperature provides an operational buffer in case the environmental support systems are down [5]. Non-Technical: There will be a cost associating to the components that is required, and NASA has already performed their own cost analysis over many uses.System Aspects: It ensures the survival of the passengers on board the shuttle.

Portfolio Identifier: PORT_13Requirement: The space transport unit shall handle no less than 3,000 degrees F (1,650 degrees C) of heat generation (for re-entry to earth).Technical: Space transport unit will require a heat shield, because it will be exposed to extreme heat (up to 2300ûF) during re-entry. Not all parts of the transport unit will experience the extreme heat, some sections may only be exposed to lower temperature, from 600û to 1200ûF, so not all sections requires the same type of heat shield [11].Safety: Heat shield prevents the space transport unit from burning up during re-entry. Non-Technical: Cost will very depending on the types of material used for the heat shield, different parts will be protected by different types of heat shield. The heat shield is re-usable [8].System Aspects: It ensures the survival of the passengers on board the shuttle.

Portfolio Identifier: PORT _14Requirement: The exterior of a space transport unit shall handle no less than 760 millimetres of mercury pressure.Technical: The airlock is normally located inside the mid deck of a spacecraft's pressurised crew cabin. Airlock depressurisation is controllable from the orbiter crew cabin mid deck and from inside the airlock. It is performed by equalising the airlocks and cabin's pressure with equalisation valves mounted on the inner hatch. The airlock is depressurised from inside the airlock by venting the airlock's pressure overboard. [4].Safety: To our knowledge their have been no safety issues with NASA's air pressure system. Each airlock hatch has dual pressure seals to maintain pressure integrity. One seal is mounted on the airlock hatch and the other on the airlock structure. A leak check quickly disconnect is installed between the hatch and the airlock pressure seals to verify hatch pressure integrity before flight [4].Non-Technical: NASA has already performed their own cost analysis over many use we will follow their use of components.System Aspects: It ensures the survival of the passengers on board the shuttle.

Portfolio Identifier: PORT_15Requirement: The interior of the system shall maintain an atmospheric pressure of 14.7psi at all times (half of FAA allowance of pressure variation, assuming a linear decrease in pressure with height) [13].Technical: The cabin is pressurised to 14.7psia, plus or minus 0.2psia, and maintained at an average 80-percent nitrogen and 20-percent oxygen mixture by the air revitalisation system. Oxygen partial pressure is maintained between 2.95 and 3.45psi, with sufficient nitrogen pressure of 11.5psia added to achieve the cabin total pressure of 14.7psia, plus or minus 0.2psia [12].Safety: Although much higher levels of thrust are capable from today’s spaceship technology. This means that spaceships must have strong walls to keep from blowing up due to the internal pressure. Even a six foot diameter sphere has a pressure of about 122 tons trying to blow it apart due to the atmospheric pressure of 15 psi (pounds per square inch) inside the spaceship (if you simulate the atmospheric pressure of the earth [6].) This level of precautions is safe for the structural integrity of the spacecraft, and will also allow all other systems to operate correctly.Non-Technical: Cost: Because NASA has already performed their own cost analysis over many use we will follow their use of components atmosphere. System Aspects: It ensures the survival of the passengers on board the shuttle.

6. Maintenance

Portfolio Identifier: PORT_16Requirement: Any hazardous materials used in design of the Space Transport Unit shall be separated at unit retirement as described by the Basel Convention on the Control of Trans-boundary Movements of Hazardous Wastes and their Disposal. Technical: Hazardous material used to design Space Transport Unit could be solid, liquid or gas that can harm humans or other living organisms due to being radioactive, flammable, and explosive etc. The hazardous material should be stored in a closed container under a dry-insert blanket. The storage area should be ventilated and the room temperature kept at 4ºC. The hazardous material requires separate unit retirement, to keep it safe.Safety: To ensure the safety of the person who handles the hazardous material, that person has to wear the protective clothing to protect him or herself from the hazardous materials. Special protective clothing has been treated to offend hazardous chemical, biological or radioactive materials. We have to ensure that, a First–Aid kit is provided near the storage area.Non-Technical: The hazardous materials could be solid, liquid or gas; therefore we have to keep the container safe. We have to avoid exposing the container to the atmosphere, because those hazardous materials could diffuse through air, which will pollute the air quality and also the environment.System Aspect: The hazardous materials are very dangerous, which will cause serious harm to human health and might lead to death. Therefore, we have to take serious action in separating the hazardous materials at the unit retirement.

Portfolio Identifier: PORT_17Requirement: Any hazardous materials used in design of the Space Transport Unit shall be disposed of at unit retirement as described by the Basel Convention on the Control of Trans-boundary Movements of Hazardous Wastes and their Disposal.Technical: Hazardous materials are very dangerous, which can harm human and living organisms. The disposal of hazardous waste must follow the Basel Convention. The Basel Convention was designed to reduce the movements of hazardous material between nations, and specifically to prevent dumping of hazardous waste from developed to less developed countries (LDC).Safety: The hazardous waste are dangerous objects, therefore we have to be very careful while disposing them. The disposal process needs to follow the way which is stated in the government and local environmental control regulation. Non-technical: To dispose the hazardous waste, special disposal company is needed to dispose the hazardous waste. The disposal company must be approved by the government. System Aspect: It is important to dispose the hazardous waste by using the correct method and must be in accordance with the government and local environmental control regulations.

Portfolio Identifier: PORT_18Requirement: Any hazardous materials used in design of the ground facilities shall be separated at retirement as described by the Basel Convention on the Control of Trans-boundary Movements of Hazardous Wastes and their Disposal. Technical: Hazardous material used in design ground facilities maybe solid, liquid or gas which can seriously harm humans or other living organisms. The hazardous material should be stored in a closed steel container under a dry-insert blanket and maintain the room temperature at 4o C. Safety: To ensure the safety of the person who handles the hazardous material, that person has to wear the protective clothing to protect him or herself from the hazardous materials. As describe before, the protective clothing is very powerful which can protect he/she from getting affected. We have to ensure the First-Aid kit is around the storage areaNon-Technical: The hazardous materials could be solid, liquid or gas; therefore we have to keep the container safe. We have to avoid exposing the container to the atmosphere, because those hazardous materials could diffuse through air, which will pollute the air quality and also the environment.System Aspect: The hazardous materials are very dangerous, which will cause serious harm to human health and might lead to death. Therefore, we have to take serious action in separating the hazardous materials at the unit retirement.

7. Storage

Portfolio Identifier: PORT_19Requirement: The Space Transport Unit Hanger shall be enclosed within the dimensions 50m x 200m x 15m.Priority: HighTechnical: The dimensions 150mx200mx15m for the transport unit’s hanger were chosen because the hanger has to enclose 5 or more transport units and also enough storage space for the associated maintenance equipment. Estimated floor space needed to house each transport unit and its equipment is 25mx35m. Non-Technical: The transport unit hanger was chosen to be a strong, secure, fully enclosed structure, but also be well ventilated. A fully enclosed hanger will help with monitored security and will provide protection from outside elements such as wind, rain etc. The transport unit hanger would cost somewhere between $250,000 and $300,000 depending on the quality of the construction material.Safety: For the hanger to meet safety requirements it will have to be well ventilated, have emergency exits, electrical safety equipment etc. System Aspects: The space transport unit’s hanger provides protection and security to the transport unit while not in operation.

Portfolio Identifier: PORT_20Requirement: The hanger shall provide security surveillance 24hours a day with restricted access and security surveillance for all Space Transporter Units.Technical: To visually monitor the surrounding areas, cameras will be attached to the outside wall of the hanger at 50m intervals. Security cameras will be capable of surveillance of 24 hours a day in all weather conditions. Non-Technical: To combat security problems entrance to the transport hanger will be restricted to authorised personnel. All personnel entering the hanger will require a security card, for further security, cameras will be installed at the hanger and will be monitored 24 hours each day at the security office.Safety: Security cameras will be used to keep the workers and equipment safe from saboteurs and thieves. Safety within in the hanger will be achieved by keeping the building secure and free from unauthorised personnel. System Aspects: 24 hour Surveillance provides security to the property of SeaLink.

Portfolio Identifier: PORT_21Requirement: The ground terminal shall provide storage space for ground terminal maintenance equipment during all working hours Technical: Ground terminal maintenance storage area will have a secure area large enough to store all the required maintenance equipment. Storage area will be subdivided for the storage of different materials e.g. hazardous, non-hazardous, flammable etc. Non-Technical: The ground terminal storage area will be always accessible to authorised personnel. Safety: The ground terminal storage area will be regularly maintained (e.g. tidy shelves, floor cleaned etc.) to reduce the likelihood of accidents. Access to hazardous and flammable materials will be highly restricted and will require special access. System Aspect: Storage facility for maintenance equipment provides security to equipments, so any unauthorised personnel cannot get access to the equipment. It also provides a safe working place.

Portfolio Identifier: PORT_22Requirement: The Ground Terminal Maintenance Storage shall be 100m x 100m x 10m.Technical: The dimensions 100mx100mx10m for the ground terminal storage were chosen because the storage area has to enclose maintenance equipment to service all ground terminal facilities. Non-Technical: The ground terminal storage area was chosen to be a secure, fully enclosed structure with some ventilated areas. A fully enclosed storage area provides security and protection for equipment from the outside elements such as wind, rain etc. The ground terminal storage area will cost somewhere between $100,000 and $150,000 depending on the quality of the construction material.Safety: For the ground terminal storage area to meet safety requirements it will have to be well ventilated in the areas containing hazardous and flammable materials, have easily accessible emergency exits, electrical safety equipment etc. System Aspect: The dimensions of the maintenance storage, provides enough space to store equipments and ease of access to equipment inside the storage area.

Portfolio Identifier: PORT_23Requirement: The Ground Terminal shall provide storage space for Space Transport Unit maintenance equipment during all working hours. Technical: It is necessary for the maintenance equipment to be stored in the appropriate conditions. The equipment can be damaged if stored in conditions that are outside its working limits. All storage space for maintenance equipment is stored at

Celsius unless the equipment states otherwise. Non-Technical: The maintenance storage space will be required to be located close to the maintenance area to accommodate quick access during all working hours for maintenance repairs. Safety: The maintenance storage space will be accessed regularly, it is necessary for there to be enough space for all storage equipment during all hours. The storage space must be free from debris and have enough lighting for persons to see the storage space easily. For safety standards there is an evacuation route indicating all safety exits. System Aspects:

Portfolio Identifier: PORT_24Requirement: The Space Transport Unit Maintenance Storage shall be 100m x 100m x 10m. Technical: The maintenance storage space is to be 100m x 100m x 10m this allows for the storage for all space plane maintenance equipment. The space transport unit maintenance storage outer casing is manufactured from a double skin insulated sheet to reduce condensation and temperature change in the storage space. Non-Technical: The storage space dimensions of 100m x 100m x 10m will require

of double skin insulated roof/wall sheeting; this is the most cost effective solution when compared to other insulating roof/wall sheeting. Safety: The storage space is engineered to 100m x 100m x 10m to allow for a safe structure which will be resistant to wind, rain, heat and cold. System Aspects: The dimensions and the materials of the space transport unit maintenance storage are made from materials to meet all requirements and the dimensions of the storage unit which will allow for all maintenance equipment to be stored safely.

Portfolio Identifier: PORT_25Requirement: The Ground Terminal shall have underground fuel storage.Technical: The fuel storage is stored underground at a constant temperature. The temperature will meet the fuel storage temperature. Fuel storage is to facilitate for 6000000ltr of fuel.Non-Technical: The fuel storage is kept underground rather than above ground for space saving. Underground storage is used rather than above ground storage because it is easier to maintain a constant temperature underground rather than above ground, this will reduce the risks of combustion due to the high temperatures in South Australia.Safety: The underground storage space has many advantages in safety. If the storage space is stored above ground it would be susceptible to many safety factors. This includes terrorists, temperature control and security access. System Aspects: Having an underground fuel storage would impact on a larger financial cost than to have fuel storage above ground, underground fuel storage is justified mainly by the safety aspects involved. If the safety of fuel storage is compromised it could result in a possible destruction of the whole ground base.

Portfolio Identifier: PORT_26Requirement: The fuel storage shall be at least 1.5km away from surrounding buildings.Technical: From a technical point of view it is not feasible to have fuel storage 1.5km away. The fuel storage should be close to the hanger. Non-Technical: The fuel storage is located a least 1.5km away from surrounding buildings to facilitate customer satisfaction; it is not pleasurable to know that the customer is situated on top of a large amount of highly flammable fuel. Therefore the fuel storage is located at a distance at least 1.5km from surrounding buildings. Safety: There is a large safety aspect when considering the location of the fuel storage, it is located 1.5km away from surrounding buildings in the case of an accident or explosion of the fuel storage, this distance will minimise any damage to surrounding buildings and personnel. System Aspects: The fuel storage space is located 1.5km away from surrounding buildings mainly from a safety prospective; technically the fuel should be located close to the hanger to make maintenance fast and efficient.

Portfolio Identifier: PORT_27Requirement: The fuel storage shall store 6000000 litres of fuel.Technical: The fuel storage is to have enough fuel to last twenty flights as required by the requirement GT_SC11, this equates to 6000000litres of fuel. Non-Technical: This allows for twenty flights due to the large number of space transport units on mission. Safety: It is not desirable to hold 6000000litres of fuel due to the huge safety concerns. System Aspects: It is not desirable to hold 6000000litres of fuel, however it is specified that the there must be enough fuel for at least 20 flights. This is due to the high demand for space travel.

8. Service

Portfolio Identifier: PORT_28Requirement: All pre-launch maintenance tools shall be stored in the Ground Terminal Storage hangarTechnical: As described previously the storage hangar is 100m x 100m x 10m, this technically provides the system with a large enough area to store all the required equipment. This includes pre-launch maintenance tools which will be located in a particular section of the hangar.Safety: Obviously the safest workplace is a clean workplace, in the case of storage for the pre-launch maintenance tools the use of a storage hangar to house any equipment required is vital. Safety for maintenance staff, flight staff and also the customer must be considered and hence is why all tools and equipment must be kept in a secure location. Non-Technical: The storage hangar will be required to be located close to the launch area to accommodate the quick access needed to make any pre-launch maintenance as the tools will be within the hangar at all times.System Aspects: The system as a whole will operate more efficiently if the pre-launch maintenance tools are stored in a secure location which is easily accessible. It therefore is clear that the pre-launch tools should be kept in the Ground Terminal storage hangar.

Portfolio Identifier: PORT_29Requirement: All basic level maintenance equipment shall be stored in the Ground Terminal Storage hangarTechnical: The basic maintenance tools will be located within the Ground Terminal storage hangar in a separate location designated for them. Safety: To ensure the safety of the customers, the basic level maintenance tools will be stored separately from other tools so that maintenance can be completed without the hassle of other maintenance staff using the required tools.Non-Technical: To ensure fast reaction to any maintenance situation, the basic level maintenance tools are located within the storage hangar in a defined place for the quickest and easiest possible access. Basic level maintenance may include minor repairs to interior or customer service facilities.System Aspects: As a large scale operation where passenger’s lives will be put at risk during every flight, the maintenance of the space transport units will be vital in a successful operation. The basic level maintenance equipment will have to be readily accessible in any situation and so it is of high importance that it is located in a separate zone within the Ground Terminal storage hangar.

Portfolio Identifier: PORT_29Requirement: All intermediate level maintenance equipment shall be stored in the Ground Terminal Storage hangarTechnical: The intermediate maintenance tools will be located within the Ground Terminal storage hangar in a separate location designated for them. Safety: To ensure the safety of the customers, the intermediate level maintenance tools will be stored separately from other tools so that maintenance can be completed without the hassle of other maintenance staff using the required tools.Non-Technical: To ensure fast reaction to any maintenance situation, the intermediate level maintenance tools are located within the storage hangar in a defined place for the quickest and easiest possible access. Intermediate level maintenance may include repairs such as exterior, software and flight systems repairs.System Aspects: As a large scale operation where passengers’ lives will be put at risk during every flight, the maintenance of the space transport units is vital for a successful operation. The intermediate level maintenance equipment will have to be readily accessible in any situation and so it is of high importance that it is located in a separate zone within the Ground Terminal storage hangar.

Portfolio Identifier: PORT_30Requirement: All advanced level maintenance equipment shall be stored in the Ground Terminal Storage hangarTechnical: The advanced maintenance tools will be located within the Ground Terminal storage hangar in a separate location designated for them. Safety: To ensure the safety of the customers, the advanced level maintenance tools will be stored separately from other tools so that maintenance can be completed without the hassle of other maintenance staff using the required tools.Non-Technical: To ensure fast reaction to any maintenance situation, the advanced level maintenance tools are located within the storage hangar in a defined place for the quickest and easiest possible access. Advanced level repairs may include things such as major propulsion system, or major navigation and flight system repairs.System Aspects: As a large scale operation where passengers’ lives will be put at risk during every flight, the maintenance of the space transport units is vital for a successful operation. The advanced level maintenance equipment will have to be readily accessible in any situation and so it is of high importance that it is located in a separate zone within the Ground Terminal storage hangar.

Portfolio Identifier: PORT_31Requirement: All pre-launch maintenance equipment shall be located within the Ground Terminal boundariesTechnical: The Ground Terminal boundaries will accommodate all of the Systems buildings, space transport units and relevant facilities. This includes the maintenance equipment which will always be stored within the boundaries of the Ground Terminal to ensure access to it can be made at any time.Safety: The access to maintenance equipment is very important to the systems success. The safety of customers and crew members depends on the availability of the safety equipment. To ensure that any problem threatening the safety of customers is eliminated, all maintenance equipment will be stored at the Ground terminal at all times. Non-Technical: For ease of maintenance and to reduce time taken all tools and equipment required for maintenance tasks are kept in storage at the ground terminal. System Aspects: For the system as a whole to operate at full efficiency the best solution is to keep everything which may be required for use on the Ground terminal or Space transport unit to be housed permanently within the Ground Terminal boundaries.

9. Reference

[1] Airplane Performance, viewed on 17th October 2005,www.boeing.com/assocproducts/aircompat/acaps/73bjsec3.pdf.

[2] Airport Standards, viewed on 18th October 2005,www.dot.wisconsin.gov/travel/air/docs/apt-standards.doc.

[3] Communications and Tracking System, viewed on 20th October 2005,http://www.apollosaturn.com/geminiNR/sec2.htm

[4] Environmental control and life support system, viewed on 20th October 2005,http://science.ksc.nasa.gov/shuttle/technology/sts-newsref/sts_eclss.html .

[5] Environmental Requirements, viewed on 18th October 2005, http://docs.sun.com/source/816-1613-13/Chapter2.html .

[6] Gauge Pressure of Space, viewed on 20th October 2005,http://www.newton.dep.anl.gov/askasci/eng99/eng99149.htm.

[7] How Space Shuttles Work, viewed on 18th October 2005,http://science.howstuffworks.com/space-shuttle5.htm .

[8] Meteors burn up when they hit the Earth's atmosphere. Why doesn't the space shuttle?, viewed on 17th October 2005,


[9] New revelations of frequencies for early Soviet spacecraft, viewed on 20th October 2005,http://www.svengrahn.pp.se/radioind/mirradio/earlyfxs.html.

[10] PAS-3, viewed on 20th October 2005http://www.panamsat.com/global_network/pas_3.asp

[11] The Space Shuttle Orbiter and Ceramic Tiles - Some History and Information, viewed on 17th October 2005, http://www.freerepublic.com/focus/news/834596/posts .

[12] Tight Control of the Space Shuttle/Spacelab Environment, viewed on 17th

October 2005,http://www.nsbri.org/HumanPhysSpace/focus1/spaceshuttle-

environment.html.

[13] Where does space begin?, viewed on 20th October 2005,http://www.space.edu/projects/book/chapter3.html.

http://www.space.edu/projects/book/chapter3.html

http://www.nsbri.org/HumanPhysSpace/focus1/spaceshuttle-environment.html

http://www.nsbri.org/HumanPhysSpace/focus1/spaceshuttle-environment.html

http://www.freerepublic.com/focus/news/834596/posts

http://www.panamsat.com/global_network/pas_3.asp

http://www.svengrahn.pp.se/radioind/mirradio/earlyfxs.html


http://science.howstuffworks.com/space-shuttle5.htm

http://www.newton.dep.anl.gov/askasci/eng99/eng99149.htm

http://docs.sun.com/source/816-1613-13/Chapter2.html

http://science.ksc.nasa.gov/shuttle/technology/sts-newsref/sts_eclss.html

http://www.apollosaturn.com/geminiNR/sec2.htm

http://www.dot.wisconsin.gov/travel/air/docs/apt-standards.doc

http://www.boeing.com/assocproducts/aircompat/acaps/73bjsec3.pdf

Conclusion:

Serious and detailed consideration was first given to the possibility of space being opened up to trips by the general public three decades ago, and some initial attempts to do so around a decade ago, mainly in Russia and the United States.

In recent years, professional space tourism studies have been conducted in the United Kingdom, Germany and, especially, Japan and China. In the U.S., technological progress has been pronounced and it has be proven to the general public that it is possible for astronaut travel to and from low Earth orbit safely. NASA and the commercial space industry now have new and promising space transportation development programs underway; especially the space plane X-33 and X-34 programs, and some related development programs [1]. From the feasibility study conducted by the team in this report, a space plane is shown to be the most feasible technology considered for the proposed joyride to space.

Today, tourism trips are limited to surface travel or low-altitude flight. Opportunities to experience space-like conditions are limited to "zero-gravity" trips in aircraft and simulations. Even so, over 10 million people each year visit a space museum, a space camp, a rocket launch-recovery site or government space R&D centres -- a business with estimated revenue of $1 billion per year [1]. This business could be expanded, especially if the general public could see programs underway that specifically offer the promise of trips to/from space becoming available early in the next decade. Its expansion would attract entrepreneurs and investment attention to in-space business possibilities and it is a venture that Australia should consider.

For Australia’s Space ambitions, Matthew King, author of the journal “The Lowdown”, address the topic of Australian Space development in focus. In this report, he states that Australia should launch a national campaign to be involved in the push to make space travel a commercial reality. If a few Russian or Chinese space engineers could be hired for their experience sharing, this could prove to be an inexpensive option worth pursuing. Space development is also perceived as an economic multiplier as every dollar spent on space percolates through the economy, creating growth and wealth.

Space travel is still considered a relatively high risk proposition, due to the cutting-edge technology relied upon. To promote the space tourism industry, operators need to ensure that both the transportation and destination are safe, accessible, and comfortable enough to provide tourists with a positive experience. If travelling patrons get hurt or sick, or if they just have an unpleasant experience, word of mouth will quickly discourage other potential customers. This may be especially true when space tours are accessible only to the rich and famous, whose descriptions of their experiences (favourable or unfavourable) will colourfully capture the public's attention.

The system utilising space planes, as described in this document, addresses all of these issues and is sure to be a commercial success for our client, SeaLink.

References:

[1] General Public Space Travel and Tourism – Volume 1 Executive SummaryURL: http://www.spacefuture.com/archive/general_public_space_travel_and_tourism.shtmlDate Accessed: 29 October 2005

[2] The Lowdown: Australian Space development in focus by Matthew KingURL: http://www.lowdown.com.au/index.htmlDate Accessed: 29 October 2005

[3] Space faring by Albert A. Harrison, The Human Dimensionshttp://www.ucpress.edu/books/pages/9028/9028.ch12.htmlDate Accessed: 29 October 2005

http://www.ucpress.edu/books/pages/9028/9028.ch12.html

http://www.lowdown.com.au/index.html

http://www.spacefuture.com/archive/general_public_space_travel_and_tourism.shtml

Documents

Preliminary Design Review [Tuesday 2pm]