DOCSLIB.ORG

Open Data: a Review of the State of The

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Open Data: a Review of the State of The Ref. Ares(2018)3457727 - 29/06/2018 Contract No. H2020 – 730539 IN2SMART Project Title: Intelligent Innovative Smart Maintenance of Assets by integrated Technologies Starting date: 01/09/2016 Duration in months: 36 Call (part) identifier: H2020-S2RJU-CFM-2016-01-1 Grant agreement no: 730569 Open data: a review of the state-of-the-art D7.1 Due date of deliverable: Month 12 Actual submission date: 31-08-2017 Leader of this deliverable: DLR Dissemination level: CO Revision: Issued Revision History Table Version Reason for change Issue Date V1.0 Initial Issue 18/07/2017 V2.0 Requested Revision 28/06/2018 This project has received funding from the Shift2Rail Joint Undertaking under the European Union’s Horizon 2020 research and innovation programme under grant agreement No 730569 D7.1 GA 730569 Open data: a review of the state-of-the-art Details of contribution Author(s) DEUTSCHES ZENTRUM - Deliverable coordination FUER LUFT - UND - Main contents in chapters 1, 2, 3, 5, 7.1, RAUMFAHRT EV (DLR) 8.1.2, 8.5, 9, 10, 11 - Discussions about document structure Elmar Brockfeld and contents Jörn Christoffer Groos - Complete document review Rüdiger Ebendt Christian Rahmig Lucas Schubert Michael Scholz Contributor(s) ANSALDO STS S.p.A. - Main contributions chapters 4, 6.5, 7.2 (ASTS) - Discussions about document structure Fabrizio Cosso and contents - Complete document review Matteo Pinasco NETWORK RAIL - Main contributions to chapter 8.1 INFRASTRUCTURE - Discussions about document structure LIMITED (NR) and contents - Complete document review Caroline Lowe BOMBARDIER - Main contributions to chapters 8.1.3 – TRANSPORTATION 8.1.6 SWEDEN AB (BT) - Discussions about document structure and contents Zbigniew Dyksy - Complete document review Mikael Danielsson Martin Karlsson SIEMENS - Main contributions to chapters 6.3, 6.4, AKTIENGESELLSCHAFT 8.3 (SIE) - Discussions about document structure and contents Sven Adomeit - Complete document review Andreas Bolm Frank Aust Jochen Grühser THALES GROUND - Main contributions to chapters 6.3.2, 7.3 TRANSPORTATION - Discussions about document structure SYSTEMS UK LTD (THA) and contents - Complete document review David Tickem IMS-WP7-D7.1-DLR-006-02-I 2 of 133 D7.1 GA 730569 Open data: a review of the state-of-the-art Kompetenzzentrum - - Main contributions to 6.1.1, 6.1.2, 6.1.3, Das Virtuelle Fahrzeug, 8.2 Forschungsgesellschaft - Discussions about document structure and contents mbH (VIF) - Complete document review Josef Fuchs Alexander Meierhofer FCP FRITSCH, CHIARI & - Main contributions to chapters 8.1.4, 8.4 PARTNER - Discussions about document structure ZIVILTECHNIKER GMBH and contents - Complete document review (FCP) Gerald Julian Rajasingam WIENER LINIEN GMBH - Main contributions to chapter 7.2.2 &CO KG (WL) - Discussions about document structure Simon Wallner and contents - Complete document review LULEA TEKNISKA - Main contributions to chapters 6.1, 6.4, UNIVERSITET (LTU) 7.4, 7.5 Mustafa Aljumaili - Discussions about document structure and contents Matti Rantatalo - Complete document review Karim Ramin IMS-WP7-D7.1-DLR-006-02-I 3 of 133 D7.1 GA 730569 Open data: a review of the state-of-the-art TABLE OF CONTENTS 1 EXECUTIVE SUMMARY .................................................................................... 10 1.1 Acronyms and Abbreviations ..................................................................................... 11 2 BACKGROUND ............................................................................................... 18 3 OBJECTIVE/AIM ............................................................................................. 19 4 SUMMARY OF RELEVANT IN2RAIL RESULTS .................................................... 20 4.1 IN2RAIL Description .................................................................................................. 20 4.2 IN2RAIL Deliverables ................................................................................................ 21 4.3 D9.1 Asset Status Representation [3] ....................................................................... 22 4.3.1 Deliverable content .............................................................................................. 22 4.3.2 Deliverable Conclusions ...................................................................................... 23 4.4 D8.1 Requirements for the Integration Layer ............................................................ 23 4.4.1 Deliverable content .............................................................................................. 23 4.4.2 Deliverable Conclusions ...................................................................................... 24 4.5 D8.5 Requirements for the Generic Application Framework ..................................... 24 4.5.1 Deliverable content .............................................................................................. 24 4.5.2 Deliverable Conclusions ...................................................................................... 25 4.6 Annex to D8.3: Description of the Canonical Data Model .......................................... 25 4.7 Conclusions ............................................................................................................... 25 5 ONLINE SURVEY ............................................................................................. 27 5.1 Questionnaire ............................................................................................................ 27 5.2 Feedback .................................................................................................................. 27 5.2.1 Participants’ domains of service ........................................................................... 27 5.2.2 Extent of use and use cases of Open Data Exchange formats ............................ 28 5.2.3 How generic/specialised are Open Data Exchange formats? .............................. 29 5.2.4 “Best” example of an Open Data Exchange format suitable for one of several sources of information ...................................................................................................... 30 5.2.5 The extent to which a participant’s company or institution participates in Open Data Exchange initiatives and communities ..................................................................... 31 5.2.6 Optional mindset questions: Open Data Exchange policy and attitude towards Open Data ........................................................................................................................ 32 IMS-WP7-D7.1-DLR-006-02-I 4 of 133 D7.1 GA 730569 Open data: a review of the state-of-the-art 5.2.7 Strengths and weaknesses of Open Data Exchange formats .............................. 32 5.2.8 Licensing and/or legal issues hampering application of Open Data Exchange formats 33 5.3 conclusions ............................................................................................................... 33 6 OPEN DATA EXCHANGE: TECHNOLOGIES .......................................................... 35 6.1 Files ........................................................................................................................... 35 6.1.1 General formats ................................................................................................... 35 6.1.2 Specific formats ................................................................................................... 39 6.2 Modeling Languages and Tools ................................................................................ 41 6.3 Communication protocols .......................................................................................... 42 6.3.1 OPC UA ............................................................................................................... 42 6.3.2 Queue/topic based messaging systems .............................................................. 45 6.4 Web services / APIs .................................................................................................. 49 6.4.1 Web Services ....................................................................................................... 49 6.4.2 Web APIs ............................................................................................................. 51 6.4.3 Comparison Web Services vs. Web APIs ............................................................ 52 6.5 In memory data grid technologies ............................................................................. 52 6.5.1 In-Memory Data Grid Overview ............................................................................ 52 6.5.2 Infinispan.............................................................................................................. 52 6.5.3 Redis .................................................................................................................... 53 7 OPEN DATA EXCHANGE: APPLICATIONS ........................................................... 54 7.1 Geodata (DLR, LTU) ................................................................................................. 54 7.1.1 Vector Data .......................................................................................................... 54 7.1.2 Raster Data .......................................................................................................... 55 7.1.3 Geo Web Services ............................................................................................... 55 7.1.4 Open Street Map, Open Railway Map ................................................................
Load more

Recommended publications
  • Odata Services Company
    PUBLIC 2021-03-09 OData Services company. All rights reserved. All rights company. affiliate THE BEST RUN 2021 SAP SE or an SAP SE or an SAP SAP 2021 © Content 1 SAP Cloud for Customer OData API..............................................4 2 New Features.............................................................. 13 2.1 What's New in OData API v2 Reference.............................................13 2.2 Add Public Solution Model (PSM) Fields to Standard OData Services........................15 2.3 Transport Custom OData Services with Transport Management............................16 2.4 Compatibility Mode for READ Operations........................................... 16 2.5 Support for User-Friendly IDs in Standard OData Services................................16 2.6 Constant Values to Function Imports...............................................17 3 OData API Reference.........................................................18 3.1 OData API v2 Reference........................................................18 3.2 OData API v1 Reference (Deprecated)..............................................20 Account Contact Relationship.................................................21 Account EntityType........................................................22 Appointment Entity Type....................................................40 BusinessPartner Entity Type..................................................46 CodeList Entity Type....................................................... 47 Contextual CodeList Entity Type...............................................48
    [Show full text]
  • Pyslet Documentation Release 0.6.20160201
    Pyslet Documentation Release 0.6.20160201 Steve Lay February 02, 2016 Contents 1 What’s New? 1 2 Compatibility 7 3 IMS Global Learning Consortium Specifications 13 4 The Open Data Protocol (OData) 101 5 Hypertext Transfer Protocol (RFC2616) 207 6 Other Supporting Standards 247 7 Welcome to Pyslet 357 Python Module Index 359 i ii CHAPTER 1 What’s New? As part of moving towards PEP-8 compliance a number of name changes are being made to methods and class at- tributes with each release. There is a module, pyslet.pep8, which contains a compatibility class for remapping missing class attribute names to their new forms and generating deprecation warnings, run your code with “python -Wd” to force these warnings to appear. As Pyslet makes the transition to Python 3 some of the old names will go away completely. It is still possible that some previously documented names could now fail (module level functions, function arguments, etc.) but I’ve tried to include wrappers or aliases so please raise an issue on Github if you discover a bug caused by the renaming. I’ll restore any missing old-style names to improve backwards compatibility on request. Finally, in some cases you are encouraged to derive classes from those defined by Pyslet and to override default method implementations. If you have done this using old-style names you will have to update your method names to prevent ambiguity. I have added code to automatically detect most problems and force fatal errors at runtime on construction, the error messages should explain which methods need to be renamed.
    [Show full text]
  • List of Published Standards
    Report Date : 2021-09-17 Cost Centre(s) : % LIST OF PUBLISHED STANDARDS Page No : 1 Of 3 Total Count: 41 Committee SANS Date Latest Reaffirmation Review/ Number Number Int Ed Ed Sansified Title Approved Amendment due Revision SABS/TC 165 SANS 60654-1:2017/IEC 60654-1:1993 2 1 Y Industrial-process measurement and control 2017-06-23 2022-06-23 equipment - operating conditions - Part 1: Climatic conditions SANS 61131-1:2017/IEC 61131-1:2003 2 Y Programmable controllers Part 1: General 2017-10-13 2022-10-13 information SANS 61131-2:2018/IEC 61131-2:2007 2 Y Programmable controllers Part 2: Equipment 2018-12-07 2023-12-07 requirements and tests SANS 61131-3:2018/IEC 61131-3:2013 2 Y Programmable controllers Part 3: 2018-07-20 2023-07-20 Programming languages SATR 61131-4:2017/IEC TR 61131-4:2004 1 Y Programmable controllers Part 4: User 2017-12-15 2022-12-15 guidelines SANS 61131-5:2018/IEC 61131-5:2000 1 Y Programmable controllers - Part 5: 2018-02-23 2023-02-23 Communications SANS 61131-6:2018/IEC 61131-6:2012 1 Y Programmable controllers - Part 6: Functional 2018-05-25 2023-05-25 safety SANS 61131-7:2018/IEC 61131-7:2000 1 Y Programmable controllers - Part 7:Fuzzy 2018-02-23 2023-02-23 control programming SATR 61131-8:2019/IEC TR 61131-8:2003 1 Y Programmable controllers - Part 8: Guidelines 2019-11-22 2024-11-22 for the application and implementation of programming languages SANS 61131-9:2020/IEC 61131-9:2013 1 Y Programmable controllers - Part 9: Single- 2020-05-29 2025-05-29 drop digital communication interface for small sensors and actuators (SDCI) SANS 61158-3-2:2021/IEC 61158-3-2:2019 2.1 1 Y Industrial communication networks - Fieldbus 2021-07-16 1 I A 2021-07-16 2026-07-16 specifications - Part 3-2: Data-link layer service definition - Type 2 elements.
    [Show full text]
  • Allegato 2 Piano ERTMS Evidenza Modifiche.Pdf
    Allegato 2 Piano Accelerato ERTMS revisione O con evidenza delle modifiche rispetto alla revisione N e-POD banca dati documentale RFI - download effettuato il 04/09/2020 19:18:20 stato di vigenza: IN VIGORE livello riservatezza Uso pubblico Piazza della Croce Rossa, 1 - 00161 Roma Rete Ferroviaria Italiana – Società per Azioni - Gruppo Ferrovie dello Stato Italiane Società con socio unico soggetta all’attività di direzione e coordinamento di Ferrovie dello Stato Italiane S.p.A. a norma dell’art. 2497 sexies del cod. civ. e del D.Lgs. n. 112/2015 Sede legale: Piazza della Croce Rossa, 1 - 00161 Roma Cap. Soc. euro 31.528.425.067,00 Iscritta al Registro delle Imprese di Roma ––– Cod. Fisc. 01585570581 e P. Iva 01008081000 – R.E.A. 758300 Codifica: PIANO DI SVILUPPO ERTMS/ETCS FOGLIO e GSM-R RFI TC.SCC SR RR AP 01 R05 O 1 di 130 PIANO DI SVILUPPO DI ERTMS (ETCS E GSM-R) SULLA RETE RFI Rev. Data Descrizione Verifica Tecnica Autorizzazione S. Buonincontri Aggiornamenti e stato di D. Caronti avanzamento attività in M. Ciaffi realizzazione rispetto al National Implementation S. Geraci O 23/07/2020 Plan e rimodulazione della G. Gallo F. Senesi e-POD banca dati documentale RFI - download effettuato il 04/09/2020 19:18:20 stato di vigenza: IN VIGORE livello riservatezza Uso pubblico proposta RFI del piano C. Iommazzo “accelerato” di rinnovamento tecnologico guidato da S. Marcoccio ERTMS G. Ridolfi D. Schiavoni PIANO DI SVILUPPO ERTMS/ETCS Codifica: FOGLIO 2 di 130 e GSM-R RFI TC.SCC RR AP 01 R05 O ELABORAZIONE DOCUMENTO VERIFICA EFFETTUATA Marco
    [Show full text]
  • ISO/IEC JTC 1 Information Technology
    ISO/IEC JTC 1 Information technology Big data Preliminary Report 2014 Our vision Our process To be the world’s leading provider of high Our standards are developed by experts quality, globally relevant International all over the world who work on a Standards through its members and volunteer or part-time basis. We sell stakeholders. International Standards to recover the costs of organizing this process and Our mission making standards widely available. ISO develops high quality voluntary Please respect our licensing terms and International Standards that facilitate copyright to ensure this system remains international exchange of goods and independent. services, support sustainable and equitable economic growth, promote If you would like to contribute to the innovation and protect health, safety development of ISO standards, please and the environment. contact the ISO Member Body in your country: www.iso.org/iso/home/about/iso_ members.htm This document has been prepared by: Copyright protected document ISO/IEC JTC 1, Information technology All rights reserved. Unless otherwise Cover photo credit: ISO/CS, 2015 be reproduced or utilized otherwise in specified,any form noor partby anyof this means, publication electronic may or mechanical, including photocopy, or posting on the internet or intranet, without prior permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester: © ISO 2015, Published in Switzerland Case postale 56 • CH-1211 Geneva 20 Tel.ISO copyright+41 22
    [Show full text]
  • Haris Kurtagic, SL-King Jason Birch, City of Nanaimo Geoff Zeiss, Autodesk Tim Berners-Lee, in Government Data Design Issues, Proposes
    Haris Kurtagic, SL-King Jason Birch, City of Nanaimo Geoff Zeiss, Autodesk Tim Berners-Lee, in Government Data Design Issues, proposes ○ Geodata on the web in raw form. ○ Raw geodata must be searchable How do you find raw geospatial data ? Data Catalogs Wouldn’t it be nice if… And see.. Searchable Raw Geospatial Data www.georest.org Open Data Protocol “The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today.” www.odata.org ODATA HTTP Atom AtomPUB JSON HTTP://.../vancouver/libraries <feed xmlns=http://www.w3.org/2005/Atom … > <title type="text">libraries</title> <id>http://…/vancouver/libraries(10)</id> <title type="text"></title> <entry> <content type="application/xml"> <m:properties> <d:library_name>Britannia</d:library_name> <d:latitude m:type="Edm.Double">49.2756486</d:latitude> <d:longitude m:type="Edm.Double">-123.0737717</d:longitude> <d:address>1661 Napier St</d:address> </m:properties> …..</entry> <entry>…</entry></feed> HTTP://.../vancouver/libraries ?$format=JSON {"d":[{"library_name":"Britannia","latitude":" 49.2756486","longitude":"- 123.0737717","address":"1661 Napier St"} , {..}] } HTTP Header accept: application/json OData Example Live OData Service from Vancouver OData Producers SharePoint 2010, SQL Azure, IBM WebSphere, … GeoREST OData Live Services Netflix, Open Goverment Data Initiative (OGDI), Stack Overflow, Vancouver, Edmonton, … City of Nanaimo OData Consumers Browsers, Odata Explorer, Excel 2010,…
    [Show full text]
  • SAP Analytics Cloud, Analytics Designer Developer Handbook
    SAP Analytics Cloud, analytics designer Developer Handbook Document Version: 5.1 – 2020-04-06 Table of Contents 1 Table of Contents Table of Contents ......................................................................................................................... 1 Figures .......................................................................................................................................... 7 1 About Analytics Designer .............................................................................................10 1.1 What Is an Analytic Application? .....................................................................................10 1.2 What Is Analytics Designer? ............................................................................................10 1.3 What Can You Do with Analytic Applications That You Can’t Do with Stories? ..............10 1.4 How Are Stories and Analytic Applications Related to Each Other? ...............................10 1.5 Why Do We Need Both Stories and Analytic Applications? ............................................11 1.6 What Is the Typical Workflow in Creating an Analytic Application? .................................11 1.7 What Are Typical Analytic Applications? .........................................................................12 1.8 How Does Scripting Work in Analytic Applications? ........................................................12 1.9 What’s the Scripting Language for Analytic Applications? ..............................................13 2 Getting
    [Show full text]
  • X2rail-1 Deliverable D7.1 Analysis of Existing Lines and Economic Models
    X2Rail-1 Project Title: Start-up activities for Advanced Signalling and Automation Systems Starting date: 01/09/2016 Duration in months: 36 Call (part) identifier: H2020-S2RJU-CFM-2015-01-1 Grant agreement no: 730640 Deliverable D7.1 Analysis of existing lines and economic models Due date of deliverable Month 09 Actual submission date 18-02-2019 Organization name of lead contractor for this deliverable 18-TTS Dissemination level PU Revision DB-001-02-R2 Deliverable template version: 02 (09/11/16) X2Rail-1 Deliverable D7.1 Analysis of existing lines and economic models Authors Author(s) Alstom Transport S.A. (ALS) Pierre Damien Jourdain AZD Praha SRO (AZD) Michal Pavel Lukas Michalik BOMBARDIER TRANSPORTATION SWEDEN AB (BTSE) Jorgen Mattisson INDRA (INDRA) Francisco Parrilla Thales Transportation Systems GMBH (TTS) Ana Millán Belen Losada Trafikverket – TRV (TRV) Jan Bystrom Contributor(s) ANSALDO STS S.p.A. (ASTS) Giovanni Canepa CAF Signalling S.L. (CAF) Ignacio Gonzalez Deutsche Bahn AG (DB) Julian Mohr MERMEC SPA (MERMEC) Vito Caliandro Siemens (SIE) Jose Manuel Mellado GA 730640 Page 2 of 165 X2Rail-1 Deliverable D7.1 Analysis of existing lines and economic models 1. Executive Summary The present document constitutes the first issue of Deliverable D7.1 “Analysis of existing lines and economic models” in the framework of the Project titled “Start-up activities for Advanced Signalling and Automation Systems” (Project Acronym: X2Rail-1; Grant Agreement No 730640). Although modern signalling systems are going to considerably reduce trackside equipment in the next years, a source of the innovation step proposed by the X2Rail-1 WP7 is to provide fully distributed control of remote trackside objects such as points, level crossings, etc., without requiring the necessity to install specialized trackside cabling and associated cable routes, ducting etc.
    [Show full text]
  • CAD Data Exchange
    CCAADD DDaattaa EExxcchhaannggee 2255..335533 LLeeccttuurree SSeerriieess PPrrooff.. GGaarryy WWaanngg Department of Mechanical and Manufacturing Engineering The University of Manitoba 1 BBaacckkggrroouunndd Fundamental incompatibilities among entity representations Complexity of CAD/CAM systems CAD interoperability issues and problems cost automotive companies a combined $1 billion per year (Brunnermeier & Martin, 1999). 2 BBaacckkggrroouunndd (cont’d) Intra-company CAD interoperability Concurrent engineering and lean manufacturing philosophies focus on the reduction of manufacturing costs through the outsourcing of components (National Research Council, 2000). 3 IInnffoorrmmaattiioonn ttoo bbee EExxcchhaannggeedd Shape data: both geometric and topological information Non-shape data: graphics data Design data: mass property and finite element mesh data Manufacturing data: NC tool paths, tolerancing, process planning, tool design, and bill of materials (BOM). 4 IInntteerrooppeerraabbiilliittyy MMeetthhooddss Standardized CAD package Standardized Modeling Kernel Point-to-Point Translation: e.g. a Pro/ENGINEER model to a CATIA model. Neutral CAD Format: e.g. IGES (Shape-Based Format ) and STEP (Product Data-Based Format) Object-Linking Technology: Use Windows Object Linking and Embedding (OLE) technology to share model data 5 IInntteerrooppeerraabbiilliittyy MMeetthhooddss (Ibrahim Zeid, 1990) 6 CCAADD MMooddeelliinngg KKeerrnneellss Company/Application ACIS Parasolid Proprietary Autodesk/AutoCAD X CADKey Corp/CADKEY X Dassault Systems/CATIA v5 X IMS/TurboCAD X Parametric Technology Corp. / X Pro/ENGINEER SDRC / I-DEAS X SolidWorks Corp. / SolidWorks X Think3 / Thinkdesign X UGS / Unigraphics X Unigraphics / Solid Edge X Visionary Design System / IronCAD X X (Dr. David Kelly 2003) 7 CCAADD MMooddeelliinngg KKeerrnneellss (cond’t) Parent Subsidiary Modeling Product Company Kernel Parametric Granite v2 (B- Pro/ENGINEER Technology rep based) Corporation (PTC) (www.ptc.com) Dassault Proprietary CATIA v5 Systems SolidWorks Corp.
    [Show full text]
  • Eine Optimierte ETCS-Architektur Für Regionalstrecken ETCS L1 – an Optimised ETCS Architecture for Regional Lines
    ETCS | ETCS www.eurailpress.de/archiv/etcs ETCS L1 – Eine optimierte ETCS-Architektur für Regionalstrecken ETCS L1 – an optimised ETCS architecture for regional lines Peter Laumen | Tim Kipshagen | Prof. Dr.-Ing. Nils Nießen as europäische Zugbeeinflussungssystem ETCS (European he European Train Control System (ETCS) is currently D Train Control System) wird aktuell auf den Hauptstrecken T being introduced on main lines, in particular in the TEN / (insbesondere den TEN-Korridoren) eingeführt. Auf Neben- und corridors. ETCS has not yet been regularly implemented on Regionalstrecken kommt ETCS jedoch bisher üblicherweise nicht regional and secondary lines, but some countries are awaiting Seiten der zur Anwendung. Einige Länder erwarten zukünftig günstige inexpensive future ETCS solutions for these lines. The use of Aachen ETCS-Lösungen für diese Streckenarten. Durch die Digitalisierung new digital technologies and the resulting digital interlocking und die daraus resultierenden ESTW bzw. digitalen Stellwerke makes it possible to optimise the existing ETCS architecture. (DSTW) kann die bisherige ETCS-Architektur optimiert werden. In addition to the possibility of generating ETCS telegrams RWTH Mit den Möglichkeiten der DSTW, Telegramme zur Laufzeit im Besucher in the digital interlocking (DI) at runtime, ETCS Level 1 (L1) für Stellwerk zu generieren und über Balisen an den Zug zu übertra- lines can also be designed dynamically, which results in ad- für gen, kann eine ETCS Level 1 Full Supervision (L1 FS)-Strecke dyna- ditional benefits. There are significant operating advantages misch gestaltet werden und dadurch einen Mehrwert generieren. with regard to speed restrictions, block sections, the trans- 2020 Es ergeben sich wesentliche betriebliche Vorteile u. a. bei Lang- mission of route specific information, the integration of level samfahrstellen, der Blockteilung, der fahrstraßenabhängigen In- crossings and shunting under ETCS, for example.
    [Show full text]
  • A Case Study on CAD/CAM Data Transfer in CIM Environment
    3 A Case Study on CAD/CAM data transfer in CIM Environment K. P. Mahadevan J.Mou M R. Henderson D. L. Shunk Department ofI&MSE Arizona State University Tempe, AZ 85287 US.A. Abstract This case study enumerates the steps involved in testing the data exchange among dissimilar CAD systems using a standard exchange mechanism and discusses the level of inter-operability that can be achieved to facilitate successful transfer of CAD data among three CAD software's namely ProlE version 17, I-DEAS Master series version 3.1 and AutoCAD release 13 in a CIM environment. First the Initial Graphics Exchange Specification (IGES) is used as the data exchange mechanism to test these software's using a standard test procedure. The same test procedure is then used to find out the effectiveness of the data exchange between ProlE and I­ DEAS using a different exchange standard called the Standard For Exchange Of Product Model Data (STEP). AutoCAD does not support STEP. Experimental results show that ProlE and I-DEAS have the capability to share complete CAD information but AutoCAD has some limitations in transferring information on surfaces and solids using IGES. By using the STEP translator, we are able to translate CAD data efficiently one way from ProlE to I-DEAS and vice versa but have some difficulty carrying out back and forth data transfer between tl1em. Computer Applications in Production and Engineering. F. Plonka and G. Oiling (Eds.) © 1997 IflP. Published by Chapman & Hall A case study on CAD/CAM data transfer in C/M environment 21 Keywords Computer Aided Design (CAD), Computer Aided Manufacturing (CAM), Computer Integrated Manufacturing (CIM), Inter-operability, Initial Graphics Exchange Specification (IGES), Standard For Exchange Of Product Model Data {STEP).
    [Show full text]
  • Today. for Tomorrow. for Us
    Today. For tomorrow. For us. ANNUAL REPORT 2019 ÖBB-INFRASTRUKTUR AG Contents CONSOLIDATED MANAGEMENT REPORT 2 CONSOLIDATED FINANCIAL STATEMENTS 80 A. Group structure and investments 2 Consolidated Income Statement 2019 80 B. General conditions and market environment 5 Consolidated Statement of Comprehensive Income 2019 81 C. Economic report and outlook 10 Consolidated Statement of Financial Position as of Dec 31, 2019 82 D. Research and development 29 Consolidated Statement of Cash Flows 2019 83 E. Group relationships 31 Consolidated Statement of Changes in Equity 2019 84 F. Opportunity and risk report 32 G. Non-financial statement 37 Notes to the Consolidated Financial Statements as of Dec 31, 2019 H. Notes to the Group Management Report 77 85 A. Basis and Methods 85 Glossary 78 B. Notes to the Consolidated Statement of Financial Position Statement pursuant to Section 124 (1) of the and the Consolidated Income Statement 106 Stock Exchange Act 79 C. Other Notes to the Consolidated Financial Statements 133 Audit Certificate 162 ÖBB-Infrastruktur Aktiengesellschaft Consolidated Management Report | Consolidated Financial Statements Consolidated Management Report A. Group structure and investments 2 The ÖBB-Infrastruktur Group must ensure the economic and efficient use of Austria's railway infrastructure and its aavailabilityvailability to all railway operators on a non-discriminatory basis. At the same time, the ÖBB-Infrastruktur Group builds Austria's railway infrastructure on behalf of the Republic of Austria. The financing of the capital expenditures in rail infrastructure development is ensured through the cash flow generated, outside capital and guarantees and investment grants from the federal government on the basis of multi-year master plans.
    [Show full text]