Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF NOVEMBER 10, 2016 FBO #5466
SPECIAL NOTICE

20 -- Request for Information for Electrical Interface Standards for Naval DC Power Systems - Attachments

Notice Date
11/8/2016
 
Notice Type
Special Notice
 
NAICS
335999 — All Other Miscellaneous Electrical Equipment and Component Manufacturing
 
Contracting Office
Department of the Navy, Naval Sea Systems Command, NAVSEA HQ, SEA 02, 1333 Isaac Hull Avenue SE, Washington Navy Yard, District of Columbia, 20376, United States
 
ZIP Code
20376
 
Solicitation Number
N00024-17-R-4202
 
Archive Date
12/31/2016
 
Point of Contact
Emily J. Stepien, Phone: 2027815047, Joseph Tannenbaum, Phone: 202-781-2629
 
E-Mail Address
emily.stepien@navy.mil, joseph.tannenbaum@navy.mil
(emily.stepien@navy.mil, joseph.tannenbaum@navy.mil)
 
Small Business Set-Aside
N/A
 
Description
2016011 MIL-STD-1399-MVDC-a 2016011 MIL- STD-1399-LVDC-a The Road to MVDC 2015319 ASNE ISS Doerry-Amy Synopsis: The Naval Sea Systems Command is hereby issuing a Request for Information (RFI) on behalf of SEA 05 (Naval Systems Engineering Directorate) and PMS 320 (the Electric Ships Office) seeking information from electrical equipment manufacturers, systems integrators, academia, and other interested parties to support the development of electrical interface standards for DC power systems applicable to naval warships. The Navy has developed two draft standards and desires recommendations addressing specific issues within the draft standards as well as more general comments as appropriate. The two draft standards are referred to in this RFI as MIL-STD-1399-LVDC for 375 volt direct current (VDC), 650 VDC, and 1000 VDC interfaces; and as MIL-STD-1399-MVDC for 6,000 VDC, 12,000 VDC and 18,000 VDC interfaces. These draft standards are available as attachments to this RFI. The development of these interface standards is in direct support of the Naval Power and Energy Systems Technology Development Roadmap (available from http://www.navsea.navy.mil ). MIL-STD-1399-LVDC and MIL-STD-1399-MVDC will have different designations when issued. Initially, the two documents will likely be issued as Project-Peculiar Documents (PPDs) for specific acquisitions including procurements for a potential Integrated Power and Energy System (IPES) Advanced Development Model (ADM). Once lessons are learned from these acquisitions and are incorporated, the two documents are intended to be new sections of MIL-STD-1399. The MVDC and LVDC interface standards are intended for future shipboard power systems similar to the power system described in " The Road to MVDC," Presented at ASNE Intelligent Ships Symposium 2015, Philadelphia PA, May-20-21, 2015, attached to this announcement The LVDC interface standard is also intended for back-fit and modified repeat designs through the implementation of the Energy Magazine as described in the Naval Power and Energy Systems Technology Development Roadmap. RESPONSES: While feedback on any aspect of the two standards is desired, responses to the following issues are of particular interest to the Navy: 1. The two draft standards include a number of "TBD"s (To be determined). The values provided alongside the TBD are either a single value or a range of values that the Navy is considering for the particular parameter. Recommendations and rationale for specifying a value for the parameter are desired. (Recommendations need not be limited to the values shown). 2. A number of the parameters and values depend on the eventually chosen grounding scheme for each of the interfaces. Recommendations and rationale for the inclusion or deletion of specific parameters, and the associated value, are desired for various possible grounding schemes. 3. A number of the parameters reflect a balance in increasing cost and complexity of sources vs cost and complexity of loads. Recommendations and rationale for parameters and parameter values are desired based on this balance of impact on sources and loads. 4. The voltage spike waveform requirements are not well understood. Insight into the nature, magnitude, and frequency of spikes on DC distribution systems is sought. Insight on the appropriateness of the proposed requirements is desired. Is the cited pulse waveform appropriate? 5. Only a framework for supporting pulse loads is provided. Recommendations for how the control negotiations should be performed are desired. Also desire feedback on the choice of the pulse load parameters. (i.e. should pulse limits be described in terms of MW/s or A/ms?) 6. The load voltage interruption tolerance time is a balance between the cost and capabilities of fault detection, localization, and isolation within the distribution system, and the holdup time designed into individual loads. Perspective on this trade-off, recommendation for a specific value, and the rationale are desired. 7. An assessment of the practicality, cost, safety, effectiveness, and appropriateness of the different verification methods is desired. Can the intent of these verification methods be captured in less costly methods? Would the acquisition of necessary test equipment be an undue burden on industry? 8. Stability is not currently addressed. Recommendations for parameters (and values) for the interfaces to ensure small-signal and large-signal stability are desired. 9. Recommendations for adding requirements that are missing from the standards are desired. 10. Recommendations for deleting requirements from the standards are desired. 11. The draft standards include requirements for both sources and loads, primarily because certain equipment may at times behave as sources, and at other times as loads (e.g. energy storage, and regenerative loads). MIL-STD-1399-300 only provides the requirements for loads. What are your thoughts on the need to include requirements for sources? 12. Tables 3 and 4 include both "independent" (such as voltage parameters for loads) and "dependent" parameters (such as current parameters for loads). Would you prefer to see these independent and dependent variables listed in separate tables? 13. The current ripple frequency limits as presented are based on MIL-STD-461 CE 101 limits. These limits may prove over-restrictive for pulse load applications. Are frequency limits necessary? If so, should the CE 101 limits be relaxed? How should the ripple frequency limits, if provided, be made consistent with the ability to meet other EMI requirements? 14. Should there be a sentence somewhere describing what Type 2 is (i.e. energy storage floating bus) or is it intended that it is understood based on the values in the table. 15. Should there be a requirement for loads to not provide reverse current into the DC Bus, particularly during faults? 16. Should different parameters from those provided be used? If so, propose the parameter definitions and recommended values for the parameters (i.e. specify line to ground capacitance instead of the current in the capacitor) Responses and comments are requested by 4:00 pm (EST), on December 15, 2016. However, submissions will be accepted after this date, but feedback may not be as timely or contribute to NAVSEA's standards development. Information should be e-mailed to Joseph Tannenbaum at joseph.tannenbaum@navy.mil or mailed to Naval Sea Systems Command, Attn: Joseph Tannenbaum, PMS 320, 1333 Isaac Hull Avenue SE, Washington Navy Yard, DC 20376 and labeled with the solicitation number and Electrical Interface Standards for Naval DC Power Systems RFI. Questions can be submitted electronically to norbert.doerry@navy.mil (with copy to joseph.tannenbaum@navy.mil) or by phone at (202) 781-2520. A clean format version of this RFI is available upon request to the points of contact noted above. Responses should indicate enough detail so that potential Navy interest can be assessed. Responses are requested to be provided electronically and acceptable formats include Adobe PDF, Microsoft Word, Microsoft Excel and Microsoft PowerPoint files. The information provided will assist NAVSEA in developing the two interfaces standards for inclusion in future developments, procurements and acquisitions. As the two standards will be publically available once published, the comments provided should not contain proprietary information. However, if some of the background on the comments provided is considered proprietary to the respondent, that portion shall be segregated and labeled as such and will be treated as Business Sensitive and will not be shared outside of Government activities and agencies without the permission of the provider. It is noted that membership of the extended Navy team includes Government support contractors and no information will be shared with non-Government employees without express permission from the source of the information. All submissions become Government property and will not be returned. This RFI in no way binds the Government to offer contracts to responding companies. Defense and commercial contractors, including small businesses, veteran-owned businesses, service-disabled veteran-owned business, HUBZone small businesses, and women-owned businesses are encouraged to participate. Academia and other research organizations are also encouraged to participate. This RFI is the initiation of market research under Part 10 of the Federal Acquisition Regulation (FAR), and is not a Request for Proposals (RFP). All information shall be provided free of charge to the Government. NAVSEA may request further information regarding the capabilities of respondents to meet the requirements and may request a presentation and/or a site visit as deemed necessary. Follow-up questions may be asked of responders for clarification, but this will not indicate a selection or preference. Responders are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI. Not responding to this RFI does not preclude participation in any future RFP or other solicitation, if any is issued. Classified material will not be accepted. Contracting Office Address: N00024 NAVAL SEA SYSTEMS COMMAND, DC 1333 Isaac Hull Avenue S.E. Washington Navy Yard, DC Point(s) of Contact: Mr. Joseph Tannenbaum at joseph.tannenbaum@navy.mil 202-781-2629 Dr. Norbert Doerry at norbert.doerry@navy.mil 202- 781-2520
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVSEA/NAVSEAHQ/N00024-17-R-4202/listing.html)
 
Record
SN04323946-W 20161110/161108235250-daff42b3b70e03b98da84ed498e7e76a (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.