(System Wide Information Management (SWIM
اسلاید 1: System Wide Information Management (SWIM)3rd Annual SWIMposium: An Informational Panel on the SWIM Program
اسلاید 2: 2AgendaIntroduction SWIM Program OverviewService Oriented Architecture (SOA) Governance and the National Airspace System (NAS) Service Registry/Repository (NSRR)NAS Enterprise Messaging Service (NEMS)Segment 1 UpdateCloud ComputingLong-Term Plans
اسلاید 3: 3AgendaIntroduction SWIM Program OverviewSOA Governance and the NSRRNEMSSegment 1 UpdateCloud ComputingLong-Term Plans
اسلاید 4: Program ConceptSWIM will:Implement a SOA in the NASAllow the FAA to create new system interfaces more quickly and cheaper than is possible todayFacilitate the data-sharing that is required for the Next Generation Air Transportation System (NextGen)SWIM will not:Be a set of avionics equipmentSubstitute for NAS modernization programsReplace FAA Telecommunications Infrastructure (FTI) SWIM is an IT infrastructure program that will operate in the background to provide data to authorized users4
اسلاید 5: 5SWIM ConceptMigrate the NAS to SOAMakes it easier to establish interfaces between systemsGet the right information to the right place at the right time: Net-Centricity!Facilitate Shared Situational AwarenessFacilitate Collaborative Decision MakingEstablish governance over service implementationsRepresents significant cultural change
اسلاید 6: 6Capabilities performed by one for another to achieve a desired outcomeWhen capabilities are self-contained and independent to enable a collection of services to be linked together to solve a business problemThe fundamental organization of a system embodied in its capabilities, their interactions, and the environmentArchitectureOrientedServiceSOASOA standardizes the necessary interfaces and behavior to support interactionSOA establishes services as the mechanism by which needs and capabilities are brought togetherSOA provides an organizing and delivery paradigm that derives greater value by reusing existing software solutions rather than duplicating capabilitiesSOA organizes technical capabilities in a standard way to allow flexible accomplishment of constantly changing demands
اسلاید 7: 7SWIM is a SOA Implementation SWIM provides:SOA technology infrastructure Governance to ensure that information management standards and processes are followedLeads to consistent service development, operation, and management across the enterpriseBy following SOA standards and principles:SWIM makes services available on a networkEnables systems on the network seeking those services to invoke them without having to change or adapt to the underlying implementation of the service (i.e., loose coupling)
اسلاید 8: 8Conceptual Overview
اسلاید 9: Business as UsualHostWARPIDS/ ERIDSATOPCIWSTFMTMASTARS/ARTS/TAMRERAMASDE-XETMSInter- AgencyTodayState of the System- Existing point-to-point hardwired NAS- Unique interfaces, custom designs- More point-to-point unique interfaces- Costly development, test, maintenance, CM- New decisions linked to old data constructs- Cumbersome data access outside the NASEnterprise ManagementLEGENDSWIM Segment 1SWIM Future Segment SWIM AdapterFAA SystemsSWIM Compliant Non-Government SystemsSWIM Compliant Government SystemsFTITFMSCIWSTDDSITWSWMSCRAIM TBFMDOTSERAMCARTS/STARS9
اسلاید 10: Segmented Approach to SWIMSWIM Segment 1: Implementation of a set of federated services in the NAS with SWIM-provided governance, standards, and software to support development of reusable SOA servicesSWIM provides requirements, schedule, and funding to seven other NAS programs; tracks progress via formal monthly reviews Segment 1 results in SOA services deployed to all Air Route Traffic Control Centers (ARTCCs), 37 Terminal Radar Approach Controls (TRACONs), the Air Traffic Control System Command Center, the William J. Hughes Technical Center (WJHTC), and NAS Enterprise Management Centers (NEMCs)SWIM Segment 2:Continues provision of governance, standards, and software to additional NAS programsImplements enterprise messaging service for new “SWIM Implementing Programs” (SIPs) and facilitates transition by Segment 1 SIPs10
اسلاید 11: Segment 1 CapabilitiesCapabilities will be implemented as multiple services by SIPs through FY1511
اسلاید 12: SWIM Schedule12FY 09FY 09FY 09FY 09FY 10FY 10FY 10FY 10FY 11FY 12FY 13FY 14FY 15FY 15FY 15FY 16FY 16FY 16FY 16FY 17FY 17FY 17FY 17SWIM Segment 1SWIM Segment 1SWIM Segment 1SWIM Segment 1SWIM Segment 1SWIM Segment 1SWIM Segment 1SWIM Segment 1SWIM Segment 1SWIM Segment 1SWIM Segment 1SWIM Segment 1SWIM Segment 1SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2SWIM Segment 2
اسلاید 13: 13DATESCAPABILITIESOctober 2010Corridor Integrated Weather System (CIWS) Publication operational • CIWS SIPDecember 2010Special Use Airspace (SUA) Automated Data Exchange operational • Aeronautical Information Management (AIM) SIPJanuary 2011Integrated Terminal Weather System (ITWS) Publication operational • ITWS SIPJune 2011Reroute Data Exchange operational • Traffic Flow Management (TFM) SIPJune 2012PIREP Data Publication operational • Weather Message Switching Center Replacement (WMSCR) SIPOctober 2012Flight Data Publication – Initial Flight Data Services operational • En Route Automation Modernization (ERAM) SIPSWIM Milestones
اسلاید 14: 14DATESCAPABILITIESFebruary 2013SUA Automated Data Exchange operational • ERAM SIPAugust 2013Flow Information Publication operational • TFM SIPAugust 2013Terminal Data Distribution operational • SWIM Terminal Data Distribution System (STDDS) SIPMarch 2014Flight Data Publication – Host Automation Data Distribution System/Flight Data Input Output (HADDS/FDIO) operational • ERAM SIPJune 2014Runway Visual Range (RVR) Publication Service operational • TFM SIPMarch 2015Flight Data Publication – Enterprise Services operational • ERAM SIPMarch 2015PIREP Data Publication operational • ERAM SIPSeptember 2015SWIM Tool Kits • SWIM Core ServicesSWIM Milestones (cont.)
اسلاید 15: FY11 AccomplishmentsReleased the SWIM Segment 2 Technical Overview and draft Final Program RequirementsCIWS and ITWS SWIM services became operational AIM demonstrated SUA Automated Data Exchange Initial Operating Capability (IOC)Deployed Terminal Data Distribution System (TDDS) prototypePerformed governance oversight of SIPs and other FAA programs to ensure interoperability between systemsContinued SOA suitability assessments of other FAA programs that are going through the Joint Resources Council (JRC) processContinued operating Commercial-Off-The-Shelf (COTS) software repository, wiki, and web site15
اسلاید 16: FY12 Planned ActivitiesImplement enterprise SOA governanceExecute Segment 2 activities Deploy WMSCR PIREP Data PublicationDevelop Domain Name Service (DNS) prototypeDesign Review for Network Time Protocol (NTP)Design Review for Identity and Key Management (IKM)Conduct Segment 2 JRC Final Investment Decision (FID)16
اسلاید 17: Questions and Comments?17
اسلاید 18: 18AgendaIntroduction SWIM Program OverviewSOA Governance and the NSRRNEMSSegment 1 UpdateCloud ComputingLong-Term Plans
اسلاید 19: 19What is Governance?The set of processes that specifies the decision making and accountability that encourage desirable behaviors in the organization (Gartner, 2007)Ensuring and validating that assets and artifacts within the architecture are acting as expected and maintaining a certain level of quality (Gartner, 2007)It needs to be just enough to ensure success, but not so much as to become inflexible and monolithic
اسلاید 20: 20How does one Govern?Establishing chains of responsibility, authority, and communication to empower people (decision rights)1Establishing measurement, policy and control mechanisms to enable people to carry out their roles and responsibilities1An Enterprise Perspective1 Rational Unified Process, version 7.0.1 SOA Governance and Management Overview
اسلاید 21: 21Enterprise Governance PerspectiveSWIM Compliant Non-Government SystemsSWIM Compliant Government SystemsSWIM Core CapabilitiesFAA SystemsThe Good……the Bad…… and the UglyZeal for SOA and Web Services without Governance leads to incompatible implementations and “rogue” services.
اسلاید 22: 22Scope of SWIM GovernanceSWIM Governance is a catalyst for improving overall NAS, Air Traffic Organization (ATO) and FAA governanceIt’s a part of FAA GovernanceWhat is FAA/ATO/NAS governance?Establishing decision making rights associated with the FAA/ATO/NASEstablishing mechanisms and policies used to measure and control the way FAA/ATO/NAS decisions are made and carried outWhat is SWIM governance?Extension of NAS governance focused on the lifecycle of services to ensure the business value of SWIMATO GovernanceSWIM GovernanceNAS GovernanceFAA Governance
اسلاید 23: 23SWIM GovernanceWHO is responsibleGovernance AuthorityInitial Service Candidate Approval by Technical Review Board (TRB)SWIM manages remainder of lifecycle for approved programsService Providers responsibilities documentedService Consumers responsibilities documentedWHAT must they doSWIM Governance Policies v1.1SWIM Service Lifecycle Management Processes v1.0HOW must they do itTechnical Standards coordinated with NAS Enterprise ArchitectureTV-1 Technical Standards ProfileTV-2 Technical Standards ForecastFAA StandardsFAA-STD-063 XML NamespacesFAA-STD-064 Web Service RegistrationFAA-STD-065 Web Service Description DocumentsFAA-STD-066 Web Service TaxonomiesSWIM Version Management Processes v1.0NSRR User Guides
اسلاید 24: 24Simplified Enterprise Architecture System View
اسلاید 25: 25SWIM Governance Policies OutlineSTRATEGIC SOA POLICIESSOA Technology AcquisitionEnterprise ArchitectureOpportunity Management for SOA ServicesInteroperability, Reuse and StandardsNSRRSERVICE DESIGN-TIME POLICIESNamespace and SchemaService Interface DesignServices Technical and DesignInformation Security Service Development ProcessService Lifecycle ManagementServices Operations ReadinessService Provisioning Service ConsumerRUNTIME AND OPERATIONAL POLICIESMessaging and RoutingRuntime SecurityService ManagementNote: Adapted from the “Simplified Enterprise Architecture System View”
اسلاید 26: 26SWIM Interoperability StandardsUse of SWIM Service Container Software (Segment 1)JMS Provider Standardization (FUSE Message Broker / Apache Active MQ)Supported Message Formats and TransportsSOAP-over-HyperText Transfer Protocol (HTTP)/HyperText Transfer Protocol Secure (HTTPS)eXtensible Mark-up Language (XML)-over-HTTP/HTTPSSOAP-over-Java Message Service (JMS)XML-over-JMSSOAP Messaging WS-I ConformanceSWIM Interoperability Basic Profile Binary Attachments in SOAP MessagesSOAP with AttachmentsMessage Transmission Optimization Mechanism (MTOM)
اسلاید 27: 27SWIM Interoperability Standards (cont.) JMS Message Type TextMessage for XML or textByteMessage for binary dataObjectMessage – NO, implies undesirable language couplingRegistry / RepositoryDiscoverability - Web Services Description Language (WSDL)Categorization - FAA-STD-066 and SWIM TaxonomiesService Interface DesignDesign PoliciesService Interface Description – Web Service Description Document (WSDD)Information Security SWIM Basic Security ProfileService Management Java Management eXtensions (JMX)
اسلاید 28: 28SWIM ComplianceSWIM Compliance Definition:“Verified conformance to SWIM Policies.” (SWIM Service Lifecycle Management Processes v1.0)Verification MechanismsManual review of artifactsGovernance-enabling TechnologyNSRRTesting Tools (Actional, Lisa, etc…)SWIM Web Service Security Compliance Test Kit (SWIM WS-S CTK)Policy ServersXML GatewaysEnterprise Service Management (ESM) software
اسلاید 29: 29Service Lifecycle Management DecisionsTRBInvestment Decision AuthoritySWIM Governance TeamIn Service Decision (ISD) Authority
اسلاید 30: 30SOA Suitability CriteriaNAS Enterprise View Potential for existing SWIM service to be utilized or tailored to meet the requirementPotential for other users to benefit from the information exchange Potential hazards for exposing data through SWIM (e.g., proprietary data, non-FAA user access)Program View (Cost, Schedule, Technical)Life-Cycle Cost of SWIM versus other solutionsSystem performance requirements: latency, transmission rate, bandwidth, response time, overhead, etc.Safety/certification requirementsInformation security requirements Existing architecture/vendor solution impacts
اسلاید 31: Service DiscoverabilityDiscoverability is a key Principle of Service Design1 in a SOACommon metadata framework to express purpose and capabilities of the ServiceAllow human browsingAllow machine-to-machine queries1 Principles of Service Design, Erl et.al. Prentice Hall, 2008 31
اسلاید 32: Registry RepositoryServiceConsumerServiceProviderServiceRegistryExchange MessagesPublishand RegisterContractDiscoverand RetrieveContractIn fact, it was the existence of a discovery mechanism that primarily distinguished SOA from previous distributed architecture models.Principles of Service Design32
اسلاید 33: Service Registry/RepositoryA Service Registry is a resource that provides controlled access to data necessary for the implementation and governance of SOA projectsA Repository is a database containing the artifacts and metadata that constitutes a SOA registryFacilitates content validation and workflow supportStores Policies, Processes, and Schemas to support Governance ActivitiesNote: These are usually referenced as one product, often called a Registry/Repository33
اسلاید 34: Why a Registry/Repository?Centralized discoveryLifecycle governanceCentralized deploymentPolicy and standards enforcementAutomated service notification mechanismCentral to any SOA infrastructure in the promotion of reuse34
اسلاید 35: Taxonomies“A hierarchical organization of categories or values used for classification” (FAA-STD-066)FAA-STD-066 defines required taxonomies for FAASWIM has defined additional taxonomies required for NAS ServicesUse and support of taxonomy enforcement is critical to the success of any registry implementationPotential Taxonomy Candidates:• Organization Unit• Business Name• Lifecycle Stage• Services for Citizens35
اسلاید 36: ArtifactsAn Artifact is a repository item attached to a service that describes the service or may be used to access the serviceSome examples include:WSDL (Web Service Description Language)WSDD (Web Service Description Document, defined in FAA-STD-065)ConOps (Concept of Operations, for interfaces, messaging, etc.)IRD (Interface Requirements Document)Registry StandardsUniversal Description, Discovery, and Integration (UDDI)Supports the enforcement of enterprise policiesPolicy enforcement will enhance registry data qualityElectronic Business XML (ebXML)Created to primarily support secured business transactions36
اسلاید 37: NSRR Video37click for video
اسلاید 38: Questions and Comments?38
اسلاید 39: For more information ...For more information on SWIM Governance and the NSRR, please contact:Paul JacksonSWIM Governance Leademail: paul.jackson@faa.govphone: (202) 267-378939
اسلاید 40: 40AgendaIntroduction SWIM Program OverviewSOA Governance and the NSRRNEMSSegment 1 UpdateCloud ComputingLong-Term Plans
اسلاید 41: NEMS AgendaNEMSSWIM EvolutionSWIM in NAS ArchitectureNEMS Integration Into NAS ArchitectureMajor Segment 2 ActivitiesTransition Planning – Provisioning – On-RampingQ & A41
اسلاید 42: Interaction ServicesMission ServicesInteraction ServicesInteraction ServicesEnterprise GovernanceRuntime ManagementStrategic GovernanceService OrchestrationService ChoreographySecurity Policy ManagementService SLA ManagementService Scorecard Generation and PublicationService Design GovernanceStrategic SOA GovernanceRun-time and Operations GovernanceSOA Governance Service Desk SupportAdministrative ServicesData/NetworkSupport ServicesNetwork Support ServicesDatabase Admin ServicesInformation System Security Support ManagementIncident Detection and Response ServicesBusiness Continuity ManagementHelp DeskBrowserWeather NotificationWeb ApplicationOn-Demand NAS PortalAdmin PortalClientFlow Constrain NotificationAirport Status and Mission Critical NotificationBoundary ProtectionInformation System Security Support InfrastructureSOA Support PlatformsWeb Application Hosting CapabilityData StorageComputing PlatformTerrestrial Network CommunicationAir/Ground CommunicationSensor SystemsData AcquisitionService AdaptationContent DiscoveryData Flow MechanismsMessage RoutingMediationPolicy Enforcement and Metric CollectionPerformance Monitoring and ReportingSLA Compliance and Metrics CollectionFault Monitoring and ReportingSeparation ManagementTrajectory ManagementFlight and State Data ManagementFlow Contingency ManagementShort Term Capacity ManagementLong Term Capacity ManagementSystem and Services AnalysisSystem and Services ManagementAeronautical Information ManagementWeather Information ManagementSurveillance Information ManagementNavigation SupportSafety ManagementService RegistrationService DiscoverySecurity Policy Enforcement and Access ManagementService Security MonitoringInstant MessagingWhite BoardUser Interaction Interface and PortalsNotifications and AlertsData AccessData Flow ManagementSupport ServicesEnterprise Service ManagementMessaging Services provided by NEMSSecurity ServicesCollaboration ServicesInterface ManagementServices ProvisioningManagementServices Development, Integration and TestServices DiagnosticsServices ProvisioningCertified Software ManagementTraining SupportTechnical Infrastructure Services= SWIM= FTI= SIPs= Future/OtherEnterprise SOA Services Allocation (NAS SV-4 2012-2016)SOA Core Services= NEMC= TBDService Policy ManagementData CompositionRequest/ ResponsePublish/ Subscribe
اسلاید 43: NEMSNAS Enterprise Security GatewayWAN ServicesNetwork SecurityLayered, Two-Tier Architecture: Enterprise Domain and Service DomainLayered architecture used for re-usability of information/content assetsService Domain Tier: application programs able to provide/consumer available dataEnterprise Tier: hosts “enterprise services” accessible by all authorized usersInterface Management layer abstracts enterprise domain to service domainsAlleviates requirements on application programs to expose services to enterpriseEnables a simple, standardized mechanism for applications programs to discover, acquire, and ingest enterprise services, rapidly improving information re-usability across the NASGovernanceService RegistryData RepositoryPolicy RepositoryService ProvisionSecurity OperationsMonitor & ControlEnterprise Tier ESBNAS UsersSystem/Security AdminInterface ToolkitExternal CustomersSponsor ProgramsInfrastructure Service DevelopersSOA GovernanceService ManagementService Level SecurityService AdministrationRuntime DiscoveryStandards-Based ESB Interface (SOA-enabled)Standards-Based ESB Interface (SOA-enabled)Message-Oriented Middleware (Legacy Systems)UESBHosted on Shared InfrastructureService Legend:NEMSFTIFlight Plan DomainWeather DomainAirport Domain43
اسلاید 44: Service Domain TierEnterprise Domain TierPolicy Implementation Points WAN Services Network SecurityEnterprise Domain Tier ESB Stakeholders – Make DecisionsProcess – Procedures, Metrics, Control MechanismsPolicies – Decisions MadeDomain Specific GovernanceProviding Local AutonomyNAS-WideGovernance Providing Central DirectionSystem/Security AdminService Level SecurityEnterprise ServicesIdentity ManagementAccess ManagementService ManagementEnterprise ServicesService AdministrationSponsorProgramsLegendNEMS ServiceFTI ServiceService Container Enabled AppsLegacy NAS System AppsLeveraging Enterprise Domain ESB Separates the IT and integration infrastructure concerns from domain specific ATM concerns SIPSWIM Service ContainerNAS ApplicationsNAS ApplicationsNAS ApplicationsLegacy SystemLegacy InfrastructureNAS ApplicationsNAS ApplicationsNAS ApplicationsTRACON 1ARTCC nNAS Enterprise Security GatewayUESBNAS UsersExternal CustomersInterface ToolkitManaged Access To Enterprise ServicesLegacy System InterfaceStandards-Based ESB InterfaceNAS UsersNAS UsersEnables NAS use of multiple vendor technologies avoiding lock-inNAS programs and lines of business are executed by domain expertsNEMSDecoupled using JMS and WS ARTCC 1TRACON nNEMS Enterprise Architecture44
اسلاید 45: Infrastructure Build Out Provisioning - On-Ramping Producers/ConsumersCapabilities EnhancementsSegment 2 Enterprise Messaging Activities45
اسلاید 46: NEMS On-ramping StepsService Provisioning: On-Ramping Providers and Consumers to NEMS DataArchitectureDecision toOn-ramp content(Policy) Consumer On-ramps Producer On-RampsConfigure Infrastructure46
اسلاید 47: NEMS User Deployment Status47
اسلاید 48: Questions and Comments?48
اسلاید 49: For more information ...For more information on how your program will interface with NEMS, please contact: Jim RobbSWIM Requirements Leademail: jim.robb@faa.gov phone: (202) 267-8357orMaureen CedroFTI Engineering Manageremail: maureen.cedro@faa.govphone: (202) 493-141049
اسلاید 50: 50AgendaIntroduction SWIM Program OverviewSOA Governance and the NSRRNEMSSegment 1 UpdateCloud ComputingLong-Term Plans
اسلاید 51: SWIM Segment 1Federated ApproachImplementation of a set of federated services in the NAS with SWIM-provided governance, standards, and software to support development of reusable SOA servicesSWIM provides:Overall Program Cost and ScheduleSWIM System Engineering and Requirements ManagementDefinition and Maintenance of Program Level Agreements (PLAs) with implementing programsGovernance of Segment 1 participantsSIPs are responsible for:Managing the development and deployment of allocated SWIM requirements per the SWIM Final Program Requirements Document and in accordance with the SWIM Program ScheduleReporting progress against schedule51
اسلاید 52: SWIM Segment 1 CapabilitiesCapabilities will be implemented as multiple services over the next five years52
اسلاید 53: AIM COISUAAutomated Data ExchangeAIM (P)ERAM (C)Service that enables SUA data updates dynamically from ERAM via an improved Air Traffic Control Graphical User InterfaceService for consumers to subscribe and receive SUA information dynamically in the Aeronautical Information Exchange Model (AIXM) standardServices to dynamically publish AIXM SUA definitions for use by the public and within NAS operational systems (i.e., SUA Airspace Management System (SAMS))ProducerNot OperationalConsumerOperational53
اسلاید 54: Weather COIServices to publish both image and binary encoded CIWS data products to serve the varied needs of the consumers. Products available are:VIL Mosaic (1KM resolution)VIL 2-hr. ForecastEcho Tops Mosaic (1 km resolution)Echo Tops 2-hr. ForecastSatellite MosaicStorm Info: Echo Top TagsStorm Info: Leading EdgesStorm Info: Motion VectorsVIL Forecast Contours (Standard Mode)VIL Forecast Contours (Winter Mode)Echo Tops Forecast ContoursGrowth & Decay ContoursForecast Accuracy: Echo TopsForecast Accuracy: Standard PrecipitationForecast Accuracy: Winter Precipitation CIWS PublicationCIWS (P)Airlines (C)ProducerNot OperationalConsumerOperational54
اسلاید 55: Weather COI (cont.)ITWSPublicationITWS (P)Airlines (C)ProducerNot OperationalConsumerOperationalServices to provide ITWS products digitally to the Airline Operation Centers (AOCs) and other subscribers. Products available are:Airport Lightning WarningConfigured AlertsForecast AccuracyForecast ContourForecast ImageGust Front TRACON MapMicroburst TRACON MapPrecipitation 5nmPrecipitation Long RangePrecipitation TRACONSM SEP 5nmSM SEP Long RangeSM SEP TRACONTerminal Weather Text NormalTornado AlertTornado DetectionsWind ProfileAP Indicated PrecipitationAP StatusGust Front ETIHazard Text 5nmHazard Text Long RangeHazard Text TRACONITWS Status InformationMicroburst ATISRunway ConfigurationStorm Motion 5NMStorm Motion TRACONTerminal Weather Text SpecialWind Shear ATIS55
اسلاید 56: Weather COI (cont.)Pilot Reports (PIREP) Data PublicationWMSCR (P)ERAM (C)ProducerNot OperationalConsumerOperationalService to allow En Route controllers that receive voice Pilot Reports, to efficiently enter them into ERAM, which will transmit the reports to WMSCRService to provide stored PIREPsService to provide altimeter settings56
اسلاید 57: Flight & Flow Management (F&FM) COIFlight DataPublicationERAM (P)TFM (C)ProducerNot OperationalConsumerOperationalService to provide flight data available to NAS users and external users57
اسلاید 58: F&FM COI (cont.)RerouteData ExchangeERAM (P)TFM (C)ProducerNot OperationalConsumerOperationalService to provide the means for Traffic Managers to efficiently convey reroutes to Air Traffic Controllers for pre-departure flights taking into account NAS Customer preferences. 58
اسلاید 59: F&FM COI (cont.)RVR PublicationTDDS (P)TFM (C)External (C)ProducerNot OperationalConsumerOperationalService to provide runway visibility data available to NAS users and external users 59
اسلاید 60: F&FM COI (cont.)STDDSTDDS (P)TFM (C)ERAM (C)External (C)ProducerNot OperationalConsumerOperationalServices will be provided to NAS users and external users:ASDE-X streaming data serviceSurface Movement Events (SME) Tower Departure Events (TDE)60
اسلاید 61: F&FM COI (cont.)Flow Information PublicationTFM (P)ERAM (C)ProducerNot OperationalConsumerOperationalServices that provide a means for ERAM to subscribe to flow information describing several types of traffic flow initiatives. These will include the following: Flow Constrained Area (FCA) Airspace Flow Program (AFP) Ground Delay Program (GDP) Ground Stops (GSs) Reroutes Advisories61
اسلاید 62: Segment 1 Status SummarySWIM Segment 1 commits to delivery of 9 capabilities, 8 of which are on track:Two capabilities complete and operational:ITWS Data PublicationCIWS Data Publication Three capabilities complete and waiting for installation:WMSCR PIREP Data PublicationAIM SUA Automated Data ExchangePre-Departure RerouteTwo capabilities are on schedule and within budget allocations: TDDSTFM Flow Data PublicationOne capability being replannedFlight Data Publication Service62
اسلاید 63: Questions and Comments?63
اسلاید 64: For more information ...For more information on SWIM Implementation, contact:Jeff HobbsSWIM Implementation Leademail: jeffery.hobbs@faa.govphone: (202) 267-9772orLinda ChenSWIM Implementationemail: linda.chen@faa.govphone: (202) 267-756664
اسلاید 65: 65AgendaIntroduction SWIM Program OverviewSOA Governance and the NSRRNEMSSegment 1 UpdateCloud ComputingLong-Term Plans
اسلاید 66: 66Cloud Computing OverviewCloud computing is “a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources… that can be rapidly provisioned and released with minimal management effort or service provider interaction.” (National Institute of Standards and Technology (NIST))Federal Cloud Computing Strategy (February 8, 2011, Vivek Kundra, U.S. Chief Information Officer)Decision Framework for Cloud MigrationNIST facilitates and leads the development of standards for security, interoperability, and portabilityEach Agency CIO is required to identify three “must move” services and create a project plan for migrating each of them to cloud solutions and retiring the associated legacy systems. Of the three, at least one of the services must fully migrate to a cloud solution within 12 months and the remaining two within 18 months.
اسلاید 67: 67FAA’s Cloud ProgressFAA NAS and Non-NAS organizations have and will continue to work collaboratively on cloud adoption under the leadership of the Chief Information Officer (CIO)SWIM Program is responsible for implementing cloud in the NASThe FAA IT Infrastructure Board is responsible for oversight and guidance for FAA’s non-NAS IT infrastructure, including cloud as well as data center consolidation effortsFAA is currently in the early stages of evolution to cloudHeld formal and informal learning sessions, which included industry cloud leaders and expertsIdentified several cloud opportunities and currently using pilots as a means to better understand cloud issuesThe FAA is currently establishing a private cloud that will be used by the FAA and other federal agencies67
اسلاید 68: 68Cloud Suitability AssessmentDeveloping a Cloud Suitability Assessment that will be used to identify which data is suitable to move to the cloud 68
اسلاید 69: Questions and Comments?69
اسلاید 70: 70AgendaIntroduction SWIM Program OverviewSOA Governance and the NSRRNEMSSegment 1 UpdateCloud ComputingLong-Term Plans
اسلاید 71: AgendaLong-Term Plans:Net-Centric Prototypes and DemonstrationsOther External CoordinationAircraft Access to SWIM (AAtS)71
اسلاید 72: Net-Centric Prototypes/Demos ActivitySWIM hosts Net-Centric Prototypes/Demos Technical Interchange Meetings (TIMs)Initial TIM held April 2008Recent TIMs held November 3, 2010 and May 4, 2011Facilitate Net-Centric Demo coordination/interaction Demos may interact with SWIM in the futureCoordination for “SWIM Compliance”Next TIM scheduled for November 2, 2011SWIM-Maintained List of Net-Centric Prototypes/DemosListing of existing and planned prototypes and demos of possible interest to SWIM Contains name, owner, location, key features, points-of-contact (POCs), and SWIM relationshipShared with Joint Planning and Development Office (JPDO) for use in information sharing environment72
اسلاید 73: Other External CoordinationJPDO Net-Centric Operations Working GroupJPDO Net-Enabled Test EnvironmentNet-Centric Operations Industry ConsortiumNextGen Implementation and Integration (I&I) Segment Alpha and Bravo Working GroupsFAA/Single European Sky Air Traffic Management (ATM) Research Joint Undertaking (SESAR JU) SWIM Interoperability Coordination73
اسلاید 74: AAtS OverviewWhat is AAtS?Provides aircraft with a connection to NAS services enabled by SWIMWhy do we want AAtS?Improves aircraft situational awarenessAircraft will have the same information the FAA uses to make ATM decisionsA collaborative decision making (CDM) enablerAAtS finally allows all three parties (ATM, AOC, and the aircraft) to operate from a common pictureOther systems get information to the cockpit. AAtS delivers common information 74
اسلاید 75: AAtS Overview (cont.)ConceptAAtS will initially use existing NAS and aircraft infrastructure (e.g., FTI, SWIM, Electronic Flight Bags (EFBs))Information delivered via AAtS is not intended for uses that directly affect the trajectory of the aircraftNote:FAA has no plans at this time to acquire a system or infrastructure to specifically support AAtSAAtS will not replace existing or planned FAA systems75
اسلاید 76: AAtS Overview (cont.)Data services via AAtS Only services available through NEMS will be available by AAtSAAtSWIM – without SWIM there is no AAtS Scalability capability is keyNew data elements can be added more quickly, more easily, and less expensivelyNew NAS data will be made available to aircraft by granting operators access to the additional data elements provided by SWIM76
اسلاید 77: AAtS – Notional Concept77
اسلاید 78: Key AAtS componentsFAA Data ProvidersAeronautical InformationFlight and Flow InformationWeather InformationEtc.FAA Enterprise Infrastructure (SWIM, FTI)Data Management Service (DMS) Providers (Non-FAA)Access, process & disseminate data products from FAA and end usersCreate applications as neededData Transport ProvidersProvide terrestrial and/or satellite data links to and from the aircraft and ground infrastructureEnd UsersAirlines, Business Aviation, General Aviation, and Military Aviation 78
اسلاید 79: Notional
اسلاید 80: Demos – to begin late 2011To continue to 2014Scope is to perform simulations, demonstrations, and trials Both domestic and oceanic/remote area global interoperability trials plannedArchitecture and technical profile definition – underwayFunctional architecture is being developed in phasesDemo – to support AAtS simulations and infrastructure development – out in draftMid-term – to support AAtS capability IOC in early 2014 – March 2012Far-term – to support long term evolution – September 2012Technical requirements development targeted for late 2012Derived from architecture as technical profile (TV-5)AAtS Activities80
اسلاید 81: AAtS – FAA EffortsNew ATM Requirements – NextGen System DevelopmentConcept of Use development. Associated definition and identification of the ways that AAtS affects the operations of the NAS – includes Human-In-The-Loop (HITL) simulations and demonstrationsTechnical Concept development. Associated definition of the AAtS architecture, technical profile, and identification of AAtS impact on the NAS infrastructure – includes technical simulations and testsAAtS Demonstrations AAtS Operational Trials – includes the demonstration of use and technical concepts developed above81
اسلاید 82: AAtS Simulations, Tests, And Operational Trials2011AAtS ConUse concepts validation AAtS technical concepts validation, requirements, and metrics developmentServices used in demo to be determined by the availability of services that are structured similar to services found on SWIM (real or emulated)2012AAtS domestic operational trialsServices used in trials to be determined by availability of services on SWIM (operational or scheduled-to-be-operational by 2014)Safety analysesRobustness evaluations and additional other technical evaluations2013AAtS global interoperability oceanic/remote area operational trialsServices used in trials to be determined by the same method as 2012 domestic operational trials with the potential addition of other ANSP SWIM productsSecurity analysesRobustness evaluations and additional other technical evaluations82
اسلاید 83: Questions and Comments?83
اسلاید 84: For more information ...For more information on SWIM’s Long-Term Plans, contact:Mike HritzSWIM Evolution & Coordination Leademail: mike.hritz@faa.govphone: (202) 385-719884
اسلاید 85: The SWIM.gov website describes the SWIM program and provides news announcements for current issuesIt also contains key documentation, including select briefings, the SWIM Newsletter and the SWIM Q&AThere are several ways to learn more about SWIMwww.swim.gov85
اسلاید 86: 86SWIM Points of ContactProgram ManagerAhmad Usmaniahmad.usmani@faa.gov(202) 267-3391ImplementationJeffery Hobbs jeffery.hobbs@faa.gov(202) 267-9772Linda Chenlinda.chen@faa.gov(202) 267-7566RequirementsJim Robb jim.robb@faa.gov(202) 267-8357Evolution & Coordination Mike Hritz mike.hritz@faa.gov(202) 385-7198Acquisition Robert Kleinrobert.klein@faa.gov(202) 493-4651Program Control Ellen Muldoonellen.muldoon@faa.gov(202) 493-5932
نقد و بررسی ها
هیچ نظری برای این پاورپوینت نوشته نشده است.