Appendix: Examples of Records

Examples of Records test

Component Record

Section A. Record Information

1. Record #: This is a static field that cannot be changed. The record number is automatically generated by the system upon completion of all required fields and after you click on the Add Record button.

2. Primary Committee Responsible: This field displays the committee responsible for the record. This committee was selected on the Staff Tab when the component record was first opened. Note: The field becomes dynamic, and can be updated, once the record has been created.

3. Record Level: This field indicates the current level of approval for a record.

This field determines the record access rights for Staff, Volunteers, and Project Managers.
The Record Level is initially generated based on the Primary Committee Responsible for the record, and automatically updates as a record moves through the balloting process.
It can also be manually updated as needed.

4. Record Sub-Type: This field indicates the appropriate sub-type for the record: Administrative, Awards, Conformity Assessment Matters, Errata, Object & Scope, Reaffirmation, Revision, White Paper. Revision is the default subtype. Note: The Conformity Assessment Matters sub-type is only available to some staff.

Committees Involved in this Record

5. Board: Select the supervisory Board(s) to which the Standards Committee (item A.6) reports from the provided list. Note: Some Standards Committees report to more than one Board (e.g. QEI), in such cases select both boards.

6. Standards Committee: Select the Standards Committee associated with this record.

7. Sub-Tier Committee: Allows you to select any additional Committee(s) in the system that may be asked to review, develop or vote on the proposal. The selected Committee(s) will be listed on the record once it has been created. Note: This field is beneficial as a search aid but is optional.

Additional Fields (Appear after a record is created)

8. Record Established: This field is automatically updated through C&S Connect and displays the date when the new record was created.

9. Last Updated By: This field is automatically updated when the record is updated. The Project Manager or staff who last revised the record is indicated in this field.

10. Last Updated On: This field is automatically updated when the record is updated. The date when the record was last revised is recorded here.

Section B. Record Description

Subject: This field is required to open a record, and is used to identify the applicable standard. It should be updated if the subject description becomes inaccurate or incomplete. The recommended identification of record should be as follows: Standard Designator (e.g. QEI, A17, B31.1, etc.), followed by applicable Part(s)/Section(s)/Article(s)/Chapter(s)/ Appendix(ces), and followed by applicable Paragraph(s)/Figure(s)/Table Number(s). The edition year may be needed. Paragraph/Figure/Table headings or other “key” words are recommended.

Examples:

CSD-1 Part CE, CE-130 Motors
B31.8 Chapter III, Table 832.2 Thermal Expansion of Carbon and Low Alloy Steel
A17.1, Figure 2.16.1.1 Inside Net Platform Areas for Passenger Elevators
PVHO-1 Nonmandatory Appendix C, C-3.2 Threaded Insert Couplings
B31.1, Para. 111.2.3 and 127.4, Undercut Rules

Proposal: This field represents the action being taken through this record. Typically the action is described by one of the following verbs: Revise, Update, Delete, Edit, Correct, Add, Renumber, etc.

Examples:

Revise protection requirements under CE-130(c)
Update Table 8.32.2 with new values
Correct area equation shown in Figure 2.16.1.1
Delete current requirements in C-3.2 and Renumber existing requirements

Explanation: This field is used to input Rationale/Explanation of the revision. It should include some or all of the following:

Technical explanation of the proposal and/or existing requirements.
Action intended to accomplish.
Detailed description of the changes / additions / deletions to the text.

Examples:

Current motor protection requirements in CSD-1 have been found to be too restrictive, and have not been validated by engineering calculations. Experience has shown that a decrease in x will not affect the safety or the life of the motor. The requirements are being revised accordingly.
Table T-1411-1 will be changed to make a distinction between elastic and inelastic analysis and restore the value of K' to its original value of K' = 0.9. About 20 years ago the value of K' was changed from 0.9 to the more conservative value of 0.67 without a distinction between elastic and inelastic analysis. Subsequent studies have shown that the increased conservatism was not warranted for elastic analysis.

Summary of Changes: The information provided in this field will be a restatement of the proposal and explanation, without associated technical background or rationale. This information is provided for the benefit of code users and is published as the Summary of Changes that accompanies most new addenda and editions. This field is required by BPVC for errata and revisions. Use of this field is optional but recommended because the information is required for publication.

Notes:

The Summary of Changes is meant to provide a brief high-level description of the changes that will be apparent to the Code user upon reviewing the published action.
The Summary of Changes should be composed in past tense. An effective Summary of Changes statement will be a restatement of the proposal and explanation, without associated technical background or rationale.
The Summary of Changes may be structured as follows, when appropriate:
- Restatement of action (from Proposal), e.g. “adopted”, “revised”, “deleted”, “moved”, “annulled”, etc.
- Affected text, e.g. paragraph, table, etc. (from Proposal).
- Purpose, e.g. “...in order to clarify, correct, update, reformat, reflect / correlate…”

Examples:

Note (22) added to Table KCS-1 for SA-723, Class 3 materials.
XII Paragraph TF-410.4 revised to add S20100 and S20400 PFHT requirements.

Section C. File Attachments

Proposal File: This field MUST contain the most recent (latest) version of the proposal/document/revision to be reviewed during the consensus process.

Notes:

The proposal file should not contain material that is not subject to consensus approval. See background material and committee correspondence fields described below.
It is essential that the correct revision file is attached to the record before it is added to a ballot because the file cannot be revised while the record out for ballot.
Once a new file is uploaded, it is automatically labeled as Current Proposal File, and the previous file is automatically archived.
Archived files contain three description fields: size, date posted, and posted by.
Staff secretaries no longer have access to deleting archived files.
The Proposal file can be viewed under the “Proposal” section of a ballot.
The Project Manager or staff should use the most up-to-date version of the Code section when providing revisions.

Background Material: This field should contain a file providing background information for the record. Background information includes but is not limited to: Sample calculations, tables, figures, and any supporting information that is pertinent to the record.

Committee Correspondence: This field should contain committee correspondence pertaining to the proposal.

File Attachments: This section allows the Staff Secretary to upload the Proposal File and attach the file to the record. You can also upload a Background Material File and Committee Correspondence File.

Once the record is created, a View/Manage File Attachments button is added to the Update Component Record Form.

When the View/Manage File Attachments button is clicked, the File Attachment History for the record is opened in a new window.

Section D through F, Project Manager and Record Creator Fields

D. Project Administrative Manager:

1. Staff contact information is automatically determined based on the Primary Committee responsible (under A.2). This field contains the Staff Contact of the Primary Committee Responsible for the record or its hierarchy selected by the system.

2. Staff Notes: This field becomes available for update once the record has been created. The Project Manager can use this field to record miscellaneous details related to the proposal.

E. Record Creator:

This field is automatically generated by the system. It lists the name of the person who originally created the record.

F. Project Technical Manager:

1. Use this field to indicate the Project Manager for the record. This is usually the committee member responsible for the record (e.g. proposal developer or Committee Chair), and should be updated as needed.

2. Project Manager Notes: This field becomes available for update once the record has been created. The Project Manager can use this field to record miscellaneous details related to the proposal.

Section G. Sub-Tier Committee Level Fields

Original Inquirer Contact Information: This field can capture the contact information of the originator or requestor of the proposal. If you use this field, as a minimum include individual’s name and phone number or email at the minimum.
Project Team Name: If a Project Team was formed to develop the proposal, this field can record that Project Team's name.
Project Team Members: If a Project Team was formed to develop the proposal, this field allows you to capture the names of the Project Team members. Note: If members are not part of C&S Connect, it is recommended that e-mail addresses are included in this field.
Subcommittee Item History: This field can capture any relevant Subcommittee and/or Project Team history. The History can include notable events (and dates) within the consensus process of the record. Note: It is recommended that entries start with the date of occurrence for the notable event. Example: 02/15/13: Subcommittee approved item at their meeting.

Section H, Additional Subcommittee Information

Codes Affected by Proposed Revision: This field is available to indicate codes affected by the proposed revision.
Related Committee Records: Use this field to link other records that are affected by this record. To do so, click on the "Search Related Records" button, and enter the record number of any other records affected by the proposed revision. Mark the checkbox to add to record (see right column) and click the Link These Records button. This field may remain blank if no other records are affected.
Proposal Keywords: This field lists the keywords that can be used to describe the record. Select the appropriate keywords that best describe the record. This field may be left blank. Selecting a proposal keyword(s) allows BPV members to filter a Review and Comment ballot by keyword; when filtered the Review & Comment ballot will show only records containing the selected keyword.
Secondary Subcommittee(s) w/ Related Actions: This field is for proposals that require consideration by multiple Committees. It is used to identify any committee(s) that is/are required to take action on the proposed standards action. If the record requires consideration by more than one Committee, the Staff Secretary of the primary Committee associated with the record should select the applicable Secondary Committee(s).

The field has two components: “Pending Committees” and “Committees Responded”. These components are to be used as follows:

The Pending Committees column should contain all committee(s) required to take action. The committees must remain in this column until the required action is completed.
Note: The Staff Secretary of the primary committee responsible is responsible for identifying all the committees with related action.
The Responded Committees column should contain the committees that have completed the required action.
Delete current requirements in C-3.2 and Renumber existing requirements
Note: The Staff Secretary of any of the secondary committee(s) identified in this field is responsible for updating this column when the related action has been completed.

Additional Notes:

Action used in the description of the field refers to:

Conducting a Review and Comment of the proposal
Endorsing proposal
Approving proposal

Once the required action is completed, the Staff Secretary of the secondary committee typically documents it under the Subcommittee History field.
This field is currently ONLY being used by BPV Code committees.

Type (Nuclear Only): This field is only used by BPV-SCXI. Select one of the following options from the drop-down menu:

· CCI: Code Case Incorporation

· COR: Clarification of Requirements

· INT: Implementation of New Technology

· IS: Increased Scope

· SOR: Simplification of requirements

· M: Maintenance such as updating to later editions of referenced documents.

· S-H: Safety (high)

· S-N: Safety (normal)

· RRE-H: Reduced Radiation Exposure (high)

· RRE-N: Reduced Radiation Exposure (normal)

· RB-H: Reduced Burden (high)

· RB-N: Reduced Burden (normal)

· M-H: Maintenance (high)

· M-N: Maintenance (normal)

Text of Subordinate Group Negatives: If required by the Committee supplemental procedures, this field captures the text of unresolved Sub-Tier Committee negatives to be reported to the Consensus Committee. In the event when there are no unresolved negatives, the term “None” should be entered.

Note: This field can be left blank if the Committee supplemental procedures do not require this documentation. It is useful for recorded voice votes at meetings.

Subordinate Group Action Date: If required by the Committee supplemental procedures. This field should contain the date the proposal was acted on by the subordinate group.

Section I. Additional Standards Committee Information

Standards Committee Description 1: This field is used only by BPV committees. It provides necessary details of any Standards Committee’s action taken at a meeting (not covered under item H.2 and H.3.), and should be updated as needed.

Standards Committee Action 1: This field is used only by BPV committees, and should be updated as needed. Choose an option from drop down menu that best reflects information contained in field I.1.

Committee Action Date 1: This field is only for BPV Standards Committee usage and should be updated as needed to reflect the date of Standards Committee action described under I.1 and I.2.

Standards Committee Description 2: This field is used only by BPV committees. It provides necessary details of any Standards Committee’s action taken at a meeting (not covered under item H.5 and H.6.), and should be updated as needed.

Standards Committee Action 2: This field is used only by BPV committees, and should be updated as needed. Choose an option from drop down menu that best reflects information contained in field I.4.

Committee Action Date 2: This field is only for BPV Standards Committee usage and should be updated as needed to reflect the date of Standards Committee action described under I.4 and I.5.

Addenda/Edition Year: This field is used to identify applicable Addenda/Edition year when the record proposal file is to be published. It is typically updated once the record has received Standards Committee approval. However, it should be further updated if the target publication date changes.

Entire Document Record

Section A. Record Information

3. Record Level: This field indicates the current level of approval for a record.

This field determines the record access rights for Staff, Volunteers, and Project Managers.
The Record Level is initially generated based on the Primary Committee Responsible for the record, and automatically updates as a record moves through the balloting process.
It can also be manually updated as needed.

Committees Involved in this Record

6. Standards Committee: Select the Standards Committee associated with this record.

Additional Fields (Appear after a record is created)

8. Record Established: This field is automatically updated through C&S Connect and displays the date when the new record was created.

9. Last Updated By: This field is automatically updated when the record is updated. The Project Manager or staff who last revised the record is indicated in this field.

10. Last Updated On: This field is automatically updated when the record is updated. The date when the record was last revised is recorded here.

Section B. Record Description

Project Intent (relates to the status of the standard in terms of ANSI only, e.g., any Standard that is not an approved ANS, is a new standard): This field relates to the status of the Standard in terms of ANSI only. Select from the drop down menu. The options are:

· Adopt identical ISO or IEC standard

· Adopt modified ISO or IEC standard

· AND this adoption revises this current ANS

· Revise current ANS

· Revise and redesignate current ANS

· Revise, redesignate and consolidate current ANS

· Revise and partition current ANS

· Reaffirm current ANS

· Reaffirm and redesignate current ANS

· Addenda to current ANS

· Supplement to current ANS

· Maintain ANS under stabilized maintenance

· Withdraw current ANS

Supersedes or Affects: This field is used to enter the complete designation of approved ANSI standard(s) associated with this record. Example: B1.1-2001 (R2007)

Designation of Proposed Standard: This field is used to enter the Standard’s designation. Example: B1.1 (Do not place year here)
Notes:
- If the proposed action is a reaffirmation, select “R” for reaffirmation.

Title of Standard: This field is used to enter the complete and exact title of the Standard as it is intended to be published. Example: Pipe Threads, General Purpose (Metric).

Scope Summary: This field is used to enter the scope of the Standard being submitted for consideration.

Section C. File Attachments

Proposal File: This field MUST contain the most recent (latest) version of the proposal/document/revision to be reviewed during the consensus process.

Notes:

The proposal file should not contain material that is not subject to consensus approval. See background material and committee correspondence fields described below.
It is essential that the correct revision file is attached to the record before it is added to a ballot because the file cannot be revised while the record is linked to an opened ballot.
Once a new file is uploaded, it is automatically labeled as Current Proposal File, and the previous file is automatically archived.
Archived files contain three description fields: size, date posted, and posted by.
Staff secretaries no longer have access to deleting archived files.
The Proposal file can be viewed under the “Proposal” section on the ballot form.
The Project Manager or staff should use the most up-to-date version of the Code section when providing revisions.

2. Background Material: This field should contain a file providing background information for the record. Background information includes but is not limited to: Sample calculations, tables, figures, and any supporting information that is pertinent to the record.

3. Committee Correspondence: This field should contain committee correspondence pertaining to the proposal.

4. (Update Record ONLY) View/Manage File Attachments Button: Opens the File Attachment History for the record in a new window. This section allows users with access to update the file attachments, as needed. If there are previous versions of any of the file attachments, all users can access those files here.

Section D through F, Project Manager and Record Creator Fields

D. Project Administrative Manager:

1. Staff contact information is automatically determined based on the Primary Committee responsible (under A.2). This field contains the contact information for the Staff Secretary of the Primary Committee Responsible for the record.

2. Staff Notes: This field is available to the Staff Secretary to record miscellaneous details related to the proposal which are not included within the item history fields (see G.4, I.1 and I.4).

E. Record Creator:

This field is automatically generated by the system. It lists the name of the person who originally created the record.

F. Project Technical Manager:

2. Project Manager Notes: This field becomes available for update once the record has been created. The Project Manager can use this field to record miscellaneous details related to the proposal.

Code Case Record

Section A. Record Information

3. Record Level: This field indicates the current level of approval for a record.

· This field determines the record access rights for Staff, Volunteers, and Project Managers.

· The Record Level is initially generated based on the Primary Committee Responsible for the record, and automatically updates as a record moves through the balloting process.

· It can also be manually updated as needed.

Committees Involved in this Record

6. Standards Committee: Select the Standards Committee associated with this record.

Additional Fields (Appear after a record is created)

8. Record Established: This field is automatically updated through C&S Connect and displays the date when the new record was created.

9. Last Updated By: This field is automatically updated when the record is updated. The Project Manager or staff who last revised the record is indicated in this field.

10. Last Updated On: This field is automatically updated when the record is updated. The date when the record was last revised is recorded here.

Section B. Record Description

Subject: This field is required to open a record, and is used to identify the applicable standard. It should be updated if the subject description becomes inaccurate or incomplete. The recommended identification of record should be as follows: Standard Designator (e.g. QEI, A17, B31.1, etc.), followed by applicable Part(s)/Section(s)/Article(s)/Chapter(s)/ Appendix(ces), and followed by applicable Paragraph(s)/Figure(s)/Table Number(s). The edition year may be needed. Paragraph/Figure/Table headings or other “key” words are recommended.

Examples:

CSD-1 Part CE, CE-130 Motors
B31.8 Chapter III, Table 832.2 Thermal Expansion of Carbon and Low Alloy Steel
A17.1, Figure 2.16.1.1 Inside Net Platform Areas for Passenger Elevators
PVHO-1 Nonmandatory Appendix C, C-3.2 Threaded Insert Couplings
B31.1, Para. 111.2.3 and 127.4, Undercut Rules

2. Proposal: This field represents the action being taken through this record. Typically the action is described by one of the following verbs: Revise, Update, Delete, Edit, Correct, Add, Renumber, etc.

Examples:

Revise protection requirements under CE-130(c)
Update Table 8.32.2 with new values
Correct area equation shown in Figure 2.16.1.1
Delete current requirements in C-3.2 and Renumber existing requirements

3. Explanation: This field is used to input Rationale/Explanation of the revision. It should include some or all of the following:

Technical explanation of the proposal and/or existing requirements.
Action intended to accomplish.
Detailed description of the changes / additions / deletions to the text.

Examples:

Current motor protection requirements in CSD-1 have been found to be too restrictive, and have not been validated by engineering calculations. Experience has shown that a decrease in x will not affect the safety or the life of the motor. The requirements are being revised accordingly.
Table T-1411-1 will be changed to make a distinction between elastic and inelastic analysis and restore the value of K' to its original value of K' = 0.9. About 20 years ago the value of K' was changed from 0.9 to the more conservative value of 0.67 without a distinction between elastic and inelastic analysis. Subsequent studies have shown that the increased conservatism was not warranted for elastic analysis.

Summary of Changes: The information provided in this field will be a restatement of the proposal and explanation, without associated technical background or rationale. This information is provided for the benefit of code users and is published as the Summary of Changes that accompanies most new addenda and editions. This field is required by BPVC for errata and revisions. Use of this field is optional but recommended because the information is required for publication.

Notes:

The Summary of Changes is meant to provide a brief high-level description of the changes that will be apparent to the Code user upon reviewing the published action.
The Summary of Changes should be composed in past tense. An effective Summary of Changes statement will be a restatement of the proposal and explanation, without associated technical background or rationale.
The Summary of Changes may be structured as follows, when appropriate:
- Restatement of action (from Proposal), e.g. “adopted”, “revised”, “deleted”, “moved”, “annulled”, etc.
- Affected text, e.g. paragraph, table, etc. (from Proposal).
- Purpose, e.g. “...in order to clarify, correct, update, reformat, reflect / correlate…”

Examples:

· Note (22) added to Table KCS-1 for SA-723, Class 3 materials.

· XII Paragraph TF-410.4 revised to add S20100 and S20400 PFHT requirements.

Section C. File Attachments

Proposal File: This field MUST contain the most recent (latest) version of the proposal/document/revision to be reviewed during the consensus process.

Notes:

The proposal file should not contain material that is not subject to consensus approval. See background material and committee correspondence fields described below.
It is essential that the correct revision file is attached to the record before it is added to a ballot because the file CANNOT be revised while the record is linked to an opened ballot.
Once a new file is uploaded, it is automatically labeled CURRENT PROPOSAL FILE, and the previous file is automatically archived.
Archived files contain three description fields: size, date posted, and posted by.
Staff secretaries no longer have access to deleting archived files.
The Project Manager or Staff should use the most up-to-date version of the Code section when providing revisions.

Background Material: This field should contain a file providing background information for the record, if applicable or needed. Background information includes but is not limited to: Sample calculations, tables, figures, and any supporting information that is pertinent to the record.

Committee Correspondence: This field should contain committee correspondence pertaining to the proposal.

(Update Record ONLY) View/Manage File Attachments Button: Opens the File Attachment History for the record in a new window. This section allows users with access to update the file attachments, as needed. If there are previous versions of any of the file attachments, all users can access those files here.

Section D. Code Cases

This section allows you to either create a new Code Case, or take action on an existing Code Case (revise, annul, or reinstate). If you are taking action on an existing Code Case, then you will need to select that Code Case as part of opening the record. This section allows you to complete that process, if needed.

Select a code case type: This section allows you to select the type of code case for which you are opening a record. Select the applicable radio button.
- New/Pending: This is for all new Code Cases. If this radio button is selected, no further action is needed in the section.
- Revise Existing: Used to revise existing code cases. Upon selection, an interface allows you to select a code case will appear.
- Annul Existing: Used to annul existing code cases. Upon selection, the interface allows you to select a code case.
- Reinstate Annulled: Used to Reinstate previously annulled code cases. Upon selection, the interface allows you to select a code case.

Select a code case number
- New Pending: N/A the code case number will be assigned at a later time.
- Revise Existing / Annul Existing / Reinstate Annulled: Use the listbox that displays when the radio button is selected to locate the code case number upon which you would like to take action. You can search by entering text in the textbox.

Click Select: Once you have located the code case upon which you would like to take action, you can use the Select >> button to move it to the selected list. If you select the incorrect code case, you can use the << Remove button to de-select it.

Section E through G, Project Manager and Record Creator Fields

E. Project Administrative Manager:

Staff contact information is automatically determined based on the Primary Committee responsible (under A.2). This field contains the contact information for the Staff Secretary of the Primary Committee Responsible for the record.

Staff Notes: This field is available to the Staff Secretary to record miscellaneous details related to the proposal which are not included within the item history fields (see G.4, I.1 and I.4).

F. Record Creator:

This field is automatically generated by the system. It lists the name of the person who originally created the record.

G. Project Technical Manager:

Use this field to indicate the Project Manager for the record. This is usually the committee member responsible for the record (e.g. proposal developer or Committee Chair), and should be updated as needed.

Project Manager Notes: This field becomes available for update once the record has been created. The Project Manager can use this field to record miscellaneous details related to the proposal.

Section H. Sub-Tier Committee Level Fields

Original Inquirer Contact Information: This field can capture the contact information of the originator or requestor of the proposal. Warning: This field is limited by the number of characters. If you use this field, as a minimum include individual’s name and phone number or email at the minimum.

Project Team Name: If a Project Team was formed to develop the proposal, this field can record that Project Team's name.

Project Team Members: If a Project Team was formed to develop the proposal, this field allows you to capture the names of the Project Team members. Note: If members are not part of C&S Connect, it is recommended that e-mail addresses are included in this field.

Subcommittee Item History: This field can capture any relevant Subcommittee and/or Project Team history. The History can include notable events (and dates) within the consensus process of the record. Note: It is recommended that entries start with the date of occurrence for the notable event. Example: 02/15/13: Subcommittee approved item at their meeting.

Section I. Additional Subcommittee Information

Codes Affected by Proposed Revision: This field is available to indicate codes affected by proposed revision.

Related Committee Records: Use this field to link other records that are affected by this record. To do so, click the Search Related Records button and enter the record number of any other records affected by the proposed revision. Mark the checkbox to add to record (see right column) and click the Link These Records button. This field may remain blank if no other records are affected.

Proposal Keywords: This field lists the keywords that can be used to describe the record. Select the appropriate keywords that best describe the record. This field may be left blank. Selecting a proposal keyword(s) allows BPV members to filter a Review and Comment ballot by keyword; when filtered the Review & Comment ballot will show only records containing the selected keyword.

Secondary Subcommittee(s) w/ Related Actions: This field is for proposals that require consideration by multiple Committees. It is used to identify any committee(s) that is/are required to take action on the proposed standards action. If the record requires consideration by more than one Committee, the Staff Secretary of the primary Committee associated with the record should select the applicable Secondary Committee(s).

The field has two components: “Pending Committees” and “Committees Responded”. These components are to be used as follows:

The Pending Committees column should contain all committee(s) required to take action. The committees must remain in this column until the required action is completed.
Note: The Staff Secretary of the primary committee responsible is responsible for identifying all the committees with related action.
The Responded Committees column should contain the committees that have completed the required action.
Note: The Staff Secretary of any of the secondary committee(s) identified in this field is responsible for updating this column when the related action has been completed.

Additional Notes:

Action used in the description of the field refers to:

o Conducting a Review and Comment of the proposal

o Endorsing proposal

o Approving proposal

Once the required action is completed, the Staff Secretary of the secondary committee typically documents it under the Subcommittee History field.
This field is currently ONLY being used by BPV Code committees

Type (Nuclear Only): This field is only to be used by BPV-SCXI. Select one of the following options from the drop-down menu:

CCI: Code Case Incorporation
COR: Clarification of Requirements
INT: Implementation of New Technology
IS: Increased Scope
SOR: Simplification of requirements
M: Maintenance such as updating to later editions of referenced documents.
S-H: Safety (high)
S-N: Safety (normal)
RRE-H: Reduced Radiation Exposure (high)
RRE-N: Reduced Radiation Exposure (normal)
RB-H: Reduced Burden (high)
RB-N: Reduced Burden (normal)
M-H: Maintenance (high)
M-N: Maintenance (normal)

Text of Subordinate Group Negatives: If required by the Committee supplemental procedures, this field captures the text of unresolved Sub-Tier Committee negatives to be reported to the Consensus Committee. In the event when there are no unresolved negatives, the term “None” should be entered.

Note: This field can be left blank if the Committee supplemental procedures do not require this documentation. This is useful for recorded voice vote requests.

Subordinate Group Action Date: If required by the Committee supplemental procedures, this field contains the date the proposal was approved by the subordinate group.

Section J. Additional Standards Committee Information

Standards Committee Description 1: This field is used only by BPV committees. It provides necessary details of any Standards Committee’s action taken at a meeting (not covered under item I.2 and I.3.), and should be updated as needed.

Standards Committee Action 1: This field is used only by BPV committees, and should be updated as needed. Choose an option from drop down menu that best reflects information contained in field J.1.

Committee Action Date 1: This field is only for BPV Standards Committee usage and should be updated as needed to reflect the date of Standards Committee action described under J.1 and J.2.

Standards Committee Description 2: This field is used only by BPV committees. It provides necessary details of any Standards Committee’s action taken at a meeting (not covered under item I.5 and I.6.), and should be updated as needed.

Standards Committee Action 2: This field is used only by BPV committees, and should be updated as needed. Choose an option from the dropdown menu that best reflects information contained in field J.4.

Committee Action Date 2: This field is only for BPV Standards Committee usage and should be updated as needed to reflect the date of Standards Committee action described under J.4 and J.5.

Addenda/Edition Year: This field is used to identify applicable Addenda/Edition year when the record proposal file is to be published. It is typically updated once the record has received Standards Committee approval. However, it should be further updated if the target publication date changes.

Interpretation Record

Most Interpretations Records will be opened by the inquirer through the newly created, public-facing Interpretation Submittal Form. When Interpretations are submitted by the public, the Staff Secretary for the Primary Committee Responsible for the Interpretation Record will receive an email alerting them of a new Interpretation Record. At that point you should access the Update Interpretation Record form by searching for the record number. The record will also appear under your My Items tab. For details on what fields should be updated, see Step 2: Updating the Interpretation Record below.

In the event that you receive a request for interpretation directly from a member or inquirier, here is how to create the interpretation record:

1. Determine whether or not the request for interpretation complies with the guidelines and ensure that the inquiry hasn’t been answered in the past.

2. Open a new Interpretations record using the Staff Tab in C&S Connect.

· Selecting the record type “Interpretation” and clicking the “Go” button shall open the Interpretations Submittal form in a new window.

3. Fill out the Interpretations Submittal Form (fields described below) in the same way an outside inquirer would – make sure to attach any documents (email, physical letters, etc.) to the original inquiry as background information.

4. Upon completion, the Interpretation Submittal Form creates a new Record on C&S Connect that you will then need to update with key information (see Step 2: Updating the Interpretations Record below for further instructions).

For more information on the process for handling interpretations, please see the Interpretation Process Document.

Step 1: Completing the Interpretation Submittal Form

Interpretations Submittal Form Fields and associated record fields: Fields marked with an * are required on this form.

Section 1, Inquirer Information

*First Name: feeds to record form G1
*Last Name: feeds to record form G2
Company/Organization: feeds to record form G3
*Address 1: feeds to record form G4
Address 2: feeds to record form G5
Address 3: feeds to record form G6
*Town/City: feeds to record form G9
*Country: feeds to record form G7 (determines the requirement for some fields)
*State/Province/Region/County: feeds to record form G8 (only required for applicable countries)
Zip/Postal Code: feeds to record form G10 (only required for applicable countries)
Phone: feeds to record form G11
Fax: feeds to record form G12
*Email: feeds to record form G13
*Confirm Email (validates against the previously entered email address)

Section 2, Request for Interpretation

*Standard Designation: feeds to record form B1.1
- If question(s) applies(y) to more than one standard, select additional standards and references that are applicable.
- List of Non-applicable standards:

The standard designator is hard-coded so that the Primary Committee Responsible and staff contact will be designated on the corresponding record form upon form submittal.
In the event that the Primary Committee Responsible and staff contact are incorrectly assigned (based on user error, or other issues), staff are able to select the correct Primary Committee Responsible from the update record form. This action changes the staff contact to the staff secretary for the new Primary Committee Responsible.

§ If Staff changes the Primary Committee Responsible, he/she send a notification to the new Staff Contact alerting him/her that he/she is responsible for a new Interpretation Record.

*Edition/Addenda: feeds to record form B1
*Paragraph/Fig./Table No.: feeds to record form B1
Subject: feeds to record form B1
*Inquiry(ies): feeds to record form G15
Proposed Reply(ies): feeds to record form G16
Background Info: feeds to record form G14
Background file: Customers can upload a file. Background file becomes record form C1.

o Supported File Types: (.doc, .pdf, .txt, .jpeg, .tiff, etc.)

o Maximum file size is 10 MB

Section 3, Important, Please Read

Clicking Review Information Prior to Submittal button will open the review form for you to double-check the entered information.
Upon submittal, an automatic email is sent to the inquirer and the Staff Secretary of the Primary Committee Responsible.

Step 2: Updating the Interpretations Record

Verify Section A. Record Information (update as needed)

· Primary Committee Responsible (A2)

o In the event that the inquiry was assigned to the incorrect Primary Committee Responsible/staff contact, Staff shall update the Primary Committee Responsible to the correct committee. Upon submittal, this action re-assigns the record to the proper staff contact.

o When the Primary Committee Responsible for an Interpretation Record is changed, the Staff Secretary making the change must send an email alerting the Staff Contact for the new Primary Committee Responsible of the change. This manual alert is the only way for a Staff Secretary to know that a new interpretation record has been assigned to him/her.

· Record Level (A3)

· Record Sub-Type (A4)

o Interpretation: This is the standard request for Interpretations that do not require either a code revision or a revision to an existing interpretation

o Intent Interpretation

§ If the Staff Secretary deems the request for interpretation to be an intent interpretation (or if it becomes necessary to change the requirement interpretation to an intent interpretation), then the record subtype will be changed to “Intent Interpretation.”

§ A component revision record will also be opened for the necessary code change associated with the intent interpretation.

§ The interpretation and component records will be linked using the “Related Committee Records” feature.

§ Linking the two records will ensure that the interpretation and revision proceed through the C&S Connect approval process at the same time and that one is not approved and published/issued without the other record having been approved.

§ The database will retain all prior interpretations that have been revised by the new interpretation, however; they will be suppressed from view to eliminate confusion. It may be required that staff manually enter the note at the bottom of the proposed Q&R field in C&S Connect, but it is preferred that the function is automated.

§ Revision of Interpretation

§ If an interpretation has a subtype of Revision of Interpretation, then Staff will need to enter the record number for the interpretation it’s revising in the Related Committee Records field.

§ When the record level for a record with the sub-type Revision of Interpretation is changed to Issued, it will trigger a note to be added to the interpretation text.

§ The note will say: “This interpretation revises the interpretation approved as record yy-xxxx.”

§ The record number to be displayed in the note will come from the “Related Committee Records” field.

· Add Committees Involved in this Record, as needed

o Board(s) (A5)

o Standards Committee (A6)

o Sub-Tier Committee(s) (A7)

Verify Section B. Record Description (update as needed)

· Subject fields under B. Record Description, update as needed

o Standard Designation

o Edition/Addenda

o Paragraph/Fig./Table No.

o Subject Description

· Add the Proposed Question(s) and Reply(ies) to the record (B2). This field feeds to the issued interpretations database, and MUST be updated to match the final version of the Question(s) and Reply(ies) used in the signed issuance letter.

· Add an Explanation for the record (B3).

Add/Update the Files in Section C. File Attachments

Note: If a Background File was included with the submittal form, this should be reviewed/updated

· Background File (C1)

· Proposal File (C2)

· Committee Correspondence File (C3)

· Signed Issuance Letter (C4) – see below for more information.

Add/Update Sections D through F

D. Staff Contact: N/A

· Staff Notes: Add as needed

E. Record Creator: N/A

F. Project Technical Manager:

Add a Project Technical Manager to the record under Section F. Project Technical Manager. The Project Manager should be added following the Primary Committee Responsible process.

Note: This field is automatically assigned when an Interpretation Record is first submitted based on the Staff Secretary for the Primary Committee Responsible. It should be updated as needed to follow the committee’s process for assigning Project Managers.

Section G. Inquirer Information, View Only – fields are pulled directly from the Interpretation Submittal Form

Section H. Additional Committee Information

Add Section H. Additional Committee Information as needed.
- Codes Affected by Proposed Revision (H1)
- Related Committee Records (H2)

Note: This field is especially important if the record is an Intent Interpretation – see more information in the Record Sub-Type section below.

Proposal Keywords (H3)
Secondary Committee[s] w/Related Actions (H4)
Type (Nuclear Only) (H5)
Committee Notes (H6)
Text of Committee Objections (if made at a meeting) (H7)
Committee Approval Date (H8)

Click Update Record to save changes

Membership Record, PF-1

Electronic PF-1 Form: Fields marked with an * are required fields on this form.

If your problem was not resolved here, send an email to helpdesk.

If you notice a mistake in the help file, send an email to training@asme.org.