Submission Form -- Justice Standards Registry

Fill in the blanks (you can hit the "tab" key to move between fields) and press the "Validate Data" button at the bottom when finished.

Also, see the Standards HELP.
Here is a tutorial of the process. (Currently in Word format) tutor1.htm    tutor2.htm
previously submitted Standard information using Retrieval Code: .
1. Standard Category:
a. Development stage:    or Other: .
b. Area or category/type of standard:

2. Current status of project:
(Note: a standard may be withdrawn by the submitter or the developer.)

3.
Brief Description of Standards Process Status:


4. Standard Title (proposed):

5. Standard Date: Month: Year:
6. Standard Version Number:
7. Application Number: (To be supplied later).

8. Author Contact information:
Organization Name:
Contact Name: (e.g., John Q. Smith)
Street Address1:
Street Address2:
City:     State:           Zip: -
Bus./Day Phone: Ext: (e.g., 303-497-3375)
Fax Number: (not required)
E-mail Address:
URL:

9. Developer Contact information:
Organization Name:
Contact Name: (e.g., John Q. Smith)
Street Address1:
Street Address2:
City:     State:           Zip: -
Bus./Day Phone: Ext: (e.g., 303-497-3375)
Fax Number: (not required)
E-mail Address:
URL:

10. Sponsor Contact information:
(Sponsor must be a government organization or agency.)
Organization Name:
Contact Name: (e.g., John Q. Smith)
Street Address1:
Street Address2:
City:     State:           Zip: -
Bus./Day Phone: Ext: (e.g., 303-497-3375)
Fax Number: (not required)
E-mail Address:
URL:

11. Submitter Contact information:
Organization Name:
Contact Name: (e.g., John Q. Smith)
Street Address1:
Street Address2:
City:     State:           Zip: -
Bus./Day Phone: Ext: (e.g., 303-497-3375)
Fax Number: (not required)
E-mail Address:
URL:
If you know the name, phone number, web address, or e-mail address where the standard being proposed for this database may be obtained, please type it below:


12. Level of Urgency:

13. Keywords (Choose all that you think apply) :
Functional Requirements.
Functional Standard.
User Requirements.

Data Model.
Network Architecture.

Data Storage Model.
Data Warehouse Model.
Data Query Model.
Data Exchange Model.

Data Exchange Language.
Data Transmission Language.
Data Query Language.

Data Transport Mechanism.
Communication Protocol.

User Interface.
User Access.
Transport Interface.
Common Air Interface.

Data Representation.
Data Element.
Data Dictionary.

Data Integrity.
Security.
Encryption.
Privacy.
Authentication.
Authorization.

Prototype Implementation.
System Testing.
Network Validation.

Others (specify).

14. Overview of Standard Proposed for the Registry
 15.
Brief Description of Standard (i.e., abstract):

16.
Target Audience of Standard (check all the boxes that apply) :
Law enforcement.
Corrections.
Courts.
Prosecution.
Public Defender.
Probation/parole.
Victim Services.
Fire.
EMS.
Transportation.
Public Works.
Others (specify).

17.
Benefits of Standard (Check boxes below and/or fill in other benefits) :
Enables or promotes database sharing and/or information sharing.
Enables or promotes compatibility of air interface [e.g. enabling radio communication].

18.
Impact of Standard on information sharing/exchange and user community
Allows users to share databases more easily.
Allows multi-agency users to communicate via radio.
Allows rapid coordination of multi-agency effort [e.g. rescue].

19.
Relationship, if any, to existing recognized or proposed standards:

20.
Describe need/use for Standard:

21.
Implementation plan/schedule:

22. Description of Proposed Standard Development Process
 23.
Practitioner participation/inclusiveness (check all the boxes that apply) :
Law enforcement.
Corrections.
Courts.
Prosecution.
Public Defender.
Probation/parole.
Victim Services.
Fire.
EMS.
Transportation.
Public Works.
Others (specify).
24.
Description of face-to-face (or electronic--teleconferencing or E-mail) meetings held during development:
Scheduled, open meetings were held with interested parties.
E-mail discussions were fairly conducted among all interested parties.
Number of meetings held (approx.)

25.
Review and comment by affected organizations:
26.
Endorsements:


27. Technical Issues
Is patent/proprietary technology required to use the proposed standard?   Yes     No
28.
Commercial support for Proposed Standard or Current users of Proposed Standard:


29. Would you like entire text of your standard posted on our web site?
Yes
No, just the title, keywords, source, and abstract

30. Set Retrieval Code:    

Appendix:


Help (Validates that required data fields exist and saves data to a file.)
Send any questions/comments/problems to Greg Hand, Email: gh@its.bldrdoc.gov Phone:303-497-3375