United States Air Forces Europe (USAFE) Theater Battle Management Core Systems (TBMCS) Unit Level Support

Transcription

1 United States Air Forces Europe (USAFE) Theater Battle Management Core Systems (TBMCS) Unit Level Support 1.0 DESCRIPTION OF SERVICES: 1.1. Purpose: HQ United States Air Forces Europe (USAFE) Directorate of Aerospace Operations, Theater Battle Management (TBM) Branch (HQ USAFE/A3RI) is leading USAFE's planning and implementation of Command, Control, Communications, Computer and Intelligence (C4I) systems for support of joint/combined (NATO/Allied) military operations. Within the USAFE theater command and control (C2) architecture, these C4I systems will support USAFE operations during peacetime or in a contingency. HQ USAFE/A3RI is responsible for all TBM programs from concept to initial operating capability and is responsible for identifying, evaluating, and coordinating operational requirements for TBM Core Systems (TBMCS) improvements. HQ USAFE/A3RI serves as the MAJCOM program manager for the core TBM systems. HQ USAFE/A3RI provides command integration management for all advanced planning systems, performs the command TBM Program Element Monitor duties, and coordinates and integrates NATO TBM interoperability requirements. USAFE Computer System Squadron (CSS), C2 Development Flight (SCP) supports HQ USAFE/A3RI by providing system implementation support for C2 systems within USAFE. SCP creates theater-wide implementation strategy and schedules for TBM systems, ensures configuration management and security accreditation of TBM systems; provides C4 expertise in estimating the installation, modification, maintenance operation, and support of both existing and new systems; serves as project officers responsible for the successful implementation of various C4 programs/projects, reviews plans and specifications to ensure adequate analysis and justification of requirements, realistic cost estimates, and implementation dates; and considering supporting requirements such as scheduling deliveries, availability of installation and test personnel, site preparation, and similar concerns. USAFE CSS C2 Systems Flight (SCW) supports HQ USAFE/A3RI by providing life cycle support for C2 systems within USAFE. In this role, USAFE CSS/SCW provides implementation engineering and theater wide support for USAFE TBM systems. 1.2 Scope: The contractor shall provide all personnel, transportation, and services to accomplish the terms and conditions of the task order (TO). This Task Order (TO) requires the contractor to provide resources necessary to support the specific activities delineated below. This support shall be provided to USAFE CSS/SCP, USAFE CSS/SCW, and for users of TBM systems and functions at the force, wing and squadron level within the USAFE AOR. TBM systems comprise Theater Battle Management Core Systems (TBMCS), Tactical Aircrew Scheduling and Airspace Management System (TASAMS), USAFE Personal Computer - Integrated Information and Intelligence (PC-I3), and NATO Integrated Command and Control System (ICC), Enhanced Maintenance Operations Center (EMOC), Higher Headquarters Reporting Management System (HHRMS), and system extensions Skill Capabilities: The contractor shall provide the skill capabilities within the following work areas Intelligence Systems and Technical Support: Page 1 of 10 Pages

2 General Support Engineering: TBM SYSTEMS SUPPORT: The contractor shall document key support provided under all subparagraphs of TBM Systems Support in a ly Project Status Report (PSR, CDRL A001). The contractor shall provide both routine and specified support for each of the Statement of Work (SOW) paragraphs below. The government will notify the contractor to provide non-routine TBM Systems Support or to develop any CDRL (other than the PSR). Government notification will consist of written tasker ( ) from the Quality Assurance Personnel (QAP) or designated alternates. Government taskers will include a brief description of the requirement, and a desired completion date. Government taskers that required a CDRL item to be produced and delivered will include a description of the level of detail required, and the desired completion date. For all Government taskers requiring delivery of a CDRL, the contractor shall assign the task to the appropriate CDRL based upon the guidance provided by the tasker and in accordance with (IAW) paragraph Unit Level Technical Support: The contractor shall provide technical support for TBM Systems and associated direct support systems at designated base Network Control Centers (NCCs) or designated work locations within USAFE. The contractor shall work with Government system and network administrators to support system operations, system engineering, and to assist with local help desk support for TBM Systems at the designated locations. Specifically, technical support shall be provided at: Ramstein AB, Germany; Spangdahlem AB, Germany; Incirlik AB, Turkey; Aviano AB, Italy; RAF Lakenheath, United Kingdom; and RAF Mildenhall, United Kingdom. Support is required during normal duty hours from the start date at each site. Contract shall support up to 2 concurrent tasks at each site, except Incirlik and Mildenhall where that shall support up to 1 concurrent task is required. In support of this requirement, these positions are deployable and mission essential. The contractor shall provide personnel experienced in Oracle RDBMS on Microsoft Windows Operating Systems, Microsoft Windows 2000 Professional, and Microsoft Windows 2000 Advanced Server. Experience with TBMCS Unit Level Operations is strongly encouraged, as is experience with NSI Double Take, Microsoft Clustering, Java Server Page (JSP) Scripting, extensible Markup Language (XML), BEA WebLogic and Veritas BackupExec. The contractor shall assist the NCC staff analyze identified TBM System or network problems, troubleshoot system problems, isolate faults, and diagnose TBM system failures. The contractor shall assist the NCC staff in documenting corrective action steps needed to resolve problems for system trouble calls using the Government provided trouble ticketing system (Remedy). The contractor shall assist the NCC in elevating identified problems to the TBM Systems Theater Help Desk if the trouble is not resolved within 4 duty hours. The contractor shall assist the NCC in response to routine requests for support such as: establishing and maintaining system user accounts; configuring file permissions and print queues; loading and configuring software updates and patches; performing system backups; evaluating user problems; and evaluating system and network operating problems. Page 2 of 10 Pages

3 The contractor shall assist the NCC in performing system administration on TBM system servers and workstations; installing operating systems; configuring/reconfiguring systems; installing government provided application and utility software; configuring application servers; and assisting in troubleshooting system problems. The contractor shall coordinate efforts between the TBM System Unit Level Functional and Technical efforts to provide cohesiveness and singularity of focus at each operating location Theater-Wide Technical Support: The contractor shall provide technical support for TBM Systems at the USAFE CSS, Ramstein AB, Germany. The contractor shall provide administrator and engineering support working with USAFE CSS systems and network administrators to provide network operations, system engineering, and Theater-Wide help desk support for TBM Systems. Support is required during normal duty hours from the start date. Contractor shall be able to support up to 2 concurrent tasks. In support of this requirement, these positions are deployable and mission essential. The contractor shall provide personnel experienced in Oracle RDBMS on Microsoft Windows Operating Systems, Microsoft Windows 2000 Professional, and Microsoft Windows 2000 Advanced Server. Experience with TBMCS Unit Level Operations is strongly encouraged, as is experience with NSI Double Take, Microsoft Clustering, Java Server Page (JSP) Scripting, extensible Markup Language (XML), BEA WebLogic and Veritas BackupExec. The contractor shall assist the USAFE CSS personnel in performance of system administration on TBM system servers and workstations; installation of operating systems; configuration/reconfiguration of client systems and servers; installation of government provided application and utility software; and assistance in troubleshooting system problems. The contractor shall work with the USAFE Network Operations Support Center (NOSC) and USAFE CSS support staff to document TBM system trouble calls using the Government provided trouble ticketing system (Remedy). The contractor shall assist the USAFE CSS staff analyze problems, troubleshoot and isolate faults, diagnose computer system failures, and assist TBM system users. The contractor shall recommend problems be elevated to the TBMCS Tier 2 Help Desk within one duty day if the trouble is not resolved. The contractor shall assist the USAFE CSS to initialize and load TBM Systems databases; execute and monitor database saves and restores; monitor database performance; provide recommendations necessary to maintain data integrity of the databases resident on TBM Systems; and use database management utilities to migrate data resident on current TBM systems to formats required for newly integrated systems. The contractor shall assist the USAFE CSS to manage the TBM system local-areanetworks (LANs) and troubleshoot issues associated with communication with external systems, such as the TBMCS Force Level Perimeter Security System (PSS) virtual private network. Page 3 of 10 Pages

4 The contractor shall assist the USAFE CSS to install and configure TBM systems and associated peripherals in support of Theater-Wide installation plans. The contractor shall assist the USAFE CSS to provide general engineering support related to the TBM systems, equipment and networks; review government provided system and architecture designs; perform system engineering studies; and perform system baseline testing. The contractor shall assist the USAFE CSS to develop and modify system administrator checklists for TBM systems. The contractor shall assist the USAFE CSS to inspect existing or new sites for potential deployment or bed-down of TBM systems. The contractor shall assist the USAFE CSS to generate Software Problem Reports (SPRs) to document identified TBM System software problems Project Management Support: The contractor shall assist the USAFE CSS staff by providing TBM Systems program and project management support in the USAFE CSS, Ramstein AB, Germany. Support is required during normal duty hours from the start date. Contractor shall be able to support up to 1 concurrent task. The contractor shall assist in preparing bullet background papers, staff summary sheets, and staffing packages; reviewing and coordinating on staff packages; responding to e- mail data requests; providing planning support; and preparing detailed implementation schedules and documentation. The contractor shall attend program and project management related meetings, working groups, conferences, and seminars in support of the USAFE CSS; provide trip reports to reflect issues and actions discussed Systems Security Support: The contractor shall provide system security support to the USAFE CSS, Ramstein AB, Germany. Support is required during normal duty hours from the start date. Contractor shall be able to support up to 1 concurrent task. This support is Mission Essential. The contractor shall observe security accreditation testing, document security issues, recommend security enhancements, and assist the USAFE CSS to maintain and update security data, policies and procedures for USAFE TBM systems. The contractor shall assist the USAFE CSS in performing limited system security testing and produce risk assessment products in support of locally proposed TBMCS system changes. The contractor shall assist the government in the preparation of new or updated DOD Information Technology Security Certification and Accreditation Process (DITSCAP) System Security Authorization Agreement (SSAA) packages for USAFE TBM systems by generating discrete portions of DITSCAP documentation packages. The contractor Page 4 of 10 Pages

5 shall assist USAFE CSS personnel in meeting TBM systems specific requirements for security. The contractor shall attend security related meetings, working groups, conferences, and seminars in support of the USAFE CSS; provide trip reports to reflect issues and actions discussed. The contractor shall assist USAFE CSS in preparing bullet background papers, staff summary sheets, and staffing packages; reviewing and coordinating on staff packages; responding to data requests; providing planning support; and preparing detailed documentation on TBM System security related tasks and activities TBM Interoperability and Integration Support: The contractor shall provide personnel with functional expertise in support of TBM Systems to augment the USAFE CSS staff at Ramstein AB, Germany. Contractor shall be able to support up to 1 concurrent task. This support is Mission Essential. The contractor shall review and comment on documents; prepare briefings and presentations; review and coordinate on staff packages; respond to data requests; provide analysis support; and assist the Government to formulate operational concepts and architectures. The contractor shall assist in analyzing future USAFE TBM systems requirements and upgrades by reviewing existing or proposed implementations of USAFE TBM system capabilities to determine if they will accommodate operational requirements validated by the Government. The contractor shall provide recommendations on requirements for interoperability with USAF and NATO Command and Control (C2) systems including those listed in the scope of this TO. The contractor shall assist the supported organizations with coordination of TBM Systems functional requirements with other agencies on issues relating to in-garrison and deployed operations. The contractor shall provide assistance in developing functional and interoperability requirements in support of USAFE exercises and contingencies. The contractor will work with USAFE CSS, HQ USAFE, and organizations external to USAFE (to include NATO) in the development, testing, and evaluation of interoperability solutions. Contractor shall provide personnel with functional and system engineering expertise in United States Command and Control Systems for Air Operations in order to support the development of interoperability requirements and solutions. Experience with Oracle RDBMS on Sun Solaris and Unix scripting languages (Perl, C-Shell, Korn, Bourne) is required. Experience with Sybase RDBMS on Sun Solaris and with NATO Command and Control Systems for Air Operations is desirable Software and Hardware Systems Engineering: Reserved Page 5 of 10 Pages

6 Configuration Management (CM): Reserved Technical Evaluation, Analysis, and Investigation: Reserved Intelligence Analytical Support: Reserved Management Assistance: The contractor shall document key support provided under the subparagraphs of Management Assistance in the ly Project Status Report. Management Assistance activities will be in support of SOW requirement paragraph 1.3.1, and will count as labor hours under those specific paragraphs Site Surveys: Reserved Training: Contractor Training: The contractor may be tasked to attend training courses specific to current and future versions of TBM systems. The Government will provide funding for all required training courses and associated travel. On the Job Training (OJT) will also be utilized System Administrator Training: The contractor may be tasked to provide formal or informal TBM Systems administrator training for USAFE support personnel. This training specifically will comprise hardware and operating systems and application software components of the TBMCS systems identified in the scope of this SOW. The contractor shall not be required to train more than 5 students per course, and will be notified to train not more than 2 courses per or 12 courses per year. Government notification to the contractor will be provided at least 15 working days in advance of the desired training start date. The government will provide the facility, equipment, and all manufacturer and program office training materials Technical Reviews and Meetings: The contractor shall attend technical reviews and meetings in support of SOW paragraph requirements. When notified, the contractor shall attend and participate in technical reviews, working groups, briefings, and meetings. Participation may include collecting data, reporting data, presenting the USAFE position (not to include obligating funds), acting as a facilitator or providing analysis or engineering support individually or as part of a working group or team. The Government tasker will include specific objectives for contractor attendance at the meeting, when possible, no later than two working days in advance of a local review or meeting. Government taskers to support meetings that require travel outside the local area will be IAW paragraph (travel). The contractor may be authorized to represent USAFE positions at a meeting or conference, but under no circumstance will the contractor make a decision for the government. The contractor may be tasked to support up to 20 meetings, conferences, reviews, training sessions, or working group meetings per. Page 6 of 10 Pages

7 Project Monitoring and Reporting: The contractor shall provide support to include, System Implementation Plan, Project Status Reports, Baseline Schedule and Control, and TO Writings. The contractor shall assist the government prepare draft SOWs and Rough Order of Magnitude (ROM) estimates. The contractor may be tasked to support up to 5 SOW preparation activities or to develop 10 ROMs during the TO Period of Performance (POP) Presentations and Briefings: The contractor shall prepare presentations and briefings. Specific formats and requirements will be identified in the TO Materials/Supplies: Reserved Travel: Travel 100 kilometers or more outside the government assigned work areas will be performed using official Letters of Identification (LOIs) for contractor employees prepared by the contractor for coordination and funding by the customer, with approval from the Contracting Officer (CO), to include per diem as authorized by the Joint Travel Regulation (JTR). Travel IAW CLIN 0004 is a To Be Negotiated item, however, shall comply with the JTR rates. All travel cost incurred in support of the requirements of this SOW are costreimbursable to the contractor by the Government. The Government will provide official Government orders in the form of Letter of Identification (LOI) for all required travel. No single contractor employee will be required to spend more than 30 calendar days in CONUS during the TDO POP. All requirements for travel will be provided by the QAP to the contractor with minimum lead-times in accordance with the following table: Duration of TDY in Days Minimum Lead Time Notification 5 or less working days 2 work days 6 to 10 working days 4 work days 11 or more working days 5 work days 1.4. Personnel Labor Categories: Qualifications: IAW SOO Equivalent experience: IAW SOO Project/Program management: The contractor shall identify a task project team leader for each TO. The contractor shall also identify an overall basic contract project manager, who may serve as both the project manager and a project team leader on a TO. Page 7 of 10 Pages

8 2.0. SERVICE DELIVERY SUMMARY (SDS): A SDS identifying performance objectives and performance thresholds will be included in the Statement of Work (SOW) for each TO. Performance Objective SOW Paragraph Required NLT Page Count Maximum Government Comments Provided Within Final CDRL Delivered NLT Maximum Required during the POP Performance Threshold TBM Systems Project Status Report Total Requirement 5 th working day of the N/A N/A N/A 1 per calendar IAW QCP Staffing Note Total Requirement 7 working days after completion of analysis 5 pages N/A N/A NTE 6 per calendar IAW QCP Technical Note Total Requirement 14 working days after completion of analysis 12 pages N/A N/A NTE 3 per calendar IAW QCP Analysis Document Total Requirement 30 working days after completion of analysis 25 pages 21 working days from receipt of Initial Document 30 working days from receipt of Governmen t comments on Initial CDRL NTE 1 per calendar IAW QCP Presentation Materials Total Requirement 14 working days after completion of data collection or analysis 10 pages 7 working days from receipt of Initial Document 7 working days from receipt of Governmen t comments on Initial Document NTE 3 per calendar IAW QCP 3.0. GOVERNMENT-FURNISHED PROPERTY AND SERVICES: 3.1. Government Furnished Property (GFP): IAW the basic contract, the Government will provide the facilities and equipment necessary to perform the tasks stipulated in this SOW. The facilities include office space in both classified and unclassified facilities; the equipment includes computers (both PCs and workstations), printers, networks, copy machines, telephones, fax machines, desks, and chairs Government Furnished Services: IAW SOO GENERAL INFORMATION: 4.1. TO procedures: IAW SOO Technical Evaluation: Reserved. Page 8 of 10 Pages

9 Task Order (TO): A firm fixed price (FFP) TO shall be negotiated, using the appropriate CLINs set forth under the contract pricing schedule Performance Period: 1 September 2004 through 31 August 2005 with phased starts for certain positions. The overall period of performance for this TO will be 1 September 2004 to 31 August The anticipated start dates for tasks at specific locations shall vary as follows, and shall be firmed up within 45 days of actual required start date: Ramstein AB, 735 CS 1 September 2004 RAF Mildenhall, 100 CS 1 September 2004 Incirlik AB, 39 CS 13 September 2004 RAF Lakenheath, 48 CS 17 January 2005 Spangdahlem AB, 52 CS 17 January 2005 Aviano AB, 31 CS 17 January 2005 Ramstein AB, USAFE CSS 17 January Hours of Performance: IAW SOO. The support requirements identified in this SOW are based on a 40-hour workweek (not including US Federal Holidays specified in the SOO). In some instances, it may be necessary to shift the time of performance to accommodate operations and work outside of the normal duty hours. Extended Work Week (EWW) hours may be called out to meet mission requirements associated with tasks identified in this SOW. All scheduled leave must be coordinated between QAP and Project Manager in order to ensure continuity of support Extended Work Week (EWW): EWW is to be determined Place of Performance: Tasks identified in this SOW shall be performed at Ramstein AB, Germany; RAF Lakenheath, UK; RAF Mildenhall, UK; Spangdahlem AB, Germany; Aviano AB, Italy; and Incirlik AB, Turkey, as specified. The SOW tasks will require travel to other OCONUS and CONUS locations for periods of temporary duty Quality Control Program/Quality Control Plan (QCP): IAW SOO. 4.3 APPLICABLE DOCUMENTS: DoD Information Technology Security Certification and Accreditation Process (DITSCAP) DODI Air Force Instruction (AFI) Computer Security USAFE Supplement to AFI , 8 March 2001 Air Force Policy Directive (AFPD) 3301, Command, Control, Communications, and Computer (C4) Systems 5.0. ASSOCIATE CONTRACTOR RELATIONSHIP: IAW SOO SECURITY REQUIREMENTS: IAW SOO. Page 9 of 10 Pages

10 7.0. Reserved MISSION ESSENTIAL PERSONNEL: Personnel are deemed Mission Essential for this TO and Paragraph 8.0 of the Basic SOO is applicable. Also, in support of this TO some of the positions are deployable and are identified in the sub-paragraphs of PERFORMANCE OF SERVICES DURING CRISIS DECLARED BY THE NATIONAL COMMAND AUTHORITY OR OVERSEAS COMBATANT COMMANDER: All services required within the scope of this contract may be determined to be essential for performance during crisis according to DoDI The contractor will be notified of the specific performance requirement, hours of operation required and the procedures to notify the contractor at the time of need. Page 10 of 10 Pages