NFLSS_SRS.docx

NATIONAL FLUIDS

LEASE SALE SYSTEM

SOFTWARE requirements SPECIFICATION

JUNE 18, 2014

NFLSS PWS SRS, vers. 1.03

UNITED STATES DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

DIVISION OF INFORMATION RESOURCE MANAGEMENT

DENVER FEDERAL CENTER

DENVER, COLORADO 80225-0047

i

Revision/Change Record

(Optional)

1 SCOPE

Identification

Members of the public nominating parcels for oil and gas, and geothermal lease sales

System Overview The National Fluids Lease Sale System (NFLSS) will be developed as a stand-alone system that will interface with existing bureau systems.

Additionally, functionality will be developed to utilize automated workflows and electronic forms allowing the public to enter information in compliance with the eGovernment initiative.

The system will be a powerful and flexible assistant in the leasing workflow process. It will interface with the Legacy Rehost 2000 (LR2000) system and the available spatial applications, and all pertinent surface use stipulations. The system will improve communications, decisions, and interactions with private and industrial clients, BLM Field Offices, and non-BLM Surface Management Agencies. This national system for onshore oil and gas and geothermal leasing will provide automated components which will reduce some duplicate data entry along with safe, reliable data handling to reduce errors and improve staff productivity.

Document Overview This Software Requirements Specification (SRS) contains the business requirements and detailed specifications for the system development. The document was developed with the user’s participation at the national and state level. This document should be used in conjunction with the business process requirements and BLM/DOI requirements for security and operations.

This document was created with the concurrence and review of the system User Requirements Team (URT), which is comprised of representation from WO300, WO310, DIRM, and State representatives from California, Colorado, Eastern States, Utah, New Mexico, Montana, Nevada and Wyoming.

Referenced documents Government Information Bulletins, Instruction Memoranda, Policy Manuals and Guides

System References The following table contains all life cycle management documents that have been or will be created.

Exhibit 300 Business Case

User Requirements Specifications

Asset Valuation Guide (BLM)

Computer System Operator’s Manual

Configuration Management Plan

BLM Enclave GSS Contingency Plan

Continuity Of Operations Plan

Data Management Plan

Implementation Plan

Interface Requirements Specification

Official Agency Record Designation Document

Plan of Actions & Milestones

Privacy Impact Assessment

Project Change Management Board Charter

Quality Assurance Plan

Requirements Traceability Matrix

Residual Risk Report

Risk Assessment Report

Security Test and Evaluation Report

Self-Assessment

Software Development Plan

Business Process Requirements

Software Test Plan

Software Test Report

Software Users Guide

ST&E Plan/Report

System Design Document

System Security Plan

Technical Vulnerability Assessment

Training Plan

Version Description Document

Requirements The detailed business requirements for the system are contained in Appendix D for Oil & Gas and Appendix E for Geothermal. The requirements were gathered and written by using the use case methodology and explains how the users (national, state, field, and public) expect to use the system.

Required States and Modes The methodology of states and modes has been replaced by the use case methodology. The required states and modes have been identified by the individual use cases; see Appendix D and Appendix E.

Software Item Capability Requirements Each use case identified in Appendix D and Appendix E is recognized as a capability. A use case can have multiple scenarios; therefore implying sub-functions.

Software Item External Interface Requirements Interface Identification and Diagram The system is a stand-alone system that will interface with the following:

· BLM Application Security Systems Version (BASS2) will control who has access to the national applications.

· LR2000

· GIS Services Project-Unique Identifier of Interface Not applicable.

Personnel-Related Requirements The skill level expected for the users accessing the system:

· National – knowledgeable about the program policies, guidelines and issues.

· State – knowledgeable about the program polices and guidelines. Responsible for the state’s data quality. Responsible for educating public of new processes.

· Field – knowledgeable about the program polices and guidelines. Responsible for the data within their office. Responsible for educating public of new processes.

· Public - knowledgeable about the lease sale process. Responsible for the data entered to initiate an Expression of Interest (EOI) for upcoming lease sales.

The skill level expected for the DIRM staff developing and maintaining the system:

· Technical team – proficient in developing WEB based programs using J2EEE applications.

· Data modeler – proficient in developing the system data model, using the standard methodology established by DIRM.

· Analysis – proficient in writing the system business rules, using the standard methodology established by DIRM.

Training-Related Requirements The system training will be done by three methods:

· Each screen in the system will have online help.

· Online training will be accessed via the WEB. The E-learning site will be developed and maintained by DIRM. The user will be able to:

· view a tutorial of the system

· frequently asked questions

· key word search

· access the software users guide

· Training classes for the state leads or all field users will be conducted prior to deployment of the system. Cost and time will determine if this method will be conducted.

Logistics-Related Requirements None reported.

Safety Requirements DIRM along with the operations and maintenance office has identified disaster and disaster recovery operations for the system. This document includes: prevention, offsite storage, backup, and recovery.

Software Item Internal Interface Requirements The system will have several interfaces. The system will be developed with COTS tools. This will not cause any special considerations since DIRM has already developed and deployed other systems using the same interfaces.

Software Item Internal Data Requirements There are no specific software item internal data requirements.

Site/Business Line Specific Requirements Not applicable.

Software Item Environment Requirements The system will be created and deployed on a BLM secured network. Access to the system will comply with the department and bureau policy and guidelines.

Computer Resource Requirements Computer Hardware Requirements The system will use the same hardware configuration as other systems maintained by DIRM. There is no special sizing, timing, or unique hardware requirements.

The Department of the Interior (DOI) will perform an assessment on the suitability and cost of hosting the development, testing, and/or the production environments via the DOI cloud contracts.

Computer Hardware Resource Utilization Requirements The following are estimated utilization for the system:

Computer Software Requirements The following have been identified in the use cases described in Appendix C and Appendix D:

· Each software unit has an unique identifier

· Specifications for databases and data files

· Security and privacy protection

· Data relationships and business rules Computer Communications Requirements Estimated utilization for NFLSS:

· Peak periods will be during the state lease sales;

· All states involving 120 users accessing the system, simultaneously;

· Average approximately 120 hrs. a week;

· Users are located in all state offices;

· Approximately 5 corrected serial numbers per state per year.

Security and Privacy Protection Requirements The system will be created and deployed on a BLM secured network. Access to the system will comply with the department and bureau policy and guidelines.

Software Quality Factors There will be access by the public to enter an Expression of Interest in upcoming lease sales throughout the Bureau. The system will be used by all levels of Bureau employees. There are no special software quality factors that are not already in place with the current systems.

Design and Implementation Constraints Design and implementation constraints, if any, will be identified in the software design document.

Other Requirements Not documented in the use case but required in the work flow process.

Packaging Requirements All deliverables will follow the national and project configuration management guidelines and standards.

Qualification provisions This section will be covered in the Requirements Traceability Matrix (RTM). The RTM will trace the requirement to the design module, how will it be tested, and state which test script will be used. The RTM will be completed when the software test scripts and software design document are done.

Requirements Traceability This section will be covered in the RTM. This document will trace the requirement to the design module, how will it be tested, and state which test script will be used.

Notes List of Acronyms and Abbreviations

Volume Glossary

Requirements Traceability Matrix This section will be covered in a separate document due to its size. The document is the Requirements Traceability Matrix. The document will provide the following information:

· Trace the requirement to the design module

· How will it be tested

· State which test script will be used.

Unanswered Technical Requirements

The on-line interface with CBS is not required at this time. The interface with CBS will be manual for the initial release of the system but may be included in a future system updates. There are several steps within the use cases that involve CBS.

The on-line payment option requirements are not included at this time. This option is necessary for on-line submittal of oil & gas pre-sale offers and for geothermal nominations. This will be implemented in a later version.

General Information for Oil and Gas and Geothermal Systems

General Information

1. Numerous systems have been developed which automate many of the manual tasks associated with the oil and gas lease sale process. The use cases for the lease sale processes include a description of the manual tasks associated with the business processes.

2. Some states have created a stipulation data base which associates stipulations with sale parcels. The states will be able to down load this information for inclusion into the system.

3. The entire sale process, which includes the Competitive Sale, the Day-After Drawing and the 2-year Window Application, is identified by the sale date. The sale date is the actual date on which the Competitive Sale is scheduled to be conducted.

4. Currently, states upload sale information to the LR2000 system via an upload file.

5. Many of the forms used in the sale process currently reside in word processing applications, almost always Microsoft Word, and can be found in the H-3120-1 Competitive Leases handbook located at: http://www.blm.gov/wo/st/en/info/regulations/Instruction_Memos_and_Bulletins/blm_handbooks.html

6. Examples of forms and reports not provided in the handbook can be obtained upon request.

General System Requirements The system must track a sale and all of its data/information from the beginning, from expression of interest nominations through the two-year window sale process.

· The system will maintain a history of the entire sale.

· The history will be editable.

· The history will be stored as a permanent record The system will have functionality to maintain records of monies collected for all sales for the life of the sale.

The system will provide a reporting mechanism, and will generate reports:

· Statistics for WO

· Bidder Sale Report

· Sale list (table)

· Sale results

· The system will provide functionality to create customized reports (“Ad-hoc” reports).

The system will access available spatial applications/services and provide legal descriptions to spatial application/services in order to create shape files. The development of shape files can occur at any phase of the lease sale process, including shapes files for nominated parcels or parcels included in preliminary sale list, final sale, day after or 2 year window.

The system will provide electronic sale data entry.

· Entered data items will be sufficient to fulfill the requirement of maintaining sale history.

· The system will link with existing systems which may act as a repository for sale data.

The system will provide printing capabilities for all reports.

The system will provide on-shore O&G and Geothermal leasing business rules and capabilities only.

The system shall store/retain all entered information in the database. The information will be available for analysis, reporting and generating lease forms.

Form letters/notifications: data will be used to automatically generate the documents in the appropriate format (either email or printed for mailing).

These specifications provide high level workflow diagrams for use by the developers. The automation of these workflows will be a part of the initial release. The information tracked by the workflows will be available for reporting and ad-hoc queries.

On-line help information will be available to the users for every data element used in the system. The information on the on-line help shall be maintained by the WO Lead based on permissions. The use cases in the administrative section shall determine what permission levels are required to access a specific function. On-line help can be in the form of text, links to laws, regulations, or manuals, or brief videos. Help can be specific to a data field, a process/workflow, a section, or a screen/window.

Global Business Rules:

1. The system will be browser-based.

2. The system will automate all processes relating to leasing oil and gas parcels excluding NEPA (already automated in ePlanning), geospatial processing (provided by available GIS services/applications), and accounting and receipting functions performed in CBS. The system will replace the manual and semi-automated lease sale processes currently practiced in various BLM offices with one central system.

3. The system will provide a capability to allow external programs to interface.

4. The system will provide a browser-based user interface allowing for common Expression of Interest (EOI) generation (by internal and external users) and utility tasks, including reporting.

5. The system shall be 508 compliant (American Disability Act).

6. The system shall meet DIRM, Bureau, and Department of Interior security requirements.

7. The system will automatically create and manage the following information for each step in a workflow and/or when a record is created or modified:

a. Action taken

b. Username (Active Directory for internal users, provided name for external users)

c. Date and Time

8. All dates in the system must be valid dates.

9. Display of date format can be selected by the user; the default will be mm/dd/yyyy.

10. All codes in the system will be displayed with the code and code text.

11. Deletion of data will be strictly limited by role.

12. All codes and acronyms in system will be stored and displayed in upper case.

13. A user can create, update, or delete information based on:

a. User has the proper permission

b. User’s office is within the administrative state. Any user with the proper permission can access any record within their administrative state. The administrative state may have one or more geographic states assigned; therefore permissions to all assigned geographic states are implied. Users from other administrative states can be granted access as needed.

c. WO and NOC users can see all data

14. For any use case that returns multiple records for viewing or selection the user shall be able to sort the list by any data element. The use case will describe the initial sort order but the user can re-sort the list.

15. All processes indicated in appendix D and E will be included in the initial release of the system unless noted in the specific use case.

16. All windows will have the capability for the user to print the contents of the window.

Oil and Gas Specifications System Diagram

Expression of Interest Nominations of mineral lands may be received for consideration of oil and gas leasing through Expressions of Interest (EOI), Pre-sale Offers, or other Federal nominations.

Note on the business process/workflow diagrams:

These diagrams have three horizontal swim lanes. The middle lane displays the sub-processes for the subject business process. The bottom lane displays processes for entities outside of BLM. The top lane displays other processes within BLM, including the previous and subsequent NFLSS processes. Not all processes are required, some execute as needed. The arrows represent information flows such as nominations, requests, notifications, etc. In general all information is shared on the NFLSS platform. Some diagrams include more than one process.

Submit/Enter Expressions of Interest/Nominations, Bureau Motions, and Pre-Sale Offers for Lease Sale Description A customer or SO user will input the Expression of Interest (EOI) into the system. The information must be stored with the ability to access for future changes. Parcels for potential sale may come from:

· Online submittal by the customer (automatic notification to SO adjudicator)

· Other submittals entered by SO user (written request/letter, email, fax from the customer)

· Bureau Motion entered by SO user

· Presale Offers from the customer entered by SO user

Future version will allow the public user to enter pre-sale offers.

Use Case ID Pre-Condition The entry screen is available on the web.

Post-Condition Nomination of land for O&G lease sale is saved within the system. A Nomination/EOI number has been established.

Use Case Flow of Events

· Customer Name - If customer name is not entered then the system will insert the wording ‘Nominator’

· Address, City, State, Zip code, and Country (Optional)

· Contact Information may include phone, fax, and e-mail

· Land Description will be entered based on selection from set values. For example: selection of a state will determine what meridians values can be selected, meridian will determine which townships values can be selected, township will determine range, and so forth.

· The user must select or enter: geo state, meridian, township, range, section, survey type, and subdivisions. If a subdivision was entered but the survey types was not entered then default survey type to ”A” indicating aliquot.

· Entry of land below the section level is mandatory; the customer will be indicating all land below that level.

· Determine the administrative state office receiving the EOI. Based on the land description entered the system will determine which admin state office will receive the EOI. For example if the land resides in Utah then the state office is Utah. The system will not allow selection of land for multiple admin states.

· The system will allow selection of land for multiple geo states that belong to the admin state.

· Surface owner information – the user can indicate federal surface or other. If ‘other’ was selected then the user shall be able to enter one or more occurrences of name and address.

· The user can indicate if U.S. owns only a fractional interest in the mineral estate.

· The system will derive the acres from the land description table.

Design constraint:

· The public user’s entry is outside the BLM’s firewall. The developers will determine how and when information is moved between the BLM’s firewall consistent with BLM/DOI security requirements.

· The land description values are derived from LR2000 the information will have to be extracted for the public user’s access. See appendix B for technical issues.

· To assist the entry of the land description the system will auto fill (meridian, township, and range) of the next line of land description if the user starts at the ‘Section’ data field.

· Entry is restricted to only one administrative state but multiple geo states belonging to the administrative state is allowed.

· Foreign addresses are allowed so the data fields will be expanded for country, providence, and foreign zip codes.

· The user shall be able to designate the submission type:

· Nomination/EOI

· Pre-Sale Offer

· Bureau Motion

· Customer Name - If customer name is not entered then the system inserts the wording ‘Nominator’

· Address, City, State, Zip code, and Country (Optional)

· Contact Information may include phone, fax, and e-mail

· Land Description will be entered based on selection from set values. For example: selection of a state will determine what meridian values can be selected, meridian will determine which townships values can be selected, township will determine range, and so forth.

· The user must select or enter: geo state, meridian, township, range, section, survey type, and subdivisions. If a subdivision was entered but the survey type was not entered default to survey type to ‘A’ indicating aliquot.

· Entry of land below the section level is mandatory for PLS states; the user will be indicating all land below that level.

· The system will not allow selection of land for multiple admin states.

· The system will allow selection of land for multiple geo states that belong to the admin state

· Surface owner information – the user can indicate federal surface or other. If ‘other’ was selected then the user shall be able to enter one or more occurrences of name and address

· The user can indicate if U.S. owns only a fractional interest in the mineral estate.

· The system will derive the acres from the land description table as the initial value but the SO user can modify the information

· If the entry is for a Pre-Sale Offer then the user must enter an Pre-Sale Serial Number Design constraint: The system will take into account the BLM needs to access the same form/entry screen as the public. The same business rules will apply.

If the user has not entered any information to be contacted by (phone number, fax number, email address, or mailing address) then the system will issue the following warning message:

“The BLM no longer requires you to provide your name or address on an EOI. You may continue to provide this information for contact purposes; however, the BLM will make this information available to the public. If you consider your name and address to be confidential, do not include it in your EOI. However, if your contact information is not included the BLM will be unable to contact you if we have questions regarding the submission.”

If contact information is provided, nominator will be required to check a box stating “they do not consider their contact information to be confidential”

The system will create a working copy of the LDs in the nomination worksheet that will be used by the SO user.

For each land description entered, the system will generate a land description ID.

Design constraint: The original document (EOI, Pre-sale offer, or Bureau Motion) must be saved and cannot be modified. From this point on the SO users will be working with another instance of the information.

RTM Entry The public user shall be able to enter an EOI.

The BLM user shall be able to enter an EOI, Pre-sale offer, or Bureau motion.

Accept/Review Nominations Description The SO user will review the land description of the nominations.

Use Case ID Pre-Condition A customer has submitted an EOI or a SO user has entered an EOI, Pre-sale offer or bureau motion.

Post-Condition Submission has been reviewed. EOI number has been established.

Use Case Flow of Events

· All land descriptions from nomination records submitted from process 1.1

· Land description must have a status of blank/null

· State nomination information for the user

· Meridian

· Township

· Range

· Section

· Survey Type

· Subdivision

· Acres

· Land Type

· Percent of U.S. Interest

· Split Estate Information

· EOI Number

· Pre-Sale Number

· Former Lease Numbers

· Remarks

· County

· BLM Field Office

· Other Agencies (SMAs). For example, Forest Service - FS, Bureau of Reclamation - BOR, etc. Original derived information can be modified by the user.

Design constraint – a land description can derive multiple occurrences of county, BLM field office, and SMAs. Since the derived information can be over-ridden by the user. The information must be stored versus generated.

The SO user shall be able to review land description nominations.

A.1.1 Acknowledge EOI, Pre-Sale Offer, or Withdrawal Description An acknowledgement by the BLM of the receipt of the Nomination/EOI, Pre-Sale Offer, or Withdrawal is returned to the customer. This process is optional and can be performed at a later time.

· Online submittals automatically acknowledged by the system

· Other submittals we will acknowledge receipt of EOI by system-generated letter.

· Email acknowledgement when email address is provided

· Generate address labels when acknowledgement is via postal mail Use Case ID Pre-Condition Nomination/EOI, Pre-Sale Offer, or Withdrawal has been entered.

Post-Condition Acknowledgement has been sent. Nominations are now ready for adjudication.

Use Case Flow of Events

· Any Nomination/EOI that does not have an acknowledgement created date.

· Any Pre-sale Offer that does not have an acknowledgement created date.

· Any withdrawal that does not have an acknowledgement created date.

· The system will not allow the SO user to select any record if there is no email address or mailing address. The system will display this type of record with an appropriate message: “Acknowledgement letter will not be created – no mailing or email address.

· Nomination/EOI Number or Pre-Sale Offer Serial Number

· Customer Information (Name, Contact, Address, City, State, Zip Code)

· Subject: Acknowledgement of Receipt

· Date Nomination Received

· The user will be able to select the SMA address and phone number

· Land Description (Meridian, Township, Range, Survey Type, Subdivisions)

· Status

· BLM Contact Phone

· Signature Block The system will insert the current date into the acknowledgement created date.

The SO user shall be able to generate acknowledgement letters for Nominations/EOI, pre-sale offers, and withdrawals

Prepare Mailing Labels Description A mailing label will be created for any letters created for notification to the customer via mail. For example any letter/form that will be utilized for mailing, drawings, etc.

Use Case ID Pre-Condition A process has created a letter or form that will be mailed to the customer.

Post-Condition The letter or form can now be mailed.

Use Case Flow of Events

· Nomination/EOI ID/Serial Number

· Customer Name

Design Constraint: the user should be able to indicate or select from a list containing manufacture and label type. This information should equate to the number of labels on a page and the size.

· Customer Information (Name, Address, City, State, Zip Code)

The SO user shall be able to generate mailing labels.

Create Nomination Worksheet Description A nomination worksheet is dynamically created view of all information relative to a submitted nomination and can be used for displaying, editing, and reporting a nomination. A nomination worksheet can be used as a checklist for the Adjudication process. A nomination/EOI land description can belong to one or more nomination worksheets. A nomination worksheet can have one or more land descriptions. Each land description will have a status and be assigned a sales date if the status indicates it is available for lease.

Use Case ID Pre-Condition Nomination has been entered.

Post-Condition Land descriptions are now available for updating via the nomination worksheet.

Use Case Flow of Events

· Nomination/EOI Number:

· Parcel ID Number:

· Sale (mo/yr):

· Pre-sale No.:

· LDs: MTRS; Acres; % US Interest; Land Type (A or P); County; BLM FO; SMA, Split Estates (yes/no). Split estates will not provide detail information on the nomination worksheet, just a yes/no to indicator if there is detail information.

· Former Lease Numbers (must accommodate multiple nominations/EOIs);

· State

· Completed by:

· Reviewed by:

· Remarks Field The SO user shall be able to sort the display by any field.

The SO user shall be able to select any record for processing

· Original submittal of the nomination

· Status history

· SMA detail

· History of all forms generated

· Attachments

The SO user shall be able to generate the nomination worksheet.

Withdraw Nomination Description A nomination can be withdrawn or partially withdrawn.

Use Case ID Pre-Condition The submitter of the Nomination sends a withdrawal request.

Post-Condition The Nomination will be withdrawn, but will remain in system.

Use Case Flow of Events

· EOI Number

· Pre-Sale Number

· Customer Name

· Date of Receipt

· County

· Field Office

· LD

· EOI Number

· Pre-Sale Number

· Parcel Number

· Serial Number

· Customer Name

· Sale Date

· Date of Receipt

· Land Description

· If there are duplicate land descriptions and all their status are “DUPL”

· Then the system will change the status to “PEND” for the duplicate land description with the earliest nomination date.

· The EOI status is set to ‘Withdrawn’

· The status for each land description is set to ‘Withdrawn’ If specific land descriptions were selected

· If the land description status is set to ‘Withdrawn’

The SO user shall be able to withdraw a nomination/EOI.

Perform Adjudication / Determine Land Status Availability A nomination may be filed for available lands prior to a competitive sale. The BLM determines land availability, surface and subsurface rights, and existing oil and gas leases. BLM users conduct research to determine if the lands included in a nomination are available for leasing.

Maintain Duplicate Land Description Information Description Nominations may contain multiple requests for the same land from different customers. Therefore, land Descriptions that are found in other nominations must be identified.

Use Case ID Pre-Condition Determine land availability.

Post-Condition Parts of LDs of nominations that are contained in other nominations will be noted.

Use Case Flow of Events

· Omit any land description that has a land description status of:

· Withdrawn from nomination

· Sold (Competitive or Non-competitive)

· EXP2Y

· DUPL

· The user can select other data fields and values to further filter the information.

· Any duplicate lands for each land description. Each land description will be compared down to the quarter/quarter. If a land description stops at a higher level (for example section) then all sub divisions below that level are assumed to be contained within the description. For example section implies all quarters, quarter implies all quarter/quarters. The possibility exists that duplicate LDs could contain a smaller piece of the land within the LD that is a portion of the same land and not be exactly the same.

· Each land description that is a potential duplicate will be linked to the associated potential duplicates.

· The duplicate nomination and the specific LD of those nominations and their status.

· LD having a duplicate record

· Specific LDs of the identified duplicate(s) The information will be sorted by the land description: Geo state, meridian, range, township, section, quarter

· Status

· Status date

· Status comments

· Parcel ID Number

· Parcel Number

· Serial Number

· EOI Numbers

The user shall be able to generate the duplicate report.

Advance Notification to the Field Office Description Due to the number of land descriptions the work load impact to the field office may be great. This process gives the state office the ability to notify the affected field office that records may be ready for an early review.

Use Case ID Pre-Condition Land has been identified for review Post-Condition Field office can start a review.

Use Case Flow of Events

The SO user can send a notification to the FO user.

Record Duplicate Land Description Review Decision

After the system has identified that there may be possible duplicate land descriptions, the SO user will research the information. Based on the review a decision about the duplicate land will be made and recorded in the system.

Use Case ID Pre-Condition Land has been identified as possible duplication. The SO user can conduct a review of the duplicate lands.

Post-Condition Land description status is updated.

Use Case Flow of Events

· EOI number

· Land Description

· Sorted by: geo state, meridian, range, township, section

· The SO user may split the land description. The user will set the land description status for each subdivision.

· The SO user can set the land description status.

· If a land description is a duplicate and does not have the earliest submission date, the status will be set to DUPL.

· If it is determined to not be a duplicate, the link to the associated potential duplicates will be deleted and the status remains blank.

The user shall be able to update the land description status.

Determine Disposition Description SO users will review parcels and determine their availability for leasing. Allow the user to indicate availability in the status of LD. If the user determines an LD is not available, allow the user to enter reason(s) (both drop down categories and text). Examples of categories:

· Etc.

· Run LR2000 Geo Report

· Review LR2000 for records with Federal Interest on Acquired Lands

· Review LR2000 for records with sub surface rights

· Review LR2000 to create survey type report

· Review Oil and Gas plats for existing leases

· Review Historical Index

· Check for conflicting Executive and Secretarial Orders

· Review land patents (Government land Office records)

· Review for existing land restriction conflicts

· Review for conflicting land withdrawals

· Review for conflicting land exchanges

· Review for existing land restriction conflicts

· Review SMA areas

· Review includes oil and gas Plat and supplemental plat Design constraint: The reviews above will not be automated in a workflow but the workflow should indicate that land status was determined. Possibly have an automated checklist with a Yes/No answer to “was the review/check done” and a Yes/No if it was OK. If not OK, then allow/require an explanation in a text box or attach a file. Also consider situations where N/A is an appropriate answer.

Use Case ID

Pre-Condition The SO office user will review the availability of LDs for each nomination and is ready to update the status in the system.

Post-Condition Nominations have been reviewed and the results of the review have been recorded.

Availability of nominated LDs have been determined.

Use Case Flow of Events

· EOI Number/Serial Number

· Customer Name

· Date of Receipt

· County

· Field Office

· LD

· Nomination worksheet, or

· Sorted list selected by the user

· Pending (“PEND”) if available for leasing

· Appropriate status if not available for leasing

Upon determination of the disposition the information is entered into the system.

Acknowledge Unacceptable Nominations Description This function can be accessed at any time during the lease sale process when it is determined that the nomination is unacceptable. A letter is sent to the originator stating a problem has occurred with the acceptance of the nomination.

Use Case ID Pre-Condition A nomination has been received Post-Condition Nomination is not acceptable.

Use Case Flow of Events

· EOI number

· Customer name