Improve IBM (Technical Support) Documentation

IBM Documentation including Technotes and Readme files are not only used to install and configure Maximo Application Suite, but also to troubleshoot any issues that arise.

Multiple Business Partners request improvements to the overall documentation especially since the environments and integrations become more complex with many types of variations due to differences in the deployment models.

Validity of Maximo documentation for MAS:

When searching for e.g. Technotes it is hard for clients to determine whether they are still valid for MAS: Idea would be to validate/add/refresh meta data like for which versions the documentation is valid, each time IBM Support shares such a Technote. By showing e.g. a "last validated date" and "valid for versions x.x to y.y", the confidence for using the documentation increases and troubleshooting can be more effective and faster.

Best Practice documents:

Best Practice documents for e.g. firewall/network/storage/mobile settings in combination with Maximo Application Suite: common issues, remedies, troubleshooting tips (step by step). While each client may be unique it would help to exclude the majority of pitfalls before IBM Support needs to be engaged. While we have lot's of Technotes and combined with the IBM Documentation, they are some times hard to read for a certain context. Maybe by combining several technotes with some troubleshooting tips and a checklist (derived out of actual Support Cases) into a Best Practice document, it could help to resolve the overarching problem quicker. 

Detailed Readme / Release Notes:

Readme files often lack accurate/sufficient details on what fixes are included, especially internal issues that may not have made it yet to a public Known Issue, but still an issue that could be encountered in the field. Sometimes just Security Fixes are being mentioned or just very high level descriptions. As not documented, it will also not appear in a search, hence clients may troubleshoot known issues and loose valuable time. It would help to reference to a list of all open Known Issues in the Readme file.

Simplify Document Enhancement Request process:

Technotes need to get out quickly, but also may therefore sometimes lack details that become available when being actually used in different scenario's. IBM Documentation is huge, but sometimes clients, business partners or IBMers have recommendations for improvements. It would be good to have a uniform way to request documentation/technote updates, maybe even similar to the Ideas portal, so it can be tracked.

Recent examples/requests:

• Maximo_NextGen_REST_API_-_nextgen.pdf without proper context for which versions valid.
• New REST APIs overview - IBM Documentation shared for a MAS Support Case , but 7.6 is referenced
• Using REST API Details referring to url's that are no longer valid and unclear whether still valid
• Best Practice for Azure WAF
• Best Practice for DOClinks/attachments
• Best Practice for Mobile deployment