Westinghouse’s RPE ©Journey with DOORS Nuclear Automation

Westinghouse’s RPE ©Journey with DOORS Nuclear Automation
Thomas W. August Westinghouse Electric Company LLC DOORS Administrator and Trainer 412.374.3855 Rev 1.0a

Safety and Administrative Location of exits Fire drills scheduled Please be mindful of any items on floor Location of restrooms Cell phones and/or pagers set to vibrate Proprietary Information for Level 3 Procedures

Agenda Brief Overview of DOORS Six-Sigma Analysis Lessons Learned with RPE POC Generic Templates Export ME (from River North Solutions) Export ME Improvements Simple Example for Standardization Sidebar and Blackline Text Weaving Documents Saving Document Creation Information in the Document Smarter Templates Summary and Discussion Questions and Demo

Traceability view User Reqts Technical Reqts Design Test Cases End-to-end visual validation in a single view

Definitions DOORS = Dynamic Object Oriented Requirements System This is a requirements management tool used to manage all of the sets of requirements across multiple programs for many different customers RPE = Rational Publishing Engine This is a publishing tool used with DOORS and other tools to build customer deliverable requirements and design documents from the DOORS modules Two main components – as “Document Studio” for creating templates and a “Launcher “ for executing specifications

Output Name location Style Sheet (MS Word dot file) Templates (input data location) Specification Output format database queries, layout, formatting master pages (which define header, footer, orientation, and paper size) Attributes Variables Output normal to your D drive /data/documents to allow macro to run. RPE Specification Content – (DSX) A Style sheet in RPE speak is actual a MS Word template (dot) DSX file Output information DTA file Output can be MS Word PDF HTML XSL-FO

Original “Publishing” Process with DOORS

Six Sigma Analysis(Customer 1st in Westinghouse Speak) SIMPLIFIED PROBLEM STATEMENT: Generation of Requirement Documents from DOORS with the level of formatting required by Westinghouse is prone to multiple iterations of manually updating DOORS and re-issuing. This results in a high likelihood of human error due to double work (updating in word & transferring updates to DOORS), higher costs due to multiple cycles through review and approval groups, lengthy approval cycle times, and low satisfaction by the authors/leads responsible for the various requirements specifications on the projects. Analysis started 2008

Six Sigma Analysis(Customer 1st in Westinghouse Speak) OBJECTIVE: Reduce the number of cycles from DOORS to the final Quality Record Simplify the Document Generation Process Reduce or eliminate opportunities for errors

Six Sigma Analysis(analysis summary) We identified 23 opportunities for human error in our process that could cause the DOORS data to be out of synch with the Quality Record Too many hand-offs between groups outside of DOORS Very little automation Manual efforts were required to reduce potential risk Original process contained excessive rework DOORS loss of credibility in People/Process Negative Effects of Rework – missed due dates, milestones, and schedule impact.

Six Sigma Analysis(proposed new workflow) Created optimal workflow using RPE: (after determining the real requirements) The least amount of rework The highest amount of collaborative engineering The smallest amount of concern for format/output for engineers Higher use of standardization with DOORS Place all Front Matter in DOORS module Trained all groups to work in DOORS to eliminate out of sync opportunities Much faster and repeatable output (result in DOORS to Quality Record cycle time reduced by 70%)

Six Sigma Analysis(Pilot proposed solution) Tested Proof of Concept with RPE 1.1.1: Error opportunities were reduced Reduced out of sync opportunities Process was much faster It did enhance standardization Some user complaints were still not satisfied: Still needed a markup copy of exported document for reviewers to see what changed Change bar indicator produced by the tool did not meet users needs

Lessons Learned with RPEand improvement we made Users do not want to learn how to create templates and specification. They just want to click and get a document: We standardized the views for use with templates Minimized deployment of RPE Studio (helped reduce use of RPE licenses and encourage standardization) Introduced the use of Export ME publishing script (by River North Solutions)

RPE 1.1.2 Generic Templates (ABC,D, & E) Templates A, B, and C have been combined into one template and will use RPE-PartA, RPE-PartB, and RPE-Part C views as default. Templates have logic to detect Project and/or Subsystem differences. Template E can be used to create tables and RTMs directly from view (regardless of the attributes used)

One-Button Document Publishing We use “Export MeTM” to produce an MS word document from DOORS using predefined, standard views – as seen here in RPE-Part[A,B,C,D] views in each module

Export Me Script helped (but we still had a lot of specifications) Every document still required its own specification. One of our users has over 200 modules and each document required a specification. If we could create a specification in 30 minutes that would be 100 hours of work If we had to update a template, we would have to update 200 specification. The one specification per document is due to the need to provide the module ID in each Specification.

Export Me improvement(proposed modifying Export Me to provide the Module ID) I theorized that if we could modify Export Me to provide the Module ID when it called the Specification, we could reduce 200 specifications to one. I discussed the idea that I called “Self ID” with Felix Morariu of IBM and Bob Parro III of River North Solutions (RNS). Felix agreed that the idea was feasible and he suggested using XML to create the method for “Self ID”. After discussing the idea with Bob, he started experimenting with the idea and was able to modify Export Me to actually do it. Now we can use one specification for hundreds of documents and updating the template is significantly reduced.

More Export Me improvement needed(we need to print multiple document from one module) As we used our product on more plants, we needed to make some changes to our document for each Customer site. Using views and filters we could produce multiple documents from one module, but Export Me could only produce one per module. We worked with Bob Parro III of RNS to develop a menu process of Export Me to accommodate multiple documents Now we can produce any combination of one or more documents from one module. If we need to produce a set of documents for 4 different sites with the same 200 modules, we only need 4 specification instead of 800. Can you calculate the savings in setup and maintenance?

Export Me™ allows production of RPE exports with minimal clicks RPE Document Specification (.DSX) File: - Defines data source- Defines values for variables- Defines output formats and associated parameters- Defines templates to be used- Stored in centrally accessible location We use logic to detect project specific formatting needs Word styles are assigned to attributes

New Version of Export Me can create a Menu for Multiple Documents from one module We can now print multiple Documents from one module No limit to number of documents per module You can select one, all, or any combination

Different Attribute order after the Requirement Guidance Exception Rationale Source Requirement Classification Plant Applicability NOTES:Some users place Rationale before Guidance. This could cause us to create and maintain duplicate templates. Simple example for Need to standardize (attribute order after requirement)

Change Indicator and Blackline text(solving the last two complaints about using DOORS) We worked with RNS to create a method on creating a sidebar indicator with DOORS. We created the sidebar attribute to “Show” or “Hide” an equivalent image for the MS Word change bar. Its granularity is to the attribute level not a single line. We worked with RNS again to create what we call “Blackline Text” for any attribute string or attribute text within a module to show changes in text.

Example of Blackline Text

Menu Blackline Text is an improvement over the old Dynamic History DXL(Now we can do any String or Text attribute)

Weaving Documents One of our groups needed to produce over forty documents from DOORS, but some key sections are the same in all the documents. We created a module with all the standard sections in it and used standardized views. We weave these sections into any one of the forty module when the document is printed. When the standard sections need revised, we can make the change in one place and the document can get the update the next time it is printed.

Weaving Documents(The Standard Module ID is the Specification and Export Me supplies the module ID for the Document)

Save Document Creation Information(for trouble shooting and/or recreation needs) The list below represents the configuration management information that is stored in the document properties, e.g., the meta data of the exported document. Source DOORS Version Document Specification Source Module and View Names: Module+View name pairs are documented for as many modules and views are published Publish timestamp RPE Version During Publish OS Username During Publish OS Name During Publish OS Architecture During Publish OS Version During Publish Host Name During Publish

Creating Smarter Templates RNS suggested ways we can reduce our number of templates and specifications even more. Add logic to the template to detect project name and adjust the template for project difference. Instead of using the DOORS attribute “Paragraph Style”, assign style based on usage and attributes

Transform ME We created a tool called Transform Me to move some of our structure information into attributes. This allows us to assign style to attributes and relieve the engineer from some formatting activities (engineer can focus on ontent not formatting).

Summary With the combination of the following methods we are learning to produce documents for DOORS faster and with less maintenance. TransformME Export ME with XML switch and menu Weaving Sidebar attributes Blackline Text Standardized default views Using Template logic Assign styles based on attribute and usage

Demo and Questions 32

Westinghouse’s RPE ©Journey with DOORS Nuclear Automation