We are using electronically signed PDF's stored in sharepoint.
-sc
From: listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dave Lum
Sent: Tuesday, October 28, 2014 1:10 PM
To: ntsysadm@lists.myitforum.com
Subject: [NTSysADM] Change Management process and
We use Salesforce for ticketing which has a change control process within it.
I'm guessing budget is limited. Perhaps a PF?
On Oct 28, 2014, at 10:11, Dave Lum li...@theitgarage.com wrote:
We are defining a new change management process at %dayjob%. The current
consensus is to do it all
*I've been asked why not email and I can't come up with anything more
useful than new engineer starts and has no way to review previous
changes. Kind of a weak argument...*
How about auditor asks for centralized update of changes, and now a bunch
of people need to generate mail dumps?
You can
Seen it done through many methods, some smart and collaborative, others not.
Word documents, Excel spreadsheets, SharePoint, System Center Service
Manager, other bespoke tools (Onyx/Vantive/etc.)
Ironically, one of the best I saw was a Lotus Notes database. I know, I
know.
I'd go SCSM if I had
Couple of small places I've worked with have used Sharepoint...
One used Excel.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Dave Lum
Sent: Tuesday, October 28, 2014 12:10 PM
To: ntsysadm@lists.myitforum.com
Subject: [NTSysADM] Change Management
Ah! Run screamingpoke yourself in the eye with a sharp
stick..its better than suggested email.
Here are just some of the reasons:
1) Email does not have a followup and reminder system (automated
notifications of approvals, escalations etc)
2) Email will flood your mailbox and
] Change Management process and documentation
Ah! Run screamingpoke yourself in the eye with a sharp stick..its
better than suggested email.
Here are just some of the reasons:
1) Email does not have a followup and reminder system (automated notifications
of approvals, escalations etc)
2
...@lists.myitforum.com] *On Behalf Of *geoff taylor
*Sent:* Tuesday, October 28, 2014 2:02 PM
*To:* ntsysadm@lists.myitforum.com
*Subject:* Re: [NTSysADM] Change Management process and documentation
Ah! Run screamingpoke yourself in the eye with a sharp
stick..its better than suggested
Boom, winner!
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
On Behalf Of geoff taylor
Sent: Tuesday, October 28, 2014 11:02 AM
To: ntsysadm@lists.myitforum.com
Subject: Re: [NTSysADM] Change Management process and documentation
Ah! Run screaming
...@lists.myitforum.commailto:listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of geoff taylor
Sent: Tuesday, October 28, 2014 2:02 PM
To: ntsysadm@lists.myitforum.commailto:ntsysadm@lists.myitforum.com
Subject: Re: [NTSysADM] Change Management process and documentation
Ah! Run
@lists.myitforum.com
Subject: RE: [NTSysADM] Change Management process and documentation
Sysaid is pretty epic, we use it for our help desk. Have not used it for
change management.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
On Behalf Of geoff taylor
Sent
, 2014 2:02 PM
*To:* ntsysadm@lists.myitforum.com mailto:ntsysadm@lists.myitforum.com
*Subject:* Re: [NTSysADM] Change Management process and documentation
Ah! Run screamingpoke yourself in the eye with a sharp
stick..its better than suggested email.
Here are just some of the reasons
...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of geoff taylor
Sent: Tuesday, October 28, 2014 2:49 PM
To: ntsysadm@lists.myitforum.com
Subject: Re: [NTSysADM] Change Management process and documentation
As I mentioned we being poor just adapted the helpdesk components. But Sysaid
.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
On Behalf Of Jason Kirkland
Sent: Tuesday, October 28, 2014 12:57 PM
To: ntsysadm@lists.myitforum.com
Subject: RE: [NTSysADM] Change Management process and documentation
So what process does a small company use
@lists.myitforum.com
Subject: Re: [NTSysADM] Change Management process and documentation
Ah! Run screamingpoke yourself in the eye with a sharp
stick..its better than suggested email.
Here are just some of the reasons:
1) Email does not have a followup
Sysaid is a fine solution, as many people have said.
And, if you hunt down an out-of-print book (I believe it was Outlook 2003 for
Developers) there is a ECM (Engineering Change Management) application
developed using public folders and the Outlook Object Model.
System Center Service Manager
...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] *On Behalf Of *Jason Kirkland
*Sent:* Tuesday, October 28, 2014 12:57 PM
*To:* ntsysadm@lists.myitforum.com
*Subject:* RE: [NTSysADM] Change Management process and documentation
So what process does a small company use for change management? Do
will we being everything over?” and “but everyone
is used to this process now…”.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Daniel Chenault
Sent: Tuesday, October 28, 2014 10:17 AM
To: ntsysadm@lists.myitforum.com
Subject: Re: [NTSysADM] Change
@lists.myitforum.com
Subject: RE: [NTSysADM] Change Management process and documentation
Thanks for the feedback everyone.
Fortunately budgeting isn’t an issue, and we only rolled out this change
management process two weeks ago and we’re still refining it. Knowing how
momentum works, I’d rather change this now
19 matches
Mail list logo
