MODIFICATION
70 -- Training Stimulator/Simulator System (TSSS) - Amendment 1
- Notice Date
- 5/3/2016
- Notice Type
- Modification/Amendment
- NAICS
- 334111
— Electronic Computer Manufacturing
- Contracting Office
- Department of the Navy, Naval Sea Systems Command, NSWC Dahlgren Division, 17362 Dahlgren Road, Suite 157, Dahlgren, Virginia, 22448-5100, United States
- ZIP Code
- 22448-5100
- Solicitation Number
- N0017816Q3023
- Response Due
- 5/2/2016
- Archive Date
- 6/15/2016
- Point of Contact
- Charles Thompson, Phone: 540-653-7094
- E-Mail Address
-
charles.e.thompson@navy.mil
(charles.e.thompson@navy.mil)
- Small Business Set-Aside
- N/A
- Description
- This Sources Sought/RFI is being posted to both the Federal Business Opportunities (FBO) page located at http://www.fbo.gov and the Navy Electronic Commerce on Line (NECO) site located at http://www.neco.navy.mil. While it is understood that FBO is a single point of entry for posting of synopsis and solicitations to the internet, NECO is the alternative in case FBO is unavailable. Please feel free to use either site to access the information posted by the Navy Sea Systems Command. Responses must be submitted in writing to the Contracting Officer, Charles Thompson, via email at charles.e.thompson@navy.mil no later than the date and time noted above. Email should reference Sources Sought/RFI N00178-16-Q-3023 in the subject line. Amendment 0001 is issued to extend the closing date and provide the following questions and answers: Question 1. Regarding the TSSS RFI: we have reviewed the list of top level requirements that focus on replacement of fielded units to remedy critical obsolescence issues. We note that capabilities like: live-virtual bridged voice communications, networked voice communications and simulated tactical radio environment are not included in the list. Can you please confirm whether or not subsystems related to the referenced capabilities are on the list of things that the Navy is considering for modernization? This RFI is only for the Simulation and/or Stimulation of specific RADAR systems. The Navy is considering the modernization of live-virtual bridged voice communications, networked voice communications and simulated tactical radio environment, but those efforts are not applicable to this RFI. Question 2. Could a revision to the RFI be released that numbers the requirements instead of the use of bullets? The RFI will stay as is. Question 3. The last requirement states "TSSS-R shall be capable of interfacing to and being controlled by the the Radar IFF Federation governed by Weapon Specification DN 15-6" a. Where can we find the Weapon Specification DN 15-6? Attached. b. Table 1 does not list IFF. Should IFF be listed or mentioned in the responses? "IFF Simulator SM-909(P)/U" should be added to Table 1. Question 4. The requirement "Radar video generation enabling accurate representation on combat systems" indicates a requirement for Video Generation. However, Table 1 systems does not list Video Generator as a system of Interest. Should the TSSS-R response include the video generation capability along with RF and IF levels to systems in Table 1? This RFI seeks innovative solutions to the RADAR training problem. Video Generation is a possible avenue of meeting the training need. The end goal is to present the sailor with a valid training picture; the technical solution is at the discretion of the design agent. Question 5. Will the Government provide an interface specification for the TSSS stimulator to the combat system, prior to the due date for the Sources Sought responses? "TSSS-R shall be capable of interfacing to and being controlled by the the Radar IFF Federation governed by Weapon Specification DN 15-6". Attached. Question 6. Will the Government provide an interface specification for the TSSS simulation software to the combat system software, in the event actual signal emulation is not required and the training scenarios can be wholly implemented in software, prior to the due date for the Sources Sought responses? This will not be provided prior to the Sources Sought due date. That interface is not currently established due to the current method of stimulation. If simulation is selected as the engineering avenue for TSSS-R that interface will be a product of the developmental process. Question 7. Will the Government provide a functional specification detailing the scenarios that TSSS will be required to represent, prior to the due date for the Sources Sought responses? No. Use case analysis will be a product of the developmental process. The scope of this RFI does not require a functional specification. Formal TSSS-R system requirements will be created and validated to reflect current fleet training needs prior to an RFP. THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to identify sources that can provide The technical acumen to fully design and realize a replacement for the TSSS as identified above. The information provided in the RFI is subject to change and is not binding on the Government. The Navy has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and as such will not be returned.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVSEA/N00178/N0017816Q3023/listing.html)
- Record
- SN04104266-W 20160505/160503235316-bafb0d1b237be8e1d2133c167c01ee36 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |