LRS
Computer software employed to implement the CMS. Software classification level B due to be significant to the management of commitments.
Originator of sorts = Brian McFarland
How to get there
You can get there through start -> nuclear corporate applications -> LRS v3.0a
You can sign in by clicking ‘sign in as guest’.
How to use LRS
The key to using LRS is the search box. First click the view/edit button in the main window. Two new windows appear. In the query results box, click new row. The search mechanism is a mechanical and strongly logical search (closely associated with SQL). Multiple rows will yield a more exacting result set.
- The main field to search is Text. This field should contain the text of the commitment.
- Summary is the next most likely field to contain keywords.
- The Operator is the search method. Contains is probably most useful. It acts like a wild card search "asterisk (*)".
Once you get a result set you have to review the commitments for relevancy and perhaps revise your search.
Wiki LRS
Integration of this database has occurred for JAF into the wiki itself. It is in a separate name space called "COM"
- Search by going to: Wiki LRS database search
The wiki will allow connections to become more apparent or at least allow its organization. Hence, it is a much better search method.
LRS is Used for
Procedure Revision Commitment Reviewer
The most common use of LRS for the average employee is performing a commitment review during a procedure revision. This process does require a qual but is otherwise rather simple.
Tracking for Licensing department
The database mostly keeps track of letter submittals which contain a commitment section.
History
When the commitment project was begun at some year, all documents were searched for possible commitments to the NRC. It was clear that these efforts were a little over zealous because many "commitments" made back then would not be considered commitments today. Efforts are needed to sort through and make sense of all the extraneous entries.
Out of date problem
LRS is an old program. A Commitment Management Project has begun to manage the existing commitments. See LRS Statistics.
Software Specifications
Section for how the LRS software works
Fields
| field | description | options | required |
|---|---|---|---|
| COMMIT_TYPE | Two options only. Is there a specific due date | A (Active), P(Passive) | Y |
| COMMIT_NUMBER | unique identifier. Picked by default | ||
| UNIT | applicable site | JAF, | Y |
| SOURCE_DOCUMENT | What document was the commitment committed to. Probable a letter name | Y | |
| SOURCE_DOC_DATE | For the source document issued date. | ||
| PARENT_1_TYPE | |||
| PARENT_1_NUMBER | |||
| PARENT_1_DATE | |||
| PARENT_2_TYPE | |||
| PARENT_2_NUMBER | |||
| PARENT_2_DATE | |||
| SUMMARY | A short description of the commitment. | ||
| LICENSING_LEAD | Licensing person in charge | ||
| LEAD_PERSON | |||
| LEAD_PER_DEPT | |||
| SUPPORT_PERSON | |||
| SUPPORT_PERSON_DEPT | |||
| PRIORITY | |||
| NRC_SUBMITAL_SIMS | |||
| ORIGINATED_DATE | |||
| SCHEDULED_COMPLETE | |||
| CLOSURE_DATE | When the commitment was changed to closed or deleted. | ||
| STATUS | Specifies if the commitment is done. | Open, Closed, History, Sat, nsat | Y |
| OUTAGE | |||
| AGENCY | |||
| LAST_UPDATE_USER | |||
| LAST_UPDATE_DATE | |||
| LAST_UPDATE_USER_RD | |||
| LAST_UPDATE_DATE_RD | |||
| CURRENT_STATUS | |||
| TEXT | Most important field. Actual text of commitment. | ||
| COMMENTS | Notes to track information about the commitment | ||
| KEYWORD_LIST | |||
| EXTENSIONS | A count of how many times the due date has changed. Auto-generated |
See also
- Regulatory Commitment
- EN-LI-110 - Commitment Management Procedure