Bid Office, SPAWARSYSCEN, Code D21B, 53570 Silvergate Avenue, Bldg. A33, Room 0061, San Diego, CA 92152-5112

R -- TACTICAL DATA LINK 16, ISEA/SSA, INSTALLATION, DESIGN, ANALY POC Contract Specialist, Ms. Pat Oliver, Code D212, (619) 553-2333. Contracting Officer, Ms. Maria Papet, (619) 553-3385. This announcement constitutes a sources sought for interest for a possible Dept. of Navy contract. SPAWARSYSCEN San Diego (SSC SD) is seeking small and small disadvantaged firms with current knowledge and ability to perform a contract to provide technical services in accordance with the level of effort and technical scope delineated herein. The SIC CODE is 8711, average annual receipts of less than 20 million dollars. See the Statement of Work Common Data Link Management & Distribution System (CDLM&DS) at http://www.spawar.navy.mil/contract/. Interested firms are invited to respond to this synopsis and submit information, not to exceed ten pages (single-spaced), of their business size and technical capabilities. Also, the respondents should describe their ability to provide qualified personnel (with the appropriate security clearances) in the following labor categories; Program Manager, Senior Systems Analyst, Senior Engineer, Engineer, Senior Software Engineer, Software Engineer, Senior Integrated Logistics Support Specialist, and Senior Electronics Technician. Respondents shall provide information related to contracts where the respondent was involved at a comparable level of effort, in the below noted areas, within the past five years. Information shall include: points of contact and phone numbers, contract numbers, and a synopsis of the work performed. Respondents should describe how they will establish/maintain a facility to perform this work in the San Diego commuting area. Worldwide travel will be required. Scope: In-Service Engineering, Software Support Activity and technical support services required for Link-16 and associated communication system programs such as Link-11, Common Shipboard Data Terminal Set (CSDTS), NATO Improved Link-11 (NILE), and Command Control Processor (C2P) as well as follow-on programs such as the Multifunctional Information Distribution System (MIDS) and the Common Data Link Management System (CDLMS). The support will involve systems engineering, software engineering, system integration, fleet support, test, training, ILS, CM, data management, installation, project management, as well as FMS support in these areas. The Government requires respondents to be knowledgeable of the scope of the technical issues, problems, and possible solutions associated with the Link-16 and associated programs, particularly in the in-service engineering and fleet support roles. The potential level of effort will be approximately 125,000 labor hours per year for five years. Interested sources are requested to submit a package by close of business on 30 October, 1998, no later than 3:00pm local time to the following address: Space and Naval Warfare Systems Center, ATTN: PATRICIA OLIVER, Code D212, Bldg A33, Room 1602W, 53560 Hull St., San Diego, CA 92152-5000. THIS SYNOPSIS IS FOR INFORMATION AND PLANNING PURPOSES AND IS NOT TO BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT. THIS IS NOT A SOLICITATION/ ANNOUCEMENT FOR PROPOSALS AND NO CONTRACT WILL BE AWARDED FROM THIS ANNOUNCEMENT. NO REIMBURSEMENT WILL BE MADE FOR ANY COSTS ASSOCIATED WITH PROVIDING INFORMATION IN RESPONSE TO THIS ANNOUNCEMENT AND ANY FOLLOW-UP INFORMATION REQUESTS. 1.0 SCOPE: This Statement of Work (SOW) defines the production engineering, installation, integration, and life-cycle support tasks that the contractor will be required to perform for the Common Data Link Management and Distribution Systems (CDLM&DS) in support of the In-service Engineering Agent (ISEA), Software Support Activity (SSA), and associated technical codes. The contractor will be required to provide specific support services as defined in the subsequent sections of this SOW. These sections define tasks that are representative of the types of requirements that currently exist or can reasonably be anticipated through fiscal year 2004. Due to the variety of tasks that may actually be required, specific work will be initiated by means of Task Orders (TOs) that shall be issued in accordance with the provision of this SOW and other provisions of the basic contract. 2.0 BACKGROUND: The Space and Naval Warfare Systems Center San Diego (SPAWARSYSCEN SD), Command and Control Fleet Engineering Division (Code D64) is the principal fleet engineering support activity for two of the Navy's Tactical Data Links; LINK-16 and LINK-11 as well as the NATO Improved Link-11 (NILE). Hardware associated with the LINK-16 is the Joint Tactical Information Distribution System (JTIDS) and the Command and Control Processor (C2P) Subsystem. JTIDS (AN/URC-107) is a high-capacity, anti-jam, secure, extended Line-of-Sight (LOS), flexible Communication, Navigation and Identification (CNI) system employing spread spectrum communication technology to provide enhanced Tactical Digital Data Information Link (TADIL-J) message capabilities. The C2P Subsystem, AN/UYQ-62(V) uses the AN/UYK-43 (V) to host the operational software required to allow the JTIDS to operate in the shipboard environment. All of these systems are undergoing product improvements; JTIDS will eventually be superceded by the Multifunctional Information Distribution System (MIDS), the C2P by the Common Data Link Management System (CDLMS), and LINK-11 will be replaced by the Common Shipboard Data Terminal Set (CSDTS). Additionally, the C2P operational software is being transitioned to new Commercial-Off-the-Shelf (COTS) hardware configurations. The first COTS configuration was named C2P Rehost. The follow-on C2P COTS configuration is called CDLMS and will be phased in over the next decade, with variants similar to the AN/UYQ-62(V) variants. All of the previously discussed configurations will be deployed concurrently over a span of several years. In summary CDLM&DS is a term used to refer to all of these Subsystems as a whole. 3.0 APPLICABLE DOCUMENTS: The portions of Military standards, specifications, and other documents that are applicable and govern a specific task will be designated in the SOW for each TO. The following list of documents is provided for reference and guidance. Certain ecifications/Standards that are listed are no longer active. These are listed here due to the nature of the planned work that will include the maintenance of software code and documents as well as other program documents that were originated under these Specifications/Standards. They are not binding on the contractor, but rather the contractor shall have in place a process that will support the intent of these specifications/standards. In the event of conflict between the requirements of these specifications, standards or documents and a SOW, the requirements of the SOW shall govern. 3.1 Specifications: MIL-PRF-29612,Performance Specifications -- Training. 3.2 Standards: MIL-STD-100, Engineering Drawings Practices, MIL-STD-449, Radio Frequency Spectrum Characteristics, Measurement of, MIL-STD-461, Electromagnetic Emission and Susceptibility Requirements for the Control of Electromagnetic Interference, MIL-STD-462, DOD Test Method Standard for Measurement of Electromagnetic Interference Characteristics, MIL-STD-498 Software Development Documentation (For guidance only), MIL-STD-973, Configuration Management (For guidance only) MIL-STD-1379B, Input/Output Interfaces, Standard Digital Data, Navy Systems, MIL-STD-1388-2, DOD Requirements for a Logistics Support Analysis Record, MIL-STD-2045 Information Technology -- DOD Standardization Profiles, SD-15 Defense Standardization Program, Performance Specification Guide. 3.3 Other Publications: DODD 5000.1, Department of Defense Directive, Defense Acquisition DODI 5000.2, Department of Defense Instruction, Mandatory Procedures for Major Defense Acquisition Programs (MDAPs) and Major Automated Information System Acquisition Programs (MAISAPs) DOD 5200.28-M, Automatic Data Processing Security DOD 5220.22-M Industrial Security Manual for Safeguarding Classified Information DOD-STD-2167, Defense Systems Software Development (For guidance only). OPNAV INST 5239.1, Department of the Navy, Automated Data Processing Security Program, MIL-HDBK-1221, Department of Defense Handbook for Evaluation of Commercial Off-The-Shelf (COTS) Manuals NAVSEA INST 4720.11 Shipboard Installations and Alteration and Alteration Installation Teams, NAVSEA TM 090-LP, Ship Repair Contracting Manual for Non-079-5010, Nuclear Surface Ships and Service Craft, ISO 9000-1. International Standard Organization (ISO) Quality Management and Quality Assurance Standards, Guidelines for the Application of ISO 9001 to the Development, Supply, and Maintenance of Software ISO/IEC-12207, Information Technology -- Software Life Cycle Processes EIA/IS-649, Electronic Industries Association (EIA) National Consensus Standard for Configuration Management, EIA/IS-632, Electronic Industries Association (EIA) interim Standard for Systems Engineering, EIA/IEEE-J-STD-016, Standard for Information Technology Software Life Cycle Processes, IEEE830-1993 Recommended Practice for Software Requirements Specifications, IEEE 1028-1988, Standards for Software Reviews and Audits. 4.0 TECHNICAL REQUIREMENTS: The contractor shall provide systems engineering, logistics support, integration, installation, and fleet support work tasks in accordance with the following requirements. Individual TOs against the basic contract shall identify specific task descriptions, requirements, and deliverable products. 4.1 Systems Engineering: The contractor shall perform the following system engineering tasks as they relate to production and life cycle engineering support: a) Performance analysis to determine attributable causes of failures/malfunctions and potential areas of redesign/improvement, b) Design engineering support to develop system improvements to answer Fleet problems, c) Corrective action engineering to provide short-term assistance as well as long-term solutions to the Fleet d) Failure mode and effects analysis, e) Gather, analyze, use and maintain operational and maintenance and statistics to propose system changes, f) Production engineering to include reviews of Engineering Change Proposals (ECPs) and Acceptance Test Plans (ATPs), g) System engineering generate/establish requirements, to perform reviews of and provide written assessments of system and subsystem level technical specifications, studies, design documents, test plans and procedures, test reports, and related design documents, h) Environmental engineering to evaluate system environmental requirements versus the operational environment, i) EMC/EMI/TEMPEST engineering support related to performing studies of and proposing plans to test for, identify and/or propose corrective action to reduce Electromagnetic Interference (EMI) and ensuring Electromagnetic Compatibility (EMC) between CDLM&DS and other shipboard systems, j) Test engineering to develop evaluate and maintain manual and automated test procedures to effectively test system functions and interfaces; perform requirements analysis, test development, evaluation, performance, manning, scheduling requirements, data collection and analysis, report generation, conduct testing both in the laboratory and operational environments, k) Evaluate adequacy of and deficiencies related to test equipment and simulators/emulators, l) Evaluate system interfaces to other systems in order to resolve interoperability discrepancies, m) Analyze system operational characteristics, mission objectives, threat, environmental factors, minimum acceptable functional requirements, and technical performance for change/enhancement, n) Assess the availability and suitability of existing technology to satisfy system upgrade performance objectives; assessments shall include COTS and Non-Development Items (NDI), o) Participate in meetings, conferences, working groups, and technical discussions to address issues of fleet performance or potential enhancements to system operation/performance (technology insertion), p) Develop and distribute via electronic and/or hard copy means (i.e. website, newsletter, etc) management, technical, operational and logistics data for use by the CDLM&DS community, q) Provide value engineering (VE) support for studies and to evaluate value-engineering proposals. 4.2 System Integration -- The contractor shall perform the following to ensure system operability/interoperability and support for field and engineering changes: a) Life Cycle Laboratory operation, maintenance and alteration, b) Operation, maintenance, and upgrade of software engineering test environments; including facilities, communications/data interfaces, equipment, material, software, tools, and documentation, c) Develop/assess integration/system test design, test case/procedure, and pass/fail criteria specifications; test design shall include performance tests that exercise the system and its components at design boundaries and under stress conditions, d) Identify test assumptions, risks, limitations, constraints, and contingencies, e) Develop and maintain test metrics, f) Perform system installation testing, g) Determine system integration requirements, h) Perform on-site installation monitoring, Quality Assurance (QA), and validation, i) Plan, design, produce, install, test, and validate field and engineering changes (including the utilization of COTS Systems), j) Coordinate Fleet Field Change installation. 4.3 Fleet Engineering Support -- The contractor shall provide worldwide on-call/on-site technical assistance, direction and support to resolve problems that are beyond the capability of the organizational level. This support shall include problem identification and isolation, inspect and repair, overhaul, test and evaluation, system checkout, on-the-job- training (OJT), documentation update, and site brief/debrief : a) Provide on-call, on-site engineering investigations and failure analysis related to casualty reports (CASREPs) by technical assists and visits, b) Evaluate adequacy of existing support equipment and allowances, c) Provide ship riders to assist/train ship's personnel in all issues related to proper system operation/interoperability issues during underway test and training missions. 4.4 Software Engineering -- The contractor shall provide the following software support services toensure support during the system's life cycle: a) Review, verify, and validate Software Trouble Reports (STRs); establish and maintain Trouble Report data bases, b) Develop and propose ECPs, c) Provide impact assessment and requirements analysis for implementation of STRs and ECPs d) Design, code, and document required changes to computer resources e) Validate and test software for all computer resources including participation in regression testing, Life Cycle Laboratory testing, System Integration Facility (SIF) testing, and Joint Interoperability Certification testing for all-service certification, f) Reproduce and distribute software updates and supporting technical documentation, g) Provide the support for software Configuration Management (CM) and provide technical representation at software Configuration Control Boards and design reviews, h) Conduct reviews of and provide written comments to contractor generated computer software documents i) Maintain and develop documentation associated with computerresources j) Ensure QA of all computer resources, k) Design, develop and establish an expanded software support facility for the CDLM&DS system life cycle software support, l) Manage and maintain a facility for software support. 4.5 Training -- The contractor shall review operator and maintenance training procedures and skill levels. Where training deficiencies are noted, the contractor shall prepare appropriate training curricula and course material changes. a) Maintain existing computer based training (CBT) programs, b) Develop new CBT in response to emerging fleet needs, c) Update the Navy Training Plan (NTP); monitor current Navy training being conducted including written assessments of adequacy, make recommendations for change, d) Conduct OJT and supplemental classroom operator and maintenance training, e) Conduct shipboard operator refresher training in support of specific Battle Group needs, f) Develop new training courses in support of Foreign Military Sales (FMS) installations addressing not only standard CDLM&DS operations, but additionally, host country unique configurations. 4.6 Integrated Logistics Support (ILS) -- The contractor shall provide technical and management support in the below listed areas of ILS. Support shall include performing studies, gathering necessary data, generating documents, reviewing and commenting on existing documents, participating in meetings/conferences where such documents are reviewed/discussed, and revising, reproducing and distributing such documents. These efforts shall address logistics management and planning, maintenance planning, supply support, training, manpower, support and test equipment, and facilities. The contractor shall also provide logistics engineering support related to generation of and providing inputs to the following: a) Integrated Logistics Support Plans (ILSP), b) User Logistics Support Summaries (ULSS), c) Integrated Logistics Support Management Teams (ILSMT), d) Logistics data bases (LSA/LSAR), e) Level Of Repair Analysis (LORA), f) Master Acquisition Program Plans (MAPP), g) Planned Maintenance System (PMS), h) Naval Training Plans (NTP), i) Preliminary Allowance Lists (PAL), j) Allowance Parts Lists (APL), k) Ship Alteration Records (SAR), l) Technical Manuals, both Navy and COTS, m) Interactive Electronic technical manuals (IETMs), n) Maintenance and depot planning, o) Evaluation of adequacy/efficiency of existing depot test procedures, test tools/fixtures, automated test equipment including Consolidated Automated Support System (CASS) test stations, Test Program Sets (TPS), and other related diagnostic tools and procedures, p) Reliability, maintainability, and availability engineering to perform data gathering and analysis to resolve reliability problems and assist in reliability growth, failure reporting and corrective action efforts, q) Maintainability analysis to review and update maintenance concepts, tasks, and technical criteria, r) Safety engineering to include reviews of operational procedures and proposed engineering changes as well as to conduct investigations and proposed corrective actions. 4.7 Configuration Management -- The contractor shall develop and implement, as tasked, configuration management (CM) program plans and procedures to assure positive configuration control and status accounting of all system items; hardware and software, military and COTS items. a) Develop/revise CM plans and procedures for assigned hardware and software items, b) Establish and maintain a definitive data base for control and status accounting of configuration items; identify and maintain the original configuration of requirements documents, design documents, software, firmware, and related documents, c) Establish procedures, maintain records, and regulate and track the flow of proposed changes to involved organizational elements, d) Provide a complete audit trail of upgrades/changes, implementation decisions, and design modifications, e) Maintain configuration baselines for assigned items addressing installation of hardware and distribution of software to appropriate platforms, f) Participate in Functional Configuration Audits (FCAs) and Physical Configuration Audits (PCAs) to assure all records reflect actual configuration as specified by the baseline documentation, g) Participate in hardware and software Configuration Control Boards. 4.8 Data Management -- The contractor shall provide services to support the following: a) Data repository and technical library operation and maintenance, b) Technical accuracy of engineering and installation drawings c) Provide drafting support s Posted 10/14/98 (W-SN262103). (0287)

Loren Data Corp. http://www.ld.com (SYN# 0069 19981016\R-0010.SOL)