You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
18 lines
3.4 KiB
18 lines
3.4 KiB
5 months ago
|
pwgsc&rquirt&custsat1&6.0.0&&&custsat1&&&bcarico@actscorp.com&N.Y.N.N
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
0.1.o.o.o.N.0&custsat1.001&custsat1.003&custsat1.004&custsat1.006&custsat1.007&custsat1.008&custsat1.009&custsat1.011&custsat1.013&custsat1.015&custsat1.016&custsat1.018&custsat1.019
|
||
|
&?0=0?1=0?2=0?3=0?4=0::.0:1:1:0&?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0?9=0?10=0?11=0::.0:1:1:0&?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0?9=0?10=0?11=0::.0:1:1:0&?0=0?1=0?2=0?3=0?4=0::.0:1:1:0&?0=0?1=0?2=0?3=0?4=0::.0:1:1:0&?0=0?1=0?2=0?3=0?4=0::.0:1:1:0&?0=0?1=0?2=0?3=0?4=0::.0:1:1:0&?0=0?1=0?2=0?3=0?4=0::.0:1:1:0&?0=0?1=0?2=0?3=0?4=0::.0:1:1:0&::.0:1:1:N.&?0=0?1=0?2=0?3=0?4=0::.0:1:1:0&?0=0?1=0?2=0::.0:1:1:N.&?0=0?1=0?2=0?3=0?4=0?5=0?6=0::.0:1:1:N.
|
||
|
&?xxx?1?xxx?xxx?xxx::Needs to be more responsive to changes in market that developers/clients are moving to.%0D%0ANeeds to improve internal NCS communications and coordination so that client requests are not dropped and do not go into a void.%0D%0ANo one contact person in NCS can handle client problems from start to finish. The problems are handed off to another group in NCS and possibly another and possibly.... It has taken months to get answers...and sometimes we never get an answer to a problem. Through frustration, we fix it ourselves if we can (we do NCS%27s job).&?xxx?1?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx::Although I am not overly happly with the suite, I have had good service in this area.&?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?8?xxx?10?xxx::Although I am not overly happly with the suite, I have had good service in this area.&?xxx?xxx?xxx?3?xxx::Any change by AMS seems to involve a long drawn-out and painfull experience by AMS and NCS. This is unacceptable to clients who want GTIS to make solid and timely decisions to deliver on their new applications.&?xxx?xxx?2?xxx?xxx::Improving this past year. More briefings at AMS Exec and to AMS Managers should be sought by NCS. Don%27t wait to be asked%21&?xxx?xxx?xxx?3?xxx::WIN2000 is an excellent example of something wrong from the start. No seen as a corporate project at start %22just an operating system change%22 is a quote from one NCS person. NCS started this project and fought against project management of it for PWGSC. AMS was forced to start conversion to WIN2000 and NCS was not (contrary to what NCS stated) ready. The list goes on. There are other examples as well such as Oracle 8i, etc.&?xxx?xxx?2?xxx?xxx::Our teams at Tupper have a different view.&?xxx?1?xxx?xxx?xxx::See above notes on internal NCS issues relating to poor customer service.%0D%0AThere are heroes in NCS (and they are great%21) but no unified NCS customer service.%0D%0A&?xxx?xxx?xxx?xxx?4::AMS Client Authority brings AMS problems to NCS for resolution. NCS shoots the messanger (the CA).%0D%0ANCS believes the issues escallation process within NCS works in spite of AMS comments to the contrary. This needs work (agreement at AMS/NCS meeting to assist AMS CA was never put in place).%0D%0AFrom an AMS perspective, nothing has changed. Reference all above comment boxes on client issues.&I have questions regarding the NCS report statistics on customer service. They don%27t always seem to match up to what I know. Corrective action time does not seem to be from the receipt of the first contact by NCS. It seems to be from the time it is assigned within NCS. This can be a considerable delay.::&?xxx?xxx?xxx?xxx?4::&?0?xxx?xxx::&?xxx?xxx?xxx?3?xxx?xxx?xxx::
|
||
|
Not Scored by Definition
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|