Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.



Relating SR Owner with Location

From: Ian Turner (2016-03-15 17:23)

Hello All, my first post so I'll try not to break the rules and ask a
sensible question that hasn't been answered 200 times before. I have
searched the group as best I can.
I want to allocate work orders to a particular contractor based upon the
location. We have several buildings that are maintained by contractor A and
several by contractor B. Allocation of the SR/work order, we thought, was
best done by setting each contractor as a People Group and allocating that
People Group as the SR owner. Hopefully this is an accepted way to deal with
this but I'm more than happy to be advised on this. What we also want to do
is drive that SR Owner from the location defined in the SR. We are
considering using the primary custodian for this but I worry this may be
needed for other uses in the future and although it is the primary
custodian, so a single option, I'd prefer to use a field in the locations
table (new field?). This seems like a common condition, is there a preferred
solution?

Thanks


From: Pat Morrow (2016-03-15 23:24)

We had a similar situation - not with buildings, but with locations spread over thousands of miles and wanted each location to be associated with a specific division.  (Using the location hierarchy did not entirely meet the corporate needs.)
1)    A field (xxx) was created on the location table and an aln domain associated with it.2)    There is a dispaly field in Assets that displays the xxx field from the location.  (Just  do a slight modification to the Asset app screen so it will be displayed.)3)    Location is REQUIRED on all WOs for this company and field xxx crosses over to the WO once a location is selected.  (Just add the new xxx field to the crossover domain and do a slight modification to the WO app screen so it will be displayed/sved with the WO.)
If and when (although I am sure that this would never happen!! :)  ) one or more of the buildings maintained by contractor A changes maintenance companies, it is a simple matter to search for all locations related to the building and change the value in field xxx to Contractor N (once Contractor N had been added to the domain).
Instead of using an aln domain (but this was really easy to set up), you could add the contractor the Companies table with a specific type.  Then set up a table domain from the Companies table that only shows the specific type. 
Custodians and Person Groups are also valid ways to handle this.  Custodians need to have the contractor set up in the Person table.  Same with putting contractors into a Person group - the contractor would need to be set up in the Person table, not the Company table.
 Pat Morrow
pmorrow8@yahoo.com
From: "'Ian Turner' ian.turner@salisburycamra.org.uk [MAXIMO]" <MAXIMO@yahoogroups.com>
To: MAXIMO@yahoogroups.com
Sent: Tuesday, March 15, 2016 8:23 AM
Subject: [MAXIMO List] Relating SR Owner with Location

  Hello All, my first post so I'll try not to break the rules and ask a
sensible question that hasn't been answered 200 times before. I have
searched the group as best I can.
I want to allocate work orders to a particular contractor based upon the
location. We have several buildings that are maintained by contractor A and
several by contractor B. Allocation of the SR/work order, we thought, was
best done by setting each contractor as a People Group and allocating that
People Group as the SR owner. Hopefully this is an accepted way to deal with
this but I'm more than happy to be advised on this. What we also want to do
is drive that SR Owner from the location defined in the SR. We are
considering using the primary custodian for this but I worry this may be
needed for other uses in the future and although it is the primary
custodian, so a single option, I'd prefer to use a field in the locations
table (new field?). This seems like a common condition, is there a preferred
solution?
Thanks
#yiv2439072626 #yiv2439072626 -- #yiv2439072626ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv2439072626 #yiv2439072626ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv2439072626 #yiv2439072626ygrp-mkp #yiv2439072626hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv2439072626 #yiv2439072626ygrp-mkp #yiv2439072626ads {margin-bottom:10px;}#yiv2439072626 #yiv2439072626ygrp-mkp .yiv2439072626ad {padding:0 0;}#yiv2439072626 #yiv2439072626ygrp-mkp .yiv2439072626ad p {margin:0;}#yiv2439072626 #yiv2439072626ygrp-mkp .yiv2439072626ad a {color:#0000ff;text-decoration:none;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ygrp-lc {font-family:Arial;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ygrp-lc #yiv2439072626hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ygrp-lc .yiv2439072626ad {margin-bottom:10px;padding:0 0;}#yiv2439072626 #yiv2439072626actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv2439072626 #yiv2439072626activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv2439072626 #yiv2439072626activity span {font-weight:700;}#yiv2439072626 #yiv2439072626activity span:first-child {text-transform:uppercase;}#yiv2439072626 #yiv2439072626activity span a {color:#5085b6;text-decoration:none;}#yiv2439072626 #yiv2439072626activity span span {color:#ff7900;}#yiv2439072626 #yiv2439072626activity span .yiv2439072626underline {text-decoration:underline;}#yiv2439072626 .yiv2439072626attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv2439072626 .yiv2439072626attach div a {text-decoration:none;}#yiv2439072626 .yiv2439072626attach img {border:none;padding-right:5px;}#yiv2439072626 .yiv2439072626attach label {display:block;margin-bottom:5px;}#yiv2439072626 .yiv2439072626attach label a {text-decoration:none;}#yiv2439072626 blockquote {margin:0 0 0 4px;}#yiv2439072626 .yiv2439072626bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv2439072626 .yiv2439072626bold a {text-decoration:none;}#yiv2439072626 dd.yiv2439072626last p a {font-family:Verdana;font-weight:700;}#yiv2439072626 dd.yiv2439072626last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv2439072626 dd.yiv2439072626last p span.yiv2439072626yshortcuts {margin-right:0;}#yiv2439072626 div.yiv2439072626attach-table div div a {text-decoration:none;}#yiv2439072626 div.yiv2439072626attach-table {width:400px;}#yiv2439072626 div.yiv2439072626file-title a, #yiv2439072626 div.yiv2439072626file-title a:active, #yiv2439072626 div.yiv2439072626file-title a:hover, #yiv2439072626 div.yiv2439072626file-title a:visited {text-decoration:none;}#yiv2439072626 div.yiv2439072626photo-title a, #yiv2439072626 div.yiv2439072626photo-title a:active, #yiv2439072626 div.yiv2439072626photo-title a:hover, #yiv2439072626 div.yiv2439072626photo-title a:visited {text-decoration:none;}#yiv2439072626 div#yiv2439072626ygrp-mlmsg #yiv2439072626ygrp-msg p a span.yiv2439072626yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv2439072626 .yiv2439072626green {color:#628c2a;}#yiv2439072626 .yiv2439072626MsoNormal {margin:0 0 0 0;}#yiv2439072626 o {font-size:0;}#yiv2439072626 #yiv2439072626photos div {float:left;width:72px;}#yiv2439072626 #yiv2439072626photos div div {border:1px solid #666666;height:62px;overflow:hidden;width:62px;}#yiv2439072626 #yiv2439072626photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv2439072626 #yiv2439072626reco-category {font-size:77%;}#yiv2439072626 #yiv2439072626reco-desc {font-size:77%;}#yiv2439072626 .yiv2439072626replbq {margin:4px;}#yiv2439072626 #yiv2439072626ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv2439072626 #yiv2439072626ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv2439072626 #yiv2439072626ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv2439072626 #yiv2439072626ygrp-mlmsg select, #yiv2439072626 input, #yiv2439072626 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv2439072626 #yiv2439072626ygrp-mlmsg pre, #yiv2439072626 code {font:115% monospace;}#yiv2439072626 #yiv2439072626ygrp-mlmsg * {line-height:1.22em;}#yiv2439072626 #yiv2439072626ygrp-mlmsg #yiv2439072626logo {padding-bottom:10px;}#yiv2439072626 #yiv2439072626ygrp-msg p a {font-family:Verdana;}#yiv2439072626 #yiv2439072626ygrp-msg p#yiv2439072626attach-count span {color:#1E66AE;font-weight:700;}#yiv2439072626 #yiv2439072626ygrp-reco #yiv2439072626reco-head {color:#ff7900;font-weight:700;}#yiv2439072626 #yiv2439072626ygrp-reco {margin-bottom:20px;padding:0px;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ov li a {font-size:130%;text-decoration:none;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ov ul {margin:0;padding:0 0 0 8px;}#yiv2439072626 #yiv2439072626ygrp-text {font-family:Georgia;}#yiv2439072626 #yiv2439072626ygrp-text p {margin:0 0 1em 0;}#yiv2439072626 #yiv2439072626ygrp-text tt {font-size:120%;}#yiv2439072626 #yiv2439072626ygrp-vital ul li:last-child {border-right:none !important;}#yiv2439072626


From: Egolf, Kevin (TechOps Solutions, International) (2016-03-15 23:52)

We addressed a similar issue to associate a customer with a location.

We utilized the company table and added a new company type for customer in the company type domain. We used an existing field on the location record and applied a table domain to filter for customer records. We are using locations.lo1 and workorder.wo1. I believe these are a couple of the original crossover fields from the old days since we did not have to add them to the location 2 workorder crossover domain. We modified the screens in both applications to display the appropriate fields.
This has worked for us for the past 10 years and updating the customer when they change is a simple process.

V/R
Kevin

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Tuesday, March 15, 2016 4:25 PM
To: MAXIMO@yahoogroups.com
Subject: [External] Re: [MAXIMO List] Relating SR Owner with Location



We had a similar situation - not with buildings, but with locations spread over thousands of miles and wanted each location to be associated with a specific division. (Using the location hierarchy did not entirely meet the corporate needs.)
1) A field (xxx) was created on the location table and an aln domain associated with it.2) There is a dispaly field in Assets that displays the xxx field from the location. (Just do a slight modification to the Asset app screen so it will be displayed.)3) Location is REQUIRED on all WOs for this company and field xxx crosses over to the WO once a location is selected. (Just add the new xxx field to the crossover domain and do a slight modification to the WO app screen so it will be displayed/sved with the WO.)
If and when (although I am sure that this would never happen!! :) ) one or more of the buildings maintained by contractor A changes maintenance companies, it is a simple matter to search for all locations related to the building and change the value in field xxx to Contractor N (once Contractor N had been added to the domain).
Instead of using an aln domain (but this was really easy to set up), you could add the contractor the Companies table with a specific type. Then set up a table domain from the Companies table that only shows the specific type.

Custodians and Person Groups are also valid ways to handle this. Custodians need to have the contractor set up in the Person table. Same with putting contractors into a Person group - the contractor would need to be set up in the Person table, not the Company table.
Pat Morrow
pmorrow8@yahoo.com<mailto:pmorrow8@yahoo.com>

From: "'Ian Turner' ian.turner@salisburycamra.org.uk<mailto:ian.turner@salisburycamra.org.uk> [MAXIMO]" <MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>>
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Sent: Tuesday, March 15, 2016 8:23 AM
Subject: [MAXIMO List] Relating SR Owner with Location

Hello All, my first post so I'll try not to break the rules and ask a
sensible question that hasn't been answered 200 times before. I have
searched the group as best I can.

I want to allocate work orders to a particular contractor based upon the
location. We have several buildings that are maintained by contractor A and
several by contractor B. Allocation of the SR/work order, we thought, was
best done by setting each contractor as a People Group and allocating that
People Group as the SR owner. Hopefully this is an accepted way to deal with
this but I'm more than happy to be advised on this. What we also want to do
is drive that SR Owner from the location defined in the SR. We are
considering using the primary custodian for this but I worry this may be
needed for other uses in the future and although it is the primary
custodian, so a single option, I'd prefer to use a field in the locations
table (new field?). This seems like a common condition, is there a preferred
solution?

Thanks



#yiv2439072626 #yiv2439072626 -- #yiv2439072626ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv2439072626 #yiv2439072626ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv2439072626 #yiv2439072626ygrp-mkp #yiv2439072626hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv2439072626 #yiv2439072626ygrp-mkp #yiv2439072626ads {margin-bottom:10px;}#yiv2439072626 #yiv2439072626ygrp-mkp .yiv2439072626ad {padding:0 0;}#yiv2439072626 #yiv2439072626ygrp-mkp .yiv2439072626ad p {margin:0;}#yiv2439072626 #yiv2439072626ygrp-mkp .yiv2439072626ad a {color:#0000ff;text-decoration:none;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ygrp-lc {font-family:Arial;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ygrp-lc #yiv2439072626hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ygrp-lc .yiv2439072626ad {margin-bottom:10px;padding:0 0;}#yiv2439072626 #yiv2439072626actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv2439072626 #yiv2439072626activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv2439072626 #yiv2439072626activity span {font-weight:700;}#yiv2439072626 #yiv2439072626activity span:first-child {text-transform:uppercase;}#yiv2439072626 #yiv2439072626activity span a {color:#5085b6;text-decoration:none;}#yiv2439072626 #yiv2439072626activity span span {color:#ff7900;}#yiv2439072626 #yiv2439072626activity span .yiv2439072626underline {text-decoration:underline;}#yiv2439072626 .yiv2439072626attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv2439072626 .yiv2439072626attach div a {text-decoration:none;}#yiv2439072626 .yiv2439072626attach img {border:none;padding-right:5px;}#yiv2439072626 .yiv2439072626attach label {display:block;margin-bottom:5px;}#yiv2439072626 .yiv2439072626attach label a {text-decoration:none;}#yiv2439072626 blockquote {margin:0 0 0 4px;}#yiv2439072626 .yiv2439072626bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv2439072626 .yiv2439072626bold a {text-decoration:none;}#yiv2439072626 dd.yiv2439072626last p a {font-family:Verdana;font-weight:700;}#yiv2439072626 dd.yiv2439072626last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv2439072626 dd.yiv2439072626last p span.yiv2439072626yshortcuts {margin-right:0;}#yiv2439072626 div.yiv2439072626attach-table div div a {text-decoration:none;}#yiv2439072626 div.yiv2439072626attach-table {width:400px;}#yiv2439072626 div.yiv2439072626file-title a, #yiv2439072626 div.yiv2439072626file-title a:active, #yiv2439072626 div.yiv2439072626file-title a:hover, #yiv2439072626 div.yiv2439072626file-title a:visited {text-decoration:none;}#yiv2439072626 div.yiv2439072626photo-title a, #yiv2439072626 div.yiv2439072626photo-title a:active, #yiv2439072626 div.yiv2439072626photo-title a:hover, #yiv2439072626 div.yiv2439072626photo-title a:visited {text-decoration:none;}#yiv2439072626 div#yiv2439072626ygrp-mlmsg #yiv2439072626ygrp-msg p a span.yiv2439072626yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv2439072626 .yiv2439072626green {color:#628c2a;}#yiv2439072626 .yiv2439072626MsoNormal {margin:0 0 0 0;}#yiv2439072626 o {font-size:0;}#yiv2439072626 #yiv2439072626photos div {float:left;width:72px;}#yiv2439072626 #yiv2439072626photos div div {border:1px solid #666666;height:62px;overflow:hidden;width:62px;}#yiv2439072626 #yiv2439072626photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv2439072626 #yiv2439072626reco-category {font-size:77%;}#yiv2439072626 #yiv2439072626reco-desc {font-size:77%;}#yiv2439072626 .yiv2439072626replbq {margin:4px;}#yiv2439072626 #yiv2439072626ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv2439072626 #yiv2439072626ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv2439072626 #yiv2439072626ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv2439072626 #yiv2439072626ygrp-mlmsg select, #yiv2439072626 input, #yiv2439072626 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv2439072626 #yiv2439072626ygrp-mlmsg pre, #yiv2439072626 code {font:115% monospace;}#yiv2439072626 #yiv2439072626ygrp-mlmsg * {line-height:1.22em;}#yiv2439072626 #yiv2439072626ygrp-mlmsg #yiv2439072626logo {padding-bottom:10px;}#yiv2439072626 #yiv2439072626ygrp-msg p a {font-family:Verdana;}#yiv2439072626 #yiv2439072626ygrp-msg p#yiv2439072626attach-count span {color:#1E66AE;font-weight:700;}#yiv2439072626 #yiv2439072626ygrp-reco #yiv2439072626reco-head {color:#ff7900;font-weight:700;}#yiv2439072626 #yiv2439072626ygrp-reco {margin-bottom:20px;padding:0px;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ov li a {font-size:130%;text-decoration:none;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv2439072626 #yiv2439072626ygrp-sponsor #yiv2439072626ov ul {margin:0;padding:0 0 0 8px;}#yiv2439072626 #yiv2439072626ygrp-text {font-family:Georgia;}#yiv2439072626 #yiv2439072626ygrp-text p {margin:0 0 1em 0;}#yiv2439072626 #yiv2439072626ygrp-text tt {font-size:120%;}#yiv2439072626 #yiv2439072626ygrp-vital ul li:last-child {border-right:none !important;}#yiv2439072626




From: maximal (2016-03-18 07:10)



---In MAXIMO@yahoogroups.com, <egolf_kevin@ne.bah.com> wrote :

We utilized the company table and added a new company type for customer in the company type domain. We used an existing field on the location record and applied a table domain to filter for customer records. We are using locations.lo1 and workorder.wo1. I believe these are a couple of the original crossover fields from the old days since we did not have to add them to the location 2 workorder crossover domain. We modified the screens in both applications to display the appropriate fields.
This has worked for us for the past 10 years and updating the customer when they change is a simple process.

---------------------------------------

This is how I would solve it as well. Let external vendors stay as entities and avoid personhood!

-C



From: Ian Turner (2016-03-21 12:45)

Thanks for the advice. The contractor will need to use Maximo to manage the
work orders they are allocated so I think the Person group would need to be
used in any case. We have now applied this and it is working.

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: 18 March 2016 17:11
To: MAXIMO@yahoogroups.com
Subject: RE: [External] Re: [MAXIMO List] Relating SR Owner with Location


---In MAXIMO@yahoogroups.com <mailto:MAXIMO@yahoogroups.com> ,
<egolf_kevin@ne.bah.com <mailto:egolf_kevin@ne.bah.com> > wrote :
We utilized the company table and added a new company type for customer in
the company type domain. We used an existing field on the location record
and applied a table domain to filter for customer records. We are using
locations.lo1 and workorder.wo1. I believe these are a couple of the
original crossover fields from the old days since we did not have to add
them to the location 2 workorder crossover domain. We modified the screens
in both applications to display the appropriate fields.
This has worked for us for the past 10 years and updating the customer when
they change is a simple process.
---------------------------------------
This is how I would solve it as well. Let external vendors stay as entities
and avoid personhood!
-C