L14PS00888_Exhibit_1_Mock_Task_Order_Revised.pdf

Division of Information Resource Management

Document Title: Exhibit 1 – Mock Task Order 1 - PWS

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

Solicitation Number: L14PS00888 Date: 9 Oct 2014

Contract Number: TBD Date: TBD ePlanning Mock Task Order for Application Operational & Maintenance and Support

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

1.0 BACKGROUND

The ePlanning application is a relational database approach to creating, managing, sharing, and reviewing land management and NEPA information in accordance with paper and digital publishing requirements. Textual and related spatial information is created and shared in a team-based environment using the Internet, Geographic Information Systems (GIS) technology, and dynamic content management.

Although created by the BLM to support the land use planning process, ePlanning is flexible enough to support a range of projects for any federal agency.

ePlanning is built around a central database within which all content is stored. It is a suite of applications consisting of custom code and commercial off-the-shelf (COTS) products. The fundamental concept behind the ePlanning system is the Interactive Digital Document, which provides a dynamic and interactive link between textual information and the geospatial data supporting and describing the text.

The Interactive Digital Document provides government and public users with web-based documents, enabling them to read text, submit comments, and view maps related to the data. Users can submit comments in a secure online environment. The ePlanning toolbox is powered by XML-based text and digitally integrated geospatial data.

Internally, project team leads, editors, and other users can perform the following tasks:

Write, edit, share, review, and approve project text

Publish multiple documents to the web, in paper format, or saved to a CD-ROM; HTML version documents include full interactivity between textual and geographic data

Post a Java-based public comment form on the HTML version of the document

Accept, submit, view, track, assign, code, group, summarize, and respond to public comments

Create a NARA-compliant administrative record

Incorporate GIS data used in the State and Field Offices

Establish a database of information for future post-project activities such as implementation, monitoring, amendments, maintenance, and tiering

1.1 Technical System Description

The ePlanning system is comprised of COTS, customized COTS, and custom components. The current version of ePlanning is estimated to be 40% custom code and 60% COTS. Below is a listing of the components with a description of its function:

Documentum: Also known as Webtop. Documentum is the document management application.

Originally a COTS product but has become highly customized.

Arbortext: Arbortext is the COTS software that is used to create XML documents. By putting the text in XML format, they can be printed in any format selected by selecting a desired style sheet which imposes a predetermined set of rules.

Back Office: Back office is a completely custom component used to setup web pages to be published to the public.

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

Front Office: Front office is a completely custom component which is utilized by the public to view and comment on published documents (Land Use Plans and NEPA documents)

CommentWorks: CommentWorks is a COTS product that is utilized by BLM to gather comments from the public. The application is also used to determine what steps will be taken to respond to public concerns.

GIS: ESRI Arc Map v10.1 is the COTS product used to create maps to be included in XML documents.

2.0 OBJECTIVES

The objective of this mock task order is to provide operational and maintenance support to the system so that it continues to comply with federal regulations (OMB, DOI, BLM, etc.) as well as maintain and surpass the high standards that BLM has for National Applications.

3.0 SCOPE

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

The scope of this mock task is to support the system and continue to comply with federal regulations as well as maintain and surpass the high standards that BLM has for National Applications. Our vision is to provide support to the system (in form of releases; recommended quarterly at minimum) addressing user submitted bugs, new policy/regulations, and/or new features so that the application remains user friendly, adheres and enforces current or new policy and procedures, and continues to support the BLM Mission. Potentially, additional releases beyond the stated quarterly release (i.e. emergency, patch, or scheduled releases) may be required depending on day to day business of BLM.

This investment is expected to continue to maintain and surpass the high standards that BLM has established for the National Applications and facilitate compliance with federal regulations as established by OMB, DOI, and other entities.

The system requires contract support as detailed in the following tasks section. This work will include software development, integration, test, maintenance, audit support, system analysis, impact analysis, documentation, reports, and progress monitoring using reporting procedures and measures of performance in accordance with best practices of the IT industry.

The contractor shall provide all personnel, administration, and management necessary to fulfill the objectives of the contract and ensure its success.

4.0 TASKS

In addition to the tasks noted in the base contract the following shall be completed by the contractor.

Of the following the primary tasks for this period of performance will be releases ( both bugs and enhancements tickets), report support, O&M, billing support and project documentation support.

The Contractor shall furnish the necessary personnel, equipment, material and/or services and otherwise do all things necessary for or incidental to the PWS as set forth below.

It shall be noted that the contractors may be required to work cooperatively with other contractors/entities performing their own dynamic BLM work and initiatives that may or may not have impact on this overall task. If the situation arises where this relationship/initiatives may/will impact the deliverables of this task it is the responsibility of the contractor to bring the situations to the attention of the COR/PM immediately.

All tasks noted in this section are to be performed at the direction of the COR.

4.1 Program and Project Management Support

The contractor shall provide Program and Project Management support activities for their technical staff as well as in support of activities required for the system including:

1. Developing and maintaining a critical milestone schedule that documents the most important schedule issues for management attention.

2. Providing recommendations to address any schedule or cost variance associated with project plans.

3. Support the COR in analysis and classification of reported items as O&M, Enhancements, or Change Request

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

4. Supporting issues management and tracking.

5. Supporting change management and risk management activities of the NOC.

6. Coordinating and planning meetings, where appropriate, including program management reviews, and walk-through/design reviews.

7. Providing project progress reports and other management documents as specified in project deliverables and as required by the government management.

8. Ensuring the integration and synergy between interconnecting systems and provide recommendations for simplification of interconnections as they arise

9. Ensure adherence to the all departmental and bureau policy

10. Monthly and weekly status reporting in a format agreed upon by the COR

11. Report on ticket reviews, analysis, solution design and time estimating as request by COR

Anticipated Deliverable(s): Project Schedule, Status Reports, Analysis Reports Acceptance Approach & Criteria: Federal PM and COR review for quality and accuracy.

4.2 Operational & Maintenance Support

The contractor shall provide operational & maintenance support for the system which at times may require system release(s) throughout the POP. Primarily O&M can be defined as keeping the system running and up to date with current standards, policy, DOI approved system-wide software updates, technology and SRS expectations as detailed below. The high level overview of the services required to do such is but not limited to:

1. Audit Support

2. Systems & Requirement Analysis and Impact Analysis

3. Bug fixes

4. Maintenance Releases

5. Database Support

6. Data cleanup Support

7. Support for (may require releases)

a. policy change

b. policy and program (WO) change

c. infrastructure changes (i.e. F15k)

d. operating system and peripheral change/upgrade (i.e. Win7/IE8/IE9 etc)

i. This includes the certification of systems on top five browser market share as necessary

e. And maintenance to system for changes to BLM baseline software (such as Hyperion, Dataflux, MS Office, IEx, Dreamweaver etc)

f. maintaining the system on vendor supported software at all times

g. database change/upgrades (i.e. Oracle 11g)

h. core system software upgrades (i.e. Esri 10.x)

i. interconnections/interfaces to other national applications

j. 508 Compliance

8. Emergency/patch fix release

9. Database management and administration

10. Reports (Development, Maintenance, Document and Technical support)

11. Ad-Hoc Report support

a. Specifically the design of complex ad-hoc reports by special request of the COR

12. PCMB Support

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

a. Provide analysis, estimating, and/or recommendations in preparation of PCMB but does not include participation in the PCMB except at the invitation of the COR.

13. Supporting the Business User Rep at the direction agreed upon by the COR/PM

a. Not being the Business User Rep

b. Typically includes troubleshooting and analysis and tier 2 or greater support,

14. Release management

15. System use analysis

16. System monitoring (including logs, security, etc)

17. System troubleshooting

18. Project data call collection and preparation support

19. Data Extracts and transformations

20. Preparation to the business on data call support (FOIA, Department, OMB, BLM, etc)

21. Interface maintenance

22. Support BLM Infrastructures moves as requested and planned by Operations or Systems

Engineering.

a. For example: F15k migrations, Establishment of new BLM DMZ etc. Moves to new BLM

DMZ environments in partnership with NOC SE team.

Tickets where appropriate for O&M work will be established throughout the POP for documentation purposes.

Anticipated Deliverable(s):

System operating in the production environment

System Releases as required to meet requirements of 4.2

Customer service

Acceptance Approach & Criteria:

>95% system availability( o COR advanced approved downtime is not included in this factor o Operational or Network downtime is not included in this factor)

Customer Satisfaction (System Users, User Rep, PM, and WO Program Lead)

System Error/Defect free

Technical Architecture compliance

4.3 Documentation Support

The Contractor is responsible for providing to the BLM complete, accurate, and timely documentation of the System. The Contractor must create and/or prepare updates to the Systems Documentation to incorporate all changes, corrections, or enhancements to the System with each O&M Release. Updates to the Systems Documentation must be delivered to the COR prior to BLM acceptance of the change, unless otherwise agreed to by COR.

Contractor staff shall provide documentation to the Government staff on all tasks and projects assigned as required. Primarily this documentation support specifically includes updates of the following documents per release or annually whichever happens more frequently:

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

Update Frequency

Document Type

W/ Major

W/ Minor

W/ Emergency

COR

Request or Annually Minimum

System Requirements Specification (SRS) X U U

Interface Requirements Specifications (IRS) X U

Software Design Document (SDD) X U U

Data Management Plan (DMP) X U

Requirements Traceability Matrix (RTM) X U

Computer Systems Operating Manual (CSOM) X U U

Operational Baseline Release Reports (OBRR) X X X

Test Baseline Release Reports (TBRR) X X X

Version Description Document (VDD) X U

FQT Test Plans X U

FQT Test Results X U

Request For Change (RFC) Draft X X X

System & Requirements Analysis and Impact Analysis

X

Software Development Plan X

System Security Plan (SSP)

Technical Vulnerability Assessments X

Risk Management Plan

Privacy Impact Notice X

Privacy Impact Assessment (PIA)

Business Impact Assessments (BIA) X

System of Records Notice (SORN)

IT Contingency Plan inputs X

Training Guide/Manuals/Materials X

X = Resubmissions of full document

U = Updates to last Major Submission as applicable

Specific addition documentation will be clarified through technical task clarifications. All documentation, programs and development shall remain the sole property of the Federal Government.

Most of this documentation already exists with the current system in which case updates at a minimum will be expected.

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

Documentation deliverables shall be provided to the government in draft format at which time the COR will have 10 business days to review and comment on the draft. The contractor shall at that time incorporate all comments and suggestions into a final version and deliver to the government according to section 5.2 and 5.3 of this task order.

Anticipated Deliverable(s): Completed documents on a release or annual basis.

Acceptance Approach & Criteria:

Timeliness

Quality

Accuracy/Correctness

4.4 Security Support

4.4.1 Application Development

Developers

Developers are encouraged to refer to this Security Checklist for Application Development document, the CWE/SANS Top 25 Most Dangerous Software Errors, the OWASP Top 10, and other references identifying common programming errors. Utilizing these references, developers are encouraged to include the recommended secure coding practices to ensure all known weaknesses are mitigated and avoided.

In addition, NIST SP 800-64, Security Considerations in the System Development Lifecycle, the OWASP Code Review Guide, the OWASP Testing Guide, and the Microsoft .NET Framework Developer’s Guide

– Secure Coding Guidelines should be utilized as primary sources for secure coding practices during new development or task orders requiring changes to source code for BLM applications. Other references, as necessary, will be identified during the business requirements phase of any new development or new task order creation.

Security Development Life Cycle

For each project, task order or release, developers and DBAs are expected to include process steps, milestones, tasks, and deliverables accounting for the development, review and testing of secure coding practices. The following is expected to be included in each project plan or development plan:

4.4.2 Security Business Requirements

Source Code Review Develop Security Test Cases Develop Positive Requirements Develop Negative Requirements Source Code Analysis (with automated tools, as necessary) Source Code Analysis Results Source Code Analysis Results – Solutions and Fixes http://cwe.mitre.org/top25/ https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project http://csrc.nist.gov/publications/nistpubs/800-64-Rev2/SP800-64-Revision2.pdf https://www.owasp.org/index.php/OWASP_Code_Review_Guide_Table_of_Contents https://www.owasp.org/index.php/OWASP_Code_Review_Guide_Table_of_Contents http://msdn.microsoft.com/en-us/library/d55zzx87(v=VS.71).aspx http://msdn.microsoft.com/en-us/library/d55zzx87(v=VS.71).aspx

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

Functional Security Test Perform Vulnerability Testing Vulnerability Testing Results Validate Minimum Security Requirements Minimum Security Requirements Results – Vulnerability Remediation Performed Functional Security Testing – UAT Migration Approval Step

Acceptance Security Test Perform Vulnerability Testing Vulnerability Testing Results Perform Configuration Testing Configuration Testing Results Configuration & Vulnerability Testing Results – Remediation Performed Acceptance Security Testing – Production Migration Approval Step

Security Testing Deliverables Deliverable Acceptance and Approval

Business Requirements

Project plans for all new development and/or task orders should include the following, at a minimum:

Project Plan Activities Source Code Review Activities Development of Security Test Cases Development of Positive/Negative Requirements Source Code Analysis Functional Security Testing Vulnerability Testing Validation of Security Requirements UAT Security Testing Timeframe Remediation Activities

Deliverables

Documented Test Cases/ Positive & Negative Requirements Source Code Analysis Results Source Code Analysis Results – Solutions and Fixes Vulnerability Testing Results Vulnerability Remediation Report Process/Procedure document creation and/or updates Security Control Implementation Description creation and/or updates Plan of Action & Milestones (POAM) Weakness Completion Verification Form Closing Requirements (as necessary)

Approvals/Sign-offs

Business Requirements Acceptance Migration

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

Production Migration Deliverable Acceptance

Applicable Security Controls: AT-03, SA-08, SA-09, SA-11

4.4.3 System Patching - The SP shall promptly install security relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during any sanctioned security assessments, continuous monitoring, incident response activities, or information system error handling event shall also be addressed expeditiously. The SP are encouraged to use resources such as the Common Weakness Enumeration (CWE) or Common Vulnerabilities and Exposures (CVE) databases in remediating flaws discovered in organizational information systems. By requiring that flaw remediation be incorporated into the organizational configuration management process, it is the intent of this control that required/anticipated remediation actions are tracked and verified.

4.5 System Specific O&M Support

This section outlines unique maintenance requirements, required by this particular system, which the contractor shall perform:

ePlanning COTS review/upgrades. Review all ePlanning COTS solutions and recommend/upgrade as appropriate. The deliverables are updated documents (VDD, SDD, SRS, FQT Test Plans, CM Documentation, CSOM, ePlanning User Guide) and successful implementation to all COTS environments.

Anticipated Deliverable(s): COTS analysis and Associated production upgrades.

Acceptance Approach & Criteria:

Timeliness

Quality

Accuracy/Correctness

4.6 System Specific Ticket Work

This section outlines specific known ticket work required for the system. In accordance with the guidelines outlined in section 5.0 of this task the contractor shall deliver the following ticket functionality/fixes/modifications to the systems production deployed codebase:

Table

Request ID Description NOTES https://cwe.mitre.org/ https://cwe.mitre.org/ http://cve.mitre.org/

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

INC00000001

ARBORTEXT

enhancement:

widows and orphans

Remedy 7 incident # INC000000802416

Is there something in our style sheets or a tag in arbortext that I'm missing that would turn on widows and orphans protection? I'm finding in my builds that there are a lot of these in my docs and reviewers are complaining. Jon

ER Note 05222013- It appears the page breaks in Jon's documents are causing the format of the document to be off. This is affected by the type of default style sheets. This is a possible PCR to be discussed about as a group.

ePlanning Team (06/03/2013): Group decided that issue is definitely a PCR and the tech team will be looking into the cost to fix. cc

Look into level of effort.

INC00000001

BACK OFFICE

MAPS: Text-to-Map function

Remedy 7 incident # INC000000829220

Incorporate text to map functionality into current system. Ticket entered to track progress.

We have three requirements gathering meetings to date, and have a draft Text to Map requirements document. This has been pushed out due to higher business priorities, and planned to be incorporated into a quarterly release during 2013.

INC00000001

FRONT

OFFICE:

Modernize Look and Feel of Front Office

PCR #19

Remedy 7 incident # INC000000872478

PCR_eP2013_AUG_2013_019: From the blm.gov site we would like to have the following included on the Front Office site: BLM logo, the BLM border, and a similar header. Then add the map detailed in PCR_eP2013_AUG_2013_014 to the page. The page described above will be the home page.

Please add a menu bar with tabs for HOME, INFORMATION and

REFERENCES.

**Design Architecture is pending approval.

INC00000001

ARBORTEXT:

Convert Word and PDF Docs to XML Docs

PCR #18

Remedy 7 incident # INC000000872485

Provide a service to convert Word or PDF documents into XML documents.

http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018536 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018536 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018554 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018554 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018597 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018597 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018606 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018606

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

WEBTOP:

Program area Changes PCR #15

Remedy 7 incident # INC000000872487

Change project statuses based on James Pavey’s recommendations. (See attached table). Changing program fields and adding sub program field in Webtop BO/FO(addition, consolidation, deletion and data conversion).

INC00000001

WEBTOP:

Script for Name Change

Remedy 7 incident # INC000000874156

Please write a script that will run through the entire ePlanning system changing a given name to the NEW name provided. This will be used when system users change their legal name so that they can access their old projects and so on.

INC00000001

ARBORTEXT:

Arbortext add on allowing voluming and large maps

Remedy 7 incident # INC000000826706It would be very useful for RMPs if we had the capability to create volumes in Arbortext while maintaining the integrity of the table of contents . We normally have to break the RMPs into volumes for the print version (and it is a good idea for the web versions to make smaller file sizes). We have to manually break up the print version and create TOC and title pages for each volume. It also breaks the bookmarks in the PDFs, so you have to recreate the bookmarks manually. It would also be useful to be able to insert large maps. We often have 11x17 maps that are too large to insert into an image object in Arbortext. By the time you shrink them down to fit a 6.5 inch width they are unreadable. Also they are not listed in the table of contents, unless you insert as a figure. Therefore, we create separate PDFs and link to the document using unlinks and create a map appendix of unlinks to create a list of maps in lieu of a TOC. This then creates other issues for task assignments.

INC00000001

CITRIX:

Citrix/Webtop

/BO:

Eliminate multiple log-ins

Remedy 7 incident # INC000000852170

Discussion: the system change may not work for Comment Works, but would eliminate the user from having to log into Webtop or Back Office once they have logged into Citrix. If a user logs into Citrix and then does not open Webtop or Back Office within 15 minutes they would need to re-log into Citrix. Leah Baker felt as though the cost is too high for the functionality that would be provided. Other members felt that the fix would be beneficial.

INC00000001

FRONT

OFFICE: RSS

feeds added to FO for constant updates

Remedy 7 incident # INC000000852181

Discussion: some members felt that this feature may be similar to sending out email notices when a project has changed. It was explained that the RSS fees would be a general overview of new events occurring within the BLM nationwide that could be sorted by topic which is a different feature all together. Jim and others felt that it would be a nice feature, almost expected today, but that it is a low priority.

http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018608 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018608 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018614 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018614 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018629 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018629 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018636 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018636 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018990 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018990

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

FRONT

OFFICE

MAPS: Maps Page redesign for FO

Remedy 7 incident # INC000000848425

1) The maps page should require both the map title and map description, each in separate columns

2) the maps page should require the release date column, and open comment period column

3) The maps page should require a "comment here" button, which would enable a quick link to the associated interactive document, at the maps page to place comments, and then continue on with the normal comment wizard application.

This is a future enhancement, and we will be discussing this requirement as a business requirement to determine when to fit into 2013 release schedule.

INC00000002

WEBTOP: My Auth Tasks, Filter by Project field default

When a user goes to My Authoring Tasks, have the "Filter by Project" field default to NULL so that the user is forced to choose a project. This way they don't accidentally edit a portion of a project unintentionally.

INC00000002

WEBTOP:

Search feature for "Subscribe Others"

The search feature that pops up when you "Subscribe Others" does not allow searching by last name. You can only find a person by their first name. You can't use %LastName either.

INC00000002

WEBTOP:

RMP Project Templates

Make RMP template available at project creation time.

INC00000002

BACK

OFFICE:

Replicate Document Section for Summar Site

For the Summary Sites, make the Documents section look just like the Documents section of the Websites so that the section has headings like Document Name, Release Date, Available Formats and Public Comment Period. Please make sure all documents are accessible, meaning from Builds and Repository files.

INC00000002

BACK

OFFICE:

ePlanning Application Troubleshooti ng

Issue: Add the "document group" to the project web sites. This would allow users to select a group of documents that would open up in a new page like the maps section.

Notes:

INC00000003

MISC: App Issue - PCRs

Software Type: National Applications - Software Name: ePlanning

-Additional Notes- I have a few PCRs:

1. Add the Project Name to the header information, next to the Project # on webpages. The # is meaningless to most people.

http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018991 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000018991 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000020746 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000020746 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000020748 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000020748 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000020749 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000020749 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000020752 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000020752 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000021724 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000021724 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000036873 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000036873

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

2. NEPA Register: The search tool appears to be designed for use by BLMers more than for the public. The primary search fields (Field Office, Document Type, and FY) are meaningless to most of the public.

The public should be able to quickly find the projects that they are looking for by State, county, project name, or project type. Along with “State,” these should be the primary search fields, not hidden in the advanced search features. Move “Field Office,” “Document Type,” and “FY” to the advanced search options. Also, consider adding a text search field which will search for text on project sites, summary data fields, and posted documents.

3. Simplify the comment submission process. This interface needs to be simple enough that anyone with beginner-level computer skills can figure it out and use it.

a. For XML documents, the directions on the document viewing page should be clearer. Consider adding something like: “To submit a comment, select the text in the document that your comment will pertain to and then click here.”

b. The comment and personal information in the submission form should be a single page. The only buttons needed on this page are:

• Insert Highlighted Content – This should not appear as an option when commenting on PDF documents.

• Add Attachment – This generates the option to browse for and select files.

• Add Another Comment – This generates another page with personal info filled in but all other fields empty.

• Review Submission - This generates a view of their entire submission.

• Cancel – This closes the comment page.

c. The Review Page should have buttons for:

• Edit Submission – This returns them to the Comment Page.

• Submit Comment(s) – This submits the comment, generates the Submission Acknowledgement page, and sends an email containing their submission to the email address provided.

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

INC00000004

BACK

OFFICE:

Enhancement for establishing Comment Periods

When loading documents into back office, we teach users to set one name for the given document and then we upload a pdf version and an interactive version. Since there are two documents linked to one chosen document name, the document name appears twice when you create a comment period. It doesn't seem to matter which one you pick when creating a comment period, it is just confusing to the users.

INC00000005

WEBTOP: E-

planning Improvement Suggestion

Please upgrade the required Project Coordinate Location options to include self-entry of UTM's and/or PLSS or even GIS shapefiles. If nothing else, please at least include the PLSS information for ease in locating. The Lands & Realty program authorizes multiple projects on the ground each year, and their preferred method of on the ground location is through PLSS. The current method is very time consuming and frustrating when trying to locate small project areas (i.e. 30'x30') or linear features (powerlines) in areas with practically no landscape references unless zoomed in quite close. You might find that users will simply put a point anywhere on the map if it is too time consuming to locate the project area by panning and zooming in. Thank you for your consideration.

WO00000000

17557

FRONT

OFFICE: RFE -

Need more menu options under Special Interests

Application Type: National Applications Application Name: ePlanning -Enhancement Description- When the public views the search page for eplanning (https://www.blm.gov/epl-front-office/eplanning/lup/lup_register.do) and they can't find a project by the NEPA number, they need more options under Special Interests. I have had numerous people complain that this website is hard to navigate and the NEPA numbers are easily typed in incorrectly. If my livestock permittees try to find a document they are currently unable to select "Rangeland Management" or "Livestock Grazing" from the drop down menu. These are two options that need to be added.

WO00000000

30168

ARBORTEXT:

RFE - PCR

request about templates

Application Type: National Applications Application Name: ePlanning -Enhancement Description- On behalf of M. Weimer, he would like to submit a ticket for a PCMB consideration. The CX and DNA templates from Washington are quite involved with chapter headings; cover pages, etc., similar to a full-scale EA. He would like to see a shorter version of the CX and DNA available, similar to a short vs. long FONSI. If someone has a long CX they can choose to use the long template, etc. He would like this issue to go before the PCMB board.

Anticipated Deliverable(s): Production releases (in accordance with 5.0) implementing ticket features.

Acceptance Approach & Criteria:

Timeliness http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000044689 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000044689 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000059062 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=INC000000059062 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=WO0000000017557 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=WO0000000017557 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=WO0000000030168 http://ilmocop3ws3.blm.doi.net/arsys/servlet/ViewFormServlet?form=SHR%3AUnion_OverviewConsole&server=ilmocop3ap22.blm.doi.net&eid=WO0000000030168

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

Quality

Accuracy/Correctness

5.0 DELIVERY

5.1 Deliverables Table

SOW Para Title Delivery Schedule

4.1 Finalized POP O&M Schedule 20 business days after NTP

4.1 POP Re-Baselined Schedule As agreed by COR

4.1 Weekly Status Report Every Friday

4.1 Monthly Status Report 10th calendar day

4.1 Analysis Reports As requested by the COR.

Not to exceed 5 per POP.

4.2 Maintenance Releases As required to maintain

system operations

4.2 Emergency/Patch Release As required

4.3 Documentation Support As required per

release/request or annual for each document (whichever greater)

4.4 Security Requirements As required

4.5 COTS Upgrade Analysis NLT 60 days after NTP

4.5 COTS Upgrade Production Releases As agreed and approved in baseline schedule

4.6 Production Ticket Releases As agreed in baseline

schedule

5.2 Deliverable Instructions

Electronic copies of document deliverables shall be delivered to the Contracting Officer (CO)/COR using Microsoft Office (e.g., Microsoft (MS) Word, MS Excel, MS PowerPoint, MS Project, or MS Visio), or pdf for graphics unless otherwise specified at the task level by the COR. Electronic submissions shall be made via email, unless otherwise agreed by the CO/COR. Software may be compressed, provided it is self-expanding upon installation.

The Government will have up to 10 business days, unless specifically denoted below or extended by notification, to review each deliverable product and provide oral and written comments. The contractor shall review and incorporate comments or implement directed changes, after discussion or clarification from the Project Manager (PM) and submit a final version of the product as required and specified by the Government, and no later than 10 business days thereafter.

Contractor shall ensure communications are open and available to avoid delay in approving deliverables.

For all software deliverables, contractors will be required to provide a warranty period to resolve software defects of up to 120 days.

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

5.3 Release Guidance and Documentation

The Contractor shall utilize software development methodologies based on incremental or iterative software development methodologies. As such, the contractor shall provide and support multiple software releases in accordance with the government’s software delivery schedule. Each incremental or iterative release shall be subject to government review and comment if required by the COR/PM. Final acceptance for the overall product is contingent upon the acceptance of the Final Operation Baseline Release Report (OBRR) which shall incorporate all of the associated system functionality identified in the specifications referenced herein.

NOTE all the following are specifically at the direction and approval of the COR.

The contractor shall perform required Release/Enhancement Development and Implementation activities for the system including:

Requirements Analysis activities for the system including:

o Determining gaps between current and desired future business state o Verifying and Validating business requirements for a new system modules and converting to technical specifications/requirements

Release design including technical documentation such as system design, functional specifications, security analysis and documentation, training/user guides, and web-based self-training.

Delivery of TBRRs/OBRRs associated with each release (TBRR 1 day prior to planned FQT, OBRR 1 days after release)

Technical documentation, as described in the release section below

Release Management

Implementation support o Provide ongoing application support and maintenance to end-users and system administrators

Emergency/Patch Releases

The contractor shall ensure the application is available for use and shall resolve problems and incidents when identified. Fixes to problems and incidents may include modification of executable code. In the event of such changes, the contractor shall execute software testing and configuration management efforts in accordance with the government cm requirements/process. The contractor shall maintain existing interfaces to other applications. The contractor shall coordinate with the government regarding system outages and hardware/firmware or interface issues come to their attention.

Release types and deliverables requirements (unless reduced in writing by the COR) for each are listed below:

Major Release Full resubmission of all documents rebranded to match system version.

Draft RFC

Object and Source Code

VDD

SRS

IRS

Description: ePlanning for Application Operational and Maintenance Support

Conforms To: FAR 2014, FAC 2005-76 Effective Date: 25 Jul 2014

SDD

DMP

RTM

CSOM

FQT Test Plans and Tech Team Test Result

TBRR & OBRR

Training Guide Updates (if applicable)

User Guide Updates (if applicable)

Entity Relationship Diagram (ERD)

Minor Release

Updates to all required Major Release documents as required to stay current and accurate per the associated release.

Emergency Release

Object and Source Code

Release Notes

After initial installation of Emergency release the delivery of any updated documents required for majors is still expected within 10 business days of the emergency release:

6.3.3 Version Control - The contractor shall provide version control for information, documents, software, hardware and other services provided to customers in order to ensure that users are provided correct and current information. The contractor shall ensure that their staff is consistent with information they provide for solutions or in general.

6.0 PERIOD OF PERFORMANCE

The mock contract will be for a base year period plus four (4) option years.