NENA Knowledge Base

NENA Development Group Guide: Difference between revisions

Page Discussion

NENA Development Group Guide (view source)

Revision as of 12:51, 1 April 2024

3,132 bytes removed ,  3 months ago
Updated url link for the document
VisualWikitext
(→‎How to Add Member in NENA Workspace to a Working Group: Added text to sort past events by Start Date-Latest when registering new members)
(Updated url link for the document)
 
(27 intermediate revisions by 2 users not shown)
Line 1:
<big>'''This Guide is a DRAFT in process'''. </big><big>If you would like to contribute and edit this material, [https://www.nena.org/page/JoinReferences_WG join the References Working Group]. If you find things here that are incorrect or could be improved, please [[Contact Us]].</big>
 
== Introduction ==
This page provides guidelines to NENA working group chairs to help them lead their groups in fulfilling the charter that was developed when the group was formed. Our volunteer working group chairs assume considerable responsibilities when they agree to lead a working group. The information presented here is intended to help guide them through the tasks that are often appear to be more complicated than necessary but are required to satisfy the requirements of a Standards Development Organization (SDO) seeking standards accredited by ANSI (American National Standards Institute). ANSI has approved the Document Development and Approval Process described in NENA-ADM-001. Since our working groups play a critical role in document development and approval, it is important that they conform to those provisions when developing documents, and that the processes can be verified. Only then can NENA standards qualify to be classified as ANSI-accredited.
=== Roles and Responsibilities of Working Group Chairs ===
The roles and responsibilities of Subcommittee and Working Group Chairs are described in [httphttps://cdn.ymaws.com/www.nena.org/resource/collectionresmgr/625EAB1D-49B3-4694-B037-8E854B43CA16standards/NENA_ADMnena-001_NDG_Org_Structure_Document_03adm-26001.5b-20122022_final_2.pdf NENA Development Group Organizational Structure (NENA-ADM-001)], Section 7.3:
 
Subcommittee and Working Group Chairs/Co-Chairs preside over their Subcommittee/Working Group, and shall coordinate their team efforts to include:
Line 55:
NENA processes and procedures that govern working group functions are described in NENA-ADM-001. In this section, we’ll describe the details of the working group processes and how they are accomplished using the various NENA resources and tools. Following these guidelines will help working group chairs manage their groups fairly and efficiently.
 
The NENA Development Group has established a collaboration web site called '''[https://nenawikikb.nena.org/wiki/NENA_Workspace NENA Workspace] (NWS)'''. The NENA Workspace provider Higher Logic has a [https://dev.nena.org/participate/faq Help/FAQs page] for their platform.
 
Each working group has a dedicated NENA Workspace account that includes an Email list, Roster, Document Library, Calendar, and other resources.
Line 65:
 
=== Managing NENA Workspace Rosters ===
NENA working groups are the hallmark of the NENA document development process. Participation from a broad industry perspective is essential, therefore, NENA does not require a NENA membership to participate in a working group or restrictsrestrict working group membership.
 
==== Request to Join ====
Line 158:
|}
 
==== How to Add a Member in NENA Workspace to a Working Group ====
In many cases, members are added to working groups and their parent committee by the Committee Resource Manager when the member is added to NENA Workspace. Members who are already in NENA Workspace can be added to the working group by the working group chair.
 
Here are the steps to add a member already in NENA Workspace to your working group.
<ol>
<li>Log on to NENA Workspace (https://dev.nena.org).
<li>Select your working group.
<li> Click the '''Settings''' gear icon.
<li>In the '''Status''' section, click on '''Add or Invite Others'''.
<li>Select the '''Invite Others''' tab.
<li> Under '''Find People to Invite''', enter the new member's first name, last name, email, or company (only need to fill in one field) and select '''Search'''.
<li>Check the box to the left of the member's name and select '''Add Selected To Invite List'''.
<li>If you need to add multiple people, repeat steps 6 and 7 above.
<li>Once all new members have been found, check the box to the left of their name and then select '''Add Immediately'''.
<li>In the pop-up window that appears, change how they are to receive messages to '''Real Time - One email for each message''' and select '''Save'''.
<li>'''Close''' the pop-up message.
<li>Select the '''Back to Community''' button in the upper left of the Invite to Community screen to return to the working group's Community Home Page.
<li>To set the new member's role, click the '''Settings''' gear icon again.
<li> In the '''Administration''' section, click on '''Members'''.
<li>At the top of the Members tab are several filters. In the first filter, select '''No Roles''' from the drop-down pick list and select the blue '''Apply Filter'''.
<li>Click the blue '''Edit Roles''' button to the right of their name. (Warning…Do not click on the drop-down arrow!)
{{Note|Note Text=To add multiple members with the same role at the same time, check the box to the left of all of the new members' names that will have the same role, change the first filter to '''Edit Roles''' from the drop-down pick list and select '''Submit'''. Check the boxes next to the appropriate roles.}}
 
<li>In the '''Edit Roles''' pop-up box, check the boxes next to '''Primary Voter''' and '''WG Member''' and then select '''Add'''.
# Log on to NENA Workspace (http://dev.nena.org).
{{Note|Note Text=<br>
# Select your working group.
* If the member is an Authorized Observer, only check the box next to '''Authorized Observer''' (do not check '''WG Member''').
# Click the '''Settings''' gear icon.
* If the member is an Alternate Voter, check the boxes next to '''Alternate Voter''' and '''WG Member'''.
#In the '''Status''' section, click on '''Add or Invite Others'''.
* '''If there are multiple members from the same company''', only one can be listed as the Primary Voter. You will need to first consult with those members to determine who will be the Primary Voter and all others will be considered Alternate Voters.
#Select the '''Invite Others''' tab.
}}
# Under '''Find People to Invite''', enter the new member's first name, last name, email, or company (only need to fill in one field) and select '''Search'''.
<li>Since NWS is a Software-as-a-Service (SaaS) solution, it can take a few minutes for the new WG member to populate in the Roster. To expedite this data population, force a sync by selecting the drop-down arrow next to the blue '''Edit Roles''' button to the right of the new member's name, and select '''Sync to Workspace''' from the drop-down menu. [[File:SynchNewMember.png|alt=Screen print: Synch to Workspace drop-down image|800x800px]]
#Check the box to the left of the member's name and select '''Add Selected To Invite List'''.
<li>Select the '''Back to Community''' button in the upper left of the Manage Community Members screen to return to the working group's Community Home Page.
#If you need to add multiple people, repeat steps 6 and 7 above.
<li>All voting members must have an Interest Category assigned (Authorized Observers do not vote). To assign an Interest Category, select the '''Workspace''' tab and then select '''Roster''' on the left side menu. For each Primary Voter, Alternate Voter, and Group Leader, select their Interest Category from the drop-down box under the '''Details''' column, and then select '''Submit Changes'''.
#Once all new members have been found, check the box to the left of their name and then select '''Add Immediately'''.
*'''Producer:''' Developers and/or providers of 9-1-1 related products (e.g., software, hardware, systems and/or networks, processes) and services.
# In the pop-up window that appears, change how they are to receive messages to '''Real Time - One email for each message''' and select '''Save'''.
*'''User:''' Those who utilize 9-1-1 related products and services, including but not limited to Public Safety Answering Point (PSAP) and 9-1-1 Authority.
#'''Close''' the pop-up message.
*'''General Interest:''' Other interested parties who do not fit in the User or Producer category (e.g., consultants, State & Federal Agencies, SMEs).
#Select the '''Back to Community''' button in the upper left of the Invite to Community screen to return to the working group's Community Home Page.
{{Note|Note Text=<br>
#To set the new member's role, click the '''Settings''' gear icon again.
* If the WG's Committee Co-Chairs are to be voting members, their role must be changed from DSC Leadership to Primary Voter (or Alternate Voter). Follow steps 13-18 above to change their role.
#In the '''Administration''' section, click on '''Members'''.
* If a new member name is not listed, repeat step 18 above to sync the member's account to NWS.
#At the top of the Members tab are several filters. In the first filter, select '''No Roles''' from the drop down pick list and select the blue '''Apply Filter'''.
}}
#Click the blue '''Edit Roles''' text to the right of their name. (Warning…Do not click on the drop down arrow!)
<li>Using your own email account outside of NWS, email a welcome letter similar to the '''[[Welcome Letter for New Members]] and copy''' [mailto:crm@nena.org crm@nena.org] to notify the new members that they have been added to the roster.
#*'''Note:''' To add multiple members with the same role at the same time, check the box to the left of all of the new members' names that will have the same role, change the first filter to '''Edit Roles''' from the drop down pick list and select '''Submit'''. Check the boxes next to the appropriate roles.
</ol>
#In the '''Edit Roles''' pop-up box, check the boxes next to '''Primary Voter''' and '''WG Member''' and then select '''Add'''. (<u>Warning</u>: See '''Note 3''' if there is more than 1 member from a company.)
'''How to register a new member to receive automated email reminders for working group meetings and attendance tracking:'''
#*'''Note 1:''' If the member is an Authorized Observer, only check the box next to '''Authorized Observer''' (do not check '''WG Member''').
#*'''Note 2:''' If the member is an Alternate Voter, check the boxes next to '''Alternate Voter''' and '''WG Member'''.
#*'''Note 3:''' If there are multiple members from the same company, only one can be listed as the Primary Voter. You will need to first consult with those members to determine who will be the Primary Voter and all others will be considered Alternate Voters.
#Select the '''Back to Community''' button in the upper left of the Manage Community Members screen to return to the working group's Community Home Page.
#All voting members must have an Interest Category assigned (Authorized Observers do not vote). To assign an Interest Category, select the '''Workspace''' tab and then select '''Roster''' on the left side menu. For each Primary Voter, Alternate Voter, and Group Leader, select their Interest Category from the drop down box under the '''Details''' column, and then select '''Submit Changes'''.
#*'''Producer:''' Developers and/or providers of 9-1-1 related products (e.g. software, hardware, systems and/or networks, processes) and services.
#*'''User:''' Those who utilize 9-1-1 related products and services, including but not limited to Public Safety Answering Point (PSAP) and 9-1-1 Authority.
#*'''General Interest:''' Other interested parties who do not fit in the User or Producer category (e.g. consultants, State & Federal Agencies, SMEs).
#*Note: If the WG's Committee Co-Chairs are to be voting members, their role must be changed from DSC Leadership to Primary Voter (or Alternate Voter). Follow steps 13-18 above to change their role.
# Using your own email account outside of NWS, email a welcome letter similar to the '''[[Welcome Letter for New Members]] and copy''' [mailto:crm@nena.org crm@nena.org] to notify the new members that they have been added to the roster.
 
#While still on the working group's Community Home Page, click the '''Settings''' gear icon.
Here are the next steps to register a new member to receive automated email reminders for working group meetings and attendance tracking:
#In the '''Events''' section, click on '''Manage Events'''.
 
#At the top of the '''Event List''' page are several filters. In the first filter, select '''Past Events''' from the drop-down pick list, in the last filter select '''Start Date - Latest''' from the drop-down pick list (in case there are multiple meeting series), and select the blue '''Apply Filter'''.
# While still on the working group's Community Home Page, click the '''Settings''' gear icon.
#Find the very first meeting in the meeting series. Select the drop-down arrow next to the blue '''Edit''' button and select '''Manage Roster.'''
# In the '''Events''' section, click on '''Manage Events'''.
#Above the filters, click on '''Manage''' and then select '''Add Registrants.'''
#At the top of the '''Event List''' page are several filters. In the first filter, select '''Past Events''' from the drop down pick list, in the last filter select '''Start Date - Latest''' from the drop down pick list (in case there are multiple meeting series), and select the blue '''Apply Filter'''.
#In the '''Register''' drop-down, select the name of the working group.
#Find the very first meeting in the meeting series. Select the drop down arrow next to the blue '''Edit''' button and select '''Manage Roster.'''
#Above the filters, click on '''Manage''' and then select '''Add Registrants.'''
#In the '''Register''' drop down, select the name of the working group.
#Check the box to the left of the new working group member(s) and then click on '''ADD.'''
 
Line 209 ⟶ 216:
#Go to '''Settings''' (gear icon).
# Select '''Members''' under Administration.
# Select '''Edit Roles''' to the far right of the person’s name you are removing (not the drop -down arrow), uncheck their voting role (e.g., Primary Voter; Alternate Voter), check '''Authorized Observer''', and '''ADD.'''
 
To remove a work group member, simply:
Line 215 ⟶ 222:
# Go to '''Settings''' (gear icon).
# Select '''Members''' under Administration.
# Select the drop -down arrow next to '''Edit Roles''' to the far right of the person’s name you are removing, and select '''Remove'''.
# Send an email to [mailto:crm@nena.org crm@nena.org] so the individual may be deactivated in NENA Workspace if they are not a member of any other work group.
 
Line 224 ⟶ 231:
# Enter all data you wish to change and '''SAVE'''.
Only the CRM can change your employer’s company name as official ballots are directly tied to company names. To change your employer, you must send an email to [mailto:crm@nena.org crm@nena.org] and request the change to your employer.
 
====Resolving Issues for Members Not Receiving NWS Emails====
When a WG member is not receiving notifications from NWS, it is important for the member to first check to see if their notification settings are correct. Notifications may not be received if:
 
*at the time the member was added to the WG, the '''Real Time''' setting was not selected.
*the member unknowingly opted-out or changed their email notifications settings.
 
If upon review of the settings, the member finds that their notification settings are correct, the CRM can be contacted for assistance. This could indicate a concern with the email address.
 
Verification of the Email Notifications must be performed by the member as the Working Group Co-Chair does not have access to the member's account. A Working Group Co-Chair should copy and paste the following instructions into an email to the member.
 
===== How a Member Verifies Email Notifications Settings For a Working Group=====
 
# Go to the <COMMITTEE or WG NAME> Home page.
#Click '''Settings''' {{Step|Step=1}}.
#A pop-up box appears with the Email Notifications displayed in the right-hand column. If '''Daily Digest''' or '''No Emai'''l is shown, click on the '''drop-down arrow''' {{Step|Step=2}} next to the setting and select '''Real Time'''. The selection will temporarily turn green with a check next to it to signify the change was made.
{{Note|Note Text=The '''Daily Digest''' setting results in only 1 consolidated email from that WG per day. This means that any last-minute notifications (such as a meeting cancelation) will not be received. The '''No Email''' setting means that no email notifications from that WG will be received. This includes meeting notices, document postings, and discussion lists.}}
 
[[File:EmailNotifications1.png|alt=Screen print: Change Email Notifications in Settings|500x500px]]
 
=====How a Member Verifies Email Notifications Settings For all of their NWS Communities=====
 
#Click the '''drop-down arrow''' {{Step|Step=1}} next to your avatar in the upper right corner of any NWS page and select '''Profile''' {{Step|Step=2}}.[[File:ProfileEmailNotification1.png|none|alt=Screen print: Change Email Notification in Profile|600x600px]]
#Click the '''My Account''' tab {{Step|Step=3}} and select '''Email Preferences''' {{Step|Step=4}}. [[File:ProfileEmailNotification2.png|none|alt=reen print: Change Email Notification in My Account|600x600px]]
#Click the '''Community Notifications''' link {{Step|Step=5}} under '''Community Emails''' to review and manage your Email Notification setting by individual NWS Community. [[File:ProfileEmailNotification3-V2.png|none|alt=Screen print: Change Email Notifications using Community Notifications link|600x600px]]
# Click on the '''drop-down arrow''' {{Step|Step=6}} next to the Email Notification setting displayed in the '''Discussion Email''' column to change the setting for an individual NWS Community. Settings are saved immediately.[[File:ProfileEmailNotification4.png|none|alt=Screen print: Change Email Notifications for all Communities|650x650px]]
 
 
=== Managing the NENA Workspace Calendar ===
The NENA Workspace Calendar must be used to for scheduling conference calls and other events. The NENA Workspace Calendar entries are available under '''Home''' in the red banner at the top of every NENA Workspace page. Reviewing the NENA Workspace Calendar prior to scheduling a new event series will assist WG Chairs in not scheduling overlapping conference calls.
 
'''If you need to reload a meeting series to your calendar:'''
Line 276 ⟶ 310:
* Confirm the full names of meeting participants are properly displayed in the Zoom Participants panel. Ask participants to correct their names as needed. The Host or a Co-host should change phone numbers to the full names of those members who have dialed into the meeting.
* Read through the Opening Questions & Statements in [https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079/documents?folder_id=130 NENA-ADM-008].
{{InfoBox|information=At the first meeting in a calendar year, the [https://nenawikikb.nena.org/wiki/NENA%27s_Intellectual_Property_Rights_(IPR)_Policy complete antitrust statement in the NENA IPR Policy]] must be read.}}
* Ask whether anyone has knowledge of Patent IPR within the scope of any deliverables. The Note Taker will record that the question was asked along with the names, affiliations, and disclosed Patent IPR stated by those responding in the affirmative.
* Ask whether anyone was aware of conflicts in content, ambiguous terms, or duplication of work. The Note Taker will record that the question was asked along with the conflict details if an affirmative response was received.
Line 297 ⟶ 331:
* The leader types a question or proposition in the Zoom Chat window addressed to "Everyone" and announces the question on the call.
* Individual callers respond to the question in the Chat window, also directing the response to "Everyone".
* After the call, the Chat log, starting with the question and including all of the responses, can be copied and pasted into the meeting notes. Zoom is set up to automatically copy the Chat window content into a text file that it writes on the Host's computer in the \Documents\Zoom folder. Alternatively, theThe Chat window content can be exported by anyone directly from the Zoom Chat window '''during the call''' by selecting the More button (three dots) and then "Save Chat."
*After the Zoom session has closed, the Chat log, starting with the question and including all of the responses, can be copied and pasted into the meeting notes. Zoom is set up to automatically copy the Chat window content into a text file that it writes on the Host's computer in the \Documents\Zoom folder.
 
==== After the Conference Call... ====
Several tasks need to be completed after the conference call is adjourned:
* If anyone disclosed patent information, contact the parent committee's Co-Chairs and Committee Resource Manager (CRM).
* Within 5 days, note taker enters attendance into NENA Workspace.
# Go to calendar and select that day’s calendar entry.
# Select '''track attendance'''.
# Select each member who was on the call.
Line 309 ⟶ 344:
# Select the group members that attended the call.
 
* Attendance must be officially recorded in NENA Workspace. An Excel spreadsheet template is available to assist note takers with tracking attendance, excused absences, and Working Group balance. '''Download the WG Attendance Template from NENA Workspace: [https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079/documents/forms130/document?document_id=28202 here]'''.
* Within 5 days, note taker uploads minutes to group library. (Use [https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079/documents?folder_id=130 NENA-ADM-008] Template)
* If edits are made to contributions or draft documents, document editor will upload updated material within 5 days using “Add a Revision” in NENA Workspace. Reviewed contributions should be updated until consensus is reached and the contributions can be incorporated into draft documents. Contributions should also be retained in the contributions folder with major contributor identified.
 
=== Conducting Polls - What you need to know aboutand NENA Workspace Ballots ===
 
Polls are an important part of a working group's activity. Surveys taken during calls using the Zoom's Poll feature or a [[NENA Development Group Guide#Use the Zoom "Chat Window" for quick surveys|Chat Window]] survey only represent the opinions of the meeting's participants but chairs are permitted to make consensus calls based on them if, in the opinion of the chairs, there is overwhelming consensus on the issue. For polls that include the entire group (or the designated voters), NENA Workspace provides two types of ballots to conduct polls. They are used to determine the preferences of the members and are also used to determine whether groups have the consensus required to publish documents.
 
See [[Conducting Polls and NENA Workspace Ballots]] for a complete guide on using NENA Workspace Ballots.
The "'''Approval Ballot'''" is the official ballot for approving documents. For informal opinion polling, NENA Workspace provides what it calls a "'''Ballot'''". This is a less formal but more flexible ballot for identifying the preferences of group members.
 
==How Issues are Processed==
This table describes the primary differences between the two ballot types and how they are used in [https://www.nena.org/page/NENAOrgStructure ADM-001 NENA Development Group Organizational Structure and Operational Procedures]:
====Issue Processing Flow Chart====
 
{| class="wikitable" style="border:#c9c9c9 1px solid; margin: 1em 1em 1em 0; border-collapse: collapse;" cellspacing="0" cellpadding="4" {{table}}
| align="center" style="background:#f0f0f0;"|'''''
| align="center" style="background:#f0f0f0;"|'''Approval Ballot'''
(Formal Ballot)
| align="center" style="background:#f0f0f0;"|'''Ballot'''
(Informal Ballot)
|+ NENA Workspace Ballot Type Comparison
|-
| Who can create the ballot? ||Committee Resource Manager (CRM), Working Group Chair or Committee Chair||Committee Resource Manager (CRM), Working Group Chair or Committee Chair.
|-
| Who can vote?||Officially designated voters as defined in [https://www.nena.org/page/NENAOrgStructure NENA-ADM-001]. The [[Consensus Body]] for NENA document approvals are the designated voters of authoring Working Group. ||Configurable:
 
* Anyone on the roster.
* Officially designated voters.
|-
| How to select in Workspace?||
# Select "Documents" in the left menu.
# Navigate to the document requiring approval.
# In the "Edit" drop-down menu, select "Create Approval Ballot."
# Complete the form(s).
|
# Select "Ballots" in the left menu.
# Click on the green "Add" button.&nbsp; (Not the drop-down arrow).
# Complete the form(s).
|-
| Answer Options||Restricted to "Yes"/"No"/"Abstain"||Flexible, Multiple Choice
|-
| Can ballot be used to determine consensus?||Yes.||No
|-
| When '''must''' the ballot be used?
|
On all document approvals at the Working Group level to move the document to next step. Approval Ballots are a required step for ANS (American National Standard) document approval process.
|Not required.
|-
| When '''should''' the ballot be used?
|
* When consensus on a document issue or disputed text is required and it is possible that the consensus on a call may not be representative of the consensus of the entire group.
* Deciding on whether or not to accept disputed responses to review comments.
|
* To sample the entire group's opinion.
* To get the group's preferences in choosing from multiple options.
* To get opinions on non document-related issues.
|-
| Is there a minimum required participation?||Yes, 50% of approved voters must vote for a valid decision on approval. A vote may be "Yes," "No." or "Abstain."||For "important" questions, 50% of approved voters must vote for a valid decision on approval.
For "trivial" questions, participation levels may be ignored.
|-
|What happens if participation does not reach 50%?
|If 50% participation is not reached, the ballot should be [[Recirculation Ballot|recirculated]] so that voters who have not voted may vote, and voters may change their vote. Otherwise, existing votes remain valid. Participation may be increased by encouraging members to use the "Abstain" option and by removing members who do not participate.
|Discretion on accepting ballot results and participation level is left to the ballot originator with consideration given to the importance of the ballot.
|-
| What is threshold of "Yes" votes to indicate consensus and approval?||2/3 of those who vote.||Consensus is not determined using an Informal Ballot.
|}
 
== How Issues are Processed ==
==== Issue Processing Flow Chart ====
This diagram is a summary of the steps for processing an Issue.<br /><br />
The colors of the elements in the chart indicate the group responsible for the activity.
Line 395 ⟶ 375:
The Issue being identified may be:
 
* A totally new topic, not related to any existing Issue or ongoing NENA work activity, or
* Associated with, or an extension of, a current Issue, or
* Associated with, or an extension of, a previously resolved Issue, or
* Associated with an existing NENA document, or
 
* Associated with a NENA document still under development.
 
If input of this nature arrives outside of a NENA Issue Submission & Charter Form ISF) (NENA-ADM-003) and it requires substantive action by an NDG Committee/entity, such input will be encapsulated within an NENA-ADM-003 form by the Committee Resource Manager (CRM) before it is processed by the DSC as described below. If the DSC determines the content does not constitute what NENA considers to be an “Issue”, the matter will be rejected through the most expedient means available (e.g., email, phone call to the submitter). If necessary and applicable, the action taken can be handled through a NENA-ADM-005 External Liaison form to provide a history of the action(s) taken by NENA in response to the input.
Line 406 ⟶ 386:
The following steps shall be followed when submitting an Issue. For details refer to NENA Development Group Guide.
 
==== Step 1. Originator Completes ISF ====
Originator completes a NENA Issue Submission & Charter Form (ISF) (NENA-ADM-003) and submits the completed Issue Form to the Committee Resource Manager (CRM).
 
* Originator may be any individual with a direct and material interest in the Issue, including NENA Members, or a ''Participant'' acting on their behalf or on behalf of a ''Participating Entity''.
* Issues that require expedited handling should be brought to the attention of the DSC Co-Chairs when submitted.
 
==== Step 2. Logging and DSC Leadership Review ====
The CRM logs the Issue into NENA Workspace (the Development Group collaboration website at <nowiki>httphttps://dev.nena.org</nowiki>) and sends a link to the DSC Leadership. The DSC Leadership will review the ISF to determine if it satisfies the following criteria:
 
* The subject matter is clearly defined via the NENA Issue Submission & Charter Form (ISF) (NENA-ADM-003).
* The issue is not intended to disrupt NENA processes defined in the NENA administrative documents.
* The subject matter is within the scope of the NENA Development Group
 
This review is not intended to judge the merits of the ISF content.
 
==== Step 3. NENA Development Group 10 business day review of ISF ====
The ISF will be released to all NDG members by the CRM for a 10 business day comment window to consider the following:
 
* Is NENA the most appropriate organization to take on the work?
* Is the requisite expertise available within the NDG?
* Is there an existing committee or working group that should take on the work?
* Is a new committee or working group needed?
* What should the scope and deliverables be?
* Is the issue intended to benefit any corporate or individual interest, or intended to frustrate competition?
* Is there is already an existing solution for the problem or opportunity, or the can the existing solution(s) be enhanced to gain efficiencies, (e.g., operational, policy, functionality)?
* Is the Issue of sufficient importance to justify resolving it within NENA?
* Will resolving the Issue provide benefit to the 9-1-1 Community as a whole?
* Are there sufficient resources available to resolve the issue without unduly affecting existing committed resources?
 
The DSC will consider these criteria along with submitted comments when deciding whether to accept or reject the issue and if accepted, to which committee it should be assigned.
 
==== Step 4. DSC Acceptance or Rejection of ISF ====
Within thirty (30) business days of the closing of the ten (10) business day review, the DSC will consider accepting or rejecting the Issue based on the acceptance criteria (see 0) and consideration of the comments received within the 10 business day review. &nbsp;Issues may be referred back to the originator for clarification before final decision on disposition can be completed. The originator is notified of the disposition of the Issue (accepted or rejected), and if it was rejected, the reasons for rejection. If the Issue is outside the scope of the NENA Development Group but still internal to NENA, the Issue may be referred accordingly, and the submitter will be so advised. The DSC will have no further responsibility for that Issue. The decision to accept or reject will be recorded in the minutes of a DSC meeting, entered into the Issue status pages by the CRM and added to the ISF.
 
==== Step 5. DSC Suggests Scopes, Timelines, Deliverables in NENA-ADM-010 Issue Tracking Form and Assigns Issue to Committee. ====
The DSC determines which existing Development Committee is best suited to work accepted Issues. The originator’s recommendation, the NDG review comments, and any DSC suggested scopes, timelines & deliverables. The DSC will determine, and the CRM will populate the applicable fields in NENA-ADM-010 (e.g., the desired due date etc.), and use it as a hand-off to the assigned NDG Committee.
 
==== Step 6. The Assigned Committee and Working Group completes NENA-ADM-011 Charter. ====
Prior to any Working Group meeting being scheduled, the assigned Development Committee Co-Chairs in consultation with their existing Working Group Co-Chairs must complete the Charter (NENA-ADM-011) by establishing scope, intermediate milestones and estimated times for both intermediate milestones and Final Deliverables. The completed Charter is to be returned to the CRM within 30 business days. Any comments received prior to accepting the issue should be considered during the development of the charter. The CRM will share the completed ISF, including Charter, with the assigned Committee members and DSC. The assigned Committee should make an assessment if it has members with sufficient expertise and willingness to advance the work, and if these members constitute a broad enough population to achieve openness and balance.&nbsp; If the committee doesn't feel this to be the case, it may either attempt to recruit new members to progress the issue or return the issue to the DSC for reevaluation.
 
The initial WG meeting shall review the Charter provided and provide any feedback to the Committee leadership so intentions are known, and overall Committee development schedules can be recognized and managed as necessary. The schedules shall be reviewed between the Working Group and Committee leadership periodically so there may be an early warning of any jeopardy relating to the schedules. Monthly WG status updates are to be provided via NENA-ADM-006, Scopes and Goals to the Development Committee Co-Chairs so they may submit a monthly report to the CRM of all Committee activities.
 
Because volunteer time for both leaders and members is limited, and the development needs are often large, the DSC shall establish development priorities across the NENA effort. Recommendations may be set to assign priority to specific development areas at both the WG level and, in some cases, the subject areas within WGs.&nbsp; These priorities shall be communicated to the WG Co-Chairs in order to assist them in managing workload. WG leaders and volunteers who are members of more than one WG are expected to self-manage the application and balancing of their time according to these priorities. WG leaders shall communicate to the Committee leaders where matters arise relating to WG membership conflicts (e.g., competing time slots for meetings).
 
==== Step 7. DSC Reviews NENA-ADM-011 Charter. ====
The DSC reviews the Working Group Charter.&nbsp; If approved, the CRM enters the approval date in the appropriate field of the ISF form and sends a copy of the updated form along with a hyperlink to the ISF to the originator. The applicable Development Committee Co-Chairs take responsibility for further oversight of the Issue until it is completed and provides status in the monthly Scopes & Goals report NENA-ADM-006.
 
==== Step 8. CRM Posts ISF & Charter ====
Upon acceptance of an ISF, the CRM will post the form to NENA Workspace and notify NDG membership via Workspace email. The CRM will also update the www.nena.org&nbsp; Committee page to reflect the associated WG, with a link to the ISF stored on NENA Workspace. Additionally, and where applicable, at the instruction of the DSC, the CRM will notify those organizations that may be impacted by or have an interest in the subject matter of the ISF, in accordance with ANSI Essential Requirements for Standards Development Notice.
 
Line 459 ⟶ 439:
When goals are achieved, the CRM closes the Issue and notifies the Orginator of the result.
 
=== Charter Updates ===
ISF Charter deliverables and objectives shall be reviewed by the Development Committee Co-Chairs frequently to keep the Working Group on track.&nbsp; In addition, intermediate milestones representing major accomplishments toward the end results shall be identified and documented. No major changes to Scope shall occur without review by the leadership of the Committee(s) (i.e. Development Committee Co-Chairs & DSC Co-Chairs. Any major changes in scope or due dates require an update to the Charter. The Working Group Co-Chairs shall return an updated Charter to the CRM for distribution to DSC for their approval.
 
=== Completion of ISF Deliverables ===
After the goals or deliverables have been completed or abandoned, the ISF shall be formally closed, the Working Group will be retired, and all ANSI required materials will be archived as appropriate. NOTE: Once a Working Group is retired, all approval process documentation that is handled by the CRM will archived on the NENA server by the CRM, and the “Group” (not the members) will be archived in NENA Workspace.
 
=== Issue Status Tracking ===
The CRM maintains a spreadsheet that tracks the status for every open Issue.
 
The spreadsheet will be available on the publicly accessible section of NENA Workspace at <nowiki>https://dev.nena.org/higherlogic/ws/public/documents?view</nowiki>.
 
== Forming a Working Group to Work an Issue ==
 
=== Completing the Charter ===
In initiating a new WG or a new subject within a WG, a clear definition of Charter, Scope and/or Mission shall be established in the beginning, to provide direction and end objective. This shall be reviewed frequently in order to keep the WG on track. In addition, intermediate milestones representing major accomplishments toward the end results shall be identified and documented. Minor adjustments to Scope can be made as perspectives evolve, but no major changes to Scope shall occur without review by the leadership of the Committee(s).
 
After Scope and Intermediate Milestones are established, the WG shall estimate the timeline for both intermediate milestones and the final deliverable. The Scope/Mission and timeline/date information shall be fed back to the Committee leadership so that intentions are known and overall Committee development schedules can be recognized and managed as necessary. The schedules shall be reviewed between the WG and Committee leadership periodically so that there may be an early warning of any jeopardy relating to the schedules.
 
Because volunteer time for both leaders and members is limited, and the development needs are often large, Committee and leaders of specific projects shall establish development priorities across the NENA effort. Recommendations may be set to assign priority to specific development areas at both the WG level and, in some cases, between subject areas within WGs. These priorities shall be communicated to the WG leaders in order to assist them in managing workload. WG leaders and volunteers who are members of more than one WG are expected to self-manage the application and balancing of their time according to these priorities. WG leaders shall communicate to the Committee leaders where issues arise relating to WG membership conflicts (e.g., competing time slots for meetings).
 
=== Recruiting Members ===
Once a working group is formed around a charter, the group's chair should recruit members with the skills and experience appropriate for the task.
 
In addition to specific subject matter experts, don't forget to recruit members with administrative skills needed to fulfill the roles of Document Editor and Note Taker.
 
* Document Editor. The editor edits text in the draft document and in contributions during a meeting to reflect the corrections, additions, and deletions that achieve consensus during a meeting. The editor also maintains the draft document and when contributions are accepted, updates the draft accordingly.
* Note Taker. The Note Taker keeps the minutes and attendance of all meetings. After the conclusion of a meeting, the note taker uploads the minutes of the meeting to the NENA Workspace folder for that group's minutes and also enters the attendance into the NENA Workspace meeting attendance page.
 
It is a good idea to also prepare other members to take over these roles when it is necessary to substitute. For these roles, subject matter expertise is not as important as administrative skills and reliable availability.
Line 491 ⟶ 471:
Here are several methods available for recruiting working group members:
 
* Contact the group's parent committee members. Initially, members can easily be recruited from the parent committee by using the NENA Workspace committee mail list.
* The parent committee chairs can forward an invitation to the other NENA committees through their representatives on the DSC.
* Group chairs who are members of other committees can email invitations directly to those committee members using the committee email list.
* Upon request, the CRM can send an invitation to all NDG members.
 
For every working group, a description of the working group is added to the committee's page on [https://www.nena.org/page/DevelopmentGroup nena.org]. The description should include the areas of expertise needed on the group and the group's normal call schedule so that prospective members can determine whether they should join.
== Managing NENA Documents ==
=== Document Types ===
The NENA Development Group publishes material and documents in five categories:
 
* Administrative Documents (ADM)
* Standards Documents (STA)
* Requirements Documents (REQ)
* Information Documents (INF)
* Reference Publication (REF)
 
===== Administrative Document (ADM) =====
NENA Administrative (ADM) documents describe the organizational structure of the association and its committees, establish the processes for document development and approval, and provide the appropriate forms to document committee work. ADM documents are developed and maintained by the Development Group Administrative Committee's Document Management Working Group and approved by the DSC and NENA Board.
===== Standard Document (STA) =====
NENA Standard (STA) Documents are published for the use of the public safety community. A NENA Standard is intended to describe methods, processes, and specifications that, if implemented as specified, should result in successful operation of the 9-1-1 emergency call and incident processing system and promote interoperability between interconnected systems. NENA Standards documents may be used by system developers, service providers, public safety agencies, regulatory authorities and others for the purposes of development, procurement, and management of 9-1-1 emergency call and incident processing products and services. Some NENA Standard documents may be published as American National Standards. See [[ANSI (American National Standards Institute)|ANSI (American National Standards Institute]]).
 
The NENA STA Template may be downloaded from the [https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079 Administrative Procedures & Templates Documents Page] on NENA Workspace.
 
===== Requirements Document (REQ) =====
NENA Requirements (REQ) documents are published as an information source primarily for use by industry stakeholders, NENA committees, and NENA working groups as guides for their development of NENA Standards. The contents of NENA Requirements documents are derived from a combination of the expressed needs of public safety agencies and the capabilities of the vendors of equipment and services. Requirements documents are not intended for use in development or procurement processes because their content does not include standard methods, processes, or specifications needed to support interoperability among the various 9-1-1 system elements.
 
The NENA REQ Template may be downloaded from the [https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079 Administrative Procedures & Templates Documents Page] on NENA Workspace.
 
===== Information Document (INF) =====
NENA Information (INF) documents are published to distribute information on a particular subject to the public safety community. Information documents may contain background information, best practices, check lists, and other material representing the collective knowledge and experiences of the NENA community. These documents may contain conditional normative statements to promote compliance with published NENA Standards but are not intended to be used to establish conformance requirements in development or procurement purposes. For example, a conditional normative statement might be "If you want to send emergency information to the NG9-1-1 system, you must conform to the provisions detailed in NENA-STA-010."
 
The NENA INF Template may be downloaded from the [https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079 Administrative Procedures & Templates Documents Page] on NENA Workspace.
 
===== Reference Publication (REF) =====
A NENA-authorized Reference Publication may consist of material in a variety of forms, including (but not limited to):
 
*NENA Knowledge Base Article
*Flyer
* White Paper
*Checklist
* Brochure
*NENA.org Web Site Content
*PowerPoint Presentation
* Video
*Microsoft Word Document
*PDF Document
 
For any of the publication formats above, The '''[https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079 Reference Material Tracking Form]''' is created as a companion document that contains important information about the published material such as the authoring committee, working group, hyperlinks to the material, approval date, etc. The title of the document includes the identification reference in the form NENA-REF-XXX.Y-yyyy. This identification reference, included somewhere in the published material, shows that the material is an officially authorized and approved NENA publication.
=== The Document Development Process ===
NENA documents are developed and approved using the processes described in NENA-ADM-001.
 
==== Process for STA, REQ, and INF Documents ====
The detailed steps for processing Standard (STA), Requirement (REQ), and Information (INF) documents are shown in this flow chart diagram:
[[File:Document Process by Step v39.png|200px|thumb|none|left|link=Process_Flow_Chart_for_STA,_REQ,_INF_Documents|Click to go to full sized drawing]]
<br />
 
==== Process for REF Material ====
The process for approving reference material was designed to reduce the time needed to publish non-standard material by removing some of the steps in the [[Process Flow Chart for STA, REQ, INF Documents|STA, REQ, and INF process]] completely or leaving some of the steps to the discretion of the [[DSC (Development Steering Council)]]. The detailed steps for processing REF material are shown in this flow chart diagram:
[[File:REF Material Process Flow Chart.png|200px|thumb|none|left|link=Process_Flow_Chart_for_Reference_(REF)_Material_(Draft)|Click to go to full sized drawing]]
<br />
==== Document Development Process in the Working Group ====
The Document Development Process and the flow chart show green Working Group steps for completing document drafts and processing comments that are received during the various review steps. The detailed steps for those working group processes are shown in this flow chart diagram:
[[File:WG_Process.png|200px|thumb|none|left|link=Working Group Process Flow Chart|Click to go to full sized drawing]]
 
=== Get the Current Template ===
If the working group is developing a Standard, Requirements, or Information document, the group's document editor will download a template that must be used in the production of any of those document types.<br /><br />
Reference material (REF) does not conform to a standard template because it may be in the form of a multimedia presentation (such as YouTube), web page, or other non-standard format.
 
The current versions of all templates are available for download from the '''[https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079?folder_id=129 Administrative Procedures & Templates & Training Material]''' page on [https://nenawikikb.nena.org/wiki/NENA_Workspace NENA Workspace]:<br />
 
[https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079/documents/document129/document?document_id=14425 NENA Template for Standard Document]<br />[https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079/documents/document129/document?document_id=16304 NENA Template for Requirements Document]<br />[https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079/documents/document129/document?document_id=16303 NENA Template for Information Document]<br />
 
=== Draft Executive Summary and Content Outline from Charter ===
One way to get started on a document is for the working group chair to prepare a draft of the Executive Summary and an outline for the content of the document. These would be based on the charter.
==== Present to WG for review, refinement, and consensus ====
Once the draft of the Executive Summary and outline is complete and distributed, the material would be reviewed and refined by the full working group on a conference call. Getting consensus on the Executive Summary and outline in the early stages helps guide the group through the process of dividing the work, getting contributions, and filling in the details.
 
=== Seek contributions ===
Working group chairs should seek contributions for identified topics from volunteers. When volunteers accept the assignment to provide a contribution, they should also agree to a time deadline for providing the contribution.
 
All submitted contributions should be uploaded into the Contributions folder in the working group's [https://nenawikikb.nena.org/wiki/NENA_Workspace NENA Workspace] library.
 
==== Contributions with graphics ====
Most contributions are text only. They may be submitted in any format that can be imported into a Microsoft Word document for review. If the contribution includes graphics or any other material that cannot be edited in Word, the source files such as Visio, PowerPoint, or any other application files used to prepare the material must also be uploaded. This is necessary to allow editors for the initial draft and future document reviews to edit the non-text material.
 
==== Seek volunteers first, then assign ====
In the event that there are topics that are not accepted by volunteers, they may be assigned to individuals at the discretion of the working group chair.
 
=== Review contributions ===
=== Complete Template Sections Including Acknowledgement Table ===
==== Prepare The Document Glossary ====
The templates for most NENA documents include a '''Abbreviations, Terms and Definitions''' table. Instructions for adding entries to the table are included in the templates. Please note that the '''Abbreviations, Terms and Definitions''' table is used as a source for terms that are selected for addition to the NENA Master Glossary and NENA Knowledge Base.
 
See [https://nenawikikb.nena.org/wiki/Main_Page#What_kinds_of_terms.2C_abbreviations.2C_and_acronyms_are_included_in_this_glossary.3F What kinds of terms and acronyms should be added to this glossary?] for guidelines on selecting the kinds of terms that should be considered for addition to this NENA Knowledge Base and to the NENA Master Glossary.
 
Terms may be added to the document's '''Abbreviations, Terms and Definitions''' table for the convenience of the document's readers and not necessarily be added to the NENA Master Glossary.
Line 592 ⟶ 572:
Do not create acronyms or abbreviations unless necessary. If there is an abbreviation that is specific only to your document, instead of creating yet another abbreviation, just spell it out.
 
==== Early Notification Process For New Terms or Definitions ====
When a Working GroupsGroup developdevelops a new term that they believe may be used by other Working Groups, this process is the method with which the proposednew term andor definition canmay be sharedsubmitted within the NDG groupan leadersISF before the document approvalcontaining processthe hasterm or new definition is approved and begunpublished.
 
'''Early Notification Resources:'''
*A folder in “00. All Group Leaders” on NWS is dedicated to this purpose.
The name of that folder is “Proposed MG Terms.” https://dev.nena.org/kws/groups/all-group-leaders/documents?folder_id=1928
*That NWS Folder is where proposals to add/modify/delete terms in the MG will be stored for sharing and approval, way ahead of when they would have otherwise been seen by anyone outside of the WG that came up with them.
*The [https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079/documents?folder_id=130 NENA-ADM-008] Agenda & Notes template includes a reminder line that will encourage meeting hosts to look to see if there’s anything in that folder that needs their attention. There is a link to the folder where such information would be if it existed. This ‘reminder’ step is similar to the Agenda line item that exists now to remind them to ask if there are any known conflicts.
 
'''How It Works:'''
*A WG Co-Chair or assigned delegate will send the proposed MG term change (add/change/delete) to the CRM via email. The email should be in the following format:
 
Subject: MG Proposal-Term (Abbreviation if applicable)
 
Email Body: The XXXXX WG is proposing to add/change/delete (select one) the following term from the MG:
 
TERM:
ABBREVIATION (if applicable):
 
PROPOSED DEFINITION:
 
Submitters Name, Email & Contact Number
 
*CRM receives the email and creates a document for uploading to NWS to be filed in “00. All Group Leaders” under the folder named “Proposed MG Terms.”
*This folder contains proposed MG terms that may affect other working group's document.
*The CRM will try to ensure the “Document Title” field is short enough that a quick glance by WG Co-Chairs will let them know if a term is applicable to their work or not.
 
When the file is uploaded by the CRM, a copy of the text will also be copied in the “Submitter Note” field. By doing this, the recipient will not be required to open the actual document, but they will be able to reply to the all-group-leaders@dev.nena.org NWS distribution list. When replying, DO NOT CHANGE THE SUBJECT as NWS will create a discussion list of all emails related to the subject term.
 
*The WG Co-Chairs will check the link when preparing the agenda and determine if any terms affect the group’s work.
 
*It remains possible that any proposed MG change could be reversed during the document’s approval cycles. This early notification concept simply meets the goal that was put forth during the 2017 JCM, to speed up the process of sharing proposed MG changes ahead of the formal approval cycles.
 
*The MG won’t be changed until the associated document is approved for publication by the Executive Board. But the WG that requested the change will know that there weren’t any objections from other WGs, and other WGs will know about the pending change, and can make use of it in their own work, if applicable.
 
*Once a new MG is published the draft proposed documents will be archived or deleted from the folder. The folder will only contain terms that are in documents that are being drafted.
 
=== Conducting Document Reviews & Comment Resolution ===
At several steps in the development process, documents are offered for review or an approval ballot. Both reviews and approval ballots can generate comments. Comments may be submitted in a variety of ways including a specific on-line comment page for the document in NENA Workspace. Comments can also be provided in uploaded versions of the document with comments and proposed edits added in a way that they can be identified. Often, that method uses Microsoft Word "tracked changes". Comments may also be submitted by email or any other method the commenter chooses.
 
Every comment, no matter how it is submitted, must be entered into the NENA Workspace "Comment Manager". The Comment Manager tracks the process by which the comment is received, reviewed by the working group, and the resolution communicated back to the comment submitter. The Comment Manager also captures the submitter's response to the working group's action.
 
When completing fields in the NENA Workspace Comment Manager, the field names should be interpreted as described in the [[Explanatory textHelp for the variousNWS Comment States and ResponsesResponse]].
 
== Reporting Status ==
'''Policy Issues'''<br />
 
Line 645 ⟶ 591:
WG members are expected to contribute ideas, text, and review effort toward the goals of the WG. If the WG leader(s) determine(s) that they are not receiving these contributions in a timely manner, they shall identify this issue to the Committee or Project lead teams as soon as possible. The lead teams will attempt to rebalance the efforts of existing volunteers and seek out new resources as appropriate.
 
== Participating in NENA events ==
 
Working Group chairs are expected to participate in scheduled NENA events such as the Joint Committee Meeting (JCM), NENA Standards and Best Practices (SBP) and the NENA Annual Conference. They may suggest appropriate session topics, help prepare the session presentation material, and may coordinate and present the material and moderate the session discussions along with other working group members.
Retrieved from "https://kb.nena.org/wiki/Special:MobileDiff/6553...7364"