EDI Introduction. Table of Contents

Transcription

1 Introduction Table of Contents 1. INTRODUCTION GENERIC ORDER FLOW BUSINESS MODEL DEVELOPER WORKSHEETS USAGE DEFINITIONS CONTENT TRADING PARTNER ACCESS INFORMATION Date/Time Reference Exceptions Delimiters

2 1. Introduction 1.1 Generic Order Flow Business Model Normal Order Flow The following diagram depicts a normal 850 Purchase Order flow. A normal order flow means: No errors, fatal or non-fatal No jeopardy situations No supplemental order will be issued Normal Order Flow Co-Provider Qwest Purchase Order 997 FA Order Provisioning FA IMA Local Response (LR) FOC OSS 3 Completion 997 FA Completion 1. A Purchase Order is initiated by the CLEC, translated by the CLEC s to an 850 Purchase Order, and passed to the Qwest. Qwest s translator performs a syntax check and returns a positive 997 Functional Acknowledgment (FA) to the CLEC. The translator then maps the 850 Purchase Order to an application file format, which is passed to Interconnect Mediated Access (IMA). The IMA gateway is a middleware that performs order content edits and interacts with the Service Order Processor (SOP) in the Operating Support System (OSS). When the resulting service request passes all SOP edits, it becomes a pending order. 2. After the SOP accepts the pending order, a Firm Order Confirmation (FOC) Local Response (LR) message is sent to IMA. The IMA gateway formats and forwards the LR - FOC message to the, where the message is mapped into an LR - FOC and transported to the CLEC s. A 997 Functional Acknowledgment will be returned to Qwest to confirm the receipt. 2

3 3. Upon completion of the service order request, the SOP generates a Completion Notification to IMA. The IMA formats and forwards the Completion Notification to the where the message is mapped to an Completion and transported to the CLEC. A 997 (FA) will be returned to Qwest to confirm the receipt. Exception Order Flow Fatal errors prevent the order from processing. To correct a system generated fatal error, the original request must be corrected and resubmitted using the same PON and version where the error originally occurred, or submit a new PON. To correct manually generated fatal errors a corrected request with the same PON and incremented version should be submitted. If the Qwest Interconnect Service Center (ISC) erroneously generates a Local Response - Reject for a LSR, the LSR can be placed back into the normal process with or without a supplement being sent. The decision to issue a supplement is at the CLEC s discretion. An 850 Purchase Order may encounter a non-fatal error generated by the service center. To correct a non-fatal error, the CLEC must send a corrected request with the same PON and incremented version to correct the errors. If the CLEC does not respond to the electronic notification of the non-fatal error within four Qwest ISC business hours, the service center will send a manually generated LR - fatal error to the CLEC, and the fatal error flow is used. The PIA field is used to communicate changes Qwest made on the service order that are different from what was requested on the original LSR. These changes are a result of two different conditions: 1) Changes that occurred as a result of a verbal directive from the CLEC. 2) Changes due to processing requirements within Qwest. Examples of processing issues would be where the Desired Due Date (DDD) on the LSR was shorter than standard interval or where the DDD was on a holiday. When the PIA field is populated, the Remarks section may contain notations that identify any deviations from the original request. After the fatal or non-fatal error is corrected by the CLEC, the SOP accepts the pending order and an or LR - FOC is sent. If an error is found on an order after a LR - FOC has been received by the CLEC, or if there is a problem meeting the commitment on the local service request, an or LR - Jeopardy will be sent. When all errors have been corrected, Qwest will send an LR - FOC as defined in step 2 of the normal order flow. There are situations in which a subsequent FOC may be issued on the existing version of an original LSR. If Qwest has made any changes to the Service Order or needs to communicate changes back to the CLEC, Qwest may send a subsequent or additional FOC LR on an existing version of a LSR The diagram below illustrates possible exception responses to the 850 or 860 Purchase Order. For simplicity, associated 997 Functional Acknowledgments are not reflected in the diagram. 3

4 Exception Order Flow Co-Provider Qwest Purchase Order System LR FATAL Pass IMA edits NO Fatal Error Message Order Provisioning Purchase Order LR NONFATAL Manual LR FATAL 860 SUPP LR Jeopardy LR Jeopardy Completion IMA Pass SOP edits Fatal or Non-Fatal Error for 850 for 860 LR Jeopardy for 860 Completion OSS 1. If an 850 Purchase Order fails IMA edits, an System LR - Fatal is returned to the CLEC with one or more fatal error codes. 2. The CLEC, having received the System LR - Fatal, needs to correct the 850 Purchase Order with the same PON and version or submit a new PON, and re-send the 850 Purchase Order as an original request. 3. If an 850 Purchase Order receives a Manual LR - Fatal, the CLEC should resubmit the request with the same PON and an incremented version. If an 850 Purchase Order receives a non-fatal LR - Error, the CLEC can either resubmit the request with the same PON and an incremented version or call the service center to discuss the error(s). 4. When the 850 Purchase Order or 860 Supplemental (SUP) is posted to the SOP, an LR - FOC or an LR - FOC will be returned to the CLEC. This confirmation means the SOP has accepted the 850 Purchase Order or 860 Supplemental (SUP) and provisioning of the service has begun. 5. If Qwest has a problem meeting the commitment on the local service request, and the CLEC has chosen to receive notification via IMA, a jeopardy will be issued. If this occurs, an LR Jeopardy or an LR - Jeopardy is sent. If the jeopardy is caused by Qwest conditions, Qwest will negotiate a new due date and send a new LR - FOC. If the jeopardy is 4

5 caused by non-qwest conditions, the CLEC must submit a supplemental request to correct the condition with the same PON and incremented version number as the original request. If this jeopardy caused the due date to be missed, the supplemental request must include a revised due date. If an error or reject condition is found after the LR - FOC is sent, an / LR - Jeopardy will be sent. 6. Upon completion of the service order request, an Completion notice will be sent. Supplemental Order Flow An 860 Supplemental (SUP) is issued when the CLEC has a need to change an 850 Purchase Order before or after it is posted in Qwest s SOP. The starting VER number of an 860 Supplemental (SUP) is 2 because the original 850 Purchase Order is assumed as 1. If a non-fatal error is returned, the CLEC must send a corrected request with the same PON and incremented version to correct the errors. The PIA field is used to communicate changes Qwest made on the service order that are different from what was requested on the original LSR. These changes are a result of two different conditions: 1) Changes that occurred as a result of a verbal directive from the CLEC. 2) Changes due to processing requirements within Qwest. Examples of processing issues would be where the Desired Due Date (DDD) on the LSR was shorter than standard interval, or where the DDD was on a holiday. When the PIA field is populated, the Remarks section contains notations that identify any deviations from the original request If the CLEC does not respond to the electronic notification of the non-fatal error prior to LR - FOC within four Qwest ISC business hours, the service center will send a manually generated fatal error to the CLEC, and the fatal error flow is used. After the fatal or non-fatal error is corrected, the SOP accepts the supplemental pending order and an LR - FOC is sent. If an error is found on an order after a FOC has been received or if there is a problem meeting the commitment on the local service request an LR - Jeopardy will be sent. There are situations in which a subsequent FOC may be issued on the existing version of a Supplemental LSR. If Qwest has made any changes to the Service Order or needs to communicate changes back to the CLEC, Qwest may send a subsequent or additional FOC LR on an existing version of a LSR. 5

6 Supplemental Order Flow: Co-Provider Initiated Change Co-Provider Qwest SUPP LR FATAL Pass IMA edits NO Fatal Error Message Order Provisioning SUPP LR NON-FATAL Pass SOP edits 3 LR FATAL 860 SUPP IMA NO Fatal or Non-fatal Error OSS 4 LR Jeopardy LR Jeopardy for Completion Completion 1. If the 860 Supplemental (SUP) fails the IMA edits, a System Fatal error, LR - Fatal, will be returned to the CLEC with one or more fatal error codes. 2. The CLEC should resolve the errors and re-submit the 860 Supplemental (SUP). While an 860 Supplemental (SUP) is in progress, the CLEC should wait until the current 860 Supplemental (SUP) is confirmed with an LR - FOC or an error is received ( LR - Fatal Reject or LR - Non-Fatal Error) before issuing another 860 Supplemental (SUP). 3. If an 860 Purchase Order receives a non-fatal error, the CLEC can either resubmit the request with the same PON and an incremented version or call the service center to discuss the error(s). If an 860 Purchase Order receives a Manual Fatal error, the CLEC should resubmit the request with the same PON and an incremented version. 4. When the 860 Supplemental (SUP) is posted to the SOP, an LR - FOC will be returned to the CLEC. This confirmation indicates that the SOP has accepted the 860 Supplemental (SUP), and provisioning of the service has begun. If Qwest has a problem meeting the commitment on the local service request, and the CLEC has chosen to receive notification via IMA, a jeopardy will be issued. If this occurs, an LR - Jeopardy is sent. If the jeopardy is caused by Qwest conditions, Qwest will negotiate a new due date and send a new LR - FOC. If the jeopardy is caused by non-qwest conditions, the CLEC must submit a supplemental request to correct the condition with the same PON and incremented version number as the original request. If this jeopardy caused the due date to be missed, the supplemental request must include a revised due date. 6

7 If an error or reject condition is found after the LR - FOC is sent, an / LR - Jeopardy will be sent. 5. Upon completion of the service order request, an Completion notice will be sent. 7

8 1.2 Developer Worksheets Usage Definitions The Developer Worksheets identify business rules for specific fields on a per-product basis. The following table defines usage values as presented for specific activity types: Usage Definition N R O C Not Required This field is not required for this activity, for this product. If the indicator is (N) for all activities, Qwest does not map the field and will return a 997 if populated. Required This field is required for this activity, for this product. The system shall enforce business rules and only allow a valid entry. Optional This field is optional for this activity, for this product. The system shall not enforce any business rules and should allow a valid entry. Conditional This field is required for this activity based upon a condition. The system shall enforce the business rule and require a valid entry when the condition is true. P Prohibited If this field is populated it will result in a fatal reject. Note: If a field contains a usage value of R, C, or O, the field is mapped to an segment. 8

9 1.3 Content The following information is documented in the remainder of this document: Assumptions - outlines assumptions and constraints. Specific Trading Partner Access Information - lists the specific -related agreements between the Co-Provider and Qwest, such as the envelope, functional acknowledgment, and other topics. Business Model/ Transaction Process Flow - describes the interaction of each business function in terms of process flow for pre-order, order and post-order activity for this release. Developer Worksheets Define Qwest business rules. Mapping Examples/Data Models - provides mapping for all types of pre-order, orders and post-order transactions defined in this release. Data Dictionary - defines the use of each segment and data element for the 850,, 860,, and 836 transaction sets for pre-order, order, and post-order transactions. 9

10 1.4 Trading Partner Access Information Date/Time Reference The D/T SENT field (DTM*097 on the Header) of every transaction set is assumed as follows: If the transaction set is originated from the Co-Provider, the Co-Provider will use a consistent time zone. If the transaction set is originated from Qwest, the time indicated is Mountain time Exceptions Transaction sets 850,, 860 and for order are used with the following exceptions: For transactions, the maximum use of the SLN has been changed to > 1 Note: There are situations where a backend system will return a blank in a data field. An example is for address validation query (AVQ) exact match response with supplemental data the N1 DT SUPPMATCH loop may be returned as "empty" if the building, room, or floor is blank in the Qwest back-end system. This is a valid response Delimiters For readability purposes, the Mapping Examples included in this document are shown using an asterisk as the element delimiter. This is illustrative only. The delimiters and separators to be used in actual trading are: Element Separator: HEX 7C = (vertical bar or pipe) Sub-Element Separator: HEX 1F = (non-printable characters of 0x1f ) Segment Separator: HEX 0A = linefeed Repetition Separator: HEX 1D = (non-printable characters of 0x1d ) 10