SOURCES SOUGHT
99 -- Assessment of Aviation System Modeling Efforts
- Notice Date
- 7/16/2003
- Notice Type
- Sources Sought
- Contracting Office
- FEDERAL AVIATION ADMINISTRATION, ACX-52 W.J. Hughes Tech Center (AC= T)
- ZIP Code
- 00000
- Solicitation Number
- DTFACT-03-R-00016
- Response Due
- 7/21/2003
- Point of Contact
- Phyliss Schlegel, (609) 485-4380
- E-Mail Address
-
Email your questions to phyliss.schlegel@faa.gov
(phyliss.schlegel@faa.gov)
- Description
- Small businesses qualified to respond to the following Statement of W= ork (SOW), shall e-mail only phone calls will not be returned) the Contract= ing Officer at Phyliss.Schlegel@faa.gov by close of business July 22, 2003,= with a request to receive the Screening Information Request (SIR). Draft = SOW follows: C.1=09 Introduction The Federal Aviation Administration's (FAA) Aviation Risk Analysis Section = (AAR-490) is responsible for conducting research in the area of risk manage= ment decision support in support of the Flight Standards System Approach to= Safety Oversight (SASO) program. The primary sponsor for the research is = the Flight Standards Certification & Surveillance Division (FSAIC), which i= s part of the Flight Standards Division (AFS) of the Certification and Regu= lation (AVR) Directorate of the FAA. AFS directs, manages and executes cer= tification, inspection and surveillance activities to ensure adequacy of fl= ight procedures, operating methods, airmen qualification and proficiency, a= ircraft maintenance, and the maintenance aspects of continuous airworthines= s programs. =20 C.2=09 Project Background and Objectives The Risk Management Decision Support Strategic Plan describes Task number 2= .0, Aviation System (AS) Functional Model, as follows: The purpose of this task is to develop functional models of the aviation sy= stem, e.g., 14 CFR Parts 121 (Operating Requirements: Domestic, Flag, And S= upplemental Operations), 142 (Training Centers), and 145 (Repair Stations).= The developed functional model will be one input (examples of other input= s are historical accidents/incidents, hazards in similar industries, etc.) = to the task titled as AS Risk Analysis, which is partly geared to identify = those work processes (or business processes) that are vital to maintain or = increase the desired level of safety. The developed functional models will= also facilitate the communication between the FAA and industry.=20 Over the past several years, the FAA and industry developed the Air Carrier= Operations System Model (ACOSM) and the Repair Stations Functional Model (= RSFM). Model development of Training Centers and Agricultural Aircraft Ope= rations is currently underway. The Risk Management Decision Support Strategic Plan describes Task 3.0, Ove= rsight System (OS) Functional and Data Models, as follows: The purpose of this task is to develop a functional and data model of selec= ted components of the current OS. The goal is to develop a logical model o= f the OS functions and data rather than a physical model. Recall that the = logical model deals with "what" is being executed whereas the physical mode= l deals with "how" the things are being executed. The developed functiona= l and data models of the OS and AS functional model would be a basis to con= duct the research. Therefore, the developed models of the OS should be as = close as possible to the current oversight system. A model of the Certification Process will begin shortly. However, the FAA = will benefit from an "Assessment of Aviation System Modeling Efforts;" that= is, take a step back and evaluate the current models and methodologies to = address the following questions: Modeling Tool - Is the FAA using the modeling methodology best suited for i= ts needs? =20 Knowledge Elicitation - How effective are the currently employed methods to= capture the knowledge of participants to develop the models? =20 Modeling Standards - How can standards be developed so that the same approa= ch is used each time a model is developed? C.3=09 General Requirements=20 The following information applies to all deliverables on this contract. De= liverables are subject to the FAA Contracting Officer's Technical Represent= ative's (COTR) approval. Drafts will be reviewed and returned within 15 da= ys after receipt. All products shall be delivered in hard copy form to the= address identified in 1.1.1, Identification and Address, and in electronic= form via the FAA e-mail system. The format for all submissions shall be i= n the MS Office or Adobe Acrobat format designated by the COTR. The contra= ctor shall submit monthly financial and status reports within 5 days of the= end of the month that detail the costs incurred and any problems that aris= e in execution of the contract. The monthly reports shall also contain a t= ravel section to identify the purpose of any trip, personnel encountered, a= nd pertinent information obtained from the visit. C.4=09Required Tasks and Deliverables The contractor shall furnish all the resources-facilities, supplies, person= nel, materials and services necessary to perform the duties defined below. Task One: Review the current models for the purpose of identifying strengt= hs and weaknesses. The contractor shall: Review the Air Carrier Operations System Models, Repair Station and Trainin= g Center Functional Models. Work with AAR-490 and Flight Standards personnel to understand the philosop= hy that underlies the need for the models and model development. =09Upon conclusion of the review, provide a written report that summarizes = the findings and identifies the strengths and weaknesses of each of the cur= rent models. Task Two: Review the literature to identify other methodologies that will = address the following concerns: Modeling Tool. A team of FAA and Industry personnel developed the aviation = system models using the Integrated Definition for Functional Modeling (IDEF= 0) methodology for the purpose of describing the functions within a specifi= c operation, i.e., air carriers, agricultural operations. These models con= tain much detail and at times, are difficult to read, but then, so are the = products of other modeling methodologies. Aviation safety inspectors will = now use the models that were originally developed for use by analysts, memb= ers of the research community, and industry. In addition, IDEF0 will also = be used to develop models of the various oversight processes. Thus there a= re several concerns: Is IDEF0 the best methodology to be used to model parts of the aviation sys= tem? IS IDEFO the best method to model the oversight system? Will the IDEF0 methodology be easily understood by various groups of users? In Task One, it is expected that the contractor will gain an understanding = of the purpose, uses, and users of the existing models in order to assess t= he currently used methodology, including BPWin (the software used to create= the models) and other potential methodologies. The contractor shall deliv= er a report assessing the current methodology and other proposed methodolog= ies, including their strengths and weaknesses, and recommend that either th= e FAA should continue using the current methodology or adopt a new one. In= either case, the contractor will be expected to justify their recommendati= ons. If the contractor believes the FAA should continue to use IDEF0, but b= elieve there are better ways to use the methodology/software, then the cont= ractor will address those recommendations in the report. If the contractor= recommends a new methodology, then he/she shall describe why it is a bette= r methodology over the current one and will also address the following: Provide an example of how one of the models will be presented using this ne= w methodology.=20 Describe an estimated level of effort to convert the existing models using = the new methodology. Knowledge Elicitation. Groups of FAA and Industry representatives periodica= lly attend meetings and use a technique called "brainstorming" to capture t= he inputs, outputs, controls, and mechanisms of the functions. This proces= s can result in model development taking several years to complete which is= neither effective nor efficient. Thus the question is what other knowled= ge elicitation methodologies could be used to capture knowledge to develop = the models, i.e. meet with smaller groups, use structured interviews, and s= o forth. The contractor shall address various knowledge elicitation method= ologies, their strengths and weaknesses, and recommend a methodology that t= he FAA could adopt for use in future model development. =20 Modeling Standards. While the software used to develop the model provides= some standardization, it does not prohibit team members from either provid= ing too detailed or too limiting definitions of functions, inputs, outputs,= controls, and mechanisms. Also, different groups of experts are used to d= evelop the models and each group may develop their own philosophy as to how= to develop the model, address issues uniquely associated with a model unde= r development, and so forth. The contractor shall provide recommendations = as to how standards may be developed and implemented to support consistent = model development. High Level Work Plan: =20 =C2=A7=09Hold kickoff meeting with FAA - Week 1=20 =C2=A7=09Deliver Interim Report Number One - Week 4 =C2=A7=09Deliver Interim Report Number Two - Week 8 =C2=A7=09Deliver draft report that will provide the results of both Tasks O= ne and Two - Week 12 =C2=A7=09Meet with AFS and AAR Personnel to present recommendations - Week = 14 =C2=A7=09Make changes to the report as requested by AAR-490 - Week 15 =C2=A7=09Complete and Deliver Final Report - Week 16 =20 Deliverables: =20 Interim Report #1 due at the end of week 4 Description of the progress made to date and early recommendations/observat= ions including a draft outline of the report Interim Report #2 due at the end of week 8 Description of the progress made to date and additional recommendations/obs= ervations including a draft revised outline of the report Draft Report due at the end of week 12 To include all recommendations/observations as obtained during the work of = the three tasks above including the outline of the paper and an executive s= ummary. Final Report Due at the end of week 16. To include all recommendations, either verbally or in writing, by FAA perso= nnel based on the draft report. C.5=09Personnel Requirements=20 Key Personnel shall include a Human Factors Engineer with the following min= imum qualifications: A doctoral degree or higher in human factors or psych= ology from an accredited college or university with at least 5 years experi= ence that demonstrates a professional knowledge of human factors principles= and at least 3 years experience working with the Flight Standards and Avi= ation Risk Analysis (RE&D) divisions. Individual must have knowledge of th= e FAA regulatory and organizational structures. Must have knowledge of the = Safety Performance Analysis System, inspector work processes and decision s= upport systems. This knowledge may be demonstrated by identifying products= delivered to the FAA. =20 C.6=09Government Furnished Information and Documentation Sources Upon contract award, the government will provide copies of all information = sources and documentation necessary for the contractor to perform the requi= red tasks. The information sources and documentation shall be identified w= ith the contractor upon award. C.7=09Travel=20 For purposes of estimating travel costs, it is anticipated that the followi= ng trips will be required: 2 trips to FAA Headquarters in Washington, DC; 2 trips to FSAIC offices in Dulles, Virginia; 3 trips to the FAA's William J. Hughes Technical Center located at the Atla= ntic City International Airport, Atlantic City, New Jersey. There may also be other meetings with AFS and industry representatives that= are necessary to perform the required tasks may be required. Actual trave= l shall be approved in advance by the COTR and all such approved travel wil= l be reimbursed in accordance with government travel regulations. C.8=09Release of Information All documents prepared by the Contractor shall be on the behalf of the FAA = and the Contractor may not independently publish or distribute any document= without prior written permission from the COTR. No documents, reports, in= formation, etc may be released to the public or provided to any party other= than the FAA and its contractors without written approval of the COTR.=20
- Web Link
-
FAA Contract Opportunities
(http://www.asu.faa.gov/faaco/index.htm)
- Record
- SN00372690-W 20030718/030716213401 (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 |