1 / 12

TIM Follow Up

TIM Follow Up. Steering Committee July 23, 2009. TIM Follow Up. Learned: FAA is less interested in process than outcome FAA wants the broadest international industry input, and indication of level of consensus or divergent opinion

belicia
Télécharger la présentation

TIM Follow Up

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TIM Follow Up Steering Committee July 23, 2009

  2. TIM Follow Up • Learned: • FAA is less interested in process than outcome • FAA wants the broadest international industry input, and indication of level of consensus or divergent opinion • FAA does not currently want a tutorial on NCOIC tools/processes. It is our job to illustrate their value through internal execution • FAA is looking for affirmation of EA approach, or rationale for change needed • Response to FAA will be delivered in language and format meaningful to them, rather than in NCOIC lexicon terminology • FAA expectation is that domain expertise will accompany netcentric expertise in deliverables • How will we get a product to FAA by mid August/Early Sept? • Invited review process, similar to recent NAVAIR exercise, leading to first task order • Broad NCOIC announcement, with invitation to join Aviation IPT during the review • Provide preliminary draft results to JW by 8/17, with updated draft materials delivered during the week of 9/14 (red diamonds) • Issue first task order as soon as possible, supporting rationale for purpose of Invited Review • Formal Review of deliverable may take place if it serves the NCOIC roadmap and if it coincides with FAA desires • What is the deliverable for the Invited Review? • Review of select EA documents for 2025 “To Be” and 2018 interim states defined for NextGen. The goal is to determine whether the FAA approach contains all necessary and sufficient attributes to achieve a netcentric ecosystem. • Next steps to deconstruct the task • Next steps to finalize internal processes for general bidding (See Next Page)

  3. Aug/Sept Task • Simultaneous to pre-task order invited review described on previous page: • Regular updates on progress and policy to TC and TT • This Wednesday: Update from last week and explanation of operational constructs • Complete all-member individual contact, informing of OTA opportunity • Post Participation agreement for member reference

  4. Prioritization of Tasks • SV-1 (“Good visual aid for difficult discussions”) • Comments will not be completely netcentric – domain expertise required as well • Wants industry feedback on which should be “black” and “blue” • Surveillance for separation (flight critical) will not be on SWIM, but surveillance info feeding to TFM will appear • All legacy systems migrated by 2025 • Voice & data to remain segregated • Roadmaps being mapped to this now – questions are arising • No current collaboration with DISA –JW expressed interest • Wants more info to aid data/network/performance discussions • Metric: 5 hrs work/element of view • Utilize key decision points • SV-2 • Get FTI briefing from Harris • We can mature needlines-operational activities • Breakdown mirrors Comms procurement • Still need some material that is SSI (May need to steer away from IA in first member review) • Need held with Hazard Assessment on the enterprise level • 5 X 5 chart: need fault propagation analysis & containment zones analysis for redundant paths • Aeronautical Info view needs study – not enough governance

  5. Prioritization of Tasks • SV-4 • Did not leverage GEI work • No core services currently shared with other agencies – comment on this • DHS and DoD sensors currently aligned, but diverging with new acquisitions • Want collective knowledge for implementation. What parts of current programs need to change? • Wants indudstry’s help with evolution & transition plan • SOA best practices helped generate SV-4 Who were they talking to? • Get FAA color coded versions of this view—Jim Eck, FTI, ENU: Talk to SIPS • Not perfect-still arguing about naming of services: Not our task • Check with other agencies on core services definitions • OV-3 (No graphic – information needs of nodes. Needlines on OV-2) • Construct for unintended user (DoD) likely not to work in FAA-must be explicit in scope. Needs pre negotiation-not dynamic • Recommendations should include more info on how to evolve to netcentricity • Can use our support on integrated surveillance w/JPDO. Get Ginger’s input. • Are there other nodes in OV-3 beyond those in OV-2?

  6. Prioritization of Tasks • OV-6 • Review scenarios for completeness • Manage daily allocation • Where is terminal? Does it merge with en route? • Interoperability does not assure operational effectiveness • OV-7 • Governance needs maturity • Eurocontrol using AIX-M v.5 • SV-7 • Do we need this level of granularity? • TV-1 (Hybrid w/TV-2) • Can help with FDO convergence of EUROCAE/ translation into an RTCA standard • New weather standards will be required to move to global standard

  7. Actions/Questions • Get Jesse’s slides from yesterday’s meeting • Are Jesse/Jay aligned for ROI? What is the role of NCOIC with JPDO? • Get CD/web access to EA artifacts/source file • Other OTAs: Embry Riddle and ?? • Who runs new Weather Group? ATO-W acquisition • Benn Deens, automation; • Format for deliverables? • Use FAA terminology • Posted in pdf, graphic markups w/ supporting narrative • Get SV-1 To Be document • Get Harris to do FTI Briefing. To Whom? • How do we provide the specific technical detail desired by FAA without mucking around in proprietary member information?

  8. Infrastructure roadmaps for SV-1 • Aircraft (avionics) • Air-ground – derived from Aircraft & Automation • Airspace & Procedures • Automation • Communication • Enterprise Services • Facility • Information Systems Security • Navigation • HIS • Safety • Surveillance • Weather NCOIC will not Review items in blue

  9. Views for SV -2 • Roll up Data • Voice Communications • Surveillance Info • Weather Info • Aeronautical Info • Flight Info • Command & Control Info

  10. SV-4 • Assure that all necessary systems functionality for NCO for services architecture are included. Also assure that elements are sufficient. • Is registry & repository included in service directory? Run Time management? • What is missing from diagram and narrative? • SWIM is currently not in this--comment

  11. OV -3 • Not a traditional netcentric element-DoD is moving from IERs to more NCO approach, while avoiding free-for-all of internet. • Suggest a variation of the tradition OV-3 that more closely aligns with a netcentric ecosystem

  12. OV-6

More Related