# Presentation: 858103

## JWST Integrated Modeling Environment

- James Webb Space Telescope

## The Task At Hand

- Create a tool to integrate the people,  processes and data used to conduct the Integrated Modeling effort for JWST.
- Requirements gathered from both the integrated modeling lead and from engineering discipline leads (who interact with the tool most often)

## Defining a Solution

- The tool should:
- build an archive of analysis results, including the documentation that identifies the assumptions and data elements used for each analysis.
- satisfies 400-PG-1440.7.2A, “Retention of Program and Project Technical Records by the Code 400 Directorate Library”
- satisfies the need for “knowledge capture”
- provide organized, efficient communication of analyses and their statuses.
- provide traceability to software types and versions used for each step of the analyses.
- allow for the reuse of previous analysis results.

## Approach

- Goals are to support integrated modeling team and their engineering processes
- Capture processes and place under configuration control
- Facilitate process execution
- Capture all assets used in each process step, provided by engineering team
- Team evaluated COTS solutions and external NASA solutions
- Potential MatLab/Simulink implementation, costly development to enable knowledge capture
- AFRL solution showed potential but mostly developmental
- Other COTS solutions either required extensive development, delays due to unavailable software, or missed major elements of either workflow creation, configuration control, and extendibility
- Turned to internal NASA network to identify possible working solutions
- Leveraged MSFC and LaRC efforts in Space Launch Initiative (now Next Generation Launch Technologies) engineering environment efforts in Code R
- Code R investment of 1.5 Years and many $M
- Established strategic partnership with Parametric Technologies Corp. (PTC)
- Also supporting LISA project with ramp up end of Summer into next FY.  Similar goals and level of support as JWST.

## Solution Architecture

- Leverage existing cross project framework, hardware, and software in Code 592
- Build from the Virtual System Design Environment (VSDE) capabilities
- JWST Integrated Modeling activity already has users using VSDE capabilities
- Purchase and leverage Agency investment with Windchill product modules
- Windchill is a Product Lifecycle Management application from Parametric Technology Corporation.
- With LaRC direction and guidance we licensed elements of Windchill version 6.2 as core foundation
- Windchill provides rich capabilities for managing configurations, workflows, data and access control through a single web-based environment.
- Developed customized front end and integration software in JAVA, JSP, and XML

## At-a-Glance

- The Interface Menu:
- Individual User Worklist
- Model and Document Repository with Baseline Creation Capability
- Pre-defined Jitter and Stop Analysis Workflows
- Soon to be added: Customizable (Ad Hoc) Analysis Workflows

**Notes:**
Identify the image as an excerpt of the application view.

Worklists:
Individual views vs. managerial views.

Model & Document Repository:
Baselines (possible discussion of baselines vs. configurations?)
Location for model and document files that will be utilized during the analyses.

Pre-defined Analyses Workflows:
Process by which we selected these as the first.
Process used to define the flow, data and engineer relationships.

## Worklist

- Each user is presented with their unique worklist upon entering the IME.
- Their activities are tracked as Potential, Accepted and Complete.
- An engineer can accept an analysis task and immediately navigate to retrieve the details of the analysis and download the related models and documents.

- The Filter option in the toolbar is provided for Managers and Administrators.  It modifies the worklist view to display the analysis tasks based on the population selected.

**Notes:**
Discuss Potential, accepted and complete
Discuss interaction when part of a team

Discuss how an engineer would proceed from here.

## Models & Documents

- The Model Repository allows for the creation of a file structure and project assembly.
- The Project File Manager provides the ability to fully customize both the file and structure hierarchies.

**Notes:**
Discuss the layout of the Project File Manager screen: PDM structure on left, document structure and details on right

Files vs. Assembly

The example presented uses the file structure to organize models and documents by their appropriate disciplines.  The Assembly organization is formatted to represent the major components of the observatory.

## Models & Documents: cont.

- The Project File Manager accepts any file type.
- Document Associations
- Allows linking between documents.
- Allows document association to Assembly parts

**Notes:**
Describe document view.
 - accepts any type of document
 - allows for linking documents together
	ability to attach notes specifying the reasons for the associations

Deleted files and folders view and recovery.

## Analysis Management

- Analysis Management can be accomplished at the project level and at the component analysis workflow level.
- The project level row depicted represents a single Jitter Analysis Workflow with a view into the status of each of the component analyses.
- The User has the ability to review the workflows based on their statuses: Running, Suspended, Executed or Terminated.
- The “Actions” drop down selection is present for authorized users allowing for the Creation, Suspension, Completion and Termination of the analysis workflows.

**Notes:**
Define this as view for both project level and analysis level workflows.

## Analysis Management – cont.

- Analysis Summary View – also available at the Analysis Workflow Level
- Lists Details of the analysis.
- Displays the data dictionary attributes for the analysis.

- Additional Views Listed in the drop down selection:
- Models
- Documents
- Workflows
- Supporting Analysis
- Dependant Analysis
- Analysis History

**Notes:**
This view is also available at the analysis Workflow level.

Define Data Dictionary attributes.

Other Views:
Models: Displays the list of models used for the analysis.
Documents: Provides access to the documents posted by the engineer at the conclusion of the analysis.
Workflows: Details all of the workflows that utilized this analysis.
Supporting/Dependent Analysis
Analysis History

## Solution Specifications

- Technical Requirements:
- Hardware:
- 1 Windchill Server
- 1 Oracle Server
- Software
- Windchill 6.2.6
- Desktop Applications
- Java 1.3.1 Plug-in
- ProductView

## JIME, the JWST Integrated Modeling Environment

- A  tool to integrate the people,  processes and data used to conduct the Integrated Modeling effort for JWST.
- JIME builds an archive of analysis results, including the documentation that identifies the assumptions and data elements used for each analysis.
- JIME provides organized, efficient communication of analyses and their statuses.
- JIME provides traceability to software types and versions used for each step of the analyses.
- JIME allows for the reuse of previous analysis results.

## Demonstration

- Live Demonstration:
- Review of Worklist
- View of File Manager
- Model Document Addition
- Review of Analysis Management
- Create New Analysis

**Notes:**
Browser Real Estate: Discuss the elements.

Review of Worklist
Individual user only sees their active worklist.
Potential: Presented to all members of a team.
Accepted and completed are unique to each user.
Admin/Manager has the ability to change the view using the filter.

View of File Manager
Review the layout of the Project File Manager screen: PDM structure(files/Assemblies) on left, document details on right.
Reiterate difference between files and assembly. – supports documentation of a model that spans several components of the assembly
Show ease and flexibility of adding folders.  (Add folder “DemoExample”)
Recover deleted folder.  Discuss feature. (Delete DemoExample – view as deleted)
Discuss the document data elements: Properties, Associations and Attributes

Model Document Addition
Demonstrate the addition of a file.

Review of Analysis Management
Review the layout of the Analysis Workflow Status views: Managerial "project" level, and "specific" analysis level
Review tabs: running, suspended, executed, terminated
Demonstrate navigation of analyses and sub analyses.
Discuss behind the scenes workflow
	auto initiation of communication of new analysis
	communicates throughout the life cycle to the appropriate team members when their portion of the workflow becomes active
	define steps:  notification, data download, analysis run, data upload, notification
Demonstrate and discuss workflow summary views.

Create New Analysis
Demonstrate the creation of a new analysis run.

## Questions & Answers

- Audience Inquiries?

- Presented by Johnny Medina and Chris Holtery with insights provided by Gary Mosier.