SOLICITATION NOTICE
99 -- Instrument Procedures Development System (IPDS)
- Notice Date
- 5/24/2005
- Notice Type
- Solicitation Notice
- Contracting Office
- FEDERAL AVIATION ADMINISTRATION, AMQ-310 Aeronautical Center (AMQ)
- ZIP Code
- 00000
- Solicitation Number
- 4192
- Response Due
- 6/7/2005
- Archive Date
- 7/7/2005
- Description
- MARKET SURVEY/REQUEST FOR INFORMATION INSTRUMENT PROCEDURES DEVELOPMENT SYSTEM (IPDS) General Information: The Federal Aviation Administration (FAA), Aviation System Standards (AVN) is conducting a Market Survey / Request for Information to improve the Government's understanding of the current marketplace, obtain information on available technology and innovative approaches that may fulfill its mission need, and gain insight into industry capabilities and best practices. This announcement is not a Screening Information Request (SIR) or a Request for Proposal (RFP) of any kind. Further, the FAA is not seeking or accepting unsolicited proposals. All interested parties are advised that the FAA will not pay for any information or any administrative costs incurred that are associated with any response received from industry in response to this Market Survey / Request for Information. Therefore, any costs associated with Market Survey / Request for Information submissions will be solely at the interested party's expense. Response to this Market Survey: Attachment A describes general characteristics of the Instrument Procedures Development System (IPDS) system requirements. Attachment B is the vendor response template. Interested vendors are required to provide full and complete responses to the performance requirements listed in Attachment B. Special emphasis is being placed on vendors with experience writing software incorporating Terminal Instrument Procedures (TERPS) and Procedures for Air Navigation Services, Operations (PANS-OPS) criteria. Excessively elaborate responses containing marketing materials are not desired and may be discarded without review. Respondents to the Market Survey / Request For Information may be requested to provide additional information at the option of the Government. Information obtained from Attachment B will be used to support an acquisition strategy for the IPDS. Any information provided under this market survey is for informational purposes only and will not be released. Any proprietary information submitted will be protected if appropriately marked. No evaluation of vendors will occur and vendor participation in any informational session is not a promise of future business with the FAA. All responses (one response per company) are to be provided on company letterhead and limited to a total of 10 pages taking into account the page count limitations specified in Attachment B. No type font less than 12-point may be used. Responses must be received no later than June 7, 2005, 3:00 p.m., Central Standard Time. Market survey responses received after the time and date specified will be determined to be late and will not be considered and shall be returned to the sender. The FAA prefers that all submittals, including attachments, be submitted electronically to the following email address: Sandra.Fink@faa.gov. Please submit in a portable document format (pdf); however, Microsoft Word is acceptable. If you cannot respond electronically, please send to: Federal Aviation Administration Attn: Sandra Fink, Contracting Officer, AMQ-310 6500 S. MacArthur Boulevard Oklahoma City, OK 73169 ATTACHMENT A DESCRIPTION OF MISSION NEED INSTRUMENT PROCEDURES DEVELOPMENT SYSTEM (IPDS) The Federal Aviation Administration (FAA), Aviation System Standards (AVN) has a need for the development of an Instrument Procedures Development System (IPDS) to fully replace its current Instrument Approach Procedure Automation (IAPA) System. The purpose of this market survey is to determine which vendor sources have the ability to participate in an IPDS procurement. Vendors should be capable of fulfilling the IPDS requirements as specified in Attachment A and in accordance with Attachment B. The United States Government has a substantial investment in a computer program, Global Procedures Designer (GPD), developed by MacDonald, Dettwiler and Associates, Inc. (MDA). This software was developed in a joint effort between the United States Air Force (USAF) and the FAA under USAF contract F19628-01-C-0012, through a charter agreement. The United States Government owns limited rights to GPD. The GPD Source Code is owned by MDA. It is the FAA's intent to modify and expand on the GPD software to work in a J2EE Architecture. 1. IPDS REQUIREMENTS 1.1. General IPDS Characteristics 1.1.1. Business 1.1.1.1. IPDS shall provide create and modify capability for all segments of terminal and en-route instrument flight procedures, for both fixed-wing and rotor-wing aircraft. 1.1.1.2. IPDS shall utilize United States Terminal Instrument Procedures (TERPS) criteria required for domestic instrument flight procedure development or amendment. 1.1.1.3. IPDS shall utilize International Civil Aviation Organization (ICAO) Procedures for Air Navigation Services, Operations (PANS-OPS) criteria required for international instrument flight procedure development or amendment. 1.1.1.4. IPDS shall allow approaches and departures to utilize multiple runways and share common segments where applicable. 1.1.1.5. IPDS shall provide capability for creating or changing all common flight procedure final segments in one work area in one work session. For example GLS, LPV, LNAV/VNAV, LNAV, GPS, RNP for Area Navigation (RNAV) procedures and ILS/LOC, TLS, MLS/AZIMUTH procedures. 1.1.1.6. IPDS shall execute either as a thin-client while attached to the FAA Air Traffic Organization (ATO) network, or as a thick-client standalone local application able to execute when not attached to the network and synchronize upon command. 1.1.1.7. IPDS shall fully replace the IAPA system used in the National Flight Procedures Office (NFPO) and all regional Flight Procedures Offices (FPO's). 1.1.1.8. IPDS shall perform an automated evaluation of proposed procedure criteria changes (TERPS and PANS-OPS) against stored active instrument flight procedures, reporting all impacts textually and graphically. New controlling obstacles shall be identified. 1.1.1.9. IPDS shall perform an automated evaluation of active instrument flight procedures for all changes to supporting master data (any change to ORS, AIRNAV, etc) reporting all impacts textually and graphically. New controlling obstacles shall be identified. 1.1.1.10. IPDS shall perform an automated periodic evaluation of stored active instrument flight procedures in accordance with FAA Order 8260.19, Flight Procedures and Airspace, requirements; reporting all impacts textually and graphically. New controlling obstacles shall be identified. 1.1.1.11. IPDS shall provide functionality to evaluate and quantify the impact of existing or proposed obstacles on all stored instrument flight procedures, minimum vectoring altitude (MVA) charts, minimum Instrument Flight Rules (IFR) altitude (MIA) charts and emergency obstruction vectoring (EOV) maps. The impact will be determined by applying U.S. TERPS or PANS-OPS criteria as required by location. 1.1.1.12. IPDS shall provide capability for airspace analysis and procedure conflict. 1.1.1.13. IPDS shall provide a computer-aided drawing tool. 1.1.1.14. IPDS shall provide on-line help and training. 1.1.1.15. IPDS shall include, but not limited to, the following stand alone applications: Geodetic Calculator, Datum Conversion, and Database Inquiry. 1.2. Data 1.2.1. IPDS shall store and retrieve instrument flight procedure data by segment in and from the Aviation System Standards Instrument Flight Procedure database or other sources. 1.2.2. IPDS shall store and retrieve instrument flight procedure surfaces in geo-spatial format. 1.2.3. IPDS shall acquire obstacle data from AVN's Obstacle Repository System (ORS). 1.2.4. IPDS shall acquire airport, runway and NAVAID data from AVN's AirNav database. 1.2.5. IPDS shall provide entry of and conversion between units of measure, such as feet and meters, statute and nautical miles, and datums, as necessary on data entry, displays and reports. 1.2.6. IPDS shall be developed in a modular fashion, with criteria validation made available to be executed on demand either within the internal environment (as a callable service(s) to IPDS, for example) or as a web-service(s) with a published interface for the external environment (Intranet or Internet). 1.2.7. IPDS shall acquire Standard Terminal Arrival Routes (STARs) from Air Traffic Terminal Area Route Generation, Evaluation, and Traffic Simulation (TARGETS) system and validate them against TERPS criteria. IPDS shall have the capability to disseminate validated results via web service(s) or other mechanisms. 1.2.8. IPDS shall accept Obstacle Evaluation (OE) cases studies. (TBD sources) 1.3. Presentation 1.3.1. IPDS shall have the capability to use one or multiple work areas at the same time. 1.3.2. IPDS shall allow the development of multiple complete instrument flight procedures within a single work area. 1.3.3. IPDS shall allow use of multiple work areas. 1.3.4. IPDS shall have the capability to work with all parts of the application, save, exit, re-start, expand work area data, and reconstruct procedure segments. 1.3.5. IPDS shall provide information, warning, stop, alert, and other type messages in accordance with acceptable criteria and standards. 1.3.6. IPDS shall allow user to control segment analysis execution. 1.3.7. IPDS shall provide capability to manipulate copies of master data for analyzing instrument flight procedures. 1.3.8. IPDS shall allow entry, display and reporting of courses, headings, tracks, bearings, and radials in 'true' or 'magnetic' north. 1.3.9. IPDS shall provide work area selection and procedure design by user specification, both textually and graphically. 1.3.10. IPDS shall prominently identify the controlling obstacle within each segment of an instrument flight procedure. 1.3.11. IPDS shall provide capability to add and remove displayed layers (overlays) of terrain, airspace, NAVAIDs, procedure trapezoid, land-use and environmental data. 1.3.12. IPDS shall display two-dimensional and three-dimensional graphical trapezoids of instrument flight procedures, by flight segment. 1.4. Outputs 1.4.1. IPDS shall provide database revision reports. 1.4.2. IPDS shall create, store, retrieve and display the flight inspection graphic (FIG) associated with an instrument flight procedure. 1.4.3. IPDS shall provide reports or results regarding OE evaluations against all stored instrument flight procedures, minimum vectoring altitude (MVA) charts, minimum IFR altitude (MIA) charts and emergency obstruction vectoring (EOV) maps that are impacted by a proposed obstacle, specifying the amount of impact. In addition, all procedures that are not impacted but are within the user-specified nautical mile radius will be reported. 1.4.4. IPDS shall be capable of disseminating obstacle evaluation results to Air Traffic, or other FAA office automation system via web service. 1.4.5. IPDS shall work with other applications and databases to generate a color graphical representation of an instrument flight procedure. 1.5. Other Application Interfaces and Integration: 1.5.1. Application shall provide the capability to interface / integrate with the following applications: 1.5.1.1. Instrument Flight Procedures (IFP) - Output procedure builds to IFP, in accordance with the IFP Data Model and/or XML schemas for procedure documentation and Aeronautical Radio Incorporated (ARINC) coding. 1.5.1.2. OE/IFR - Provide procedure segment builds and altitude information to the OE application. (TBD sources) 1.5.1.3. Electronic Notice to Airmen (E-NOTAM) - Provide data output for procedures requiring Notice to Airmen (NOTAM) action and receive current NOTAM information. 1.5.1.4. Provide data output to AVN approved aeronautical databases for data updates. Read data from AVN approved databases for data elements required for procedure development. 1.5.1.5. Flight Inspection Graphic (FIG) - (TBD sources) 1.5.1.6. Obstacle Repository System (ORS) - (TBD sources) 1.5.2. Application Interfaces include, but not limited to: AVN Process Tracking System (APTS) RNAV-PRO Collision Risk Model (CRM) Expanded Service Volume Management System (ESVMS) TARGETS Sector Design and Analysis Tool (SDAT) ARINC Tools Flight Management System (FMS) and DME/DME Screening Model 1.6. Customer Base Requirements: 1.6.1. The IPDS may include requirements for other federal or international agencies in anticipation of their subsequent use. The current customer base is defined in the following paragraphs: 1.6.1.1. National Flight Procedures Office (NFPO) located in Oklahoma City. The organization consists of approximately 115 procedure development specialists, 11 team leads, 7 managers, and 8 supporting staff. The quantity of personnel at the NFPO is subject to change periodically based on workload. 1.6.1.2. Nine Flight Procedures Offices (FPO) located in Boston, MA; New York City, NY; Atlanta, GA; Kansas City, MO; Fort Worth, TX; Los Angles, CA; Anchorage, AK; Seattle, WA; and Chicago, IL. The number of people at each office varies from 3 to 8 for an approximate overall staff of 45, and is subject to change. 1.6.1.3. Mobile capabilities with/without network connectivity at locations worldwide. 1.6.1.4. USAF staff of approximately 20. 1.6.1.5. Commercial vendors. 1.6.1.6. System shall have the expandability to accommodate additional users and locations and/or remove users and locations. 1.6.2. FAA system requirements are listed below that shall be further defined. 1.6.2.1. Ability to display the design menus, graphics, forms, and flight inspection graphics together without having to minimize back and forth between them. 1.6.2.2. Ability to centrally manage all work areas to include: 1.6.2.2.1. Design Process 1.6.2.2.2. Graphic Process 1.6.2.2.3. Publication Process 1.6.2.2.4. Periodic Review 1.6.2.2.5. Check In/Out and Sharing Processes 1.6.2.2.6. Search Tools 1.6.2.2.7. Reports 1.6.2.3. Application's response time shall have time limitation for routine and complex calculations. 1.6.2.4. The IPDS system availability shall comply with a specified (TBD) mission capable (MC) goal during peak operating hours (Monday through Friday 6:00 a.m. to 6:00 p.m.). 1.6.2.5. System shall support and interface with current versions of Windows compatible programs. 1.7. General Requirements: 1.7.1. Database Requirements 1.7.1.1. Oracle Database (current version) 1.7.1.2. Erwin entity relationship Diagrams 1.7.1.3. Limited legacy conversion requirement 1.7.1.4. Data Requirements: Airports/Heliports Runways/Helipads Lighting Systems Weather Systems Navigational Aids Fixes Obstacles (National Aeronautical Charting Office (NACO) - Central Depository) Spot Elevations Digitized Terrain and Elevation Data (DTED) (Level 1 and/or 2) Digital Elevation Model (DEM) (Level 1 and/or 2) Light Detection and Ranging (LIDAR) (Obstacle Surveying Method) Terrain Features (Transmission lines, Roads, Railways, Waterways, Shorelines, Urban Areas, etc) Airspace (Class A, B, C, D, E, G), Special Use (Restricted, Prohibited, Warning, Military Operations Area (MOA)) Air Traffic Boundaries Airways / Jet Routes / Q Routes Digital MVA/MIA Charts Digital Enroute Hi/Low Charts Digital Maps of 1:24/25K, 1:100K, 1:500K, and other scales (1:50K, 1:63,360, 1:250K, etc), for areas not covered with previous scales. 1.7.2. Anticipated possible Data Sources: AirNav IFP APTS AAFIF DTED/DEMS LIDAR OE/AAA TARGETS Sectional Maps QUADS ORS FAA 405 AIP 1.7.3. Application Technical Requirements 1.7.3.1. J2EE architecture 1.7.3.2. Periodic code reviews 1.7.3.3. On-demand text help for users 1.7.3.4. Version control 1.7.4. Historical/Audit requirements 1.7.4.1. Data Warehouse 1.7.5. Integration Requirements 1.7.5.1. Centralized security model 1.7.5.2. Centralized code tables such as Country, Region, State, etc 1.7.5.3. Web services/API 1.7.6. General IT Requirements 1.7.6.1. IT standards 1.7.6.2. User and system documentation 1.7.6.3. Software installation methodology 1.7.6.4. Test Plans 1.7.6.5. Detailed test plans tied to requirements 1.7.7. Notify all users of additions, changes and deletions to Airports, Runways, NAVAIDS, and Obstacle Data. 1.7.8. Application shall read from AVN approved database sources. All data stored in AVN approved databases to be obtained from FAA recognized/authorized source. 1.7.9. Application shall: 1.7.9.1. Utilize the Windows operating system for presentation layer 1.7.9.2. Have web-based functionality running on IE6.0 or higher 1.7.9.3. Be written to operate in a thin and thick client configuration 1.7.9.4. Provide thin client usage when operating when connected to a WAN and a client-based when operating in a stand-alone configuration 1.7.9.5. Be structured and coded in the J2EE architecture 1.7.9.6. Include but not be limited to Java, Java Script, SQL, XML, and Oracle database 1.7.9.7. Conform to Department of Transportation (DOT) and FAA security requirements 1.7.9.8. Operate on a Pentium based PC, running at 2ghz with 512meg of RAM and 10 gig of hard drive space. 1.7.9.9. Allow GLS, LPV, LNAV/VNAV, LNAV, GPS, and RNP finals and associated shared segments within the same work area. 1.7.9.10. Allow arrivals and departures to be based on single or multiple runways contained within the same work area, having shared and unique segments within each route. 1.7.9.11. Include QC / QA / Lead screening capabilities as well as informational, warning, and stop messages. 1.7.9.12. Provide the capability to layer data and change their layer levels. ATTACHMENT B MARKET SURVEY / REQUEST FOR INFORMATION RESPONSE TEMPLATE INSTRUMENT PROCEDURES DEVELOPMENT SYSTEM (IPDS) The purpose of this market survey is to determine which vendor sources have the ability to fulfill the IPDS requirements specified in Attachment A. Responses to this Market Survey / Request for Information must include full and complete descriptions on how the respondent meets each of the performance requirements listed below. The FAA is looking for companies with the following capabilities, qualifications, and staffing: 1. Experience in writing software incorporating Terminal Instrument Procedures (TERPS) criteria in excess of 10 years. 2. Experience in writing software incorporating Procedures for Air Navigation Services, Operations (PANS-OPS) criteria in excess of 3 years. 3. Knowledge and understanding of FAA Order 8260.3, United States Standard for Terminal Instrument Procedures (TERPS) and FAA Order 8260.19, Flight Procedures and Airspace. 4. Experience in writing software capable of performing Obstacle Evaluation (OE) in accordance with TERPS criteria including CFR 49 Part 77. 5. Capability in writing software in a J2EE Architecture. 6. Staffing sufficient to perform the IPDS requirements. Respondent must have access to software staffing of at least 30 personnel. 7. Previous history designing and delivering multi-million dollar software systems to government agencies. 8. Familiarity with Unix and Microsoft based server platforms. 9. Extensive knowledge of Oracle database in excess of 5 years (illustrate certifications). 10. Experience applying geo-spatial data elements in the configuration and design of instrument flight procedure software. 11. Proficiency using Rational Unified Process in excess of 5 years. 12. Experience in using Environmental Systems Research Institute (ESRI) Geographic Information System (GIS) and Mapping software in excess of 5 years. 13. Experience in building Erwin entity relationship diagrams in excess of 2 years. 14. Experience designing all segments of terminal and en-route instrument flight procedures, for both fixed-wing and rotor-wing aircraft in excess of 5 years. 15. Experience in designing ground and space-based instrument flight procedures in excess of 5 years. 16. Knowledge of Aeronautical Radio Incorporated (ARINC) 424 coding specifications. The response is limited to ten (10) pages.
- Web Link
-
FAA Contract Opportunities
(http://www.asu.faa.gov/faaco/index.cfm?ref=4192)
- Record
- SN00814336-W 20050526/050524211821 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |