Sunday, 31 July 2016

Security. Understanding People, User, and Labor Records in MAXIMO

When you create records for individuals,the system requires the creation of additional records in the following cases:
Labor- You use the Labor application to create and manage labor records for employees and contractors who perform work on tickets and work orders. Labor records contain information about an individual’s skills and qualifications. These records are used toplan and schedule work, and to track labor costs for tickets and work orders.
A labor record must have a person record associated with it. A labor record needs a user record if the laborer is going to use the system to view work orders, report labor hours, and so forth. You can associate a labor and user with the same person record. As a best practice, you createcraft records for different job skills and qualification records for certifications, and record that information about the labor record. Other resources records are optional, but not required. For example, a labor record can have:
  • One or more crafts
  • One or more skill levels associated with a craft
  • One or more qualifications
Person - You use the People application to create and manage records for individuals. A person record contains basic information about an individual’s name, address, contact information,and other generic information.
A person record does not require any other resource records, such as craft, labor, user, and so forth. However, you must create a person record when you create a user record or labor record. You can associate a single person record with both a labor and user record.
A person can be a user and a laborer or neither. For example, someone calling the service desk to make a service request does not need to be a user, but your company might require that a person record exist for that user.
As a best practice, create a person record for any individual whose name appears anywhere on a record. For example, someone calling the service desk might not need a user ID to access the system. However, you can use person records to check if the individual is authorized to make a service request.
To manage employee information, you can create person records for all of your employees and contractors. Alternatively, you can create person records for laborers and others who must access the applications as part of their jobs.
User - You use the Users application to create and manage records for users. User records contain user names, passwords, and security profiles that determine which applications, options, and data a user can access. A user must have a person record. A user record can be associated with only one person record, and a person record can be associated with only one user record. You can associate a labor record and user record with the same person record.
Other resource records (labor, craft, and so forth) are optional, but not required. If you create new user records and you do not specify a value in the Person field, the system prompts you to create a matching person record for the user record.
You create a user record for anyone who must log into the system to view create or manage records.

Maximo Asset Management and SmartCloud Control Desk Migration Series

Abstract

This series is intended to assist our customers in planning their upgrade to the latest versions of Maximo Asset Management and SmartCloud Control Desk. The bulk of this series will be devoted to the Maximo product suite, add-on's and industry solutions.

In each session, a member of the business architecture team will deliver a presentation chronicling the incremental enhancements made in the product as well as point out functional changes to existing features. Ample time will be allowed for customer questions. Attendees will come away with a better understanding of what to expect, functionally, after the upgrade. This information should prove valuable for customers in determining customizations and configurations that could be modified or removed upon implementation of the latest version. Who should attend these sessions? Any current Maximo customer who is on version 6.x or 7.1.x and is planning to upgrade to version 7.5 or any customer who plans to upgrade to or implement the latest version of SmartCloud Control Desk. Review the session schedule to determine who from your organization is the best fit for each topic.

This session is also open to any IBM business partner or IBM employee who would gain useful information in helping your clients upgrade to the latest versions of Maximo or SmartCloud Control Desk. Please note that these sessions are primarily intended for customers. If time allows, business partners and IBM employees can pose questions after all customer questions have been addressed.

Content

Session topics, with the recording playback Amazon Cloud Download links are listed below.

Session Topic
Date
Playback Amazon Cloud Download links
Integration
17-Jul
Amazon Cloud Download link
ERP Adapters
19-Jul
Amazon Cloud Download link
Reporting
24-Jul
Amazon Cloud Download link
Email, Workflow, Esclations
26-Jul
Amazon Cloud Download link
Security
2-Aug
Amazon Cloud Download link
Migration Manager
7-Aug
Amazon Cloud Download link
Archiving, Monitoring
9-Aug
Amazon Cloud Download link
Scripting
14-Aug
Amazon Cloud Download link
Nuclear
16-Aug
Amazon Cloud Download link
Work Management
21-Aug
Amazon Cloud Download link
PMs, Meters, Condition Monitoring
23-Aug
Amazon Cloud Download link
Labor, Person, Craft
06-Sep
Amazon Cloud Download link
Utilities
11-Sep
Amazon Cloud Download link
Assets and Locations
13-Sep
Amazon Cloud Download link
Control Desk
18-Sep
Amazon Cloud Download link
Life Science, Calibration
20-Sep
Amazon Cloud Download link
Scheduler
25-Sep
Amazon Cloud Download link
Crew Management and Healthcare
27-Sep
Amazon Cloud Download link

Where clause for condition node in workflow for definition related records in not final status

For TICKET: 
(select count(1) from ticket where origrecordid = :ticketid and origrecordclass = :class and status not in ('CLOSED', 'RESOLVED')) = 0
and
(select count(1) from workorder where origrecordid = :ticketid and origrecordclass = :class and status not in ('CLOSE', 'REJECTED', 'CAN', 'FAILPIR', 'COMP', 'FAIL', 'REVIEW')) = 0
For WORKORDER: 
(select count(1) from ticket where origrecordid = :wonum and origrecordclass = :class and status not in ('CLOSED', 'RESOLVED')) = 0
and
(select count(1) from workorder where origrecordid = :wonum and origrecordclass = :class and status not in ('CLOSE', 'REJECTED', 'CAN', 'FAILPIR', 'COMP', 'FAIL', 'REVIEW')) = 0

Installation of Maximo Content Pack from Local Directory

Even if you cannot access the internet, you can still install Smartcloud Control Desk content packs using using Content Installer.  However, you must first download the content pack remotely and then copy it to your SCCD server.
To install content packs from behind a firewall, complete the following steps.
  1. Create an XML file called ContentSource.xml in the C:\temp directory on your Smartcloud Control Desk server system that contains the following text:
    <?xml version="1.0" encoding="UTF-8"?>
    <catalog infourl="" lastModified="" owner=""
      xmlns:tns="http://www.ibm.com/tivoli/tpae/ContentCatalog"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="ContentCatalog.xsd">
      <catalogItem>
        <version>Enter the version number of the Content Installer pack, for example 7.5.1</version>
        <type>mriu</type>
        <name>Enter the name of package</name>
        <description>Enter a description of the package here</description>
        <homepage/>
        <licenseurl/>
        <category>Describe the category of the content</category>
        <url>file:////C:\temp\TestPackage.zip</url>
      </catalogItem> 
    </catalog>
  2. Edit the name and description and the category according to the content that you are installing. Change the file name in the URL to the name of the content pack zip file.
  3. Save the file.
  4. Copy the content pack zip file to the C:\temp directory on the server.
  5. Go to the ISM Content Installer application: System Configuration>IBM Content Installer.
  6. Click the New icon.
  7. Enter the location of the ContentSource.xml that you created in step 1 and a description. The file name in our example is:  file:////c:\temp\ContentSource.xml
  8. Click Save.
  9. Click the newly created content source.
  10. Click the download link to install the content.

Saturday, 18 June 2016

Differentiating ReportedBy and AffectedBy when using Classifications in SR

Question

I change the ReportedBy user in the Service Request but I'm not getting an updated list of classifications based on my new User. I can see the classifications that belonged to the original user. Why?

Cause

I'm creating an SR and I select ReportedBy User1, the list of classifications is populated but once I change that user to User2, the classifications aren't being updated based on the updated ReportedBy user.

Answer

The classification is filtered according to the Customer field. When you
add the User1 as Affected By, User1 is also added into Affected Person
that adds the Customer (customer) on the customer field. The customer field
is linked with Affected By person and not Reported By.
So when you change Reported By to User2, the Affected Person and
Customer fields are not changed. That is why an updated list in classifications is not being
displayed when you change the Reported By.


The customer comes from the Affected By, not the Reported By.

1. Go to SR app.
2. New SR
3. Entered Sinclair in Reported By. Sinclair also appeared in the
Affected By and Gillette appeared in the Customer field
4. Tabbed to the Affected By and replaced Sinclair by Reid. Received a
warning message about changing Customer value. I clicked on Accept My
Value.
5. Reid displayed in the Affected By field, and the Customer was
changed from Gillette to DCH.

Setting Site on SRs created from chats

Question

How do I change the default site that gets applied to a Service Request created from a chat so that it matches the SITE of the person who reports it?

Answer

1) Create a crossover domain with the following settings:

Name: SR_SITE
Object: PERSON
Validation Where clause: personid=:reportedby
Source field: LOCATIONSITE
Destination field: SITEID

2) Associate the created domain to the SR.REPORTEDBY attribute with Database Configuration

3) In the Attributes tab, select the REPORTEDBY attribute and click on the Edit Lookup Map button that is beside the trash button

4) Create a lookup map with the following settings:

Target Attribute: SITEID
Source Object: Person
Source Key: Locationsite
Sequence: 1
Allow Null: checked

With that setting the livechat will be creating SRs, where the SITEID will be the same of the REPORTEDBY Site id.

Note that it is required that the Person record, in the Peoples applications have the Person's Site set.

Relating incident records to global issue not working



Problem(Abstract)

From an Incident select "Show Similiar Tickets' from action menu, check the relate incident records , click the 'relate records to global issue' , receive 'bmxaa4187e relationship called does not exist for the TICKET business object'

Cause

System does not allow you to relate incidents to global incidents.

Resolving the problem

Add the following relationship to the INCIDENT object.
Field Value
Relationship GLOBALINCIDENT
Where Clause ticketid=:globalticketid and class='INCIDENT'
Child Object INCIDENT
Remarks Relationship to the global incident for this
incident

IBM Readme for IBM Maximo Asset Management 7.6.1.3 Fix Pack

  Fix Readme Abstract This fix pack updates IBM® Maximo® Asset Management version 7.6.1, 7.6.1.1, and 7.6.1.2 Content IBM Maximo Asset Manag...