Renault Trials Blockchain Platform for Component Compliance

Market NewsSeptember 13, 2020 by Kelly Cromley

Auto manufacturer Renault has trialed a blockchain venture intended to simplify conformity certification of vehicle parts.

The venture, named as Extended Compliance End-to-End Distributed, also referred to as XCEED, is an outcome of Renault’s collaboration with other enterprises to build a blockchain powered supply chain solution by exchanging info.

It is developed on the Hyperledger Fabric network and installed in partnership with IBM. XCEED monitors and endorses regulatory conformity of vehicle spare parts.

Renault piloted XCEED in its Douai plant and handled more than a million documents with processing capacity of 500 transactions per second. XCEED disburses conformity data among manufacturers of spare parts and cars.

Renault stated that the platform expedites data sharing, paving way for real-time delivery. XCEED, the carmaker detailed, builds a dependable network to share info in a trustworthy manner.

Renault’s associates for the venture include Continental, Plastic Omnium, Faurecia and Saint-Gobain. The partnership was initially revealed in 2019. The automaker stated the necessity for an improved compliance solution has arisen due to the implementation of fresh supervising guidelines on September 1.

The European Union’s Directive 2007/46/EC, amended earlier this year, paves way for enhanced tracking of new vehicles and spare parts to fulfill security and environment criterion. Renault stated that its overall production chain “has to adjust its structure” to meet the shortened time period indicated in the guidelines.

Odile Panciatici, blockchain vice president at Groupe Renault, said:

“The XCEED project we initiated is a powerful illustration of Groupe Renault’s capacity to innovate. We are convinced that blockchain is a vector for transforming the automotive industry.

Blockchain technology really comes into its own in a vast ecosystem involving a number of different companies, providing a link between the partners’ various processes, computer systems and databases. There are multiple uses for this type of technology in the automotive industry, where we have exchanges with countless actors from outside the company, such as suppliers, clients and independent distributors.”

It is not Renault’s first entry into blockchain technology. Renault, in association with other automobile enterprises BMW, Ford, GM and tech enterprises IBM, Bosch, Hyperledger and IOTA labored on the Mobility Open Blockchain Initiative (MOBI). It developed a database of Vehicle Identity Numbers on the blockchain. BMW also developed a blockchain powered supply chain solution.

Related:

Lemons or Le Mans: Why Not Using A Processor-Optimized System Will Leave You Underwhelmed

An Impractical Approach Would you ever think that a smart car could beat a souped-up sports car on a quarter-mile race track? You could, by modifying the tiny smart car with an over-powered engine packed into its lightweight frame. This is a clever trick to get maximum power over a short distance. However, would you ever race one of these cars on an F1 track? Or tow a boat? Or take kids to swim practice? Although these mental images are entertaining, a super-powered smart car does not make a useful or effective value prop for these … READ MORE

Related:

  • No Related Posts

Is Dual-Socket Server Performance Possible in a Single-Socket Server? Gartner Says Yes.

Imagine you are a small cafe owner who brews 20 gallons of tea every day for your customers. Your cafe has recently seen an influx of business, so you are going to invest in some new pots. Would you choose to buy a 100-gallon pot for your 20-gallon tea needs? Probably not. You would most likely purchase a 30 or 50-gallon pot that would not only help you grow, but would also be cheaper. The same goes for IT. In many cases, businesses often purchase dual-socket servers without thinking about the workload requirement. Why should you … READ MORE

Related:

  • No Related Posts

7023251: Could not autodiscover endpoint for user

14:38:13, 945[ajp-nio-48009-exec-6] [ERROR] ServerErrorHandlerStrategy: reportError: Exception during discover of SRVURLs :: com.gwava.ews.autodiscover.AutoDiscover.getEWSUrl:114 :: EXCEPTION : javax.na

ming.NameNotFoundException: DNS name not found [response code 3]; remaining name ‘_autodiscover._tcp.domain.com’ javax.naming.NameNotFoundException: DNS name not found [response code 3];

remaining name ‘_autodiscover._tcp.domain.com’

at com.sun.jndi.dns.DnsClient.checkResponseCode(DnsClient.java:660)

at com.sun.jndi.dns.DnsClient.isMatchResponse(DnsClient.java:578)

at com.sun.jndi.dns.DnsClient.doUdpQuery(DnsClient.java:426)

at com.sun.jndi.dns.DnsClient.query(DnsClient.java:211)

at com.sun.jndi.dns.Resolver.query(Resolver.java:81)

at com.sun.jndi.dns.DnsContext.c_getAttributes(DnsContext.java:434)

at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getAttributes(ComponentDirContext.java:235)

at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(PartialCompositeDirContext.java:141)

at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(PartialCompositeDirContext.java:129)

at javax.naming.directory.InitialDirContext.getAttributes(InitialDirContext.java:142)

at com.gwava.address.exchange.impl.GetAutoDiscoverSCP.getSRVURLs(GetAutoDiscoverSCP.java:466)

at com.gwava.ews.autodiscover.AutoDiscover.getEWSUrl(AutoDiscover.java:108)

at com.gwava.ews.autodiscover.AutoDiscover.getEWSUrl(AutoDiscover.java:43)

at com.gwava.ews.archiveimpl.process.ExchangeUser.autodiscoverEndpointURL(ExchangeUser.java:256)

at com.gwava.ews.archiveimpl.process.ExchangeUser.autodiscoverEndpoint(ExchangeUser.java:357)

at org.apache.jsp.Util.testExchange_jsp._jspService(testExchange_jsp.java:423)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)

at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:438)

at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:396)

at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:340)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)

at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)

at com.gwava.Filters.ResponseFilter.doFilter(ResponseFilter.java:48)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)

at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:720)

at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:466)

at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:391)

at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:318)

at com.gwava.Filters.MainFilter.doFilter(MainFilter.java:356)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:94)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)

at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:620)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:509)

at org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:877)

at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)

at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1524)

at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1480)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

at java.lang.Thread.run(Thread.java:748)

14:38:13, 965[ajp-nio-48009-exec-6] [DEBUG] AutoDiscover: We have a problem. We could find NO AUTODISCOVER SERVER

14:38:13, 965[ajp-nio-48009-exec-6] [INFO ] AutoDiscover: DEBUG: EXIT AUTODISCOVER

14:38:14, 090[ajp-nio-48009-exec-6] [TRACE] EwsTraceListener: <Trace Tag=”AutodiscoverConfiguration” Tid=”180″ Time=”2018-08-07 20:38:14Z”>

Determining which endpoints are enabled for host domain.com

</Trace>

14:38:14, 124[ajp-nio-48009-exec-6] [TRACE] EwsTraceListener: <Trace Tag=”AutodiscoverConfiguration” Tid=”180″ Time=”2018-08-07 20:38:14Z”>

No Autodiscover endpoints are available for host domain.com

Related:

  • No Related Posts

DPA GUI hangs and crashes when tries to Delete Smart Groups

Article Number: 499956Article Version: 3 Article Type: Break Fix



Data Protection Advisor 6.3

Unable to delete smart group. After clicking on the smart group, the application server (GUI) hangs and crashes after a while.Error message while deleting the smart group: Error 12002, and the GUI hangs for few minutes and then it crashes .

Server log:

2017-05-05 10:32:05,583 ERROR [com.emc.dpa.command.nodes.DPASmartGroup] (Thread-3988 (HornetQ-client-global-threads-296458697)) Failed to generate smart group children, please check configuration: com.emc.apollo.common.exception.ApolloException: The Object Type with the name ‘object_name’ was not found (exception.name_not_found)

2017-05-04 10:32:25,515 ERROR [com.emc.dpa.command.nodes.DPASmartGroup] (Thread-1855 (HornetQ-client-global-threads-296458697)) Failed to generate smart group children, please check configuration: com.emc.apollo.common.exception.ApolloException: The Object Type with the name ‘object_name’ was not found (exception.name_not_found)

Listener log shows:

<node version=”1″ type=”ExternalSmartGroup”>

<id>6a277479-c44b-45ae-ad53-dbf5ebcd63b9</id>

<link rel=”self” href=”https://server.com:9002/apollo-api/nodes/6a277479-c44b-45ae-ad53-dbf5ebcd63b9“/>

<name>delete me</name>

<displayName>delete me</displayName>

<globalName>Groups:Smart Groups:delete me</globalName>

<createTime>2017-03-27T11:36:35.0+01:00</createTime>

<lastSeen>2017-03-27T11:36:39.797+01:00</lastSeen>

<creatorType>unknown</creatorType>​

For some reason DPA try to generate smart group children when we delete that smart group (In theory that can be if that on demand smart group).

Smart group fail to run and deletion process broken.

In this case we applied the below workaround and able to delete the smart group.

  • Go to “Edit Smart Group” window
  • Click on “Select Frequency”
  • Select “Once a day at”
  • Save Smart Group
  • Delete Smart Group

Please contact Dell EMC Technical Support for further details or information.

.p

Related:

  • No Related Posts

Driving Human Progress with McLaren

EMC logo


Dell Technologies and McLaren logos
I can’t tell you how excited I am about our partnership with the McLaren Technology Group.

At the core of McLaren is design and engineering – characteristics that are most often expressed through their Formula 1 team, which is second only to Ferrari in terms of success. But this is not your father’s McLaren.

Over the past seven years, McLaren have applied their Formula 1 racing heritage to the street and are now well on their way to building a billion dollar business.  Its automotive business includes the McLaren 720S (below), which was named the most beautiful supercar of 2017.

McLaren 720S

But our partnership also extends to the McLaren Applied Technologies division.  This is probably the least well-known area of their business, but potentially the most exciting.  The Applied Technologies division takes the advanced design, engineering and analytics expertise that McLaren has developed over decades of F1 competition, and applies this know-how to other industries.  They are driving innovation across areas such as connected public transport, entertainment and healthcare, and working with companies like Deloitte in the world of IoT, GlaxoSmithKline on Analytics, and the National Health Service for body sensor technology.

Dell Technologies will be using this partnership in many different ways.

First and foremost we will be using Formula 1 to underpin the expansion of our brand campaign in Europe and Asia. Think of us using it in the same way as we have used the PGA Tour golf events so successfully over the past couple of years. Over 400 million people watch Formula 1 each year, most outside of the US, and it contains a high concentration of tech-savvy watchers – which is of particular interest to us!  As well as featuring the Dell Technologies brand on the McLaren F1 car and drivers, we will also be featuring their use of our technology in our brand campaign.

The McLaren Technology Group provides us with a great, ‘edge to core to cloud,’ case study in their use of Dell Technologies products and services. McLaren has been a longtime customer with everything from PCs to servers to storage and SecureWorks. Over the next few years they will be expanding their use of our technology as their Digital Transformation picks up speed – an incredibly hot topic in the automotive industry! We plan on showcasing the McLaren story (along with racing simulators!) at our tier 1 global event during 2018.

During 2017, McLaren increased its focus on gaming by not only running the inaugural “World’s Fastest Gamer” (and signing up the winner), but also appointing a new director to oversee their eSports strategy. eSports currently enjoys a following of about 200 million people and that’s expected to grow to over 300 million by 2020. This represents another opportunity for us to build on our recent eSports announcements at CES.

Providing customer hospitality at F1 races and leveraging the amazing McLaren Technology Campus as a venue for press, analyst and executive events will be a key part of our partnership with McLaren as well. We want to use McLaren’s facilities, and their executives, to help us build stronger relationships with our best customers. We will once again be partnering with Intel on our customer hospitality, executive events and eSports activities.  We’ve had a lot of success over the past couple of years demonstrating our combined value at marquee events such as this.

Finally, we believe there is an opportunity to partner with McLaren Applied Technologies and apply their know-how in industries such as transportation, media & entertainment and healthcare to make IoT real for our customers.  Similar to the natural alignment between McLaren and Deloitte, GlaxoSmithKline, and the National Health Service, McLaren Applied Technologies offers Dell Technologies deep industry expertise as well as leading edge sensor technology that plays well with our edge gateways and data center infrastructure.

back of driver inside McLaren car

Over the next few weeks you will see McLaren announce their new F1 car for the upcoming season and then you’ll be able to see it in action at the first race in Melbourne on March 25th.   We will be working on new case study materials for DellTechnologies.com as well as creating a live interactive experience at Dell Technologies World in Las Vegas in May. Our partnership with the McLaren Technology Group gives us a great platform to tell the Dell Technologies story, building on the great work done in 2017 in the United States… and now expanding to Europe and Asia!



ENCLOSURE:https://blog.dell.com/uploads/2018/02/Dell-x-McLaren-Press-Release1000x500.jpg

Update your feed preferences


   

   


   


   

submit to reddit
   

Related:

  • No Related Posts

There’s No Place Like a Smart Home

EMC logo


We’ve been using technology to make our homes more comfortable, more secure and more entertaining for decades – with varying degrees of success. In this episode, we’ll discuss a history of smart technologies used inside the house, and analyze just how smart they really could be.

For more on these stories go to delltechnologies.com/trailblazers. Please let us know what you think of the show by leaving us a rating or review in Apple Podcasts.



ENCLOSURE:http://tracking.feedpress.it/link/16581/8005800/839a7be9.mp3?CID=311880

Update your feed preferences


   

   


   


   

submit to reddit
   

Related: