1. ASSESS Workgroups
Democratizing Software Tools for Analysis, Systems Engineering, and Simulation (STASES) John Chawner, Pointwise STASES Confidence Keith Meintjes, CIMdata Business Challenges Marc Halpern, Gartner The Intersection of Systems Modeling and Classical Simulation Steve Coy, TimeLike Systems

2. Democratizing Software Tools for Analysis, Systems Engineering, and Simulation (STASES)

3. Mission
Make it possible for people who could benefit from using STASES to be able to use STASES.
Get STASES into the hands of current non- users.
New (more users w/in existing organizations)
New New (non traditional users)
Address STASES’ ease of use issues.

4. Scope
The discussion about democratization at ASSESS 2016 in January overlapped three other breakout topics.
Confidence: Simulation governance as it pertains to non-expert use of STASES, validating ROI
Business Challenges: Licensing models (i.e. cost), value proposition (i.e. engaging current non-users)
Heterogeneous Models: data exchange including standards

5. Vision
Customers will benefit from optimized products for which STASES was an integral part of their design.
Design organizations will benefit from a well-defined value proposition for the application of STASES to the development of new products.
Users within a design organization willing to use STASES will be able to use it reliably.

6. Goal Grow STASES use by 10x in 5 years inside & outside of engineering
mostly from SMBs but the Fortune will benefit too

7. Issues Winston Churchill
“You may take the most gallant sailor, the most intrepid airman or the most audacious soldier, put them at a table together - what do you get? The sum of their fears.”
Winston Churchill

8. The devil you know… Current non-users of STASES say…
“What we do now is working.”
“But we do physical tests!”
“Why not Excel (or MATLAB)?”
“We’ll just make the part thicker.”
Because they don’t know…
what STASES can do for their product.
what STASES can do for them.

9. It costs too much. Cost is a significant barrier to entry for SMBs.
A $30,000 software license is a significant barrier to entry for SMBs.
Then there’s the computer to run it on.
And an expert to use it.
Because today’s norm is…
Annual/leased software licensing
On-premise computing
Expert usage

10. It’s too hard to use. Use of STASES is complex. New users fear…
Requires both CAE & subject matter expertise.
Results are not presented in a form appropriate for non- experts.
New users fear…
Non-expert use of STASES
Reliability of results
But it needn’t be complicated.
Causes: general purpose STASES tools, lack of V&V

11. The Unknown Unknowns
Organizations not using (or not widely using) STASES may not be aware of some challenges awaiting them.
Workflows will need to change to support use of STASES
Representation and management of STASES data (inputs and outputs) is a significant challenge.
Data exchange between STASES tools is a quagmire.

12. Next Steps (1 of 3) Communicate STASES success stories.
Technical successes
Benefits to casual users
Benefits to expert users
Business successes
“Simulation is the key enabler to increased competitiveness.”

13. Next Steps (2 of 3) Promote the appification of STASES.
Successes of early adopters.
Expand their implementation and adoption.
Consider frameworks to aid their proliferation
Consider any other idea to improve STASES ease of use.
For example, invisible mesh generation

14. Next Steps (3 of 3) Cost – What are the main issues?
Up-front cost as barrier to entry?
On-going (TCO) cost?
Too expensive relative to what?
Is the barrier to adoption total installed cost or license?
What alternative business models can reduce the barrier(s)?

15. Democratizing Software Tools for STASES