Use the Preferences page to manage many of the configurable settings within XFRACAS. Permissions required to access this page: Access Admin Tab, and Mange System Wide Preferences or Manage Entity Preferences.
To open the page, choose Admin > Configure > Preferences.
Choose Admin > Preferences > Save to save any changes.
If your implementation has more than one entity, some preferences apply to the entire website (System-Wide Preferences) and the rest will be managed separately for each entity. The drop-down list at the top of the page determines which entity-specific preferences are currently displayed.
Tip: In the website, preferences are grouped by type (e.g., true/false, date, string, etc.) and listed alphabetically. In the documentation below, related preferences are discussed together when applicable (i.e., not always in alphabetical order).
Secure Socket Layer Protection
SSL Server Mode Required: If True, the website will use https (rather than http) when building links. Before you enable this option, make sure the IIS web server is configured properly for SSL/TLS (as discussed in the XFRACAS Implementation Guide).
SSO Authentication - XFRACAS uses Windows authentication by default. Alternatively, if your web server is set up to support SSO authentication, XFRACAS will check for the "Auth_User" variable by default. If your SSO method has been configured to use a different variable, set the following preferences:
Single Sign-On (SSO) Authentication Enabled: If True, indicates that your web server is set up for SSO authentication and uses a variable other than "Auth_User."
Single Sign-On (SSO) Server Variable: The alternative variable that XFRACAS needs to check for SSO authentication.
The admin/TESTSSO.aspx page on the website provides additional details to help with troubleshooting the configuration.
Location of the XFRACAS Website
XFRACAS Server - Filesystem Prefix: The absolute path on the server where the website's IIS folder is installed (e.g., C:\inetpub\wwwroot\XFRACAS\).
XFRACAS Server - IIS Prefix: The path that can be used to build links to pages within the XFRACAS website (e.g., servername/XFRACAS or 10.0.0.2/xfracas).
Link to the SEP Website (if Applicable)
Synthesis - Display Synthesis Enterprise Portal (SEP) Command: If True, the XFRACAS ribbon will include a link to your organization's SEP website.
Synthesis Enterprise Portal Server - IIS Prefix: The path that can be used to build the link to the SEP website (e.g., servername/SEP).
Upload Files for Attachments
Attachments - Allow Uploaded Files: If True, the Attachments window will include the option for users to upload files. The files may be stored in the database or uploaded to a designated folder on the web server, depending on how you configure the related preferences.
Attachments - Store Uploaded Files in Database: If True, files will be stored in the database. If False, files will be stored in a designated folder on the web server.
Attachments - Uploaded Files Filesystem Prefix: If applicable, this is the absolute path to the folder on the web server where uploaded attachments will be stored (e.g., C:\inetpub\wwwroot\XFRACAS\uploads\ or D:\storage\xfracas) For requirements and instructions to prepare this folder, refer to the XFRACAS Implementation Guide.
Attachments - Uploaded Files IIS Prefix: If applicable, this is the path that will be used to build links to download files that were saved on the web server.
If you are using an actual file folder within the website, enter a relative path (e.g., uploads).
If you are using a virtual directory created in IIS, use an absolute path (e.g., http://servername/uploads).
SMTP Server for E-Mail Notifications
SMTP Server: The address of the SMTP server that will be used for sending e-mails (e.g., mail.servername.com or 10.0.0.2).
SMTP Port: The port used to connect to the SMTP server. If left blank, the default SMTP port 25 will be used.
SMTP Connection Timeout: The amount of time, in seconds, before the connection to the SMTP server times out when sending e-mails.
Use Web-based Help: If True, the help commands always open the most up-to-date help files from the Internet when possible. If False, they open the local help files that were installed with the software.
DIU Service - Generate Import Log: If True, an import log will be generated during an import. The log will be stored with the import record.
Terms of Use Agreement Page Required: If True, users will be prompted to accept an agreement the first time they access XFRACAS each day. To customize the content of the agreement, edit the files directly on the web server:
Agreement.aspx is stored in the website's main folder and will be displayed if the user visits any of the regular pages.
AdminAgreement.aspx is stored in the website's Admin folder and will be displayed if the user visits any of the admin pages.
Unknown Users - Allow Account Request: If True, users not already in XFRACAS can request access to the system, and users not already in an entity can request access to the entity.
Report Filter Display Max Rows: Indicates the maximum number of rows that a report can return and still have filtering and grouping capabilities.
DB Version and License Number: The database version and license number of the XFRACAS system. These are available for technical support purposes and cannot be changed.
CSI - Display CSI Wizard: If True, the Use CSI Wizard command will be available when users are creating new Customer Support records. The wizard prompts users to enter the data one step at a time, instead of all in a single form.
These preferences show/hide some of the fields in the Customer Support page. For information about how these fields are used, see Customer Support. To configure other fields for this record type, use the Details page.
CSI - Display Shipment Date
CSI - Display Delivery Date
CSI - Display Distributor
CSI - Display MTBF
CSI - Display MTBCF
CSI - Display MTBNCF
CSI - Display MTBI
CSI - Display Chargeable Incident Count
CSI - Display Non-Chargeable Incident Count
CSI - Enable Operational Availability
CSI - Display Calculated System Downtime
CSI - Display Unit Owner Address Information
CSI - Display Contact
CSI - Display Warranty Section
CSI - Display ASP Information (ASP and ASP Field Service Tech)
CSI - Commission Date Required: If True, the commission date is required in the Customer Support page. If False, the shipment date becomes a required field and will be populated based on the system build date if left blank by the user.
CSI - Create Incident Link Transfers Hours from CSI: This applies when the user clicks the "Create Incident" link in the Customer Support page. If True, the time metric field(s) in the incident (e.g., System Hours) will be populated based on the latest info in the CSI. (See Time Metric Calculations.)
CSI - Display All Authorized Service Technicians: This applies if the "CSI - Display ASP Information" preference is enabled. If True, all service technicians will be displayed in the drop-down list, regardless of the company they are associated with. If False, only service technicians associated with the selected company will be displayed.
CSI - Show All Unit Contact Names: This applies if the "CSI - Display Contact" preference is enabled. If True, the Contact field will show all contacts available in the system. If False, the list will be filtered by unit owner.
CSI - Extended Warranty Purchase Anytime: This applies if the "CSI - Display Warranty Section" preference is enabled. If False, the purchase date for the extended warranty must be within the date range of the initial warranty. (See Warranty Information Area).
Incident - Display Incident Wizard: If True, the Use Incident Wizard command will be available for new Incident records. The wizard prompts users to enter the data one step at a time, instead of all in a single form.
These preferences show/hide some of the fields in the Incidents page. For information about how these fields are used, see Incidents. To configure other fields for this record type, use the Details page.
Incident - Display Unit Location
Incident - Display Title (and Incident - Require Title)
Incident - Display Team Members
Incident - Display Potential Criticality and Incident - Display Actual Criticality (see Managing Criticality Fields)
Incident - Display Service Response Time/Date
Incident - Display ASP Field Service Tech (and Incident - Require ASP Field Service Tech)
Incident - Display Repair Duration
Incident - Display Repair/Replace Parts
Incident - Assign Creator as Owner: If True, the user who creates the incident will be assigned as the owner of the incident. If False, the incident owner depends upon the responsible part or the choice in the Owner field.
Incident - Display System Status: If True, the System Status field will show in part incidents, for information purposes only. This field is always hidden for simple incidents and always shown for serialized incidents. When applicable, the summary area of the Customer Support page displays the current status for a particular system based on all of the serialized incident reports for that unit.
These preferences specify whether to display calculated metrics in the summary for a serialized incident.
Incident - Display Calculated Response Time
Incident - Display Calculated Downtime
Incident - Auto-populate Time Metric 1: If True, the primary time/usage metric field (e.g., hours. miles, kilometers, cycles, etc.) will be populated automatically in a serialized incident when the required inputs are available. (See Time Metric Calculations.)
These preferences specify whether to track additional time or usage metrics (e.g., hours, miles, kilometers, cycles, etc.) in the Customer Support page and Incident page for serialized incidents and part incidents. By default, these three metrics are labeled "System Hours," "Number of Starts" and "kW Run Hours" but you can use the Resource Editor to customize the labels to fit your specific needs.
Incident - Display Time Metric 2
Incident - Display Time Metric 3
These preferences specify whether to automatically calculate the value of one time/usage metric based on the value entered for another. The behavior also depends on the "Display Time Metric" and "Time Metric Formula" preferences. (See Time Metric Calculations.)
Incident - Use Tree to Select Responsible Part: If True, the "Responsible Part" field in the Incident page will allow users to select one or multiple parts from a tree view of all system templates. If False, users can select only one part from a drop-down list. When the tree is used, you can also specify:
Incident - Auto-select Responsible Part for New Incidents: If True, the part number specified in the System/Component Information area will be selected by default in the Responsible Part tree.
Incident - Enable Responsible Part Filter: If True, the Responsible Part tree will only allow users to select parts from the system specified in the System/Component Information area.
Incident - Defaults: These preferences apply when the entity has only one system template defined. If True, then XFRACAS will automatically set relevant part fields when creating a new incident.
Incident - Default Part Number
Incident - Default Responsible Part
These preferences specify whether XFRACAS will automatically set date fields in the incident based on today's date.
Incident - Default Repair Date
Incident - Default Response Date
Incident - Require Date Field Validation: If True, the date in any date field on the Incident page cannot be less than the incident's creation date.
Incident/Problem - Display Audience Restriction and Incident/Problem - Require Legal Team Member: If both of these preferences are True, the Audience Restriction field will be displayed in the Incident page and Problem page after the record is created, and if the "Attorney/Client Privilege" option is selected for a particular incident or problem, then:
Only users assigned to the team for that record will be able to view it in any form. Make sure the "Incident - Display Team Members" and "Project - Display Team Members" preferences are also enabled so users will be able to assign an appropriate team before restricting access to the record.
The team assigned to the record must have at least one user assigned to the "Legal" team role. Only users who have the "Legal Expert" category in the Users page can be assigned to this role.
Incident - Display Customer Requested Feedback: If True, the "Customer Requested Feedback" check box is displayed in the Incident page and the "Report Sent to Customer" check box is displayed on the Failure Analysis page.
Incident - Closure: These preferences specify the conditions that must be met to close an incident. Select all that apply.
Incident - Closure Restriction Level 1: All actions for the incident are completed.
Incident - Closure Restriction Level 2: All failure analysis reports belonging to the incident are closed.
When an incident is closed, it no longer appears in the XFRACAS Portal under "Unclosed Incidents." Only users with the "Incident - Open a Closed Incident" or "Incident - Edit All Incidents" permissions can reopen a closed incident.
Incident - Disable Edit of Closed Incidents: If True, closed incidents will be read-only and can only be edited by users with either the "Incident - Open a Closed Incident" or "Incident - Edit All Incidents" permissions.
Allow Cross Entity Association: These preferences apply when assigning an incident to a problem or assigning a problem to a project. They also apply when creating an attachment to an XFRACAS record. If True, records from all entities that the user has access to will be available. If False, only records from the current entity will be available.
Incident/Problem - Allow Cross Entity Association
Project/Problem - Allow Cross Entity Association
Incident - Create Problem Link: These preferences apply when the user clicks the "Create Problem" link in the Incident page.
Incident - Create Problem Link Transfers Incident Description
Incident - Create Problem Link Transfers Incident Title
Incident - Create Problem Link Transfers Responsible Part (transfers to the problem's Part Category Code field)
These preferences show/hide some of the fields in the Problem page. For information about how these fields are used, see Problems. To configure other fields for this record type, use the Details page.
Problem - Display Team Members
Problem - Display Requested Closure Date
Problem - Display Expected Closure Date
Problem - Display Criticality (see Managing Criticality Fields)
Problem - Display Associated Incidents
Problem - Display Associated Projects
These preferences show/hide some of the fields in the Associated Incident Reports section on the Problem page.
Problem - Display Incidents by Status (open or closed)
Problem - Display Incidents by Chargeability (chargeable or non-chargeable)
Problem - Show Steps: These preferences specify which of the optional steps will be displayed on the Problem page in addition to the four steps that are always displayed: Establish the Team, Describe the Problem, Choose and Verify Permanent Corrective Actions and Prevent Recurrence.
Problem - Show Step - Implement and Verify Containment Actions
Problem - Show Step - Identify and Verify Root Cause
Problem - Show Step - Implement Permanent Corrective Actions
Problem - Show Step - Congratulate the Team
Problem - Always Show All Problem Steps: If True, after a user has entered the first step and created a new problem, the page will show all of the subsequent steps that need to be performed. If False, each subsequent step will be displayed only after the previous step is completed and saved.
Problem - Completed Date Warning: If True, entering a problem completed date that is in the future will show a warning.
Problem - Enable Created Date Restriction: If True, the problem's creation date must be earlier than the completion/sign-off date for any step in the problem.
Problem - FRB Sign-Off CC Restriction: If True, the priority order of FRB reviewers will be enforced. Once the first reviewer signs off on the problem step, the second reviewer can then review the step. Reviewers cannot sign off out of order.
Problem - FRB Sign-Off Restriction: This applies only if the "Problem – FRB Sign-Off Restriction" preference is True. If True, the review request e-mail will be sent only to the next FRB reviewer based on priority order. If False, the e-mail will be sent to all reviewers on the FRB reviewers list for the current step.
These preferences specify the conditions that must be met before a problem step or problem can be closed. Select all that apply.
Problem - Closure Restriction Level 1: All actions for the problem must be completed.
Problem - Closure Restriction Level 2: All incidents associated with the problem must be closed.
Problem - Closure Restriction Level 3: All actions associated with a problem step must be completed before you can close the step.
When a problem is closed, it no longer appears in the XFRACAS Portal under "Open Problems." Only users with the "Problem - Open a Closed Problem" or "Problem - Edit All Problems" permissions can reopen a closed problem.
These preferences show/hide some of the fields in the Project page. For information about how these fields are used, see Projects. To configure other fields for this record type, use the Details page.
Project - Display Team Members
Project - Display Target Completion Date
Project - Display Revised Completion Date
Project - Display Actual Completion Date
Project - Display Scope of Project
Project - Display End Result
Project - Show Associated Problems
Project - Show Associated Incident Reports
Project - Display Associated Incidents
Project - Show Associated FA Reports
These preferences specify the conditions that must be met before a project can be closed. Select all that apply.
Project - Closure Restriction Level 1: The actual completion date must be set and all actions for the project must be completed.
Project - Closure Restriction Level 2: The actual completion date must be set and all problems associated with the project must be closed.
When a project is closed, it no longer appears in the XFRACAS Portal under "My Projects." Only users with the "Project - Open a Closed Project" or "Project - Edit All Projects" permissions can reopen a closed project.
These preferences specify whether e-mails will be sent to the incident owner when a new incident is created, or when an existing incident is assigned to a new owner.
E-mail - Incident Creation
E-mail - Incident Owner Reassigned
These preferences specify whether e-mails will be sent to the problem owner when a new problem is created and the problem owner is not the same as the problem creator, or when a problem is assigned to a new owner.
E-mail - Problem Creation
E-mail - Problem Owner Reassigned
These preferences specify whether the Status utilities in each record type will include the E-mail Notify option.
E-mail - Action Status Update
E-Mail - Incident Status Update
E-Mail - FA Status Update
E-Mail - Problem Status Update
E-Mail - Project Status Update
If e-mail notifications are enabled for new/modified statuses, these preferences specify which check boxes will be selected by default.
E-mail - Action Status Update Associated Owner Checked
E-mail - Action Status Update Creator Checked
E-mail - Action Status Update Team Checked
E-mail - Incident Status Update Creator Checked
E-mail - Incident Status Update Owner Checked
E-mail - Incident Status Update Team Checked
E-mail - FA Status Update Associated Owner Checked
E-mail - FA Status Update Creator Checked
E-mail - FA Status Update Team Checked
E-mail - Problem Status Update Creator Checked
E-mail - Problem Status Update Owner Checked
E-mail - Problem Status Update Team Checked
E-mail - Project Status Update Owner Checked
E-mail - Project Status Update Team Checked
These preferences specify whether e-mails will be sent to the action owner when an action is created or when an existing action is assigned to a new owner.
E-Mail - CSI Action Creation
E-Mail - Incident Action Creation
E-Mail - FA Action Creation
E-Mail - Problem Action Creation
E-Mail - Project Action Creation
E-mail - Action Associated Owner on Creation: If True, e-mails will be sent to the owner of the parent record when an action is created. For example, creating an action associated with an incident will cause an e-mail to be sent to the incident owner.
E-mail - Action Owner on Update: If True, e-mails will be sent to the action owner when the owner, descriptions, date or statuses for an action are changed.
These preferences specify whether e-mails will be sent to the action owner when the due date is approaching or the action is past due. (See E-mails Based on Calendar Date.)
E-mail - CSI Action Due Date
E-mail - Incident Action Due Date
E-mail - FA Action Due Date
E-mail - Problem Action Due Date
E-mail - Project Action Due Date
These preferences specify whether the incident or problem owner will receive a copy of action e-mails based on due date.
E-mail - CC Incident Owner Action Due Date
E-mail - CC Problem Owner Action Due Date
E-mail - Send Action Due Notify Once: If True, e-mails will be sent only once when actions approach their due dates. If False, e-mails may also be sent at regular intervals when an action is past due. (See E-mails Based on Calendar Date.)
E-mail - Group Action Due Date: If True, only one e-mail will be sent for all of a user's actions approaching their due dates. If False, an individual e-mail will be sent for each action.
These preferences specify whether e-mails will be sent to the owner of the parent record when an action associated with that record has been closed.
E-Mail - CSI Action Closed
E-Mail - Incident Action Closed
E-Mail - FA Action Closed
E-Mail - Problem Action Closed
E-Mail - Project Action Closed
These preferences specify when e-mails will be sent to members of the Failure Review Board (FRB) in a problem.
E-mail - Reviewer Added to FRB: E-mails will be sent to reviewers when they assigned to an FRB.
E-mail - Send Problem Signed Off: E-mails will be sent to the problem owner and the reviewer when an FRB reviewer signs off on a step.
E-mail - Problem Signed Off by FRB (All): E-mails will be sent to the rest of the FRB when a reviewer signs off on a step.
E-mail - Problem FRB Not Signed Off: E-mails will be sent to the FRB reviewers when the requested closure date is approaching or past due. (See E-mails Based on Calendar Date.)
E-mail - Problem FRB Rejected: E-mails will be sent to the problem owner and the FRB members when a FRB reviewer has rejected closure of a problem.
E-mail - Group Problem FRB Not Signed Off: If True, only one e-mail will be sent for all of the problems for which a user is an FRB reviewer as a reminder that they need to sign off on a problem. If False, an individual e-mail will be sent for each problem.
E-mail - BCC Administrator on XFRACAS Data Sent: If True, the e-mail address specified in the "Administrator E-mail" preference will receive a copy of every e-mail sent that includes data from a CSI, incident, failure analysis, problem or project record (i.e., every e-mail where the printer-friendly view is included). This is a way of tracing that data from a security standpoint (such as an organization that has ITAR-related data).
E-mail - FA SAP Work Order Request: If True, e-mails will be sent when a failure analysis report requests an SAP work order (or a similar record from another enterprise resource planning system).
E-mail - Incident Customer Requested Feedback: If True, e-mails will be sent when a customer requests feedback on a failure analysis. The recipient is defined in the "E-mail - Customer Requested Feedback Notify To" E-mail preference.
E-mail - RMA Received to Problem Owner: If True, e-mails will be sent to the problem owner when a Return Materials Authorization (RMA) has been received. This only applies if the incident report that contains the RMA is associated to a problem.
Reports - Allow Send via E-mail: If True, the E-mail button will be available in the Reports page.
Reports - BCC Administrator on Data Sent via E-mail: If True, the e-mail address specified in the "Administrator E-mail" preference will receive a copy when report results are sent via e-mail.
Reports - Display Qualifiers: If True, the "Results based on the following qualifiers" area will be displayed in report results.
Reports - Include End Date Matches: If True, the end date set in a report is included in the results. For example, with a setting of True, a report of dates between Jan. 1, 2017 and Jan. 2, 2017 would include results for date matches from the entire days of Jan. 1, 2017 and Jan. 2, 2017. With a setting of False, the report would only include results from the entire day of Jan. 1, 2017. This applies if the "XFRACAS - Display Time with Date Fields" preference is set to False.
Action - Allow Setting Due Date Before Current Date: If True, users can enter an action date that is earlier than the creation date. This allows you to enter historical information that did not get entered when the action was actually performed.
These settings apply when using the Synthesis Data Warehouse in Weibull++ to extract data sets for life data analysis.
Analysis - Fixed Daily Operating Hours: If True, systems are considered to run constantly (i.e., 24x7). System operating time (system up hours) will be calculated based on numerous factors, including commission or shipment date, incident occurrence date, the "Incident - Max Units/Day" Integer preference and the system down time. If False, the times are those reported in either the incidents or in the CSI.
Analysis - Weibull++ Export Rollup: If True, failures of child parts will be considered to also precipitate failures of parent parts. If the System Down Event incident detail is available in the current entity, then for incidents that are marked as system down events, the failure will affect all levels above the child part all the way to the top level item. For incidents that are not marked as system down events, the failure will affect all but the top level item. If False, failures of child parts will not roll up to parent parts. It is important to note that if this preference is True, the times that are exported are the times between failures, not the failure times. If you are unsure if this analysis method is appropriate for you, please contact ReliaSoft for further information.
Lists - Autosize List Height: If True, the area used to display lists in the Lists page varies in height depending on the number of items in the list. If False, a scroll bar will be used to scroll through the list. Note that there is a maximum height of 300 pixels for any list, even when this preference is set to True.
Manage User - E-mail/Login Auto Build: If True, the user login and e-mail address fields will automatically be assigned in the Users page based on the user’s first and last names and the "Manage User - E-mail Suffix used for Auto Build" E-mail preference.
These preferences apply to the "data tree" on the Template page and the Serialized page. They also apply to the Responsible Part in incidents (when it is used as a tree) and for the Part Category Code in problems.
System - Data Tree Auto Collapse
System - Data Tree Sort by Part Description (rather than part number)
XFRACAS - Autopopulate Associated Record Dialog: This applies to all Assign/Find windows (e.g., when assigning an incident to a problem). If True, all records will be displayed when the window opens. If False, only currently assigned records will be displayed upon open and users can click Filter to see all records.
XFRACAS - Display Debug IDs: If True, the resource IDs will be shown in square brackets beside the name for all fields. You can use this in conjunction with the Resource Editor to customize text labels displayed in the website. In addition, the Detail Type IDs will be shown in square brackets on the Details page.
XFRACAS - Display Employee ID With User Name: If True, the employee ID will be displayed along with the user name in locations where a user is being selected (e.g., the Assign Team Members utility, drop-down lists, etc.).
XFRACAS - Display Last Updated Timestamp: If True, information on the last update of the record will be displayed in the summary area for incidents, problems, projects, failure analysis reports, CSIs and actions.
These preferences apply to all date/time input fields. Note that there are separate preferences for dates and times displayed as regular text (the "XFRACAS - Date Format - Long" and "XFRACAS - Date Format - Short" String preferences).
XFRACAS - Display Day Before Month in Date Input Fields: If True, Date input fields will display using the day before month format (e.g., "21 March 2017").
XFRACAS - Display Time with Date Fields: If True, the Time input fields will be displayed with applicable Date fields.
XFRACAS - Display Time in 24 Hour Format: If True, the Time field will display using a 24-hour clock. If False, it will display an A.M./P.M. indicator.
XFRACAS - Enable Header in Printed Records: If True, the print logo and full entity name will appear in the document header when records are printed using the Print Preview command on the Home tab. To change the logo, you can replace the logopfv.gif file stored in the Images folder on the web server (e.g., C:\inetpub\wwwroot\XFRACAS\Images\logopfv.gif).
XFRACAS - Sort Statuses by Descending Date: If True, the notes in the Status fields will be displayed in descending order based on creation date (i.e., the oldest note is listed first).
XFRACAS - Testing Mode: If True, a "watermark" that reads "TESTING" will be placed in the background of the pages to indicate that the "testing" version of the system is distinguished from the actual "live" system.
Fiscal Year Begins: The start date of the fiscal year, which is used to determine the current quarter when reporting information based on a specified date range. The value entered must be a valid date but the current year will always be assumed when calculating the date range. For example, if the fiscal year begins on January 1st, you can enter that date with any year (01/01/2005, 01/01/2020, 01/01/2015). XFRACAS will only consider the month and day.
Portal - What's New Modify Date: The date of the most recent modification to the What's New page maintained by your company (i.e., the Whatsnew.html page in the main folder on the web server where XFRACAS was installed). This page is displayed if the user has not visited the website since the page was last modified.
These preferences specify which type(s) of incident can be created, and which will be selected by default.
Incident - Display Part Incident Type
Incident - Display Serialized Incident Type
Incident - Display Simple Incident Type
These preferences specify whether the Failure Review Board (FRB) will be displayed for each step in the Problem page, and whether all assigned members are required to sign off users you can move to the next step.
Problem - Display FRB - Describe the Problem
Problem - Display FRB - Implement and Verify Containment Actions
Problem - Display FRB - Identify and Verify Root Cause
Problem - Display FRB - Choose and Verify Permanent Corrective Actions
Problem - Display FRB - Implement Permanent Corrective Actions
Problem - Display FRB - Prevent Recurrence
Problem - Display FRB - Congratulate the Team
XFRACAS - Language: The default language for the interface text. If the Language option in the user's account is blank, the interface will display in the default language. However, if the user's account specifies a language, the interface will display in the user's preferred language instead.
XFRACAS - Skin: Sets the appearance of the ribbon and some other elements within the XFRACAS interface.
Administrator E-mail: The e-mail address used for new user account requests and the place where the "E-mail - BCC Administrator on XFRACAS Data Sent" Boolean preference e-mails are sent.
E-mail - Customer Requested Feedback Notify To: The e-mail address where the customer requests for feedback notification will be sent if the "E-mail – Incident Customer Requested Feedback" Boolean preference is True.
E-mail - Default New Incident From: If specified, then the e-mail address on new incidents will come FROM this address. If the TO address is not valid, then the e-mails will get bounced back to this address instead of the specific user who created the incident.
E-mail - SAP Work Order Request To: The e-mail address where the SAP work order request notification will be sent if the "E-mail – FA SAP Work Order Request" Boolean preference is True.
E-mail - Single From Address: If an e-mail address is specified, then all e-mails sent from the entity will be "from" the specified address. If it is blank, the e-mails will be "from" the specific user who initiated the e-mail.
Manage User - E-mail Suffix Used for Auto Build: The suffix (e.g., @company.com) to be used for the e-mail addresses automatically generated for new users if the "Manage User - E-mail/Login Auto Build" Boolean preference is True.
CSI - Hours Decimal Places: The number of decimal places displayed in time figures in the Customer Support page.
CSI - Operational Availability Decimal Places: The number of decimal places that the Operational Availability percentage in the Customer Support page will be rounded to.
CSI - Warranty Months: These preferences set the number of months in the warranty period in the Customer Support page, if company-specific values have not been specified on the Companies page.
CSI - Warranty Months from Commission
CSI - Warranty Months from Shipment
CSI - X Warranty Days for Repaired/Replaced Parts: The number of parts that were repaired or replaced in the last X days. This information will display below the associated incidents on the Customer Support page.
Max Units/Day: These preferences set the maximum amount of time/usage (e.g., hours, miles, kilometers, cycles, etc.) that a serialized system may accumulate in a single day. The max value for Time Metric 1 is used in the Customer Support page to make sure the "Estimated System Hours" calculation does not exceed the maximum possible per day. It is also used if you have selected to auto-populate Time Metric 1 in the Incident page for serialized systems. (See Time Metric Calculations.)
Note that the max values for Time Metric 2 and 3 are relevant only if you are using a custom report that requires these inputs, or a custom method for extracting reliability data for analysis in Weibull++ or RGA.
Incident - Max Units/Day - Time Metric 1
Incident - Max Units/Day - Time Metric 2 (only for custom functionality)
Incident - Max Units/Day - Time Metric 3 (only for custom functionality)
Default Due Dates and Closure Dates: These preferences specify the number of days from today's date to set as the default due date for a new action or the default closure dates for new problems.
Action - Default Due Date Offset by X Days
Problem - Expected Closure Date Offset
Problem - Requested Closure Date Offset
These preferences specify the number of business days for e-mails based on calendar date.
E-mail - Action Due in X Days Offset: The number of days prior to the action due date that the e-mail reminder will be sent.
E-mail - Remind Action Due Every X Days: The number of days after the first or previous reminder of an action due date that another reminder is sent.
E-mail - FRB After Requested Closure in X Days Offset: The number of business days after closure has been entered on a problem that the FRB reviewers are sent an e-mail if they have not yet signed off on it.
E-mail - Remind FRB After Requested Closure Every X Days: The number of days after the first or previous notification has been sent that a reminder e-mail will be sent to the problem reviewers. This applies only to the reviewers for the final step.
These preferences set the number of days that records will be highlighted in the XFRACAS Portal.
Portal - Action Due Date Highlight Offset (days prior to the action due date)
Portal - Incident Due Date Highlight Offset (days after the incident occurrence date)
Portal - Problem Due Date Highlight Offset (days prior to the problem requested closure date - if the requested closure date is turned off, then the due date is calculated)
Portal - Problem to Review Due Date Highlight Offset (days prior to the problem review due date)
Portal - Project Due Date Highlight Offset (days prior to the project due date)
XFRACAS - Description Number of Lines Displayed: The default height for description fields (i.e., the maximum number of lines of text that can be visible without scrolling). For descriptions that are configurable detail fields, you can override this for a specific field by setting the Number of Lines Displayed in the detail properties.
Reports - Filter Display Max Columns: The maximum number of optional columns that a report created in the Report Builder can include.
XFRACAS - System Search Timeout: The maximum amount of time, in seconds, that the application can spend searching for a part in a system.
Diagnostics - Number of Exception Items Displayed: The maximum number of items the Diagnostics page can display on a single page.
Active Directory - Maximum Groups to Display: The maximum number of groups that will be displayed when loading Active Directory groups.
These preferences specify information that displays on the XFRACAS About page.
Administrator Name
Administrator Phone
Company Name
Company Homepage Link: This the anchor text for the link. The URL is specified in the "XFRACAS - Company Homepage" URL preference.
These preferences specify the formats of e-mails sent for incidents, failure analyses and problems. (See Configuring E-mail Message Formats.)
Incident - E-mail Message Format - New
Incident - E-mail Message Format - Customer Feedback
Incident - E-mail Message Format - RMA Received
Failure Analysis - E-mail Message Format - Work Order
Problem - E-mail Message Format - New
Problem - E-mail Message Format - Reject
Problem - E-mail Message Format - Signed Off
These preferences specify the formats of the e-mails for new, updated and completed actions associated with each record type. (See Configuring E-mail Message Formats.)
Action - E-mail Message Format - New - CSI
Action - E-mail Message Format - Updated - CSI
Action - E-mail Message Format - Complete - CSI
Action - E-mail Message Format - New - Incident
Action - E-mail Message Format - Updated - Incident
Action - E-mail Message Format - Complete - Incident
Action - E-mail Message Format - New - FA
Action - E-mail Message Format - Updated - FA
Action - E-mail Message Format - Complete - FA
Action - E-mail Message Format - New - Problem
Action - E-mail Message Format - Updated - Problem
Action - E-mail Message Format - Complete - Problem
Action - E-mail Message Format - New - Project
Action - E-mail Message Format - Updated - Project
Action - E-mail Message Format - Complete - Project
These preferences specify the format of the e-mails sent from the Status utility when a user adds a new status for the specified record type. (See Configuring E-mail Message Formats.)
Detail Status - E-Mail Message Format - Action
Detail Status - E-Mail Message Format - Incident
Detail Status - E-Mail Message Format - FA
Detail Status - E-Mail Message Format - Problem
Detail Status - E-Mail Message Format - Project
For fields that use drop-down lists, each issue in the list may have an e-mail address associated with it (see Managing Lists). These preferences specify the format of the e-mail sent when one of the monitored issues is selected for a particular record. (See Configuring E-mail Message Formats.)
Detail Drop-down - E-Mail Message Format - CSI
Detail Drop-down - E-Mail Message Format - Incident
Detail Drop-down - E-Mail Message Format - FA
Detail Drop-down - E-Mail Message Format - Problem
Detail Drop-down - E-Mail Message Format - Project
These preferences define the formulas used to calculate the criticality metrics for an incident or problem. (See Configuring Criticality Metrics.)
Criticality - Incident Actual
Criticality - Incident Potential
Criticality - Problem Base CIN
Criticality - Problem Current CIN
These preferences specify the formulas used to calculate the value of one time/usage metric based on the value entered for another. The behavior also depends on the "Display Time Metric" and "Always Auto-calculate Time Metric" preferences, and what the user enters in the incident page. (See Time Metric Calculations.)
Incident - Time Metric 1 Formula
Incident - Time Metric 2 Formula
Incident - Time Metric 3 Formula
Problem - Default Owner: The user who will be assigned by default as the owner for new problems.
These preferences specify the formats for dates. Note that this should match the IIS culture setting on the web server in order for dates in charts to be displayed correctly.
XFRACAS - Date Format - Short: Displays only the date and not the time. The default format is MM/dd/yyyy (e.g., 03/01/2017).
XFRACAS - Date Format - Long: Displays the time along with the date when applicable. The default format is MM/dd/yyyy hh:mm tt (e.g., 03/01/2017 01:00 PM).
If the "XFRACAS - Display Time in 24 Hour Format" Boolean preference is True, remove the "tt" segment from the long date format (e.g., MM/dd/yyyy hh:mm will display 03/01/2017 13:00).
If you want to display only the date (without the time), set to the same format as the short date field (e.g., MM/dd/yyyy) or set the "XFRACAS - Display Time with Date Fields" Boolean preference to False.
XFRACAS Decimal Separator: The text (usually a period or comma) used to indicate the decimal place in both input and output.
XFRACAS Thousands Separator: The separator (usually a comma, period or space) used to separate groups of thousands in both input and output.
XFRACAS - Web Page Title Suffix: The text that will be displayed at the end of the title in the browser caption bar (e.g., "Proprietary and Confidential Information").
Exchange ADS Path: The Active Directory Services Path used for an LDAP connection to the GAL (Global Address List). (See Entering an ADS Path.)
Default GMT Offset for New Users: The time zone, or offset from Coordinated Universal Time (formerly known as Greenwich Mean Time), that will be used when a new user is created if a different time zone is not specified for that user.
Tips URLs: For many fields in XFRACAS, a help icon next to the input box opens a separate HTML page designed to provide data entry tips for that particular field. You can customize the information in these pages to meet the particular needs of your organization. By default, they are installed in the "Tips" folder on the web server (e.g., C:\inetpub\wwwroot\XFRACAS\Tips), but you can change the URLs if desired.
These preferences specify the URLs for some of the fields that have tips. For other fields that are configured from the Details page (such as the Incident Description or the Problem Description), you can specify the "Tips URL" when you edit the settings for the special detail field.
Action - Description Tips
Action - Result Tips
Action - Status Tips
CSI - Installation Detail Tips
FA - Detailed Analysis Tips
FA - Fault Description/Troubleshooting/Rework Tips
FA - Initial Repairs/Comments Tips
FA - SAP Items
FA - Visual Inspection Tips
Incident - Actual Criticality Tips
Incident - Potential Criticality Tips
Problem - Criticality Tips
Problem - FRB Rejection Description Tips
Project - End Result Tips
Project - Scope of Project Tips
XSLT Style Sheet URLs: These preferences specify the URLs for the *.xslt style sheets for pages that have a Print Preview command in the ribbon. By default, these are installed in the "XSLT" folder on the web server (e.g., C:\inetpub\wwwroot\XFRACAS\XSLT), but you can change the URLs if desired.
CSI - Print Preview Style Sheet
FA - Print Preview Style Sheet
Incident - Print Preview Style Sheet
Problem - Print Preview Style Sheet
Project - Print Preview Style Sheet
XFRACAS - Company Homepage: The URL of your company's home page link that displays on the XFRACAS About page. The anchor text is specified in the "Company Homepage Link" string preference.
These preferences specify whether target and/or completed date fields will display in specific areas of the Incident page and Problem page.
Incident - Description - Show Target Date
Incident - Description - Show Completed Date
Incident - Resolution - Show Target Date
Incident - Resolution - Show Completed Date
Incident - Initial Failure Analysis - Show Target Date
Incident - Initial Failure Analysis - Show Completed Date
Incident - Additional Comments - Show Target Date
Incident - Additional Comments - Show Completed Date
Problem - Problem Description - Show Target Date
Problem - Containment Description - Show Target Date
Problem - Root Cause Verification - Show Target Date
Problem - Corrective Action Description - Show Target Date
Problem - Implement Corrective Action Description - Show Target Date
Problem - Prevent Recurrence Description - Show Target Date
Problem - Recognize Team Description - Show Target Date
© 1992-2018. HBM Prenscia Inc. ALL RIGHTS RESERVED.
 |
E-mail Link |