it it was branded 'Phoenix', then yes...that was the system :) On Wed, Nov 12, 2014 at 2:33 PM, Danaceau, Chris <[email protected]> wrote:
> ** > > LJ was the the WCom system I eventually took over? > > > > -- > > Thank You, > > > > Chris Danaceau > > FINRA > > 240-386-6728 (desk) > > 301-367-8949 (cell) > > Remedy FAQ > <http://wiki.finra.org/confluence/display/TechOpsCtr/Remedy+FAQ> > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *LJ LongWing > *Sent:* Wednesday, November 12, 2014 12:51 PM > *To:* [email protected] > *Subject:* Re: OT: What was the first ARS app you built? > > > > ** > > My first app was a rebuild of a custom HelpDesk we used internally....it > was on 3.2...had tons of bells and whistles and did many things that tons > of systems I've worked on since didn't do...was a healthy team and > experience to start off my Remedy career...wow, it's been a long time. > > > > On Wed, Nov 12, 2014 at 10:27 AM, Jason Miller <[email protected]> > wrote: > > ** > > I thought I would start a side topic from the "how fast could that be?" > thread. We have seen more and more "out of the box ITSM" installs in > recent years and custom development appears to be less prevalent. Many of > us started out building anything and everything under the sun. > > > > For me, I had just switch from working in an aerospace fabrication shop to > my first IT job at a help desk. About 6 months in I became very interested > in what else Remedy could do. As I learned more about what Remedy could do > I really wished we would of had it at the job I had left. > > > > So with that my first app was one geared around running a fab shop. The > app tracked customers, jobs/parts, equipment and staff. It could associate > what machine a part is in and who is working on it. Also it could show the > status of a machine so planners didn't schedule a job in a machine that was > down for maintenance. Also you could not schedule machinists to a job if > they were on vacation. > > > > It probably also had things like an email to the worker when a job/part > was assigned to them. I have been trying to find the definition in recent > years. I am sure I would get a kick out of how I built things back then. > > > > Jason > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > Confidentiality Notice:: This email, including attachments, may include > non-public, proprietary, confidential or legally privileged information. If > you are not an intended recipient or an authorized agent of an intended > recipient, you are hereby notified that any dissemination, distribution or > copying of the information contained in or transmitted with this e-mail is > unauthorized and strictly prohibited. If you have received this email in > error, please notify the sender by replying to this message and permanently > delete this e-mail, its attachments, and any copies of it immediately. You > should not retain, copy or use this e-mail or any attachment for any > purpose, nor disclose all or any part of the contents to any other person. > Thank you. > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
