1 00:00:00,000 --> 00:00:05,760 you guys have been up to at your company? Do you want to give us just a general broad 2 00:00:05,760 --> 00:00:14,460 update? Right now we're in the middle of a beta of our Xenos Core 2.1, which is pretty 3 00:00:14,460 --> 00:00:20,160 exciting for us because it's the first time we've really done some aesthetically pleasing 4 00:00:20,160 --> 00:00:27,800 things in our interface. We worked on integrating our network monitoring data with Google Maps 5 00:00:27,800 --> 00:00:32,780 so you can actually see geographically where your failures are in your network or what 6 00:00:32,780 --> 00:00:38,900 status is in your network. So systems management is far from sexy, but when you have a little 7 00:00:38,900 --> 00:00:46,120 bit of eye candy in there, it's nice and it's more useful. To our earlier discussion about 8 00:00:46,120 --> 00:00:51,200 customization of the interface, we're working on sort of the drag and drop interface and 9 00:00:51,200 --> 00:00:57,600 ability to customize our dashboards versus previous versions where a predefined interface 10 00:00:57,600 --> 00:01:02,580 interface. So that's pretty exciting for us. We've gotten a lot of interest and lots of 11 00:01:02,580 --> 00:01:06,580 good feedback from our user community, our beta testers. 12 00:01:06,580 --> 00:01:12,860 And OSBC, when you and Bill and I talked, it seemed like you guys were, kind of unlike 13 00:01:12,860 --> 00:01:16,720 a couple of other people in the area, moving more into the sort of model CMDB sort of way 14 00:01:16,720 --> 00:01:21,120 of doing things. And I wonder, in that time, how has that worked out for you guys? 15 00:01:21,120 --> 00:01:26,100 Well, I think since that time, I think they've announced the new ITIL spec for CMDB version 16 00:01:26,100 --> 00:01:33,080 3. And it's interesting because they're talking more about federated CMDB because the CMDB is 17 00:01:33,080 --> 00:01:35,080 sort of a unicorn, right? 18 00:01:35,080 --> 00:01:40,080 You're trying to collect all the information about your organization in one place. 19 00:01:40,080 --> 00:01:45,060 Right. And so that implies that one system is going to be doing that. And I don't think 20 00:01:45,060 --> 00:01:51,060 that's realistic. Because while Xenos has a very, very detailed view of the world, there 21 00:01:51,060 --> 00:01:56,060 may be small parts of your infrastructure you can't see. And having a federated CMDB is very, 22 00:01:56,060 --> 00:02:02,060 very interesting, I think, to a lot of people who already have existing systems. So you can 23 00:02:02,060 --> 00:02:07,060 pull it all together. So I think we get a lot of interest in that area. I think a lot of people 24 00:02:07,060 --> 00:02:15,060 we talk to about CMDB and ITIL and that stuff are still trying to digest what ITIL is and how 25 00:02:15,060 --> 00:02:20,060 they're going to apply it and what CMDB is. But having an option where your data structure 26 00:02:20,060 --> 00:02:24,060 is easily accessible makes it a lot more appealing. 27 00:02:24,060 --> 00:02:29,060 Do you guys work or think you would work with the CMDB Federation group to do things along that line? 28 00:02:29,060 --> 00:02:36,060 We'd be glad to. I think when you're a small company, being an active participant in a lot 29 00:02:36,060 --> 00:02:40,060 of those organizations, you have to be very selective about what you can do. 30 00:02:40,060 --> 00:02:44,060 Sure. I guess they take up a lot of time to get the perfection of the standards. 31 00:02:44,060 --> 00:02:51,060 Yeah. And it's complex stuff. It's consensus building and understanding how everybody's technology. 32 00:02:51,060 --> 00:02:56,060 And there's a lot of things I'd like to be participating in now that we just didn't have the cycles. 33 00:02:56,060 --> 00:03:01,060 John, you do a lot of Tivoli consulting. And do you come across CMDBs a whole lot? 34 00:03:01,060 --> 00:03:06,060 Yeah. I mean, it's white hot in the enterprise. I mean, everybody's talking about it. 35 00:03:06,060 --> 00:03:14,060 I mean, everybody's trying to build a strategy around it. In the IBM space, they have a product called TATAM, 36 00:03:14,060 --> 00:03:20,060 which is their discovery module. So it was from a collation acquisition they made where it's pretty interesting. 37 00:03:20,060 --> 00:03:25,060 It will actually go out and do kind of spidering discovery of your enterprise. 38 00:03:25,060 --> 00:03:31,060 You know, to kind of first go out and collect your basic port scans and then start building on top of that. 39 00:03:31,060 --> 00:03:34,060 And then go into your, you know, deep dive into like an Oracle database. 40 00:03:34,060 --> 00:03:42,060 And they built that all on a structured CMDB. They actually call it the CCMDB, configuration change management database. 41 00:03:42,060 --> 00:03:51,060 So yeah, I mean, the problem is, you know, in the big enterprise, unless you've got it from kind of the CIO level mandating it, 42 00:03:51,060 --> 00:03:55,060 there's a lot of false starts, I think. It's hard. 43 00:03:55,060 --> 00:04:04,060 And one of the things you talked about federated CMDB, you know, and this is why I've got to be a little bit cynical is that the problem with federated projects like that, 44 00:04:04,060 --> 00:04:10,060 where you get big, large vendors in there that actually are competitors, and they try to create this one simple standard. 45 00:04:10,060 --> 00:04:18,060 You know, in my experience over the last 25, 30 years of doing this stuff, I've never seen something like that really succeed. 46 00:04:18,060 --> 00:04:29,060 Particularly when you pull in large competitive like a BMC with HP and an IBM and say, "Okay, we're all going to hold hands and build this thing." 47 00:04:29,060 --> 00:04:31,060 It typically doesn't work that way. 48 00:04:31,060 --> 00:04:33,060 Well, thanks for spending this time. 49 00:04:33,060 --> 00:04:34,060 Thanks, KJ.