This page was updated on 12/11/2001
ETAP
The
new version of ETAP V2.1.0 is on the MSDT available for downloading at the MSDT
INTRA-net site at http://cru-x.faa.gov/downloads
This version will also be on the June 2001 CRU-X release.
Reported bugs to be fixed on this new version are the "domestic overwater/oceanic displays" on the CI report, possible problem with DOW calculations, possible problem with DOW/Oceanic prior month averaging. Thanks to ZOA and ZHU focals for bringing these possible bugs to the attention of the NVT. Remember when reporting bugs send the bug report to the entire ETAP NVT listed below. MSDT is also updating profile information as requested by facilities (new sectors, non-approach airports etc).
It is important each facility verify their profile information contained in their data base. Any bad profile information such as, but not limited to, Non-approach airports or an incorrect adapted altitude can cause you CI to be inaccurate.
Does MSDT have your ETAP Data?
Missing a few days
MSDT is preparing to run Classification Indexes (CI) on all ETAP equipped ARTCCs for August 2001. If MSDT does not have your ETAP data for any period of time used in that CI run your CI will be impacted. See the "Feedlist" file below to ensure MSDT has all the data to run a August 2001 CI.
This "Feedlist file" represents the latest, one year, snap-shot of data on-hand at MSDT. As HAME tapes are received by MSDT they update this file. This file shows you missing ETAP data as of October 25, 2001 and uses a September 2001 filter.
If days are not recoverable MSDT should be notified so they can indicate the data is lost. Attention:
ZME- can we get June 10, 2001 or is it non recoverable?
ZLC- MSDT needs your September 2001 data.
ZAB- MSDT needs your September 2001 data.
Have management make arrangements to get the data to MSDT or notify MSDT the data is gone.
Check the file on the link below to ascertain the actual missing dates. If your facility has red dates have your management person send the data to MSDT via tapes or via FTP and notify MSDT by sending Tyese Brown (MSDT) an email at 9-AWA-MSDT@faa.gov or via ccmail. If the data is lost let Tyese know so she can update the feedlist. Tyese can also be reached via phone at MSDT by dialing (202) 493-5787.
Missing September 2001 tapes
Tapes normally take up to 7 days from time of mailing to be received and processed by MSDT. As of October 23, 2001 MSDT has not received the Setpember 2001 Hame tapes for ZLC and ZAB. We will run August CIs next week so ZLC and ZAB please contact Tyese and figure out where your tapes are.
Questions on receipt of tapes should be directed to Tyese Brown MSDT at (202) 493-5787. Be nice to her...she's nice to us...the problem is the archaic data delivery process...not her.
Remember to set up procedures to ensure your data is received in a timely fashion. Get the missing data in as soon as possible.
September 2001 Feedlist as of October 25, 2001
The following facilities still need to email me a September 2000 CI run at oceanview@worldnet.att.net ----->>>>>> ZAU, ZLC, and ZME.
Other ETAP Program stuff for Domestic ARTCCs
All ARTCCs will need to set up access to the Intra-net for their ETAP Focals.
Here are some much needed files for ETAP Focals. Check back often we'll use this sit to try to supply you what you need.
I have included the ETAP Documentation (3 files). You will need the Users Guide, 7210.57 and Manual Augmentation Guide. You can get them here or from the MSDT web site on the Intra-net. Also listed below is the Position Classification Standard (with break points) and the 7210.57 Traffic Count Order.
These are large files (most won't fit on a floppy) but they are very well done and an absolute requirement for ETAP Focals and Regional Coordinators.
I would like to thank beyond thanks; the National Validation Team (ETAP) members for their tireless dedication to making these documents superb and making an old "track file data base", aka HAME; talk to ETAP.
If you know any of these people, or you don't, or if you see them, don't see them, talk to them, heard of them or whatever....say "thanks" for their tireless, and thorough efforts. You can also drop them an email by clicking below. Don't beat them up on the standard...that wasn't their mission. They were simply tasked with making apple pie (ETAP V2.0) using only peaches (HAME data) and validate CIs. They had direction to not worry or even bother with what the CI was....just get it right so we could take our beating and move forward. Here they are:
Tom Meints Seattle Center Supe
Mike Riley Seattle Center Controller
Tom Roberts Boston Center Controller
Mike Edmonds Boston Center Controller
Cris Johnson Chicago Tracon Controller and a whole lot more.
Bill Peery ATX 20
and
Mark is an extremely talented individual. Mark currently resides between "good time" and "bad time" and between a "Flow Control bargaining unit member" and a talented program developer. Mark took some programming code (that wasn't his) and read it like a book and rewrote the story according to the script. Thanks to Mark and MSDT for the support.
ETAP Version 2.0.X is a bridge to version 3.0 "data offload" that makes the requirements of manual augmentation a temporary necessity to truly get an accurate CI. Of course it is important to manually augment correctly too. See the examples in the Manual Augmentation Guide and make sure you set up procedures to follow the instructions on who to augment and who not to. Keep some paper/electronic trail.
If you have a problem with the program make sure you've read the users guide and then email the question/problem to MSDT at 9-AWA-MSDT@faa.gov or call Tech support at (202) 493-5787. Also, copy Bill Peery ATX 20 and Jeff Walukonis so we can have the NVT help support MSDT. NATCA Focals should also participate on the .net BBS under the ETAP Topic for the details on current program issues and solutions of other ETAP Users. If you need help, want to talk to another facility to see how their doing or need assistance from the NVT contact them at etap_contacts.xls
Anyway....thanks to the NVT, here are the 3 ETAP Version 2.0 supplemental files:
ETAP Users Guide for ETAP Version 2.0.X (zipped 1.3 meg)
ETAP Manual Augmentation Guide (unzipped; zipping it only knocks off 200K size is 1.3 meg)
FAA 7210.57 supplemental order (tiny file 27kb)
Here is the Position Classification Standard and the 7210.57 Traffic Count Order
Position Classification Standard (Break Points are in the back of this document)
Very Important info follows:
It is important that facilities verify their profile and adaptation information as described in the users manual. You will want to do this before you process data. If you find a change after you have processed the data you will need to complete the form in the back of the Users Manual, forward the form as required and obtain a new release of ETAP and then re-process your data.
Go to the users manual and read up on the following in detail:
Verify Profile and Adaptation Information
It is critical that the Profile and Adaptation information contained in ETAP is accurate. Verify all information BEFORE processing any data in ETAP.
To view the facility profile data select Profile Data from the View pull-down menu.
The Profile Data screen will be displayed.
The facility profile provides general information on the facility, such as ID, Name, Region, Type, Description, and Computer ID. It also provides the Profile Version and the date that the Profile was last updated. Four items in the Profile are used when calculating a CI:
- The low and high airspace are averaged and that value is used to calculate the Density Add-on.
- The number of foreign facilities that a center interacts with determines the Foreign Add-on. (Number will not exceed 3)
- If a center is eligible for the Mountainous Terrain Add-on it is indicated here.
To view the facility Adaptation data select Adaptation from the View pull-down menu.
A window with seven radio buttons will be displayed. Select a radio button to review the data in the corresponding table.
- Non-Approach Control Airports is a list of all airports that the center has adapted in HOST and are not within an approach control.
- VFR Adapted Altitude is the altitude that is adapted in HOST for VFR. Flight plans for aircraft with an assigned altitude of VFR OTP and flight plans entered using a "VP" flight plan or will show this altitude as the assigned altitude.
- CERAP Facilities is a list of those facilities that are "hosted" by a domestic center but are actually a enroute facility themselves. Most centers will not have an entry in this table.
- Operational Sectors is a list of all sectors within the center that work live traffic. Tracks started at any position not listed in this table will be rejected by ETAP.
- Fringe Airports is a list of airports that are within an approach control and are either outside, or partially outside of center airspace. The majority of arrivals/departures worked by the center from airports in this list are transferred/received directly from the approach control. Airports that are "hosted" by your center should not be included in this list.
- Jet Type Aircraft is the table that ETAP uses to determine if an aircraft is a jet or prop.
- Military Radar Units is a list of MRU’s where the center has the capability of automated track transfer.
ETAP users are not given the capability to change Profile or Adaptation information within the program. If any information is incorrect, use the form provided in Appendix 1 to request changes.
then,
September 2000 CI
Attention NATCA ETAP Focals:
Once you have the program up and running AND you have your profile/adaptation validated; run a CI for September of 2000. This run will produce a result that appears similar to what is below this section. Paste that info into an E-Mail and send it to me at oceanview@worldnet.att.net also include what version of ETAP the CI was run on.
This way we'll know your up and running and compare your CI and amount of data to the ones run at MSDT for September of 2000. The CI run looks like this:
{\rtf1\ansi\deff0\deftab720{\fonttbl{\f0\fswiss
MS Sans
Serif;}{\f1\froman\fcharset2 Symbol;}}
{\colortbl\red0\green0\blue0;}
\deflang1033\pard\plain\f0\fs17 Facility = ZMP
\par End Date = 09/30/2000
\par CI = 1471.2449
\par Hours = 8640 (360 Days * 24 hours)
\par Unweighted Top 1830 Count = 808817
\par Unweighted Top 1830 Average (Cav1) = 441.97650273224
\par Unweighted Second 1830 Count = 643996
\par Unweighted Second 1830 Average (Cav2) = 351.910382513661
\par Dt (1 + (Cav2 / Cav1)) = (1 + (351.9 / 442.0))
\par Dt (1 + (Cav2 / Cav1)) = 1.79621966402783
\par Weighted Top 1830 Count = 1203477.0
\par Average Top 1830 (Wav1) = 657.637704918033
\par Total Air Traffic = 2222054
\par Total Military = 51737
\par MiltaryAddon ((TotalMilitary / TotalAirTraffic) / 4) * Wav1 = ((51737 /
2222054) / 4) * 657.6
\par MiltaryAddon = 3.828
\par Total Jets = 1283021
\par Jet Mix (TotalJet / TotalAirTraffic) = 1283021 / 2222054
\par Jet Mix = 0.5774
\par Total Props = 939033
\par Prop Mix (TotalProp / TotalAirTraffic) = 939033 / 2222054
\par Prop Mix = 0.4226
\par Mix used for calculation = 0.4226
\par Jet/PropMixAddon (MixToUse / 4 * Wav1) = 0.4226 / 4 * 657.6
\par Jet/PropMixAddon = 69.4789
\par Domestic Percentage (TotalOceanic / TotalAirTraffic) = 0.0 / 2222054
\par Domestic Percentage = 0.0
\par DomesticOverwaterAddon (DomesticPercent / 5 * Wav1) = 0.0 / 5 * 657.6
\par DomesticOverwaterAddon = 0.0
\par Oceanic Percentage (TotalOceanic / TotalAirTraffic) = 0.0 / 2222054
\par Oceanic Percentage = 0.0
\par OceanicAddon (OceanicPercent * 3 * Wav1)= 0.0 * 3 * 657.6
\par OceanicAddon = 0.0
\par DensityAddon = (Wav1 / (objProfile.Airspace / 10000)) * 1.5 = (657.6 /
(287644 / 10000)) * 1.5
\par DensityAddon = 34.2944
\par Average High 1830 Hourly Flight Time Minutes (Total Flight Time / 1830) =
22733640 / 1830
\par Average High 1830 Hourly Sector Penetrations (TotalPenetrations / 1830) =
1443004 / 1830
\par AirspaceUsageAddon (Average High 1830 Hourly Flight Time Minutes / Average
High 1830 Hourly Sector Penetrations * 3) = 12422.7541 / 788.5268 * 3
\par AirspaceUsageAddon = 47.2632
\par Foreign Percentage = 1
\par Mountainous Percentage = 0
\par ProfileAddon ((MountainousPercent + ForeignPercent) * Wav1) = ((0.0 + 0.01)
* 657.6377)
\par ProfileAddon = 6.5764
\par
\par (1 + (Cav2 / Cav1)) * (Wav1 + MilAdd + TfcMix + DOWAdd + Ocean + Density +
Airspace + Profile)
\par (1 + (351.9104 / 441.9765)) * (657.6377 + 3.828 + 69.4789 + 0.0 + 0.0 +
34.2944 + 47.2632 + 6.5764)
\par
What issues or bugs in ETAP Version 2.0.1 are fixed or being worked?
Known issues "error 52 message". This issue appears when you have selected a "default" location (check box) for the ETAP Program to look for your data and then move to another computer where the mapping is different. This issue is fixed in ETAP Version 2.0.3.
How long will we have to do the Manual Count?? See the following email sent to ETAP focals:
ETAP Focals, Please show this to your FACREPs and Post this in all Host equipped ARTCCs:
As facilities are working through implementation of the Manual Augmentation Guide please understand this is an interim bridge to ETAP 3.0.
Let me explain.
There is a project currently under way in the Agency (ATX-400 a.k.a. MSDT) called Data Off-Load. The initial test site, we have heard, is Fort Worth Center (ZFW).
In San Juan CERAP (ZSU), Anchorage Center (ZAN) and Honolulu Consolidated Facility (HCF) they use a Micro EARTS Parser Program to process the data and determine a Classification Index (CI) instead of ETAP and a Host System that generates only "Track Information" (starts/drops). The Micro Earts Parser program is superior because it uses "Radar data" instead of Track File Data (HAME) to process the operation.
This Micro EARTS parser provides data that is much superior to HAME data provided by Host Equipped ARTCCs. The Micro EARTS Parser Program is currently under final development by Cris Johnson (NVT). This program actually "sees" the radar returns from the Aircraft and "knows" where sector boundaries are. This program can capture the aircraft in accordance with the Standard without Manual Augmentation.
The Off Load project is under initial beta development and testing by MSDT at Fort Worth ARTCC (ZFW). Once this "data stream" is available the Micro EARTS Parser should be able to process that data for all the Host equipped ARTCCs.
The problem is I cannot tell you when MSDT will be ready to implement Off-Load for all Host equipped ARTCCs. I have heard ZFW may be ready by this summer.....but I heard that last summer too. As with all Computer programming initiatives it is impossible to give an exact date of the first Beta Site at ZFW going operational with Data Off-Load. When ZFW goes, and the waterfall of implementation hits your facility, you won't have to do any Manual Augmentation. My guess would be two years.
So the bad news is due to the limitations of HAME data we must use Manual Augmentation, Fringe list tools etc to get a CI we can use. The good news is ETAP Version 3.0, which starts at ZFW will fix that.
Reminds me of a story I once heard: "No matter where you go, there you are".
Additional Information
If you have any other information you want to see here send an email to me at Oceanview@att.net and include the subject ETAP. Also, if you are the ETAP Focal for your facility and have a question send it to Tom.Meints@faa.gov with a copy to Oceanview. Tom will answer the question and use it to help compile our Frequently Asked Questions page for ETAP that is currently under construction....as is the rest of this page.