SourcesSought_57IS_SB_SOW_Final.doc

Basic Contract -- STATEMENT OF WORK SENSOR BEAM Support Sources Sought Draft

1.0 BACKGROUND:

1.1 The 57th Intelligence Squadron (57 IS), Air Combat Command (ACC), is responsible for technically documenting US and friendly foreign electromagnetic systems parametric data and analysis/documentation of airborne target signatures. These responsibilities address the electronic warfare operational requirements mandated by Air Force Instruction 10-703; the Joint Chiefs of Staff, CJCSM 3320.04 & CJCSI 3320.01D; and the formal tasking issued by the Defense Intelligence Agency (DIA) for EWIR Database (EWIR) production.

1.2 The unit has been at the forefront of integrating the functional areas of Intelligence Mission Data (IMD) for the Combat Air Force (CAF) and the DoD. Historically, these functional areas have been stove-piped with little crossover in product or analysis. The 57 IS and NASIC have been merging portions of the analytic processes, tasking, and products over the last decade to provide EWIR customers, most notably the 5th Generation Fighter Community, with an integrated set of intelligence products that meet the needs for modern sensor fusion and Integrated Defensive Aids Suites. These integrated products comprise the concept of Intelligence Mission Data (IMD).

1.3 The 57 IS has a need for a contractor with an established Electronic Warfare Integrated Reprogramming Database (EWIR) infrastructure, a capability to generate Tier 2 EWIR Database (EWIRDB) files (technical electronic intelligence [ELINT] reference file [TERF]- and standard EWIR reference format [SERF]-based), ability to create complex simulation-ready Tier 1 files, and expertise with tools used to generate modernized EWIR SERF-based products. Further IMD files include (but are not limited to) Characteristics and Performance (C&P) data, Signatures data, as well as supporting the Order of Battle (OOB) mission area through Defense Intelligence Equipment (DIEQP) Code generation/maintenance and electronics/platform-fit data. This also includes commensurate experience in the basic information gathering, data reduction, product preparation, and database production functions for related intelligence products/models such as the Military Equipment Parametrics and Engineering Database (MEPED), Improved Many-on-Many (IMOM) elements, Air Force Mission Support System (AFMSS), Combat Support Database (CSDB), Combined ELINT Database (CED), and ELINT Intercept Model/Observed ELINT Engineering Model (EIM/OEEM).

2.0 SCOPE. The contractor shall perform all tasks necessary to research, analyze, technically document, and perform reviews for the electromagnetic systems, events, and signatures specified by the 57 IS. These tasks include but are not limited to, analytical studies, feasibility analyses, certification evaluation, quality reviews, system management studies, computer system administration and software development, developing and updating analysis tools and methods using software process improvement as required, as well as all tasks necessary to performing a complete study of systems, events, and signatures. Systems include but are not limited to, radar systems, missile warning receivers, electronic counter measure systems, electro-optical/ infrared (EO/IR) systems, communications systems, surface-to-air missiles, anti-aircraft artillery, and passive radar systems. Events include, but are not limited to, identification, targeting and signature events. Signature descriptions include but not limited to, radar cross section (RCS), antenna patterns and EO/IR signatures of airborne targets, including aircraft, missiles, and physical countermeasures. These tasks/studies will include the acquisition of information, analysis of specific and non-specific data items, and technical documentation of data into an established format. Examples of established formats include those associated with the Electronic Warfare Integrated Reprogramming Database (EWIRDB), the United States Electromagnetic Systems Database (USELMSDB), the Combat Support Database (CSDB), Blue Airborne Target Signatures Database (BATS), and the NATO Emitter Database (NEDB). Most services will be performed in the contractor’s facilities; however some tasks must be performed in 57 IS workspaces. Computer systems support includes, but is not limited to, automated information systems based on MS Windows and various UNIX and UNIX-like operating systems to complete all tasks associated with enabling and sustaining the information technology infrastructure including hardware and software required to accomplish the mission areas and system enumerated in this Statement of Work.

3.0 REQUIREMENTS:

3.1 Task 1 (Analysis):

The contractor shall use appropriate researched information and/or laws and principles of electromagnetic science when there is a lack of information available on an assigned system. The contractor shall consult with the contracting officer and the contracting officer’s representatives concerning questions dealing with the accuracy or validity of the data entries and the adherence to analysis and technical standards of practice. The contractor shall respond to the Contracting Officer and the contracting officer’s representatives concerning questions dealing with the accuracy or validity of the data entries and the adherence to analysis and technical documentation strategies.

Analysis for CSDB requires particular experience in generating Sensitivity Time Control (STC) and Moving Target Indicator (MTI) plots to create specialized CSDB beam pattern data. This ensures the Mission Planning community is provided accurate data to route their ingress, egress and weapons delivery paths, and requires a keen understanding of the requirements for the Threat-On-The-Fly (TOTF) and Common Low Observable AutoRouter (CLOAR) models and how they interact with the parametric definitions within the CSDB radar studies.

3.2 Task 2 (Production):

3.2.1 The contractor shall create, modify, and update USELMSDB, EWIRDB, NEDB, BATS, CSDB, and platform characteristics and performance studies in accordance with the corresponding study creation process, and quality control and guidance given by 57 IS. The contractor shall migrate USELMSDB studies to EWIRDB and NEDB formats. The contractor shall identify similar systems that can possibly be combined in an effort to conserve time and avoid report duplication. USELMSDB, EWIRDB, and CSDB file production shall be completed simultaneously to economize the production effort. The number and types of file and data production will be set by subordinate task orders issued under this contract. A rough order of magnitude estimate, not binding on the government, for these production types is 100 USELMSDB/EWIRDB studies, 300 CSDB studies, 100 platform characteristics and performance studies, and 12 NEDB files per task order and/or year, depending on immediate government needs and available funding.

3.2.2 The development of the Joint Strike Fighter resulted in a revolutionary shift in EWIR releasability requirements and is a major community concern. The 57 IS is developing RELPARA under OPANA, a relational toolset, which supports its unique processes required to fulfill the EWIR “Blue/White” releasability efforts. This is a problem not shared among the “Red” threat data producers within the intelligence community. The requirement to manage multiple data formats greatly expands the management burden, requiring analysts to be proficient in multiple models, tools, and standards.

3.2.3 After analyzing each electromagnetic system, the contractor shall prepare a finished report in accordance with applicable standards listed in section two of this statement of work. The contractor is encouraged to develop stand-alone technical documentation and analysis tools to improve the analytical and technical documentation and analytical process. Tools developed under this contract, and modifications to existing tools shall remain the property of the Government, this includes the source code and documentation. All reference materials used, procured, or acquired to perform these analyses will become Government property.

3.2.4 Digitize file folder contents (using the Portable Document Format (.pdf) structure/format) and load these files into the Scanning of Library Air Force References (SOLAR) database.

3.2.5 The contractor shall concisely and thoroughly document all methods and procedures used for acquisition of data, analysis of the data, QA of data, and procedures/methods used for deconflicting various sources of data. This will enable the Government to assess the technical quality of specified, measured, and predicted data.

3.3 Task 3 (Research): The contractor shall locate and obtain the data required to complete research on all assigned systems for inclusion into the research tracking system in use by the 57 IS. All primary data sources and networks (at Attachment 1) shall be examined and explored, and all primary personnel (also at Attachment 1) shall be contacted to obtain the necessary information. The contractor shall obtain official endorsement demonstrating need-to-know from the Contracting Officer Representative (COR) as required by vendors, etc. to complete the assigned file research.

3.3.1 Provide on-site researchers capable of performing all levels of research tasking and gaining the appropriate security clearances. In addition, the contractor will staff the off-site technical library with qualified personnel to provide the appropriate technical research required to support the 57 IS and this contract. Staff analysts can provide research assistance as required.

3.4 Task 4 (Technical Library): Maintain any documentation gathered in support of this contract in the Technical Site Library unless otherwise directed by the COR. Documents will be classified up to SECRET//NOFORN and may be proprietary in nature. The portion of the library, which consists of Air Force technical orders and documents belonging to the Air Force and DOD Agencies, shall be maintained in accordance with Air Force and DoD instructions. A technical library is required in performance of this contract. The Government will provide the initial technical library. The contractor shall accept and maintain the technical site library (at contractor’s location) no later than 60 days after receipt of contract award. The contractor shall maintain any documentation gathered in support of this contract. The contractor shall use this technical site library to gather and maintain parametric, event, and signature data on assigned systems. The contractor shall maintain a record system for the technical site library from which the government may request abstracts, inventories, and other reports. The contractor shall not release data to any other government agency or contractor without the written permission of the 57 IS. The technical site library contents shall be properly inventoried and returned upon completion of the contract. The contractor shall ensure that 57 IS personnel have access to the library for research purposes within one hour of telephone notification of visit. The contractor shall perform limited research on designated topics in the 57 IS library under the guidance of the 57 IS research personnel. The contractor shall provide a current monthly listing of all publications contained in the technical site library to the COR.

3.4.1 Use of automated database(s) to monitor document control and system folder analysis status is required. The government may request copies of this data on up to a weekly basis.

3.4.2 Refer to Attachment 3 for Technical Library Phase-Out/Phase-In Plan.

3.5 Task 5 (Advisory and Assistance): The contractor shall provide assistance in the development of, and/or preparation of recommendations on, project strategies, management plans, and schedules, to find and utilize emerging technologies that are potentially useful to this project.

3.5.1 The contractor shall assist in the organization, execution, preparation, and/or presentation of material for various committee meetings, seminars and conferences. This includes, but is not limited to the annual Electronic Warfare Integrated Reprogramming Data Base (EWIRDB) Forum, EWIRDB Standardization Committee, Intelligence Mission Data Committee (IMDC), and Mission Planning Interface Control Working Group meetings (ICWG), among others.

3.5.2 The contractor shall provide support as required in the form of oral and written presentations, program/project reviews, and meeting preparation and attendance at such times and places as designated by the government. The contractor shall prepare studies, program plan development, and publications for 57 IS dissemination (in formats designated by the 57 IS).

3.5.3 The contractor shall assist 57 IS analysts in responding to Requests For Information (RFIs), production requirements, and problem reports pertaining to USRELMSDB, USELMSDB, Platform, and CSDB systems and their use.

3.5.4 The contractor shall perform research and development of new production techniques and tools to improve the technical documentation report generation methodologies. The contractor shall also perform special research projects pertaining to parametric data, signature data, and events as requested by the government. The contractor shall conduct studies to include requirements definition, cost performance analysis, feasibility studies, long-range analysis, and other studies as requested by the government. Research shall be conducted at both the contractor facility and in 57 IS workspaces. The contractor shall provide reports that document the methodology and results of any research.

3.6 Task 6 (Training):

3.6.1 The contractor shall develop, produce, and deliver training courses for 57 IS analysts and others to perform analysis and quality control of parametric and signatures studies and other activities as specified in the task orders. The contractor shall maintain the ability to assist 57 IS representatives in developing, producing, and delivering 57 IS training courses for 57 IS analysts and other customers (to include representative of foreign nations in accordance with Section 10 of the National Industrial Security Program Operating Manual (NISPOM) and 22 CFAR 120 – 130 of the ITAR) in performing analysis and quality control of parametric studies and other activities as required. These courses may be taught in the USA or in other countries as directed by 57 IS. This may require the maintenance of Technical Assistance Agreements (TAAs) with key US allies to provide training and familiarization while staying within the bounds of the International Trading in Arms Regulations (ITAR).

3.6.2 Attend training as required by the Government. Training will consist of at least training for specific positions/tasks in the local area at no additional cost to the Government or the contractor. In addition, the contractor shall complete other training as required by the COR, including but not limited to such courses as the annual USAF Information Assurance Training for those personnel with access to government networks.

3.7 Task 7 (Computer System Administration and Software Development):

3.7.1 Provide systems support for MS Windows and UNIX-based systems. System support includes troubleshooting problems that arise in those systems and returning same to operation. The contractor shall possess an in-depth knowledge of a variety of operating systems (OS) to include, but not limited to, those required for MS Windows, various types of UNIX (Linux, BSD, Solaris, HP-UX, etc.), and other computer systems that are introduced during the life of the contract. The contractor shall assist users in solving problems caused by the addition of hardware or software.

3.7.2 Evaluate/integrate Commercial Off-The-Shelf (COTS)/Government Off-The-Shelf (GOTS) Web Software for the 57 IS IntraWeb or other networks. The contractor shall address inter-relationship issues of Web Server, Data Base, and Computer Graphic Interface (CGI) programming technology and the workings of the MS Windows operating system at the machine administration level. The contractor shall install, test, evaluate, and integrate COTS/GOTS software. The contractor shall assist the network user in solving problems related to computer hardware, operating system and application software.

3.7.3 Provide planning, design, development, testing, and implementation of SENSOR BEAM databases which require COTS relational database software tools. This will include such COTS as ORACLE and SYBASE software tools on UNIX or MS Windows client/server workstation configurations, as well as other configurations involving MS Windows compatible workstations.

3.7.4 Provide planning, design, development, testing, and implementation of modernized software tools associated with the population and modification of SENSOR BEAM databases. Such tools shall include platform-independent software applications that expand capabilities and increase ease-of-use for both producers and users of the SENSOR BEAM databases.

3.8 Task 8 (Quality Assurance):

3.8.1 The contractor shall produce Quality Assurance (QA) reports as required by the task order requirements. These reports will consist of the results of a comparison of parametric, signature and event data entries against each other for reasonable values. Other databases will be used for comparison as well. Consistency of format must be maintained. The step by step procedures used by the contractor to maintain the quality of the data shall be defined in the QA report. Upon completion of contractor QA, the Government will review all or a portion of data for proper formatting and data accuracy and will provide written notice to contractor of the Government’s acceptance.

3.9 Task 9 (Data Delivery): Quarterly CSDB shipments and monthly USELMS updates are required to ensure the Production lines are periodically synchronized.

3.10 Task 10 (Administrative):

3.10.1 Prepare and deliver monthly status reports, which shall include all pertinent information concerning this task directive and/or any other information requested by 57 IS.

3.10.2 Prepare a final report upon completion of this task directive. This should include an electronic version of all monthly and trip reports generated under this task.

3.10.3 Transport classified and unclassified materials between the contractor and 57 IS facilities as required. All applicable government security regulations governing the transportation of classified material shall be strictly adhered.

3.10.4 Provide sufficient space to government personnel at contractor site for QC, acceptance review, analytical exchanges, USAF network administration, software beta testing, document review and other purposes. Appropriate equipment shall be made available to accomplish these tasks in this space.

3.10.5 The contractor shall attend meetings, guidance interchanges and working groups as required by 57 IS and outlined in individual task orders. The contractor shall provide minutes of any forums, etc. attended pursuant to this contract to the SENSOR BEAM Program Manager and the COR.

3.10.6 Attend a post award/guidance conference held at 57 IS within 30 calendar days after the date of receipt of the contract award. Specific format standards, technical documentation conventions, working arrangements, format modifications, and 57 IS evaluation methods will be discussed. Interim program reviews shall be conducted on an as needed basis, but at a minimum semi-annually.

3.10.7 Attend a quality review meeting as required by the COR at 57 IS within 30 days of submission of the final report on each task order. This meeting will be used to discuss discrepancies found in previous contractor work, to provide guidance for future tasking, and for the contractor to outline any plans, suggestions, or problems with past or future tasking. The contractor shall provide minutes for this quality review meeting.

3.10.8 Monthly Status Reports. These reports will include all pertinent information concerning each active task order plus any other information specified by the 57 IS before publishing the report.

3.10.9 Final Report. The contractor shall prepare a final report on each task order. These reports will include a summary of all efforts performed to give 57 IS an understanding of the problems and successes of each project.

3.11 Other Requirements:

3.11.1 Period of Performance: This contract is expected to be a one (1) year base contract with four (4) 1-year options requirements-type indefinite delivery/indefinite-quantity (IDIQ) contract with subordinate task orders. This expectation is not binding on the government.

3.11.2 Travel: Travel to customer sites and other areas as determined by the Government. Travel outside the local area shall be required. Such trip funding will include airfare, hotel accommodations, auto rental, and meals at the standard US Government reimbursement rates in accordance with the Joint Travel Regulation. Travel requirements will be specified in individual task orders.

3.11.3 Contingency Support: In accordance with DODI 3020.37, 6 Nov 1990 and AFI 63-124, 01 Aug 2005, the functions under this task order are considered to be mission essential and the contractor shall be required to continue to perform at the same level during national crisis. The contractor shall develop contingency plan(s) for these tasks to provide reasonable assurance of continuation during crisis conditions. The contractor shall identify to the government any employees working under this contract’s subordinate statements of work/statements of objectives (SOW/SOO) having military mobilization recall commitments. The contractor shall notify the government upon activation or recall of any such personnel. The contractor shall document these items in the first monthly status report unless required to do so by the COR in another format. In either case, the contractor shall provide the above documentation within 60 days.

3.11.4 Task Orders: Individual task orders will contain an individual Statement of Work, Service Delivery Summary (SDS), Performance Plan, Visitor Group Security Agreement, and DD 254.

4.0 DELIVERABLES When each group of deliverables is delivered to the 57 IS, the information shall be in a format specified by the 57 IS and as described in referenced paragraphs. The government will evaluate all or a portion, at the government’s discretion, of these deliverables for accuracy, currency, completeness, and adherence to the stated goals in the tasking for each deliverable. 57 IS will notify the contractor in writing of the formal acceptance or rejection of all deliverables, including reasons for rejection where appropriate, within 30 days of receipt. Common measures of acceptance include, but are not limited to: meeting specific timelines for getting product into customer hands, and minimal error rates on system analysis/file production (specific rates depend on the technology involved, and will be determined on a case by case basis, if necessary to do so). When specific quantities of systems are requested for delivery in a period of time, 57 IS reserves the right to reduce the required quantity of deliverables and introduce new tasking as needed for end user support. 57 IS will notify the contractor in writing of such task changes as soon as the need for such a change becomes readily apparent. All deliverables related to the technical documentation of a system must be both via electronic and hard copy, in a format specified by the COR. Each system documented must be accompanied by a folder, which contains all items specified in the 57 IS Standard Folder.

5.0 Government Furnished Property: The COR and Contracting Officer must approve all government furnished property activities. Government furnished property will be returned to 57 IS immediately upon expiration of the applicable task order or the basic contract. The contractor shall be responsible and accountable for all GFP provided under this contract and will be used solely for the purpose of this contract.

5.1 Applicable Documents. The applicable documents in Attachment 3 will be provided to the contractor. Any changes or updates to any document provided shall remain government property.

5.2 Secure Communications. The government will provide the contractor with secure voice and data communications equipment between the 57 IS and the contractor. The contractor shall provide appropriate security and physical space to accommodate the equipment and its use (see paragraph 6).

5.3 Technical Site Library. The technical site library consists of multiple sources of technical references in various formats (e.g. microfiche, hardcopy, magnetic media, and optical media). The approximate required reinforced floor space is approximate 1,500 square feet. The contractor shall make provisions for additional document storage estimated at up to 25% over the period of the contract. The contractor shall maintain a technical site library. The baseline collection will be transferred by the government to the contractor. The technical site library transfer will begin once the required facility clearance has been awarded to the contractor by the cognizant security office.

In addition, the contractor shall store and maintain approximately 2,500 system folders containing the technical information on each electromagnetic system tasked. References will be maintained at the contractor facility to aid analytical and research capabilities. A record system (compatible with the 57 IS technical library) for these references will be provided. The contractor shall have appropriate on-line or other data sources as specified by the government. The highest classification for the above sources is SECRET//NOFORN. 57 IS will provide the contractor’s need-to-know and approval for access where needed for the above on-line sources.

5.4 Personal Computers. 57 IS will provide personal computers and peripherals for use by Air Force personnel at the contractor’s site.

5.5 Government Office Space. Task orders may be issued which require contractor personnel to perform duties in 57 IS spaces. When this onsite work is required, workspace and general supplies will be provided by 57 IS.

5.6 Logging Tools. 57 IS will initially provide logging tools necessary for the analysis and Quality Control of data files. The contractor shall provide the ability to add and/or alter and improve items including, but not restricted to, additional data elements, analysis tools, and formatting tools as requirements change or additional 57 IS needs dictate.

6.0 Contractor Furnished Property and Services: The contractor shall be responsible for providing all required facilities, supplies, resources, and research not specifically identified as government furnished. This shall include equipment identified by the government required to conduct 57 IS mission at the contractor’s facility. The facility shall be located within a 20-mile radius of 57 IS facilities, with all work areas, storage areas, and site library collocated. The primary reason for this restriction is the necessity of 57 IS personnel having physical access to the technical library, contractor personnel, and facilities on very short notice. A secure Air Force-controlled enclosed area shall be made available either within the contractor-controlled controlled area or in an exclusion area adjacent to the contractor’s controlled area. In either case, this area shall meet the standards of the National Industrial Security Program Operating Manual (NISPOM) regulation number 5220.22M, to include alarms, a sprinkler system, a hard ceiling, and DSS-approved locks. This area shall be established to accommodate Air Force-owned automated information systems equipment and a server for a secure data link to 57 IS over a government telecommunications circuit. Any Air Force terminals within the contractor’s facility will be connected to the server to create an Air Force local area network (LAN). System accreditation shall be either as a “guest system” under the contractor’s DSS accreditation, if allowed by DSS, or as an Air Force system in the exclusion area.

7.0 Security Requirements:

7.1 Industrial Security: The Contractor is required to have the appropriate clearance level as stated in the DD Form 254, Department of Defense Contract Security Classification Specification, for its personnel to perform on this contract. This clearance will be in effect before contractor personnel are allowed to perform work on this contract. The contractor shall comply with all security provisions outlined in the DD Form 254.

7.2 Operations Security: The contractor is required to comply with operations security (OPSEC) contained in AFI 10-701, OPERATIONS SECURITY (OPSEC).

8.0 Applicable Documents

8.1 Contractor will use the following documents in performance of this contract:

· Electronic Warfare Integrated Reprogramming (EWIR) User’s Guide (SECRET)

· Combined KILTING/EWIR Definitions Vol. I - III (FOR OFFICIAL USE ONLY)

· EO/IR Data Dictionary (FOR OFFICIAL USE ONLY)

· Communications Data Dictionary (FOR OFFICIAL USE ONLY)

· Radar Warning Receiver Data Dictionary (FOR OFFICIAL USE ONLY)

· EWIR Security Classification Guide (SECRET//NOFORN)

· NAIC-0000-6394-00 Defense Intelligence Agency Analyst’s Handbook for Foreign Electronic Warfare Integrated Reprogramming Database Production (CONFIDENTIAL//NOFORN). 10 March 2000

· AFMSS: CLOAR Threat Parametric Data (SECRET)

· CLOAR Security Classification Guide (UNCLASSIFIED), 27 May 1998

· FMS Analyst’s Handbook

· Current version of NGES production guide (SECRET) from Secure Internet Protocol Router Network (SIPRNet) NASIC website.

· IEEE Standard 100, "The Authoritative Dictionary of IEEE Standards Terms”

8.2 Other Documents.

· Joint Travel Regulation. This document is available on-line on the internet at http://www.dtic.mil/perdiem/jtr.html, as well as other locations.

· National Industrial Security Program Operating Manual (NISPOM) regulation number 5220.22M Additional documents may be added during the period of performance as necessary to complete specific objectives.

8.3 Data Sources: The government will provide the contractor access to the Primary and Secondary data sources, networks, and personnel listed in Attachments 1 and 2, at either the contractor’s offices or the government’s offices, or both. Attachments 1 and 2 are subject to change by the government at any time.

Attachment 1. Primary data sources

- Electronic Warfare Integrated Reprogramming (EWIR) User’s Guide

- Combined KILTING/EWIR Definitions, Volumes I, II, and

- EO/IR Data Dictionary (TERF) as well as EO/IR threat model (SERF)

- Communications Data Dictionary (TERF) as well as telecommunications threat model

- Radar Warning Receiver Data Dictionary (TERF)

- Current Radar Threat Model in use through the EWIR community (SERF)

- Scientific and Technical Information Library Automation System (STILAS) or other acceptable library inventory/circulation system

- Federal Logistics (FEDLOG) system and DO43 system

- USAF Air Logistics Complexes (ALC) (e.g., item manager, program manager, equipment specialist, and/or engineer, etc.) if still in the Air Force inventory; if not still in the Air Force inventory, contact the manufacturer of the system

- INTELINK-SCI (e.g. Modernized Integrated Database (MIDB) including DIA Equipment Code (DIEQP) tables, Combined Emitter Database (CED), NSA’s Wrangler, Threat Analysis and Reporting System (TARS)

- INTELINK-S (see INTELINK-SCI); but at the SECRET non-compartmented level.

- Avionics Installation Plan (AIP), if available. In its absence, Fleet Support Team Information System (FSTIS) will be used for naval systems

- Surface Ship Combat System Master Plan (SSCSMP)

- Manufacturer of the system

Note: Classified networks will be accessed either via the encrypted data line between the contractor and the government, or from the government offices.

Attachment 2. Secondary data sources (used if Primary sources are insufficient).

- Cataloging and Standardization Center (CASC)

- Technical Equipment List (TEL)

- Joint Electronics Type Designation Automated System (JETDAS)

- NSA Electronic Subscription Service (ESS)

- USAF unit that operates the system

- SPECMASTER

- Reliability Maintenance Management Information System (REMIS)

- E-STEPS

- Central Information Reference and Control (CIRC) system (if applicable) Note: Classified networks will be accessed either via the encrypted data line between the contractor and the government, or from the government offices.

Attachment 3. Technical Library Phase-Out / Phase-In Plan

This plan is to take effect only if the incumbent does not retain the contract. The phase out plan for the incumbent and the phase in plan for the awardee will be handled simultaneously.

If the incumbent does not retain the contract, then incumbent shall have the site library inventoried and returned to the 57 IS within 20 calendar days after previous contract termination. It is understood that the performance period for individual task orders may vary, and until individual task order completion, the incumbent will continue to maintain and manage the documents necessary to complete those task orders. As each task order is completed, those documents will be inventoried and returned to the 57 IS within 20 days after completion. All others will be returned as described in the deliverable listing in the current contract.

All documents for the site library on hand at the 57 IS will be made available to the new contractor at the beginning of the new contract. At that point, the new contractor will begin to maintain and manage the site library as described in paragraph 3.4. As documents are released by the incumbent, they shall be transferred to the new site library for inclusion in their management system.

If a task order is issued to the new contractor which will require documents in the incumbent’s possession, requests for the necessary documents or copies must be coordinated through the Contracting Officer. Original documents will be maintained under the incumbent’s management system until they are permanently transferred from their possession. Copies transferred to the new contractor will be marked as such and will be maintained in the new contractor’s management system until they are replaced by the originals transferred from the incumbent to the 57 IS. The new contractor shall dispose of duplicates and copies in a timely manner after receipt of originals.

24-Sep-96