The document describes a domain specific language (DSL) called ERTMSFormalSpecs (EFS) that was created to formalize specifications for the European Rail Traffic Management System (ERTMS). EFS models 100% of the ERTMS business logic using requirements analysis, modeling, and automatic code generation. It addresses issues with the natural language ERTMS specifications such as structure, size, completeness, consistency and handling changes between releases. The goals of EFS are to provide a formal and unambiguous representation of the specifications that can be used for assessment, testing, visualization and future code generation activities.
CICS is the power of mainframe. It has all the capabilities to handle online transactions. The ppt covers highly useful CICS concepts to refresh your CICS knowledge quickly.
The document discusses ERTMSFormalSpecs (EFS), a domain specific language for formalizing ERTMS specifications. EFS aims to model 100% of the ERTMS business logic through requirements analysis, modeling, testing, and visualization. It addresses issues with the natural language ERTMS specifications such as structure, size, completeness and consistency. EFS models requirements as formal representations to assess specifications, enable animation and testing. It integrates with other tools for scenario editing, visualization and comparing outputs to production onboard units. EFS helps analyze proposed changes to specifications and reduce interpretation issues.
Read all our success stories! We are very proud of the achievements and relationships we created with our clients and partners. Contact us for more information info@ertmssolutions.com
This document discusses approaches for migrating data from Oracle's Financial Data Management Enterprise Edition (FDMEE) to its successor product, Oracle's Financial Data Management Enterprise Edition (FDMEE). It outlines two main approaches - using Oracle's migration utility or doing a full rebuild. The migration utility uses Oracle Data Integrator (ODI) under the hood and can automate some but not all aspects of the migration. A full rebuild takes more time but allows for cleaning up of unused artifacts and other improvements. Best practices are discussed such as designing the target system structure, rebuilding scripts with Jython, and thorough testing.
The document describes a vehicle management system provided by an Indian company. The company has a dedicated software and support team, operates in 9 countries, and integrates with major hardware manufacturers. It offers fleet management solutions including live vehicle tracking, dispatch, and web-based reporting features to over 15,000 assets for clients in several industries.
ISOBUS software stack is a pre-packaged software solution developed in compliance with ISO 11783 standard.
This software stack enables and manages the in-vehicle network communication between the agricultural tractor ECUs and implements ECUs.
https://www.embitel.com/isobus-software-stack-integration-services
New HyperWorks Pedestrian Impact Tool for vehicle engineering and CAE simulationAltair
The engineering challenges according to the pedestrian safety requirements have an important impact on the vehicle development time line and on vehicle design. The different pedestrian safety regulations that a vehicle has to fulfill (legal (ECE, GTR…) or consumer (EuroNCAP)) represent a high number of impact points that have to be defined depending on the regulation protocol. For each impact point, a FEM simulation has to be performed in order to evaluate the overall pedestrian protection performances. The integration of this process into an innovative virtual prototyping method needs a CAE tool allowing the automatic definition of the impact points and the automatic generation of ready-to-run FE models for impact simulation. Moreover, pedestrian requirements have a direct influence on vehicle design. That’s the reason why, an automatic definition of the impact points based on CAD design surfaces is a key to allow engineering judgment and design changes in the early phase of the vehicle development. The new HyperWorks Pedestrian Impact Tool, developed by Altair Engineering in cooperation with the Ford of Europe Pedestrian Protection Team, offers a perfect solution to these challenges. During the presentation, an overview of the tool capabilities will be given as well as results of an application on a Ford vehicle model.
Speakers
Dany Tapigue, Engineer, Ford Werke GmbH
CICS is the power of mainframe. It has all the capabilities to handle online transactions. The ppt covers highly useful CICS concepts to refresh your CICS knowledge quickly.
The document discusses ERTMSFormalSpecs (EFS), a domain specific language for formalizing ERTMS specifications. EFS aims to model 100% of the ERTMS business logic through requirements analysis, modeling, testing, and visualization. It addresses issues with the natural language ERTMS specifications such as structure, size, completeness and consistency. EFS models requirements as formal representations to assess specifications, enable animation and testing. It integrates with other tools for scenario editing, visualization and comparing outputs to production onboard units. EFS helps analyze proposed changes to specifications and reduce interpretation issues.
Read all our success stories! We are very proud of the achievements and relationships we created with our clients and partners. Contact us for more information info@ertmssolutions.com
This document discusses approaches for migrating data from Oracle's Financial Data Management Enterprise Edition (FDMEE) to its successor product, Oracle's Financial Data Management Enterprise Edition (FDMEE). It outlines two main approaches - using Oracle's migration utility or doing a full rebuild. The migration utility uses Oracle Data Integrator (ODI) under the hood and can automate some but not all aspects of the migration. A full rebuild takes more time but allows for cleaning up of unused artifacts and other improvements. Best practices are discussed such as designing the target system structure, rebuilding scripts with Jython, and thorough testing.
The document describes a vehicle management system provided by an Indian company. The company has a dedicated software and support team, operates in 9 countries, and integrates with major hardware manufacturers. It offers fleet management solutions including live vehicle tracking, dispatch, and web-based reporting features to over 15,000 assets for clients in several industries.
ISOBUS software stack is a pre-packaged software solution developed in compliance with ISO 11783 standard.
This software stack enables and manages the in-vehicle network communication between the agricultural tractor ECUs and implements ECUs.
https://www.embitel.com/isobus-software-stack-integration-services
New HyperWorks Pedestrian Impact Tool for vehicle engineering and CAE simulationAltair
The engineering challenges according to the pedestrian safety requirements have an important impact on the vehicle development time line and on vehicle design. The different pedestrian safety regulations that a vehicle has to fulfill (legal (ECE, GTR…) or consumer (EuroNCAP)) represent a high number of impact points that have to be defined depending on the regulation protocol. For each impact point, a FEM simulation has to be performed in order to evaluate the overall pedestrian protection performances. The integration of this process into an innovative virtual prototyping method needs a CAE tool allowing the automatic definition of the impact points and the automatic generation of ready-to-run FE models for impact simulation. Moreover, pedestrian requirements have a direct influence on vehicle design. That’s the reason why, an automatic definition of the impact points based on CAD design surfaces is a key to allow engineering judgment and design changes in the early phase of the vehicle development. The new HyperWorks Pedestrian Impact Tool, developed by Altair Engineering in cooperation with the Ford of Europe Pedestrian Protection Team, offers a perfect solution to these challenges. During the presentation, an overview of the tool capabilities will be given as well as results of an application on a Ford vehicle model.
Speakers
Dany Tapigue, Engineer, Ford Werke GmbH
S. Yakaiah's CV summarizes their professional experience and skills. They have over 10 years of experience working as a Tech Lead and Senior Engineer at Honeywell developing software for aircraft applications. Their roles included requirements analysis, software development, testing, and ensuring certification standards compliance. They also have experience developing flight control systems for Boeing 787 and working as a software consultant for the Department of Atomic Energy in India.
End-to-End Architectural Considerations for Supporting Telematics Solutions -...mfrancis
This document discusses architectural considerations for telematics solutions. It begins by reviewing the telematics market trends, including increasing penetration of embedded telematics systems in vehicles. It then covers solution considerations like operating environments and wireless network management. An end-to-end reference architecture is presented involving client, communication infrastructure, and backend server components. Finally, an IBM telematics reference implementation is described that demonstrates an on-demand managed client solution using WebSphere technologies.
S1000D is the European standard of technical publications or technical documentation being followed in Aerospace since 1980, which uses CSDB, a Common source database which is used for preparing, managing, and publishing technical information for a warship, or Aerospace, or even Civil airlines too.
Technical manuals (e.g. maintenance, user, training, operations, etc) published in electronic format are becoming more and more popular than paper based manuals for their interactivity, convenience and ease of use.
The document discusses various topics related to C*Cure security systems including new features in version 10.0, I-Star Edge vs. I-Star Pro readers, database options for reporting, data warehousing concepts, and considerations for system redundancy and virtualization. Global Implementation Group provides professional services and support for security systems and aims to discuss integration, reporting and advanced implementations.
ERTMS Solutions is specialized in the development of innovative products for the railway signalling world, and for a majority of them compatible with the European railway signalization standard ERTMS/ETCS.
The FleetBoard Solution and the Case for OSGi Technology - Hendrik Höfer, Mic...mfrancis
The document discusses the DispoPilot project, which developed a telematics solution for fleet management. It describes the software challenges in developing a mobile driver workstation unit with features like barcode scanning, navigation, and remote software updates. It also summarizes the technical components used, including an OSGi-based architecture, IBM J9/SMF virtual machine, and WebSphere Everyplace Device Manager for remote management.
Connectivity Solutions with InduSoft Web Studio and Software toolbox.AVEVA
The document discusses two products from Software Toolbox, Inc: TOP Server and OmniServer. TOP Server is an OPC UA server that connects industrial devices like PLCs to clients and provides diagnostic tools. It supports dynamic addressing, redundancy, and optimized performance. OmniServer connects a variety of non-PLC devices like scales, barcode scanners, and analyzers to bring their data together. The document provides an overview of the products and when each one should be used.
Tony Scalese, Edgewater Ranzal Oracle Financial Data Management (FDM) practice director, presented "Getting the Most Out of FDMEE in a Multiproduct Environment" at KScope14.
Our Customer (an Automotive Tier-I Supplier) encountered a major roadblock during software porting.Due to limited on-chip memory (RAM and ROM) of DsPIC 30F4011 platform, it became imperative for the customer to port highly-optimized embedded software to the EPS system.
Find out how a re-usable SAE J1939 compliant stack, best suited for commercial vehicles, was integrated with the EPS system to resolve the issue
- eTOD (electronic terrain and obstacle data) involves collecting digital terrain and obstacle data according to standards to improve aviation safety.
- It is driven by continued risks like CFIT (controlled flight into terrain) and industry demands for standardized data to power new applications.
- eTOD data must meet quality requirements and include metadata. It is captured for various areas around airports and used by systems like flight procedures and terrain awareness.
This document describes a dispensing system that uses a Baldor motion controller. It provides details on the controller's features such as memory, programming language support, I/O capabilities. It also describes the user interface software, programming tools, motion control capabilities, fieldbus options and how the system can be used for product selection applications using sensors.
This document describes a dispensing system that uses a Baldor motion controller. It provides details on the controller's features such as memory, programming language support, I/O capabilities. It also describes the user interface software, programming tools, motion control capabilities, fieldbus options and how the system can be used for product selection applications using sensors.
Solution Architect with 9 years of experience in solutioning, designing, developing and integrating Network Management Solutions using Ericsson Experience Manager, Customer Experience Management, ENIQ, OpenNMS, Core Java, SQL, PL/SQL, Java-J2EE technologies, Web Content Management, OFBiz, Javascript, XML, UNIX scripting and other Ericsson proprietary products.
Functional expertise includes
o Designing Solution Architecture, Database.
o Implementation in various Java-J2EE technologies like Core Java, Struts, Hibernate, Spring MVC, AJAX, EJB, Restful Web Services, Flex, OFBiz, JSF-Seam, Jboss Portal
o Webcontent Management using Alfresco Content Management, Interwoven Web Content Management
Executed Roles include
o As Solution Architect for designing Service Models, KPIs and Adaptations of COTS products like Ericsson Experience Manager (EEM).
o As Solution Architect for designing and developing extraction algorithm for complex database architecture following several standards like base64 decoding, JAXB Parser and normal PL/SQL extraction.
o As Solution Architect for designing Database, Flex Cairngorm Framework, Spring MVC-Hibernate Integration of Web based Dashboard Solutions (CXO Dashboard)
o As Team Lead for designing Portal site of several State Governments using Alfresco Content Management, JBoss Portal, Core Java
o As Scrum member for ERP Solutions using OFBiz (J2EE based ERP Solution), JavaScripts, JUnit
o As developer for development using EJB, Restful Web Services, Struts, Hibernate, JUnit, AJAX etc
o As trainer of Ericsson Experience Manager (EEM), Customer Experience Manager (CEM), OpenNMS, CXO Dashboard, Java-J2EE to several teams
At exactEarth, we have a lot of formats for the same AIS data. We had a proliferation of ad-hoc converters that developers had written with varying quality and performance.
By modelling the problem of format conversion as a graph traversal problem, I was able to create a library of battle tested code that could dynamically produce the converters needed to make the task of format conversion simple for developers.
The Spansion® Traveo™ microcontrollers are based on the ARM® Cortex®-R5 core and will deliver high performance, enhanced human-machine interfaces, high-security and advanced networking protocols tailored for a broad range of automotive applications such as electrification, body electronics, battery management, automotive cluster displays, HVAC and ADAS.
Overcoming the Complexities of AIXM with Model Based Data IntegrationSafe Software
FME is a powerful tool for working with AIXM data. The document discusses how FME can be used to:
1) Read, write, transform, and validate AIXM data in various versions and encodings.
2) Visualize and analyze AIXM data in 3D for applications like airspace management and obstacle avoidance.
3) Integrate AIXM data with other systems and formats through automated workflows for tasks like data migration, validation, and distribution via web services.
Overcoming the Complexities of AIXM with Model Based Data IntegrationSafe Software
The Aeronautical Information Exchange Model (AIXM5) is an open standard that was designed to exchange information, (like airspace, navigation aids, runways, etc.) between databases, messaging systems and GIS.
For any data exchange system, dealing with the volume and variety of data can be a challenge. The AIXM5 standard is also rather complex. Many AIXM users find that sharing, visualizing, or integrating any of that data can be difficult.
But it doesn’t have to be. In this webinar, learn how you can use data integration with AIXM to:
- Extract, process and build AIXM objects and geometries
- Overcome object to relational difficulties
- Migrate from AIXM 4.5 to 5.1
- Easily manage schema changes and extensions
- Automate validation and updates
- Integrate with web services and messaging applications
By automating data transfer with AIXM and data integration, you can both improve internal operations and ease regulatory compliance.
The document discusses frameworks and patterns for reusable software architectures in C++ network programming. It provides an overview of product line architectures and how frameworks can be used to support concurrent and networked applications. The document outlines some key frameworks in ACE (Adaptive Communication Environment) and how they embody commonality and variability. It also discusses design patterns used in a networked logging service example.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
High performance Serverless Java on AWS- GoTo Amsterdam 2024Vadym Kazulkin
Java is for many years one of the most popular programming languages, but it used to have hard times in the Serverless community. Java is known for its high cold start times and high memory footprint, comparing to other programming languages like Node.js and Python. In this talk I'll look at the general best practices and techniques we can use to decrease memory consumption, cold start times for Java Serverless development on AWS including GraalVM (Native Image) and AWS own offering SnapStart based on Firecracker microVM snapshot and restore and CRaC (Coordinated Restore at Checkpoint) runtime hooks. I'll also provide a lot of benchmarking on Lambda functions trying out various deployment package sizes, Lambda memory settings, Java compilation options and HTTP (a)synchronous clients and measure their impact on cold and warm start times.
More Related Content
Similar to ERTMSFormalSpecs Presentation 9/10/2015
S. Yakaiah's CV summarizes their professional experience and skills. They have over 10 years of experience working as a Tech Lead and Senior Engineer at Honeywell developing software for aircraft applications. Their roles included requirements analysis, software development, testing, and ensuring certification standards compliance. They also have experience developing flight control systems for Boeing 787 and working as a software consultant for the Department of Atomic Energy in India.
End-to-End Architectural Considerations for Supporting Telematics Solutions -...mfrancis
This document discusses architectural considerations for telematics solutions. It begins by reviewing the telematics market trends, including increasing penetration of embedded telematics systems in vehicles. It then covers solution considerations like operating environments and wireless network management. An end-to-end reference architecture is presented involving client, communication infrastructure, and backend server components. Finally, an IBM telematics reference implementation is described that demonstrates an on-demand managed client solution using WebSphere technologies.
S1000D is the European standard of technical publications or technical documentation being followed in Aerospace since 1980, which uses CSDB, a Common source database which is used for preparing, managing, and publishing technical information for a warship, or Aerospace, or even Civil airlines too.
Technical manuals (e.g. maintenance, user, training, operations, etc) published in electronic format are becoming more and more popular than paper based manuals for their interactivity, convenience and ease of use.
The document discusses various topics related to C*Cure security systems including new features in version 10.0, I-Star Edge vs. I-Star Pro readers, database options for reporting, data warehousing concepts, and considerations for system redundancy and virtualization. Global Implementation Group provides professional services and support for security systems and aims to discuss integration, reporting and advanced implementations.
ERTMS Solutions is specialized in the development of innovative products for the railway signalling world, and for a majority of them compatible with the European railway signalization standard ERTMS/ETCS.
The FleetBoard Solution and the Case for OSGi Technology - Hendrik Höfer, Mic...mfrancis
The document discusses the DispoPilot project, which developed a telematics solution for fleet management. It describes the software challenges in developing a mobile driver workstation unit with features like barcode scanning, navigation, and remote software updates. It also summarizes the technical components used, including an OSGi-based architecture, IBM J9/SMF virtual machine, and WebSphere Everyplace Device Manager for remote management.
Connectivity Solutions with InduSoft Web Studio and Software toolbox.AVEVA
The document discusses two products from Software Toolbox, Inc: TOP Server and OmniServer. TOP Server is an OPC UA server that connects industrial devices like PLCs to clients and provides diagnostic tools. It supports dynamic addressing, redundancy, and optimized performance. OmniServer connects a variety of non-PLC devices like scales, barcode scanners, and analyzers to bring their data together. The document provides an overview of the products and when each one should be used.
Tony Scalese, Edgewater Ranzal Oracle Financial Data Management (FDM) practice director, presented "Getting the Most Out of FDMEE in a Multiproduct Environment" at KScope14.
Our Customer (an Automotive Tier-I Supplier) encountered a major roadblock during software porting.Due to limited on-chip memory (RAM and ROM) of DsPIC 30F4011 platform, it became imperative for the customer to port highly-optimized embedded software to the EPS system.
Find out how a re-usable SAE J1939 compliant stack, best suited for commercial vehicles, was integrated with the EPS system to resolve the issue
- eTOD (electronic terrain and obstacle data) involves collecting digital terrain and obstacle data according to standards to improve aviation safety.
- It is driven by continued risks like CFIT (controlled flight into terrain) and industry demands for standardized data to power new applications.
- eTOD data must meet quality requirements and include metadata. It is captured for various areas around airports and used by systems like flight procedures and terrain awareness.
This document describes a dispensing system that uses a Baldor motion controller. It provides details on the controller's features such as memory, programming language support, I/O capabilities. It also describes the user interface software, programming tools, motion control capabilities, fieldbus options and how the system can be used for product selection applications using sensors.
This document describes a dispensing system that uses a Baldor motion controller. It provides details on the controller's features such as memory, programming language support, I/O capabilities. It also describes the user interface software, programming tools, motion control capabilities, fieldbus options and how the system can be used for product selection applications using sensors.
Solution Architect with 9 years of experience in solutioning, designing, developing and integrating Network Management Solutions using Ericsson Experience Manager, Customer Experience Management, ENIQ, OpenNMS, Core Java, SQL, PL/SQL, Java-J2EE technologies, Web Content Management, OFBiz, Javascript, XML, UNIX scripting and other Ericsson proprietary products.
Functional expertise includes
o Designing Solution Architecture, Database.
o Implementation in various Java-J2EE technologies like Core Java, Struts, Hibernate, Spring MVC, AJAX, EJB, Restful Web Services, Flex, OFBiz, JSF-Seam, Jboss Portal
o Webcontent Management using Alfresco Content Management, Interwoven Web Content Management
Executed Roles include
o As Solution Architect for designing Service Models, KPIs and Adaptations of COTS products like Ericsson Experience Manager (EEM).
o As Solution Architect for designing and developing extraction algorithm for complex database architecture following several standards like base64 decoding, JAXB Parser and normal PL/SQL extraction.
o As Solution Architect for designing Database, Flex Cairngorm Framework, Spring MVC-Hibernate Integration of Web based Dashboard Solutions (CXO Dashboard)
o As Team Lead for designing Portal site of several State Governments using Alfresco Content Management, JBoss Portal, Core Java
o As Scrum member for ERP Solutions using OFBiz (J2EE based ERP Solution), JavaScripts, JUnit
o As developer for development using EJB, Restful Web Services, Struts, Hibernate, JUnit, AJAX etc
o As trainer of Ericsson Experience Manager (EEM), Customer Experience Manager (CEM), OpenNMS, CXO Dashboard, Java-J2EE to several teams
At exactEarth, we have a lot of formats for the same AIS data. We had a proliferation of ad-hoc converters that developers had written with varying quality and performance.
By modelling the problem of format conversion as a graph traversal problem, I was able to create a library of battle tested code that could dynamically produce the converters needed to make the task of format conversion simple for developers.
The Spansion® Traveo™ microcontrollers are based on the ARM® Cortex®-R5 core and will deliver high performance, enhanced human-machine interfaces, high-security and advanced networking protocols tailored for a broad range of automotive applications such as electrification, body electronics, battery management, automotive cluster displays, HVAC and ADAS.
Overcoming the Complexities of AIXM with Model Based Data IntegrationSafe Software
FME is a powerful tool for working with AIXM data. The document discusses how FME can be used to:
1) Read, write, transform, and validate AIXM data in various versions and encodings.
2) Visualize and analyze AIXM data in 3D for applications like airspace management and obstacle avoidance.
3) Integrate AIXM data with other systems and formats through automated workflows for tasks like data migration, validation, and distribution via web services.
Overcoming the Complexities of AIXM with Model Based Data IntegrationSafe Software
The Aeronautical Information Exchange Model (AIXM5) is an open standard that was designed to exchange information, (like airspace, navigation aids, runways, etc.) between databases, messaging systems and GIS.
For any data exchange system, dealing with the volume and variety of data can be a challenge. The AIXM5 standard is also rather complex. Many AIXM users find that sharing, visualizing, or integrating any of that data can be difficult.
But it doesn’t have to be. In this webinar, learn how you can use data integration with AIXM to:
- Extract, process and build AIXM objects and geometries
- Overcome object to relational difficulties
- Migrate from AIXM 4.5 to 5.1
- Easily manage schema changes and extensions
- Automate validation and updates
- Integrate with web services and messaging applications
By automating data transfer with AIXM and data integration, you can both improve internal operations and ease regulatory compliance.
The document discusses frameworks and patterns for reusable software architectures in C++ network programming. It provides an overview of product line architectures and how frameworks can be used to support concurrent and networked applications. The document outlines some key frameworks in ACE (Adaptive Communication Environment) and how they embody commonality and variability. It also discusses design patterns used in a networked logging service example.
Similar to ERTMSFormalSpecs Presentation 9/10/2015 (20)
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
High performance Serverless Java on AWS- GoTo Amsterdam 2024Vadym Kazulkin
Java is for many years one of the most popular programming languages, but it used to have hard times in the Serverless community. Java is known for its high cold start times and high memory footprint, comparing to other programming languages like Node.js and Python. In this talk I'll look at the general best practices and techniques we can use to decrease memory consumption, cold start times for Java Serverless development on AWS including GraalVM (Native Image) and AWS own offering SnapStart based on Firecracker microVM snapshot and restore and CRaC (Coordinated Restore at Checkpoint) runtime hooks. I'll also provide a lot of benchmarking on Lambda functions trying out various deployment package sizes, Lambda memory settings, Java compilation options and HTTP (a)synchronous clients and measure their impact on cold and warm start times.
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
"Scaling RAG Applications to serve millions of users", Kevin GoedeckeFwdays
How we managed to grow and scale a RAG application from zero to thousands of users in 7 months. Lessons from technical challenges around managing high load for LLMs, RAGs and Vector databases.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Northern Engraving | Nameplate Manufacturing Process - 2024Northern Engraving
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
The Department of Veteran Affairs (VA) invited Taylor Paschal, Knowledge & Information Management Consultant at Enterprise Knowledge, to speak at a Knowledge Management Lunch and Learn hosted on June 12, 2024. All Office of Administration staff were invited to attend and received professional development credit for participating in the voluntary event.
The objectives of the Lunch and Learn presentation were to:
- Review what KM ‘is’ and ‘isn’t’
- Understand the value of KM and the benefits of engaging
- Define and reflect on your “what’s in it for me?”
- Share actionable ways you can participate in Knowledge - - Capture & Transfer
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
"$10 thousand per minute of downtime: architecture, queues, streaming and fin...Fwdays
Direct losses from downtime in 1 minute = $5-$10 thousand dollars. Reputation is priceless.
As part of the talk, we will consider the architectural strategies necessary for the development of highly loaded fintech solutions. We will focus on using queues and streaming to efficiently work and manage large amounts of data in real-time and to minimize latency.
We will focus special attention on the architectural patterns used in the design of the fintech system, microservices and event-driven architecture, which ensure scalability, fault tolerance, and consistency of the entire system.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
This talk will cover ScyllaDB Architecture from the cluster-level view and zoom in on data distribution and internal node architecture. In the process, we will learn the secret sauce used to get ScyllaDB's high availability and superior performance. We will also touch on the upcoming changes to ScyllaDB architecture, moving to strongly consistent metadata and tablets.
1. ERTMSFormalSpecs (EFS)
A domain specific language to formalize ERTMS
specifications
Laurent Ferier – EFS Project Manager and Software Architect
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
1
2. 13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
2
Introduction
Context
AGENDA
4. The Challenge
Specification of the EVC behavior
• Normative documents
– Subset-026 : SRS
– Subset-027 : JRU
– Subset-034 : TIU
• Additional documents
– DMI start & stop conditions
– Requirements scope identification (trackside,
onboard, system, rolling stock)
• Issues
– Natural language
– Structure
– Size
– Completeness
– Consistency
– Releases
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
4
5. Impact
• All stakeholders involved
– Specifiers (ERA, Unisig, …)
– System supplier
– Users (IM, EUG, …)
• Impact
– Interpretation issues
• Expected behavior
• Impact of a change
– Integration and interoperability
– Safety
– Maintenance
• Costs
– Development
– Maintenance
• Rewriting the requirements is out of scope
– The industry needs to address those issues
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
5
6. 13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
6
Introduction
Context
Requirement management
AGENDA
7. ERTMSFormalSpecs
Objective: model 100% ERTMS Business Logic
Process and project management, Requirements analysis,
Traceability, Domain Specific Language (DSL), Diagrams,
Tests, Visualization, …
ERTMS Specifications
CASE tool
Target
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
7
Assess the specification
(visualization , tests, …)
Current
Code generation
(language, coding rules, …)
Future
Version 3.4.0
8. Objectives
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
8
Requirements elicitation
• Understandable
• Check completeness / consistency
• Does it match customer needs
• Provide a structure
• Traced to original requirements
Tests
• Test sequences validation
• Reference OBU
Future
Design and implementation
• Code generation
9. Requirements handling
• Subset-026, 027, 034
– More than 7000 requirements,
– 4500 applicable to the OBU
• Requirements management
– Create the inventory
• Encode (copy & paste)
• Verify against text file
– Categorize
• Identify the scope
• Functional blocs (project dashboard)
– Fill the gaps with hypothesis
– Comment
• Traceability
– Metrics
– Handle changes
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
9
11. Requirements
Scope
Category and dashboard
Traceability
Metrics
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
11
Live presentation
12. 13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
12
Introduction
Context
Requirement management
Modelling
AGENDA
13. Modelling in EFS
• Translation of requirements into a formal representation
– Well defined
– Unique interpretation
• Purpose
– Assess requirements
– Animation
– Testing
– Visualization
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
13
14. Model properties
● As close as possible to the requirements
– To be understood by domain specialists
– Should match Subset-026 expressivity
– High level artifacts
• State machines
• Braking curves
● Traceability
– References the requirements covered
by the model
– Comments
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
14
15. EFS Model
Input OutputInternal
Interpretation model
Input
Input
Input
Output
Output
Output
Validation +
Business
Business
Cleanup
Cleanup
Cleanup
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
15
16. Structures
● Data types
– Ranges
• Speed, Distance, Length, …
– Enumerations
• Level, Mode, Q_SCALE, …
– Structures
• Messages and packets,
• Structured data (TSR, LX, …)
– Bounded collections
• Several TSRs, several LXs
– State machines
● Functions
– Compute a value based on its parameters
• No side effect
● Procedures
– Updates the system’s state
● Rules
– Triggers the system behavior
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
16
18. Expressions and statements
• Expressions
– Used to compute values
– Typical expression language
• Binary expressions
• Unary expressions
• Operator precedence
• Functions calls
– Specificities
• Functional operators to express operations over collections
• Statements
– Used to alter the system state
– Assignment
– Procedure call
– Operations over collections (APPLY)
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
18
19. Interpretation model
• System state stored in variables
– Input messages
– Internal state
– Output data
• Interpretation machine
– Provided by rules
– Evaluation does not rely on side effect
• Evaluate the rules that should be activated according to their precondition values
• Compute the new value
• Apply the changes on the system (all at once)
– One interpretation model:
• High level structures (state diagrams, braking curves)
– translated into rules, and interpreted as such
– Built back from rules when displayed
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
19
20. State machines : Information built back from model
(Transitions not expressed as such in Subset-026)
21. State machines : Information built back from model
(not expressed as state machine in Subset-026)
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
21
23. Domain Specific Language coverage
• Typical data structures, used to describe
– internal data used to model concepts of chapter 2 and 3
– packets of chapter 7, messages from chapter 8
– functions, also used to model tables
• State machines, used to describe
– mode transitions from chapter 4
– procedures of chapter 5
• Rule based interpretation machine
– to model system behaviour (all chapters)
• Braking curves
– Huge amount of chapter 3
Chapter 1
Chapter 2
Chapter 3
Chapter 4
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Ch.3 Brake
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
23
24. 13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
24
Traction/Braking models
Trackside related Inputs
Speed & Distance
Monitoring
Trackside Speed
Restrictions
Gradients
Track conditions
powerless section &
brake inhibition
Reduced Adhesion
conditions
Speed and distance limits:
LoA
EoA / SvL
Location from SR distance
National Values
Trackside integrated correction factors:
Kv_int, Kr_int, Kt_int
Available adhesion
EB confidence level
SB command inhibition in TSM
EB command revocation in CSM/TSM
Guidance curve inhibition
A_NVMAXREDADH under reduced adhesion
Service Brake feedback inhibition
Release Speed
Conversion
Model
Brake
percentage
Acceleration /
Deceleration
due to Gradient
Determination of
the supervised
targets
Determination of
brake deceleration
curves:
EBD
SBD
GUI
Supervision limits:
Emergency brake intervention (EBI)
Service brake intervention (SBI)
Warning (W)
Permitted speed (P)
Indication (I)
Pre-Indication location
Release speed monitoring start
location
Speed and distance
monitoring commands
TI commands
Emergency brake command
Service brake command
TCO command
DMI commands:
Normal status
Indication status
Overspeed status
Warning status
Intervention status
Calculation of decelerations:
A_safe(v,d) for EBD curve
A_expected(v,d) for SBD curve
A_normal_service(v,d) for GUI curve
Calculation of
brake build up times:
T_bs for SBI limit
T_be for EBI limit
A_gradient
TI commands
Traction model
Fixed Values
Onboard correction factors:
Kdry_rst, Kwet_rst, Kn
Train related
Inputs
Braking model
OR
Brake percentage
SB interface
SB command implemented
SB feedback implemented
TCO interface
Nominal rotating mass
Train length
Fixed Values
Maximum train speed
A_brake_emergency
A_brake_service
A_brake_normal_service
T_brake_service
T_brake_emergency
MRSP
Train position
/ speed /
acceleration
track conditions
Kdry_rst / Kwet_rst /
Kv_int / Kr_int /
reduced adhesion
TRK speed
restrictions /
Max train
speed
Electro-pneumatic brake
Kt_int
speed / distance
limits
DMI
commands
Brake
position
Traction
model
Special Brakes
Electro-pneumatic brake
Eddy current brake
Magnetic shoe brake
Regenerative brake
Braking curves
25. Braking curves modeling
• Model by functional composition
– Speed restriction example: TSRs
• Single TSR
• Several TSRs
– Handle other speed
restrictions
• Provides a complex
speed profile
• Explanation is available
FUNCTION TSRSpeedRestriction(
aTSR : TemporarySpeedRestriction
Distance : Default.BaseTypes.Distance
) RETURNS Default.BaseTypes.Speed
// During TSR
aTSR.Location <= Distance AND
Distance < aTSR.Location + TSRLength (aTSR)
=> aTSR.Speed
// Outside TSR
=> BaseTypes.Speed.MaxSpeed
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
25
FUNCTION SpeedRestrictions(
Distance : Default.BaseTypes.Distance
) RETURNS Default.BaseTypes.Speed
// Value
=>
(REDUCE TSRs USING
MIN(
First => TSRSpeedRestriction(X, d),
Second => RESULT)
INITIAL_VALUE MaxSpeedFunction
)(Distance)
26. Deceleration factors
• The same technique is applied to compute deceleration
factors
– Surfaces instead of step functions
• Computation of the deceleration curves
– based on P (variant SBI, EBI)
– and the deceleration factor
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
26
27. Traction/Braking models
Trackside related Inputs
Speed & Distance
Monitoring
Trackside Speed
Restrictions
Gradients
Track conditions
powerless section &
brake inhibition
Reduced Adhesion
conditions
Speed and distance limits:
LoA
EoA / SvL
Location from SR distance
National Values
Trackside integrated correction factors:
Kv_int, Kr_int, Kt_int
Available adhesion
EB confidence level
SB command inhibition in TSM
EB command revocation in CSM/TSM
Guidance curve inhibition
A_NVMAXREDADH under reduced adhesion
Service Brake feedback inhibition
Release Speed
Conversion
Model
Brake
percentage
Acceleration /
Deceleration
due to Gradient
Determination of
the supervised
targets
Determination of
brake deceleration
curves:
EBD
SBD
GUI
Supervision limits:
Emergency brake intervention (EBI)
Service brake intervention (SBI)
Warning (W)
Permitted speed (P)
Indication (I)
Pre-Indication location
Release speed monitoring start
location
Speed and distance
monitoring commands
TI commands
Emergency brake command
Service brake command
TCO command
DMI commands:
Normal status
Indication status
Overspeed status
Warning status
Intervention status
Calculation of decelerations:
A_safe(v,d) for EBD curve
A_expected(v,d) for SBD curve
A_normal_service(v,d) for GUI curve
Calculation of
brake build up times:
T_bs for SBI limit
T_be for EBI limit
A_gradient
TI commands
Traction model
Fixed Values
Onboard correction factors:
Kdry_rst, Kwet_rst, Kn
Train related
Inputs
Braking model
OR
Brake percentage
SB interface
SB command implemented
SB feedback implemented
TCO interface
Nominal rotating mass
Train length
Fixed Values
Maximum train speed
A_brake_emergency
A_brake_service
A_brake_normal_service
T_brake_service
T_brake_emergency
MRSP
Train position
/ speed /
acceleration
track conditions
Kdry_rst / Kwet_rst /
Kv_int / Kr_int /
reduced adhesion
TRK speed
restrictions /
Max train
speed
Electro-pneumatic brake
Kt_int
speed / distance
limits
DMI
commands
Brake
position
Traction
model
Special Brakes
Electro-pneumatic brake
Eddy current brake
Magnetic shoe brake
Regenerative brake
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
27
Braking curves
28. Braking curves comparative results
• Comparison with ERA braking curve
spreadsheet
– Tool differences
• ERA spreadsheet handle a single target
• whereas EFS handles complex speed profiles
• Version 3.3.0 vs version 3.4.0
– Results
• Same results for the simplest cases (modulo ɛ)
• Similar results for complex deceleration factors
– due to discrete computation in the spreadsheet
– acceptable : initial train speed=140km/h induced Δ=20cm
– note : acceptable error not defined in Subset26
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
28
29. 13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
29
Introduction
Context
Requirement management
Modelling
Testing
AGENDA
30. Testing
• Objectives
– Functional tests, related to Subset-026 requirements
• Make sure that the model behaves as required
• 100% model in the loop testing
– Integration tests
• As expressed in Subset-076
• Specific translations from Subset-076 database
• Test description
– Actions
• Statements
• Used to trigger the model
– Expectations
• Boolean expressions
• Check that the condition is respected
• Instantaneous / Continuous
• Deadline
• Traceability
– References the requirements covered by the test
– Comments
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
30
31. Test description and execution
Execution
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
31
32. Testing (continued)
• White box testing
• Traces available (for investigation)
• Folding and unfolding
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
32
33. Functional Tests
Braking curves
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
33
Live presentation
34. 13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
34
Introduction
Context
Requirement management
Modelling
Testing
Visualization
AGENDA
35. Open interface
● EFS provides an open interface
– Access the model
– Drive the simulation
● Plug additional tools to EFS
– a DMI which displays the system state
– a animator, to drive the train (more later)
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
35
36. Open interface
WCF software bus
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
36
WCF software bus
38. Current status and next steps
• Modeling status
– Subset-026: 4156 applicable requirements (out of 6389)
– Subset-027 : 402 applicable requirements (out of 427)
– Subset-034 : 71 applicable requirements (out of 191)
– Modeled: 3777
– Completion: more than 80 %
• Testing
– Unit tests: 13% formally tested
– Subset-076:
• 6 full sequences completed.
• 2 ongoing sequences
• Next steps
– Complete model coverage
– Complete formal functional test coverage
– Complete Subset-076 test coverage
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
38
39. 13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
39
Introduction
Context
Requirement management
Modelling
Testing
Visualization
Current status
Usages
Subset-076
AGENDA
40. Scope of Subset 076
● Subset 076
– Define interoperability tests between trackside & trainborne
• Inputs from either trackside or driver
• Expected output from EVC
– Define EVC integration tests
– Available as word documents, generated from an Access database
The idea is to apply Subset-076 tests to EFS model.
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
40
41. ● Integration model
– Source is the (non formal) subset 076 Access database
– Imported as structured text in the EFS test database
– Access databases are no more useful
– Automate the translation process
– Some parts might not be automated
The same translation rules can be used
to translate several test cases
Textual translation database can be used
to translate new releases
Subset-076 and EFS
S76 Access
databases
Textual import
EFS tests
database
Text
Model
Textual
tranlations
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
41
43. 13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
43
Introduction
Context
Requirement management
Modelling
Testing
Visualization
Current status
Usages
Subset-076
Analyze CR
AGENDA
44. CR1084
Problem description
● Current situation
– Two successive targets
• Pre-indication should happen 7s before indication point
– Second target too close from the first one.
• Insufficient time for the driver to react adequately to reach the new target speed
• Intervention is inevitable.
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
44
46. CR1084
ERA Solution
● Proposed by ERA
– Formally defined in ERA_solution_proposal_for_CR1084_230914
– Idea
• When several targets are too close one to the others,
apply the display algorithms to the most restrictive target
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
46
48. CR1084
EUG Solution
● Proposed by ERTMS User’s Group
– Formally defined in CR1084 EUG proposal 20141119_SG 20141125
– Idea
• When several targets are too close one to the others,
switch from Target1 to Target2 as soon as the train passes the pre-indication location
for the second target
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
48
50. Test description
● Use EFS functional tests to describe the problem
– Train characteristics (brakes, …) and train state (Level 1, FS)
– Speed restrictions and MA
– Points of interest
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
50
51. Step by step test animation
● Test description
– Used to animate the model
• Step-by-step fashion
• Evaluate what happens in the model
• Display using DMI
• Display braking curves specifics
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
51
52. Live execution
● Animate the test sequence
– Get dynamic behavior of the system
– Create videos
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
52
53. CR analysis
The impact of a spec modification is difficult to evaluate
because one cannot animate text documents
● We used EFS to analyze behavior-related CRs
– Create test scenarios
• Graphical editor
• Structure editor for complex data entry
– Allows to model the various proposed solutions
• Access to the full model
• Tools to investigate the model behavior
– Displays the system dynamics
• DMI integration
• Train animator
● Efficient for CR implementation impact analysis
– These analysis + results were prepared in 2 man-days
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
53
54. Conclusions
● Results presented to
– ERA (December the 17th 2014)
– EUG (the same day)
Positively impressed : it was the first time they could directly see
the impact of a change
● Next steps
– Analysis of other CRs
• CR1166, CR1187, CR1249
– More flexibility when animating the train
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
54
55. Scenario Editor
● Objectives
– Create test scenario
– Drives the animation process
● Designed with the help EUG
– Currently used to analyze more CRs
● Features
– Graphically specify events sent to the train
• Repository of events (train data, driver actions, …)
• Custom event (balise messages, …)
– Graphically specify the train speed
– Display braking curves
• During test creation
• During execution
– Display specific system changes
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
55
56. Scenario Editor
CR Analysis
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
56
Live presentation
57. Current project
ERTMSFormalSpecs vs production OBU
● Based on trace files
– Feed the model
– Compare the results
● Ongoing work…
– … but current results can be shown
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
57
59. 13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
59
Introduction
Context
Requirement management
Modelling
Testing
Visualization
Current status
Usages
Subset-076
Analyze CR
Reference EVC
Model other systems
AGENDA
60. IXL modelling – objectives and team
● Objectives
– Assess completeness and consistency of IXL specs
– Demonstrate ERTMSFormalSpecs is suitable to model IXL
– Test learning curve for signalling engineer in
ERTMSFormalSpecs
– Evaluate effort to model 100% of IXL specs
● Team
– 1 EFS modelling expert
– 1 Signalling expert
– 1 Junior signalling consultant
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
60
61. Scope of the prototype
● Model of the Interlocking
– Points
– Signals
– Treadles
– Segments
– Routes
● Behaviour
– MA allocation
– Monocinetic conditions
– Route release
● Out of scope
– EBP commands
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
61
62. Demo – The big picture
Requirements analysis
Modelling
Functional tests
Animation
• Show system state
• Execute what-if scenario
Track simulatorERTMS Formal Specs
Specifications
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
62
63. Results
● Metrics
– POC :
• 872 requirements in full specification
• 116 out of 172 implementable requirements
● Results
– ERTMSFormalSpecs is suitable to model IXL
– Modelling
• Allowed to detect grey areas in the specification
– What are the assumptions ?
– Specific operational rules ?
– Exact concept definition ?
– Learning curve ERTMSFormalSpecs is short :
• 3 weeks
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
63
65. 13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
65
Introduction
Context
Requirement management
Modelling
Testing
Visualization
Current status
Usages
Subset-076
Analyze CR
Reference EVC
Model other systems
Generate Code
AGENDA
66. Code generation
● Prototype
– Simple model + tests
– Generate C code
– Verify that the tests are still satisfied by the C code
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
66
67. C code generation
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
67
Live presentation
68. 13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
68
Introduction
Context
Requirement management
Modelling
Testing
Visualization
Current status
Usages
Subset-076
Analyze CR
Reference EVC
Model other systems
Generate Code
Conclusions
AGENDA
69. EFS
What is it ? What is it not ?
• EFS
– Modelling tool
– Focus on execution and
visualization
– Traces model and tests to
requirements
– Helps project management
– White box
– Open Source
– Can be integrated in a test
environment
• Not EFS
– Real time
– SIL 4
– Embedded
– A proving tool
– A Toy
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
69
70. Your comments
(questions, remarks, jokes) …
… are welcome!
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
70
71. Thank you for your attention!
www.ertmssolutions.com
13/10/2015
EFS - A domain specific language to formalize
ERTMS specifications
71