David Ewing さんのグループアクティビティ

2020 A&D Wrap-up and Looking Ahead

David Ewing — Tue, 22 Dec 2020 19:00:00 GMT

2020 certainly has been a bizarre year. It seems so long ago I was in San Diego and Washington, DC working with prospects and subscribers. Next thing I know, I’m at home being a part-time teacher. My wife and I are fortunate to be in a situation where we were able to work from home. Not everyone has that luxury—thanks Peter!

At Aras, transitioning to remote work was not a big step. Many of our team were already working remotely and the nature of software development afforded us a quick change over. In fact, our SAFe (Agile) process was already done completely virtually. We even increased the frequency that we release service packs. In the move to remote work, it was interesting how quickly the term “Zoom” has become the “Kleenex” of the web video conferencing industry.

We’ve certainly seen an impact on the commercial aerospace business. With less aircraft in the air, there was a significant reduction in new orders, maintenance, and impacts on all of the surrounding industries. This has affected the entire PLM industry.

On the Defense side, there’s been less of an impact. Most of the prime contractors kept moving forward on existing projects and there were several new contracts awarded as well. COVID was definitely a bump in the road, but things smoothed out a bit as the year wore on. One difference (that likely was common to all industries) was that any “end of year” money that would have normally been used to kick off projects and ensure budgets, was not available, as any “extra” funds were used to support new COVID practices.

I really missed being out working with people in the field. I missed presenting at conferences and giving briefings in person. It really sucked that we were forced to cancel our yearly conference, even though it was the right thing to do. I really love talking turkey with people. Sometimes it is imagining new things, sometimes it is educating someone new to the industry, and other times it is architecting a solution for new customers. I miss the energy in those conversations, the scribbling on the whiteboard, and the clinking of glasses after an ah-ha moment at the pub.

A&D Roundtable

We held an A&D Roundtable last week to try and regain a bit of the missing energy of working together, albeit virtually. We had participants from USAF, US Navy, SAIC, MIT Lincoln Lab, Purdue University (Boiler Up!), General Dynamics, and Aerospace Corporation. Funny thing—it is harder to get dedicated blocks of a person’s time now that they are working remote. Normally, we would have roundtable events as part of a conference, but nature abhors a vacuum and calendars get filled up. Even with that challenge, we got a great group of people and a conversation that was still going strong after two hours. We even had to drop our last topic and agree that it was worth a follow-up meeting in January. Our topics included Systems Architecture /Engineering /MBSE integration, Establishing the Digital Thread and Digital Twin/Single Source of Truth, and Remote Work in a multiclassification environment and COVID reality. These are important topics in the A&D Industry and it is clear that they will continue to be going forward. As a group we decided to allow the digital twin discussion to keep running into the last segment as it was a very lively conversation. Here are some of the points discussed:

Systems Engineering:

Model validation is key
Incremental improvements are good
Modeling for the sake of modeling is not valuable, model with a purpose and decompose, there is a need for connectivity to other domains and tools
Change control is out of control, no enterprise Configuration Management
Integration: right information to the right person at the right time
Update frequency across teams/domains is still in flux
Stovepipes/siloes persist— consistent problem

Digital Thread/Single Source of Truth:

Detailed thread/twin definitions vary
Integration and interoperability are challenges
What is a “single source of truth and who decides?
Digital twin is still abstract—how to interact etc.
Need connected system model/simulation to support generative modeling
Connecting model parameters to design/simulation/testing is powerful
Commercial is WAY faster to release product
Age gap, hiring, skill sets, engineering theory vs practice—there was significant discussion about this

Our roundtable event concluded with agreement from the entire team that there was value in the discussion and the participants took home ideas and things to look into. To support an ongoing and healthy discussion, we are going to plan a recurring schedule of events—stay tuned.

Looking forward to 2021

I believe that the transition into 2021 is unclear. With a newly elected president and policies on the horizon, an economic recession, and a pandemic whose end is uncertain, it is hard to predict anything. But here is what I do know. The engine of innovation and technology will continue. We may be in a lower gear, but that means we will have fuel when we rev up and bust out of our current funk!

We will continue to see advances in technology and, unfortunately, we will see resistance to change. We will continue to see innovators like SpaceX defy convention, reuse rockets, and win. And others will keep on keeping on.

“And this is the best that you c - that the-the government, the *U.S. government* can come up with? I mean,..you-you're NASA for cryin' out loud,..you put a man on the moon, you're geniuses! You-you're the guys that think this *** up! I'm sure you got a team of men sitting around somewhere right now just thinking *** up and somebody backing them up!““–Bruce Willis as Harry Stamper in, “Armageddon”

I continue to see the pace of change slowed by various forms of inertia. The shame is, there is plenty of proven technology available that can positively impact a firm’s bottom line. I talk to many people about the idea for a Rapid Development Incubator (i.e. Greenhouse) and see plenty of ah-ha moments. We know this initiative will help our subscribers go fast—we have seen it at USAF, Airbus, and SAIC. Now, we need to get everyone to jump on the bandwagon.

Systems Architecture and MBSE are only going to continue to push forward. We are seeing an evolution in systems development that is driving improved methodology for how systems engineering is approached and how MBSE tools are being utilized. MBSE tools are like CAD for Systems Engineers.The challenge is connecting the information in a model to the product development process. That data is the digital DNA that defines the context and missions for a product/system. Simply creating a MagicDraw model and throwing it in a shared folder or in its own lonely PDM is not good enough. If you can’t get that information to the downstream domains efficiently and effectively, you have thrown away much of the utility of the model.

Want to shake things up? Make the block definition diagram the input to the detailed design team—MCAD, ECAD, and software. Watch the MCAD guys start throwing out excuses.

To bring modeling full circle, we cannot simulate enough. I’m a huge proponent of “simulate early, simulate often.” We will see more processing power from Intel, new cloud capabilities from ReScale, and the raw power of simulation number mashing from Ansys. But just like MBSE—what are you going to do with the data? Is it related to that systems model? Is it related to the test plan? Is it statistically correlated with test results so you can save $$ on physical tests?

We recently partnered with SAIC to present: Systems Architecture-The Connective Tissue of Your Digital Thread. Check it out and let’s talk shop!

The digital thread will keep on threading in 2021. The curious question is—when will people realize that just having data in a database does not make a digital thread? A digital string yes—but it is still a silo!

And when will there be a realization that shoe-horning data into a 30-year-old legacy data model is not the answer? Stock up on digital duct tape—you’re going to need it to keep things running.

If you want to make a real change, we need to look at the product development process, the people, and the tools used. (If you don’t know why the people are important go to any book about Kaizen or the Toyota Production System and you will realize that the people involved are important.) With this view we can understand how a firm works, how processes need to be executed, and the proper data structure to support the needs of the business.

We all know that everyone has a favorite tool for MBSE, Software, CAD and Simulation. Don’t fight it—integrate it. Connect those tools and sometimes even their respective PDMs. But, the key is to wrap configuration management and business logic around all the processes and tools. That is how you achieve your digital thread single source of truth.

I wish everyone out there a Merry Christmas, happy holiday season, and a happy new year. I’m really hoping to get out and talk shop with you soon!

2020 A&D Wrap-up and Looking Ahead

David Ewing — Tue, 22 Dec 2020 19:00:00 GMT

Model validation is key
Incremental improvements are good
Modeling for the sake of modeling is not valuable, model with a purpose and decompose, there is a need for connectivity to other domains and tools
Change control is out of control, no enterprise Configuration Management
Integration: right information to the right person at the right time
Update frequency across teams/domains is still in flux
Stovepipes/siloes persist— consistent problem

Digital Thread/Single Source of Truth:

Detailed thread/twin definitions vary
Integration and interoperability are challenges
What is a “single source of truth and who decides?
Digital twin is still abstract—how to interact etc.
Need connected system model/simulation to support generative modeling
Connecting model parameters to design/simulation/testing is powerful
Commercial is WAY faster to release product
Age gap, hiring, skill sets, engineering theory vs practice—there was significant discussion about this

“And this is the best that you c - that the-the government, the *U.S. government* can come up with? I mean,..you-you're NASA for cryin' out loud,..you put a man on the moon, you're geniuses! You-you're the guys that think this *** up! I'm sure you got a team of men sitting around somewhere right now just thinking *** up and somebody backing them up!““–Bruce Willis as Harry Stamper in, “Armageddon”

I wish everyone out there a Merry Christmas, happy holiday season, and a happy new year. I’m really hoping to get out and talk shop with you soon!

You Can’t Handle the Single Source of Truth

David Ewing — Tue, 23 Jun 2020 13:35:00 GMT

Everyone who has seen the movie A Few Good Men remembers the courtroom scene with Jack Nicholson weaving his craft. The idea that the truth is hard to swallow translates surprisingly well into the world of product development and product lifecycle management.

No longer is PLM just about data and CAD management; it even extends beyond the boundaries of an innovation platform. -Kirk Carlsen

Product Lifecycle Management has grown and morphed over time from simplistic CAD data management into a multi-domain, connected platform. The lifecycle of PLM software (see how I did that?) has seen a consistent increase in incorporating both additional domains and their tools – for example Systems Engineering. Interestingly, those domains have been considered part of the academic definition of PLM for years, however, the “big box” PLM systems have only recently started bringing them into the PLM fold – you should ask yourself why.

All of this increase in capability in PLM is intended to create an integrated environment where all of the data related to the product and process are stored. We should know when problems in the field drive a Problem Report that in turn drives an Engineering Change AND who signed off on them. We should be able to see what system model elements, simulation, and validation test are driven by a given requirement.

Bringing all of the data together and providing linkage and traceability is what we call the Digital Thread. The theory also goes that this increase in capability should also establish the Single Source of Truth. This is where the harsh reality starts to set in.

Truth #1: Single Source of Truth ≠ Single Vault of Truth.

Lionel Grealou, a digital transformation evangelist, writing about Single Source of Truth noted: “SSoT is often mistaken for a single database or repository for all data; rather it implies an intelligent enterprise data model constructed for optimum data integration and control across multiple sources, avoiding duplication and redundancy.”

Lionel is spot on. Creating a single source of truth does not mean that all of that data needs to be in one place. It means that there is only a single master of the data in question. That data may be used in many other projects, departments, and even in different software tools – but only by linking to that master. This is the idea behind the Single Source.

Additionally, not all Product Data Management systems and authoring tools fit well together. That is okay as long as the Single Source concept is retained. Put simply you can not shoehorn a data model from a modern authoring application in to a 30-year-old PDM data model. The idea that you can is myopic.

Truth #2: Domains will always use their favorite tool

Pick a domain…any domain and ask them about their tool of choice. What you will see is that each domain has their favorite. That is fine. People use what they like. But often the choice of tool is not from the same vendor as their PDM. More often than not that is because a company that is focused on a singular area will be good at it. Some examples:

MBSE – Dassault Cameo
Software Development – Microsoft Visual Studio
Simulation – Ansys
Agile Project Management – Atlassian Jira

The common thread in all of these favorites is that not one of them comes from a company that makes PLM. The real trick is ensuring that the various datasets that are generated can be configuration managed, revised, related to other items. More often than not, they live in disconnected silos relying on Excel and email to share data.

Truth #3 – Silos exist

Enough said. They need to go!

Truth #4: Things change

It seems like every time I go to a conference, I see a group of recent college graduates that have created the next great tool. And you know what? That is a good thing. It keeps the wheels of competition going. We have seen this in the CAD wars over the past 20 years. I used to be a NX guy (yep, my competition in PLM – but Aras does not make CAD tools). Other CAD vendors need to keep inventing to stay ahead of their competition like Catia and the upstart, OnShape.

As those new tools appear, firms say “Hey this might be better than tool X. Let’s give it a try.” Normally a department or program will take the lead on adopting this new tool into their processes. After a while they really like it. Guess what? See Truth #3.

These truths have made it near impossible for firms to successfully transform their businesses – because their Legacy PDM can’t handle the truth. It is holding them back. Still passing requirements from your Requirements Management tool to your design and validation teams via Excel? Can’t handle the truth. Do you have multiple tools in place because the “old school” users still like the old one and the new guys like the new one? Can’t handle the truth.

Time For a New Lens

All these truths do not mean that the vision for PLM 4.0 and beyond is unachievable. It means that firms need to re-evaluate their PLM roadmap and look at things through a different lens. Product Lifecycle Management, as the name suggests, is “all about the product.” It is not a CAD tool or software IDE . It is a business process.

Since PLM is a business process, methodologies form the foundation of product development. Methodologies include how to model a system architecture, how to best simulate a use case, how to test the use case, etc. But most important methodologies also determine the relationships between the items I noted AND what data they share. While Legacy PDM is focused on managing CAD data the processes are left by the wayside. This is where a PLM platform comes in. A PLM platform is created to deliver a connected enterprise with all of these truths in mind.

By taking a platform approach, a firm has options and can control its own destiny. A platform can connect disparate people, processes, and tools into an integrated environment. There is no need to throw everything away and start fresh. You have product to deliver and that takes too much time! So, here are a few things to help you along your journey.

Focus on methodology. Understand your business processes and focus on how things get done. Understand what data is important to other users in the enterprise and how to link/federate to important data (to achieve a Single Source of Truth). Also determine data governance and access control as well. Most important - don’t let your PLM system dictate your process. PLM is intended to implement and automate YOUR process. If it can’t – it’s time for a change.

Use best in class tools or those that best fit your firm’s needs AND integrate them. Your needs are going to grow. As that happens—change tools. The universal constant needs to be the integration – no more silos! From Word to NoMagic to Ansys. Connect those tools so they get out of the silo and the data is managed. This becomes very powerful when important inputs are passed into a model from the platform. A great example is a maximum load or stress that can be stored as a requirement and passed into the simulation tool for virtual analysis and the test plans to validate the simulation.

The same applies to your legacy PDM. The PDM that manages your CAD likely works fine.There is no need to replace it and forfeit your investment. Integrate it to a PLM platform that can support passing data back and forth, manage access control, and configuration management. We are still maintaining the Single Source of Truth in this model (ask General Motors). We have thrown out the fallacy that everything needs to be in a single vault.

“It is not possible to establish single data source and store all data in a single database. It is too limited and it doesn’t scale from all standpoints.” - Oleg Shilovitsky

This concept can be grown to apply to other TDM/PDM systems you may have. The PLM platform will connect to the individual PDM vaults and become the reference to use the data in other processes that need it. This delivers not only the Single Source of Truth but the Digital Thread as well.

Finally, if your business processes are not changing – you are not getting better. If your Legacy PDM system is not helping you to enable the new processes, it’s time for a change. Resilience is a key facet of the ability of a PLM platform to support your firm’s growth path.

The Aras platform was specifically created to support these use cases. This is accomplished with the requirements that we applied to ourselves. When you are ready to take a look at a new way to support your businesses needs, watch a few of our videos to get a feel for what we are all about and download Aras Innovator and give it a try for yourself. When you are ready, let’s build a proof of concept so you can see it for yourself with your own data.

You Can’t Handle the Single Source of Truth

David Ewing — Tue, 23 Jun 2020 13:35:00 GMT

No longer is PLM just about data and CAD management; it even extends beyond the boundaries of an innovation platform. -Kirk Carlsen

MBSE – Dassault Cameo
Software Development – Microsoft Visual Studio
Simulation – Ansys
Agile Project Management – Atlassian Jira

“It is not possible to establish single data source and store all data in a single database. It is too limited and it doesn’t scale from all standpoints.” - Oleg Shilovitsky

Aras PLM or/and PDM

Former Member — Wed, 26 Jul 2017 04:39:29 GMT

Hello, Excuse me for my ignorance but Aras is considered a PLM software (because we can manage the lifecycle for our products from WIP-review and also create BOM etc) or/and it is considered a PDM software (because we can manage our files)? Thank you in advance!

The PLM Punks Take the Baton

David Ewing — Thu, 06 Apr 2017 16:18:06 GMT

Aras sent shockwaves through the PLM industry by announcing that former Siemens PLM CEO Tony Affuso has joined the company's Board of Directors. It’s another significant step forward for Aras’ growth, a major industry validation, and another eyebrow raiser for those who have been entrenched in PLM for a long time. You can read the formal announcement here and some initial reactions here and here.

The Punks From Andover

A PLM industry follower once referred to us as “The Punks from Andover,” to describe us as the noisy, ambitious upstart intent on shaking up the PLM establishment. That assessment rung true with the team at Aras. It sums up our company’s spirit and ethos.

The Punks from Andover just received another sizable industry validation, and we don’t have plans to quiet down soon. We’re hitting our stride with customers like Microsoft. Airbus, Huntington Ingalls, and most recently Schaeffler, and GM.

The best tech companies benefit from guidance and influence over their journey. And it’s often the industry pioneers who are the ones that help them unlock their full potential along the way. Aras is more dangerous than ever with Tony Affuso at our back.

Shock & Awe

Rock ‘n’ roll has always been a staple of Aras events; our CEO Peter Schroer’s signature intro music is AC/DC's Hells Bells, which is fitting, as the song suggests something significant about to arrive. At ACE 2017, the song had just faded when Peter shocked the audience like feedback through an amplifier by welcoming Tony Affuso to stage as our newest board member. There was pretty much a collective gasp from the audience, followed by a round of applause.

Following the main stage presentation, Tony was greeted by attendees, one after another, some who have known him for years, heard him speak at previous PLM events, or simply wanted to welcome him to the Aras community. It was a surreal moment for many, seeing someone that has left a lasting impact on PLM join with the upstart Punk, clearly signaling - the Punks aren't going away.

In nearly every free moment, Tony engaged customers, prospects, and investors as if he had been with Aras for years. The ACE attendees were blown away by the opportunity to get a moment to chat with a PLM Rock Star.

Tony is one of the luminaries in PLM. No one knows PLM – the technology, the industry, the customers – like him, and over a 20-year period, he led UGS and Siemens PLM through significant growth. I have personally known him for more than 10 years now, and I can say that not only is he a wealth of knowledge, he is a great person whom I respect immensely.

Tony was also one of the earliest PLM disruptors, driving Unigraphics and Iman, a forefather of modern PLM, while at UGS. He’s now going to help change the PLM game again with Aras.

[gallery link="file" size="medium" ids="9273,9274,9275,9276,9277,9278" orderby="rand"]

Aras PLM BOM import Tools

khoap — Thu, 27 Jul 2017 19:46:37 GMT

Hi folks, I'm new to Aras PLM and was wondering if there is an option for users to import BOM (not dataload) to perform the BOM upload changes from one revision to the others. For example: BOM A was initially release with preliminary BOM with 100 components with revision A. Users wants to release a prototype BOM with the next revision B with changes to the preliminary BOM such as adding new components, change existing component quantity, reference designator..etc Thanks in advance, Khoa

Design Quality Document Item Reference

Former Member — Thu, 27 Jul 2017 01:29:37 GMT

How to add Item with reference to the Design Quality Document of Quality Management 11.0R2? There isn't reference selection in context menu of Item of Design Quality Document.

How to collaborate in ARAS development

Former Member — Thu, 20 Jul 2017 00:25:08 GMT

Hi, Our team is looking for a replacement of our out-of-date PLM system, so we are doing some investigations around PLMs like ARAS, Agile, PTC. I am a newbie of ARAS, I have downloaded and installed ARAS community edition in my laptop. I have several questions about collaboration among team. If each of us has a development environment of ARAS, how can we sync with others? I mean after sync from version control, how to deploy the code, use import/export tool? Or is there a better solution? And how can we upgrade from integration environment to staging environment? Appreciate your help.

Technology Highlight: Onshape Connector for Aras Innovator

David Ewing — Fri, 14 Apr 2017 12:02:22 GMT

Aras partner AMC Bridge has created a proof of concept (POC) connector to integrate the Onshape cloud-based CAD platform to the Aras PLM Platform. Onshape is a full-cloud 3D CAD system that is built to democratize CAD. It empowers everyone on a design team to work together using any web browser, phone, or tablet.

This connector is a great example of Aras’ Open Architecture that allows anyone to create new capabilities that extend and customize our technology, no licenses needed. In this case, the team at AMC have added a connection to one of the hot new CAD technologies bringing together the leading disruptors in the PLM and CAD markets.

The Onshape Connector adds another option to our CAD Integration capability. It allows users to utilize Onshape’s fast and lightweight CAD modeling capability with Aras Innovator’s world-class Configuration Management and Visual Collaboration features. This is done via a custom application that resides in Onshape that communicates with Aras Innovator. The communication with Aras Innovator is performed through our open interface, data model, and API.

Here are some of the use cases of the connector project that are key to PLM and CAD users:

Part registration – The document hierarchy is registered in Aras Innovator creating new part items with part numbers and BOM structure
CAD model storage – The Onshape application sends the binary geometry (Parasolid or STL) to Aras Innovator to create the matching CAD Document Items and support integrated visualization
Visual Collaboration - Full support for 3D visualization, commenting, and markup with Aras Visual Collaboration
Configuration Management - The parts and CAD documents have full workflow and lifecycle support, and can be put into release and/or change workflows like any other Aras items.

Check out AMC’s video of the integration:

The PLM Punks Take the Baton

David Ewing — Thu, 06 Apr 2017 16:18:00 GMT

The Punks From Andover

Shock & Awe

Tony was also one of the earliest PLM disruptors, driving Unigraphics and Iman, a forefather of modern PLM, while at UGS. He’s now going to help change the PLM game again with Aras.

[gallery link="file" size="medium" ids="9273,9274,9275,9276,9277,9278" orderby="rand"]

Improving your Business of Engineering with 3D PDF

David Ewing — Wed, 29 Mar 2017 15:35:48 GMT

As an ex-CAD guy I enjoy "going home" every now and then. For my work at Aras that means working with our built in 3D viewing capability that we call Visual Collaboration. At home, that means designing furniture projects with 3D CAD tools.

I firmly believe that PLM is a valuable and needed tool for a firm to be successful. At Aras, we use the term Business of Engineering to describe the vitally important aspects of your business that are non-CAD. However, I understand that CAD is where firms start - because after all, you have to design the product. But there is so much more you can do with that data!

I am doing a webinar with our friends from Tech Soft 3D and the 3D PDF Consortium to discuss the Myths and Truths of 3D PDF. 3D PDF is a great way for your firm to begin a digital transformation into a Model Based Enterprise. Of Course, you need a World Class PLM Platform to get you there...but all journeys start with a first step.

Ill be discussing some use cases and will also show you how Aras has integrated 3D PDF and visualization into our Platform from the start. Please join us for some great information. You can Register here.

Improving your Business of Engineering with 3D PDF

David Ewing — Wed, 29 Mar 2017 15:35:00 GMT

Aras Installation

Sathishkumar C — Wed, 08 Feb 2017 02:07:04 GMT

Hi eveybody, I am Sathishkumar C. I want know about Aras PLM installation hardware requirements. Interms of RAM and Processor (Dual core or Quad Core). Currently i have a system Dual core and 4 GB RAM. Can i Install Aras with this specifications? My requirement from Aras is:

I want install Development Server from Aras. I don't know the exact system requirement.
Less than 20 users will use the Aras in my Startup company.
How was the environment (Development server - Aras) will be? I don't have that much knowledge in programming.
What are the limitations and advantages with development server?
If i installed Aras in my system, how can i define a each user of my company?
Can access via Aras from outside from the company? Or within the company (LAN) ? How it will be connected?

Please give me a reply. Thank you in advance.

ACE 2017 Presenter Highlight: Thought Leaders

David Ewing — Tue, 31 Jan 2017 10:30:05 GMT

ACE 2017 is fast approaching. If you haven't marked your calendars - grab a pencil! We will be in Nashville on March 21-23. We have another solid agenda including user presentations, partners and Team Aras showing you the latest developments. Just like last year we will cap the event with Aras In The Round where we throw our CEO into the middle of the audience for a raw and unfiltered discussion with the community. You NEED to be there to experience it!

System Lifecycle Management as a bimodal IT approach

Product development is facing a significant technological pull. IoT is one familiar component but there are many more. Consumers want more features and connectivity. With each additional feature or connected system, product complexity increases exponentially.

Prof. Martin Eigner will illustrate System Lifecycle Management, a concept for providing the product development teams a platform to manage their complex products. SysLM is an extension of PLM which fully integrates the Industrial Internet, Model Based Systems Engineering (MBSE), Product Line Engineering, and Service Lifecycle Engineering.

Dr. Eigner's talk will also reflect on similar approaches like "bimodal PLM/IT" (Gartner, 2016) and "Digital PLM" (Accenture, 2016) which, like SysLM, call for an evolution in product development processes and tools. This evolution will see the transition from document based to model bases processes, integrated Configuration Management, and traditional hierarchical product structures to network and linear structures.

Design for IoT or Design by IoT?

IoT is constantly in the news. New connected products and manufacturing operations are appearing daily. That is a good thing. The result will be better products and processes.

But how does a firm jump into this new pool and create new connected products. Joe Barkai asks you to consider your product design process. Are you designing a new product FOR Iot or are you designing BY IoT?

This is a critical two sided coin of design that needs to be understood. You cannot simply connect your product to the internet - what data will you be transmitting and collecting? The opposite is also true. You need to understand the product context to properly utilize the collected data.

Joe will help you to create opportunity in your IoT journey. He will discuss the interwoven product design and business fundamentals that enable successful IoT products. This lays the groundwork to discuss the critical interaction between IoT and PLM needed to expand and enhance your product development efforts.

David Ewing さんの グループ アクティビティ

2020 A&D Wrap-up and Looking Ahead

2020 A&D Wrap-up and Looking Ahead

You Can’t Handle the Single Source of Truth

You Can’t Handle the Single Source of Truth

Aras PLM or/and PDM

The PLM Punks Take the Baton

The Punks From Andover

Shock & Awe

Aras PLM BOM import Tools

Design Quality Document Item Reference

How to collaborate in ARAS development

Technology Highlight: Onshape Connector for Aras Innovator

The PLM Punks Take the Baton

The Punks From Andover

Shock & Awe

Improving your Business of Engineering with 3D PDF

Improving your Business of Engineering with 3D PDF

Aras Installation

ACE 2017 Presenter Highlight: Thought Leaders

System Lifecycle Management as a bimodal IT approach

Design for IoT or Design by IoT?

David Ewing さんのグループアクティビティ