Emergency Services Interconnection Forum ESIF Subcommittee G

1
Emergency Services Interconnection Forum (ESIF)
Subcommittee G

• July 20, 2005
• AGENDA

2
Subcommittee G

• Objectives for this Meeting
• Address any New Issues from Opening Session
• Continue development of Issue 30 resolution
  document
• Continue work on Issue 33

3
Agenda

• Call to Order and participant sign-up
• Agenda Review and Approval
• Opening Remarks
• a. Summary of Virtual meetings and conference
  calls
• New Business
• a. New Issue discussion and disposition (1 hr)
• Old Business Issue 30 Discussion (1.5 hr)
• Review and Approve Baseline document
• Address Contributions
• Old Business Issue 33 Discussion (1.5 hr)
• Review and Approve Baseline document
• Address Contributions
• Workplan Review
• Review Decisions and Action Items
• Next Meeting

4
Issue 30 Call Delivery
5
Issue Statement / Business Need

• Data Delivery Testing There is a need to
  establish a standard testing procedure, including
  rebid intervals, that will measure the consistent
  and timely delivery of the data of wireless 911
  calls to the PSAP. This standard procedure
  should include all elements of the emergency
  services network and the PSAP CPE/ALI network.
  There is thus a need to establish a testing
  procedure that will measure the timely, accurate
  delivery of wireless 9-1-1 calls and the
  associated location data to the PSAP. The intent
  of this interconnection issue is not to test
  wireless carrier accuracy, but rather to
  establish procedures/standards to test that the
  delivery of that data remains constant through
  the network and is delivered with integrity to
  the PSAP.

6
Desired Results

• Development of a standardized wireless Enhanced
  911 call and data delivery test mechanism.

7
Impact on Other Issues or Procedures

• This effort will be dependent, in part, on the
  work product of ESIF Issue 22 and the related
  efforts of Study Group G.

8
Issue 33 Maintenance Testing
9
Issue Statement/Business Need

• There is a need to establish a standard set of
  requirements for Maintenance Testing as defined
  by the ESIF Subcommittee G during ESIFs 5 and 6.
  These testing requirements are essential to
  addressing the need for on-going compliance with
  the FCCs E9-1-1 Phase 2 performance mandate and
  the pertinent guidelines identified in the FCCs
  OET Bulletin No. 71 regarding Post-installation
  monitoring and testing.

10
Suggested Solution

• Development of the associated requirements
  document for maintenance testing after an E9-1-1,
  Phase 2 system has been deployed. This effort
  will be leverage the work product of ESIF Issues
  22 and 30.

11
Subcommittee G Test Methodology

• Gustavo Pavon
• Chair

12
Subcommittee Group G Test Methodology

• Decision
• Issue 33 will include Accuracy maintenance and
  Functionality Maintenance
• Issue 30
• Doug Stuard of Andrew Corp. presented current
  baseline text under development. The group
  reviewed approximately 50 of the document.
  Review will continue at a future Web Meeting.
• Contribution 21 from Nextel and Intrado will be
  re-distributed with changes suggested during the
  meeting. Consensus on the contents will be
  called at the next meeting. If approved, will be
  included in the next revision of the baseline
  document.

13
Subcommittee Group G Test Methodology

• Issue 33
• Contribution from T-Mobile
• Agree on text leading to use of Incremental
  testing and Predictive Modeling
• Agree on Useable Life of Accuracy Test Data (as
  modified)
• Contribution 20
• Verizon will revise and resubmit per discussion
• Contribution 18 from Technocom
• Agree on possible smaller sample size
• Agree on adaptive sample size
• Contribution 19 from Technocom
• Will be discussed at the next opportunity