System Validations and Tracking Clause Samples

System Validations and Tracking. After you complete and comply with all registration and application requirements and submit your application, the application will be validated by ▇▇▇▇▇▇.▇▇▇. You will receive a notification that your application is being processed. You will receive two additional e-mails from ▇▇▇▇▇▇.▇▇▇ within the next 24-48 hours (one notification email will confirm receipt of the application in ▇▇▇▇▇▇.▇▇▇, and the other notification email will indicate that the application was either successfully validated by the ▇▇▇▇▇▇.▇▇▇ system or rejected due to errors). It is important that you retain this ▇▇▇▇▇▇.▇▇▇ tracking number. Receipt of the ▇▇▇▇▇▇.▇▇▇ tracking number is the only indication that ▇▇▇▇▇▇.▇▇▇ has successfully received and validated your application. If you do not receive a ▇▇▇▇▇▇.▇▇▇ tracking number, you may want to contact the ▇▇▇▇▇▇.▇▇▇ help desk for assistance (see Resources for Assistance in Section 3.4). If ▇▇▇▇▇▇.▇▇▇ identifies any errors and rejects your application with a “Rejected with Errors” status, you must address all errors and resubmit. If no problem is found, ▇▇▇▇▇▇.▇▇▇ will allow the eRA system to retrieve the application and check it against its own agency business rules (eRA Commons Validations). If you use ASSIST to complete your application, you can validate your application and fix errors before submission. After you successfully submit your application through ▇▇▇▇▇▇.▇▇▇, your application will go through eRA Commons validations. If no errors are found, the application will be assembled in eRA Commons. At this point, you can view your application in eRA commons. It will then be forwarded to SAMHSA as the receiving institution for further review. If errors are found during eRA Commons validation, you will receive a System Error and/or Warning notification regarding the problems found in the application (see 4.2 below). You must take action to make the required corrections and resubmit the application through ▇▇▇▇▇▇.▇▇▇ before the application due date and time. Do not assume that if your application passes the ▇▇▇▇▇▇.▇▇▇ validations that it will successfully pass eRA validations and will be received by SAMHSA. You must check your application status in eRA Commons to ensure that no errors were identified. It is critical that you allow for sufficient time to resubmit the application if errors are detected. You are responsible for viewing and tracking your applications in the eRA Commons after submission through ▇▇▇▇▇▇.▇▇▇ to ensure accurate an...
View SourceView Similar (36)

Related to System Validations and Tracking

  • Points of Interconnection and Trunk Types 2.1 Point(s) of Interconnection. 2.1.1 Each Party, at its own expense, shall provide transport facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA selected by Covista.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • CONTRACTOR NAME CHANGE An amendment is required to change the Contractor's name as listed on this Agreement. Upon receipt of legal documentation of the name change the State will process the amendment. Payment of invoices presented with a new name cannot be paid prior to approval of said amendment.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.