INCITS/RD-5, Project Proposal Guide (07/05)

Foreword

This document defines the information to be submitted INCITS by any person, organization, or group as a proposal to initiate a project to develop a new or revised INCITS standard or technical report.

The person, organization, group, or INCITS Technical Committee initiating a standard development project proposal is asked to provide, in as complete a manner as possible and practicable, the information indicated for each of the Format Sections 1 through 4. If supplementary material is required for presenting the proposal as a recommendation to INCITS to pursue the activity, this will be supplied by INCITS, an INCITS Technical Committee, or a Study Group.

Proposals should be submitted to:

INCITS Secretariat/ITI
ATTN: Associate Director, Standards Operations, INCITS
1250 Eye Street, N.W - Suite 200
Washington, D.C. 20005
Email:   incits@itic.org

with a copy to the Associate Manager, Standards Operations, assigned to the INCITS/TC

Study of the proposal may be undertaken by INCITS acting as a committee of the whole, or be assigned by INCITS to an appropriate INCITS Technical Committee or to an ad hoc Study Group of experts representing the communities of interest in the subject matter of the proposal and appointed for the purpose. During the review and in developing the recommendation, the proposal will be examined to determine whether:

In preparing the recommendation, the definition of the standard development project in the original proposal may be augmented or modified. If the recommendation is that no INCITS activity be undertaken, reasons for this decision will be appended. It must be kept in mind that INCITS recommendations are based on current judgment, and reconsideration of proposals may be appropriate in the event of changes in the conditions examined during the review.

The time and effort expended in the preparation of a well-researched and well-documented proposal will generally reduce that required in the development of the recommendation and ultimately, accelerate realization of the standards development desired.


Format for Proposal for Project to Develop
A New or Revised Standard or Technical Report

1. Source of the Proposed Project

1.1 Title
1.2 Date Submitted
1.3 Proposer(s)
2. Process Description for the Proposed Project
2.1 Project Type (Development or Revision)
2.2 Type of Document
2.3 Definitions of Concepts and Special Terms
2.4 Expected Relationship with Approved Reference Models, Frameworks, Architectures, etc.
2.5 Recommended INCITS Development Technical Committee (Existing or New)
2.6 Anticipated Frequency and Duration of Meetings
2.7 Target Date for Initial Public Review (Milestone 4)
2.8 Estimated Useful Life of Standard or Technical Report
3. Business Case for Developing the Proposed Standard or Technical Report
3.1 Description
3.2. Existing Practice and the Need for a Standard
3.3. Implementation Impacts of the Proposed Standard
3.3.1 Development Costs
3.3.2 Impact on Existing or Potential Markets
3.3.3 Costs and Methods for Conformity Assessment
3.3.4 Return on Investment
3.4 Legal Considerations
3.4.1 Patent Assertions
3.4.2 Dissemination of the Standard or Technical Report
4. Related Standards Activities
4.1 Existing Standards
4.2 Related Standards Activity
4.3 Recommendations for Close Liaison
5. Units of Measurement used in the Standard


Explanatory Text Follows:

1. Source of the Proposed Project

1.1 Title
Provide a descriptive subject matter title.
1.2 Date Submitted
The date should be the date of submission of the proposal to the INCITS Secretariat.
1.3 Proposer(s)

If the proposer is not an existing INCITS TC, identify the individual who will serve as the acting chairman until a new TC has been established.

2. Process Description for the Proposed Project
2.1 Project Type (Development or Revision)
Indicate "D" if DEVELOPMENT will be done within an INCITS Technical Committee and the expected result is an ANSI standard.

Indicate "DT - A" if the project proposal describes a proposed ANSI technical report;

Indicate "DT - N" if the project proposal describes a proposed INCITS technical report.

Indicate "R" if the project proposal describes a proposed REVISION to a standard or technical report.

2.2 Type of Document
Specify the type of document to be developed (standard or technical report).
2.3 Definitions of Concepts and Special Terms
Provide definitions of key concepts and special terms (if any) needed in developing and understanding the document.
2.4 Expected Relationship with Approved Reference Models, Frameworks, Architectures, etc.
Identify relevant reference models, frameworks, architectures, etc., that are being used to conceptualize the relationships among the various information technologies and this project, and any known or anticipated areas of conformance or conflict.
2.5 Recommended INCITS Development Technical Committee
Indicate a preference for assignment of the proposed project to a particular existing Technical Committee, or propose creation of a new INCITS TC. Creation of a new TC must include the rationale. Include a description of available resources -- at least four individuals and organizations competent and interested in the subject matter --to assure that adequate resources exist to accomplish the proposed program of work. Indicate which are members of INCITS.
2.6 Anticipated Frequency and Duration of Meetings
Estimate of the anticipated frequency and duration of meetings.
2.7 Target Date for Initial Public Review (Milestone 4)
Estimate the target date for releasing the draft document for public review (described as Milestone 4 in section 5.1 of the INCITS/RD-2, Organization, Rules and Procedures.).
2.8 Estimated Useful Life of Standard or Technical Report
Estimate the useful life of the document.
3. Business Case for Developing the Proposed Standard or Technical Report
3.1 Description
Describe the technical information that will be covered by the document.
3.2 Existing Practice and the Need for a Standard
Identify why a standard is needed, rather than another kind of solution.

Describe existing practice in the area of a proposed document to aid in judging timeliness and appropriateness of the project.

Address the expected stability of the proposed document with respect to both current technology and potential technological advances.

3.3 Implementation Impacts of the Proposed Standard
This section addresses the potential impacts of the proposed standard. To the extent possible, the proposer is requested to address the following implementation considerations:

3.3.1 Development Costs

Provide an overall estimate of the technical development costs for this standard.

Include labor costs for technical editor(s), logistical costs for meetings, work between meetings, and any other significant costs.

3.3.2 Impact on Existing or Potential Markets
Provide a cost/benefit statement (qualitative or quantitative) on the impact on users and suppliers, should this standard be implemented.

Describe any potential markets (using publicly-available economic data from security analysts, market trend or venture capital reports, etc.), should this standard be implemented.

3.3.3 Costs and Methods for Conformity Assessment
What testing environment is appropriate for this technology (e.g., suppliers' declaration, accreditation of testing laboratories, certification bodies)? Will this standard contain the necessary and sufficient testing information for assessing conformity to this standard? If not, how will this information be developed, and what are the associated development costs?
3.3.4 Return on Investment
What is the estimated ROI for development of this standard and the conformity assessment costs associated with it?
3.4 Legal Considerations
3.4.1 Patent Assertions
Calls will be made to identify assertions of patent rights in accordance with the relevant INCITS, ANSI and ISO/IEC policies and procedures. Is the proposer aware of any patent assertions that may be made? If so, describe.
3.4.2 Dissemination of the Standard or Technical Report
Drafts of this document will be disseminated electronically. Dissemination of the final standard will be as the document becomes the property of INCITS, ANSI, or ISO/IEC. Is the proposer aware of any IPR assertions that will hinder this distribution? If so, describe
4. Related Standards Activities
4.1 Existing Standards
Identify existing standards (including but not limited to INCITS, ANSI, and ISO/IEC/JTC1) that may affect or be affected by the proposed project.
4.2 Related Standards Activity
Identify projects under development (including but not limited to INCITS, ANSI, and ISO/IEC/JTC1) that may affect or be affected by the proposed project. For each project identified, indicate if the liaison arrangements have been made with these activities.
4.3 Recommendations for Close Liaison
Recommend which INCITS subgroups should be identified as close liaisons.

[Close liaisons require an exchange of information, but the work of one is not dependent upon the work of the other.]

5. Units of Measurement used in the Standard
Indicate units of measurement used in the Standard: