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
------------------------------



#MaximoEAM
#AssetandFacilitiesManagement
#Maximo

DISA STIGs would be a good place to start. The requirements are pretty hefty though. There are STIGs for the OS, Database, and for WebSphere.

https://public.cyber.mil/stigs/downloads/

------------------------------
Tim Ferrill
Solutions Consultant
Intelligent Technology Solutions
tferrill@webuildits.com
www.webuildits.com
@tferrill/@webuildits
------------------------------

As Tim said, the DISA STIGS are going to give IT a great baseline of security configurations that can be implemented.

However, guidelines that cover Maximo Data Changes, Screen Changes, and Integrations that cover "all aspects of implementation" are going to be difficult to impossible to find.  IBM uses a partner network of authorized implementers and each has its own methodologies for making changes and how they implement/configure Maximo.  If they have documents, these are not items that partners share.

In general, you should be using a standard configuration and change management philosophy/procedures to implement change.  There are many out there and you would need to choose one that applies best to your organization.  For EAM 360, their support team should be able to provide you guidance that is specific to their product.




------------------------------
Richard Minnigh
Vice President
Intelligent Technology Solutions
RMinnigh@WeBuildITS.com
www.WeBuildITS.com
@webuildits
------------------------------

Hi mx pro,

I do not have any of these documents. It is mostly owned by customer and IBM Business partners.

Just on this related topic, I would like to hear from our Maximo community experts if these documents can be shared over IBM digital Twin.
I have little knowledge about digital twin but with that little knowledge, I wonder if companies would be ready to share these kind of document on IBM digital Twin accessible to other customers.
I think it will help companies use these documents as reference points for their implementation.
The best of the implementation do not get exposed or valued. May be this will be a way for customers/business partner to give the great work done by IBM Maximo implementers a place to show case. I believe these documents would definitely be bought by a number of customer which will give Maximo implementation some standards and principle.

It would be great to hear some thoughts about this from the Maximo Community experts.

------------------------------
Biplab Choudhury
Maximo Consultant
Tata Consultancy Services
Melbourne
------------------------------

Hi mx pro

As others have said these are not documents that Business Partners are likely to freely/publicly share.

There are several reasons for that:

• Some of the settings / choices will be commercially sensitive e.g. custom changes can deliver a lot of value and give competitors ideas of features they could be missing out on
• Sharing the documents means that the customers don't buy consultancy from a BP
• A BP document a setting to close a security hole but publicising that setting could give a hacker information about a weakness they could exploit in a different system

------------------------------
Mark Robbins
Support Lead/Technical Design Authority / IBM Champion 2017 & 2018 & 2019 & 2020 & 2021
Vetasi Limited
https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/
------------------------------

The Maximo Business Object Development guideline document was moved from the old wiki and is provided by IBM. This should help as well.

------------------------------
Thanks,
christopher winston
------------------------------

thanks chris

------------------------------
mx pro
ON
------------------------------

Original Message:
Sent: Wed October 20, 2021 08:39 PM
From: christopher winston
Subject: Document for IT guidelines and standards on Maximo Maximo System Design and Implementation

The Maximo Business Object Development guideline document was moved from the old wiki and is provided by IBM. This should help as well.

------------------------------
Thanks,
christopher winston
------------------------------