NENA ISSUE SUBMISSION & CHARTER FORM - NENA-ADM-003

Instructions for NENA ISSUE SUBMISSION FORM:

1.  The Originator completes Section 1 and e-mails the form to the NENA Committee Resource Manager (CRM) at .

2.  Upon approval of the DSC Co-Chairs & HQ Staff[1], the CRM publishes the form for 10-day review.

3.  The Development Steering Council (DSC) reviews Section 1 along with comments received during the 10-day review and decides whether to accept the Issue according to the criteria described in NENA ADM-002. Acceptance of the Issue does not necessarily include acceptance of the “Requested Outcome or Proposed Solution”. If the Issue is accepted and assigned to a Committee, the CRM fills out Section 2 based on DSC instructions.

4.  The Committee Co-Chair(s) and all Subcommittee/Working Group Chairs complete Section 3 (the Working Group Charter) and emails the form to the CRM.

5.  The DSC approves the Working Group Charter and the CRM enters the approval date in Section 2.

6.  The CRM sends a copy of the updated form to the Originator.

7.  The CRM updates Section 2 when the Issue status changes.

NOTE: Some fields on this form will be used to populate the Charter if this Issue is accepted and assigned by the DSC.

Section 1 - Issue Details
To Be Completed by the Originator
Please provide input for all fields
Short title (what the Issue may easily be referred to by)
Map Database Service (MDS) / Date Submitted:
4/6/2017
Originator Name / Richard Kelly, Brooks Shannon
Originator Organization / 911Datamaster Inc., GeoComm Inc.
Originator Email / ,
Originator Phone / 512-331-0633, 763-954-0900
Description of Problem or Opportunity (Provide detailed and clear information. If this is time sensitive or critical provide an explanation.
The proposed MDS functional element from STA-010.2 requires definition of its required functionality and support needs. While the objective of the MDS is a system that can deliver BOTH a standardized map view of any place in the US and/or deliver the GIS data for that place, which in turn can be utilized by local map displays or CAD systems, technical details and operational impacts and considerations are lacking.
To provide guidance on this complex functional element for NG9-1-1, work should begin immediately on forming a workgroup and drafting an informational or requirements document. WG members should be required to have GIS, and/or on-line data management and delivery experience as well as other related CPE, networking and 9-1-1 technical support expertise.
Requested Outcome/Proposed Solution (Provide detailed and clear information):
The request of this ISF is for a workgroup to be formed to draft a document (INF or REQ) to provide a description of the basic functionality necessary in an MDS, which can also guide standards work within the i3 Architecture working group. Content to cover and questions to be answered include:
·  Definition of the MDS and how it interacts with other functional elements (for example, how it is discovered)
·  Who operates the MDS? Should a single entity such as NENA operate it and provide the service, or should a private sector organization manage one via an RFP (such as with the NEAD), or should vendors and local governments each provide their own authoritative MDS?
·  General structural requirements (ex. PSAP connectivity support for potentially thousands of locations).
·  Where would the database server(s) be located (geographic diversification required)?
·  Network and bandwidth requirements for information delivery.
·  Security needs and concerns (who can access the MDS, and what actual data can they access?).
·  Performance requirements (ex. 24, 7, 365 availability?).
·  Preparations for non-responsiveness or failure of access.
·  Expectations from GIS data provisioning authorities regarding data updates (speed of the process, need for high-availability or lack thereof, etc.)
·  Discrepancy notification and correction process for map display and GIS data
·  Map display basic requirements (ex. cartography).
·  GIS data delivery basic requirements (ex. layer download selection process).
·  MDS service provider responsibilities.
·  Out of country display extent (Mexico, Canada, off-shore, etc.).
·  2D vs 3D, or how to handle elevation in the display or data.
This effort may be very similar in structure to the ECRF and LVF provisioning document and that doc could be used as a template for this work.
Note: The final resolution and disposition of this issue may not conform precisely to the Requested Outcome or Proposed Solution. The Working Group consensus will determine the actual means used to accomplish the intent of the Requested Outcome or Proposed Solution.
Section 2 – DSC Tracking
To be Completed by NENA DSC
Issue Number / 20170406
Date Published for 10-Day Review / 04/07/2017
Review Comments / 04/25/2017
Date and Reasons for Rejection by the DSC
Date Assigned by DSC / 04/25/2017 – reassigned 5/16/2017
Submit PINS to ANSI? / ☐ Yes ☐ No Date PINS Submitted:______
Referred To - Who will receive the Issue?:
If applicable, which NENA Committee will own this Issue?
☐ Accessibility ☐ Agency Systems ☒ Data Management ☐ Data Structures ☐ Interconnection & Security ☐ NGTPC ☐ PSAP Operations ☐ Public Education & PSAP Training
Or specify the internal NENA owner of this Issue ______
********************************************************************************************
Or specify which external entity it was referred to:
☐ APCO ☐ ATIS-ESIF ☐ ATIS-PTSC ☐ ATIS-WTSC ☐ IEEE ☐ IETF ☐ NFPA
OTHER ______
Working Group Assigned To
(If applicable)
Estimated/Requested Completion Date of draft (if applicable)
DSC Instructions to the Working Group (includes supplements or modifications to the Originator’s Requested Outcome)
Date the Charter is due back to DSC / 6/23/2017
Date Working Group Charter Approved
Actual Completion Date
(to be completed later)
Status Updates: link to Scopes & Goals
Resolution: (a brief explanation of how the Issue was resolved for closure)
Section 3 – Working Group Charter
To Be Completed by the Committee Co-Chairs & all Subcommittee/Working Group Co-Chairs, and approved by the DSC.
Assigned Committee Working Group (should be based on the name used in the Issue Submission form, and include the Parent Committee name.)
Data Management Committee & Map Database Service Working Group / Issue Number
(from above)
20170406 / Date WG Created
(if it is a new WG)
Goal/Objective/Deliverable (Describe each goal/objective/deliverable and provide detailed and clear information, based on the accepted Issue.)
#1 goal/objective/deliverable: ______
#2 goal/objective/deliverable: ______
#3 goal/objective/deliverable: ______
Importance (Rank each goal/objective/deliverable as Essential, Important, or Desirable as follows;
·  Essential – required for something else to succeed
·  Important – helpful toward the success of another work effort
·  Desirable – asset for other reasons
#1 goal/objective/deliverable is ranked: Choose an item. :
#2 goal/objective/deliverable is ranked: Choose an item.
#3 goal/objective/deliverable is ranked: Choose an item.
Schedule (Considering the Estimated Completion Date for the Issue, establish when each goal/objective/deliverable should be met or accomplished, and provide detailed and clear information, based on the accepted Issue.
If applicable, list any intermediate schedule milestones, e.g., “Outline complete”, “First draft complete”.)
#1 goal/objective/deliverable: ______
#2 goal/objective/deliverable: ______
#3 goal/objective/deliverable: ______
Dependencies (Identify all known dependencies for achieving success, e.g., completion of work in other committees or other organizations outside of NENA.)
Chair(s) (Who will serve as the Chair(s) for the group performing this work? Provide name, phone and email.)
Editor(s) (Who will serve as the Editor(s) for the group performing this work? Provide name, phone and email.)
Participating Organizations (Identify all outside organizations that will be needed for success of the identified goals/objectives/deliverables, e.g., APCO, ATIS, NEIM, IHIS, etc.)
Subject Matter Expertise Needed (Identify the types of SMEs needed to achieve success.)
Required Resources (Identify the types of non-human resources needed to achieve success, e.g., list server, web site, etc.)
Initial Work Schedule Plan (Identify the initial call & meeting schedule, e.g., every Tuesday at 10am EASTERN.)
Status Reporting Schedule (The Charter serves as the guiding document to drive work activities toward established goals. Additionally, it serves as a tool to ensure timely status reports to the DSC throughout the work interval. Depending on the nature of the work, and its impact on other work, the timing of status reports may differ among WG activities.
This field is to be used by the DSC to establish the timing of WG status reports to the DSC or designated Project Mgr(s).)
Measurement (How will each goal/objective/deliverable be evaluated? Use quantitative and/or qualitative measures which are descriptive of the measurement criteria)
#1 goal/objective/deliverable: ______
#2 goal/objective/deliverable: ______
Other?

NENA ADM-003, 07/28/2015 Page 1 of 5

[1] See ADM-002 for details surrounding Issue acceptance.