MODIFICATION
58 -- Small Airborne Networking Radio (SANR) Program, Airborne, Maritime, Fixed Station (AMF) Program Office - SANR RFI 3 24 2017
- Notice Date
- 3/24/2017
- Notice Type
- Modification/Amendment
- NAICS
- 334220
— Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing
- Contracting Office
- Department of the Army, Army Contracting Command, ACC - APG (W15P7T) Division B, 6001 COMBAT DRIVE, Aberdeen Proving Ground, Maryland, 21005-1846, United States
- ZIP Code
- 21005-1846
- Solicitation Number
- W15P7T17R0002
- Point of Contact
- Lee ALEXIS, Phone: 4438614965, Brian Bosmans, Phone: 4438614972
- E-Mail Address
-
Lee.Alexis.civ@mail.mil, Brian.c.Bosmans.civ@mail.mil
(Lee.Alexis.civ@mail.mil, Brian.c.Bosmans.civ@mail.mil)
- Small Business Set-Aside
- N/A
- Description
- ---Change 1--- The purpose of this Change (Change 1) is to (1) provide Government Responses to Industry Questions, (2) to provide a reminder regarding access to the Joint Tactical Networking Center (JTNC) Developmental Information Repository (IR) Airborne Maritime Fixed-Station (AMF) Small Airborne Networking Radio (SANR) folder, (3) to provide a Request for Information on aspects of the upcoming SANR Solicitation that have been updated since the SANR Draft RFP, and (4) to provide industry with an updated Draft SANR Performance Requirements Document (PRD), Compliance Verification Matrix (CVM) as well as Appendix T (Draft Source Selection Test Requirements) 1. Government Response to Industry Questions Government Responses to Industry Questions that were marked by the vendors as "Non-Proprietary" are attached in Attachment 1 of FedBizOpps Posting W15P7T-17-R-0002. Per FAR 15.201(f), when specific information about a proposed acquisition that would be necessary for the preparation of proposals is disclosed to one or more potential offerors, that information must be made available to the public as soon as practicable, but no later than the next general release of information, in order to avoid creating an unfair competitive advantage. Therefore, in instances where Industry Questions were either unmarked as "Proprietary" or "Non-Proprietary", or which were marked "Proprietary" but do not contain any information that would reveal an offeror's confidential business strategy, vendors will be notified that an alternative version of their Question and Answer will be posted on FedBizOpps. 2. SANR Information Repository Content Reminder The Government hereby wants to remind potential industry sources having an interest in the SANR acquisition program of the availability of SANR-related software and technical data (documentation) in the Joint Tactical Networking Center (JTNC) Developmental Information Repository (IR) AMF SANR folder. The SANR IR folder has been recently updated with the latest Performance Requirements Document (PRD), threshold waveforms and network management software and source selection test plan. The pertinent software and technical data (documentation) may be provided to each authorized vendor and their subcontractors, if applicable. In order to receive a copy of the SANR material, vendors and their subcontractors must be authorized to have access to the JTNC IR AMF SANR folder. To obtain authorization, each vendor/subcontractor must complete the request for AMF SANR access available only on the JTNC IR Registration website, https://www.public.navy.mil/jtnc/ir. Vendors are encouraged to request authorization to the AMF SANR folder as soon as possible. Access to the JTNC IR Registration website requires users to have a Public Key Infrastructure (PKI) certificate. For information on External Certification Authorities (ECA) vendors that are authorized to provide non-DoD personnel and contractors with PKI certificate services, please see the following website, http://iase.disa.mil/pki/eca/. In order to receive material stored in the IR, the requesting vendor is required to have a current DD 2345 (Military Critical Technical Data Agreement) certification. The certification is required by U.S. contractors that wish to obtain access to unclassified technical data disclosing militarily critical technology with military or space application that is under the control of, or in the possession of the U.S. Department of Defense (DoD). Information on applying for DD 2345 certification can be found on the Defense Logistics Agency (DLA) Joint Certification Program (JCP) web page located at https://public.logisticsinformationservice.dla.mil/PublicHome/jcp. Please note that the certification process can often take three to four weeks to complete. Those vendors that do not have a properly certified Military Critical Technical Data Agreement (DD Form 2345) can start that process immediately. Important Note: Contractors that were previously approved for JTNC IR AMF SANR access must reapply for access using the AMF SANR Use and Non-Disclosure Agreement found in the JTNC IR Registration website that contains the latest Solicitation No., currently W15P7T-17-R-0002. 3. SANR Information Repository Classified Data No classified information will be made available to any contractors or subcontractors via the JTNC IR website. Contractors and/or subcontractors requiring access to the JTNC IR classified artifacts for SANR source selection must first obtain access to the JTNC IR AMF SANR folder as described above, then must complete a DD Form 254 with the Government. To generate the DD Form 254, contractors must provide the Primary Company Address, Cage Code, Cognizant Security Office Location and address information to Lee Alexis at Lee.Alexis.civ@mail.mil. After Government confirmation of clearance and DD Form 254 signature, JTNC IR classified artifacts for SANR solicitation will be provided by JTNC administration on a Compact Disk (CD) or via SIPR email account. The CDs will be encrypted in order to protect the data, and will be sent to the contractor's approved address for receipt of classified information. The CD recipients will need to contact the SANR Contracting Specialist, Lee Alexis at Lee.Alexis.civ@mail.mil, in order to receive the CD's password to decrypt the content. All recipients of the classified artifact CD shall agree to return the CD as well as any/all copies of the Data contained on the CD in the vendor's possession as agreed between the vendor and the Government JTNC IR office. 4. Supportability and Maintenance subfactor clarification The Government wishes to provide clarification to industry, in regards to the Supportability and Maintenance subfactor, as previously outlined in the Small Airborne Networking Radio Draft Request for Proposals (SANR Draft RFP) W15P7T16R0002. First, it is important to note that the SANR Draft Statement of Work (SOW) Appendix 10 (page 101) that was posted under Draft RFP W15P7T16R0002 incorrectly stated the following: "The Government does not require Level III drawings, or documentation, for the production of SANR DLR items." This statement was inadvertently included in the SOW and will be removed. Next, the Government wishes to provide clarification on two aspects of the evaluation criteria for the Supportability and Maintenance subfactor of the SANR Draft RFP Sections L&M. Specifically, there is 1) an evaluation criteria related to facilitating organic sustainment of SANR hardware and software; and 2) another evaluation criteria related to facilitating competitive procurement of SANR spare and repair parts. Foremost, it is important to note that an Offeror's proposal will not be considered non-responsive to a solicitation or ineligible for contract award if the Offeror does not sell or otherwise relinquish data or software license rights (related to privately developed items, components, and processes) to the Government (with the exception of the license rights provided under DFARS 252.227-7013 and DFARS 252.227-7014) [See 10 USC 2320(a)(2)(F)]. However, strengths and weaknesses will be assigned to an Offeror's proposal related to the aforementioned evaluation criteria related to organic sustainment and competitive procurement goals, therefore it would be prudent for Offerors to consider this when drafting a proposal. In particular, the aforementioned evaluation criteria do not require that the Offeror to assign copyright ownership of technical data and software deliverables to the Government. Rather, the Government will assess whether the Offeror has provided an approach that facilitates the aforementioned organic or competitive sustainment goals, such as a specific data/software license rights approach, an alternate vendor approach (i.e., a strategy where the Offeror has developed and located alternative sources of supply and manufacture), or another strategy that facilitates the aforementioned organic sustainment or competitive procurement goals. When considering data/software license rights approaches that facilitate organic sustainment, it is important to note that even a "limited rights" license (as defined in DFARS 252.227-7013) permits the Government to "use, modify, reproduce, release, perform, display, or disclose technical data, in whole or in part, within the Government" (with the exception of using technical data for manufacture) and disclose to covered Government support contractors "in performance of a covered Government support contract for use, modification, reproduction, performance, display, or release or disclosure" [See DFARS 252.227-7013(a)(14)]. Accordingly, organic sustainment of SANR hardware may be facilitated with a "limited rights" license to technical data deliverables necessary to facilitate organic sustainment. However, under a "Restricted Rights" license for software deliverables (which were developed exclusively at private expense), the Government may only "use a computer program with one computer at one time. The program may not be accessed by more than one terminal or central processing unit or time shared unless otherwise permitted by this contract" [See DFARS 252.227-7014(a)(15)]. These limitations on the number of copies within the Government may inhibit organic sustainment of SANR software (from a logistics standpoint). In order to address this organic sustainment concern, an Offeror may, for example, choose to offer the Government the use of additional copies of the software within the Government and for covered Government support contractors. However, this is merely an example; as discussed, Offerors may address this subfactor in a number of ways. Lastly, depending on the license terms, both non-commercial and commercial software and hardware may facilitate the aforementioned organic sustainment or competitive procurement goals. Thus, this solicitation and evaluation criteria does not dissuade the use of commercial software and hardware components. Furthermore, this solicitation does not require Offerors to refrain from offering to use, or from using, items, components, or processes that were developed at private expense [See 10 USC 2320(a)(2)(F)]. However, if the Offeror is aware of any license restrictions for non-commercial or commercial technical data or software deliverables that will impair the aforementioned organic sustainment or competitive procurement goals, the Offeror shall identify and explain the impact of these restrictions on the aforementioned organic sustainment or competitive procurement goals in the Offeror's proposal. An update to the SANR Draft RFP Supportability and Maintenance subfactor is attached as part of this FedBizOpps posting, along with a Request for Information (RFI), comprised of the following questions listed below: a. In regards to software supportability and maintenance, it is currently envisioned that a Center of Industrial and Technical Excellence (CITE) designation will be obtained by the US Army Communications-Electronics Command Software Engineering Center (CECOM SEC), so that CECOM SEC can maintain and sustain SANR software and so that Tobyhanna Army Depot will provide logistics and sustainment support for hardware aspects of SANR. Based on the new information in the Draft SANR RFP Supportability and Maintenance subfactor contained in this RFI, what sustainment strategy approach do you envision, in order for software to be ultimately be maintained and sustained by CECOM SEC, and for Tobyhanna Army Depot to be able to maintain, sustain, and competitively procure spare and repair parts? b. Given the additional detail in the SANR Draft RFP Supportability & Maintenance Subfactor that is posted in this RFI, are there any additional priced or not-separately-priced CDRLs, and any additional CLINs for items including (but not limited to) training, support services, data, software, or rights; that would be needed in order for the Government to be able to implement any aspect of the Offferor's proposed Supportability and Maintenance strategy on a contract/order at any time during a 5-year base and 5-year-option period of an Indefinite Delivery / Indefinite Quantity (ID/IQ) contract? c. In order to prevent disruption of the Government's ability to support and maintain SANR in the event a Contractor or Subcontractor/Supplier goes out of business, or in the event a manufacturer or supplier deems some components obsolete, the Government is exploring the idea of having the Offeror propose to frequently input data/software/plans etc., into an Escrow Account as part of their sustainment strategy. Is this a feasible solution in order to mitigate risks to Government sustainment of SANR, in the event a company or their supplier goes out of business or deems a hardware/software component obsolete? If this solution is feasible, what is the best way to have it executed on a 5-year base and 5-year option period of an ID/IQ contract? As a result of this additional information, if vendors wish to provide additional comments/feedback to the Government Regarding the SANR Draft RFP Supportability and Maintenance subfactor, please submit a response via email using the attached comment matrix to the Contract Specialist (email: Lee.Alexis.civ@mail.mil) by 5pm Eastern Time 24 April 2017. If a vendor's feedback/comment relates to proprietary information, the vendor shall place the feedback/comment on the "Proprietary" tab of the SANR RFI Comment Matrix. With the comment, the vendor shall submit a statement explaining why the comment is proprietary. The updated SANR PRD version 2.6, and its accompanying Compliance Verification Matrix (CVM), as well as Appendix T (Draft Source Selection Test Requirements) are available via email request to interested sources that intend to compete as a Prime Contractor or a Subcontractor on a future procurement for SANR. Please submit requests for the above documents via email to Contract Specialist Lee Alexis at Lee.Alexis.civ@mail.mil and Contract Specialist Gregg Martin at Gregg.G.Martin.civ@mail.mil In the request email, vendors shall provide responses to the following questions (1) What is your company's intended use of the SANR PRD? and (2) How does your company intend to compete on a future SANR procurement (i.e. Prime Contractor or Subcontractor)? These documents are FOR OFFICIAL USE ONLY and shall not be further distributed without express written permission from the Contracting Officer, Brian Bosmans at Brian.C.Bosmans.civ@mail.mil 5. Request Industry feedback on the following questions: a. Please review updates to the following requirements: SANR-3793, SANR-3794, SANR-3797, SANR-3857, SANR-3858, SANR-3859, SANR-3860, SANR-3861, SANR-3790, and SANR-3792. • Would your SANR offering be capable of meeting these requirements by first hardware delivery? If not, please explain the technical reasons your offering won't be able to meet the requirement. b. SANR Warranty Coverage Background: It is envisioned that the SANR radio system may be stored for an extended period of time prior to SANR being integrated and completely installed into an aircraft. There is also a possibility that once the SANR radio is installed into an aircraft, the aircraft and/or SANR radio may not be operational often until the aircraft is fielded to a gaining unit. 1: Is it possible that the vendor provide from the time of Government acceptance, a 3 year failure free warranty, IAW AR 700-139 Army Warranty Program in lieu of a 3-year manufacturer's defect warranty IAW AR 700-139, at no additional cost to the price of the radio? This warranty shall include repair of fielded SANR LRUs that experience failures due to "fair wear and tear" during government test & integration events and/or normal operation. 2: Referring to the background, would it be possible for your SANR offering to have a warranty length that is based on the number of hours the SANR radio is operational in order to reduce the possibility of a warranty lapsing from the time of Government acceptance to the end of a warranty agreement (i.e. instead of warranty based on years) 3: In reference to #2 above, would the offeror also provide a detailed explanation as to how the number of SANR operational hours (usage rates) could be tracked and viewed at the field level? *For your response to #3 above, refer to this spreadsheet for a complete list of Army approved Test Measurement and Diagnostics Equipment (TMDE) that is utilized at the field level for maintenance: (See Attachment "TMDE Preferred Items List 18 Jan 17") c. Integrated Data Environment (IDE) • Is the offeror currently utilizing the IDE known as Windchill for deliverable development and submission of any and/or all contract deliverables and data? This notice is issued solely for information and planning purposes. It does not constitute an RFP or a promise to issue an RFP in the future. This notice does not commit the Government to contract for any supply or service whatsoever. Further, the Government is not at this time seeking proposals and will not accept unsolicited proposals. Respondents are advised that the Government will not pay for any information or administrative costs incurred in responding to this notice; all costs associated with responding to this notice will be solely at the interested parties' expense. Not responding to this notice does not preclude participation in any future RFP, if issued. If an RFP is released, it will be synopsized on the Federal Business Opportunities (FedBizOpps) website. It is the responsibility of the potential responder to monitor this site for additional information pertaining to this requirement. All information provided within this announcement is subject to change. Vendors interested in the SANR procurement are advised to monitor the Federal Business Opportunities (FBO) website at http://www.fbo.gov for additional updated information about the SANR program.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/9a5f45eba1a5e2c245f967519da1d8f6)
- Record
- SN04446703-W 20170326/170324234237-9a5f45eba1a5e2c245f967519da1d8f6 (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 |