Creation of a FIDES Lab model

Managing profiles

To have access to the profile management, you have to go to the Mission Profile tab

Table features

Profile management is based on 2 tables, before defining the mission profile, we will detail the generic features of tables.

As most Fides Lab tables, the profile table is made of 3 parts:

• Filter part at the top: typing a word in the text field will filter table and keep only line containing this word.
• The table itself
• The toolbar on the right contains buttons whose functions are defined below.

Button	feature
#i	Display the number of filtered lines
	Refreshing table
	Enable table edition (cell by cell instead of forms), don't forget to quit edition by clicking a second time on it, otherwise other features won't be available
	When table edition is enabled, you have to use this button to apply modifications
	This + button adds a new entity (an entity is an object corresponding to a line, here is the mission profile, it usually opens a window containing a form to edit the new entity
	Opens a form to edit the entity corresponding to the selected line
	Deletes the selected line(s)
	Copy the current selection to the clipboard
	Paste the previously copied element to the table, adding new line(s)
	Import table content from an EXCEL file
	Export table content into an EXCEL file
	Import data from a Open-Fides (the full entity, here the profile and its phases)
	Export selected profiles into Open-Fides format

If you want to edit a line (here the mission profile) in the standard mode, you have to double-click on any cell of the line. It will open a window that contains a form gathering all the editable fields of the profile.

If edit mode is activated (), each double-click enabled cell editing, you can type or copy/paste values in the cells.

Creating new mission profiles

You can create a new profile using the add () button of mission profile table. Then edit the form:

You can put any information you can in the text field but the fields with a red start () must not stay empty.

The purpose of a profile is to contain phases. The phases describe the mission profile and so must be defined.

Creating phases

When you select a mission profile on the left, the table of phases (on the right) displays the phases of the selection profile. By default, this table is empty since mission profiles are “empty” (without phase) when you create them. In order to increase the size of the right part, we recommend moving the vertical separator on the left like this:

Use the add () button of phase table to create a new phase, it will open the phase form:

All fields are mandatory, each one is related to the phase parameter defined in FIDES Guide, please refer to the guide for the definition of each parameter and its possible values. When the possible values are limited, a drop-down menu will let you choose the value. Most of the fields that require a numerical are followed by the unit. Units are very important to check, especially for people using other software having different default unit. Here most of the durations are in hour, and temperatures in Celsius degrees.

There is a specific GUI for π factors. In all the forms of FIDES Lab, π factors can be specified either with a numerical value or by answering questions in a specific π form. When you click on the π form button (), you must answer each question. The question are the ones of the guide; a description is added to help you to choose the right answer in the Response column. The weight column shows the importance of the answer in the total result.

Once you click on the OK button, the value of π application is no more editable.

if you want to be able to put a numerical value, you have to clear the π form, instead of clicking OK

It will close the form window and clear the π Application field, and it is now editable.

If you type an invalid value, the OK button of the phase form won't close the windows. Instead, it will display the invalid field in red.

Editing phase with phase table

Instead of opening the phase form to modify each phase, you can use the table edition mode. Once activated with the unlock button, you can edit cell by cell, copy/paste and select values in drop-down menu if available.

BOM-Tree

The BOM-Tree (or Product Architecture) is the description of the content of your product. A product is the top level of the hierarchy. This is the root node, you have to define the node adding a child in the tree hierarchy using the add () button. Keep in mind that the add button will provide different feature according to the selected node in the BOM. The possible hierarchy is in the following paragraph, check it to be sure you can create the item you want.

A product can be/contain one of these item:

• System: contains sub-systems
• Sub-system: contains equipment
• Equipment: can contain sub-assemblies, COTS, Part count, Hybrid MCM
• Sub assembly: can contain components, keyboard, sub-assemblies, COTS, Part count, Hybrid MCM
• COTS: contains functions
• Part count: contains Parts
• Hybrid MCM: contains Cavities

They are usually classified as Container, since they contain lower-level items. You may have noticed that you cannot create a component or other leaf item (without children) directly under product. You have to create the right hierarchy first, but it is not mandatory to create a System/Sub-system/… you can start directly at Sub-assembly level.

The only one container that can't be a product is the Cavity it must be inside a Hybrid MCM. The cavity can contain components, keyboard, sub-assemblies, COTS and Part count.

The hierarchy is made not only to organize your item but also to define parameters (Profiles and π factors) in a hierarchical way. If one parameter is defined for one item/container of the hierarchy, it is automatically defined for all its children (containers or leaf). Actually, for computations, the behavior of FIDES Lab is the following for each item:

• if a parameter is defined for one item, the value is used for calculations of this item
• if not defined, the software will look for the first parent in the hierarchy with a value for this parameter and use it. It means that modifying a container parameter can have an impact on all its components (expect for the component where the parameter is specifically defined)

BOM GUI (Add and edit)

When you use the add () button to create a container or a leaf, it will open a configuration window.

Here is an example of Equipment:

All items (whatever the hierarchy level) have a configuration window that contains at least a General panel where you can define:

• Name
• Quantity (if you have several identical items)
• Info 1 (you can take advantage of language files to change this name by a more relevant name)
• Info 2 (as for Info 2, nobody agreed on a name for this field, change it to what you need in your industry)
• Info 3 (you got it :-) )
• Description
• Schematic reference
• Function
• Miscellaneous

Copy / Paste / Delete

When you copy a leaf item (component, part, function, board/keyboard) you have to select the destination container before using the paste button. When you copy a container, it copies the container and everything that is inside. Select another container before using the paste button.

If you delete () a container, it will delete its content.

Edition panel

The edition panel of a component is made of 4 parts:

• General
• Computation
• Family Params
• Application Stresses

Synthesis table

Until the point, all setting is done thanks to dedicated forms. Forms are user-friendly for beginners, but for large models, a table view is more efficient. A table enables quick verification of a lot of data, and modifications are easy to do when you paste from EXCEL. That why FIDES Lab gathers the maximum data in a synthesis table.

Each time you click on an element of the BOM tree, the “Synthesis” table display the detail of this element in one line and all its children (in the hierarchy).

By default, the table cannot be edited, you have to unlock it before. Please refer to Table features section) for more details about table editing.

Structure

The H&MC component must contain cavities, and a cavity can contain any components, or sub-assembly, or COTS, or Part-count. But a H&MC cannot contain another H&MC.

Cavity configuration

A cavity has a dedicated Family params panel that enable a precise description of the cavity of a H&MC.

Components inside cavities

When a component is in a cavity you have access to HMC Macro family that contains families dedicated to H&MC. Otherwise you can configure it as any other component.