thanks steve for the reply and sorry i am replying late...
the need is...
As i wrote in my original messages, that since our departments will be implemented simultaneously, the IT Solution Architect cannot be at multiple places at same time
so what we are thinking to give guiltiness to the designers, when they design solutions based on user requirements.
These guidelines will cover screen changes and other aspects... for example, while designing screen... a guideline can be... try using out of the box as much as possible and do not move table windows from one screen to another... like do not move work logs screen on main Work order tab... sort of these guiltiness as general.. so that we know that when design is adhered to these guidelines... some sort of standardization is incorporated in system design...
hope i was able to make myself clear
another thing which i want to discuss with u.. as an implementation expert... a Solution Architect.. basically he should be validating and approving the design and build .. which is proposed and done by vendor... are we going in right direction... ?? what are ur thoughts on this
issue we see here is with multiple implementations happening... including integration as well.. will this create bottle neck... and what are ur recommendations in this aspect??
------------------------------
mx pro
ON
------------------------------
Original Message:
Sent: Thu September 16, 2021 08:45 AM
From: Steven Shull
Subject: Document for IT guidelines on Maximo Maximo System Design and Implementation
I'm not sure if you're looking for approaches (IE how to support multiple business units configuring the system at once) or general guidelines for configuring Maximo (IE use a prefix when defining custom objects/attributes to avoid potential future conflicts with Maximo).
No matter what you're looking for, I would suggest that you setup e-audit on some system tables. If you have multiple departments configuring the system, it's very easy for mistakes to happen without any sort of tracking as to who made the change and when. I'd only suggest e-audit on some of the columns in these objects, but some example objects where I've found it useful for e-audit:
1) MAXPRESENTATION
2) REPORTDESIGN
3) AUTOSCRIPT
4) SCRIPTLAUNCHPOINT
5) MAXVARS
6) MAXPROPVALUE
7) MAXOBJECTCFG
8) MAXATTRIBUTECFG
This covers a large portion of the configuration with a way to easily revert. For example MAXVARS stores most of the options displayed in the Organization application. A change to these could drastically impact how the system functions.
------------------------------
Steven Shull
Original Message:
Sent: Wed September 15, 2021 03:32 PM
From: mx pro
Subject: Document for IT guidelines on Maximo Maximo System Design and Implementation
Hello Guys,
we are implementing Maximo at enterprise-level, which involves multiple departments and hence there will be simultaneous implementations going on for our departments.
What we are looking for is a document by IT, which can be the enterprise level guidelines and standards which should be followed at enterprise level. Essentially that will be our EAM system design and implementation guidelines and standards, which IT can implement on our Maximo system. Also these should guide on minimum or company level configs based on general market standards.
We will impose that these cofigs to be applied at company level while any department specific config will be on top of these guide lines, but still should follow the standards. These guidelines should cover, for DB changes, screens, integrations, mobility (we are using EAM360 mobile solution) etc... covering all aspects of implementation.. We are in municipal sector. Any this sort of sharing will help a lot and will be appreciated.
We r pretty much hopeful that these kind of docs do exist in companies... that's why we are requesting the sharing...
Regards
------------------------------
mx pro
ON
------------------------------
#Maximo
#AssetandFacilitiesManagement