PRESOL | D | Aviation Data Management System - Package #1

FBO DAILY ISSUE OF MARCH 27, 2011 FBO #3410
SOLICITATION NOTICE

D -- Aviation Data Management System - Package #1

Notice Date: 3/25/2011
Notice Type: Combined Synopsis/Solicitation
NAICS: 541519 — Other Computer Related Services
Contracting Office: Department of Commerce, National Oceanic and Atmospheric Administration (NOAA), Eastern Region Acquisition Division-KC, 601 East 12th Street, Room 1756, Kansas City, Missouri, 64106, United States
ZIP Code: 64106
Solicitation Number: WC133M-11-RQ-0415
Archive Date: 4/26/2011
Point of Contact: Sharon Clisso, Phone: 816-426-7471
E-Mail Address: Sharon.Clisso@noaa.gov
(Sharon.Clisso@noaa.gov)
Small Business Set-Aside: Total Small Business
Description: Past Performance Questionnaire Client Authorization Letter AOC Training List Definition for ELOG Database Diagram for ELOG Database 091007 Sample Flight Schedule Report Sample Daily Flight Log This is a combined synopsis/solicitation for commercial items prepared and processed in accordance with the Federal Acquisition Regulations (FAR) Part 12.6 as supplemented with additional information included in this notice. This is a solicitation from the U. S. Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), Eastern Acquisition Division - Kansas City Office. The requirement is for the development of, web-based access to, and training for an aviation data management system for the NOAA Aircraft Operations Center (AOC) at MacDill AFB, Tampa FL. This notice constitutes the only Request for Quote (RFQ). Written quotes are being requested. A hardcopy written RFQ will not be issued. Any questions pertaining to this solicitation must be submitted via email to the Contract Specialist, Sharon Clisso, at email address Sharon.Clisso@noaa.gov. Questions must be received by 10:00 AM CDT on March 30, 2011. NOAA will answer questions, which may affect quotes, in an amendment to the RFQ. NOAA will not reference the source of the questions. Questions received after 10:00 AM CDT on March 30, 2011, will not be considered. A quote shall comply in all material respects with this RFQ and will represent the quoter's acceptance of all the terms and conditions of the request. The quoter shall provide a narrative response for each factor and sub-factor of the evaluation factors. The quotation page limitation is 20 pages. A page is defined as one side of a sheet, 8 1/2" x 11", with at least one inch margins on all sides, using not smaller than 12 point type. Line spacing or the amount of vertical space between lines of text shall not be less than single line (Microsoft Word's default line spacing). The quote may contain text, charts, and graphs as long as it remains within the 20 page limitation. Pages submitted in excess of the limitation specified will not be evaluated by the Government. For example, if the pricing information is on page 21 of the quote, the quote will be considered nonresponsive and will be rejected. DOC, Eastern Acquisition Division - Kansas City Office requires that all contractors doing business with this office be registered with the Central Contractor Registry (CCR). No award can be made to a company not registered in CCR. For additional information and to register in CCR please access the following web site: http://www.ccr.gov. In order to register, all offerors must have a Dun & Bradstreet Number. A Dun & Bradstreet number may be acquired free of charge by contacting Dun & Bradstreet on-line at http://www.dnb.com/eupdate or by phone at (800) 333-0505. All contractors are also required to complete Online Representations and Certifications Applications (ORCA) at http://ORCA.BPN.GOV. This notice is hereby issued as RFQ WC133M-11-RQ-0415. This RFQ and the following incorporated provisions and clauses are those in effect through Federal Acquisition Circular (FAC) 2005-49. CLAUSES AND PROVISIONS The FAR and CAR clauses incorporated into this acquisition are: 52.212-1 Instructions to Offerors - Commercial Items (JUN 2008) [Paragraph (c) is amended from 30 days to 60 days] 52.212-2 Evaluation-Commercial Items (JAN 1999) (Evaluation Criteria: Technical, Delivery Schedule, Key Personnel and Past Performance) 52.212-3 Offeror Representations and Certifications Commercial Items (JAN 2011) 52.212-4 Contract Terms and Conditions (JUN 2010) 52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders-Commercial Items (JAN 2011), Section (b) (1), (10), (12), (14), (20), (21), (22), (23), (24), (25), (26), (27), (33), (37), (42) 52.217-5 Evaluation of Options (JUL 1990) 52.217-8 Option to Extend Services (NOV 1999) within 60 days before the contract will expire 52.217-9 Option to Extend the Term of the Contract (MAR 2000) (a) within 60 days before the contract is set to expire, 60 days; (c) shall not exceed 5 years 52.232-18 Availability of Funds (APR 1984) 52.245-1 Government Property (AUG 2010) applicable if solution is to use OMAO IT system 52.247-34 F.O.B Destination (NOV 1991) 1352.201-70 Contracting Officer's Authority (APR 2010) 1352.201-72 Contracting Officer's Representative (COR) (APR 2010) (Will be designated at time of award) 1352.209-72 Restrictions Against Disclosure (APR 2010) 1352.209-73 Compliance with the Laws (APR 2010) 1352.209-74 Organizational Conflict of Interest (APR 2010) 1352.233-70 Agency Level Protest (APR 2010) (Donita McCullough, DOC/NOAA, Eastern Acquisition Division-KC Office, 601 E. 12th St., Room 1756, Kansas City, MO 64106 1352.237-71 Security Processing Requirements - Low Risk Contracts (APR 2010) 1352.237-54 Progress Reports (APR 2010) 1352.237-75 Key Personnel (APR 2010) (Project Manager) 1352.239-72 Security Requirements for Information Technology Resources (APR 2010) 1352.246-70 Place of Acceptance (APR 2010) (DOC/NOAA/AOC/MacDill AFB, FL) FAR clauses and provisions are available on the internet website: http://www.acquisition.gov/far. CAR clauses and provisions are available on the internet website: http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=3fb01eeae7b9c808d918ae0d557a63df&rgn=div5&view=text&node=48:5.0.6.47.44&idno=48 PRICE/QUOTE: This is an order for commercial supplies and services (web-based access aviation data management system). The line items will be quoted and completed in accordance with the terms and conditions and statement of work specified herein. Prices quoted for the contract line items shall be firm-fixed price inclusive of all costs (FOB Destination at AOC, MacDill AFB, FL). The offer must include pricing for Line Items 0001 - 0008. If the offer does not contain pricing for all line items, the quote will be considered non-responsive and will be rejected. LINE ITEM 0001: PROVIDE INITIAL OPERATING CAPABILITY: Provide the web-based access for a commercial off-the-shelf aviation data management system which addresses 1) flight management; 2) maintenance; 3) inventory; and accounting, assuming at least 20 concurrent users and 10 operational aircraft; complete a preliminary design review of the production aviation data management system per the Statement of Work by 5/27/2011. Quantity: 1 Unit: EA Unit Price: $_______ Amount: $_______ LINE ITEM 0002: PROVIDE AVIATION DATA MANAGEMENT SYSTEM DESIGN SERVICES: Provide customized forms and reports within the aviation data management system per Statement of Work; complete a critical design review of the aviation data management system per the Statement of Work by 8/26/2011. Quantity: 1 Unit: EA Unit Price: $_______ Amount: $_______ LINE ITEM 0003: PROVIDE FINAL OPERATING CAPABILITY: Provide the web-based access, and user training for a fully functional, production aviation data management system for 43 AOC users per Statement of Work; assume at least 95 standard user accounts and 3 advanced user accounts per Statement of Work; assume at least 20 concurrent users and 10 operational aircraft; complete the migration of AOC data into the aviation data management system by 9/30/2011. Quantity: 1 Unit: EA Unit Price: $_______ Amount: $_______ LINE ITEM 0004: PROVIDE SUPPORT SERVICES FOR BASE YEAR: Provide user web-based access and support services for the aviation data management system for the base year per the Statement of Work, 10/1/11-9/30/12. Quantity: 12 Unit: MO Unit Price: $_______ Amount: $_______ LINE ITEM 0005: PROVIDE SUPPORT SERVICES FOR OPTION YEAR I: Provide user web-based access and support services for the aviation data management system for option year one per the Statement of Work, 10/1/12-9/30/13. Quantity: 12 Unit: MO Unit Price: $_______ Amount: $_______ LINE ITEM 0006: PROVIDE SUPPORT SERVICES FOR OPTION YEAR II: Provide user web-based access and support services for the aviation data management system for option year two per the Statement of Work, 10/1/13-9/30/14. Quantity: 12 Unit: MO Unit Price: $_______ Amount: $_______ LINE ITEM 0007: PROVIDE SUPPORT SERVICES FOR OPTION YEAR III: Provide user web-based access and support services for the aviation data management system for option year three per the Statement of Work, 10/1/14-9/30/15. Quantity: 12 Unit: MO Unit Price: $_______ Amount: $_______ LINE ITEM 0008: PROVIDE SUPPORT SERVICES FOR OPTION YEAR IV: Provide user web-based access and support services for the aviation data management system for option year four per the Statement of Work, 10/1/15-9/30/16. Quantity: 12 Unit: MO Unit Price: $_______ Amount: $_______ STATEMENT OF WORK BACKGROUND: The Aircraft Operations Center (AOC) is a Center of the NOAA Office of Marine and Aviation Operations (OMAO). The AOC fleet of 12 aircraft (of which 10 are operational and are applicable to this RFQ) is flown in support of NOAA's mission to promote global environmental assessment, prediction, and stewardship of the earth's environment. A support staff at AOC of approximately 95 employees operates these aircraft throughout the United States and around the world. Eight aircraft are headquartered at MacDill Air Force Base, Tampa, FL, and are, for the most part, maintained in Tampa, FL at an AOC owned-and-operated maintenance facility. The remaining four aircraft are based at various locations throughout the country and are maintained by AOC through contractual arrangements with a multiplicity of commercial aircraft maintenance facilities. Currently, most activities related to aircraft operational management including maintenance, parts inventory, and accounting are managed using a local Oracle v9.2i database and a contracted, proprietary software system. The current volume of data in this database is equivalent to a text export of 15 Megabytes. Flight management data including pilot and flight records are currently stored locally in a Microsoft Access database. Other accounting, training, document control, and operational data are stored in various small spreadsheets or data tables. More detailed information on NOAA's AOC can be found at www.aoc.noaa.gov. SCOPE: AOC has identified the need for an integrated database system capable of managing information critical to the function of its aviation program. For the purposes of this document, these functions are categorized broadly as 1) flight management; 2) maintenance; 3) inventory; and, 4) accounting. Information currently stored in AOC databases and spreadsheets must be integrated to form a new centralized data clearinghouse for aircraft management data. An integrated architecture will allow for more efficient data storage and recovery, provide greater access to operationally critical information, and offer more effective management tools. To realize these benefits, AOC is requesting quotes from vendors that will satisfy the following requirements. Personnel must be able to interact with the aviation data management system quickly, easily, and securely. A web-based front end client shall provide access to the data system and utilize Secure Socket Layer (SSL) or comparable security technology. The proposed data system solution may be hosted on the OMAO IT system or located offsite and provided by the contractor. A tiered (web and data) server architecture is preferred, with security features such as redundant but distant servers, frequent data backups, and uninterruptable power. These features are available on the OMAO network and may be utilized by the offeror as Government Furnished Equipment. Microsoft software including Windows Server and SQL Server 2008 is also available on OMAO equipment; however, the Oracle database software in use at AOC is not available for the proposed data system. If the offeror is capable of providing a solution for both the contractor-owned and OMAO-owned IT systems, two separate proposals must be submitted. The solution must be in compliance with CAR 1352.239-72 Security Requirements for Information Technology Resources (APR 2010). In accordance with the Federal Information Processing Standard 199 "Standards for Security Categorization of Federal Information and Information Systems" (FIPS199) and NIST Special Publication 60 "Guide for Mapping Types of Information and Information Systems to Security Categories:" (SP800-60), NOAA's Information Technology System NOAA2010 "OMAO Land Based Support System" (LBSS) Risk Categorization has been identified as Moderate Confidentiality, Moderate Integrity, and Moderate Availability, for an overall rating Categorization of Moderate Impact. If the proposed solution is based on using the OMAO owned IT system, the Certification and Accreditation (C&A) requirements of Clause 1352.239-72 do not apply, and a Security Accreditation Package is not required. To be used effectively as a management tool, the aviation data management system must offer extendable data entry and reporting capabilities that allow custom forms and reports to be generated in-house. AOC personnel must be able to build customized data reports in a reasonably short period of time with minimal effort. The aviation data management system shall provide the means to query the stored data and generate reports from the queries. The queries shall allow searches on any one substantive record attribute or combination of attributes, and allow the use of wildcard characters. The reports shall present query results using text and/or optional bar graphs, line graphs, and pie charts. To ensure that AOC functional and schedule requirements are met, design reviews shall be conducted biweekly (at a minimum) between the contractor and the AOC project manager. A preliminary design review shall occur before completion of Line Item 0001 and serve to communicate AOC design requirements and the vendor's data migration and system design strategy. A critical design review shall occur before the final operating capability is achieved to ensure that AOC design requirements will be met. The preliminary and critical design reviews shall include AOC representatives knowledgeable in each functional category (flight management, maintenance, inventory, and accounting) and take place at AOC. Technical support shall be offered by the contractor to address problems with or modifications to the aviation data management system, and be included for equipment and software furnished by the contractor. Technical support requests from AOC shall be addressed within 24 hours. Access to the system shall be controlled through an administrative role that may be performed by select individuals at AOC. Privileges to perform administrative, read and write functions shall be controlled independently through the administrative role. The contractor must supply complete documentation of data system user functions by the final operating capability of the aviation data management system. The capability to download a copy of the raw aviation data must also be provided by final operating capability. Account access shall be granted to 95 AOC users and initial end-user training provided to 40 AOC users at the MacDill AFB location. If appropriate to the system, module-specific training shall be provided. The proposal shall also include a "train the trainer" style program for 3 additional AOC personnel at the MacDill AFB location. I. Flight Management: Flight and flight crew records shall be accessible from outside AOC, allowing remote data entry and reporting with controlled access. Data currently entered in the daily flight log (see attached sample), with the following changes, shall be recorded on an electronic form and submitted to the database. The flight log changes include: 1) remove the "Blue" category from Section 5, 2) allow the entry of a complete fuel expense record (see Accounting section below) to replace the fuel service block (Section 6), 3) allow miscellaneous expenses to be logged (see Accounting section below), 4) allow aircraft location, location address, location phone number, pilot location, location address, and pilot phone number to be entered, 5) increase the size of the remarks block (Section 9) to allow for at least 2000 characters of text, 6) add a new block that allows for annotation of the utilization code of the flight (i.e. O, U, M, L, or C,) and 7) Account for dropsonde performance in Section 10 (e.g. good, no data, free-fall, etc.). The flight log form shall allow one or more funding codes to be entered for the flight, selectable from a list of applicable codes. The form shall have an option to copy data from the previous flight for a particular aircraft, so that a minimal amount of new flight data is required to fill the form and data entry errors are reduced. The form shall quality check the entered flight time aviation data between block, flight, project, personnel, aircraft, and training times to identify any potential entry or calculation errors before the log is submitted. The user shall be notified with a warning that a discrepancy has been found and asked if the change should be made by the system. The aviation data management system shall allow the submission of flight information directly to the database through a local or remote connection, and then automatically send an email including the filled flight log to a customizable distribution list. A mission situation report shall also be generated from submitted flight, mission, and location information, and be sent by email to a distribution list. The distribution list will be provided to the contractor on request following the contract award. The situation report is a daily report on aircraft activity that contains the aircraft and crew location and contact information, utilization code, flight number, flight time, and remarks. A flight schedule shall be maintained and reported daily in the following form. The flight schedule daily report shall include the following statistical data for the current month and fiscal year: total number of flights, total flight hours, total hours flown for Aircraft Services, total hours flown for Programs, and total hours flown for Reimbursable Projects. The body of the report shall contain the following information: current calendar day and next calendar day itineraries for all aircraft assigned to AOC, location of each aircraft, phone number of aircraft location, crew location, task code and project name for aircraft mission if assigned to a project, a color coded aircraft status (green for up and red for down), notes concerning the aircraft status, crewmember positions, and assigned personnel. Additionally, the flight schedule daily report shall include remarks entered at the time of the generation of the report. The ability to print the flight schedule daily report in a legible font on no more than two 8.5x11 pages, shall be provided ( an example of a flight schedule report is attached). If a crewmember qualification is expired and the crewmember has been assigned to a flight, a warning shall be issued at the time of the generation of the report. The aviation data management system shall allow the entry of the flight schedule and generation of the report directly through a local or remote connection, and then automatically send an email including the flight schedule daily report to a customizable distribution list. The aviation data management system shall be able to accommodate the data currently stored in ELOG (the flight management Microsoft Access database) and use it effectively in the forms and reports described herein. The structure of the ELOG database is provided in the following documents which are separate attachments: Diagram for Electronic LOG (ELOG) Database 091007.pdf Definition for Electronic LOG (ELOG) Database 091007.pdf The aviation data management system shall be able to track medical, flight, and ground training qualifications of AOC employees and aircrew, and provide automated email warnings of approaching and passed expiration dates for training qualifications. AOC shall be able to customize the mailing list for the email warnings. A list of training qualifications is provided in the attached diagram for the ELOG database (in the RECORDS table) and in the following document which is a separate attachment: AOC Training List 10 Feb 2011. II. Maintenance: The aviation data management system shall provide a single point of entry for maintenance discrepancies in addition to flight data. Remote data entry shall be enabled for the flight information and maintenance work orders. The aviation data management system shall track aircraft engine, propeller, and applicable subcomponent maintenance records and manage multiple, user-definable aircraft configurations. The system must be able to track compliance events and display status, intervals, applicability for inspections, (Service Bulletins/Airworthiness Directives (SB/AD), P-3 Airframe Bulletins, P-3 Airframe Changes, and component tracking. The system shall allow user-definable windows to display irregular frequency/intervals for compliance. The aviation data management system shall update all aircraft records appropriately with each change in a master event and generate reports regarding fleet status and compliance. The system shall display forecasted due compliance events based on projected aircraft utilization, current real-time fleet status on single screen and color-coded events based on user-definable parameters (e.g. number of days from event), and discrepancy history. Logbook entries and documentation requirements shall be flagged and man-hours tracked for maintenance tasks. The aviation data management system shall provide a means to manage scanned aircraft and aircraft systems documents (e.g. drawings, 337s, 8110-3ss, correspondence) and aircraft weight/balance data; however, the archival ‘digitizing' of hard copy data is not requested as part of this statement of work. At all data recording points, the aviation data management system shall minimize typing and writing by data entry personnel. Electronic signatures acceptable to the FAA shall be utilized for maintenance documentation. Standard reports, such as maintenance due items, maintenance cards, and flight-hour per man-hour, shall be provided. The aviation data management system must also allow for the generation of user-definable reports. III. Inventory: The aviation data management system shall store inventory and order information, including the attributes listed below. The primary use of inventory records is for the organization, accounting, and tracking of aircraft-related parts. At a minimum, inventory records shall include stock number, part number, alternate part numbers, quantity, minimum quantity, maximum quantity, order point, Air Transport Association (ATA) tracking code, unit of issue, shelf life status, shelf life expiration date, repairable status, depot level repairable status, overhaul serial number, kit association, rotatable status, serialized status, location, quantity, price, and accounting data. The management of parts orders is also required. These records allow for the planning, accounting, and tracking of inventory item acquisitions. Parts order records shall include the order number, order date, back order date if applicable, date received, date issued, tail number of applicable aircraft, date of transaction, unit cost, quantity ordered, quantity received, total cost, item description, supply source, and accounting data. An alert system shall be implemented to warn of low inventory levels and an anticipated need for inventory orders. Various reports shall be provided for displaying information based on the underlying database. Reports include, but are not limited to, a history of issues by aircraft or part number for trend analysis and a history of receipts by aircraft or part number. IV. Accounting: The aviation data management system shall store accounting information, including the items listed below, and generate reports from the data. AOC must be provided with the ability to customize new data entry forms and reports from the underlying database. The entry of accounting data in the database must include, but not be limited to the following: 1) aircraft fuel expenses; 2) vehicle fuel expenses; 3) aircraft miscellaneous expenses; 4) invoice records; and, 5) funding codes. Aircraft fuel expenses shall include the aircraft tail number, date of fuel transaction, flight log number, type of fuel, quantity, cost per unit, total cost (internal calculation), credit card used, sale location and accounting data. Vehicle fuel expenses shall include the vehicle registration number, date of fuel transaction, type of fuel, quantity, cost per unit, total cost (internal calculation), credit card used, sale location, and accounting data. Miscellaneous expenses other than fuel shall include the aircraft tail number, date of transaction, flight log number, description of transaction (e.g. maintenance, ground handling, oxygen service, hangar rental, etc.), cost per unit, total cost (internal calculation), credit card used, sale location, and accounting data. Invoice records shall include the type of invoice or description, vendor, invoice number, original invoice date, AOC process date (auto fill), and accounting data. Accounting data for these records shall include the funding code and object class. There shall be a means for assigning multiple accounting codes to an item, order, or invoice, and assigning a portion of the cost to each accounting code. A master list of funding codes shall be stored with the associated fiscal year, organization code, project code, task code, project type (i.e. Program, Services, or Reimbursable), supported NOAA mission goal by percentage, supported primary and secondary budget programs, and description. The opportunity to update this list shall be made available to AOC. Object class codes shall also be maintained in an editable record for use when assigning the codes to a charged item. Various reports shall be provided for examining the accounting data, and an option shall be available to export the reports into spreadsheet form. Reports shall include, but not be limited to, the following output: 1) the issue of parts for specific periods; 2) parts received but unbilled for specific periods; 3) paid invoices for specific periods; 4) unpaid invoices and invoice dates for specific periods; 5) backorders and backorder dates for specific periods; 6) expenses for specific projects in a specific period; 7) expenses for a specific task in a specific period; 8) expenses by aircraft; 9) parts ordered but not received for a specific period; and, 10) aircraft expense report by date and accounting information. Alerts produced by the aviation data management system shall include the detection of a discrepancy in price or quantity of parts orders and invoices. TIME OF DELIVERY SCHEDULE The Government requires delivery to be made according to the following schedule which is based on anticipated award date of April 29, 2011: Required Delivery Schedule: CLIN 0001: Initial Operating Capability: May 27, 2011 CLIN 0002: Aviation Data Management System Design Services: August 26, 2011 CLIN 0003: Final Operating Capability: September 30, 2011 CLIN 0004: Provide Support Services for Base Year: October 1, 2011-September 30, 2012 CLIN 0005: Provide Support Services for Option Year I: October 1, 2012-September 30, 2013 CLIN 0006: Provide Support Services for Option Year II: October 1, 2013-September 30, 2014 CLIN 0007: Provide Support Services for Option Year III: October 1, 2014-September 30, 2015 CLIN 0008: Provide Support Services for Option Year IV: October 1, 2015-September 30, 2016 MONTHLY TECHNICAL REPORT The contractor shall furnish one (1) copy of a technical progress report each month. The report is due by the 10th day of each month following the first complete month of the contract. The technical progress report shall include a summary of the effort performed and/or completed during the reporting period. Specific discussions shall include any difficulties encountered and the corrective action taken during the reporting period. It shall include an outline of anticipated activity and an estimate of progress to be made during the subsequent reporting period. Any anticipated changes in personnel shall also be included. See the Statement of Work for further specifics. The monthly technical progress report is the basis for partial payment requests for CLIN 0002. SUBMITTAL OF INVOICES (EAD-KC Office Addendum to FAR 52.212-4(g) The contractor shall prepare and submit an invoice which will serve as the request for payment. All requests for payment shall be based on work completed as of the end of the most recent billing period and shall be submitted by the 10th day of the subsequent month to the Contracting Officer's Technical Representative (COTR) at the Aircraft Operations Center (AOC) using the address shown in Block 15 of the award document, Solicitation/Contract/Order for Commercial Items-Standard Form 1449. The invoice shall indicate the line item and timeframe covered by the invoice (example: 11/16/03 - 12/15/03). To constitute a proper invoice, the contractor's invoice shall be prepared in accordance with and contain all elements specified in paragraph (g) of FAR 52.212-4 entitled "Invoices". If the invoice does not comply with the applicable prompt payment provision of the contract, it will be returned to the contractor within seven (7) days after the date the designated office received the invoice, with a statement as to the reasons why it is not a proper invoice. SCHEDULE OF DELIVERABLES The following is a schedule of all deliverables, including administrative deliverables, required during the period of performance for this procurement. DELIVERABLE DELIVERY DATE DELIVER TO Line Item 0001 5/27/2011 AOC ProjectManager Line Item 0002 8/26/2011 AOC Project Manager Line Item 0003 9/30/2011 AOC Project Manager Design review meetings Bi-Weekly before final AOC Project Manager operating capability is achieved Critical design review Before final operating AOC Project Manager capability is achieved Technical Report Monthly Due the 10th AOC Project Manager day of each month Technical Support Processed within 24 hours AOC Project Manager after AOC request IT Security Orientation 5 days after award AOC Project Manager Training (per Clause 1352.239-72) EVALUATION--COMMERCIAL ITEMS The Government will issue an order resulting from this RFQ to the responsible quoter whose quote, conforming to the solicitation for an aviation data management system including flight management, maintenance, inventory, and accounting functions, provides the best value to the government. The best value will be determined as a tradeoff between price/cost, technical merit, delivery schedule, key personnel and past performance. The following factors shall be used to evaluate quotes and are listed in descending order of importance: FACTOR 1 - TECHNICAL: Sub factors a), b), c), and d) will be evaluated by the variable decisional rule. In the trade-off process, this rule uses distinctions based on merit. The sub factors a), b), c), and d), are listed in descending order of importance. a) Experience: The offeror shall provide evidence of having developed an aviation data management system for aircraft operations similar to the scope of the solicitation. b) Approach: The quoter shall provide a detailed description of how they plan to achieve the web-based access solution per the Statement of Work. c) Approach: The quoter shall provide evidence of ability to migrate existing AOC data into the proposed web-based aviation data management system and generate the required reports and queries. d) Approach: The quoter shall provide evidence of ability to provide accessible, responsive technical support for the aviation data system, maintenance, and access procedures. FACTOR 2 - DELIVERY SCHEDULE: This factor will be evaluated by the go/no-go decisional rule. A quoter who does not meet the requirements of this factor will be eliminated from further consideration. A quoter who meets the requirement of this factor will receive further consideration. The quoter must provide a timeline for completing CLINs 0001, 0002, and 0003. The Government requires delivery to be made according to the following schedule which is based on the anticipated award date of April 29, 2011. Required Delivery Schedule: CLIN 0001: Initial Operating Capability: May 27, 2011 CLIN 0002: Data Management System Design Services: August 26, 2011 CLIN 0003: Final Operating Capability: September 30, 2011 FACTOR 3 - KEY PERSONNEL: This factor will be evaluated by the variable decisional rule. In the trade-off process, this rule uses distinctions based on merit. NOAA will evaluate the experience of the proposed key personnel (Project Manager) to determine the extent to which his or her background, education, work experience, and accomplishments demonstrate his or her ability to effectively perform the role for which he or she is proposed. The quoter shall provide evidence that the proposed key personnel (Project Manager) to be assigned to this project has knowledge and experience of an aviation data management system. FACTOR 4 - PAST PERFORMANCE: The past performance information will be evaluated on quality of product or service, cost control, timeliness of performance and business relations, to determine its relevance to the current requirements and to the extent to which it demonstrates that the quoter has successfully completed contracts which are of similar scope, magnitude, relevance, and complexity to the aviation data management system requirements. If a quoter has no relevant past performance history, a quoter must affirmatively state that it possesses no relevant past performance history. The Government will assign a neutral rating to quotes with no relevant past performance. Quoters shall provide past performance information regarding contracts which are similar in nature to this aviation data management system requirement and which it has performed in the last three (3) years. The contracts may include those entered into with Federal, State and local governments, and commercial businesses, which are of similar scope, magnitude, relevance, and complexity to the aviation data management system requirements which is described in the RFQ. Quoters shall submit at least three (3) past performance references. Include the following information for each reference: (a)Name of contracting activity (b)Contract number (c)Contract title (d)Contract type (e)Contracting Officer, telephone number, and email address (f)Program Manager/Project Officer, telephone number, and email address Quoters must send Client Authorization Letters (see attached) to each reference listed in their quote to assist in the timely processing of the past performance evaluation. Quoters should send the Client Authorization letters electronically to their references with copies to the Contract Specialist on or before the due date for submission of quotes. A Past Performance Questionnaire (see attached) will be used to collect information on a quoter's performance. The Contract Specialist will send the Past Performance Questionnaire to each reference listed in the quote. Technical, delivery schedule, key personnel and past performance, when combined, are significantly more important than price. As the technical ratings become more equal, price becomes more important. Conversely, as price proposals become more equal to one another, technical proposals will become a more important determining factor. NOAA will evaluate the quoter's proposed prices for fairness and reasonableness in relation to the RFQ's requirements. PLACE OF PERFORMANCE: U.S. Department of Commerce NOAA/Aircraft Operations Center 7919 Hangar Loop Drive, Hangar 5 MacDill AFB, FL 33621-5401 Attachments: Sample Daily Flight Log Sample Flight Schedule Report Diagram for ELOG Database 091007 Definition for ELOG Data base 091007 AOC Training List Client Authorization Letter Past Performance Questionnaire
Web Link: FBO.gov Permalink
(https://www.fbo.gov/spg/DOC/NOAA/CASC/WC133M-11-RQ-0415/listing.html)
Record: SN02409805-W 20110327/110325234811-13d0e7aa273fa96c4d5dbc1179e8b43a (fbodaily.com)
Source: FedBizOpps Link to This Notice
(may not be valid after Archive Date)

| FSG Index | This Issue's Index | Today's FBO Daily Index Page |

Loren Data's SAM Daily™

D -- Aviation Data Management System - Package #1