Skip to main content

Test 000-005: IBM Maximo Asset Management V7.1 Solution Design

Tab navigation

Section 1 - Requirements Gathering and Validation

  1. Given the customer has developed a requirement matrix and has a good understanding of how IBM Maximo Asset Management V7.1 (MAM) works out-of-the-box, determine the modules, features, and functions in MAM which satisfy each requirement and which requirements are not satisfied by out-of-the-box functionality so that a requirements matrix can be developed indicating MAM fit and gaps.
    With emphasis on performing the following tasks:
    1. Determine the modules to be used by the customer.
    2. Determine external systems which might have to be interfaced to MAM.
    3. Review customer-developed requirement matrices to understand the meaning and the impact of the requirement.
    4. Review reports and sample forms.
    5. If no requirement matrices are available or if the customer Subject Matter Experts are unfamiliar with MAM functionality details, schedule, and deliver workshops to cover the functional areas of MAM and how functions work out-of-the-box.
    6. Validate that the requirement is provided by base MAM by demoing the standard MAM functionality by using their data.
    7. Develop the requirements matrix and note out-of-the-box requirements and those that require configuration, and so on. (gaps). No solution has to be recommended at this time.
    8. Obtain customer approval of requirement matrix.
  2. Given participation from customer Subject Matter Experts from each process area are available, schedule and conduct MAM module-oriented workshops so that the requirements have been gathered and approved which states which features in MAM will be used and how.
    With emphasis on performing the following tasks:
    1. Schedule and deliver workshops to cover the functional areas of MAM and how functions work out-of-the-box.
      1. Organizations and Sites
      2. Assets and Locations
      3. Work Management
      4. Preventive Maintenance
      5. Inventory
      6. Requisitions/Request for Quotation/Purchasing
      7. Contracts
      8. Accounting/Financial Setup
      9. Data Gathering/Mapping
      10. Interfaces
      11. Reports
      12. Role based security and people
    2. Facilitate discussions about how each function will be used by the customer and if there are differences in their processes needed by the customer.
    3. Develop workshop findings documents as necessary (narrative of the workshop findings).
    4. Obtain customer approval of Workshop Findings.
  3. Given familiarity with Maximo Industry Solutions and add-ons, identify industry specific requirements during requirement gathering workshop, and demonstrate how these can be fulfilled by using an industry solution or add-on so that recommendations can be made to fulfill requirements which are industry specific.
    With emphasis on performing the following tasks:
    1. During Requirement Gathering Workshops, identify industry specific requirements.
    2. Suggest and demonstrate industry solutions which can fulfill the requirements. These might include:
      1. MAM for Government
      2. MAM for Life Sciences
      3. MAM for Nuclear Power
      4. MAM for Oil and Gas
      5. MAM for Service Providers
      6. MAM for Transportation
      7. MAM for Utilities
    3. Suggest MAM add-ons that might fulfill requirements. These might include:
      1. Linear Assets
      2. Change and Corrective Action Manager
      3. Asset Configuration Manager
      4. Spatial Asset Management
      5. SLA Manager
      6. Service Provider
      7. Asset Navigator
    4. Contact the software sales representative to get them involved.
  4. Given the customer's requirements, specifications of baseline, and historical data to be migrated, identify data requirements, sources, and tools to meet data migration requirements so that data migration requirements have been identified.
    With emphasis on performing the following tasks:
    1. Define MAM solution data requirements (Baseline and Transactional History).
      1. Supporting Data such as lists for select lists and field validations
      2. Base Data including such data as GL Accounts, Assets, Locations, Item Master, Inventory, Resources, Plans, and Schedules
      3. Transactional Data of a historical nature required by the customer to support their business processes at go-live
    2. Define sources for Base and Transactional data.
      1. Databases
      2. Electronic Documents
      3. Hard Copy Documents
      4. Workforce Knowledgebase
    3. Determine high level data conversion requirements.
      1. Matching data types
      2. Concatenations or Parsing
      3. Unit Conversions
      4. Structure Conversions
      5. Language Conversions
    4. Describe MAM Integration Framework data migration capabilities.
      1. Enforcement of core Maximo Business Objects
      2. File Import Functionality
  5. Given the customer's requirements and specifications of legacy systems to be interfaced, define data and interface requirements so that data interface requirements are identified.
    With emphasis on performing the following tasks:
    1. Define MAM solution data requirements.
      1. Addition/Deletion/Modification of Base Data
      2. Addition/Deletion/Modification of Transactional Data
    2. Define legacy systems data structure to be integrated.
    3. Map high level integration points and flows.
    4. Determine high level data conversion requirements.
    5. Determine frequency and process for executing each integration point (real-time, batch).
    6. Describe MAM Integration Framework functionality and requirements for developing interfaces.
  6. Given the customer's requirements and their organizational and GL structures, evaluate customer information so that Organization/Site setup requirements are identified.
    With emphasis on performing the following tasks:
    1. Determine whether multiple organizations or MAM instances are required.
      1. Multiple organizations are required if the company's business units have different charts of account or base currencies.
      2. Multiple MAM databases are required if the company's business units have different GL Component Structures.
    2. Determine whether multiple sites are appropriate.
      1. Sites share common business processes, assets, and locations.
      2. Multiple sites might be appropriate if the business units have distinct geographies, process workflows, data access control, or functional requirements.
      3. Multiple sites are optional in all cases.
    3. Describe an Organization/Site model structure.
      1. Describe System level features and functionality.
      2. Describe Organizational level features and functionality.
      3. Describe Site level features and functionality.
    4. Describe settings for System/Organization/Site configuration options.
  7. Given a familiarization with MAM, define and describe the usages of Maximo Assets and Locations so that differences between Maximo Assets and Locations are understood.
    With emphasis on performing the following tasks:
    1. Define a Maximo Asset.
      1. A Maximo Asset is a fixed, physical, or capital asset used to conduct the client's business. They generally fall into one of four categories: Production, Facilities, Fleet, and IT.
      2. A Maximo Asset is any equipment, machinery, or technology that the company owns, operates, leases, or manages and is maintained by the company.
    2. Define a Maximo Location.
      1. Locations are places where a Maximo Asset is stored or used and allows the tracking of asset movements and the tracking of financial costs.
      2. Locations are typically the places where assets operate, but include any building, place, or other areas that contain assets, where maintenance work might be performed.
    3. Describe the usage of a Maximo Asset.
      1. A Maximo Asset is used when the client wants to track the lifecycle of a particular piece of equipment or physical plant. The asset lifecycle includes planning, acquiring, installing, maintaining, and retiring. MAM also records the current status which can be aligned to the lifecycle, these are: not ready, operating, and decommissioned.
      2. Maximo Asset records can be used to trace historical events and costs related to that particular piece of equipment or physical plant.
    4. Describe the usage of Maximo Locations.
      1. A Maximo Location stores aggregated data of all events and costs performed within that Location. This includes the movement of assets into and out of the location, as well as the use of labor and materials charged to that location.
      2. There are six types of location:-Operating - Locations where assets operate. Assets are moved between Operating Locations. Assets are issued or returned between Storerooms and Operating Locations.-Storeroom - Locations where inventory is maintained. Items are issued or returned to and from a Storeroom Location. Items are transferred between Storerooms.-Vendor - Used to record that an asset is off-site with external vendor usually for repairing. -Salvage - Used to record the end-of-life for an asset. They are usually created with the labels like "Scrapped", "Sold", "Destroyed", and "End-of-lease"-Repair - Used to record that an asset is being repaired internally or at an on-site workshop by trade staff.-Courier - Used to record that the asset is in transit to another location by using a courier company, where it will be received at its destination. The destination might be another storeroom or another vendor.-Labor - Used to record that the asset is in transit to another location by using a labor (normally a staff member), where it will be received at its destination. The destination might be another storeroom or another vendor. Alternatively it might a location used to record all company issued items or tools under the care of that labor, and when the labor has finished with the asset, it can then be returned to the storeroom.-Holding - Used as part of the rotating item receiving process as a temporary storeroom while the item gets either inspected and/or turned in an asset by using serialization. There can only be one per Maximo site, and while in this location it does not count towards a storeroom's balance nor does it incur any cost until the inspection/serialization process is complete.
  8. Given a familiarization with MAM, define and describe rotating assets and non-rotating assets so that the differences between rotating assets and non-rotating assets are understood.
    With emphasis on performing the following tasks:
    1. Describe a rotating asset.
      1. Rotating assets are assets that are interchangeable.
      2. Rotating assets have a unique asset number and an inventory item number; the item must be marked as rotating. Service Items cannot be marked as rotating; the items found in the Item Master or Tools application can be marked as rotating. Non-rotating assets do not reference an item number.
      3. Rotating assets can be located in a storeroom, either an item storeroom or a tool storeroom.
      4. Rotating assets can also exist in labor and courier locations where these have been set up to maintain a balance of an item. Non-rotating and rotating assets can exist in Operating Locations, Vendor, Salvage, and Repair Locations.
      5. Rotating assets can have an Item Assembly Structure (IAS) applied. The IAS can be considered as a template for a hierarchy of assets, saving time when creating many similar asset hierarchies.
      6. The classification of a rotating asset is determined from its rotating item. If the attribute values are updated on the rotating item, they are also changed on all rotating assets that belong to this rotating item.
      7. During the receiving process rotating assets have to be given an asset number.
    2. Describe a non-rotating asset.
      1. Non-rotating assets can be purchased, received, and issued directly to the person who requisitioned the item.
      2. Non-rotating assets are not associated to an Item.
      3. Non-rotating assets do not have to share a common classification.
  9. Given a familiarization with MAM, define and describe Linear Assets so that Linear Assets are understood.
    With emphasis on performing the following tasks:
    1. Describe a Linear Asset.
      1. Linear Assets have linear properties not bound by a single location or bound space and often connect with each other by their relationship within the linear infrastructure itself.
      2. Non-Linear Assets occupy finite and bound spaces and can be tracked by their location or modelled as part of a parent child hierarchy.
      3. Linear Assets are preserved and restored in place and in segments.
      4. Non-Linear Assets are installed, maintained, and replaced as a whole.
    2. Describe common usages for Linear Assets.
      1. Roads
      2. Railroad tracks
      3. Pipelines
      4. Electrical or Telecommunication transmission lines

Section 2 - Gap Analysis

  1. Given customer required functionality has been discussed, documented, and validated, perform a GAP analysis so that functional gaps between customer requirements and standard IBM Maximo Asset Management V7.1 (MAM) functionality have been identified, defined, and documented.
    With emphasis on performing the following tasks:
    1. Determine functional areas for gap documentation.
    2. Create a gap list.
    3. Identify if customer requirements can be fulfilled with standard MAM functionality.
    4. Document the differences between standard MAM functionality and required functionality based on customer requirements.
    5. Perform impact assessment for each gap identified.
    6. Document possible solutions and required design modifications for each gap.
  2. Given that MAM has been installed and the basic system data has been set up, define the key difference between configuration and customization of the system so that the differences are understood.
    With emphasis on performing the following tasks:
    1. A configuration is a change made to the system by using the administrative tools such as application designer and database configuration included with the application.
    2. A customization is a change made to the system by using any external tool to add custom code.
    3. Configuration of the system is considered to be supported.
    4. Customization of the system is considered to be unsupported by a standard IBM support contract.
  3. Given that functional gaps have been defined and documented, determine time required and level of difficulty for each functional gap so that the level of effort to solve functional gaps between standard MAM functionality and customer requirements has been identified, categorized, and documented.
    With emphasis on performing the following tasks:
    1. Determine levels and categories for time and difficulty to design, implement, and close a functional gap.
    2. Calculate time needed/required to design, implement, and close each functional gap.
    3. Determine level of difficulty to design, implement, and close each functional gap.
    4. Categorize the functional gaps, based on level of effort. (time & difficulty)
    5. Document levels of effort in the gap list.

Section 3 - Identifying Features and Functions

  1. Given an understanding of IBM Maximo Asset Management V7.1 (MAM) and EAM processes, describe the various features and components or MAM so that the EAM components features of MAM are understood.
    With emphasis on performing the following tasks:
    1. Have an understanding of the EAM features of MAM. MAM unifies comprehensive asset lifecycle and maintenance management on a single platform. This asset management software provides insight for all enterprise assets, their conditions, and work processes, for better planning and control.
      1. Manage asset lifecycle, specifications, monitoring, calibration, costing, and tracking from a single system.
      2. Provide enterprise asset management software for long and short-term planning, preventive, reactive, condition-based maintenance, maintenance schedule management, resource optimization, and key performance indicators (KPIs).
      3. Plan inventory to meet maintenance demand and make the right parts available at the right location when needed.
      4. Manage vendor contracts with comprehensive support for purchase, lease, rental, warranty, labor rate, master, blanket, and user-defined contracts.
      5. Manage the procurement lifecycle from requisition, request for quotation, Purchase Order placement, receiving, and invoice matching.
      6. Adapt to changing business requirements and connects with other enterprise systems through a flexible business process configuration platform and scalable service oriented architecture.
  2. Given a list of users, security groups, and functional requirement describe what security consideration have to be taken into account when securing MAM and that they users have the appropriate authorizations so that the customer is aware of all security considerations.
    With emphasis on performing the following tasks:
    1. Describe the difference between by using application server authentication versus native authentication.Application server authentication uses a Lightweight Directory Access Protocol (LDAP) solution such as Microsoft's Active Directory or Tivoli Directory Server through IBM WebSphere's Virtual Member Manager. This allows for user creation and password control to be done from a centralized location where the user might be granted access to more than one business application. It also allows for the business to then implement a single sign-on solution. The user is authenticated through the LDAP tool before being granted authorization to MAM based on their security group privileges. Native authentication is when the user logs in to MAM they are authenticate solely from MAM. Once authenticated they are then authorization to MAM based on their security group privileges. Authentication is the process of validating the identity of a user by providing proof that the user is the one that person claims to be.Authorization is concerned with granting or denying access to system resources that is, applications or data.
    2. Describe how the properties in the maximo.properties file can be encrypted.In the maximo.properties files, mxe.db.password and mxe.system.regpassword can be encrypted by using encryptproperties.bat file in ..maximo\tools\maximo directory. The passwords can become encrypted.
    3. Describe the difference between independent and non-independent security groups.A user can belong to one or more security groups, because of this, MAM creates a specific profile of what they can/cannot do and if this is not understood properly, uses might not have access to the data they want, or they might have too much access.Independent security groups are used where the rights have to be preserved that is, on site A they can approve Purchase Order to $1000, but on site B they have no Purchase Order approval.Dependant security groups are used where the rights can be combined to form a profile where the highest right is granted that is, group A read-write to asset, but for group B they have read-only access to assets, thus when combined the user with read-write access as this is higher than just read-only.A user can belong to both independent and non-independent groups.
    4. Describe the use of the conditional UI, conditional option access and data restrictions.Conditional UI: Dynamically changes presentation elements for an application based on the profile configured in the application designed. This allows for tabs and fields to become hidden or display based on a combination of the security groups the user belongs to, and the conditional expression being used. The conditional expression is either a SQL statement that if true will do one, and do another if false. For example, if the asset is a type=IT, then the labels will change to "IT Asset", and if it was another type of asset, the original label will be used instead.Conditional option access: This will dynamically grant or revoke the user's privilege to use a security option base on a conditional expression. The conditional expression is either a SQL statement that if true will do one, and do another if false. For example, if the asset is a type=IT, then the user cannot delete, and if it was another type of asset they can delete the asset.Data restrictions: This is where the data when access from any application or from a specific application will be filtered to meet the needs of the role. For example, all contractors can only see Work Order for a nominated contract and staff can see all Work Orders. Alternatively, it can make the field hidden or read-only.
  3. Given that MAM has been installed describe the uses of workflow so that users can move records to individuals according to their business processes and so the users can view these records on their Start Center Inbox.
    With emphasis on performing the following tasks:
    1. Create a simple business process flow diagram that describes Work Order approvals through various levels within an organization.
    2. Describe the use of roles in MAM and how they relate to workflow.
    3. Define Maximo Actions and explain their use in the workflow process.
    4. Describe how a person will receive the task on their Start Center.
    5. Identify the various workflow nodes and explain how they are used in the process.
    6. Map the business process on a canvas in Workflow Designer by adding the appropriate nodes with positive and negative connecting lines.
    7. Configure Task and Condition Nodes to meet the needs of the process.
    8. Enable and Activate the Workflow.
  4. Given that MAM has been installed, describe the use of the Start Canter as a configurable screen to give an individual quick access to tools, information, assignments, and KPIs, so that users are enabled to navigate to applications and information within MAM according to his or her needs.
    With emphasis on performing the following tasks:
    1. Describe the configurability of the Start Center.
    2. Define the term; Portlet.
    3. List the 7 Portlets available to be placed on the Start Center. Result set, KPI Graph, KPI List, Bulletin Board, Favorites, Quick Insert, Workflow inbox.
    4. Change content of the Start Center by configuring the Left/Right Columns.
    5. Configure individual Portlets to meet the user's needs.
    6. Set up a result set that uses Chart options for a graphical view.
    7. In the Work Order Application define a simple query for all WO's that are Waiting for Approval (WAPPR).
    8. Define a result set that uses saved queries.
  5. Given that MAM has been installed and the module's applications are available. Demonstrate the use of the applications so a client can gain an understanding of how he can use the Inventory Module in his business processes.
    With emphasis on performing the following tasks:
    1. Describe the overall purpose of the Item Master Application.
    2. Define the critical elements in setting up an Item in Item Master; Commodity Codes, Order/Issue units, Lotted, Rotating, and Condition Enabled.
    3. Describe the use of an Item Assembly Structure in Item Master.
    4. Describe how to add/modify Units of Measure and Conversion factors within Item Master.
    5. Define the use of the Service Items Application for a client.
    6. Describe how to avoid increasing the average cost of an Item when adding Service Items.
    7. Explain the use of the Tools/Stocked Tools Applications and how these are used on Work Orders and Job Plans.
    8. Describe the Inventory Application and how it is related to the Item Master.
    9. Define how to set the Inventory default settings by organization and site, including the reorder configurations, item issue cost, and non-capitalized rotating item issue cost.
    10. Describe the use of the required fields in the Inventory Application, Stock Category, Count Frequency, Reorder Points, Lead Time, and Economic Order Quantity.
    11. Compare the different methods to Issue and Return items to a storeroom.
    12. Describe how Items are moved from one storeroom to another.
    13. Identify how Condition Codes are set up in Item Master and can be applied in the Inventory Application.
    14. Describe the use of Storerooms in a multi-Site, multi-Org situation.
  6. Given that MAM has been installed, describe the uses of the Preventive Maintenance application in defining time based and meter based frequencies to generate scheduled Work Orders with specific tasks from the Job Plans Application so that Preventive Maintenance record is now ready to be demonstrated to a client.
    With emphasis on performing the following tasks:
    1. Describe the relationship between Master PM and the Preventive Maintenance Application including assigning associated PM's across Sites and Organizations.
    2. Describe how a Master PM updates can be overridden on associated PM's.
    3. Define a PM Alert and how this can be used to reduce asset/location downtime.
    4. Define the relationship between Extended Date and the Estimated Next Due Date.
    5. Describe PM Work Order Generation including; Use Last WO's Start Information to Calculate Next Due Frequency, Generate WO Based on Meter Reading (Do Not Estimate), Generate WO When Meter Frequency is Reached.
    6. Describe how Job Plans can be ordered/sequenced.
    7. Demonstrate how PM Hierarchies are setup.
  7. Given that MAM has been installed, describe the use of the Planning module application in preparing work plans so that an effective PM program can be established to improve asset/location uptime.
    With emphasis on performing the following tasks:
    1. Describe the Job Plan Statuses.
    2. Describe the use of Job Plan templates.
    3. Explain the use of Flow Control and Flow Actions for Job Plans.
    4. Use Labor/Crafts, Materials, Services and Tools setup to build Work Plans.
    5. Describe how work assets are used to build safety plans to the work plan.
    6. Describe how Classifications can be used on Job Plans and down to the Task level.
    7. Describe how the Routes Application can be used so that Route Stops can be turned into Child Work Orders, Work Order Tasks or entries in the Work Order's Multi-asset and Location.
    8. Demonstrate how Safety Plans, Hazards and Precautions, Hazard Materials, and Tag-outs can be used on Work Orders to protect others and safely accomplish the job.
  8. Given the applications; Work Order tracking, quick reporting, labor reporting, activities and tasks, and service request, describe the function of the Work Order module.
    With emphasis on performing the following tasks:
    1. Describe the function of the Work Order tracking application.Used to plan, review, and approve Work Orders for assets and locations. Manage both planned and unplanned maintenance activities, from initial work request and Work Order generation through completion and recording of actuals. Work planners can match job tasks to available resources, estimate and obtain approval of costs, establish priorities, and initiate maintenance activities across the enterprise. Work management supports the business goals by providing the following benefits. This also supports task sequencing, attaching documents at the task level, and generating Work Orders from asset information.
    2. Describe the function of the quick reporting application.Used to complete emergency work where the physical work has already been complete and thus does not require any planning or authorization to perform the works. Any emergency job raised will start its Work Order lifecycle at the INRPG status. It can also be used to manage to completion any existing Work Orders from a single screen, including completing failure reporting.
    3. Describe the function of the labor reporting application.Used to report the type and total number of hours of work that was performed by external contractors or internal employees and the specific craft used to accumulated against a Work Order that is approved or greater and not yet closed or cancelled. The application is designed so that the time can be reported for an individual labor against a Work Order, ticket, craft, or any labor, including themselves - security dependant.
    4. Describe the function of the assignment manager application.Used to dispatch or assign labor to urgent work and to schedule labor to planned work requirements with a view to increasing the labor's utilization for any given 7-day period.
    5. Describe the function or the activities and tasks application.Used to plan, review, and manage activities that can initiate the maintenance process and create a historical record of work being performed. Activities can be raised from services requests, incidents, or problem tickets, whereas, tasks can be raised from activities, Work Orders. Work planners can match job tasks to available resources, estimate and obtain approval of costs, establish priorities, and initiate maintenance activities across the enterprise. This also supports the business goals by providing the following benefits. Work management also supports Work Order tracking, task sequencing, attaching documents at the task level and generating Work Orders from asset information.
    6. Describe the function of the service request manager application.Used to create, view, and resolve service requests from customers.
  9. Given the Knowledge of the Resources module in MAM, provide a brief explanation of the module so that the Resource module has been defined.
    With emphasis on performing the following tasks:
    1. The Resources module organizes the options related to people, person groups, crafts, labor records associated to them, and skills that they have related to asset/inventory management.
    2. The Labor application is used to create and manage labor records for employees and contractors who perform work on tickets and Work Orders. Labor records contain information about an individual's skills and qualifications. These records are used to plan and schedule work, and to track labor costs for tickets and Work Orders.
    3. The People application is used to create and manage records for individuals. A person record contains basic information about an individual's name, address, contact information, and other generic information.
    4. The Crafts application is used to create and work with craft records. The craft code typically reflects the type of work done by employees and contractors.
    5. The Crafts application is also used to define skill levels, standard rates, and premium pay codes for crafts.
    6. The Qualifications application is used to create qualifications and certification requirements for qualifications. By using their labor records, one can associate individuals with a qualification. One can also view qualifications associated with a particular labor record and can renew and change the status of their qualifications.
    7. The Person Groups application is used to create, view, and modify person groups. A person group consists of people, who might or might not be workers. Once these groups have been created, a person group for any of the following examples can be used:
      1. a work group
      2. an owner group on a Work Order
      3. an owner group on a ticket
  10. Given that MAM has been installed and the basic system data or demo data has been setup, demonstrate the features and functions for queries, reports, and KPIs so that the customer understands their use and flexibility.
    With emphasis on performing the following tasks:
    1. Describe the use of List Page.
    2. Describe Advanced Search.
    3. Explain wildcard searches.
    4. Describe Saved Queries.
    5. Describe Quick Search Key.
    6. Describe Filter capabilities.
    7. Describe downloading a query to an external application such as Excel.
    8. Describe out of the box reports from an application.
    9. Describe report administration.
    10. Describe KPI Manager.
    11. Describe KPIs on the Start Center.
    12. Explain the types of KPIs which are available.
  11. Given the need to move data or a configuration from a development environment through to a production environment, define package, create and distribute to a migration package, and successfully import and deploy it into another environment so that a package is created and required data and any compiled sources are able to be moved to another database.
    With emphasis on performing the following tasks:
    1. The goal of Migration Manager is to provide the tools that enable one to take configuration content into production in a safe, efficient, and repeatable manner. All of this is configuration content usually created in a development environment; tested and certified in a user-acceptance environment and promoted to production environment. For example, the customer might choose to extend the Purchase Order application. In extending this application, the client adds a new table, several columns to the database by using Database Configuration; adds a new domain containing several look up values by using Domains; adds a new tab into the Purchase Order application presentation by using Application Designer and finally develops a business workflow to automate an approval of data managed through the new table.
    2. There are four steps to migrating MAM configuration data to another environment:
      1. Define - This is where the package is designed by using one or more migration groups. Each migration group is made up of one for more object structure. Also what type is the type of package will have to be defined.
      2. Create - Creates that XML manifest for the package to gather the data.
      3. Distribute - Creates the file or inserts the data into another database by using JDBC. If a file is generated then it can be copied to the appropriate location.
      4. Deploy - This is where the packaged file is imported into the next database. This is a two-step process:-import-deploy
    3. There are two types of packages:
      1. Snapshot - A Snapshot package is a collection of content representing data available at a particular point in time in the underlying database. This is similar to executing a SQL SELECT statement with a WHERE condition against a table in a database. The records that are returned from the database are the records that match the SELECT statement.
      2. Change - A Change package is based on changes performed by one or more users over a period of time. Changes result in database events. These events can be inserts, updates, or deletes. When a change package is defined, Migration Manager has tracked such events in real-time. Such tracking is performed by Migration Manager between two designated points in time. The starting point is package activation and the ending point can be either package creation or package deactivation. The tracking is performed only upon the content based on various migration groups actually included in the package definition.
  12. Given a customer requirement to capture information in the various log files about the MAM environment, describe Logging and the Logging application capabilities so that the use of the Logging application has been defined and is understood.
    With emphasis on performing the following tasks:
    1. Logging enables one to create and manage log files that contain informational, warning, or error messages about the system.
    2. Logging has three main components:
      1. Loggers: Loggers are components in the product that prepare log statements to be written to console or log file. Loggers are named entities or keys, for example, log4j.logger.maximo.sql. Loggers form a hierarchy. A logger is defined as an ancestor of another logger if its name followed by a dot is a prefix of the descendant logger name. A logger becomes the parent of a child logger if there are no ancestors between itself and the descendant logger. For example, log4j.logger.maximo.sql is the parent of log4j.logger.maximo.sql.WORKORDER. One can assign the following levels to loggers: DEBUG, INFO, WARN, ERROR, and FATAL. A level indicates a type of event that the system logs.
      2. Appenders: One can send logging requests to multiple destinations. An output destination is called an appender. Appenders can exist for consoles or files. One can associate one or more loggers with a given appender. Alternatively, one can associate a single logger with multiple appenders.
      3. Layouts: A layout determines the output format of a log statement. A layout is always associated with an appender. For example, a conversion pattern such as %d{dd MMM yyyy HH:mm:ss:SSS} [%-2p] %m%n results in the following log statement: 27-08-2009 14:07:41,508 [main] INFO MyApp - Entering application.
    3. The capabilities of the Logging application are:
      1. Create loggers that are components in the product that prepare log statements to be written to console or log file.
      2. Associate the appropriate log level with each logger.
      3. De-activate loggers except root loggers.
      4. Configure appenders that represent a console or log files to which log statements are written.
      5. Specify an appropriate file name for an appender.
      6. Specify a log file size for an appender.
      7. Associate a logger with multiple appenders.
      8. Associate an appender with multiple loggers.
  13. Given a customer requirement to retrieve historical and structured data from the system, describe the use of Classifications so that a customer understands how Classifications can be used to structure data and help retrieve historical data from the system.
    With emphasis on performing the following tasks:
    1. The Classifications application is used to create classifications and establish an overall classification hierarchy. Classifications can help to retrieve historical data from applications.
    2. Classification is used as templates for specifications which store information about many objects such locations, assets, items, and Work Orders.
    3. Classification structures are like directory structures. A classification structure can be built the same way that a directory structure is built: from the top down in parent-child relationships. First, a parent (a classification) is created, and then its children are added (each child is also a classification), which belong to the parent. Each child then can become a parent and have its own children. This pattern can continue indefinitely. The structure from the top-level parent to the child is the classification path. For example, a classification called Request For Service is created. Under it, several children can be created - IT, Facility, Telco, and HR - which belong to Request For Service. Each child is a classification. Request For Service is the parent of the children: IT, Facility, Telco, and HR. Next, a child under Facility is created: Move. Facility is now a parent of Move, with the following classification path:Request For Service \ Facility \ MoveThis path shows that a Move belongs to Facility and Facility belongs to Request For Service.
    4. Objects such as assets, locations, or items can be added to Classifications. These objects can also be associated with the classification path. Consequently, a classification path that will be used with multiple objects can be created, such as assets, locations, and items. For example, one hierarchy to classify an asset, but a different hierarchy to classify the repair of that asset can be used. Associations can be made with one or more objects, such as asset, item, or solution. These settings can be used as a filter to identify the following criteria:
      1. Records that can be associated with the classification
      2. "Select Value" dialog boxes that display the classification.

Section 4 - Design Documentation

  1. Given a set of business process diagrams, scope of work, gap analysis, project documents, and workshop outcomes, create one or more functional specification.
    With emphasis on performing the following tasks:
    1. Collect and collate the documented outcomes from the project scope, business process documents, functional workshops, and gap analysis.
    2. Define the objective or purpose statement for the functional requirement.This outlines the need in the first place to even have this document and what business drivers there are.
    3. Define the outcome of the functional specification.This is a statement that drives the necessary outcomes to achieve this statement. Such a statement should clearly outline who, how, what, when, and why.
    4. Define the assumptions used within the creation of the functional specification.Each functional specification might have some areas to be presented, implemented, or at least put forward as an option, might have one or more areas that have to be assumed to be either correct in place or available for the function to work. For example, for me to get to work on time I assume that the trains will be running on time.
    5. Define the risks and benefits of the functional specification to the project and to the business.Each functional statement contains areas that if implemented will have a risk or benefit on the project's outcome for such things as time, scope, and money.
    6. Define the recommendations.This is providing a list of recommendation options based on all the available input.
    7. Document the functional requirements.
  2. Given a saved query, a Key Performance Indicators (KPI), a Workflow, a conditional UI, a data restriction, the application designer, and security groups, configure IBM Maximo Asset Management V7.1 (MAM) so that the user's experience through the UI is customized to meet the needs of the company.
    With emphasis on performing the following tasks:
    1. Generate a Start Center template
      1. Grant security groups access to one or more Portlets from the security group application.
      2. Create one or more saved queries (marked as public is preferred) in each application that one will be presenting on the Start Center in the Result Set Portlet.
      3. Create one or more KPI's (marked as public is preferred) in each application, or from the KPI Manager application that one will be presenting on the Start Center in either the KPI Graph Portlet or the KPI List Portlet.
      4. Create a Start Center template, choosing one or more Portlets.-Define the content of each Portlet. There are the following Portlets:-KPI List-KPI Graph-Result Set-Favorites-Quick Insert-Bulletin board-Inbox/Assignment
      5. Save the template.
      6. Assign the template to one or more security groups.
    2. Create a Workflow
      1. Determine when in a workflow that it will have to:-Assign a user to task.-Use a notification.-Use an escalation.
    3. Design a security group and assign one or more users so that it:
      1. Grant or restricts which application and its functions they have access to.
      2. Make any UI control hidden, read-only by using object restrictions.
      3. Make any attribute hidden, read-only or required by using attribute restrictions.
      4. Restrict what data that the user has access to by using data restrictions.
      5. Grant or revokes security option access by using conditional option access.
      6. Grant access to sites and their storerooms.
    4. Design application changes based on which security group the user belongs to, the data being used or as a globally set option so that the UI controls are hidden or change. The change can be the color of a field changes based on the data.
    5. Create one of more statements in the conditional expression manager that can be used in security groups or in the application designer.

Register for a test

Register for an IBM Certification test at Prometric and take a step into your future.

IBM at Prometric