031715_IDIQ_PWS_Oil_and_Gas_App_Dev_(3).docx

Oil & Gas Applications Development IDIQ - PWS April 30, 2015

Division of Information Resource Management (DIRM)

Oil and Gas Information Technology (IT) Application Development Support Services

Indefinite Delivery/Indefinite Quantity (IDIQ) Performance Work Statement (PWS)

Contents

1. General

The Bureau of Land Management (BLM), National Operations Center (NOC), Division of Information Resources Management (DIRM) located in Denver, Colorado has a vision to establish a commitment to excellence in delivering quality Information Technology (IT) services and systems to its customers the first time, every time.

The DIRM supports the BLM's mission by providing collaborative technical leadership, guidance, application development, engineering, and enterprise administration of BLM IT infrastructure to the whole of BLM inclusive of state offices, field offices, national centers, interagency partnerships, and the Washington Office. The division emphasizes the application of IT to meet specific business processes to improve public service, enhance employee productivity, and improve data quality. The division’s intent and commitment is to support the BLM with superior information systems and processes that help serve customers better.

The DIRM will implement an environment that is capable of yielding consistent, repeatable and predictable IT project outcomes delivering high quality information systems and services to its customers. The DIRM is committed to providing our customers the highest quality systems and IT services by improving system engineering process discipline and planning through sound project management.

1.1. Scope

This IDIQ scope includes all personnel, equipment, material, administration, and management necessary to fulfill tasks associated with system development and operate and maintenance of Oil and Gas Applications for BLM. Currently the Automated Fluid Minerals Support System (AFMSS) II and National Fluid Lease Sale System (NFLSS) are in need of immediate performance. Identification of these applications does not exclude the Government from including other future applications or efforts that fall within the scope of oil and gas application development and maintenance support.

Period of Performance - This Indefinite Delivery/Indefinite Quantity (IDIQ) contract will be awarded with a base period of one (1) year, with the possibility of four (4) option years.

This Performance Work Statement (PWS) describes a performance-based work requirement in terms of the expected service output rather than task-based or “how” the work is to be performed.

1.2. Business Objectives

The primary objective is to establish a business partnership relationship to meet a the application development needs of oil and gas based requirements. Specifically, the new contracting relationships are envisioned to fulfill the following goals:

1. Identify and secure long term relationship with capable provider for key business and technology services.

2. Streamline procurement processes to support dynamic business and technology needs.

3. Provide access to technology solutions and alternative approaches for achieving business objectives per http://www.blm.gov/wo/st/en/info/About_BLM.htmlw.

4. Continuously strive to improve applications and process automation understanding the ever-evolving IT Environment.

1.3. Background

This IDIQ is established in response to BLM need of unique and specialized application development support services to obtain specific capabilities associated with the development and maintenance of oil and gas applications meeting process, industry and regulatory compliance. BLM’s current development needs are associated with the following applications.

The current Automated Fluid Minerals Support System (AFMSS) and the Well Information System (WIS) fully support the bureau's mission-critical Fluid Minerals Inspection and Enforcement Program, Environmental Inspections, and tracking of operational approvals such as Application for Permit to Drill (APD), Well Completion Reports, and Sundry Notices on both Federal and Indian Trust Lands and Leases. AFMSS and WIS are crucial to the BLM’s implementation of the President’s National Energy Policy Act of 2005 and are now in place in all offices with oil and gas oversight responsibilities. AFMSS II is currently in need of development to replace the existing system.

The purpose of the National Fluid Lease Sale System (NFLSS) is to standardize the work flow processes and automation associated with oil and gas and geothermal lease sales. Currently, there are significant variations throughout the states doing lease sales within the same U.S. Government Statutes and Regulations. The variety of computer solutions and manual work processes has inadvertently led to an increased state of variability and capability among the BLM's offices. The BLM State Offices provide overall administration of oil and gas and geothermal lease sales and lease issuance. The application will automate and standardize lease sales process in BLM.

2. Description of services

2.1. General Requirements

In accordance with FAR Part 7.5, Inherently Governmental Functions, this PWS shall not be used for the performance of inherently governmental functions such as making decisions/policy or making approvals.

The Contractor shall provide a single point of contact for all post award communication related to this IDIQ.

The BLM will review and approve all work performed under task order prior to acceptance. The Contractor will furnish the BLM any information, data, working papers, notes, procedures, worksheets etc. which the BLM deems necessary for review and acceptance of performed work. No portion of the work shall be released to an outside party or otherwise publicized without expressed prior consent of the Contracting Officer.

All deliverables shall be submitted in accordance within timeframes and/or schedules established at the task order level and/or agreed to. Deliverables shall be submitted in a format and file type as specified in each task order.

The Contractor shall provide only personnel who are fully qualified and competent to perform their work and who possess the basic qualifications for each labor category per the Labor Categories attachment.

2.1.1. Kick-Off Post-Award Conference

Upon award, a Kick-Off Post-Award Conference will be held and will include all pertinent Contractor Personnel, BLM Contracting Personnel and DIRM Representatives.

Date: Award Date +5 days Time: To Be Determined (TBD) Location: TBD Agenda: Review of contract, define roles and discuss any questions

2.1.2. Place of Performance

In general, unless otherwise identified at the Task Order Level, the Contractor shall plan to provide its own office space, equipment, software, communications, supplies and furnishings for their personnel. For the most part, the Government anticipates that it will only provide limited office space and equipment for key personnel as necessary. The requisite place of performance and the facilities to be provided by the Government will be identified at the Task Order Level.

Requirements for on-site meetings will be identified at the Task Order Level. BLM will provide access to all required space, supplies, and facilities as needed for meetings, briefings and other required on site activities with BLM staff. Meetings, briefings, or other activities that are to be at the BLM site must be scheduled at least one (1) day in advance with the applicable Contracting Officer’s Representative (COR) to ensure space is available.

Possibilities may exist for virtual coordination between the Government and the Contractor, yet initially BLM does not have the capacity in many cases to support such coordination; it is, however anticipated that this capability will become more accessible over the course of this contract. Therefore, especially initially, any virtual coordination needs requiring expenditure will be paid by the Contractor inclusive of the need to rent space (such as renting space in the General Services Administration (GSA) Building 41 on the Denver Federal Campus), equipment, etc. in order for BLM to participate. Possibilities should be identified at the Task Order Level by the Program, yet the Contractor may also address these possibilities at the Task Order Level.

2.1.3. Federal Holidays

The following Federal Holidays are observed by DIRM which the Contractor needs to take into consideration for coordination purposes. When a Holiday occurs during a weekend, it will be observed either the Friday preceding or the Monday following for Saturday and Sunday respectively.

Attachment 1 to RFP L15PS00378

New Year’s Day, January 1st Martin Luther King’s Birthday, 3rd Monday in January President’s Day, 3rd Monday in February Memorial Day, Last Monday in May Independence Day, July 4th Labor Day, 1st Monday in September Columbus Day, 2nd Monday in October Veteran’s Day, November 11th Thanksgiving Day, 4th Thursday in November Christmas Day, December 25th

2.1.4. Core Hours of Operation

In the instance where Contractor Personnel are working at the Contractor’s own facility, the Contractor will assure that said personnel will be available during the core hours of 9:00 a.m. Mountain Time (MT) to 3:00 p.m. (MT) or as otherwise noted under each Task Order.

In the instances where Contractor Personnel are working at a directed BLM site, the core hours for the BLM DIRM are Monday-Friday 6:00 a.m. (MT) to 6:00 p.m. (MT); specific work hour requirements will be addressed at the Task Order Level.

2.1.5. Adverse Weather Conditions

During adverse weather conditions, the Contractor shall continue to provide services that have not been cancelled due to weather. Delayed-reporting or early release (for government employees) in and of itself does not constitute cancellation of requirements or relieve the Contractor of PWS responsibilities. Contractor is responsible to contact the Contracting Officer’s Representative (COR) to see if the planned activity is affected.

2.1.6. Security

The BLM places the utmost importance on IT Security to ensure that assets and information are safeguarded. BLM uses multiple layers of security starting at the Internet gateway all the way down to the individual user's permissions/privileges and their desktop configuration. The BLM also has a very active IT Security monitoring and analysis program in which systems and users’ activities are logged and analyzed. The Contractors will be an integral part of the IT Security at all layers. Each task created within this PWS will have some level of responsibility for IT Security and access to sensitive information.

The Contractor shall comply with all the Federal, Office of Management and Budget (OMB), and DOI policies, directives, procedures and memorandums in effect at BLM. Copies to be provided upon award of the IDIQ Contract.

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. Developers are required to perform secure coding practices in development as part of task order performance. 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 shall be utilized as primary sources for secure coding practices during new development or task orders requiring changes to source code for BLM applications.

2.1.6.1. 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:

Source Code Review

Functional Security Test

Acceptance Security Test

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 Production Migration Deliverable Acceptance

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

2.1.6.2. Contractor Personnel Security and Suitability Requirements

In accordance with DIAPR 2010-04, performance of this contract requires Contractor personnel to have a Federal Government issued Personal Identity Verification (PIV) credential before being allowed unsupervised access to a DOI facility and/or information system. The COR will be the requesting official, and will make arrangements through a DOI Access Card Sponsor for personal identity verification and DOI Access Card issuance.

At least two weeks before start of each Task Order performance, the Contractor must identify all Contractor and Subcontractor personnel who will require physical and/or logical access for performance of work under this contract. Physical Access means routine, unescorted or unmonitored access to non-public areas of a Federally-controlled facility. Logical Access means routine, unsupervised access to a Level 3 or 4 federally controlled information system. The Contractor must make their personnel available at the place and time specified by the COR or DOI Access Card Sponsor in order to initiate screening and background investigations. The following forms and inquiries, or their equivalent, will be used to initiate the credentialing process:

· OPM Standard Form (SF) 85 or 85P

· OPM Optional Form (OF) 306

· National Criminal History Check (NCHC) (local procedures may require the fingerprinting to be done at a police station; in this case, any charges are to be borne by the Contractor)

· Release to Obtain Credit Information

· PIV card application (web-based) (DOIAccess Card Request Form)

Before starting work under this contract, an NCHC will be initiated to verify the identity of the individual applying for clearance and to determine the individual’s suitability for the position. If the NCHC adjudication is favorable, a DOI Access Card may be issued for that individual. If the adjudication is unfavorable, the credentials will not be issued and the Contractor must make other arrangements for performance of the work. In the event of a disagreement between the Contractor and the Government concerning the suitability of an individual to perform work under this contract, DOI shall have the right of final determination.

Contractor employees must give, and authorize others to give, full, frank, and truthful answers to relevant and material questions needed to reach a suitability determination. Refusal or failure to furnish or authorize provision of information may constitute grounds for another than favorable suitability determination or denial or revocation of credentials. Government personnel may contact the Contractor personnel being screened or investigated in person, by telephone or in writing, and the Contractor must ensure they are available for such contact.

Alternatively, if an individual has already been credentialed by another Federal agency and that credential has not yet expired the Government will determine whether further investigation is necessary. In that case, the Contractor must provide the COR with documentation that supports the individual’s credentialed status.

Contractor employees who have been favorably adjudicated may be issued a DOI Access Card, which must be activated at a USAccess Credentialing Center. Those Contractor employees not located within a reasonable travel time of a USAccess Credentialing Center will be screened and issued alternate credentials, such as temporary access badges.

During performance of the contract, the Contractor must keep the COR apprised of changes in personnel to ensure that performance is not delayed by compliance with identity verification (background investigation and credentialing) processes. Credentials that have been lost, damaged, or stolen must be reported to the COR and Issuing Office immediately. If reissuance of an expired credential is needed, the reissuance process must be coordinated through the COR.

At the end of contract performance, or when a Contractor employee is no longer working under this contract, the Contractor must ensure that all identification cards is immediately returned to the COR.

This requirement must be incorporated into any subcontracts that require Subcontractor personnel to have routine unsupervised access to a federally controlled facility or any unsupervised access to a federally controlled Level 3 or 4 information systems.

2.1.7. Miscellaneous Requirements

At a minimum, at the time of award of each Task Order, the Contractor shall provide Key Personnel possessing the appropriate background investigation required by the Task Order. Furthermore, at the discretion of the Government, higher levels of background investigation may be required for certain positions and will also be identified at the Task Order Level. (Collectively these background investigation levels will be referred to as National Agency Check with Inquiries (NACI) background investigations herein).

Project Information Non-Disclosure Agreement – For each Task Order awarded, and prior to beginning work under the Task Order, the Contractor shall submit, to the COR and CO, signed Project Information Non- Disclosure Agreements from all employees, inclusive of sub-contractors, that will be working on the Task Order.

Application / Data Security - Contractor staff may have access to privileged and confidential materials of the United States Government. These printed and electronic documents are for internal use only and remain the sole property of the United States Government. Some of these materials are protected by the Privacy Act of 1974 (AMENDED) and Title 38 Code of Federal Regulations (Title 38). Unauthorized disclosure of Privacy Act or Title 38 covered materials is a criminal offense. Each Contractor employee will be given access to only the information and facilities needed to perform the work associated with the Task Order.

2.1.8. Compliance

In addition to compliance with Section 508 of the Rehabilitation Act, the Contractor shall comply with Federal and DOI IT policy and procedural guidelines. The Contractor shall also comply with applicable specifications and standards found in the National Institute of Standards and Technology's (NIST) Federal Information Processing Standards Publications (FIPS PUBs) (http://www.nist.gov/itl/fips.cfm), and the use of ANSI/EIA Standard 748 (As Amended) Earned Value Management System (EVMS) (http://webstore.ansi.org/FindStandards.aspx?SearchString=EIA-748-C&SearchOption=0&PageNum=0&SearchTermsArray=null%7cEIA-748-C%7cnull).

2.1.9. Travel

Anticipated travel will be addressed in each Task Order and will be a reimbursable Contract Line Item Number (CLIN) subject to compliance with the federal travel regulations found at:

http://www.gsa.gov/portal/content/104790?utm_source=OGP&utm_medium=printradio& utm_term=ftr&utm_campaign=shortcut.

Prior to the Contractor making any travel arrangements, the Contractor will submit to the CO, Contract Specialist (CS) and COR a written request for travel outlining exactly who will be traveling, the destination of travel, mode(s) of transportation, when the travel will take place and, finally, the Contractor must state what the travel supports in the contract, specifically tying it to an exact task or CLIN. Upon receipt, the COR will communicate if the requested travel is necessary or not in writing to the CO; the CO will then issue a final determination of approval/disapproval in writing. The Contractor is responsible for requesting these travel approvals far enough in advance to accommodate all necessary approvals. If an approval is not garnished in advance, the Contractor may be responsible for all travel costs incurred.

2.1.10. Training

2.1.10.1. Technical Proficiency

In the performance of work under this PWS, the Contractor is required to provide fully trained personnel to perform the required services. No direct cost reimbursement will be made by the Government for training Contractor employees who are not proficient in the Related Technologies for Applications.

In cases where the Government replaces equipment, systems and software or introduces new equipment, systems and software which are significantly different from those previously supported reimbursement may be considered. In advance of any training, the Contractor will work with the COR to identify the cost impact of the training and provide detailed information of costs associated. This information will then be provided to the CO for final approval and modification to the associated Task Order(s) determined appropriate for the circumstance.

2.1.10.2. BLM Training

The following training will be required to be successfully completed by all Contractor employees, as applicable in order to gain access to BLM’s IT accounts, the internal IT network or IT resources accordingly. After initial successful completion, the training is required annually:

1) All Contractor employees who create, access or dispose of BLM data or information are required to complete web-based training courses on Records Management, the Freedom of Information Act, and the Privacy Act. This training takes approximately two hours.

2) All Contractor employees who are given BLM IT accounts, have access to BLM's internal IT network or IT resources are required to complete web-based general IT Security training and web based role-specific IT Security training. This training takes approximately ten hours.

3) All Contractor employees who are given BLM IT accounts, have access to BLM's internal IT network or IT resources may be required to complete a web-based certification of storage of a particular type of data. Requirements for this certification will be identified within each Task Order. This certification is required annually and takes approximately 15 minutes.

2.1.11. Government-Furnished Property

Government-Furnished Property (GFP) will be identified at the Task Order Level.

NOTE: Work performed at the Contractor's facility likely will require access to the BLM infrastructure. Currently this can only occur through the use of Government-provided laptops with Virtual Private Network (VPN) connection; it is projected that this capability may change over the course of the contract yet is not guaranteed. Any access must be in compliance with security requirements.

2.1.12. Government-Furnished Information

In general, Government-Furnished Information (GFI) will be provided by the COR as specified within each Task Order. In some cases, the delivery of GFI may be accomplished through direct coordination with the current incumbent Contractor. The applicable COR will be responsible for oversight of this effort to assure that the Government’s interests and integrity are maintained. This requirement, along with any pertinent information, will be identified at the Task Order Level.

2.1.13. Key Personnel

The Contractor shall appoint the following Key Personnel to be maintained throughout the course of this contract and at the Task Order Level (herein after referred to as Key Personnel):

Project Manager (PM) – The Department will not issue a task order exclusively for the PM’s services, however this individual will be accountable at the Task Order Level and is expected to provide oversight of all Task Orders. This person will also be responsible for presenting the QSR and briefings per Section 4.2 Deliverables and Schedules herein. Multiple Project Managers may be appointed for each project as determined at the Task Order level.

Additional Key Personnel - The requirement for these individuals will either be identified at the Task Order Level or proposed by the Contractor when applicable. Only those persons whose resumes are approved by the Government shall be assigned to perform any task involving key personnel duties.

Key Personnel Changes - No Key Personnel substitutions or additions will be made unless necessitated by compelling reasons. In such an event, before the substitution of any Key Personnel at all levels occurs, the Contractor must provide the information required below for Key Personnel Change Requests to the CO and COR. Proposed substitutes must have qualifications that meet or exceed the qualifications necessary for the Key Personnel Title being bestowed.

Key Personnel Change Requests - At least fifteen working days in advance of the proposed change when advanced notice is possible, a request for a Key Personnel change shall provide a detailed explanation of the reason for the proposed substitution or addition; a complete resume for the person to be substituted or added; and any other information requested by the CO or COR.

2.1. 14 Continuity of Services

The Contractor shall develop a General Continuity of Services Plan to accomplish phase-in (applicable to AFMSS II only) and phase-out as follows:

Phase-In Close coordination not only with BLM staff, but also with other BLM Contractors may be required. Contractor shall participate in project meetings and system coordination meetings or conference calls with existing development and O&M contractors every two weeks until the transition is complete. In addition the Contractor will participate in system coordination meetings with other IT Contractors as the BLM deems necessary.

Requirements for coordination will be identified within the Task Orders by establishing a ‘Phase-In’ stage with a set timeframe at the beginning of each Task Order. During this ‘Phase-In’ timeframe, the Contractor will acquire an understanding of BLM business activities as it relates to application systems, IT infrastructure, and present BLM and Contractor staff resources. To accomplish this level of operational readiness, the Contractor shall implement its General Continuity of Services, Phase-In Plan, supplemented by any requirements specific to each Task Order.

Phase-Out Similarly to the Phase-In stage, the Contractor shall implement its General Continuity of Services, Phase-Out Plan supplemented by any requirements specific to each Task Order.

Consistent with 52.237-3 Continuity of Services upon which the Contractor’s plan is based, the Contractor shall assist the Government in planning and implementing a complete transition from this Task Order to any incoming support provider. This shall include formal coordination with the Government and incoming provider staff and management and delivery of soft copies of existing manuals and documentation, procedures, knowledge, documentation, hardware, software, and required metrics and statistics.

2.2. Funtional Areas

IT services under the resultant Orders will require the Contractor to provide a range of technical and non-technical services associated with the management of systems. Work performed by the Contractor may involve any or all stages of a system’s lifecycle.

Contractor management shall ensure all work is performed in a consistent, repeatable, predictable, and coordinated manner. BLM highly encourages The Contractor to continuously improve practices and procedures throughout all aspects of the Contractor’s performance to help ensure quality products. Whenever appropriate, the Contractor is encouraged to recommend alternative solutions, approaches, changes or corrections.

The following enumerates the Primary functional Areas, inclusive of associated activities / tasks, in which the Contractor may be engaged under this Contract:

2.2.1. Application Development

Application development often times called software development is the process of developing software products that directly meet a need of the customer business responsibilities. The process can include a single mobile application, a stand-alone application, an Enterprise Resource Planning (ERP) system and everything in-between. While there isn’t a set definition for process most agree to the common best practice activities of: requirements gathering, design, implementation, testing, and maintenance. In addition to these best practices BLM considers the following activities/tasks to also fall within this functional area:

· Technical

· Full Systems Development/Maintenance Life-Cycle Support

· Including, but not limited to, methodology and standards development; use case development and decomposition, business process analysis associated with IT, technology research, communications analysis/management, system architecture, systems design, system development and maintenance, software development, re-hosting applications, conversion of legacy systems, COTS analysis and implementation

· Data Administration/Management and Modeling

· Mobile (iOS and Android at a minimum) Development

· Web Design and Development

· Mobile/Responsive Design Development

· Technology Research and Development

· Quality Assurance

· BLM Data Registry

· Test and Evaluate Software

· Internet/lntranet Development and Maintenance

· Post-Implementation Reviews

· Use Case/Story Point Development

· Use Case/Story Point Decomposition/Analysis

· Product Vision/Roadmap Analysis

· Portal Development and Maintenance

· Program Support

· Project Management Support

· Business Process Analysis

· Business Case Mapping

· Business Case Preparations and Studies

· Conduct User Conferences/Walkthroughs

· Database Administration/Management

2.2.2. Application Training and Help Desk Operations

Application training is the act of planning, developing, and/or instructing training specific to an application. Training can be performed in many formats such as end-user instruction or computer-based training.

Help desk operations provides a single point of contact for all users whenever IT customer support is needed. A single point of contact allows BLM to ensure service levels meet expectations in the areas of response quality, action, feedback, timeliness, and solutions. 1800BLMHelp is established as the Tier 1 help desk for all BLM technical issues. Tier 2 and 3 services are spawned from the initial point of contact whenever needed and provides more technical and application specific support to customers per this PWS.

BLM considers the following activities/tasks to also fall within this functional area:

· Training for Legacy and New Systems

· Third Party Products Training

· BLM Client Awareness Training

· Product Development Tools Training

· Training Support

· Helpdesk Support, Tier 2+ Help Desk Operations

· Technical Equipment Support

2.2.3. Project, Forecasting and Planning, Security, and Quality Control

Project forecasting and planning ensures the identified processes, activities and outputs necessary to ensure that projects are well conceived, cost-effective, and support its missions and business goals. It is based on guidance from the Office of Management and Budget (OMB), United States Congress and the General Accounting Office (GAO), Washington Office (WO800), and/or Information Technology Investment Board (ITIB).

Security is an integral element of today’s IT environment. As explained by NIST information and computer systems are critical assets that support the mission of organizations. The primary focus of our security is to serve as a trusted advisor to the federal community by provisioning sound security services that balance the business need with the security risk while ensuring compliance with federal regulations. The primary guiding factors for these activities are Federal Information Security Management Act of 2002 (FISMA) and NIST Special Publications (800 series).

Quality control efforts are those that provide the foundation for and oversees the efforts such as Quality Assurance (QA), Configuration Management (CM), Project Management (PM), and Independent Verification and Validation (IV&V) to improve products and services provided by the BLM IT community, specifically DIRM.

BLM considers the following activities/tasks to also fall within this functional area:

System Security Analysis Systems Security Testing Configuration Management Change Management Release Management Project Planning and forecasting Knowledge Management Technical Security Support Software Quality Assurance

2.2.4. Systems Engineering Support

Systems engineering has been defined as the science of designing complex systems in their totality to ensure that the component subsystems making up the system are designed, fitted together, checked and operated in the most efficient way. Stages of system engineering best practice include: system concept, system definition and preliminary design, detailed design and development, system production or fabrication, and system operation and support. Specific areas include:

· Technology Analysis and Assessment

· Test and Develop Telecommunication Methodologies

· WAN/LAN Support

· Telecom and Radio Communication Analysis and Support

· Technical Engineering and Support

· Systems Analysis and Documentation

· Design Reviews (Preliminary and Detailed)

· Mobile Application Engineering

2.2.5. Geospatial Technology

Major resources utilized to effectively meet the mission of BLM are Geographic Information Systems (GIS) and other associated geospatial technology. As defined by wiki.gis.com GIS is an integrated collection of computer software and data used to view and manage information about geographic places, analyze spatial relationships, and model spatial processes. A GIS provides a framework for gathering and organizing spatial data and related information so that it can be displayed and analyzed. Examples of the associated types of activities are:

· Geographical Information System (GIS) Services

· Spatial Data Management (SDM) Support

· GIS Application Development

· GIS Tool development

· Geodatabase management

· GIS Web Application Development

· GIS Design

· GIS Administration

2.2.6. Miscellaneous Technical Services

In addition to the specific functional areas called out above there are a plethora of services which an enterprise IT office are required to perform to meet the needs of their organization. Some specific areas not easily categorized above but recognized as active or future areas of work are:

· Statistical Services Accessibility Standards

· Communications Management/Support

· Knowledge Management

· Strategic Planning

· Enterprise Architecture

· Technical Library Management

· Technical Analyses

· Feasibility Studies

· Data Entry

· Preparation and Presentation of Management Briefing Materials

· Development of product newsletters and any other effective communication aids needed to provide system related information to interested parties

· Develop Guidelines and Standards

· Assist with COTS Selections & Evaluations

· Technical Writing

· Software Library Management

2.3. Support Services

Applications Development Lifecycle (ADLC) Support Services. This section describes the types of support services that may be required under task orders to be issued under the ITSS contracts.

1. Service Development. The design and development of services and service management processes. Design principles and methods for converting strategic objectives into portfolios of services and service assets. Includes the changes and improvements necessary to increase or maintain value to customers over the lifecycle of services, the continuity of services, achievement of service levels and conformance to standards and regulations. It guides organizations on how to develop design capabilities for Service Management.

2. Service Operations. Provisions for effectiveness and efficiency in the delivery and support of services so as to ensure value for the customer and the service provider. Strategic objectives are ultimately realized through Service Operations, therefore making it a critical capability. Maintain stability in Service Operations, allowing for changes in design, scale, scope and service levels. Supporting operations through new models and architectures such as shared services, utility computing, web services and mobile commerce.

3. Service Management. Support for establishing an IT Service Management (ITSM) process intended to align the delivery of IT services with needs of the enterprise, emphasizing benefits to customers. Assistance in managing the paradigm shift from managing IT as stacks of individual components to focusing on the delivery of end-to-end services using best practice process models. These services will be based upon the Information Technology Infrastructure Library (ITIL), a globally recognized collection of best practices for IT service management. Additional support for ITSM audits based on analysis of four key performance indicators in specific ways:

· Growth and value, which involves tracking revenue growth against investment and utilization.

· Budget adherence, which involves optimizing the use of available funds and avoiding unnecessary expenditures.

· Risk impact, which involves identifying and evaluating the consequences of risks taken or avoided.

· Communication effectiveness, which involves examining internal customer feedback and gauging customer satisfaction and awareness

4. IT Planning. Identification, evaluation and recommendation of solutions and opportunities, including the modification and process re-engineering of existing systems to encourage and facilitate the development of integrated systems, provide added functionality and improve productivity, while taking into account all applicable federal standards and procedures and the client organization’s standards and policies. Includes support for enterprise architecture planning, migration planning, implementation governance, and technology architecture. Also includes IT Strategy and Vision Development, IT Effectiveness Analysis, and IT Cost Reduction.

5. Program Management Support. Providing assistance to a Government Program Management Office (PMO). This support could include performing and/or assisting the PMO staff in the development and maintenance of program and project plans, standard operating procedures, contingency plans, continuity of operations, and other documentation. It may also include acquisition support by preparing procurement related documentation, such as Performance Work Statements, independent Government cost estimates, internal acquisition review board packages and justifications, and source selection material. Financial management support could include the collection and management of financial data; assisting in financial analysis tasks; tracking program progress against the program plan; and preparing required financial reports. PMO support could include Portfolio Management, which would allow BLM to track and align expenditures across the portfolio in a manner that would dedicate specific investment percentages to broad areas of IT, such as infrastructure, application development and operations, new technology, etc. Other support may include providing meeting support by planning and arranging for meetings, preparing meeting materials and recording and disseminating minutes; development and tracking of correspondence, reports and briefing materials; maintenance of a document library. Support may also include researching and providing recommendations on best practices to improve areas within Program Management; evaluating issues and providing recommendations related to program cost, schedule, and performance; and, providing analysis and recommendations to respond to Congressional, other Government agencies, and industry inquiries; audits; or Congressional testimony.

6. Use Case Analysis, Development, Decomposition and Estimation. The Government will establish business requirements. This service encompasses the process of taking Government established business requirements in the forms of a product vision, product roadmap, business process mapping, epic user stories, and other requirements definition methods of product scope and converting them into detailed functional and system requirements necessary for design and development of the system. This includes effort estimation and assisting the government in working with users in the prioritization of functional requirements established in the product backlog. Users’ requirements are documented meaningfully using automated gathering tools, wherever applicable. It is assumed that the user knows what process he needs automated, but has difficulty in translating requirements into data-processing terminology. This procedure helps get the product backlog established to begin systems design and implementation. This sub-phase is one of the most important in the entire project lifecycle.

7. Feasibility Study. Identifies objectives, requirements, system concepts, and candidate approaches. It researches possible solutions and analyzes commercial off-the-shelf (COTS) products available for achieving the objectives. Includes familiarity with various COTS products in the marketplace. May include making recommendations on the approach to be taken. The feasibility studies will be used by managers to decide whether to proceed with the task.

8. Cost-Benefit Analysis. An in-depth evaluation of a given approach as to technical feasibility and/or the benefits to be gained for a specific cost. The analysis involves identifying, developing and analyzing the costs (actual and opportunity) and benefits of a given approach in quantitative terms if feasible and in qualitative terms otherwise, and preparation of a recommendation to proceed or not to proceed. The user may require that this type of analysis occur independently or with other activities comprising a full system development effort.

9. Business Process Analysis and Re-engineering. A complete analysis of the processes used in a government service with focus on revamping the entire approach to improve the value of the process. The primary drivers should always be the customer’s needs and the mission. The issues that need to be reconciled include time, quality, customer perspective, people empowerment, efficiency and flexibility. Technology is considered a potential enabler of the new approach. Includes support for feasibility studies, cost benefit analysis, process modeling, business event modeling, organization design, business strategy, and change management/leadership.

10. Systems and Information Engineering. An integrated set of methodologies and products used to guide and develop information processing within an organization. It starts with enterprise-wide strategic planning and ends with operational applications. It includes activities required for the support of operational systems oriented toward enhancing operations of hardware and software systems to include the collection and analysis of systems information, diagnosis of problems and development of recommendations to resolve problems. It establishes and maintains systems and software configuration baseline data and documentation. It includes redesign activities that modify functionality and/or produce technical improvements to enhance software and security. It monitors system execution and performance; tracks and reports change requests (CRs) and discrepancy reports (DRs); performs problem analysis and resolution; and provides technical assistance to the end-user. It performs system and software conversion activities that include the transition of existing applications from one environment to another. It performs production control activities such as the support of cyclical changes to operational workloads, data compression, data restores, reorganization of files, recovery of systems, production of reports, download/upload of information, and setup and verification of fields and programs for the execution of production runs. It prepares and executes disaster recovery procedures; analyzes, compiles and aggregates data to produce statistical trend analysis reports; develops user-friendly interfaces between different automation functions and upload/download capabilities; and develops and implements an audit strategy to ensure the integrity and confidentiality of data.

11. Systems and Database Design. Includes the design approach, alternative designs and analysis, and impact analysis. Maps and maintains traceability of the design to requirements; develops user interfaces; identifies the major components and interfaces of the system; determines impact on work flow processes; and develops testing strategies, test cases and testing plans. Also includes conducting design reviews to clarify design drivers; select an IT platform and/or architecture; identify and weigh portability considerations, potential capacity and performance implications; identify existing systems that may be reused; identify any integration issues with legacy systems; and other pertinent design information. Unique database design tasks include creating the logical and physical database design for a system using data modeling and data normalization techniques.

12. Systems Procedures and Standards. Devising systems procedures and standards using all applicable standards and procedures as required by the Federal Information Processing Standards (FIPS), BLM requirements, other standards, and the client organization’s standards and policies. Includes identifying the applicable standards and procedures and making recommendations about their use to the client organization.

13. Systems Development and Testing. Translating system specifications and detailed design documentation into system components, or code or both. May include initial development of a prototype of the system that will be tested and evaluated before the systems development effort using automated testing tools, whenever applicable. Includes: developing code, conducting peer reviews and providing summary progress of the development effort; establishing and maintaining the integrity of baseline configuration, software version descriptions and related documentation; establishing test and verification procedures to ensure system integrity so that the system meets functional requirements; and, conducting unit, system and integration testing to validate the system's capabilities. Also includes Performance Testing to verify that the system meets specific response time requirements and User Acceptance Testing to verify that target user groups concur that the business objectives are met.

14. Systems Installation and Acceptance. All activities associated with the installation and operation of the system. During systems implementation, includes providing support through the development of prototype installation test plans, installation test reports and the preparation of systems manuals including operations, maintenance and user manuals customized by site. Delivery of the system and all documentation and products associated with the system. Installation, integration, testing and implementation of the systems developed to include all activities associated with data conversion, data collection, capture, validation, and verification, user training and system turnover.

15. Systems Programming. Programs are written using the programming standards established by the client organization. Substantial emphasis is put on a structured process for preparing a test plan, which outlines all of the testing to be done. The programmer plans testing problems thoroughly before the testing begins. The results of the testing are then reviewed by qualified personnel to decide that each program and module is operating satisfactorily.

16. Systems Integration. Includes the analysis of the distribution of functionality across systems, development of system interface concepts, designs and specifications, and the development of specifications and standards for…