Tool Tips: Adding Records Out of Order in Xfmea/RCM++, Block Status/Function Indicators in BlockSim

Can I add records "out of order" in Xfmea and RCM++?
Beginning with version 4.0.5, both Xfmea and RCM++ allow you to enter data for a lower-level record in the FMEA Worksheet View without first creating the higher-level record(s) that it will be associated with. For example, if you type the Cause description in a row that does not yet have an Effect defined, the software will now allow you to type the Cause description and will enter a placeholder ("<undefined>") for the associated Effect record, as shown next.

Note: The Worksheet View also allows you to change the order of the columns by dragging the column header into the desired position. By combining these two features, you have the option to always enter causes before effects, if desired.

To determine the compile revision of the application on your computer, select About from the Help menu. For the latest updates of all ReliaSoft software, please visit http://www.ReliaSoft.com/downloads.htm.

What are the status/function indicators on blocks in BlockSim’s RBDs?
The blocks in a BlockSim reliability block diagram have different appearances depending on their status and function. The table shown next explains what each visual indicator means.

Visual Indicator	Block Type	Block Status/Function
	Block without any indicators	For blocks with no indicators, none of the following conditions apply.
	Inactive Block	An X through the block indicates that the block is inactive for reliability calculations (i.e. set to "off").
	Optimized Block	A green box at the lower right corner indicates that the block will be considered for optimization calculations.
	Mirrored Block	A grey box at the upper left corner of the block indicates that the block is a mirrored block. When simulation is performed, every event associated with the "target" block will be exactly the same for the "mirrored" block(s) because all of the blocks represent the exact same component in more than one location within the diagram.
	Static Block	A blue box at the lower left corner of the block indicates that the block has been defined with a reliability value at a fixed point in time or without respect to time.
	Subdiagram Block	A block that is in the shape of a folder represents another diagram within the same project.
	Node Block	A block that is circular in shape is a node block. In order for a system that contains node blocks to be successful, a specified number of paths must reach the node and the node must not fail (k-out-of-n configuration).
	Multi Block	A block that appears to be a stack of blocks represents more than one block with the same properties. These blocks can be configured in series or parallel.
	Container Blocks and Contained Blocks	A block that is transparent with a green border is a container block, which allows you to identify blocks that operate in a standby or load sharing configuration. A block that is inside a container block is a contained block, which describes the characteristics of the items that operate together in the standby or load sharing configuration. If a container is resized so that contained blocks become hidden/invisible, the borders of the container will become bold.