Inactive

***DRAFT*** SCOPE OF WORK 3. SUPPLIES AND SERVICES All work under this Contract must be assigned, controlled, managed, and accounted for by Government-issued delivery/task orders. The Contracting Offi... ***DRAFT*** SCOPE OF WORK 3. SUPPLIES AND SERVICES All work under this Contract must be assigned, controlled, managed, and accounted for by Government-issued delivery/task orders. The Contracting Officer must issue all delivery/task orders. The Contractor must provide sufficient personnel, both in number and qualifications, to perform work described herein and specified in the delivery/task orders. The Contractor must provide sufficient oversight of the Contract in order to ensure that: • All personnel are functioning within their designated labor categories and at acceptable levels of performance; • All activities performed are covered by applicable task orders and are related to the scope of this Contract; • Staff positions are filled promptly and kept filled with qualified, competent personnel; and • All Contractor personnel are performing their designated assignments in a timely manner, and all reporting requirements are met. Delivery/task orders will be of variable scope and duration and may require concurrent efforts. To accomplish the overall objectives of this SOW, specific delivery/task orders may be issued in the following areas: 3.1 PDARS OPERATION, MAINTENANCE, EXPANSION, AND SUPPORT The Contractor must work in this area must include the continuation of PDARS operation, maintenance, expansion, and support efforts. In addition, work efforts must include the design and development of customized computer hardware/software/data system solutions which complement or enhance the current PDARS capabilities, and procurement, installation, and operation of commercial software/hardware solutions that together provide operations monitoring, performance measurement, and reporting, operations planning, decision support, special studies/analyses/evaluations, and other uses as required per FAA direction. Examples of specific work efforts in these areas may include the following: 3.1.1 Provide software for use within the PDARS system to perform the radar data extraction/processing function and the aviation data visualization and analysis function matching or exceeding the current capabilities of the PDARS system. The PDARS system must provide the capability to extract and process data from the FAA Air Route Traffic Control Centers (ARTCC) Host, Common Automated Radar Terminal System (ARTS), Automated Radar Terminal System Internet Information Infrastructure Architecture (ARTS IIIA), Standard Terminal Automation Replacement System (STARS), En Route Automation Modernization (ERAM) and Airport Surface Detection Equipment (ASDE-X) computer systems in real time and/or batch processing mode for seamless inclusion into other PDARS processing modules and reports. The data visualization tool SKYVIEWER and analysis software must be capable of displaying and analyzing aviation-related data (including airports, airspace structures, aircraft tracks, routes, geographic data, weather, etc.) as well as animate traffic, sector airspace, and weather movements. To ensure the accuracy and currency of PDARS data, the Contractor must update the PDARS system and related software to accommodate changes in the NAS or FAA data delivery. 3.1.2 Provide continuous/uninterrupted operations, maintenance, and support to the PDARS systems installed in FAA Air Traffic Control (ATC) facilities and other facilities, including responsibilities for remote monitoring and failure recovery for all hardware/software components, network monitoring and failure recovery, data quality assurance, software, and hardware maintenance, application assistance, training, documentation updates, and user information exchange activities with no interruption in the operation of the system. 3.1.3 Provide, operate, maintain, and support a PDARS central hub site including responsibilities for system monitoring and failure recovery, software and hardware maintenance, application assistance, documentation updates, data sharing, data archiving, and data back-up on a continuous basis beginning on the date of Contract award and continuing for the entire Contract period of performance. 3.1.4 As tasked, expand the PDARS network to additional ATC facilities, including responsibilities for coordinating the installation of communication lines, assisting in user needs assessments, computer system integration and customization, the procurement and installation of equipment, testing, and transition. 3.1.5 Produce uninterrupted daily, weekly, monthly, and other PDARS reports in support of FAA operational facilities, FAA service area offices, and FAA headquarters, including the continued generation of the over 900 standard daily reports and special reports, which contain system performance information that supports the Federal Aviation Administration Operations Network (FAA OPSNET) delay reporting system, and other reporting systems as directed by the FAA. These reports contain custom algorithms that encompass NAS data elements to determine system performance and are automatically generated on a daily, weekly, or monthly basis. 3.1.6 Design, develop, and deliver special request reports of new and archived PDARS data to support FAA NAS initiatives as directed by the FAA. 3.1.7 Modify, refine, and update existing computer methodologies, models, and simulations to provide enhanced capabilities required for PDARS. 3.1.8 Design, develop, and implement computer tools for collecting and analyzing data for monitoring, testing, and evaluating existing or advanced NAS operations, components, and air traffic control/management tools. 3.1.9 Develop the capability to use the existing PROC machine to process data as the source for the SKYVIEWER virtualized application as well as use a centralized warehouse within the NAS Data Warehouse known as WILBUR. 3.2 PROGRAM SUPPORT, STUDIES, ANALYSES, AND EVALUATIONS The Contractor must provide support to programs or projects that require PDARS data or PDARS system analytical use to conduct studies, analyses, and evaluations of existing or potential NAS operations. This support must also involve measurement, analysis, reporting, and simulation of FAA operations, planning, or modernization efforts. Examples of support in the application of these tools in these areas may include the following: 3.2.1 Design, evaluate, and/or analyze air traffic system alternatives, which may involve technological, operational, procedural, and facility aspects of the air traffic system, including system users, providers, and consumers of air traffic services. 3.2.2 Conduct evaluations of the performance of air traffic systems, including existing baseline operations and tests of advanced systems, concepts, procedures, and technologies. 3.2.3 Perform operational, technical, and feasibility assessments of air traffic system alternatives including capacity, delay, operating cost, traffic loading, environmental, and economic factors. 3.2.4 Conduct aviation-related studies that may be generic in nature, site-specific multi-modal, or innovative in concept to establish feasibility, viability, marketability, or benefit-cost effectiveness. 3.2.5 Perform evaluations, assessments, and benefit-cost trade-off analyses of ongoing or proposed programs and projects. 3.2.6 Provide technical assistance, including development and implementation of operational concepts, formulation of schedules, resource requirements, systems engineering studies, plan preparations, and general analytical and technical support. 3.2.7 Provide engineering assistance, including development and implementation of system architecture documents, requirements documents to include Interface Requirements Documents (IRDs), Interface Control Documents (ICDs), and National Change Proposals (NCPs), and the use of FAA configuration management systems to obtain appropriate approvals. 3.2.8 Provide assistance to the FAA in performing its responsibilities for planning, definition, oversight, and policy formulation, including computer tool capabilities to meet requirements for demonstrations, analyses, and evaluations. 3.3 TRAINING The Contractor must manage and execute the PDARS training program for FAA Air Traffic Services personnel, managers, and analysts in each FAA facility supported by PDARS, at FAA Headquarters in Washington D.C., and the various Service Area offices supported by PDARS. Training may also be provided at the Contractor facility. The Contractor must perform each delivery/task order using a mix of personnel appropriate for accomplishing the work requirements. Such personnel mix must be identified in each delivery/task order. 3.4 TRANSFER PLAN The Contractor must prepare and submit a Transfer Plan for transferring the PDARS system to the FAA. The Transfer Plan must address the transfer of all hardware, software, processes, tools, and documentation, owned by the FAA. The Transfer Plan must describe the approach to transfer the PDARS equipment and data owned by the FAA from the Contractor to the FAA. The Contractor’s transfer planning must begin at Government direction. The FAA will determine when the transfer process is to be completed and will provide formal acceptance indicating such. 3.4.1 The Transfer Plan must describe the sequence of activities from the beginning to the end of the system transfer. The Contractor must specify the actions they expect from the Government during the transfer process. 3.4.2 The Transfer Plan must address the transfer of any and all Government Furnished Equipment (GFE) and any and all Government Furnished Information (GFI). The Transfer Plan must address the dispensation of any Contractor-owned property. 3.4.3 The Plan must describe the retention of the required number of fully qualified Contractor personnel to the Contract during the transfer period. 3.4.4 The Transfer Plan must describe the Contractor’s approach to knowledge transfer and accessibility to program information. Knowledge transfer must include documentation/instruction manuals, including as-built documents, training, configuration management documentation, and one-on-one training/knowledge transfer. 3.4.5 The Transfer Plan must include a schedule denoting all major transition activities and milestones. The schedule must reflect the proposed handover approach and address all major Contractor and Government activities required for the transfer of the system. The Transfer Plan must include all activities necessary to retire the PDARS system and transfer data, information, and infrastructure to the government and/or the government’s designated representative, as necessary. The Transfer Plan must include, with the schedule, an assessment of schedule risks and mitigation activities and tasks. A Transfer Schedule is required for Government approval. The Transfer Schedule must indicate completion of all transfer activities within 12 months of initiation. 3.5 WILBUR TRANSFER PLAN IMPLEMENTATION The Contractor must perform the activities in the Subsection 3.4, Transfer Plan, that are required to facilitate the FAA’s ability to assume full responsibility for the acceptance of Government-owned PDARS hardware, software, processes, tools, and documentation. The FAA will direct the Contractor when to begin the Transfer Plan implementation. The FAA is in the process of providing a replacement system for the PDARS system through the development and implementation of WILBUR. The WILBUR platform is the authoritative operational data source for the FAA for Operational Performance Metrics and Data. PDARS is one of four legacy systems that will be phased out and transitioned to WILBUR. Once approved, a transition period will be required to migrate data, reporting functions, and tools to the new WILBUR system which necessitates the need for PDARS to continue its services until WILBUR is operational. 3.6 PROGRAM MANAGEMENT 3.6.1 CONTRACT MANAGEMENT The Contractor must provide program management support that identified tasks are performed efficiently, accurately, on time, and in compliance with the requirements. The Contractor must assign a dedicated Program Manager to establish the program requirements and to organize, plan, schedule, implement, control, analyze, and report on all elements of the Contract. The Program Manager must be accountable to the FAA for all coordination efforts and work performed under this Contract, such as the standards established by the Project Management Institute (PMI). The program management tasks and responsibilities must include, but are not limited to, the following: • The Contractor must perform ongoing project management throughout the duration of each Task identified within this SOW, including, but not limited to, planning milestones, activities, deliverables, and schedules and reporting project status against scheduled milestones, activities, and deliverables. • Participate as a member of a Government-led team as required by the Contracting Officer’s Representative (COR). • Participate in the Kick-Off meeting between FAA, COR, and Contractor to review SOW requirements of the scope of work, deliverables, and provide minutes to the meeting. • As required by the COR, the Contractor must attend meetings in support of this SOW and provide meeting minutes. • The Contractor must support the Tasks elements and corresponding Subtasks identified within this Statement of Work (SOW). • The Contractor must work with the Program Management Office (PMO), third-party support contractors and in-service management contractors, and other stakeholders to complete Contract tasking. • The Contractor must work with the PMO by providing ad-hoc reports as required by the COR in support of this SOW. In addition to the above and as required by the COR, the Contractor must schedule, run, and provide meeting minutes, briefings, and agenda materials for meetings and provide recommendations and ad-hoc reports and analysis. 3.6.2 MONTHLY STATUS REPORTS (MSR) The Contractor must provide Monthly Status Reports (MSRs), and any other required reports, based on the deliverables identified in this SOW. The Contractor must provide an MSR that documents the activities of the previous month and identifies planned activities for the following month. The reports must be delivered to the COR specified at award and must include, at a minimum, the following information: • Overview of work completed, work in progress and work planned for each task. • Hours expended on tasks, labor categories, and personnel used. • Status of individual deliverables and planned activities. • Identification of risk areas with recommended remedial actions. • Status of all outstanding risks identified during previous months status reports. • Summary of expenditures for the monthly reporting period, as well as cumulative year-to-date totals for the performance period and any additional information pertinent to the Government in administering the performance of this Contract effort. 3.6.3 MONTHLY FINANCIAL REPORTS The Contractor must provide Monthly Financial Reports. Monthly review meetings must be provided upon request of the PDARS Program Manager. Each report must include the following for each Task: • Contract Line Item Number(s) (CLINs) used during the month. • Cost/hours funded or apportioned by CLIN. • Cost/hours used by CLIN. • Projected date when 75% of funds are spent. • Projected date when funds are exhausted. • Funds/hours remaining by CLIN. • Other direct costs (ODCs) estimated, used, and remaining by month. The Contractor must provide the Monthly Financial Reports in two (2) separate sections to reflect OPS and F&E funding data. 3.6.4 MONTHLY PROGRAM MANAGEMENT REVIEW (PMR) The Semi-Annual PMRs, beginning on the sixth month of the Contract, the Contractor must meet semi-annually with the PMO and COR for a Program Management Review at their Washington, DC office, or location as determined by the PMO and COR. The Contractor must conduct the monthly program management review meetings. The PMR must include, but is not limited to the following discussion: • Vendor Contract Information. • Financial Summary. • Contract Staffing Summary. • Subcontractor Status. • Performance Summary. • Accomplishments. • Delivery/Task Order Information. • Action Item Summary. • Backup Information. The Contractor must provide meeting minutes resulting from the PMRs. Meeting minutes must include, but are not limited to: • List of Attendees. • Topics Discussed. • Comments. • Action Items and Owners. 3.6.5 SCHEDULES The Contractor must provide a schedule that describes the tasks to be performed, task level resource requirements, and the end results/deliverables to be produced as defined in each delivery/task order. 3.7 DELIVERABLES See table in attached Market Survey pdf. 3.8 TRAVEL All required travel will be specified in individual delivery/task orders (DO/TO) issued. The cost of transportation, lodging, subsistence and incidental expenses (per diem) incurred by the Contractor personnel when requested to travel in the performance of a DO/TO will comply with the limitations as set forth in FAA Travel Policy, Federal Travel Regulations (FTR) for civilian agency work. Before undertaking any travel in performance of a DO/TO, the Contractor must obtain a written approval from the Contracting Officer (CO) and acceptance by the Program Office Contracting Officer's Representative (COR). The Contractor must provide, at a minimum, the number of persons in the party, traveler name(s), destination(s), and duration of stay, purpose, and estimated cost. Local travel by offsite Contractor employees is not considered Other Direct Costs (ODCs) and will not be reimbursed. Local travel is within the 30-mile radius of the FAA Headquarters (HQ). Whenever possible, it is required that tax exempt forms are to be provided for lodging. All other ODCs must be coordinated in advance by the COR and approved in writing by the CO before expenditure by the Contractor. 3.9 PERIOD OF PERFORMANCE The period of performance for this Contract is a two (2) year base period with a three (3) one (1) year option periods. 3.10 PLACE OF PERFORMANCE The principal place of performance must be as designated in individual task/delivery orders issued during the term of this Contract. It is anticipated that the primary place of performance will be at the Contractor’s sites/locations. 3.11 TRANSITION The Contractor must develop and deliver a Transition Plan to the Government. Uninterrupted provision of the services required by this SOW is critical to the FAA. Consequently, it is imperative that transition to performance under this SOW be accomplished in a well-planned, orderly, efficient manner. For purposes of this SOW, the transition period must be defined as the period between contract awards to total performance of all requirements, in this case no more than thirty (30) calendar days. The Contractor in place must be required to assist in the phase-in activities required for any subsequent Contractor or the FAA. ***DRAFT***