If this is a template Press Submit first

General Document Analysis

Documents
Templates
History

Help
REs
Training

FAA History Analysis

This template performs detailed analysis of the FAA history using search criteria defined, saved, and exchanged by you. Think of it as a search engine on steroids that analyzes any document so it can be clearly written, read, and understood. The FAA history document came from the FAA external website and was converted to a single text document. It is located in the directory structure of this tool at C:\z-cassbeth\gda\documents. Enjoy...

ReStart Default Rules No Rules

Prior to uploading your file, set your report options.
Also check the rules and modify them as desired.

      Stop Now

This tool is a broad document mining tool.
It can be used on any document

1. select browse, go to z-cassbeth/gda/documents
2. pick any.txt document
3. select a service and a rule, press submit
4. go thru each service and rule one at a time
5. select browse, pick another document
6. compare the results
7. update and create new rules and templates

. . . These template instructions are user defined.

Sustainable Development Possible with Creative System Engineering buy from amazon.com
Book Information
Previously Uploaded File: all-history.txt

Analysis Settings Hide Report Areas Hide
Analysis Results
Accessed Words
Accessed Patterns
Metrics

Doc Shape
Reading Level
Comments

Services and Rules

Template Comments FAA History Analysis

General Search
Find Duplicate Objects
Profile Document
Topics of Interest Show Search Show Simple Rules Show Complex Rules
. . .
Automation Computer Install SAGE STARS
Software NAFEC Research AAS Beacon RADAR
Hijack Restricted Areas ADIZ Air Defense Terrorist
NAS Stage A Curtis Report Design Competition Startup Shutdown

Decades
Organizations
Overall Reaction
Approach
FAA Systems Services
Predecessors

Add New Service Name Remove Last Service: Predecessors


Analysis Results Hide

Filter case sensitive
Access Object Reject Object Access Risk

Show Comment Details Hide All Comments Hide Checked Items Save Results . File

Processing previously uploaded file in all-history.txt

1. GDA-561 Apr 10, 1953: The U.S. Air Force decided to proceed with the production of SAGE (Semiautomatic Ground Environment), an electronic defense system developed by MIT's Lincoln Laboratory. (See Jul 10, 1956.) .

2. GDA-615 Jul 10, 1956: CAA announced the establishment in the Boston area of a Military Integration Branch of the Technical Development Center. The new office was created to provide closer coordination with military development programs, such as the SAGE Air Defense System, at Lexington and Deer Island, Mass. (See Apr 10, 1953, and Sep 21, 1959.) .

3. GDA-708 Sep 21, 1959: FAA announced that its representatives and those of DOD and the Air Force had signed an agreement to establish nine FAA air route traffic control centers at Air Force SAGE supercombat centers. The supercombat centers were part of the SAGE (semiautomatic ground environment) system for radar surveillance and identification of air traffic for air defense. (See Jul 10, 1956, and Apr 12, 1960.) Sep 29, 1959: A Braniff Lockheed Electra lost a wing and exploded in flight over Buffalo, Tex., with the loss of all 34 persons aboard. (See Mar 17, 1960.) .

4. GDA-735 Apr 12, 1960: FAA announced the start of a live test of the SAGE air defense system as a means of improving high-altitude air traffic control services. A part of a joint FAA-USAF project called Trailsmoke, the flight advisory service test (FAST) aimed essentially at evaluating the capability of the SAGE system to provide civil and military radar advisory information on potential air traffic conflicts. Specific operating positions would be occupied by FAA controllers at two SAGE direction centers of an Air Defense Division monitoring air activity in the Midwest section of the nation. (See Sep 21, 1959, and Apr 17, 1960.) .

5. GDA-737 Apr 17, 1960: FAA announced a contract award totaling nearly $6 million to the MITRE Corporation, Lexington, Mass., for advanced experimentation on automated air traffic control. Work to be performed under the contract included research and experimentation on joint use of military SAGE equipment and facilities for air traffic control, as well as for air defense purposes. FAA and the Air Force would share the cost of the project. (See Apr 12, 1960, and Sep 11, 1961.) .

6. GDA-814 Sep 11, 1961: The Project Beacon task force on Air Traffic Control (see Mar 8, 1961) submitted its report to the FAA Administrator. While finding that the air traffic control system was "being expertly operated by a highly skilled organization," the report concluded that substantial improvements were needed to meet the future challenge of aviation's projected growth. FAA urgently needed an overall systems plan. In effect, the recommended improvement involved a major reorientation of the modernization effort that had been launched in 1957 following the Curtis report. Keyed to the use of an air traffic control radar beacon system (ATCRBS) as a primary means of providing controllers with aircraft position information, the new concept found little promise in ground-based altitude measuring devices such as the 3-D radar under test as part of the earlier program (see Apr 7, 1961, and Dec 27, 1963). The report also urged expanded use of general purpose computers rather than special computer systems formerly under development for air traffic control. Rejecting the idea of fully merging air traffic control with the SAGE air defense system, the report urged that only radar elements of SAGE be used for the air traffic control system (see Apr 17, 1960, Feb 21, 1962, and Dec 1, 1963). The task force also urged a variety of changes involving airports, the segregation of controlled traffic, navigation and all-weather landing systems, a new category of flight known as controlled visual rules (CVR), and the extension of positive control and weather information. On Nov 7, having reviewed the Project Beacon report, President Kennedy directed FAA Administrator Halaby to begin carrying out the report's recommendations. With respect to unresolved differences of opinion between FAA and DOD concerning integrating the SAGE air defense and air traffic control systems--a matter which had delayed release of the report by some two months--Kennedy asked Halaby "to consult with the Secretary of Defense and the President's Scientific Advisor, Dr. [Jerome B.] Wiesner, so that the optimum application of all resources of the Government in the safe and economical use of the airspace may be assured." .

7. GDA-833 Feb 21, 1962: The U.S. Senate confirmed Major General Harold W. Grant, USAF, as FAA's Deputy Administrator, succeeding James T. Pyle (see Dec 31, 1958). A specialist in communications, General Grant was Commander of the Air Force Communications Service when the President selected him, on Feb 1, for the FAA position. Born in Louisville, Ky., General Grant received a bachelor of science degree from Northwestern University in 1928, and was commissioned in the Army Air Corps the following year. In World War II, he served as U.S. Air Signal Planner for Combined Operations in the European Theater and as Deputy Signal Officer in Chief of the Southeast Asia Command in India. During the Korean conflict, he was Vice Commander of the Japan Air Defense Force. After other assignments of high responsibility in the Far East and the United States, he became, in mid-1958, director of communications and electronics in the Office of the Deputy Chief of Staff for Operations, U.S. Air Force Headquarters. From this position he was assigned in July 1961 to the command from which he came to FAA. His decorations include the Legion of Merit with two clusters and the Order of the British Empire. (See Jul 1, 1965.) During the two years after his appointment, Grant helped to work out a series of agreements with military commands that provided close integration of communication systems and joint use of facilities, espcially radar. Under an agreement with the Continental Air Defense Command, FAA handled the ATC operations of interceptor flights going to and returning from a target. These agreements reduced the chances of civil-military midair collisions and provided better defense readiness. The improved coordination of military and FAA activities helped to ease tensions that had developed over the FAA decision to make only limited use the military’s SAGE system in the national ATC system (see Sep 11, 1961, and Dec 1, 1963). .

8. GDA-899 Dec 1, 1963: FAA's air route traffic control center at Great Falls, Mont., began joint use with the Air Force of facilities originally installed to serve the latter's SAGE direction center at Malmstrom Air Force Base, Great Falls. Under this arrangement the same facilities served the dual purpose of air traffic control and air defense. This marked the first use of SAGE data for air traffic control by an FAA facility. (See Sep 11, 1961.) .

Processed Entire File


Accessed Words Hide

Filter Noise Words

No results to report.

Accessed Patterns Found Hide

Number Sort
132 research 101 computer 86 installation 73 installed 69 Research 39 software
37 Automation 21 automation 21 hijacking 17 Curtis 17 Air Defense 17 air defense
16 STARS 13 Stage A 12 Computer 11 Installation 10 installations 9 hijacked
8 installing 8 SAGE 8 NAFEC 7 FAA Technical Center 7 sequestration 7 ADIZ
6 hijackers 6 hijackings 6 ATCRBS 5 terrorists 5 design competition 4 privatization
4 AAS 3 DABS 3 restricted airspace 3 hijacker 2 Hijacking 2 restricted areas
2 Installing 2 Curtis report 2 World Trade Center 1 Aug 23, 1958: 1 May 20, 1926: 1 Aug 22, 1938:
1 Jul 7, 1964: 1 privatize 1 Apr 1, 1964: 1 May 21, 1958: 1 Oct 1, 1958: 1 installer
1 February 3, 2016: 1 May 20, 1964:

Alpha Sort
7 ADIZ 11 Installation 2 Installing 86 installation 10 installations 73 installed
1 installer 8 installing 4 AAS 1 Apr 1, 1964: 1 Aug 22, 1938: 1 Aug 23, 1958:
1 February 3, 2016: 1 Jul 7, 1964: 1 May 20, 1926: 1 May 20, 1964: 1 May 21, 1958: 1 Oct 1, 1958:
13 Stage A 2 Curtis report 17 Curtis 7 FAA Technical Center 8 NAFEC 12 Computer
101 computer 3 restricted airspace 2 restricted areas 39 software 16 STARS 2 World Trade Center
5 terrorists 69 Research 5 design competition 132 research 6 ATCRBS 3 DABS
4 privatization 1 privatize 7 sequestration 17 Air Defense 8 SAGE 17 air defense
37 Automation 2 Hijacking 21 automation 9 hijacked 3 hijacker 6 hijackers
21 hijacking 6 hijackings

Accessed Patterns Not Found

FAATC Mode-s


Metrics Hide

Save Metrics with analysis run all-history.txt 05/28/017 10:09:38 Appended Metrics File

Total Lines: 4123
Blank Lines: 3
Non Blank Lines: 4120
Imperatives: 71
Shalls: 8
Wills: 69
IsReq:

Message: These metrics are what allow you to compare different documents and different analysis runs. Consider moving the numbers into a spreadsheet for visualization. Counts of Shalls, Wills, IsReq, and Imperatives are hardcoded into the tool. You have the ability to enter a Norm value, which can be surfaced after multiple analysis sessions.

Item Risk Count Children % lines % imperative % shall % will % isreq % Norm
AAS s4s

ADIZ s4s

Air Defense s4s

Automation s4s

Beacon RADAR s4s

Computer s4s

Curtis Report s4s

Design Competition s4s

Hijack s4s

Install s4s

NAFEC s4s

NAS Stage A s4s

Research s4s

Restricted Areas s4s

SAGE s4s

8

0.19

11.26

100

11.59

STARS s4s

Shutdown s4s

Software s4s

Startup s4s

Terrorist s4s

z Mined Objects

8

0.19

11.26

100

11.59

Rules Total 21
Rules Triggered 2
Rules Not Triggered 19
Percent of Rules Triggered 9%

Reading Level Hide

Disabling the noise filter may reduce the reading level. Re-run the report to capture metrics for both instances.

Accessed Unique Words:
Accessed Unique Syllables:
Words with 3+ Syllables:
Polysyllabic Count: 0
Reading Level: No reading level is available. Select any rule option and check: Count Accessed Words or use a Reading Level Service which has checked: Count Accessed Words.

Document Shape Hide

The number of children at a particular level translate to a document shape. There are diffrent document shapes and each have implications. The document shapes are: random, rectangle, pyramid, inverted pyramid, trapazoid and diamond.

There are no child counts. Try disabling all services except for the service that has checked: Count Accessed Words.

Services and Triggered Rule Comments Hide

Topics of Interest: Think of this as your highlighter pen or a really advanced search engine option.

. . . 1. AAS No Comment Text in this rule.
. . . . . . Rule Summary Name: AAS Color: BROWN Access Object: \bAAS\b Count Accessed Patterns: CHECKED

. . . 2. ADIZ No Comment Text in this rule.
. . . . . . Rule Summary Name: ADIZ Color: BLUE Access Object: ADIZ Count Accessed Patterns: CHECKED

. . . 3. Air Defense No Comment Text in this rule.
. . . . . . Rule Summary Name: Air Defense Color: PURPLE Access Object: Air Defense Count Accessed Patterns: CHECKED

. . . 4. Automation No Comment Text in this rule.
. . . . . . Rule Summary Name: Automation Color: RED Access Object: automation Count Accessed Patterns: CHECKED

. . . 5. Beacon RADAR No Comment Text in this rule.
. . . . . . Rule Summary Name: Beacon RADAR Color: ORANGE Access Object: ATCRBS|Mode-s|DABS Count Accessed Patterns: CHECKED

. . . 6. Computer No Comment Text in this rule.
. . . . . . Rule Summary Name: Computer Color: GREEN Access Object: computer Count Accessed Patterns: CHECKED

. . . 7. Curtis Report No Comment Text in this rule.
. . . . . . Rule Summary Name: Curtis Report Color: FUCSHIA Access Object: Curtis report|Curtis Count Accessed Patterns: CHECKED

. . . 8. Design Competition No Comment Text in this rule.
. . . . . . Rule Summary Name: Design Competition Color: OLIVE Access Object: Design Competition Count Accessed Patterns: CHECKED

. . . 9. Hijack No Comment Text in this rule.
. . . . . . Rule Summary Name: Hijack Color: RED Access Object: Hijack\w+ Count Accessed Patterns: CHECKED

. . . 10. Install No Comment Text in this rule.
. . . . . . Rule Summary Name: Install Color: BLUE Access Object: install\w+ Count Accessed Patterns: CHECKED

. . . 11. NAFEC No Comment Text in this rule.
. . . . . . Rule Summary Name: NAFEC Color: FUCSHIA Access Object: NAFEC|FAATC|FAA Technical Center Count Accessed Patterns: CHECKED

. . . 12. NAS Stage A No Comment Text in this rule.
. . . . . . Rule Summary Name: NAS Stage A Color: BROWN Case Sensitive : CHECKED Access Object: Stage.A Count Accessed Patterns: CHECKED

. . . 13. Research No Comment Text in this rule.
. . . . . . Rule Summary Name: Research Color: OLIVE Access Object: research Count Accessed Patterns: CHECKED

. . . 14. Restricted Areas No Comment Text in this rule.
. . . . . . Rule Summary Name: Restricted Areas Color: GREEN Access Object: Restricted Area\w+|Restricted air\w+ Count Accessed Patterns: CHECKED

. . . 15. SAGE No Comment Text in this rule.
. . . . . . Rule Summary Name: SAGE Color: PURPLE Case Sensitive : CHECKED Access Object: SAGE Count Accessed Patterns: CHECKED

. . . 16. STARS No Comment Text in this rule.
. . . . . . Rule Summary Name: STARS Color: NAVY Case Sensitive : CHECKED Access Object: STARS Count Accessed Patterns: CHECKED

. . . 17. Shutdown No Comment Text in this rule.
. . . . . . Rule Summary Name: Shutdown Color: ORANGE Access Object: Seques\w+|privatiz\w+ Count Accessed Patterns: CHECKED

. . . 18. Software No Comment Text in this rule.
. . . . . . Rule Summary Name: Software Color: MAROON Case Sensitive : CHECKED Access Object: software Count Accessed Patterns: CHECKED

. . . 19. Startup No Comment Text in this rule.
. . . . . . Rule Summary Name: Startup Color: BROWN Access Object: May 20, 1926:|Aug 22, 1938:|May 21, 1958:|Aug 23, 1958:|Oct 1, 1958:|Apr 1, 1964:|May 20, 1964:|Jul 7, 1964:|Feb\w+ 3, 2016: Count Accessed Patterns: CHECKED

. . . 20. Terrorist No Comment Text in this rule.
. . . . . . Rule Summary Name: Terrorist Color: NAVY Access Object: terrorist\w+|world trade center Count Accessed Patterns: CHECKED

original processing URL http://localhost:4444/~gda/satpro.cgi v 1.6 p

10:09:38 Start Time
10:09:44 End Time
6 Seconds

5.008006 satpro pid: 5404 C:/Windows httpd pid:2096 error pid: 4036