Attachment_E-Task_Order_One_Performance_Work_Statement.docx

DOCX document 25 KB Posted

Attached to
eDraws Services IDIQ
Solicitation number
140R8119Q0109
Issued by

About this file

Attachment E-Task Order One Performance Work Statement

View the file

Other files

File Type Posted
Attachment_A_-_Performance_Work_Statement.docx DOCX document
Attachment_B_Labor_Category_Descriptions.xlsx XLSX spreadsheet
Sol_140R8119Q0109.pdf PDF
Attachment_C_Labor_Category_Pricing.xlsx XLSX spreadsheet
Attachment_D-Task_Order_One_Pricing.xlsx XLSX spreadsheet

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

140R8119Q0109 Attachment E 01/28/2019

Attachment E: IDIQ Task Order One: Performance Work Statement

1) INTRODUCTION:

a) Background: During FY13/14 the Bureau of Reclamation (Reclamation), in conjunction with, and as directed by, the Department of the Interior, developed and implemented an enterprise solution to automate and standardize an electronic drawing repository and workflow system. Implementation of eDRAWS was completed in February of 2014.

2) SCOPE:

a) Requirement: This requirement is to acquire professional support services to provide vendor support of Reclamation’s configuration of the Meridian Enterprise Software. This will be a firm fixed price contract for the period beginning April 1, 2019 through March 31, 2020.

3) PERSONNEL QUALIFICATIONS:

a) Experience: Vendor personnel will have experience working with BlueCielo’s Meridian Enterprise Server and experience in reading and writing Microsoft Visual Basic Scripting (VBScripting). In addition, they will have completed the Meridian System Administrator Course within the last 3 years as well as the following:

i) Fully trained via BlueCielo Implementation Specialists Training Course.

ii) C# programming experience.

iii) Meridian implementation experience with an Enterprise-sized customer and a minimum of 300 users.

iv) Meridian implementation experience with a distributed decentralized environment.

v) Meridian implementation with a centralized environment with the ability to leverage Site Cache.

vi) Meridian implementation experience with native application rendering for Adobe *.PDF and Autodesk applications using *.DWG and *.RTV.

vii) Experience with authoring beyond AutoCAD such as Inventor, REVIT, and Civil 3D, with the full Meridian product set (Explorer, Publisher, Portal, etc.).

4) GOVERNMENT-FURNISHED EQUIPMENT (GFE) AND MATERIALS: None.

5) REGULATIONS/POLICIES: None.

6) TRAVEL: No travel is required.

7) GOVERNMENT VEHICLES: No transportation in government vehicles will be required.

8) SECURITY:

a) Vendor produced, and Government furnished information related to this requirement is designated “Controlled Unclassified Information (CUI).” This information shall not be shared with anyone outside of Reclamation.

b) The vendor will not be entering secure areas under this requirement.

c) The vendor shall be required to supply Reclamation with the legal names and other personal information of employees who will be working under this requirement.

d) Reclamation reserves the right to perform security checks on the vendor and other persons identified in accordance with established procedures.

9) TRAINING: No training is expected under this task order.

10) DELIVERABLES: The scope of the requirement work effort consists of two program areas – system administration and Meridian Architecture Support. Vendor personnel will use the Reclamation’s call logging software for all work activities.

a) System Administration: Reclamation currently has 17 servers that host and operate the Meridian system for various locations. Such a system requires server monitoring, application maintenance and assistance to users. This section outlines the activities and responsibilities proposed to be undertaken by a full-time Meridian System Administrator

i) Server Monitoring: Provide resources to constantly monitor and regulate the current server environment for eDRAWS. This will require regular scheduled monitoring and related tasks.

(1) Server resources monitoring – Meridian performance related

(2) Support to Reclamation for required operating system patches/updates

(3) Impact / risk assessment of server updates on Meridian

ii) Application Maintenance: In addition to regular monitoring of servers, the Meridian application itself requires elements of maintenance and general user assistance. User assistance differs from user support in that it provides activities that aid the ongoing use and day to run running of the application, as opposed to merely responding to errors. Application maintenance activities include:

(1) Execution of vault consistency checks;

(2) Publisher queue monitoring and error resolution;

(3) User / group management;

(4) Event log monitoring for recurring issues;

(5) Creation / amendment of Explorer views;

(6) Creation / amendment of Power (and web) searches and reports;

(7) Bulk property updates / corrections;

(8) BlueCielo license management;

(9) Monitoring and management of Explorer synchronization tasks;

iii) Minor configuration corrections / changes to:

(1) meta-data fields;

(2) property dialog layouts;

(3) existing workflows;

iv) System purging and document recovery support.

b) Meridian Architecture Support: Meridian architecture support covers centralization of the current Meridian systems, extending the system, and adjustments to the configuration and scripting related to patches, updates, and enhancements.

i) Centralization: Reclamation has interest in centralizing the eDRAWS architecture which equates to the unification of servers into a single architecture, with all remote sites accessing via the web browser Meridian interface, while implementing appropriate redundancy of data. Proposed activities related to centralization include

(1) Existing architecture review;

(2) Future use analysis (user counts, document counts, usage patterns);

(3) Existing solution configuration review (alignment across locations, readiness for web interface);

(4) Future proposed architecture/infrastructure needs (including site cache services);

(5) Proof of Concept phase

(a) Prepare POC for web-only interface to replica system;

(b) Identify key use cases for testing (performance and usability);

(c) Support test execution by allocated personnel;

(d) Report findings and recommendations.

(6) Prepare outline of proposed conversion to a centralized system

(7) Equipped with the above data and findings, Reclamation will be better prepared to make the decision on centralization and determine a suitable roll-out plan.

ii) Extending the system: The Meridian system can be enhanced significantly through initiatives aimed at getting more value from their eDRAWS investment. These initiatives include assessment, planning and scoping of the following:

(1) Integration with IBM Maximo - Provide users with direct access to drawings, documents and other Meridian content directly from the Maximo interface.

(2) Tag data extraction - Linking or associating drawings and documents to equipment data to make the Maximo integration more complete.

(3) Data analysis & cleansing – Data accuracy and consistency through analysis and bulk changes/corrections.

(4) Dashboard reporting - Workflow processes, work activity, data integrity, and other relevant real-time data via dashboard reporting.

11) QUALITY: In accordance with above specifications/deliverables.

a) All activities will be tracked using the Reclamation call logging software. Weekly status reports will be required detailing all activities.

i) Performance Standard for PWS Section 10.0

(1) Accuracy: No more than two (2) errors/documentation and written communication.

(2) Timeliness: All reports must be submitted in accordance with the delivery schedule mutually agreed upon.

(3) Acceptable Quality Level: 98%

(4) Method of Surveillance: Government representative to monitor

ii) Procedures taken when performance standards are not met

(1) FAR Clause 52.212-4(a)

12) Identification of Contractor Employees: All contract personnel are required to identify themselves as contractors. Whether attending meetings, answering Government telephones, or working in other situations where their contractor status is not obvious to third parties, they must make their status known to avoid creating an impression that they are Government employees.

File details come from the government source that posted it.