Post in EXT] Service agreements

We have a core that develops Aps.  They do not offer a service contract.  If
additional work needs to be done, a new contract is negotiated for external
users or a new request is submitted by internal users. We also had problems
with customers not understanding what was included and what was not.  Just like
Jeff said we had problems until we learned to clearly communicated scope of
work.

Rest of post

-----Original Message-----
From: Core Administrators Network Forum <email obscured>> On Behalf Of
Megan Tardif
Sent: Monday, January 3, 2022 3:29 PM
To: <email obscured>
Subject: [EXT] Re: [core administrators network forum] Service agreements

WARNING: This email originated from outside of MD Anderson. Please validate the
sender's email address before clicking on links or attachments as they may not
be safe.

Thank you, Jeff. I hadn't thought of that issue.

Megan

On Mon, Jan 3, 2022 at 4:27 PM Jeffrey Weiss <email obscured>>
wrote:

> Hi Meghan,
>
> We had a core that did exactly that for 5 or 6 years and it did not
> work out well. It was difficult to recover the actual cost of
> providing the service, in part because customers routinely
> overestimated what they were entitled to and the core underestimated
> the effort require to provide that support. When the core folded it
> took us well over a year to disengage from the active projects, a
> number of which had difficulty finding someone to take over maintenance of
their code.
>
> Jeff
>
>
> -----Original Message-----
> From: Core Administrators Network Forum <email obscured>> On
> Behalf Of Megan Tardif
> Sent: Monday, January 3, 2022 3:22 PM
> To: <email obscured>
> Subject: [core administrators network forum] Service agreements
>
> Hi. Does anyone currently offer Service Agreements on the work that
> they perform under their service center? For example, a service center
> develops an app and the client would like to purchase a 2 year service
> agreement to help cover maintenance needs and/or software updates over
> the next 1 or 2 years.
>
> Thank you,
> Megan
>
> Megan J. Tardif
> Sr. Financial Manager of Coordinated Operating Research Entities
> (CORE) University of Maine Engineering & Science Research Building
> (ESRB), Room
> 153 Orono, Maine 04469
> Phone:  207-581-1225
>
> ――
> View topic
> https://urldefense.com/v3/__http://list.abrf.org/r/topic/7pxBHVL6IrtLF
> od8wbPDlL__;!!Dq0X2DkFhyF93HkjWTBQKhk!HY_AOoERbpSC6r3VbsulhFogzt6bAcAe
> 1hnErYsubBsfMke3nJeJJ-W8yRJnWCm02s-qCs1CWg$
> Leave group <email obscured>?Subject=Unsubscribe
>
>
> ――
> View topic
> https://urldefense.com/v3/__http://list.abrf.org/r/topic/2Pxf8jpSC0U76
> Yltm73Al6__;!!PfbeBCCAmug!we92KiznmJtd0uQdcfj9NPhlv_p-fodoSxM90YPcgirw
> Xx2OEnI1L6dnXJ6H-Pw$ Leave group
> <email obscured>?Subject=Unsubscribe
>
>

――
View topic
https://urldefense.com/v3/__http://list.abrf.org/r/topic/1sNwcISWzL4W2OcI4q9AQV__;!!PfbeBCCAmug!we92KiznmJtd0uQdcfj9NPhlv_p-fodoSxM90YPcgirwXx2OEnI1L6dnrHuvVbo$
Leave group <email obscured>?Subject=Unsubscribe


The information contained in this e-mail message may be privileged,
confidential, and/or protected from disclosure. This e-mail message may contain
protected health information (PHI); dissemination of PHI should comply with
applicable federal and state laws. If you are not the intended recipient, or an
authorized representative of the intended recipient, any further review,
disclosure, use, dissemination, distribution, or copying of this message or any
attachment (or the information contained therein) is strictly prohibited. If
you think that you have received this e-mail message in error, please notify
the sender by return e-mail and delete all references to it and its contents
from your systems.