SOP CE Builds Process - v1

WORK INSTRUCTION Internal Information
Doc No.: Rev. State: 00 5 Page(s) 1
Date
Issued by: Christopher Rivera March 8, 2007
Approved:
Approved by: Rameses T. Marzan; Minette Llarena
Standard Operating Procedure

EDC Builds Process
Initial DRAFT
Date Approved:
March 3, 2007
Date Implemented:
March 22, 2007
Overview:
Builds process is a process performed when a new publication is acquired and will be
monitored by LexisNexis. This new publication will then be designed, coded and
monitored by LN in such a way that client’s satisfaction is met.
Related Documentation:
XML Detailed Process Documentation (included all types of checklist)
Objectives:
This SOP outlines the process and guidelines of Content Editor’s participation in the
Builds Process.
Scope:
All Builds publications assigned to SPi Content Editor.
Definition of terms:
PM – Product Manager
DA – Design Analyst
SE – Systems Engineer
CE – Content Editor
EDC – European Data Center
CI – Conversion Instruction
Printed copies will only be valid if it bears the DMC “CONTROLLED COPY” stamp (in red).
1/Q-01/0006 rev. 01
Date
Approved:
FABC – tool wherein test data can be checked

TOD – Turn over documents
Procedure:
1.0 Webstar Assignment
A Webstar ticket is created by the SPi DA requesting for an SPi SE and CE for a new
publication. The creation of webstar signifies the start of SPi Content Editor’s
participation in building a new publication for EDC.
The SPi CE will only add in the webstar’s Actions Diary his acknowledgement that
he/she will be the assigned SPi CE for this build publication. It is the SPi SE who
will assign the webstar ticket to him/herself.
2.0 Conversion Instruction Review Process
2.1 The SPi CE receives an invitation from the DA for the schedule of internal
review of CI. A document copy of the CI is also attached.
2.2 The SPi CE will update the ISM Work Information tracking schedule to reflect
the CE’s start time of CI review.
2.3 The SPi CE will start reviewing the CI through the help of a checklist. A
checklist is a guide on what items in the CI should a CE focus into. (See XML
Detailed Process Documentation). The SPi CE will take down all his comments
in preparation for the internal review with SPi DA and SE.
2.4 In the internal review of the SPi DA, SE and CE, they discuss the issues that each
party will address then finalize.
2.5 The DA will revise the CI in preparation for the external review wherein the LN
PM is now invited. The SPi DA will send invitation for the scheduled external
review. In this meeting, the CI is thoroughly reviewed and finalized.
2.6 The SPi CE will update the Work Information tracking schedule to reflect the end
time of CI review.
2.7 The SPi DA will send an email notification to the LN PM, SPi SE and CE
informing that the CI is already finished and will be passed on to the SPi SE for
conversion coding.
1/Q-01/0006 rev. 01
Date
Approved:
3.0 FABC Checkout Process
3.1 The SPi DA will create a webstar ticket to SPi CE queue, (F1320)EDC Builds
Data Technician, requesting to add the SMI and DPSI of the publication to
Nexis Editor. (See XML Detailed Process Documentation). After these
processes are done, the SPi CE will resolve the webstar.
3.2 The SPi SE will start their conversion codes.
3.3 Once the conversion code is finished, the SPi SE will send an email notification
to the SPi CE advising him/her to perform data check out in FABC. The SPi
CE will use a checklist to help perform the process. (See XML Detailed Process
Documentation).
3.4 SPi CE will again update the ISM Work Information tracking sheet to reflect
the start time of FABC.
3.5 SPi CE will email his observations and comments to the SPi SE. (Note: An
exchange of correspondence and recoding process is most likely expected until
all parties are satisfied with the code and result of data online as per CI).
3.6 The SPi CE will send an email notification to the builds team informing that
he/she is approving the data checkout.
3.7 SPi CE will again update the ISM Work Information tracking sheet to reflect the
end time of FABC.
4.0 Adding new publication to the ISM tool
4.1 The SPi CE will now create and submit the Production Schedule Form for ISM
tool. This form indicates the instruction that a new build pub is to be added in
the ISM production schedule tool. The SPi CE will follow a checklist to ensure
that all pertinent information is in the SI of the publication. (See XML Detailed
Process Documentation.).
start time of adding pub in ISM tool.
1/Q-01/0006 rev. 01
Date
Approved:
4.3 SPi CE will also send an email to Jackie Evans informing her of the submission
of the form and requesting its exception to be turned-off first since the pub is not
yet released and turned-over to production.
4.4 Once the pub is added in the tool, the SPi CE will validate the information in the
tool is correct. (See again the checklist for adding information in the SI to ensure
that everything is correct).
end time of adding pub in the ISM tool.
5.0 Turn - Over Document (TOD) Approval
5.1 The SPi SE will send the TOD to the SPi CE for approval.
start time of TOD approval.
5.3 The SPi CE will thoroughly review the TOD by using checklist and will send an
email to the SE of his/her comments. (Note: An exchange of correspondence and
revisions is most likely expected until all parties are satisfied with the
documentation. See XML Detail Process Documentation).
5.4 The SPi CE will send an email notification to the build’s team that the TOD is
now approved.
end time of TOD approval.
6.0 Release Date
6.1 The SPi DA will advise to the builds team that the publication is now release to
production.
6.2 The SPi CE will advise the EDC Maintenance team that a new publication is
now release to their production tool however he will still monitor it until such
time that it is turn-over to the maintenance team.
6.3 The frequency of the new publication will help determine until when the SPi CE
will monitor it. Below is the frequency guide:
1/Q-01/0006 rev. 01
Date
Approved:
• 5 days check out for daily’s

• 1 day for Weekly
• None for every 14 days and above frequency
6.0 Turn - Over to EDC Maintenance team
When the new publication has no issues after the release date and until the SPi CE
is monitoring it, the new publication will now be formally turned-over to
production. The SPi CE will send an email notification to all EDC Maintenance
team attaching all pertinent documents such as CI and TOD.
Process Goals:
Provide a successful release of builds publication to production.
Escalation:
Failure to comply with the above procedures, please escalate to SPi CE Team Lead
Revision History
Revision No. Revision Date Author Revision Description
1/Q-01/0006 rev. 01

SOP CE Builds Process - v1

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SOP CE Builds Process - v1

Uploaded by

Copyright:

Available Formats

WORK INSTRUCTION Internal Information

Doc No.: Rev. State: 00 5 Page(s) 1

Standard Operating Procedure

XML Detailed Process Documentation (included all types of checklist)

FABC – tool wherein test data can be checked

1.0 Webstar Assignment

2.0 Conversion Instruction Review Process

3.0 FABC Checkout Process

4.0 Adding new publication to the ISM tool

5.0 Turn - Over Document (TOD) Approval

6.0 Release Date

• 5 days check out for daily’s

6.0 Turn - Over to EDC Maintenance team

You might also like