Answers to ques recd 12 Feb 10_Amend 4.doc

DOC document 78 KB Posted

Attached to
Data link services Federal contract opportunity
Solicitation number
HC101310R2002
Issued by
Defense Information Systems Agency

About this file

Answers to vendor questions round 2

View the file

Other files for this federal contract opportunity

Other files attached to Data link services, newest first.
File Type Posted
HC101310R2002_AMEND 7.doc DOC document
HC101310R2002_AMEND 6.doc DOC document
HC101310R2002_AMEND 5.doc DOC document
Answers to questions_ROUND 3.doc DOC document
CLINs for Pricing_RFP_17 Feb 10_Amend 4.xls XLS spreadsheet
HC101310R2002_AMEND 4.doc DOC document
Delivery Order Usage.xls XLS spreadsheet
Answers to ques recd 22 Jan 10_Amend 3.doc DOC document
HC101310R2002_AMEND 3.doc DOC document
HC101310R2002_CONFORMED.doc DOC document
HC101310R2002_AMEND 2.doc DOC document
Aircraft Projections —
CLINs for Pricing_RFP_04 Feb 10_V2.xls XLS spreadsheet
Answers to ques recd 22 Jan 10_Amend 2.doc DOC document
RFP_13 Jan 10_Amend 1.doc DOC document
CLINs for Pricing_RFP_04 Dec 09.xls XLS spreadsheet
RFP_08 JAN 10.doc DOC document
Show all 17

On GovTribe

Work with this file on GovTribe

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

Text version

Responses to HC101310R2002 Questions Received on February 12, 2010

Page
Paragraph
Question/Comment/Request for Clarification
Response
5
ITEM 000101
Is variable rate required pricing for this proposal or can a flat rate only be acceptable pricing?
The vendor must provide pricing for all CLINs and SubCLINs. The customer is requesting a three-tier pricing structure for all data link services to include a flat rate per aircraft and flat rate for all aircraft within a single MDS per delivery order. The vendor can and is encouraged to provide additional pricing options and/or bundled services as part of their solicitation bid. (See HC101310R2002_CONFORMED.doc, page 73, Instructions for Preparation of Offers, paragraph 1)
6
ITEM 0002
In order to provide best pricing, the vendor will require to know which aircraft Model Design Series (MDS) are equipped with VHF Mode 2 and the quantity of each MDS capable of VHF Mode 2
See the Excel spreadsheet “Delivery_Order_Usage.xls” tables included as part of answers in Amend 2 on the Federal Business Opportunities website.
8
ITEM 000203
Is it necessary to provide a Kilobit rate or can a flat rate per aircraft type be acceptable?
The vendor must provide pricing for all CLINs and SubCLINs. The customer is requesting a three-tier pricing structure for all data link services to include a flat rate per aircraft and flat rate for all aircraft within a single MDS per delivery order. The vendor can and is encouraged to provide additional pricing options and/or bundled services as part of their solicitation bid. (See HC101310R2002_CONFORMED.doc, page 73, Instructions for Preparation of Offers, paragraph 1)
8
ITEM 0003
Need clarification regarding VHF DATALINK ACARS. Vendor provides VHF datalink services via SITA, ARINC, AVICOM, and other VHF networks. The datalink avionics are engineered to seek out ANY VHF signal as a priority and Vendor would like to offer the greatest VHF coverage possible by providing datalink through all the VHF networks.
The bid for VHF DATALINK ACARS needs to include pricing consideration for all VHF networks for billing and payment on a consolidated invoice per delivery order. (See HC101310R2002_CONFORMED.doc, page 84, PWS Performance Requirements paragraph 6.1.6 “Subtask 6 – Itinerant Rates”)
8
ITEM 0003
Can the customer provide the datalink equipment installed in each aircraft?
Government will not provide avionics specific equipment and configuration unless vendor can justify a need to know. (See “ Answers_to_ques_recd_22_Jan_10_Amend_3.doc”, page 6, referenced Page 89, Paragraph 13, Question/Comment/Request for Clarification and government Response)
10
ITEM 0004
Can a flat rate per event (downlink & uplink received) be acceptable and not provide Kilobit rates?
The vendor must provide pricing for all CLINs and SubCLINs. The customer is requesting a three-tier pricing structure for all data link services to include a flat rate per aircraft and flat rate for all aircraft within a single MDS per delivery order. The vendor can and is encouraged to provide additional pricing options and/or bundled services as part of their solicitation bid. (See HC101310R2002_CONFORMED.doc, page 73, Instructions for Preparation of Offers, paragraph 1)
10
ITEM 000401
Is per Kilobit counting required? Can a rate per character be used instead of Kilobit?
For the purpose of this solicitation, the government is requesting per Kilobit for pricing/cost comparisons. Once the contract is awarded, pricing may be converted to per character rates for ease of tracking and billing as long as pricing rates are not altered and the vendor secures permission from the customer through the DITCO contracting officer.
10
ITEM 000402 and 000403
Are 402 & 403 asking for the same discount?
No. The customer is requesting a three-tier pricing structure for all data link services to include:

(1) per kilobit usage rate

(2) flat rate per aircraft (high individual tail number – (e.g. C-17A, Fleet ID # 21107A) usage discount that caps the maximum charge per aircraft

(3) flat rate for all aircraft within a single MDS per delivery order - all MDS tail numbers (e.g. all C-17A aircraft) bulk fleet discount that caps the maximum charge for each MDS on a delivery order

17
ITEM 0008
Is VHF radio Air To Ground an optional service as HF is optional per amendment 2?
Yes. (See HC101310R2002_CONFORMED.doc, page 17, ITEM NO 0008)
30
ITEM 001001
Would the customer be receptive to a Voice Over IP solution if a router and an IP-PBX is installed?
Yes. The vendor can and is encouraged to provide additional pricing options and/or bundled services as part of their solicitation bid. (See HC101310R2002_CONFORMED.doc, page 73, Instructions for Preparation of Offers, paragraph 1)
34
ITEM 001004
Can the customer please clarify what Mini M Data Services are needed?
Currently, this service is not used. Added to solicitation to allow future expansion and use by other aircraft. (See HC101310R2002_CONFORMED.doc, page 34, renumbered to ITEM NO 001010)
35
ITEM 001101
Outside the U.S. how is D-ATIS being requested? i.e. ACARS, ADS/CPDLC
Via ACARS air to ground message.
35
ITEM 001101
In answers to questions Amend 3 dated Jan 10 - would the customer be willing to limit successful events for VHF only and leave satellite per request?
Yes, as long as the customer is billed only for services performed. (i.e.: If a request is sent from the aircraft air to ground, but the vendor’s ground to air response is not transmitted all the way back to the aircraft (a third party vendor does not accept or forward to an aircraft on logged into their system), the government should not be billed.)
38
ITEM 001108
In answers to questions Amend 3 dated Jan 10 it is still not clear what the difference between item 1108 & 1110. Suggest item 1108 modified to datalink text and graphical weather data and item 1110 be modified to provide text & graphical weather data (none datalink).
SubCLIN 001108 will be deleted from this RFP as a requirement. In accordance with Clause 52.215-9205-INSTRUCTIONS FOR PREPARATION OF OFFERS, 1. These instructions prescribe the format of proposals and describe the approach for the development and presentation of proposal data. They are designed to ensure the submission of information essential to the understanding and comprehensive validation of proposals. There is no intent to limit the content of the proposals. The instructions permit the inclusion of any additional data or information an offeror deems pertinent. Offerors are cautioned to follow the instructions carefully. The Government reserves the right to reject any proposal that does not substantially comply with these Proposal Preparation Instructions.
39
ITEM 001110
In answers to questions Amend 3 dated Jan 10 it is still not clear what the difference between item 1108 & 1110. Suggest item 1108 modified to datalink text and graphical weather data and item 1110 be modified to provide text & graphical weather data (none datalink).
SubCLIN 001110 will be deleted from this RFP as a requirement. In accordance with Clause 52.215-9205-INSTRUCTIONS FOR PREPARATION OF OFFERS, 1. These instructions prescribe the format of proposals and describe the approach for the development and presentation of proposal data. They are designed to ensure the submission of information essential to the understanding and comprehensive validation of proposals. There is no intent to limit the content of the proposals. The instructions permit the inclusion of any additional data or information an offeror deems pertinent. Offerors are cautioned to follow the instructions carefully. The Government reserves the right to reject any proposal that does not substantially comply with these Proposal Preparation Instructions.
CLINs_for_Pricing Spreadsheet
SLIN 001003
In SLIN 001003 – Swift Broadband Background IP Data, the Unit of Measure is listed as “Megabit”. Should it be the industry standard “Megabyte”? Inmarsat doesn’t report this information in less that Megabyte.

Yes, it should be megabyte. This change has been made to the CLIN spreadsheet and is reflected in RED.

CLINs_for_Pricing Spreadsheet
SLINs 000604, 000605 & 000606 and new SLINs 000910, 000911, 000912, 000916, 000917 & 000918
For new SLINs 000604, 000605 & 000606 and new SLINs 000910, 000911, 000912, 000916, 000917 & 000918, what is the SATCOM (Aero H+) I-4 Satellite predicted usage by MDS for the base year and the four option year?

ORT tables will likely still give preference to I-3 satellites, so usage will be minimal.

CLINs_for_Pricing Spreadsheet
SLINs 001001 through 001008
For SLINs 001001 through 001008, what is the predicted usage by MDS for the base year and the four option year?

DO 1, 2, and 29 will be zero. Pricing is for current and future DO cabin users. Provides opportunity to consolidate other contracts under a single contract vehicle.

SLIN 000103 (optionally priced), 000203, 000303, 000403, 000503 and SLINs 000903, 00906, 000909, 00912, 000915 and 000918
In SLIN 000103 (optionally priced), 000203, 000303, 000403, 000503 and SLINs 000903, 00906, 000909, 00912, 000915 and 000918, since the size of the MDSs fleets is different, is the Government requesting separate prices for each aircraft MDS type fleet? If so, will the pricing spreadsheet be modified to enable the itemized pricing by MDS type?

Or is the Government requesting one tier three price that can be applied to any MDS, and then multiplied by the MDS fleet size to obtain a maximum MDS monthly amount?

Requesting one three-price tier that can be applied to a MDS fleet to contain monthly costs (e.g. KC-135 fleet usage).

CLINs_for_Pricing Spreadsheet
All SLINS
Please clarify exactly what the government requires us to enter into each cell of the “CLINs for Pricing” spreadsheet. E.g. It appears that the cells that are not filled with green (the “white” cells), are where the government is expecting us to insert our prices and related data. If this is correct, why are there two white cell for data entry for SLIN000101 (and similar cells) when only one entry is required?

Also, it appears that the threshold values for SLINS 000102, 000103 (and similar) are to be entered into Column F, but entries into that column for the SLINs referenced, return a $ value. Does the government want a $ value in Column F for these SLINs? If so, what does that $ amount represent?

Also, there a many other white cells in column D, which would indicate that the government wants us to bid “Non-Recurring Charges” for those SLINs. Is this correct?

Pricing is to be filled in on the spreadsheet in the GREEN cells. The tier pricing (per tail and per MDS) is reflected as a Non-Recurring Charge as it will be billed once per month if that happens to be the most cost effective way to bill for the government. Any GREEN cells under Monthly Recurring Charge will be billed once per month for unlimited usage.

Reference IRD and IDD documents: Each of these documents references an “ARINC proprietary protocol” in section 1.4.4 which is used to exchange messages between the IFGR/CFE and the TACC Service Provider Node. Is the government expecting the current ACARS (TACC) Service Provider Node to be replaced by a similar capability from the offeror? If so, what commercial message exchange protocols (application and network levels) currently in use are supported by the IFGR/CFE? Please confirm that the offeror is not required to provide any elements beyond the Service Provider Node?
No. Please also refer to answers to previous questions:

Page 38, ITEM 0015 – Transition Cost, Since an incumbent’s transition costs would presumably be significantly less than a new awardee, will this CLIN be evaluated independently or in some fashion, differently?

“Yes, this CLIN will be evaluated separately as a one-time cost (not included in service pricing). The Air Force is mandating changes to our current interfaces to comply with requirements of the RFP. Therefore, all vendor solutions will require new interface transition costs.”

Page 78, Para 6.6.1.1 (5), Should there be an additional CLIN for circuit access fees? If not, under which CLIN should these fees be included?

“Depends upon the interface solution implemented (Internet VPN vs. dedicated circuit) for each delivery order customer. AMC prefers Internet VPN solution as most desirable, dedicated circuit solution as second most desirable.”

Reference PWS Paragraph 6.6.1.3, Rates for Communications Services: “The third tier in the pricing structure will automatically be applied when the delivery order total kilobit levels reach a designated threshold.” In the Pricing CLINs/SLINs, the third tier references aircraft model design series (MDS). Please clarify whether the third tier pricing is tied to delivery order or MDS. Was it intended that the CLINs/SLINs for third tier pricing be a:

a. “Flat Rate per Aircraft Model Design Series (MDS) across all delivery orders that include that MDS”. For example, in the information provided, the C-40 appears in delivery orders DO 5, 6, 7, 10, 15 and 19. Would the third tier price be a summation of usage for all C-40s under those delivery orders, to determine if the third tier volume discount threshold has been met; or

b. “Flat Rate per Aircraft Model Design Series (MDS) within a delivery order”. For example, again referencing the C-40 example above, would the third tier price be a summation of usage for only the C-40s within a given delivery order; or

c. “Flat Rate per delivery order inclusive of all Aircraft Model Designs (MDS) within the delivery order”. For example, delivery order DO 2 includes 5 MDS platforms. Would the third tier price be a summation of usage for all 5 MDS platforms within delivery order DO 2?

We respectfully request clarification as to which of these three scenarios is correct, and updated verbiage in PWS 6.6.1.3 and/or the CLINs/SLINs in the Excel spreadsheet to reflect the appropriate scenario.

Answer: b. is correct.

Wording for the next to last sentence in paragraph 6.6.1.3 is changed from:

“The third tier in the pricing structure will automatically be applied when the delivery order total kilobit levels reach a designated threshold.”

To:

“The third tier in the pricing structure will automatically be applied when the total kilobit level within a delivery order MDS reaches a designated threshold. The third tier rate will apply only to the specific delivery order and specific MDS within the delivery order that meets the third tier criteria.”

Upon contract award, can we expect new delivery orders or a transition of existing delivery orders? Do the existing delivery orders terminate at the end of the current contract period of performance 30 September 2010?
Expect transition of existing delivery orders (unless the delivery order customer elects to use another contract vehicle to satisfy their requirements).

We presented the following information regarding Swift Broadband pricing:

“Swift Broadband supports two types of DATA services: Background and Streaming. Background Internet Protocol (IP) data is priced by the megabyte (MB). Streaming IP data is priced by the minute based on the rate (8, 16, 32, 64, 128 kbps) selected. Suggest the government modify the CLIN structure to outline pricing for both types of service.”

In the updated CLIN pricing spreadsheet, SLIN 001003 is asking for a unit of issue of “Megabit”. Standard industry pricing is based on a unit of issue of “Megabyte”. SLINs 001004 – 001008, Swift Broadband Streaming Internet Protocol (IP) 8-16 kbps show units of issue of “Megabit”. The industry standard pricing is based on a unit of issue of “Minute”. Suggest the government update the pertinent base and option year pricing units of issue for Swift Broadband services accordingly.

We will change Unit of Issue for CLIN 001003 to Megabyte (reflected in RED in revised CLIN pricing spreadsheet). Change CLINs 001004-001008 from Megabit to Minute (reflected in RED on revised CLIN pricing spreadsheet).

Reference 6.6.1.1, Item 5, “Ground Services”: Since there is a separate category for “Circuit Access Fees,” should there be a separate CLIN/SLIN added to cover any associated fees based on the vendor’s proposed solution?
Please refer the previous question and response:

Page 78, Para 6.6.1.1 (5), Should there be an additional CLIN for circuit access fees? If not, under which CLIN should these fees be included?

“Depends upon the interface solution implemented (Internet VPN vs. dedicated circuit) for each delivery order customer. AMC prefers Internet VPN solution as most desirable, dedicated circuit solution as second most desirable.”

Vendor will need to recommend additional CLINs as part of the solution in their proposal.

Table Page and Paragraph column references taken from HC101310R2002_CONFORMED.doc

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