Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

Oliver and Pat had an initial call with BMC (Pete Grammaticas, Bryan Campbell, Dave Haddad and Scott Eshleman) to talk about the IS&T Service Portfolio, our prototype, and the possibility of using the Remedy CMDB to house this information.  Attached are the notes from the conversation:

IS&T Service Portfolio
Remedy CMDB
Considerations
Data needs to feed other systems
Ability to schedule both push and pull of data from other systems
Need to decide where what data should live

API integration with web services
BMC needs to look specifically at CMDB web services and what is available
Ability to show integration points and dependencies for given offering or component
Ability to relate configuration items and designate type of relationship
CMDB is flat, not a tree like the prototype, so visual representation is different
Ability to attach documents to specific fields
Ability to store up to 3 attachments
CMDB does not have designated fields for attachments, just generic space for what ever attachments you deem necessary, limit of 3
Ability to associate people, teams and RT queues with services, offerings and products/components
Information can be captured, but functionality (see below) cannot

Ability to launch email directly from application
No ability to launch email
Is this requirement?
Ability to create RT ticket directly from application
No ability to launch email attached to rt queue
Is this requirement?
Hierarchy of family, service, offering
Hierarchy of business service, technical service, service offering instance
Not clear what this would look like in Remedy, need to model in WebEx
Live link to KB and Website
Ability via federated links to "launch in context"
Not clear what it would take to implement in CMDB
Ad hoc searches
No ad hoc searches
Reports can be built to replace popular searches, but staff would not have a one stop shop for information (like Daptiv, staff would have to navigate different parts of the application to get certain kinds of information)

Prototype vs CMDB.xlsx

Next steps:
Pete and Bryan will determine technical resource from BMC to continue exploration with us by Monday 4/30 (Scott)
Technical resource will have access to prototype for review and discussion (Pat will address)
WebEx will then be scheduled (5/10/12) to gather additional data (putting portfolio side by side with Remedy CMDB and try to create portfolio hierarchy in Remedy dev)