
with Tags:
specification
X

BiLog: Detail Requirements....Report Specification Best Practice
You’ve read my mind, heard my frustrations with folding maps and seen the aftermath of the attack , as we’ve reviewed the components of report specifications over the last few weeks. Today, we’ll conclude this series on the importance and components of creating report specifications. Our series started a few weeks back when we highlighted the three major components of creating report specifications which were 1. Understand report capabilities 2. Understand user requirements 3. Detail the user requirements on the report... [More]
Tags:  report ibmeam bilog maximo data best_practice specification user |
BiLog: Maps and Best Practices....Report Specifications!
Do you know how to fold one of these…..while cramped in car traveling 72 miles per hour…with a husband exasperated that you also don’t know how to read one…along with a dog panting in your ear and your child questioning ‘ Are we there yet ?’ We’ve since graduated to the amazing electronic GPS technology where a woman in a lovely voice calmly directs us to where we need to go. Truly loving this technology where no folding is required! As maps define how we get from here to there, report specifications do the same. Report specifications... [More]
Tags:  spec v7 best_practice data bilog report ibmeam specification maximo analysis |
BiLog: Understand User Requirements...Report Specifications Best Practice.
Read my mind. Have you ever muttered those words when someone asks you where the milk is ? or if there any cookies to go with that milk? Don’t try to read your user’s mind when detailing a report specification. Instead, work with your user to fully understand his report requirements, which you can then translate into a deliverable report specification. As noted in the last BiLog entries, we have been reviewing the best practices Of report specification development which include (1) Understand report capabilities (2) Understand user... [More]
Tags:  bilog analysis maximo best_practice report ibmeam specification data |
Conditional Restrictions for Classification Specifications (Attributes)
IBM Maximo and Control Desk products have classifications in order to categorize records such as items, assets, locations, work orders, tickets etc. Classifications are not only useful for easily identifying, restricting or filtering records, they also bring in specifications functionality. Specification attributes are extra fields defined for a classification used with one or more Maximo objects. In spite of adding new fields to main database tables, related specification records are added to the specification tables only for the classified... [More]
Tags:  maximo jython mandatory validation maximo+7.5 script attribute python restriction required classification condition specification automation controldesk maximo+7.6 |