New Initiatives Subcommittee Report To TAC - Space 2016 Jeff Laube – Chair 14 September 2016

Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Agenda Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Guidelines and Forms for TC/PC Fundraising – Sophia Bright & team TC/PC “Clean Sheet” Review – Robbie Robertson & team Including 2017 TAC Workshop Planning Digital Systems Integration Program Committee

Attendees to 09/13/2016 NIS Meeting Jeff Laube Robbie Robertson Mat French** Jeanette Domber Terry MorrisT Masoud Rais-RohaniT Steve RizziT Betty Guillie* Mitch Ingham Sophia Bright David Dress T - Teleconference * AIAA Staff ** Visitor/Alumni

Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Agenda Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Guidelines and Forms for TC/PC Fundraising – Sophia Bright & team TC/PC “Clean Sheet” Review – Robbie Robertson & team Including 2017 TAC Workshop Planning Digital Systems Integration Program Committee

Topics for 2016-Q3 TAC Newsletter Message from Your VP, TAC – Dave Riley   -or -   Message from Your VP-Elect, TAC – Jim Kennan Message from Your AIAA Director, Programs – Megan Scheidt  -or -  Message from Your AIAA Director, Content – Tom Irvine Betty’s Corner – Betty Guillie Meet Your TAC Team: Rob Vermeland – Director, Aerospace Sciences PC-of-the-Quarter: Energy Optimized Aircraft and Equipment Systems – John Nairus TC-of-the Quarter: Dimitri Mavris’ choice New Initiatives Subcommittee: Hot Topics – Jeff Laube/Sophia Bright Recent Developments & Upcoming Events Highlights from 2016 SPACE – Megan Scheidt Sneak Preview of 2017 SCITECH – Megan Scheidt Update on AIAA Governance/Constitution Changes – AIAA Staff(?) Any additions & substitutions anybody would like to propose? Please have you newsletter contributions into Peter by no later than Friday, Sep-23.

Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Agenda Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Guidelines and Forms for TC/PC Fundraising – Sophia Bright & team TC/PC “Clean Sheet” Review – Robbie Robertson & team Including 2017 TAC Workshop Planning Digital Systems Integration Program Committee

Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Agenda Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Guidelines and Forms for TC/PC Fundraising – Sophia Bright & team TC/PC “Clean Sheet” Review – Robbie Robertson & team Including 2017 TAC Workshop Planning Digital Systems Integration Program Committee

NIS – TAC Policy for TC Fundraising Proposal Sophia Bright, Jimmy Kenyon, Dave McGrath, Steve Rizzi September 2016

NIS Action Item for to Address Corporate Sponsorship NIS will create a form for TC/PC Fundraising similar to the TAC Funding request form, which provides some do's and don'ts along with a form that lists the fundraising activity, amount, and company for Director/PCC signature. Current TAC Funding Request Form Basic Structure Descriptions of Funding Sources Basic do’s and don’ts Template Solicited suggestions and recommendations from NIS at-large

Approach Used Reviewed some of the Regional / Local Section processes for Corporate Sponsorship That process was somewhat ad hoc Create a decision tree for funding sources that are available to TCs (e.g. TAC Operating Funds, Corporate, etc.) The decision tree should delineate the type of activity constitutes what type of funding (e.g. Corporate for major initiatives and TAC Operating for promotional shirts, etc.) The tree would also provide some guidance for the type of funding Created a new template specific for Corporate Sponsorship based on the decision tree criteria Delineated levels of funding that would determine what level of approval would be needed One level only requiring TAC leadership approval Another level requiring both TAC leadership approval and approval/vetting via Corporate Sponsor Member For now we will still elevate all requests to TAC VP for awareness initially Same overall guidance would be applied to the TAC approval for the requests Recommend adding guidance around Approval/Denial Timeframe Receipt of decision to requestor within 30 days of receipt of the request for Operating Funds and for Corporate Sponsorship requiring TAC Director Approval lower than TBD $$ threshold Receipt of decision to requestor within 60 days for the Corporate Sponsorship approvals that are higher than the TBD $$ threshold However, determined at June 2016 meeting to remove the threshold requirement

Sponsorship / Funding Decision Tree Sponsorship / Funding Needed Operating Funds * PC Requesting PC Funding Available Not Available VP Tech Funds TC Requesting TC Funding Corporate Sponsorship Request See Corporate Sponsorship Decision Tree * Use Form B

Corporate Sponsorship Request Decision Tree Promotional / Recruitment Recurring Monetary A In-Kind Donation (Material / Facility) C One-Time B Workshop / Event Endowment / Awards / Others a A Initial approval from TAC Director request for final approval by TAC VP and possible coordination with AIAA Corporate Liaison. Use Form A. B Use TAC Operating Funding – Use Form B C Notification to TAC Leadership / AIAA for Awareness. Use Form A for the notification.

Current Form with Modifications in Red Font Pages 1 and 2: TAC/TC/PC Funding Utilize the Request for Sponsorship / Funding Decision Tree to determine what type of funding and corresponding approval will be required. Corporate Sponsorship Requests Operating Funds Operating funds are set aside for Technical and Program Committees to use to fund special projects. Requests may be made at any time, and need to be used by the end of the fiscal year. Allotments are made on a first-come, first-served basis at the discretion of the Directors/Program Committee Coordinator (PCC) and the Vice President-Technical. Funds not allocated by the end of the fiscal year will revert to the general operating fund – they may not be cached to use at a later time. There are several types of Operating funding:  Technical Committee Funding from Directors Each Technical Director is given a specific allotment of funds. TCs apply to the Technical Director for funding (request form is below). If the Technical Director approves the request, he or she sends it to headquarters for fulfillment. The money will be held for the TC at AIAA headquarters until reimbursement or payment is made. The money is not placed in the individual TC account. The Directors may fund all or only part of a request, at their discretion. Program Committee Funding from Program Coordinator Program Committee Chairs may submit a request to the Program Coordinator to apply for funding. If the Program Committee Coordinator approves the request, he or she sends it to headquarters for fulfillment. The money will be held for the PC at AIAA headquarters until reimbursement or payment is made. The money is not placed in the individual PC account. Vice President-Technical Funds These funds may be used after the Technical Director has allocated all of the funds for his or her technical group. Requests must go through the Technical Director to the VP-Technical and the VP sends an approval form to the Staff Liaison for fulfillment. The Vice President may elect to fund all or only part of the request. The same process should be followed if the Program Committees are interested in applying for these funds. Eligibility Any TC/PC is eligible to apply for these funds, regardless of whether or not it has other sources of funding or whether or not it has other funds on hand. However, any committee applying must have an up-to-date roster on file with AIAA staff. Final Review  A final review will be done by the AIAA Staff Liaison for Technical Activities to ensure that the request does not violate any AIAA rule or procedure that may be unknown to the TCs or Directors. Utilize the Request for Sponsorship / Funding Decision Tree to determine what type of funding and corresponding approval will be required. Corporate Sponsorship Requests In-Kind Donations of materials or facilities would still go through the approval process but it is primarily only to notify the TAC Leadership and AIAA for awareness. Monetary sponsorship requires initial Technical Director approval. The Technical Director will present the request to the TAC Exec for final TAC VP approval. AIAA TAC liaisons will determine if the request requires coordination with AIAA Corporate liaisons. These requests can be both recurring and one-time Operating Funds

Current Form with Modifications in Red Font Page 3: Hints on Obtaining Funding (Page 3 of 7) Definitions: Promotional / Recruitment: intended to promote AIAA and increase/retain membership Workshop / Event: as part of Forums or separate activities (e.g. STEM, outreach) Endowment / Awards / Other: corporate contributions to AIAA Foundation, awards, or others that do not fall into the above definitions Requests will generally be approved if: it is an event that supports/promotes: the mission of the committee aviation/aerospace in general student-committee interaction student-industry interaction it is an outreach aligned with the Strategic Plan/Vision. it is an enhancement/improvement to an activity or event that requires funding beyond what is budgeted for that year No change to Page 2 except the title. Please change the title to “Guidance on Obtaining Funding”.

Current Form with Modifications in Red Font Page 3: Hints on Obtaining Funding (Pages 3 and 4 of 7) Continued If AIAA Logo will be used then it must be approved prior to proceeding Requests will be turned down if: the funding is of personal benefit to any member or close relative of a member of the committee any activity that would violate the AIAA Code of Ethics funding requests for capital equipment (computers, projectors, etc.) funding requests for travel reimbursement will not be considered if using TAC funds For Corporate Sponsorship a draft of the request must be included for consideration (see draft template) Corporate Sponsorship Best Practices to Consider [adapted from the Sponsorship Best Practices guidelines used by the AIAA Corporate Liaison group] Details included in the document No change to Page 2 except the title. Please change the title to “Guidance on Obtaining Funding”.

Current Form with Modifications in Red Font Page 5: Template Form A Updated title of form to be specific to Corporate Sponsorship requests. For In-Kind Donations, write “In-Kind Donation”. Along with the date required for an In-Kind Donation. Correspondingly, the “Please disburse” amount will be zero. Attach a copy of the Funding Request Proposal to ensure that it meets the AIAA intent. The completed forms will need to be submitted to Betty and to the Technical Director for their committee.

Current Form with Modifications in Red Font Page 6: Template Form B Updated title of form to be specific to Operating Funding requests. There are no other changes to Operating Funding request template.

Sample Corporate Sponsorship Request Letter Page 7: Example Letter Use appropriate letter head representing AIAA or the committee within AIAA. The use of the AIAA logo will need to be approved prior to submitting the request. Note that the letter may be tailored differently if the company is a corporate member or not. The author may want to coordinate specific details with the AIAA Corporate Liaison group to strengthen the request.

Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Agenda Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Guidelines and Forms for TC/PC Fundraising – Sophia Bright & team TC/PC “Clean Sheet” Review – Robbie Robertson & team Including 2017 TAC Workshop Planning Digital Systems Integration Program Committee

Technical Activities Committee Special Working Group September 2016 Clean Sheet Analysis Technical Activities Committee Special Working Group September 2016

Clean Sheet Analysis Team Lawrence “Robbie” Robertson Air Force Research Lab David Dress NASA Betty Guillie AIAA Wayne Hurwitz Northrop Grumman James A. Keenan US Army Jeffrey R. Laube Aerospace Corporation Thomas E McLaughlin Air Force Academy John D Schmisseur UTSI Huge Thanks to Betty for Pulling Together the TC/PC Data

Overview of Clean Sheet Analysis SciTech 2015 TAC Meeting Asked to look at look at a “Clean Sheet” of the TC/PC structure Spent some time understanding current structure and status of the TC/PCs Moving on to look at “clean sheet” Status Identified initial questions and issues Collected current data on TCs/PCs One third of the TCs/PCs not doing well – one third doing more than half the work Metrics easy to identify for some TCs (awards, etc), not so easy for others (History TC) TC stand-up and sunset – no nurturing or sunset methodology for starting or eliminating TCs Way forward: SciTech Workshop Value of TC/PC-like part of AIAA – what should they be doing to serve the membership (metrics) Organization – how should “they” be organized to best serve and engage the membership TAC Feedback: Move forward with “Clean Sheet” Workshop Sunday Before SciTech

Terms of Reference of “Clean Sheet” What are the "requirements" of a TC or PC (functions)? Are there categories of functions (i.e. technical, outreach, standards) etc.? What does the aerospace community need (Academia, Industry, Government)? What do you get from other professional societies that AIAA does not provide (in context of the TCs/PCs)? 2. Why are these functions enhancing to the AIAA community? What is it that is unique? What is the specific value and why? What is the cost (i.e. is this massively expensive or is there a mechanism for AIAA to recoup the costs)? 3. What should a TC or PC do to meet that need (i.e. how)? What do TCs/PCs do well? What do TCs/PCs not do well? Inclusion of all versus exclusively for those who participate (Community of Interest vs. Community of Practice Sunsetting and start up - ideas on how to control this better

Example Initial Answers from Tom McLaughlin What are the "requirements" of a TC or PC (functions)? A TC or PC must serve as the AIAA focal point for a technology area. They have a responsibility to provide a venue where interested parties can gather to exchange findings, advocate new technology thrusts, honor members of the community for their contribution, further cross-disciplinary interchange, and advance the interests of the technology. Where necessary, these units should provide the technical expertise and institutional framework to support the development of standards, summary documents, and advocacy materials to the AIAA leadership and community.

Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Agenda Attendance at NIS Meeting TAC Newsletter Status NIS Action Items Guidelines and Forms for TC/PC Fundraising – Sophia Bright & team TC/PC “Clean Sheet” Review – Robbie Robertson & team Including 2017 TAC Workshop Planning Digital Systems Integration Program Committee

Digital Systems Integration Program Committee Proposal September 2016 Digital Systems Integration Program Committee Proposal Points of Contact: AIAA Digital Systems Working Group Chair, Mat French (LibertyWorks/Rolls-Royce) AIAA Digital Systems Subject Matter Expert, Dr. John Matlik (Rolls-Royce) AIAA AD&S Group Director, Dr. Achille Messac (Howard University) AIAA Information Systems Director, James Rankin (Univ Arkansas) AIAA TAC Program Committee Coordinator, Mark Melanson (LMCO)

Supporting Objective for charter Establish a Digital Systems Integration Program Committee (DSPC) to: Accelerate integration of new & existing ‘digital’ capabilities for improving US national competitiveness, security and operational readiness Establish an Aerospace forum for integrating currently disparate ‘digital’ activities (e.g. Digital Twin, Digital Thread, ICME, BIGDATA, etc.) Support constituent groups in the organizational development and creation of a technical program related to Digital Systems. Recommend simplifying maintenance activities to reduce maintenance costs Create environments to encourage the development of a ‘digital culture’ within member organizations AIAA - Digital Systems Integration Program Committee

Benefit opportunity … in cost INCOSE Systems Engineering Handbook, v. 3.2.1 AIAA - Digital Systems Integration Program Committee

Relevance to a product life cycle … 29 29 NPI Integrate “as-built” with “as-designed” EIS Digital solutions for “Virtual Overhaul” CPI Service experience Certification* ‘As Designed’ Product ‘As Validated’ Product ‘In Service’ Product HPC & Data Analytics for “Virtual Certification” Certification Knowledge & Methods Integrate “as-used” with “as-designed” Service Knowledge & Methods Strengthen Design to Manufacturing “Handshake” * Link into virtual certification activities

For example … a potential future digital capability framework A digital systems viewpoint of capability Big Data? Note that interoperability is key difference from iCloud activities. The more digital industry becomes, the more interoperability becomes challenging. Use Case Example For example … a potential future digital capability framework 30 AIAA - Digital Systems Integration Program Committee

Includes geometry & functionality For example…ICME use case Includes geometry & functionality Traditional CAD only looks at geometry, but need to expand to include product definition & function across the life cycle Example: “ICME … aims to integrate computational materials science tools into a holistic system that can accelerate materials development, transform the engineering design optimization process, & unify design and manufacturing.” Integrated Approach • Quantitative • Digital Data and Processes • Standards • Improved Interfaces to Designers, Manufacturers, and Users 2008 NRC Study sponsored by DoD & DoE http://www.nap.edu/catalog.php?record_id=12199 31 AIAA - Digital Systems Integration Program Committee

Importance of collaboration <TITLE>System Operational Models (e.g. ConOps) System Models Component Models Influence Standards across System Functional product allocation Physical product decomposition Business model & requirements Digital Lifecycle “Twin” “Thread” “Environment” Virtual “Design & Cert” Environment Virtual “Make” Environment Virtual “Use” Environment Functional System Decomposition Allocated to Physical System** 8 System Subsystem Unit Component Part Assembly Material System of Systems Physical System Decomposition Spans Multiple Organizations* A digital system has multiple interfaces to acknowledge & manage Sources: *Jimenez, French. “SE_CoS_for_G135_Face_to_Face_Meeting.” AIAA Aerospace Systems Integration Working Group, PowerPoint Presentation, January 2012 ** Picture source - OMG SysML Tutorial 32 AIAA - Digital Systems Integration Program Committee

Membership Roster Michel Ingham – NASA JPL Ed Kraft – USAF AEDC John Hsu – California State Univ Mark Melanson – LMCO James Rankin – Univ of Arkansas Melanie Lorang – Boeing Michelle Bailey – DAU & GWU Mat French – LibertyWorks/Rolls-Royce John Matlik – Rolls-Royce Eric Tuegel – AFRL Steve Engelstad – LMCO Alex Selvarathinam – LMCO Steve Wanthal - Boeing Alicia Kim – Univ of Calif, San Diego Barron Bichon – SwRI Ben Thacker - SwRI Ed Kraft – USAF AEDC Michael Sangid – Purdue University Steven Arnold – NASA GRC Joshua Dustin - GE Aviation Evan Pineda – NASA GRC Jason Hui – BAE Systems Daniel DeLaurentis – Purdue University Vasisht Venkatesh – Pratt & Whitney Ajit Roy – AFRL Stephanie TerMaath – Univ of Tenn, Knoxville Wenbin Yu – Purdue University Ali Najafi – ANSYS Gregory Odegard – Michigan Tech Anthony Waas – Univ of Washington Dave Loda – NCPS Research AIAA - Digital Systems Integration Program Committee

AIAA Technical Committee Relationships Digital Systems PC will host AIAA members and non-traditional AIAA members that might not be inclined to join a TC, but is nonetheless interested in participating in creating digital system capability. (e.g. manufacturing, digital infrastructure & software, service providers, public-private collaborations, other professional societies, etc.) This PC will bring an aerospace focus on work being explored with many other professional societies (e.g. ASME, INCOSE, etc.) This PC will leverage DMDII by using AIAA as an outlet to share information for aerospace Product Support TC Digital Systems Systems Engineering TC* Digital Avionics TC non-AIAA members Intelligent Systems TC Materials TC non-TC AIAA members ICME Working Group Structures TC AIAA conferences MDO TC NDA TC Other TCs & PCs * Working Group/PC Sponsor AIAA - Digital Systems Integration Program Committee

Technical Committee Relationships The DS PC description and charter statement has been shared with the chair of the following committees: Systems Engineering TC ICME Working Group Materials TC Information Systems Group Structures TC Digital Avionics TC Multidisciplinary Optimization TC Product Support TC Nondeterministic Approaches TC Cooperation with other TCs/PCs has resulted in liaisons identified to participate on the DS PC: Michel Ingham – DATC & ISTC Michelle Bailey – SETC Chair John Hsu – SETC & AIAA Fellow Mat French – SETC & CASE Mark Melanson – TAC PC John Matlik – ICME & MTC Jim Rankin – IS Group Eric Tuegel – Digital Twin Melanie Lorang – BIGDATA Ed Kraft – Digital Thread AIAA - Digital Systems Integration Program Committee

Develop summary charter Next Steps Develop summary charter Betty has provided examples Provide summary presentation to be sent to all TCs and PCs Once the review is complete, present to NIS for concurrence Present to TAC for approval Present to Board for approval

Back-Up Materials

September 2016 Digital Systems Integration Program Committee Proposal (Full Presentation to NIS) Points of Contact: AIAA Digital Systems Working Group Chair, Mat French (LibertyWorks/Rolls-Royce) AIAA Digital Systems Subject Matter Expert, Dr. John Matlik (Rolls-Royce) AIAA AD&S Group Director, Dr. Achille Messac (Howard University) AIAA Information Systems Director, James Rankin (Univ Arkansas) AIAA TAC Program Committee Coordinator, Mark Melanson (LMCO)

Opportunities in Digital Systems Charter Statement Contents Impetus / Benefit Objective & Context Opportunities in Digital Systems Charter Statement History of Working Group Activity Membership Roster Related AIAA Committees Recommendation AIAA - Digital Systems Integration Program Committee

Benefit opportunity … in development time Global Horizons Missions Panel – Demonstrate 25% reductions in development cycle time by applications of the digital thread AIAA - Digital Systems Integration Program Committee

Benefit opportunity … in cost INCOSE Systems Engineering Handbook, v. 3.2.1 AIAA - Digital Systems Integration Program Committee

Context This PC will support an AIAA and non-AIAA constituency that is currently shaping a future digitally integrated advanced manufacturing enterprise. The PC focuses on creation of “digital system capability” to accelerate innovation & adoption of advanced manufacturing for Aerospace Industry benefit. The combination of platforms, infrastructure, and technologies that will enable this capability is not currently known, however it will certainly be multi-disciplinary and go beyond today’s federated elements. The value of the market opportunity is not yet well quantified, however it will surely include service offerings that go beyond today’s business models. The PC will engage students and constituents who are enthusiastic about future digital systems concepts. This PC will communicate with TCs to ensure that advanced ‘digital’ technology is brought forth across the broader AIAA community. The PC will focus on the technical aspects of digital systems and how they can help resolve top concerns from the business community This PC will help resolve the gap between high level (60kft) digital thread / twin concepts with low level (2ft) implementation activities - we will start putting meat on the bone. AIAA - Digital Systems Integration Program Committee

Digital system across the “V” Investigate improvements in critical elements of the “V” Interfaces between lifecycle phases Speed to mitigate and handle emergent behaviors Rapidly understand system impacts due to requirements changes “Fill the Vee” Fill the vee means virtual system representation / engineering across the Vee simultaneously with steps through vee process “Vee Outline” Sequential & linear representation of non-linear process Systems Engineering “V” Process* *Source: Kevin Forsberg, Hal Mooz. Visuaizing Project Management: Models and Frameworks for Mastering Complex Systems. Hoboken: John Wiley & Sons, Inc., 2005. Speed through Digital Thread to Outline & Fill the Vee

Objective Establish a Digital Systems Integration Program Committee (DSPC) to: Accelerate integration of new & existing ‘digital’ capabilities for improving US national competitiveness, security and operational readiness Establish an Aerospace forum for integrating currently disparate ‘digital’ activities (e.g. Digital Twin, Digital Thread, ICME, BIGDATA, etc.) Support constituent groups in the organizational development and creation of a technical program related to Digital Systems. Recommend simplifying maintenance activities to reduce maintenance costs Create environments to encourage the development of a ‘digital culture’ within member organizations AIAA - Digital Systems Integration Program Committee

Information from Product Lifecycle not digitally connected What is a Digital System? FABRICATE Today’s “Siloed” Process FABRICATE PRODUCT LIFECYCLE FABRICATE Cert reports Qual reports In-service inspections FSR reports etc FABRICATE QUALIFY AFTER- SALES SERVICE END OF LIFE REUSE RECYCLE DESIGN ASSEMBLE SELL & DELIVER Prints CAD models Inspection records MRB Assembly drawings CAD models Assembly records Pass-off tests Inspection records Contractual records Prints CAD models Information from Product Lifecycle not digitally connected 46 AIAA - Digital Systems Integration Program Committee

Digital Thread: Data across the full product lifecycle What is a Digital System? FABRICATE Tomorrow’s Process FABRICATE PRODUCT LIFECYCLE FABRICATE FABRICATE QUALIFY AFTER- SALES SERVICE END OF LIFE REUSE RECYCLE DESIGN ASSEMBLE SELL & DELIVER DATA INFORMATION DECISIONS VALUE 11001011 1101001001000111101101010111101111101 10101101101000010100100100011110111110101011110111110101111101111 010101001101010101101101010100100100101001001000111101010101111011111010111110111110101111 101101101010101010000011010101011011010101001010010010111101010010001111010101111011111010111110111110101111101111101 0001001010101111010101001001000111101101000100100011010101011011010101000101010110110101101001111011111010111110111110101111101111101011111011 101111011010011110111011010101010110010110100100011010101011011010101001001000111101010010100100100011110101111111101111101011111011111010111110111110101111101111101011111 Digital Thread: Data across the full product lifecycle 47 AIAA - Digital Systems Integration Program Committee

The “digital” opportunity … an every day example EXISTING ROAD DESIGN NEW ROAD DESIGN PLANNED IN-SERVICE REPAIRS ACCIDENTS LIVE USER FEEDBACK DATABASE Human Decisions with “Live” data 11001011 1101001001000111101101010111101111101 10101101101000010100100100011110111110101011110111110101111101111 010101001101010101101101010100100100101001001000111101010101111011111010111110111110101111 101101101010101010000011010101011011010101001010010010111101010010001111010101111011111010111110111110101111101111101 Digital Thread AIAA - Digital Systems Integration Program Committee

The “digital” opportunity … a supply chain example Tuned manufacturing to meet material spec Informed by physics models & digital data “As-made” feedback to Design SLAB Material Chemistry Initial Time-temp History Rolling Parameters Final Time-Temp History Micro-Structure & Props Human Decisions with “Live” data DATABASE (Siemens VAI) 11001011 1101001001000111101101010111101111101 10101101101000010100100100011110111110101011110111110101111101111 010101001101010101101101010100100100101001001000111101010101111011111010111110111110101111 101101101010101010000011010101011011010101001010010010111101010010001111010101111011111010111110111110101111101111101 Digital Thread Spec Compliance AIAA - Digital Systems Integration Program Committee

The “digital” opportunity … an Aerospace example Defense & Civil Aerospace experience Digital data on asset specific usage “As-used” feedback to Design PART LIFING ALGORITHM TRAINING POWER SETTING THROTTLE MOVEMENTS OPERATOR & OEM FEEDBACK Human Decisions with “Live” data DATABASE (Microsoft Azure IoT Suite) 11001011 1101001001000111101101010111101111101 10101101101000010100100100011110111110101011110111110101111101111 010101001101010101101101010100100100101001001000111101010101111011111010111110111110101111 101101101010101010000011010101011011010101001010010010111101010010001111010101111011111010111110111110101111101111101 Digital Thread AIAA - Digital Systems Integration Program Committee

Relevance to a product life cycle … 51 51 NPI Integrate “as-built” with “as-designed” EIS Digital solutions for “Virtual Overhaul” CPI Service experience Certification* ‘As Designed’ Product ‘As Validated’ Product ‘In Service’ Product HPC & Data Analytics for “Virtual Certification” Certification Knowledge & Methods Integrate “as-used” with “as-designed” Service Knowledge & Methods Strengthen Design to Manufacturing “Handshake” * Link into virtual certification activities

For example … a potential future modeling marketplace framework A modeling viewpoint of the marketplace For example … a potential future modeling marketplace framework 52 AIAA - Digital Systems Integration Program Committee

A digital system design, manufacturing, and service information Digital system enabling capabilities Digital environment Digital Twin Digital Thread Big Data ICME … Design Environment Make Environment Use Environment Subsystem System Material ‘Digital Twin’ Digital product …… Digital product is NOT limited to manufacturing DSPC definitions*: “Digital Twin” - Virtual avatar of products and environmental assets using cloud based sensor fusion “Digital Thread” – Digital system information (e.g. functionality, structure, processes, throughput, efficiency, resources, etc.) across entire lifecycle A digital system design, manufacturing, and service information 53 *See DAU glossary of Defense Acquisition Acronyms & Terms for detailed and lengthy US DoD definitions AIAA - Digital Systems Integration Program Committee

For example … a potential future digital capability framework A digital systems viewpoint of capability Big Data? Note that interoperability is key difference from iCloud activities. The more digital industry becomes, the more interoperability becomes challenging. Use Case Example For example … a potential future digital capability framework 54 AIAA - Digital Systems Integration Program Committee

Includes geometry & functionality For example…ICME use case Includes geometry & functionality Traditional CAD only looks at geometry, but need to expand to include product definition & function across the life cycle Example: “ICME … aims to integrate computational materials science tools into a holistic system that can accelerate materials development, transform the engineering design optimization process, & unify design and manufacturing.” Integrated Approach • Quantitative • Digital Data and Processes • Standards • Improved Interfaces to Designers, Manufacturers, and Users 2008 NRC Study sponsored by DoD & DoE http://www.nap.edu/catalog.php?record_id=12199 55 AIAA - Digital Systems Integration Program Committee

For example … a potential future global interoperable framework A global viewpoint of interoperability For example … a potential future global interoperable framework 56 AIAA - Digital Systems Integration Program Committee

Importance of collaboration <TITLE>System Operational Models (e.g. ConOps) System Models Component Models Influence Standards across System Functional product allocation Physical product decomposition Business model & requirements Digital Lifecycle “Twin” “Thread” “Environment” Virtual “Design & Cert” Environment Virtual “Make” Environment Virtual “Use” Environment Functional System Decomposition Allocated to Physical System** 8 System Subsystem Unit Component Part Assembly Material System of Systems Physical System Decomposition Spans Multiple Organizations* A digital system has multiple interfaces to acknowledge & manage Sources: *Jimenez, French. “SE_CoS_for_G135_Face_to_Face_Meeting.” AIAA Aerospace Systems Integration Working Group, PowerPoint Presentation, January 2012 ** Picture source - OMG SysML Tutorial 57 AIAA - Digital Systems Integration Program Committee

The reality of uncertainty & variability … DESIGN creates & defines the foundation for “belief” and “intent” for products & processes MAKE & TEST assesses & validates belief with “reality” of as-built “uncertainty” & “variability” CERTIFICATION & USE qualifies and updates reality to deliver “confidence” in the resulting product Reinforces networks of feedback between all stages increases system knowledge Future digital systems emphasize the importance of a lifecycle view AIAA - Digital Systems Integration Program Committee

Membership Roster Michel Ingham – NASA JPL Ed Kraft – USAF AEDC John Hsu – California State Univ Mark Melanson – LMCO James Rankin – Univ of Arkansas Melanie Lorang – Boeing Michelle Bailey – DAU & GWU Mat French – LibertyWorks/Rolls-Royce John Matlik – Rolls-Royce Eric Tuegel – AFRL Steve Engelstad – LMCO Alex Selvarathinam – LMCO Steve Wanthal - Boeing Alicia Kim – Univ of Calif, San Diego Barron Bichon – SwRI Ben Thacker - SwRI Ed Kraft – USAF AEDC Michael Sangid – Purdue University Steven Arnold – NASA GRC Joshua Dustin - GE Aviation Evan Pineda – NASA GRC Jason Hui – BAE Systems Daniel DeLaurentis – Purdue University Vasisht Venkatesh – Pratt & Whitney Ajit Roy – AFRL Stephanie TerMaath – Univ of Tenn, Knoxville Wenbin Yu – Purdue University Ali Najafi – ANSYS Gregory Odegard – Michigan Tech Anthony Waas – Univ of Washington Dave Loda – NCPS Research AIAA - Digital Systems Integration Program Committee

AIAA Technical Committee Relationships Digital Systems PC will host AIAA members and non-traditional AIAA members that might not be inclined to join a TC, but is nonetheless interested in participating in creating digital system capability. (e.g. manufacturing, digital infrastructure & software, service providers, public-private collaborations, other professional societies, etc.) This PC will bring an aerospace focus on work being explored with many other professional societies (e.g. ASME, INCOSE, etc.) This PC will leverage DMDII by using AIAA as an outlet to share information for aerospace Product Support TC Digital Systems Systems Engineering TC* Digital Avionics TC non-AIAA members Intelligent Systems TC Materials TC non-TC AIAA members ICME Working Group Structures TC AIAA conferences MDO TC NDA TC Other TCs & PCs * Working Group/PC Sponsor AIAA - Digital Systems Integration Program Committee

Technical Committee Relationships The DS PC description and charter statement has been shared with the chair of the following committees: Systems Engineering TC ICME Working Group Materials TC Information Systems Group Structures TC Digital Avionics TC Multidisciplinary Optimization TC Product Support TC Nondeterministic Approaches TC Cooperation with other TCs/PCs has resulted in liaisons identified to participate on the DS PC: Michel Ingham – DATC & ISTC Michelle Bailey – SETC Chair John Hsu – SETC & AIAA Fellow Mat French – SETC & CASE Mark Melanson – TAC PC John Matlik – ICME & MTC Jim Rankin – IS Group Eric Tuegel – Digital Twin Melanie Lorang – BIGDATA Ed Kraft – Digital Thread AIAA - Digital Systems Integration Program Committee

Recommendations Digital Systems activities should be integrated and approved to proceed together as a Program Committee to be known as the Digital Systems Integration Program Committee (DSIPC). AIAA - Digital Systems Integration Program Committee