Industry Day Q A 10.2.2014.pdf

Date: 10/2/14 Event: FAA Industry Day Outreach TFDM & TFMS

TFDM Questions/Comments:

1. Question: Is there a formal Concept of Operations document?

Answer: The formal TFDM ConOps was posted with RFI #2, DTFAWA-13-R-00013

2. Question: Is there any consideration on leveraging FCS cloud services?

Answer: The cloud is currently not an option for the TFDM program. It will be re-assessed for FID. The Draft SIR package has it as a constraint not to use cloud.

3. Question: Would a joint partnership with DoD affect the maximum implementation of 12 sites per year?

Answer: Yes, the 12 sites per year is an FAA constraint. The DoD site deployments would be in addition to those for the FAA.

4. Question: For the TFDM TFM capabilities in the TRACON, will the TFDM contractor be allowed to make modifications to the TFMS system?

Answer: No, TFDM will exchange data with TFMS, with requirements allocated accordingly.

TFMS will have modifications to their system requirements and the TFMS contractor will be responsible for modifications to TFMS.

5. Question: Will TFDM be responsible for pre-departure substitutions?

Answer: TFDM will aid in the management of substitutions in coordination with other DSS systems.

6. Question: Would you agree that this aggregation of technology increases the complexity of technology rather than decrease, especially with other implementations occurring? Why would you not move to compete and deploy COTS capability earlier?

Answer: At the system level, there is no such thing as COTS in the FAA. In order to be able to support a system for a 20 year lifecycle programs have to meet rigorous orders for system supportability and any COTS system will have to be modified to meet the FAA system requirements and to meet the requirements of the In Service Decision (ISD) checklist.

7. Question: You mentioned AEFS being implemented. Why would more AEFS systems be implemented at this time?

Answer: AEFS will be pulled out once TFDM is implemented. Currently, we are modifying requirements in the Spec based off feedback from AEFS operational use. Tech Ops cannot maintain AEFS today, so we’re developing an interim support strategy until TFDM can replace AEFS. More AEFS systems will be implemented, primarily at new air traffic control towers, in the interim at a few sites until TFDM comes along. This is part of TFDM’s Early Implementation effort.

8. Question: Where will AEFS be implemented?

Answer: AEFS will be implemented at Cleveland, Las Vegas, San Francisco, Charlotte and possibly at the 3 New York metro towers.

9. Question: You briefed that there would be a significant delay between Contract Price Final Negotiation and the Planned FAA JRC FID and Contract Award. Would FAA consider reducing that delay and perhaps adding more time between the “One on One” discussions and the Final SIR?

Answer: No, there are internal FAA activities that must occur during that time to support the source selection and the final business case development.

10. Question: You briefed a specific number of planned sites and seemed to indicate that electronic flight strips would only be deployed to towers. If that is correct, would FAA consider deployment of EFS to TRACONs as part of this program?

Answer: No, EFS for the FAA TRACONs is not a requirement of this program.

11. Question: You briefed that FAA is deploying the FAA developed EFS (currently at Phoenix) to other airports as an interim solution to be replaced by TFDM.

a. Question: Would FAA consider posting more detail about that program (schedule, limitations, architecture, locations, etc.) and providing an opportunity for those vendors who have not seen the Phoenix system to visit and talk with controllers?

Answer: No, site visits to Phoenix for vendors will not be offered. The requirements for the Phoenix Prototype AEFS system are included in the TFDM specification.

b. Question: Could visits to the Program Team at the WJHTC be permitted, either as requested or by a scheduled Industry Forum?

Answer: Not at this time but may be considered for the future. If planned in the future, it will be scheduled via the FAACO, similar to the process used for the Industry Outreach Event.

TFMS Questions/Comments:

1. Question: How do you envision what happens between the contract award date on 11/15 and the completion of the current contract?

Answer: The government has budgeted time to allow for up to 6 months for transition;

during this time, there will be some overlap of period(s) of performance between the incumbent contract and the newly awarded contract.

2. Question: Integration of TFDM and TFMS. Is there a disconnect between these two systems? Have the requirements of both systems been considered?

Answer: TFDM and TFM programs are working together on requirements that are to be integrated. These requirements will be included and released in the respective SIRs.

3. Question: What is the status of the Performance-Based Acquisition emphasis?

Answer: The initial approach was to structure a portion of the procurement around a performance based approach, but now it is structured around requirements based procurement.