Industry Day Q&A_dtd 22 March 2019.pdf

PDF 66 KB Posted

Attached to
SATCOM CB ISEA Support
Solicitation number
N65236-18-R-0081
Issued by

About this file

This document contains the questions and answers from an industry day held to discuss a forthcoming solicitation for SATCOM CB-ISEA Support. The Navy seeks to award a single contract to provide in-service engineering agent support for satellite communications systems across the SPAWAR enterprise in support of PEO C4I PMW/A 170 Office and Fleet Readiness Directorate FRD 100. Services include technical sustainment, engineering support, and modernization support. The period of performance is five years with an estimated minimum of 40 FTEs required annually. Incumbents included Centurum, Parsons, GDIT, and SRC under various prior contracts and task orders. The final RFP will incorporate revisions to page limits, clarify that controlled unclassified information can be stored on contractor systems, and provide a pricing model and ODC estimates. The Navy intends to evaluate based on technical approach, past performance, and price. The response deadline is 1 June 2018.

View the file

Other files

Show all 21

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

March 18, 2019

SATCOM CB-ISEA – Industry Day Q&A

N65236-18-R-0081

NOTE: Unless specifically noted within the individual question, the responses provided below are for LANT’s SATCOM CB-ISEA requirement and may not be applicable to PAC’s SATCOM CB-ISEA requirement. These answers are provided based on the knowledge and planning of this procurement to date and the Government’s definitive position will be provided on the final solicitation.

Question Answer 1 Is this a new requirement? If not, who is the incumbent? Can you provide contract/task order numbers?

This is a new requirement. However, portions of this requirement were performed on the previous contract/task orders:

• N00178-14-D-7658-N6523618F3106

(MIL & COM SATCOM): Centurum

• N65236-14-D-4925-0002/0003 (NMT

Support): Centurum

• N65236-14-D-4933-

0003/0004/0005/0006/0007/

N6523617F3136 (SCN SATCOM &

CBSP): SMS/Parsons

• N00178-04-D-4012-N6523618F3107

(GBS): GDIT

• N65236-13-D-4869-0008 (WBSOTM):

SRC

2 On Page L-7 of the Draft RFP, Factor B (Technical Understanding) is limited to a total of ten (10) pages. That number of pages will not allow a detailed of the problem and proposed solution to all of the requirements described in the existing three (3) subfactors.

Will the Government allow up to 20 pages total for the Factor B response?

The Government will revise the page limitations as follows (13 pages total):

• Subfactor 1 (Tech Sustainment): 10 pgs

• Subfactor 2 (Eng Support): 2 pgs

• Subfactor 3 (Modernization Support): 1 pg

3 On Page 35 of the PWS, Section 8.5 states that the contractor shall not process, store, and/or transmit Government CUI on any asset owned by or for the contractor. However, the rest of section 8.5 explains how the contractor will protect CUI and CDI. It is expected that if the CUI is not allowed on any contractor system then DFARS clauses 252.204-7012 and CUI controls from the 52.000 Volume 4 manual would not apply. Can you clarify if CUI or CDI will be allowed on contractor systems? If it is not allowed can the 252-7012 clause and the other requirements from section 8.5.1.1 – 8-5.2.3 be removed?

Paragraph 8.5 will be revised to state, “The contractor shall process, store, and/or transmit Government controlled unclassified information (CUI) on information systems…..”

252.204-7012 is still applicable.

4 Is the proposed fee to be a fee percentage or per hour?

Both. Contractors will propose a fee percentage.

That percentage will be utilized to calculate a fee per hour for the purposes of invoicing.

5 What kind of installs and skill set required for

LANT?

There is no requirement to install an entire system for hardware. Software upgrades and mechanical and software IA’s are some of the software installs that are required.

6 Will an LOE be provided? Yes. This will be provided on the pricing model.

7 Has the Government considered unique facility requirements to support equipment repairs/tech refreshes? Are these detailed in PWS? (i.e. -power, storage, locations, high bay areas, etc.?

Yes, the Government has considered these requirements. PWS paragraph 2.2 includes general contractor facility requirements. Any specific contractor facility requirements will be identified at the TO level.

8 Does PAC have a similar strategy? Yes, PAC plans to award a single award contract around the same dollar value. Their evaluation criteria is still under development.

9 Is there a facility requirement for integration? It is anticipated integration will be done at the Government facility. However, overflow or surge requirements may need to be done at the contractor facility.

10 Is this in SeaPort? No 11 Will the addition of subcontractors after award be allowed?

Yes, in accordance with 52.244-2. Tripwires may apply.

12 The current contract has a requirement for Secret safeguarding. Is TS for a SCIF?

No SCIF required.

13 Will this include any terrestrial work? Yes. It is anticipated that there will be terrestrial work/requirements to connect between commercial and DoD/Navy Shore sites (see PWS paragraphs under 3.5.4).

14 Are the RMC’s customers? Yes 15 Will a TDL process be included? Yes 16 For past performance references, is the intent for the threshold to be $10M for each reference or a cumulative invoiced total of $10M?

This section will be revised. The intent is to have a cumulative invoiced dollar threshold for all 5 references ($10M).

17 Will a draft Pricing Model be released ahead of the final RFP?

If the Government is able to prepare this attachment in advance of the final RFP, we will post on e-Commerce.

18 What is the timeframe for the PAC requirement?

PAC is expecting to release their solicitation by 2019 April 1.

19 Is there any PNT-related work under this action? Will work cover

GPNTS/PNT/NAVSSI?

GPNTS/PNT/NAVSSI efforts are not planned under this contract. However, the contractor is expected to troubleshoot beyond our demarcation to work with personnel that may be supporting those systems. The SATCOM systems listed under PWS paragraph 1.1 include “Other corresponding equipment managed by the Communications and GPS Navigation Program Office (PMW/A 170), Shore and Expeditionary

Integration Program Office (PMW 790), and the Fleet Readiness Directorate (FRD) 100.”

20 Is there no SCI portion for this requirement?

Why do TS and not include SCI?

SCI access approval is a timely process and is not necessary for this requirement. Any TS/SCI requirements will be done by Government personnel.

21 It is understood that on Day 1 of performance a CASREP plan is important. Other than that, what is the next highest priority on Day 1?

It is imperative that the contractor have fully-trained personnel with the proper qualifications.

22 Will there be a breakout of locations for personnel?

For the purposes of bidding, this information is included in the Pricing Model.

23 There appears to be possible surge support throughout the 5 year ordering period. Is this to be done utilizing baseline staff or will there be surge support at multiple times requiring more personnel?

The government does not dictate how the contractor supports surge requirements.

24 For cross-training personnel on more than one SATCOM system, is there a plan in place or do you want the contractor to submit a plan?

Cross training is a goal of CB-ISEA but is not part of the evaluation criteria or a requirement for proposal submission.

25 Will the contractor be training Government personnel?

Yes, possibly.

26 Is there a plan/requirement to support Diminishing manufacturing sources and material shortages (DMSMS)?”

The PWS will be revised to clarify DMSMS requirements under PWS paragraph 3.4.

27 Will work include LCS platforms? Yes, LCS-class ships have SHF systems that will be supported under this contract.

28 What is the estimated number of FTEs (not for bidding purposes)?

For the first year of performance, the estimated number of FTEs is no less than 40 people. For bidding purposes, the labor mix will be provided on the Pricing Model.

29 Will there be a draft RFP? No. A draft L & M was previously posted.

30 Will the brief be posted to e-Commerce or emailed to attendees?

The brief and all Q&As will be posted on e- Commerce.

31 Will travel/ODC totals be provided or will we need to price independently?

A plug number for ODCs (travel and material) will be provided.

32 Is diminishing manufacturing sources and material shortages (DMSMS) being added to the PWS? Would this be under Proactive Support or ILS?

This would be covered via task orders if/when needed. It usually becomes an issue during some part of a POR’s lifecycle. It would be covered under ILS.

Recommendations:

1 Consider using an incentive fee structure for CASREPS or for reducing costs by having cross trained personnel?

The Government will take this into consideration. Final CLIN structure and contract type will be included in the final solicitation.

2 Release a draft Pricing Model ahead of final RFP so industry can review for errors, inconsistencies, and ask questions prior to the final RFP release.

If the Government is able to prepare this attachment in advance of the final RFP, we will post on e-Commerce.

File details come from the government source that posted it. Updated .