1. Lawrence Berkeley National Laboratory
MAXIMO Integrations using IBM Datastage and OSLC JSON API
Pankaj Bhide
Computer Systems Engineer

2. About LBNL Managed and Operated by University of California
4200 Employees, 3000 Affiliates, 10,000 visitors processed annually
~$800M/year Budget
180 buildings on site
6 leased offices in the Greater Bay Area
6 User Facilities

3. LBNL Mission Biosciences Computing Sciences
Solving national challenges in energy, environment and health issues; and advance the engineering of biological systems for sustainable manufacturing..
Computing Sciences
High-performance computing and networking through research in mathematical modeling, data analysis and computer system architecture and software.
Earth and Environmental Sciences
Tackling some of the most pressing environmental and energy challenges of the 21st Century in order to enable sustainable stewardship and judicious use of the Earth’s subsurface energy resources.
Energy Sciences
Seeking solutions to the global energy-related challenges that impact our planet through a deeper understanding of the interactions between energy and matter.
Energy Technologies
Internationally recognized global leader in energy-efficient technologies, developing science and policy solutions to address the world’s most critical challenges.
Physical Sciences
Exploring the fundamental forces and particles of matter from deep within the hearts of atoms to the farthest edges of the universe. .

4. MAXIMO@LBNL Brief implementation history
Rel (pure windows app, work order tracking, procurement, SQRs)
Rel (Assets, Locations, Inventory)
Rel (Y2K compliance, Job Plans, PMs)
Rel (More functions - MEA, Safety Plans)
Rel (Web enabled, replace MEA with MIF, SQR with Actuate)
Rel (Implemented at the Advanced Light Source division
Rel (JAVA extensions, development of home grown web apps
2010 Rel (Lockshop / dataSplice for mobile implementation)
Rel (replace JAVA with Jython, BIRT with Actuate, SSO)
Rel (MRO workflow for WPC activities)
Rel (Akwire from Solufy)
Re-design and develop the integrations using Datastage and OSLC JSON Rest API………………...

5. Integrations at a glance
Slide 1

6. Integrations (technologies used - past)
Slide 1

7. Integrations (technologies used - past -[contd.])
Collect/analyze integration requirements.
Using MAXIMO sql logger, find out the “select/insert/update/delete” statements using the application.
Develop common functions/procedures.
Develop Oracle PL/SQL programs/Java that perform the needed “insert/update/delete” statements required for the integration needs.
Develop a unix shell script that launches the PL/SQL programs.
Using Tidal job scheduler, schedule their execution at the predetermined intervals.

8. Integrations (technologies used - past -[contd.])
Limitations
Can only work with the Oracle database.
Not supported by IBM.
May need to revise the code before upgrading MAXIMO to the newer release.
Old technology (not useful for web services, features similar to meta data sharing, upsert etc.)

9. Integrations (options considered)
Options evaluated for the integration
Flat files export/import
Interface table/s processing
HTML calls to object structures (XML based)
MAXIMO REST API
OSLC JSON REST API

10. Integrations (OSLC JSON REST API)
Primary features of OSLC JSON REST API
RESTful
Provides Insert, Read, Update, Delete capabilities
Payload in JSON format
Columns and filtering criteria can be supplied similar to Structured Query Language.
Utilizes Object Structures
Allows loading the data in bulk mode
Filtering using Saved queries
Queries using relationships
Dynamic paging
Handling Attachments
Provides aggregation functions
Tight integration with Automation scripts

11. Integrations (OSLC JSON REST API - Quick Examples)
Get the data from MAXIMO
No extra installation/configuration is needed.
Find out the out-of-box object structure [OS] (if not available, create a new OS from the underlying MBO).
Perform HTTP Get by specifying the MAXIMO host, path, the columns (from the object structure) and the filtering criteria (if needed)
Depending upon the filtering criteria, MAXIMO will fetch the results from the database and it will display the results in JSON format.

12. Integrations (OSLC JSON REST API - Quick Examples)
Get a few details of the corrective maintenance work orders reported by :
&oslc.select4=wonum,description,description_longdescription,rep ortedby&oslc.where5=supervisor=”813149” and worktype=”CM”
Host name
Path for OSLC resource
Name of the Object Structure
Details of the work orders (columns from the OS)
Filtering criteria

13. Integrations (OSLC JSON REST API - Quick Examples)
Sample HTTP Response JSON

14. Integrations (OSLC JSON REST API - Quick Examples)
Inserting work orders (request): Provide details of work orders (bulk-load) to be inserted

15. Integrations (OSLC JSON REST API - Quick Examples)
Inserting work orders (response) : 2 work orders are created.

16. Integrations (How to utilize API? … Options)
Now, it has been decided to utilize OSLC JSON REST API for the integration...…. How to utilize ??
A few options were evaluated:
Development of the programs using Python that read the data from the source application and performs HTTP Post/Get to MAXIMO and vice versa.
Development of the programs using Java that read the data from the source application and performs HTTP Post/Get to MAXIMO and vice versa
Utilize Data Extraction and Loading (ETL) tool that reads the data from the source application and performs HTTP Post/Get to MAXIMO.

17. Integrations (IBM InfoSphere DataStage)
IBM® InfoSphere® DataStage® is a data integration tool for designing, developing, and running jobs that move and transform data.
InfoSphere DataStage, allows:
Design data flows that extract information from multiple source systems, transform the data as required, and deliver the data to target databases or applications.
Connect directly to enterprise applications as sources or targets to ensure that the data is relevant, complete, and accurate.
Reduce development time and improve the consistency of design and deployment by using prebuilt functions.
Minimize the project delivery cycle by working with a common set of tools across InfoSphere Information Server.

18. Integrations (Let us review an example…!!!)
High level requirement
The data about buildings/floors/rooms originates in Archibus. It needs to be periodically synchronized into MAXIMO’s “locations” MBOs.
Analysis
Review tables/columns of the source application in Archibus
Prepare a custom object structure (OS) based upon “locations” MBO in MAXIMO
Prepare a mapping document that describes how the columns from the source table will get mapped to the columns of the OS in MAXIMO and if needed any transformation rules.

19. Integrations (An example...continued)

20. Integrations (An example… Overall job - before review)

21. Integrations (An example...)
Let us build the datastage job…..
Read the data from Archibus

22. Integrations (An example...)
Let us build the datastage job…..
Read the data from Archibus

23. Integrations (An example...)
Let us build the datastage job…..
Read the data from MAXIMO

24. Integrations (An example...)
Compare the data between Archibus and MAXIMO

25. Integrations (An example...)
Compare the data between Archibus and MAXIMO

26. Integrations (An example...)
Look up properties

27. Integrations (An example...)
T R A N S F O R M A T I O N

28. Integrations (An example...)
Filter

29. Integrations (An example...)
J S O N C O M P O S E R

30. Integrations (An example...)
J S O N C O M P O S E R

31. Integrations (An example...)
Shared container
(similar to functions/methods/subroutines...)

32. Integrations (An example… Overall job - revisited)

33. Integrations (concluding points)
Automation scripts using Jython that are tightly integrated with OSLC JSON REST API and Datastage.
ZERO SQL (for insert/update/delete) for any MAXIMO Objects (strict interaction with MAXIMO business objects using OSLC JSON REST API).
Throttling input and output traffic for MAXIMO.

34. Integrations (concluding points)