Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Lists all roles and their responsibilities relevant to this Work Instruction.

RoleResponsibilities
Heads of Standards
  1. Approves the standards
Copy Editor
  1. Reviews the draft standards before publication
Project Manager
  1. Works with the Publication Committee to finalize the comment resolution spreadsheet
  2. Refresh the TA Specification
  3. Addresses copy-editing comments
  4. Ensures all project documents are posted on the portalPublish the document.
Communications Team
  1. Archives space
  2. Announces availability of the standardPosts the standards on CDISC portal and announces availability.
Education Representative 
  1. Post Posts education course and announces availability.
CDISC IT
  1. Locks down Wiki space for the standard
Software Engineer
  1. Pushes the standard to QA
  2. Pushes the standard to Stage
  3. Posts the standard on the website 
Metadata Stweard
  1. Does the User Acceptance Testing
SCR
  1. Approves final change.

Instructions

Describe each step to be taken to complete the scope of this Work Instruction in the prescribed sequence. Use active verb in the Instructions column.

www.cdisc.org
Step #RoleInstructions
1.0Head of standardsApproves the standard
2.0Copy EditorReviews the draft standard as a quality check right before Publication
3.0Project Manager Addresses copy-editing comments
4.0CDISC ITLocks down Wiki space for the standard
5.0
Creates PDF
6.0Software EngineerPushes the standard to QA
7.0Metadata Steward Does the User Acceptance Testing
8.0Software EngineerPushes the standard to Stage
9.0
Exports public review comments
10.0Software EngineerCommunications TeamPosts the standards on the website
11.0Communications TeamArchives space
12.01.1Communications TeamAnnounces availability of the new standard package.
213.0Education RepresentativePosts education course.
214.10Education RepresentativeAnnounces availability of the education course.
315.0Project ManagerEnsures all project documents are posted on the portal.
4.0Project ManagerSubmits package as final after resolving all provisional dependencies.
5.0SCRApproves the change to final. 
616.0Project TeamCreates a record of issues they have determined will be addressed in future versions of the standard.

...