I believe that SNOW does have an advanced development package (for extra cost of course) that I think allows you to build custom workflow for your environment. I changed the subject line since I want to go on a bit of tangent.
Let me play devil's advocate for a moment and hopefully not generate too many intense responses, just consider this food for thought. I find it interesting how loyal we all seem to be to a specific platform (ARS) but history shows us that languages and platforms arrive on the scene, rise to dominance and then eventually are phased out for the next latest & greatest technology. ARS has evolved over time and has been able to stay relevant but depending on the direction that BMC takes the platform that could change. As an arbitrary example how many COBOL programmers are left these days? I am sure they have a great list of the advantages of that language but the reality is that the market for their skills is not nearly as large as it once was. I know this is not an exact comparison but hopefully my point comes across. If you are an ARS developer and have skills in requirements gathering, designing workflow etc. there will come a day when you may have to transition to a different product whether you like it or not. I know that consultants will have an easier time of this since they can jump from client to client. Direct hires will have the tough choice of learning a new platform or leaving their company for a job elsewhere at a company who is still using ARS. In a past life I was only spending a maximum of 40% of my time in ARS development and the rest on other duties. Had my company decided to move to another platform I would more than likely have remained with them and learned the new platform rather than attempt to find a job as a Remedy developer elsewhere. That type of decision will be tougher for someone who is devoted 100% to ARS development. Something else to note is that it seems from what I've seen that many companies are moving to a mindset of configuration instead of customization and are using more out of the box applications rather than spend development cycles on custom code. I am not sure I understand the driving forces behind that but have experienced it first-hand. That type of mindset would steer a company towards a platform like SNOW instead of ARS in my opinion. -Rick From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe D'Souza Sent: Wednesday, July 30, 2014 8:28 AM To: [email protected] Subject: Re: ENGAGE ** That is because to the best of my knowledge, you cannot really develop or customize SNOW, you use it as is. So implementation time is obviously quicker. I haven't worked with the product myself, but in none of their demo's would they claim that they can customize the product to tailor it completely to your needs. They basically define the product and you got to wrap your needs around it. But then again this might be my biased opinion about it, being a Remedy person for as long as I have been. I wonder if SNOW sales reps watch this list... I would love their comments on my statement that their product is not customizable and hence would suck for a house that needs some tailoring to the OTB offering.. Joe ________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Richter, Howard (CEI - Atlanta) Sent: Wednesday, July 30, 2014 8:32 AM To: [email protected]<mailto:[email protected]> Subject: Re: ENGAGE John, I do agree with what you wrote, and would like to add. That our world is changing and we need to prepare for those changes. We know that SNOW is knocking on BMCs door, with its pretty UI and fast (per their sales department) development/implementation time. And we know that others are out there as well (since they see they can make money). So I am looking for this meeting not just to show me how to fix bad code or create new items, but on what are BMC's future plans. To see if they have the vision to address these new comers to our world, or if they don't. Also maybe BMC will see this thread and add some technical sessions. However, (at least in my view) we need to look a little into the future that BMC sees and then think about what is the best for the companies we work for (and with) and ourselves. Just my thoughts, hbr From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of John Sundberg Sent: Tuesday, July 29, 2014 5:11 PM To: [email protected]<mailto:[email protected]> Subject: Re: [arslist] ENGAGE ** Thanks for the plug Mr. Baker. Good one. I don't think you will find any BMC Remedy specific stuff at KEG. BUT*** - you will definitely find stuff on how to make your BMC Remedy system nicer/easier to manage and how to do even more with the system you already have. Also - I will throw in - this is not a new complaint/issue for BMC RUG - this has been the issue for quite awhile. Ultimately - the ARSList is looking for a Remedy development only event. (Not even ITSM) If BMC (or somebody else) would create it - it would be helpful - and therefore people would expand their existing system. A "sticky system" is a system that solves your needs in unique ways that are not easily replaceable. But - if your goal is to be out of the box and ITIL (Blah blah blah). Well, you just made it very easy for your competitor to displace you. Where - the only differentiator of meaning is price - and that is not a fight BMC wants to be in (or most any company for that matter). A "sticky system" is one that you can make yours. So BMC would be wise in encouraging that, making it be easy and the "norm" to do so. Educate - and it can happen. Show everybody new features for out of the box - and you simplify your replacement strategy for your competitors. -John _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
