SOURCES SOUGHT
A -- METOC TACTICAL APPLICATIONS SOURCES SOUGHT
- Notice Date
- 11/14/2003
- Notice Type
- Sources Sought
- Contracting Office
- N00024 1333 Isaac Hull Avenue S.E. Washington Navy Yard, DC
- ZIP Code
- 00000
- Solicitation Number
- XXXXXXXXXX
- Point of Contact
- Jim Watts 202-781-3958
- Description
- Program Executive Office ? Integrated Warfare Systems, Advanced Systems & Technology Office in cooperation with the Operational Effects Program Office in PEO C4I is seeking sources for the design, development, integration, validation, installation and support of METOC Tactical Applications for all Navy and Marine Corps Warfare Areas using a spiral build process. Formal design and development processes ensure that the applications meet the operational requirements and the software design reflects the required system specifications. The software must be well documented using state-of-the-art software tools. METOC Tactical Application development is accomplished using C, C++ and Java software languages in an Object Oriented framework. METOC Tactical Applications use several different types of inter-process communications. The current Applications use RMI, CORBA, XML and other c ommercial standards. The legacy applications utilize Automatic Data Entry ? Inter-process Control (ADE-IPC) and are required to be updated as Software Trouble Reports (STRs) are reported and corrected. The Defense Information Infrastruction Common Operating Environment (DII-COE) used in the Global Command and Control System (GCCS) and Global Command and Control Systems ? Maritime (GCCS-M) is the high-level architecture being implemented and utilized for these Applications Meteorology and Oceanography (METOC) Tactical Applications Program. Point of Contact: Paul R. Tiedeman, Program Manager, (202) 781-1531, e-mail:tiedemanpr@navsea.navy.mil, Fax: (202) 781-4703. METOC Tactical Applications are currently in the Fleet as part of GCCS-M Version 3.1.2.1. The new METOC Tactical Applications are being developed under the Common Operating Environment (COE) Version 4.7. The s oftware segments developed under the COE architecture must be level 7 compliant. Environmental data is available through a seamless interface to the Tactical Environmental Data Server (TEDS)/Tactical Environmental Data Services (TEDServices) As part of the fielding/delivery process to the GCCS and GCCS-M host systems, there are specifications and documentation standards that must be adhered to. The Applications must be compatible with and utilize the DII COE Joint Mapping Tool Kit (JMTK), the new Commercial/Joint Mapping Tool Kit (C/JMTK) and the Polexis WebCop. In addition, the METOC Applications must be interoperable and be able to display outputs on other Mission Planning Systems such as the Joint Mission Planning System (JMPS), Portable Flight Planning System (PFPS) and C2PC. Applications are currently being delivered and deployed to the U.S. Navy, DISA and several Alli es. The detailed METOC Application architecture must be flexible enough to comply with the requirements for these implementations as well. METOC web services are being developed and will be deployed in the near future. As METOC Applications are developed, the architecture/design needs to accommodate the web services paradigm. The existing design is based on an N-Tier Architecture. It employs industry best practices with separation of the business logic, data and presentation layers allowing for greater software re-use in multiple Thick Client systems as well as web based User Facing Services (UFS) and Data Oriented Services (DOS). METOC Tactical Applications are being integrated into the Navy Enterprise Portal (NEP) and must be fully compliant with those requirements/standards to be part of the NEP. The NEP is used to integrate services throughout the Navy, and to prov ide services for enterprise portal participants such as quality assurance, data standardization, metadata management and interoperability. Exercise support is a key requirement for the overall METOC Data Applications program. System Engineers are required to support METOC Applications at shore-based and shipboard locations. In addition to U.S. exercises, METOC Data Applications engineers participate in a variety of Joint and Allied exercises Period of Performance The period of performance is expected to be 60 months (12 months basic with four 12 month options). Response to Sources Sought Interested potential sources should respond by indicating their ability to meet the following screening criteria: a) Experience/Expertise and understanding of all Navy and Marine Corps Warfare Areas and experience/expertise in oceanography and meteorology and its effect on w ar-fighting operations/combat systems b) Prior experience in the design/development and support of JAVA, Object Oriented, hardware/operating system independent METOC Tactical Applications/Tactical Decision Aids c) Experience in developing and fielding COE 4.7 and GCCS/GCCS-M 4.X/3.X applications d) Web-Services (User Facing Services and Data Oriented Services) development experience e) Knowledge of and development experience with JMTK, C/JMTK and Polexis WebCop charts f) U.S. and Allied exercise and Fleet support experience g) Foreign Military Sales experience including experience with Allied architectures/Command and Control Systems (e.g. MCCIS) h) Ability to obtain a SECRET facility/personnel clearances and TOP SECRET clearance for at least one or two individuals. Interested potential sources should provide their responses to the above screening criteria, in writing , no later than 5:00 pm EST, 8 December 2003 and should not exceed 10, one-sided, 8.5 x 11 inch pages, with font no smaller than ?courier new? size 10. Electronic submittals are acceptable. Responses should be sent to: Naval Sea systems Command Attn: NAVSEA 02632 (J. Watts) 1333 Isaac Hull Avenue, SE Stop 2050 Washington Navy Yard, DC 20376-2050 wattsjr@navsea.navy.mil Response should be in MS Word 98 or higher format. A source's capability package should clearly indicate the source's intent to be either a prime contractor or subcontractor. Sources interested only in subcontractor opportunities should briefly identify relevant experience and expertise in a two-page vice 10 page response. Sources should also indicate whether they are a large business, small business, or a small disadvantaged business. Sources are also requested to identify any on-going Government contract vehicles they may have for the same or similar work. Please include the name and number of the on-going contract, contract scope, contract type, period of performance, contract deliverables, dollar thresholds and limitations, the issuing Government agency, and the name and telephone number of the Contracting Officer. This synopsis is for information and planning purposes only and does not constitute a Request for Proposal (RFP) nor does its issuance restrict the Government as to the ultimate acquisition approach. The Government will not reimburse the contractor for any cost associated with preparing or submitting a response to this notice. THIS IS NOT A SOLICITATION.
- Record
- SN00470453-W 20031116/031114212424 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |