Digital model of deployed system

4 views
Skip to first unread message

Jack Ring

unread,
Aug 15, 2014, 2:08:58 PM8/15/14
to Bob Kenley, Bill Miller, astewg, Sys Sci, Brad Holtz, Dan Shunk, david...@incose.org, john.frederick@faa.gov Frederick
In the 1960’s we devised "system in operation” models to highlight ramifications of choices in Range Safety and in Test Range Planning and Scheduling.

In the 1970’s 
I learned that the Honeywell TDC 3000 contained a 2500 equation model of the catalytic cracker that the TDC 3000 was supposed to control. 
Likewise, at the USAF Satellite Test Center we devised digital models of spacecraft and of ground ‘subject matter’ in order to plan and command spacecraft activity to get the most "bang for the limited lifetime resource."
Meanwhile, although other larger scale systems were "managed by model” we observed that most 'In Service Engineering' failures had one common denominator — no digital model of the thing they were supposed to be servicing.

The 1980’s Computer Integrated Manufacturing movement demonstrated that having a Computer Integrated factory was only half the story, one also needed a high fidelity digital model of the factory in order to really manage it well. This was especially true in semiconductors wherein each of the N stages had to be configured based on the achievements (or not) of previous stages (a real-time, self-adaptive system) 

This led us to the notion that SE not only generates a digital model of an intended system up front but also evolves the model of the system into a certified, deployable deliverable in parallel with the system realization engineering activity. Further, that V&V of the system-as-built model is as necessary as is V&V of the system of interest.

The ramifications of all this in the ‘system of systems’ domain was described in the IEEE-SMC 2005 paper "Key Challenges and Opportunities in
‘System of Systems’ Engineering” by Azad Madni and yours truly. 

Also, George Friedman’s excellent book, Contraint Theory, tells you just how detailed such model has to be, 

Now, Aviation Week informs us of the need for digital models of autonomous systems.

even though, as near as I can tell, the plan for the FAA NextGen does not provide for evolving, validating and certifying a digital model of the NextGen system (montage?) as it evolves.

Claim:  A certified digital model of a system-as-deployed is mandatory, ideally from Day 2 of a systems project through Year N of its suitable operational availability. 

Meanwhile, Caution, do not be under-informed by the current ministrations in the SE Handbook, SEBoK, ISO standards, etc.. 

Jack Ring

unread,
Aug 15, 2014, 2:10:48 PM8/15/14
to Bob Kenley, Bill Miller, astewg, Sys Sci, Brad Holtz, Dan Shunk, david...@incose.org, john.frederick@faa.gov Frederick

Georg...@aol.com

unread,
Aug 15, 2014, 3:32:25 PM8/15/14
to syss...@googlegroups.com, bob.k...@kenley.org, william...@incose.org, ast...@googlegroups.com, syss...@googlegroups.come, Brad....@cyonresearch.com, dan....@asu.edu, david...@incose.org, john.fr...@faa.gov
In  the  early  70's  Hawker  Siddeley  Dynamics  Hatfield  developed  a  "Fortran"  computer  model  of  the  Sky  Flash  missile   flight from  launch  to  impact,  which  was  updated  continuously  by reference   to   telemetry  results  etc.
 
George
 
 
 
--
The SysSciWG wiki is at https://sites.google.com/site/syssciwg2013/ .
 
Notifications on web activities can be sent from https://groups.google.com/forum/?fromgroups#!forum/isss-incose.
 
Contributions to the discussion are licensed by authors under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
---
You received this message because you are subscribed to the Google Groups "Sys Sci Discussion List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to syssciwg+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

skr...@parker.com

unread,
Aug 15, 2014, 3:41:50 PM8/15/14
to syss...@googlegroups.com
thanks for that !

Steve Krane
Sr. Technical Staff, Engineering Fellow
Parker Hannifin Corporation
Hydraulic Systems Division
(949) 289 7634 (direct)

--
The SysSciWG wiki is at
https://sites.google.com/site/syssciwg2013/ .

Notifications on web activities can be sent from
https://groups.google.com/forum/?fromgroups#!forum/isss-incose.

Contributions to the discussion are licensed by authors under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
---
You received this message because you are subscribed to the Google Groups "Sys Sci Discussion List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
syssciwg+u...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.


"PLEASE NOTE: The preceding information may be confidential or privileged. It only should be used or disseminated for the purpose of conducting business with Parker. If you are not an intended recipient, please notify the sender by replying to this message and then delete the information from your system. Thank you for your cooperation."

Hillary Sillitto

unread,
Aug 15, 2014, 7:24:53 PM8/15/14
to syss...@googlegroups.com

So: what to do? Has anyone given serious thought to building on the Fellows' consensus 'SIMILAR' model for SE, where 'M' is for 'Model'?

Best regards

Hillary

Doug McDavid

unread,
Aug 15, 2014, 7:56:39 PM8/15/14
to ast...@googlegroups.com, Bob Kenley, Bill Miller, Sys Sci, Brad Holtz, Dan Shunk, david...@incose.org, john.frederick@faa.gov Frederick
Jack, one of my soapboxes these days is to advocate a baby-steps version of the "digital twin" idea in the realm of enterprise.  Until that last pointer, I didn't have good language to describe it.  I've been calling it 21st Century enterprise architecture, or sometimes enterprise architecture for the rest of.  The basic idea is that a startup would be delivered with a simplified model of itself, which would start to be maintained from Day 2, as you say, in a distributed, crowd-sourced, cloud-based, gamified way by all enterprise participants who are able to make changes to the operations in any way.  I've got to get this out in the form of a paper, methinks.  Thanks for pointing toward some great terminology!


--
--
To unsubscribe from this group, send email to
astewg+un...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "ASTEWG" group.
To unsubscribe from this group and stop receiving emails from it, send an email to astewg+un...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Skype: dougmcdavid
Mobile: 916-549-4600

profhitchins

unread,
Aug 16, 2014, 5:25:22 AM8/16/14
to syss...@googlegroups.com, bob.k...@kenley.org, william...@incose.org, ast...@googlegroups.com, Brad....@cyonresearch.com, dan....@asu.edu, david...@incose.org, john.fr...@faa.gov
Excellent article. Interesting to see the difference between the military and the civil applications. Thanks

Jack Ring

unread,
Aug 16, 2014, 9:19:19 AM8/16/14
to Sys Sci
The SIMILAR MODEL already says "The model for the preferred alternative will be expanded and used to help manage the system throughout its entire life cycle.
Unfortunately (for most users) SIMILAR did not succeed in directing INCOSE attention beyond the Acquisition phase.
Perhaps we should simply make the point, INCOSE-wide, that both system effectiveness and Operational Availability can be managed best if model-based. 
We can start by updating the Praxis accordingly.
Reply all
Reply to author
Forward
0 new messages