[AusNOG] AAPT metro Ethernet

[Jeffrey Sims]

Yes exactly David and a minor correction because punctuation makes all the
difference along with the missing words.

Previous I wrote "Pipe you ask for an RFO, AAPT you ask for an RFO" should
have read

"You ask Pipe for an RFO and you will get one if asked, AAPT you ask for an
RFO and you seem to get a bag full of excuses".

This has just been my experience dealing with the companies, Pipe seem to
care about their customers, AAPT on the other hand, I've just recently had
an email from a manager which I'll reply to shortly with the details and
the case brief for their review.

On Mon, Jul 2, 2012 at 3:04 PM, David Hughes <David at hughes.com.au> wrote:

>
> In "official" ITIL IT Service Management terminology, a PIR is actually a
> Post Implementation Review.   ITIL uses the term "Incident Report" to
> describe the document we are talking about here.
>
>
> David
> ...
>
>
>
> On 02/07/2012, at 2:40 PM, Aaron Wigley wrote:
>
> > On 2/07/12 2:28 PM, "Jeffrey Sims" <jeffy at tehintartubes.net> wrote:
> >
> >> RFO = Reason for Outage.
> >> That's how I've always known them as. Some people call them PIR (Post
> >> Incident Reports).
> >
> > As opposed to a Pre-Incident Report? :-)
> >
> > I've seen _Incident Report_ and _Post Mortem Incident Report_ also used.
> >
> > --
> > Aaron Wigley
> >
> >
> > _______________________________________________
> > AusNOG mailing list
> > AusNOG at lists.ausnog.net
> > http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20120702/5c935d95/attachment.html>