SMPTE   AG   19
Administrative Guideline

Project Status Values

Approved: 2023-03-21

Copyright Β© 2023 , Society of Motion Picture and Television Engineers . All rights reserved. No part of this material may be reproduced, by any means whatsoever, without the prior written permission of the Society of Motion Picture and Television Engineers.


Table of contents πŸ”—

  1. Foreword
  2. 1 Scope
  3. 2 Conformance
  4. 3 Normative references
  5. 4 Terms and definitions
  6. 5 Projects
  7. 6 Project Completion States
    1. 6.1 Overview
    2. 6.2 Project States for ST, RP & EG documents
    3. 6.3 Project States for RDD documents
    4. 6.4 Project States for ER documents
    5. 6.5 Project States for TSP documents

Foreword πŸ”—

The Society of Motion Picture and Television Engineers (SMPTE) is an internationally-recognized standards developing organization. Headquartered and incorporated in the United States of America, SMPTE has members in over 80 countries on six continents. SMPTE’s Engineering Documents, including Standards, Recommended Practices, and Engineering Guidelines, are prepared by SMPTE’s Technology Committees. Participation in these Committees is open to all with a bona fide interest in their work. SMPTE cooperates closely with other standards-developing organizations, including ISO, IEC and ITU. SMPTE Engineering Documents are drafted in accordance with the rules given in its Standards Operations Manual.

For more information, please visit www.smpte.org .

This Standards Administrative Guideline forms an adjunct to the use and interpretation of the SMPTE Standards Operations Manual. In the event of a conflict, the Operations Manual shall prevail.

1 Scope πŸ”—

This Administrative Guideline describes the tracking of project completion so that consistent progress can be measured between projects, between document types and between TCs

This Administrative Guideline is intended to help manage SMPTE Projects.

2 Conformance πŸ”—

The following keywords have a specific meaning in the context of this document:

3 Normative references πŸ”—

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

4 Terms and definitions πŸ”—

For the purposes of this document, the terms and definitions given in the following documents apply:

5 Projects πŸ”—

General rules for Projects:

  1. For every SMPTE document being worked on, there should be a SMPTE Project associated with that document
  2. Work that requires multiple documents should have a parent project that references all child projects for the documents being worked on. TC Chairs may rule that a parent project is not needed.
  3. At the discretion of the Technology Committee, a Sub Group may be allocated one or more projects (see SMPTE Standards Operations Manual ).

6 Project Completion States πŸ”—

6.1 Overview πŸ”—

The states given below relate to the definition of the document states for different document types in the SMPTE Standards Operations Manual or in SMPTE AG-22 . The trigger(s) for transition to another state are given in italics in parenthesis.

NOTE 1 —⁠ In all cases, the project chair is responsible for updating the project completion state where the state less than or equal to 90%. HQ updates the state above 90%.

NOTE 2 —⁠ DP vote comments and ST Audit comments are actually late comments on an FCD ballot and the Project Chair should determine the status according to whether such comments are to be addressed or deferred according to the SMPTE Standards Operations Manual .

6.2 Project States for ST, RP & EG documents πŸ”—

6.3 Project States for RDD documents πŸ”—

6.4 Project States for ER documents πŸ”—

6.5 Project States for TSP documents πŸ”—