National Lifeline Accountability Database (NLAD ... · Households that became Lifeline Program subscribers prior to June 1, 2012 . Date service provider determined subscriber was

NLAD Connectivity Workshop #3 (October 31, 2013) 3

National Lifeline Accountability Database (NLAD)

Connectivity Workshop

October 31, 2013



Goal and Agenda


The goal of this workshop is to further refine how carriers will interact with NLAD by providing new and updated information, answering questions from the second workshop, and providing NLAD Access Portal screen shots.

Goal

Goal and Agenda


Part 1 • Introductions • NLAD resources • NLAD background

(updated timeline, problem resolution)

• NLAD Release 1.1

Part 2 • CSV data format (new

fields) • NLAD Input Template (new

fields) Part 3 • NLAD Access Portal • API (new fields, return

batch file change)

Agenda

Goal and Agenda

We’ll take a break before Part 3.



NLAD Resources


Available since 9/18/2013: • Overview webinar • Initialization video • Connectivity Workshops 1 & 2

(webinar and slides) • NLAD Input Template • NLAD File Validation Rules • NLAD Enrollment Eligibility Codes

handout • Address Standardization Guide

handout • Release 1.0 User Guide

www.usac.org/li/tools/nlad

NLAD Resources

New as of 11/4/2013: • Training videos

– Upload a Subscriber File – Enroll a Subscriber – De-enroll a Subscriber – Transfer a Subscriber’s Benefit

• Glossary • Error messages • NLAD Input Template (updated) • NLAD Field Descriptions • NLAD File Validation Rules (updated) • Release 1.1 User Guide



NLAD Timeline


November 2013 • API Testing (test data only) • Connectivity workshop 11/20

October 2013 • Notifications to ETCs

(first five states)

Q1 2014 NLAD

population complete

December 2013 • NLAD account set up • Scrubbing first five

states 12/2

NLAD Timeline


We expect ETCs for the first five states (AR, LA, MD, OK, WA) to be ready to load their subscriber information by December 2. You should be transmitting this info or you will be out of compliance with FCC rules [RULE/FCC 47 C.F.R. Section 54.404(b)(1)(6), (c)(4)]: • The subscriber’s full name; • Full residential address; • Date of birth; • Last four digits of the subscriber’s Social Security number or Tribal Identification number,

if the subscriber is a member of a Tribal nation and does not have a Social Security number;

• The telephone number associated with the Lifeline Program service; • The date on which the Lifeline Program service was initiated; • The date on which the Lifeline Program service was terminated, if it has been terminated; • The amount of support being sought for that subscriber; and • The means through which the subscriber qualified for the Lifeline Program

FCC Public Notice 10/23/2013


Question Received:

During the scrubbing period, if I identify issue with subset of subscriber records do I need to correct only those records and resend them?

Answer:

No, during the scrubbing period you must correct the subscriber records and resubmit the entire file.

NLAD Timeline


Question Received:

After my state is migrated to production, do I need to provide a total refresh of the data or can I just submit the updated transactions?

Answer:

After a state is migrated to production, carriers only need to send new transaction details. Carriers do not have to resubmit the complete universe of subscribers again.

NLAD Timeline



Problem Resolution


NCS Help Desk

NLAD Customer Service (NCS)

Lifeline Program Support


• Address

• Age

• Duplicate – subscriber

• Duplicate – address

• Record missing

• TPIV

Exceptions

Exception Process


• An ETC can appeal any rejection via the same NLAD resolution request function.

• This function is available via the NAP or by calling the NCS.

Appeals

Exception Process



Dates to Remember


Service Initiation Date Subscriber Service Initiation Date to Use for NLAD Households that became Lifeline Program subscribers prior to June 1, 2012

Date service provider determined subscriber was eligible for Lifeline Program-supported service If ETC cannot provide the above date, service provider should enter the following date for that subscriber: May 31, 2012

Households that became Lifeline Program subscribers between June 1, 2012 through end of initialization (1st Quarter 2014) — Date may vary depending on state loading time frame

Date service provider determined subscriber was eligible for Lifeline Program-supported service

Households that become Lifeline Program subscribers once the database is in production, i.e. 4th Quarter 2013 and thereafter

Date service provider determined subscriber was eligible for Lifeline Program-supported service


Transaction Effective Date

Transaction Transaction Effective Date Enroll Same as Service Initiation Date

Update Date subscriber record is updated (address change, name change, etc.)

Benefit Transfer Service Initiation Date, date the new Lifeline Program benefit begins

De-Enroll Date ETC removed the Lifeline Program benefit from the subscriber


Examples

Transaction Service Initiation Date Transaction Effective Date Enroll 04/17/2011 04/17/2011 Update 05/31/2012 12/21/2013

Benefit Transfer 02/13/2013 ETC-A to 12/31/2013 ETC-B

12/31/2013

De-Enroll 04/17/2011 12/17/2013


The 60 day benefit transfer windows begins on the service initiation date.

Benefit Transfer Window

Subscriber 60 day window begins

Lifeline Program subscribers prior to June 1, 2012

Date service provider determined subscriber was eligible, or May 31, 2012

Lifeline Program subscribers between June 1, 2012 through end of initialization (1st Quarter 2014) — Date may vary depending on state loading time frame

Date service provider determined subscriber was eligible

Lifeline Program subscribers once the database is in production, i.e. 4th Quarter 2013 and thereafter.

Date service provider determined subscriber was eligible


Examples

Service Initiation Date

Transaction Effective Date

60 Benefit Transfer Window Begins

04/17/2011 04/17/2011 04/17/2011 05/31/2012 05/31/2012 05/31/2012 02/13/2013 02/13/2013 02/13/2013 12/17/2013 12/17/2013 12/17/2013 01/30/2014 01/30/2014 01/30/2014



NLAD Release 1.1


• Subscriber enroll

• Subscriber de-enroll

• Subscriber update

• Subscriber benefit transfer

• ETC subscriber check

• Subscriber verify information

• Resolution request

NLAD Release 1.1

APIs Available for Testing


• No SACs are eligible to conduct post-initialization business-as-usual transactions

• All test data currently in the system will be deleted

• Two fields have been added to the NLAD Input Template and files without these columns will be rejected:

– ETC General Use

– TPIV Flag

NLAD Release 1.1

Release 1.1 Testing


Release 1.1 Testing

NLAD Release 1.1

• A new field will be added to the Errors Download File

– ETC general use


• Download the Errors Download File

– Does not work with Internet Explorer 8

– Some users of Internet Explorer 9 may experience intermittent issues

– All other browsers appear to work without issue

• Wrong username/password combination entry may not result in error message. If the system doesn’t appear to log you in after submitting your credentials, reload the page and try again.

NLAD Release 1.1

Known Issues


Questions

Questions?



CSV Data Format: UPDATES


CSV Data Format: Updates

Field Length Type Format Comments transactionType* enroll, transfer, update,

deEnrollDeceased, deEnrollLeaving, deEnrolledFailedRecertification, deEnrollNonUsage

phoneNumberInNlad 10 Numeric nnnnnnnnnn Current NLAD phone number is required in NLAD update or de-enroll transactions and is requested but optional in an NLAD benefit transfer transaction

transactionEffectiveDate* Date mm/dd/yyyy Date associated with the action being submitted, i.e. enroll date, address change date, etc.

sac* 6 Numeric nnnnnn SAC that the subscriber is associated with

Required Fields* / Conditional Fields



Field Length Type Format Comments lastName* 50 Alpha+ Special characters

allowed – two alpha character minimum with no period allowed

firstName* 50 Alpha+ Special characters allowed

middleName 50 Alpha+ a or aaaaaaa

Special characters allowed



Field Length Type Format Comments phoneNumber* 10 Numeric nnnnnnnnnn Must be unique per subscriber

last4ssn* 4 Numeric nnnn Must provide either last four digits of the SSN or Tribal ID Number (TIN)

tribalId* 20 Alphanumeric 2 alphanumeric characters minimum

dob* Date mm/dd/yyyy Date of birth



Field Length Type Format Comments iehFlag 1 Bit 0 = no

1 = yes Flag indicating the subscriber is in a multi-household unit – if yes must provide IEH date of certification

iehCertificationDate Date mm/dd/yyyy

The date IEH information was certified

iehRecertificationDate Date mm/dd/yyyy

The date IEH information was recertified



Field Length Type Format Comments primaryAddress1* 50 Alphanumeric

primaryAddress2 50 Alphanumeric

Secondary address

primaryCity* 50 Alpha

primaryState* 2 Alpha

primaryZipCode* 10 Numeric nnnnn or nnnnn-nnnn



Field Length Type Format Comments primaryPermanentAddressFlag 1 Bit 0 = permanent

1 = temporary Flag indicating the subscriber's address is located at a permanent or temporary location

primaryTribalFlag 1 Bit 0 = no 1 = yes

Flag indicating the subscriber's address is a Tribal address

primaryRuralFlag 1 Bit 0 = no 1 = yes

Flag indicating that no postal delivery service is available at this address



Field Length Type Format Comments mailingAddress1 50 Alphanumeric

mailingAddress2 50 Alphanumeric Secondary mailing address

mailingCity 50 Alpha

mailingState 2 Alpha

mailingZipCode 10 Numeric nnnnn or nnnnn-nnnn



Field Length Type Format Comments serviceInitializationDate* 10 Date mm/dd/yyyy

serviceReverificationDate 10 Date mm/dd/yyyy Date subscriber eligibility was re-certified

eligibilityCode* 10 Alphanumeric Program under which the subscriber is eligible for the Lifeline Program benefit



Field Length Type Format Comments bqpLastName 50 Alpha+ Special characters allowed

– 2 alpha character minimum with no period allowed

bqpFirstName 50 Alpha+ Special characters allowed

bqpMiddleName 50 Alpha+ a or aaaaaaa Special characters allowed

bqpDob Date mm/dd/yyyy

bqpLast4ssn 4 Numeric nnnn Must provide either last four digits of the SSN or Tribal ID Number (TIN)

bqpTribalId 20 Alphanumeric 2 alphanumeric characters minimum



Field Length Type Format Comments linkUpServiceDate Date mm/dd/yyyy If Link Up is requested provide

date of service lifelineTribalBenefitFlag 1 Bit 0 = no

1 = yes Flag indicating carrier is claiming Lifeline Program Tribal support

acpFlag 1 Bit 0 = no 1 = yes

Flag indicating Address Confidentiality Program (subscriber address information is protected)

etcGeneralUse 50 Alphnumeric General use for ETCs1

tpivFlag 1 Bit For future use

1 Special Characters allowed: See NLAD Field Descriptions


• etcGeneralUse

• tpivFlag

NLAD Input Template




Addresses


• All subscribers must have a valid address. • If a mailing address is provided, it too must be valid. • Addresses are validated through the United States Postal

System (USPS) Address Matching Service (AMS). • The AMS system will reformat the address and search for

a single, matching address. – If it can find one, it will validate the address. – If not, the transaction will be rejected and sent back

with an AMS failure code.

Valid Addresses

Addresses


Question Received:

Is NLAD going to allow addresses that do not appear in the USPS databases as primary address if the appropriate proof is presented to prove their validity?

Answer:

A valid address is required. If the primary address is not found in the AMS, give a mailing address and set the flag to “non-deliverable rural address.”

Addresses


Question Received:

This question is for clarification of address standards. For example, if a street address says “ROAD” instead of “RD,” with it be thrown out?

Answer:

No, it will not be rejected. AMS will translate Road to RD.

Addresses


Question Received:

Our serving addresses are all MSAG 911 validated, which many times will not match a postal address. For this reason, we ask if we could set the flag on all our records that indicates the subscriber address is not postal and always send our mailing address, which is validated as postal.

Answer:

A primary address is required, so give the mailing address and set the flag to “non-deliverable rural address.”

Addresses


Address Flag Rules

Case Rule Primary Address Flag

Rural Address

When the subscriber has a non deliverable address, not registered with AMS

LOT 6 SUNNY COVE KODIAK, AK 98765 primaryRuralFlag=1

Primary Address Rural Flag Mail Address LOT 6 SUNNY COVE KODIAK, AK 98765

1

P O BOX 179 KODIAK, AK 98766


Address Flag Rules


Tribal Address

When the subscriber has a Tribal address, not registered with AMS

3 1/2 MI N OF CONOCO STORE MANY FARMS, AZ 87654 primaryTribalFlag=1

Primary Address Tribal Flag

Link Up Service Date Mail Address

3 1/2 MI N OF CONOCO STORE MANY FARMS, AZ 87654

1 9/11/2013

P O BOX 179 MANY FARMS, AZ 87655

3 1/2 MI N OF CONOCO STORE MANY FARMS, AZ 87654 1 9/11/2013 3 1/2 MI N OF CONOCO STORE MANY FARMS, AZ 87654 1


Address Flag Rules


Independent Economic Household

When the subscriber has the same address as another subscriber, but is still a qualified, independent subscriber

1234 ANY ST CLEVELAND, OH 12345-6789 iehFlag=1

Subscriber Primary Address IEH Flag

A 1234 ANY ST CLEVELAND, OH 12345-6789

B 1234 ANY ST CLEVELAND, OH 12345-6789 1


Address Flag Rules


Temporary Address

When the subscriber's address is at a temporary location ? primaryPermanentAddressFlag=1

Primary Address Temporary Address Primary Permanent Address Flag

? 1234 ANY ST CLEVELAND, OH 12345-6789 1


Questions

Questions?


BREAK



NLAD Access Portal (NAP)


• Required fields – marked with an * (asterisk)

• Fill in a field with the appropriate alpha and/or numeric data

• Format for date of birth field should be MM/DD/YYYY

– Example: 02/17/1949

• Some fields use a drop down menu to enter data

• Some fields use a radio button to enter data

Data Entry

NAP


NAP

Enroll Subscriber





Question received:

Who is the Benefit Qualifying Person (BQP)? When is the BQP required? What is the relationship between a BQP and the subscriber?

Answer:

In most cases, the subscriber is the person eligible for Lifeline Program-supported service. If the subscriber is eligible, there will be no BQP. If the subscriber is not eligible, but the subscriber is the guardian or caretaker of someone who is eligible, the subscriber qualifies based on the status of the individual they are the guardian/caretaker of. The eligible individual, in this case, would be considered the BQP.

BQP



• After entering subscriber data, you have the option of verification.

• The purpose of verification is to enable an ETC to determine whether a potential subscriber’s record is eligible for enrollment in NLAD prior to assigning a phone number.

Verify Subscriber Data

NAP


• Verify

– Phone number optional

– Validates subscriber

– Validates address

– Runs business rules

– Does not save data

Verify vs. Enroll

NAP

• Enroll

– Validates phone number

– Validates subscriber

– Validates address

– Runs business rules

– Enrolls subscriber in NLAD



Subscriber successfully enrolled


NAP

Subscriber Lookup



NAP

Update Subscriber





NAP

De-enroll Subscriber





NAP

Submit Resolution Request


12345678


NAP

Benefit Transfer




NAP

Reports



NAP

Account Management


Account Management

Sub Accounts API Account

ETC Admin

497 Officer


Questions

Questions?



API


• Subscriber file upload

API

API Testing


• Check subscriber (ETC & agency)

• Verify subscriber

• ETC reports

– Subscriber

– Transaction

– Resolution

Functionality Added

API

• Return error messages to include:

– Error code

– ETC general use field data

– Phone number in NLAD


• All required fields must contain data.

• You must include a phone number.

• If you are updating the phone number, the phone number in NLAD will automatically update.

• Sending blank information in optional fields will remove existing data.

• The same business rules apply as in initial enrollment.

When updating a subscriber:

API


API

Questions?


Email: [email protected]

With questions, please contact:

Contacts

mailto:[email protected]


Thank you!

Documents

National Lifeline Accountability Database (NLAD ... · Households that became Lifeline Program subscribers prior to June 1, 2012 . Date service provider determined subscriber was