Canada Inc

C130 TOLD Solution

1.Introduction

GLOBERS offers a variety of aeronautical software to facilitate rapid and accurate operational calculations. With 30 years of flying experience, we offer consultation services, operational test & evaluation, and thinking outside the box solutions.

TOLD Solution “Ts” for the C-130 Hercules is a Take-Off and Landing Performance Calculation Tool. It is a significant new contribution for flight planning, which brings a professional approach to the C-130 Hercules.Ts incorporates into a single application all the data and calculations required to plan for safe and accurate take-offs and landings.

Ts will provideflight crews, with Take-Off and Landing Performance TOLD including all relevant speeds (V1, VR, Take-Off distance, Reduced Power Take-Off), de-rated and assumed temperatures, and stop margins, as well as a unique reduced power take off calculation tool.

Managers understand the advantages of using reduced power Take-Offs.Unfortunately, to date, there were no quick and easy ways to calculate an effective reduced power Take-Off. Ts takes advantage of the reduced power Take-Off and provides saving on operational cost, while increasing engines life and decreasing engine damage from over torques.

In most situations, the highest torque required during a mission is for take off. By calculating the required Take-Off torque, one can assume that this would be the maximum torque required to accomplish the mission. For most missions 18000# of torque is more than sufficient to do the mission. TOLD Solution provides flight crews with the only available tool to calculate effective reduced power Take-Off.

Table of Content

1.Introduction

Table of Content

Table of figures

2.Overview of TOLD Solution User Experience.

2.1.Ts Features:

2.2.Required Data Entry:

2.3.Aircraft Conditions Setting:

2.4.The Take-off related computed display:

2.5.The Landing related computed display:

3.Reduced Power TO Calculations

4.Functional Components

4.1.Description of Components

5.General System Security

5.1.System Location

5.2.Protection Against Unauthorized Local Access

5.3.Copy Rights, ITAR and Control Goods.

5.4.Typical Disclosure of Controlled Documentation by the Lockheed Martin Aeronautics Company:

5.5.Protection Against Unauthorized Network Access

5.6.Security Breach Plan

5.7.GLOBERS’ security breach response plan will include the following:

6.Software Development & IT Policies

6.1.DO-178B, Software Development Considerations.

6.2.Software Level

6.3.Processes and Documents

6.4.Planning

6.5.Development

6.6.GLOBERS Software development process, modified waterfall

6.7.Verification

6.8.Configuration Management

6.9.Quality Assurance

6.10.Tools

6.11.Requirements Management

6.12.Resource Management

Below is a set of workflows to request and provide a resource.

6.13.Operating System & Software Policies

6.14.System Logs

6.15.Employee Accounts

6.16.Backup

6.17.Software Change Management

6.18.Other Policies

6.19.Sales, Download and Licensing

7.Portable Device Count – Registration / License Management

7.1.Copy Protections

7.2.Registration Example

Table of figures

Figure 1 Security set

Figure 2 Development process

Figure 3 Life Cycle

Figure 4 Resource Management Workflow

Figure 5 CSIRT

Figure 6 Computer ID

Figure 7 Computer ID registration

2.Overview of TOLD Solution User Experience.

2.1.Ts Features:

2.1.1.Ts is compatible with any PC or Tablet running Microsoft® Windows® with an Excel® application, created by professional airline pilots and does not require any other software.

2.1.2.Ts is portable; just save the file on a USB drive and use on any computer to view and print TOLD Data. This application is customized to fit any display. Easy-to-use, it has a user-friendly interface resembling a real-life TOLD card. Ready-to-print and ready-to-save, take-off and landing TOLD cards.

2.2.Required Data Entry:

2.2.1.Ts requires minimal manual DATA entry for the TO calculations and includes customable presets, reducing greatly the required DATA entry.

  • Wind direction and velocity/gust
  • Weights (BEW, Ramp Fuel weight, Cargo weight)
  • Altimeter setting in both Hg and QNH
  • Outside Air Temperature (OAT)
  • Runway data
  • True heading
  • ASDA
  • Field Elevation
  • RCR
  • RSC and
  • Slope

2.2.2.The primary option for the calculation of landing DATA is to use the TO data simulating an emergency landing immediately after TO.

2.2.3.TS offers a custom landing calculations option, allowing the modification of the following parameters:

  • Wind direction and velocity/gust
  • Gross weight
  • Altimeter setting in both Hg and QNH
  • Outside Air Temperature (OAT)
  • Runway data
  • Heading
  • LDA
  • Field Elevation
  • RCR
  • RSC and
  • Slope

2.3.Aircraft Conditions Setting:

  • Bleeds air
  • Anti-skid
  • Brake pressure
  • Take-off flaps
  • Type IV and
  • Drag index, and
  • DER calculations

2.4.The Take-off related computed display:

Take-off parameters:

  • Take-Off Weight
  • Pressure altitude
  • Take-Off factor
  • Head/Tail wind and Cross wind
  • 3 ENG Climb Rate, in ft/NM
  • TIT for the torque set, and
  • Refusal, Take-Off, Obstacle clearance, 3 ENG climb, 4 ENG climb speeds

2.5.The Landing related computed display:

Parameters:

  • POWER OFF STALL SPEED at TAKE-OFF GROSS WEIGHT for different Combinations of FLAPS and BANK ANGLES.
  • Landing ground roll for different combinations of FLAPS and Obstacles.
  • VMCA OGE 1 engine and VMCA OGE 2 engines speeds.
  • 3 and 2 engines service ceiling.
  • 4 and 3 engines climb speeds (missed approach).

3.Reduced Power TO Calculations

3.1.By selecting the Torque value, you will in fact select, indirectly, a T I T value. All other calculationswill be made from this T I T value. It is important that you select a realistic torque value. Before selecting your torque value, take a look at the available 95% torque provided. Unless the engines have been confirmed, to provide more than 95% power, the maximum value shall be no greater then the 95% value. Ts will warn you with an amber box if the value selected is greater than the 95% engine value. As well, if you use more then 95% you must use 100% and select the option box just above the torque value.

Bottom Line: reducing power, will save on maintenance and engines over torque.

3.2.Note: Depending on the Clients available DATA, GLOBERS may or may not have sufficient DATA in order to produce reduced power calculations. In the event that reduced power can not be calculated, GLOBERS will produce the 95% and 100% engines power calculation.

4.Functional Components

4.1.Description of Components

4.1.1.GLOBERS’ C130 Ts makes use of the power and stability of Microsoft Excel 2003. The Excel 2003 baseline version can be upgraded as requested by the customer with a minimal cost. This usually requires minimal coding and mainly involves Operational Test and Evaluation.

4.1.2.The user requireshaving a Microsoft Excel License and program installed on the computer. The Excel license is not included with Ts.

4.1.3.Furthermore, in order to provide safe code protection, the Ts is compiled with the DoneEx compiler.

4.1.4.The software is highly DATA driven. The customer must provide all the DATA required to perform the TOLD calculations. GLOBERSrequires that potential customers have all the rights to the DATA provided for the purpose of manipulation and automation for his / her own operational use.

4.1.5.GLOBERS developed an expertise in decoding aircraft performance charts, digitizing and automating calculations. GLOBER is the sole proprietor of the expertise and TOLD calculation technology.

5.General System Security

5.1.System Location

GLOBERScomputers are located in a co-location facility in Trenton, Ontario with a redundant backup system.

5.2.Protection Against Unauthorized Local Access

5.2.1.As required, the computers are locked up for maximum security. Enterprise level security practices, biometric access control and 24/7 surveillance are currently in place. Security restricted access to the Data Center is strictly enforced with escorted access only.

5.2.2.Every effort is made to exceed industry standard security measures to prevent the loss, misuse and alteration of the information under our control. Any access both physical and remote to equipment or data located within our data center, is accessible to internal staff only and on a need to know/access basis only. All personnel have undergone criminal and security checks.

5.3.Copy Rights, ITAR and Control Goods.

5.3.1.In many instances the DATA is subject to copy rights. Some manualsindicate clear ITAR warnings regarding the use of the data, while others clearly state distribution limitations, and that the export is restricted by the Arms and Exports Control Act or the Export Administration Act. It is the Clients responsibility to ensure that he/shehas the rights to use the DATA as he/she wishes in the Ts Program. Note: GLOBERS requires proofof clients DATA, from the manufacturer, that he/she is authorized to use or copy documents, which are delivered under his contract in order to produce a TOLD calculator.

5.3.2.Ts may contain technical data within the definition of the International Traffic in Arms Regulations (ITAR), and is subject to the export control laws of the U.S. Government. When subject to ITAR the Ts program will clearly state,“It is approved for transfer to The Clients through the Defence Science and Technology Agency (DSTA) under DTC Case TA 1366-08. Retransfer of this data by any means to any other end user or for any other end use, whether in the United States or abroad, without the written approval of the U.S. Department of State, is prohibited.”

5.3.3.CONTROLLED GOODS: Ts may contain controlled goods. Examination, possession, and transfer of these goods are restricted by Canada’s Defence Production Act and Controlled Goods Regulations.

5.4.Typical Disclosure of Controlled Documentation by the Lockheed Martin Aeronautics Company:

BACKGROUND INFORMATION

5.4.1.This document contains proprietary and commercial information of Lockheed Martin Aeronautics Company. Use and/or disclosure to others without express authorization of Lockheed Martin Aeronautics Company is strictly prohibited except as authorized by Contract No. XXXX with the Customer.

DISCLOSURE NOTICE

5.4.2.This document contains commercial proprietary technical data of Lockheed Martin Corporation and others. Use, copying, and/or disclosure of the technical data contained herein is governed by the terms of the Lockheed Martin Corporation’s C-130 X sales contract with the Customer. LM hereby authorizes the Customer to use or copy documents which are delivered under the subject contract. Please note that disclosure to others is restricted to the Customer.

WARNING

5.4.3.This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. Sec 2751et seq.) or the Export Administration Act of 1979, as amended, (Title 50, U.S.C., App. 2401 et seq.). Violations of these export laws are subject to severe criminal penalties.

5.5.Protection Against Unauthorized Network Access

5.5.1.Research and Development is conducted on stand alone computers, linked to an automated back up system.

5.5.2.The public Network is protected via the redundant set of firewalls.

5.5.3.Here’s a diagram to illustrate how our network architecture protects against unauthorized access.

Figure 1Security set

5.6.Security Breach Plan

5.6.1.GLOBERSsecurity breach plan involves a computer security incident response team (CSIRT) that provides assistance and information to help prepare, protect, and secure constituent systems in anticipation of attacks, problems, or events. Within that program proactive measures include the enforcement of a strict company policy covering removal from company facilities of laptop computers (and any other portable devices) containing personal information, requirement of encryption in such circumstances with described appropriate disciplinary action for violations of these principles and maintaining enterprise level security of its servers and their contents.

5.6.2.Other proactive detection measures include: technology watch, security audit and assessments, configuration and maintenance of tools, applications and infrastructures, development of security tools, intrusion detection services and a timely dissemination of security-related information.GLOBERS proactive measures also include on-going training and in-house security education programs.

5.7.GLOBERS’ security breach response plan will include the following:

5.7.1.Determine whether the breach is ongoing (e.g., a hacker still accessing the data) and, if so, have the information systems group shut it down;

5.7.2.Notify Computer Security Incident Response Team “CSIRT”;

5.7.3.Determine owner of affected data. If a licensee of data, (i) immediately inform the owner of the affected data about the breach; (ii) identify any obligations the company has under its contract with the owner; and (iii) discharge those obligations;

5.7.4.Ascertain whether to inform any law enforcement agency and, if so, which one(s);

5.7.5.Determine affected data/data subjects (using sophisticated forensics tools);

5.7.6.Determine the jurisdictions in which each affected data subject resides;

5.7.7.Identify the "trigger" thresholds (e.g., unauthorized access, misuse) in each such jurisdiction; figure out which thresholds (if any) were met;

5.7.8.Determine whether to limit the individuals notified to those required by law;

5.7.9.Analyze obligations in each affected jurisdiction (e.g., manner and content of notification; whether the attorney general must be notified, whether the three credit bureaus must be notified and time limits);

5.7.10.Determine whether to offer "extras" (e.g., free credit monitoring, toll-free information line) and, if so, which ones;

5.7.11.Decide whether to have in-house personnel send the notifications, or to engage a third party to send them

5.7.12.Choose the mode of communication to be used for the notifications;

5.7.13.Determine the content of the notifications;

5.7.14.Send the notifications (or have them sent by the pre-selected third party);

5.7.15.Arrange for remediation of the problem; and

5.7.16.Arrange for post-incident investigation and analysis.

6.Software Development & IT Policies

6.1.DO-178B, Software Development Considerations.

6.1.1.DO-178B, is a document dealing with the safety of software used in airborne systems.

6.1.2.The FAAapplies DO-178B as the document it uses for guidance to determine if the software will perform reliably in an airborne environment, when specified by the Technical Standard Order (TSO) for which certification is sought.Although not DO-178B certified, GLOBERSuses the guidance of the RTCA DO-178B throughout the software development as a standard of practice.

6.2.SoftwareLevel

6.2.1.DO-178B alone is not intended to guarantee software safety aspects. GLOBERS safety attributes in the design is evidence of meeting explicit safety requirements.

6.3.Processes and Documents

6.3.1.Processes are intended to support the objectives, according to the software level (A through D - Level E is outside the purview of DO-178B). Processes are described as abstract areas of work in DO-178B, and it is up to the GLOBERS to define and document the specifics of how a process is carried out. These activities are defined by GLOBERS as part of the Planning process.

6.3.2.Notes: This objective-based nature of DO-178B allows a great deal of flexibility in regard to following different styles of software life cycle. The flexible nature of DO-178B's processes and entry/exit criteria make it difficult to implement the first time, because these aspects are abstract and there is no "base set" of activities from which to work. The intention of DO-178B is not to be prescriptive.

6.4.Planning

Output documents from this process may include:

  • Plan for software aspects of certification (PSAC)
  • Software development plan (SDP)
  • Software verification plan (SVP)
  • Software configuration management plan (SCMP)
  • Software quality assurance plan (SQAP)
  • System requirements document (SysRD)
  • Software requirements standards (SRS)
  • Software design standards (SDS)
  • Software code standards (SCS)

System requirements are typically input to the entire project.

The last 3 documents (standards) are not required for software level D.

6.5.Development

The development process output documents may include:

  • Software requirements data (SRD)
  • Software design description (SDD)
  • Source code
  • Executable object code

GLOBERS provides traceability from the system requirements to all source code or executable object code.

6.6.GLOBERS Software development process, modified waterfall


Figure 2Development process

In the event a process does not meet the intended requirements, a review is carried out and the process restarts at the appropriate level.

6.7.Verification

6.7.1.Document outputs made by this process may include:

  • Software verification cases and procedures (SVCP)
  • Software verification results (SVR):
  • Review of all requirements, design and code
  • Testing of executable object code
  • Code coverage analysis, includes analysis of all code and traceability from tests and results.

6.7.2.GLOBERS Operational Test and Evaluation:

  • Systems testing
  • Integration testing, and
  • Acceptance testing

6.7.3.The testing is conducted throughout the complete range of the DATA and all charts simultaneously. The DATA is verified throughout the complete scale of testing,for everyinput / outputwithin the program. While testing the inputs, every single chart is verified for its accuracy.

6.8.Configuration Management

6.8.1.Documents maintained by the configuration managementprocess:

  • Software configuration index (SCI)
  • Software life cycle environment configuration index (SECI)


Figure 3Life Cycle

6.8.2.This process handles problem reports, changes and related activities. The configuration management process provides archive and revision identification of:

  • Source code development environment
  • Other development environments (for e.g. test/analysis tools)
  • Software integration tool
  • All other documents, software and hardware

6.9.Quality Assurance

6.9.1.Output documents from the quality assurance process may include:

  • Software quality assurance records (SQAR)
  • Software conformity review (SCR)
  • Software accomplishment summary (SAS)

6.9.2.This process performs reviews and audits to show compliance with DO-178B. The interface to the certification authority is also handled by the quality assurance process.