RFP_CMMS_DHQCAP15MP60007.docx

DEFENSE INFORMATION SYSTEMS AGENCY

DEFENSE INFORMATION TECHNOLOGY CONTRACTING ORGANIZATION

One Overcash Avenue Chambersburg, PA 17201

March 7, 2016

Small Business Contractors:

1. This request for proposal (RFP) is to support DISA’s requirement for a Computerized Maintenance Management Software (CMMS) Solution.

The specifics are as follows:

Other Direct Charges (ODCs) / Travel Cost Reimbursement

2. Offerors are requested to submit a written technical and price proposal in response to the attached Performance Work Statement (PWS) (Attachment 1) and Quality Assurance Surveillance Plan (QASP) (Attachment 2). Further information on submission of technical and price proposals is provided throughout this document.

a. IAW with DISA Acquisition Regulation Supplement (DARS) 52.209-9000, each offeror shall specifically identify in their proposal, whether or not any potential or actual Organizational and Consultant Conflicts of Interest (OCCI) as described in Federal Acquisition Regulation (FAR) Subpart 9.5 exists for this procurement. If the offeror believes that no OCCI exists, the OCCI response shall set forth sufficient details to support such a position. If an offeror believes that an actual or perceived OCCI does exist on this procurement, the offeror shall submit an OCCI plan with the proposal, explaining in detail how the OCCI will be mitigated and/or avoided.

b. Any “no-bid” reply must include a brief statement as to why the offeror is unable to perform.

3. Evaluation Factors and Basis for Award Determination:

a. Award will be made to the offeror whose proposal is determined to represent the overall best value to the Government using a Lowest Price Technically Acceptable (LPTA) evaluation process consisting of two phases as noted below.

b. Phase one will consist of Lowest Price evaluation. The lowest price offer will proceed to Phase Two.

c. Phase Two will consist of a Proof of Concept Phase. The Proof of Concept Phase will be evaluated on an Acceptable/Unacceptable basis. Offerors will be required to supply a complete proposed solution to support testing the CMMS Solution. Instructions for submission will be provided to the lowest price offeror. Total testing time will be six (6) weeks and broken into two categories: Security Review and Technical Testing to include functionality and ability to meet all technical requirements noted in section 6 of the PWS. The Proof of Concept testing is designed to validate the offeror’s CMMS solution as contained within the offeror’s technical proposal. The Technical items to be tested during Phase Two are contained in the Functional Test Plan (Attachment 3). The results of the demonstration will be rated as Acceptable or Unacceptable. The technical proposal should include all information the offeror wants the Government to consider and evaluate regarding its company’s ability to perform all required tasks and conform to all required terms and conditions. In order to be eligible for award, the contractor’s proposal must sufficiently address all aspects of the PWS.

Offerors that are unable to demonstrate the ability to meet all the test plan objectives will receive a rating of unacceptable. Offerors that are able to demonstrate the ability to meet all the test plan objectives will receive a rating of acceptable.

Offerors that receive an unacceptable rating will be eliminated from further consideration.

During the offerors’ Proof of Concept testing, offerors will be required to provide written verification that the software solution used to demonstrate their Proof of Concept is the same software solution contained in their initial written proposal.

d. The offeror will be allowed two (2) persons in the test lab at any one time. An exception will be made for the in-brief, out-brief, and equipment setup phases of the test schedule. At those times, up to four (4) persons will be allowed in the test lab and/or conference room. At least one member must be knowledgeable enough to answer technical questions regarding the offeror’s solution, during document review. Scheduling of the Proof of Concept will be mutually agreed upon with the Government and the Offeror prior to each offeror’s testing.

e. Any proposal failing to meet the Section 508 Accessibility Standards, as listed in the PWS, shall be eliminated from consideration for award.

f. After receipt of proposals, the Government will first evaluate the lowest price proposal. If the lowest price proposal is determined to be technically acceptable and otherwise properly awardable, no further evaluations will be conducted, and award will be made. If, however, the lowest price proposal is determined to be technically unacceptable and/or otherwise not properly awardable, further evaluations will be conducted.

g. The standards for determining technical acceptability are below, as well as information concerning price proposals. Page limitations are identified below under each evaluation factor and will be treated as maximums. If exceeded, excess pages will not be read or considered in evaluation of the proposal. The following items will not be considered when calculating page limits: cover page, table of contents and glossary. In the event any evaluation notices are issued, page limitations may also be placed on those. The technical portion of the proposal is to be submitted as a Microsoft (MS) Word 2007 or PDF document. The page format shall have a 1 inch margin using no smaller than an 11 point Ariel, Times New Roman, or Courier New font for all text to include any text contained in a table. The price proposal spreadsheet shall be a separate document from the technical proposal and shall be submitted in MS Excel 2007 format. All formulas shall remain present in the spreadsheet for verification. The file size of each document shall not exceed 2MB. Page limitations shall not be circumvented by including inserted text boxes/pop-ups or internet links to additional information; such inclusions are not acceptable and will not be considered part of a proposal. The Government reserves the right not to consider for award any proposal that does not adhere to the administrative requirements of this RFP.

(1) Price Factor:

(a) Price proposals will be evaluated to determine if they are reasonable and complete. The offeror shall submit pricing for the base period and all option periods, including option pricing for an additional 6-month period that may be authorized IAW FAR 52.217-8. See FAR 52.217-8 which authorizes the Government to require continued performance of any services within the limits and at the rates specified in the contract. The pricing proposal should include a separate line item for the additional 6-month period IAW FAR 52.217-8. These prices shall be identical to the quoted pricing in the 6 months prior to expiration of the base period, or the final option period, if option periods are present. The total evaluated price will consist of the contractor’s proposed price for the base period, all option periods, the option pricing for the additional 6-month period, and surge pricing as requested below.

(b) Offerors should ensure price proposals include detailed information regarding the resources required to accomplish the task (e.g., labor categories, labor hours, number of employees for each labor category, rates, travel, incidental equipment, contract access fees, etc.). Again, the price proposal spreadsheet shall be a separate document from the technical/management proposal.

(c) All travel must show the specific detail, if known (e.g., number of days, locations, number of personnel, etc.). All ODCs shall annotate the specific detail (e.g., quantity, part number, manufacturer, etc.) to include supporting documentation to justify the costs (i.e., price quotes, price history, etc.). Travel shall be authorized by the COR in writing prior to performance and will be paid IAW FAR Part 31.205-46.

(d) Due to the likely inability of any offeror to accurately estimate travel and material/equipment purchases associated with this requirement, the Government is providing plug numbers to be used by all offerors when proposing ODCs. Offerors are instructed to propose plug numbers for ODCs in the following EXACT amounts, however actual travel shall be authorized by the COR in writing prior to performance and will be paid IAW FAR Part 31.205-46.

Travel ODCs Base Year: $ Option Year 1: $10,000.00 Option Year 2: $10,000.00

These EXACT amounts shall include all audited markups and burdens and shall not be rounded or adjusted based upon independent decisions regarding actual anticipated ODCs. A proposal that fails to bid the plug numbers EXACTLY as provided may be excluded from further consideration.

(e) The Government may require surge support during the base or any option period and surge modifications will be in-scope to provide increased support for the defined task areas of the PWS. Surge support is OPTIONAL and is not a guarantee. If the Government determines that an increased quantity of support is required for the task areas defined in the PWS, the Government reserves the right to exercise the surge option unilaterally. The contracting officer will provide written notice to the offeror at least 30 calendar days prior to any unilateral exercise of the surge option. The Government is providing a percentage value to be used by all offerors when proposing surge: surge support will not exceed 20% of the offeror’s total proposed cost/price for the base and all option periods, excluding any 6-month extension of services pursuant to FAR 52.217-8. Offerors are instructed to propose this EXACT percentage for Surge CLIN 9999. In the event the Government does elect to exercise the surge option, surge support will be realigned under new or existing CLINs for the relevant task areas identified in the PWS, and an equal amount will be deducted from optional surge CLIN 9999. The Government will not conduct a cost realism analysis on optional surge CLIN 9999 if all other labor CLINs under the contract/task order are firm-fixed price. Surge support will be provided at the same labor rates proposed and found fair and reasonable at time of contract/task order award for the applicable period of performance. When surge support is realigned under cost-type CLINs, if actual reimbursable labor rates exceed the labor rates originally proposed and found fair and reasonable at time of contract/task order award, the contractor is only entitled to a fee amount based on the originally proposed labor rates.

(2) Technical/Management Approach Factor:

The Technical/Management Subfactors will be evaluated and rated either Acceptable or Unacceptable. In order for a proposal to be rated overall Technically Acceptable, each of the items identified in the Functional Test Plan (Attachment 3 paragraph 2.4) must be rated Acceptable. Technical/ management proposals should not exceed 35 pages.

4. Offerors shall propose a fixed price payment plan commensurate with the value of the deliverables and/or significant milestones in the PWS for this requirement. A FFP payment plan with the total dollar amount divided into 12 equal monthly payments will not be accepted unless the offeror provides justification for this plan that the Government subsequently deems adequate. The eventual awardee will be authorized to invoice monthly for all approved travel costs incurred and approved by the contracting officer representative (COR).

5. The Government intends to evaluate proposals and award a contract without discussions with offerors. However, the Government reserves the right to conduct discussions or seek clarifications if the Contracting Officer (KO) determines they are necessary. In the event issues pertaining to a proposed task cannot be resolved to the KO’s satisfaction, the Government reserves the right to withdraw and cancel the proposed task order. In such an event, offerors will be notified in writing. In the event a competitive range is established and the KO determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the KO may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition.

6. Attachment 4 contains a CLIN pricing worksheet, Attachment 5 contains evaluation tables and Attachment 6 contains provisions that apply to this solicitation and clauses that will be applicable to the resulting award. Some of the provisions require a response from the offeror and will need to be submitted along with your proposal.

7. In response to this RFP, no terms, conditions, or assumptions will be entertained. If terms, conditions, or assumptions are included in a proposal, the proposal may be excluded on grounds that it failed to comply with the RFP’s instructions.

8. An offeror agrees that if their proposal is accepted within 60 calendar days from the date of receipt of proposals (unless a different period is stated in the proposal), they will furnish the items and/or services identified in their proposal at the price offered to the designated point(s) within the time specified in the contract.

9. In response to the Request for Information, questions were received. The Government has provided answers to the questions submitted. Additional questions should be addressed to cindy.m.goshorn.civ@mail.mil. The phone number is 717-267-5707. Please provide any questions, in writing, no later than March 16, 2016 at 2:00pm (EST). The Government reserves the right to not answer questions submitted after this time.

10. Proposals are due no later than March 21, 2016 at 2:00pm (EST) and should be submitted to the contracting officer at DITCO via the following email address: cindy.m.goshorn.civ@mail.mil.

Sincerely, Cindy M. Goshorn

CONTRACTING OFFICER

Attachment 1, PWS

Attachment 2, QASP

Attachment 3, Functional Test Plan

Attachment 4, CLIN Pricing Worksheet

Attachment 5, Evaluation Tables

Attachment 6, FAR, DFARS, DARS Provisions/Clauses image1.emf

DHQCAP15MP60007 CMMS PWS.docx

PERFORMANCE WORK STATEMENT (PWS)

as of 4 March 2016

1. Contracting Officer Representative (COR)

a. Primary COR.

Name:

Shanna Neil

Organization:

Defense Information Systems Agency (DISA)/IML11

DODAAC:

H98272

Address:

1 Overcash Ave, Bldg 12, Chambersburg, PA 17201

Phone Number:

717-267-9682

Fax Number:

N/A

E-Mail Address:

shanna.b.neil.civ@mail.mil

b. Technical Point of Contact.

Name:

Marie Billett

Organization:

DISA/SE231

Department of Defense Activity

Address Code (DODAAC):

H98249

Address:

PO Box 4598

Greenwood Village, CO 80155-4598

Phone Number:

303.224.1734

Fax Number:

303.224.1608

E-Mail Address:

marie.r.billett.civ@mail.mil

2. Title. Computerized Maintenance Management Software (CMMS) Solution

3. Background. The DISA datacenters provide routine and mission-critical computer processing resources and support to numerous Government agencies, 24 hours per day and 7 days a week.

DISA Implementation and Sustainment Center (ISC) currently utilizes MP2 (through a maintenance and operations service contract) and Microsoft Excel inventories in support of CMMS for data center and non-data center (e.g. administrative) maintenance and asset management. This project is intended to replace those systems to maintain, inventory, and manage equipment assets within DISA Facilities.

The Government requires greater operational visibility over infrastructure maintenance and management activities in order to optimize their inventory and asset tracking procedures. Additionally, enhanced visibility is required over critical infrastructure. CMMS will streamline asset lifecycle management as well as identify preventive and predictive maintenance tasks, and automate the Work Order (WO) process under one centralized repository.

4. Objectives. The objective of this requirement is to procure a software solution. The software solution will consist of software licenses, implementation, data collection and/or data migration, software support, and annual software license maintenance. The objective of CMMS solution is to provide flexibility and scope of support sufficient to meet current and future DISA environment workload, security, availability, scalability, and modernization requirements, while ensuring DISA customers receive uninterrupted, continuous access to their applications and data. The contractor will acquire, install, configure, and provide software and software updates for all products associated with this contract.

5. Scope. The scope of this requirement is to procure a commercial off the shelf (COTS) software product including software licenses, implementation, data collection and/or data migration at all DISA Facilities. This includes software support and annual software license maintenance for an enterprise-level CMMS solution. This solution should include unlimited (non-restrictive) user licensing to support the enterprise. This project will integrate contract operations and maintenance support and Government facility management disciplines at DISA Facilities to centralize maintenance, lifecycle management, and asset optimization for the DISA Facilities. The CMMS tool is required to communicate with and integrate equipment and change control management information with other Government systems including, but not necessarily limited to, the DISA enterprise building automation system (BAS), the DISA enterprise information technology service management (ITSM) tool suite, the Data Center Information Management (DCIM) solution and the SharePoint/DoD Enterprise Portal Service (DEPS). Deployment will consist of using Government furnished development, test, and production computing environments to build, test, and deploy the application as designed. The vendor will develop a site migration and implementation plan that addresses data collection, procedural and reporting requirements for inclusion in CMMS, application training, and site operational transition support. Following award, the vendor will work with the Government to develop a proposed project schedule. Mutual agreement is required.

This project will use DISA-furnished and administered infrastructure resources (computing platforms including all required hardware, connectivity components, operating system, and Enterprise Systems Management (ESM) utilities for development, test, and production (e.g., operating environment). The operating environments for this project will be virtual. The solution must be operational in a high availability, redundant architecture (active/active, clustered, server pool, etc.) and operate on a virtual platform. If the solution contains embedded components (e.g. Java, etc.) these imbedded components must be maintained in accordance with information assurance (IA) and Security Technical Implementation Guide (STIG) compliance timelines. Vulnerabilities must be remediated within Government security guidelines and schedules. Patches and updates must be independent of the vendor software release lifecycle. For example, a java patch that is required to be applied immediately must be provided in accordance with Government guidelines and schedule and not held to coincide with next vendor software release.

The specific task areas addressed in the PWS are:

· Task Area 1 – Software

· Task Area 2 – Technical Support

· Task Area 3 – Implementation of the CMMS Solution

· Task Area 4 – Operations Support

· Task Area 5 – Option Year Software Support

· Optional Task Area 6 – On-site data collection in Stuttgart-Vaihingen, Germany for the CMMS Solution

· Optional Task Area 7 – On-site data collection in Bahrain for the CMMS Solution

6. Performance Requirements.

6.1 Task 1 – Software

The contractor shall provide a solution that includes the following capabilities:

Architecture/CMDB

Requirements

Provides tracking of assets and locations in a DISA Facilities utilizing a web front-end and/or client with a centralized back-end database.

Enables infrastructure to be managed and stored in the solution's repository. Must be able to differentiate between types of spaces classified as data center, office, warehouse, mechanical/electrical, etc. This classification will facilitate searching for all assets in a particular space, for example, all assets in a warehouse vs. all assets on the raised floor in a data center.

Enables the addition of unlimited user-defined fields (Make, Model, Serial #, Bar Code, Capacity, Capacity Units, UID#s, Parent UID#s, Child UID#s, Replacement Cost, Warranty Period, Comment, etc.) to the asset type record.

Allows for configurable printing options.

Prohibits acceptance of duplicate entries on specific defined fields.

Supports the following relationship information between Configurable Items (CIs) - one-to-one, one-to-many, many-to-many, many-to-one including hierarchical parent-child and connectivity between assets.

Supports the ability to change the sort and apply filters when searching for items in the solution's repository and on reports.

Supports the ability for users to select data for editing purposes by entering the information about the CI.

Supports auto-save capability for user data input to ensure minimum data loss in the event of system or network outage.

Provides capability for configurable user screens.

Scalable from one user to multi-plant.

Supports the use of bar code scanning and automatic updates to the inventory.

Architecture includes software for a centralized database using one of the DISA standard enterprise database servers for the solution repository.

Integrations/Interface

Requirements

Supports Web Service interface based virtual environment on standard protocols such as SOAP, and application APIs for integrating with other products.

Supports standard interface protocols such as ODBC, XML, and HTTP/HTTPS.

Supports bi-directional interface to DISA's enterprise CMDBs (ITSM).

Supports interface to DISA's enterprise CMDBs (DCIM, BAS).

Support interface to SharePoint/DEPS for dashboard functionality.

Optionally supports an interface to the U.S. Army CORP of Engineers Builder product.

Import/Export Capability

Requirements

Supports the capability to import and export data from the following file formats: .xml, .html, .htm, .pdf, .xlsx, .doc, .docx, Office 2010 - current releases.

Provides ability for importing and bulk loading data from legacy data sources (Oracle, MP2, Xcel, etc).

Security/Permissions

Requirements

Provides the ability to restrict access to portions of the infrastructure based on roles, location (e.g., site, campus, building, floor, rooms) or other user-defined grouping of System, Equipment and Component (SEC); restrict access to specific items; and restrict user view/update rights.

Work Orders

Requirements

For repeatable work tasks, allows automatic scheduling and automatic status performance reporting.

Repeatable WOs can be created once and reused across the Annual Schedule (Weekly, Monthly, Quarterly, and Annually).

Allows assignment of staff and responsible Manager for performance tracking and status reporting.

Additional information can be incorporated into the WO, such as materials, costs, and labor hours.

Incorporates Work-Flows that adapt processes to the business functions. Work-Flows define specific 'actions' and 'alerts' across the organization and direct individuals on 'how to proceed' (Task Instructions) in performing their related assignment.

Allows WO request submission by designated customers.

Provides ability to set specific fields as mandatory.

Supports the preventive (PM), predictive (PdM), condition-based (CBM), reactive maintenance (RxM) and Zero Failure Maintenance (ZFM) procedures and schedules for all Systems, Equipment, and Components that require PM, PdM, CBM, RxM and ZFM.

Allows for automatic generation of WOs based on BAS alarm events.

Inventory Management

Requirements

Incorporates technical specifications, OEM manuals, maintenance history, costs, and parts inventory of the SEC.

Allows for spare parts, material, and benchstock management.

Life cycle tracking from acquisition to disposition of SEC.

Reporting and Analytics

Requirements

Enables the user to customize reports, including imbedding formulas, concatenate data, and produce reports with specific color fields based on source data parameters.

Provides the ability to report on all assets in a DISA Facility, in a single data center and within a single room, including mission critical and non-mission critical spaces and equipment.

Provides the ability for flexible, configurable reporting to allow retrieval of all fields and data.

Supports a SQL query language that allows users to interactively interrogate the database and analyze its data.

Provides an ad-hoc reporting capability that generates reports based on ad-hoc queries.

Provides reports which combine a graphic view along with metadata (attributes) from the solution repository, along with user-specified metadata.

Provides the ability to report on SEC by allowing the user to specify the SEC and the metadata to be reported on for each SEC.

Provides the ability for users to create textual and graphic reports/templates by configuring standard reports that are created out-of-the-box by the application.

Provides the capability of generating scheduled reports on all data.

Provide the ability to display reports and graphs on SharePoint/DEPS in a dashboard format.

The COTS solution shall meet requirements captured in the PWS, be fully compliant with Department of Defense (DoD) information assurance requirements and security requirements, and be interoperable with the targeted DoD architectures. The software licensing and support shall cover the entire IT environment to include Non-classified Internet Protocol Router Network (NIPRNet) and pre-production enclaves. Maintenance does not become effective until the Government approves 100% solution.

The contractor shall ensure that the software products and any product enhancements associated with the products in this contract will support commercially available operating systems, hardware, and processing environment technologies, and must comply with all applicable Federal and DoD IPv6 policies and the DoD IPv6 Capable definitions as specified in the DoD Chief Information Officer (CIO) Memorandum, DoD Internet Protocol Version 6 (IPv6) Definitions, dated 26 June 2008. Additionally, the solution must be capable of interfacing with the DISA enterprise ITSM tool suite. This enterprise system uses an Oracle Real Application Clusters (RAC) backend databases.

The Contractor’s software solution must be able to operate within DoD guidelines and directives.

6.1.1 Subtask 1 – Program Management. The Contractor shall provide the technical and functional support required for the Program Management of this PWS including Quality Assurance, progress/status reporting, schedule development, integration, and status reporting, risk identification/handling/mitigation strategy, and Program Reviews. The Contractor shall provide the centralized administrative, clerical, documentation, and related functions needed to develop work products and demonstrate completion of activities required under this task. The Contractor shall assign organize, plan, schedule, implement, control, analyze, and report on all elements of the contract. The vendor’s Program Manager (PM) shall have resources and authority to ensure efficient and timely program execution and shall be the focal point within the contractor's activity for all required program tasks. The PM shall be the primary contact through which communications, work assignments, and technical directions flow between the Government and the Contractor. The Contractor shall assign a designated representative to act in the absence of the PM.

6.2 Task 2 – Technical Support

6.2.1 Subtask 1 – Internet and Toll-Free Based Support

The contractor’s product support staff shall be accessible via a toll-free support line and available to assist in resolving software errors, answering questions regarding installation procedures, compatibility with other software, and general questions of the licensed software products during and after installation. All calls to the toll-free support line are at no cost. There are no instances that a call would include a cost. The contractor shall also provide Internet-based support to facilitate status reporting (acceptance and socialization) of software problems, and provide downloads of software patches, fixes, and documentation.

6.2.2 Subtask 2 – Software Errors Support

Upon notification of software errors, the contractor shall respond to all emergency and urgent requests for software support. Response times for requests are based upon the software error severity level. Upon failure of the contractor to resolve software errors, the contractor shall escalate the issue(s) to the next level of issue resolution category until reaching the emergency level, at which time the contractor will focus all resources available to resolve the issue(s).

The contractor’s escalation process shall include clear procedures that outline the escalation process, the identification of management points of contact within the escalation process, and the ability to communicate directly with upper management when errors are not resolved.

6.2.2.1 – Software Errors Support - Severity and Support Response Times

Required availability and response time varies based on the severity levels. The severity level of a software error may be increased at DISA’s discretion up to a Severity 1, as the severity of the issue to DISA’s business increases, to verify proper focus and attention of the issue.

6.2.2.1.1 – Severity Level 1

Severity Level 1 consists of a system going down or a software product’s inoperative condition impacting a production environment.

· A production environment where the product is unable to run

· A product is preventing another production application from executing

6.2.2.1.2 – Severity Level 2

Severity Level 2 creates a high impact business condition, which endangers a production environment. The software may operate, but it is severely restricted.

· A major portion of the software product is unusable in a production environment

· A software product is causing another production application to not perform correctly or inhibits the production application’s ability to meet its commitments

6.2.2.1.3 – Severity Level 3

Severity Level 3 creates a low-impact business condition in which the majority of software functions are still usable; however, some circumvention may be required to provide service.

· The product is not performing as documented

· The product is causing another application to not perform correctly

6.2.2.1.4 – Severity Level 4

Severity Level 4 consists of minor problems or questions that do not affect the software functions.

· The customer has questions about the product

· The product is having minor problems

· The product is causing another product to have minor problems

MANAGED SOFTWARE ERRORS -

SUPPORT REQUIREMENTS:

SEVERITY 1

SEVERITY 2

SEVERITY 3

SEVERITY 4

EMERGENCY

URGENT

ROUTINE

1. 24 Hours x 7 Days x 365 Days a Year Contractor Support

1. 1 hour Voice Response (Contractor returns call to the Government within 1 hour)

1. Support Direct to DISA Managed / Maintained Facility

1. Resolution within 12 hours

X

1. 8 Hours x 5 Days x 52 Weeks a Year Contractor Support

1. 2 business hours Voice Response Support Direct to DISA Managed / Maintained Facility

1. Resolution within 24 hours

X

1. 8 Hours x 5 Days x 52 Weeks a Year Contractor Support

1. 4 business hours Voice Response Support Direct to DISA Managed / Maintained Facility Support Direct to Requestor

1. Resolution within 2 Business Days

X

1. 8 Hours x 5 Days x 52 Weeks a Year Contractor Support

1. 1 business day Response Support Direct to DISA Managed / Maintained Facility Support Direct to Requestor

1. Resolution within 5 Business Days

X

Software Errors - Support Requirements Table

6.3 Task 3 – Implementation of the CMMS Solution

The contractor shall provide on-site installation of the CMMS solution. The contractor shall also be responsible for configuration, integration, testing, and STIG remediation of the software solution.

Throughout the implementation process, the contractor shall provide a weekly activity report (WAR) outlining the progress of current and future tasks with completion status, as well identifying any issues that require Government interaction for resolution and/or impact agreed upon delivery. The contractor shall also submit monthly status reports (MSRs) that include financial and schedule status, proposed changes to the schedule, technical accomplishments, issues and risks, and planned activities for the next reporting period. Any issues requiring Government response or action shall be readily identified in both weekly and monthly reports.

Deliverable 1: WAR

Deliverable 2: MSR

6.3.1 Subtask 1 – Stage 1 – Project Setup and Initiation

Within 2 weeks of contract award, a technical interchange meeting (TIM) will take place either in person or via teleconference or a combination of both. The TIM will be the beginning of a dialogue between the Government and the contractor to ensure successful execution of this contract. The Government shall coordinate the date, place, and agenda for the TIM with the COR. The agenda shall include, at a minimum, the following:

1. Introduction of management and technical teams

1. Creation and approval of draft project management and engineering/implementation plans

Deliverable 3: TIM Minutes

Deliverable 4: Approved Draft Project Management Plan

Deliverable 5: Approved Draft Engineering/Implementation Plan

6.3.2 Subtask 2 – Stage 2 – Solution Requirements Definition

During this stage the contractor and the Government will review the current technical and existing product architecture documents or other materials related to the implementation effort to identify unique configurations or environmental considerations that may impact the implementation. The contractor shall review and document the requirements for NIPRNet and provide a solution requirements specifications document (SRS).

Deliverable 6: Solution Requirements Specifications document

Additionally, the contractor will work with the Government to establish and document the final project management plan as well as the final engineering/implementation plan for the solution architecture and design. The project team will define and document the design and configuration decisions needed to support the implementation. The team shall produce a final engineering plan document that contains the following:

1. Solution architecture model, which defines solution components and component interface specifications

1. Physical architecture model, which provides a network diagram, system specifications, and configurations

1. Validation approach document, which provides a high-level description of how the solution’s functional and non-functional requirements will be validated

1. Solution phasing document, which describes the sequence of phases to roll out the solution and the high-level integration plan

The contractor shall also provide a high-level solution test and integration plan.

Deliverable 7: Final Project Management Plan

Deliverable 8: Final Engineering/Implementation Plan

Deliverable 9: Test and Integration Plan

6.3.3 Subtask 3 – Stage 3 – Solution Install, Configuration, and STIG

During this stage, the contractor, as the lead, will work with the Government to install and configure the solution in a pre-production/test environment, located in Montgomery, Alabama or Oklahoma City, Oklahoma. Site determination will be made by DISA during the engineering solution development following contract award. Non-consecutive days of on-site installation support will be required for pre-production installation in the test environment. During this stage, the contractor shall also provide a draft configuration design document that summarizes the configurations that have been applied by the contractor to the solution in the pre-production and/or NIPRNet environments. This document shall contain the following:

1. Configuration specifics, including code changes, settings, etc.

1. Discovery methods for initial services

1. Integration and reporting configuration details

Deliverable 10: Installation Guide

Deliverable 11: Draft Configuration Design Document

The contractor will work with the Government to ensure all STIG requirements and application reviews are successfully conducted. The contractor will address any outstanding security items. Any outstanding items shall have a plan of action and milestones (POA&M) document.

Deliverable 12: POA&M Document

6.3.4 Subtask 4 – Stage 4 – Production Deployment and Integration

During stage 4, the contractor, as the lead, will work with the Government to install and configure the solution in a production environment for NIPRNet at the DISA site locations identified in the engineering solution. DISA requires non-consecutive days of installation support for the NIPRNet production environments within the Government sites.

During the implementation effort, Government personnel will receive CMMS solution knowledge transfer information, including documentation from the contractor describing DISA-specific installation and configuration items. The knowledge transfer information shall include tasks, personnel, and dates that the following activities were completed:

· Review of deployment architecture

· Demonstration of access management functionality

· Walkthrough discovery process

· Walkthrough configuration process

Deliverable 13: Final Engineering Solution Design Document

Deliverable 14: Final Configuration Design Document

Deliverable 15: Knowledge Transfer Activity Document

The contractor will conduct a technical wrap-up session with the Government to provide final project documentation and review the proposed next steps/phases. The Government shall coordinate the date, place, and agenda for the wrap-up session with the COR.

The mandatory publications listed herein and other guidance that can be obtained from http://iase.disa.mil will be critical in the contractor's successful implementation of the CMMS tool. The following publications are anticipated to be the absolute minimum IA documents necessary for the contractor to maintain certification and accreditation; other documents are possible dependent on the system(s) and components that are selected for implementation.

· DoDI 8510.01, Risk Management Framework (RMF) for DoD IT RMF

· Web Server STIG

· Database STIG

The contractor will work with the Government to ensure all STIG findings are mitigated and application reviews are successfully conducted. Any outstanding items shall be mitigated by the contractor or shall have a POA&M document submitted to the Information Assurance team to ensure compliance with the certification and accreditation process.

Once the solution is installed, configured, and in production by the contractor, the contractor shall load each site's data immediately after data is collected. As soon as the site data is loaded and validated, the site will assume responsibility for data and will update as changes are made. The contractor will have responsibility for the initial data load and validation with each respective site.

With regard to integration with identified systems, the schedule contractor and DISA shall work together to determine the appropriate frequency of synchronization based on industry best practices.

6.3.5 Subtask 5 – Stage 5 – Testing and Quality Assurance

During this stage, for each environment, the vendor’s project team, along with operators and end users, will perform testing and quality assurance to verify operational integrity. The team will validate the pre-production environment and utilize test plans to ensure mandatory requirements are met as well as execute use cases supplied by the Government based on defined functional and technical requirements.

Deliverable 16: Testing and Quality Assurance Report

6.3.6 Subtask 6 – Stage 6 – Configuration and Backup Strategy Documentation

During this stage the contractor will complete the system configuration documentation and back up strategy. The vendor and government teams will review the backup strategy for the solution which identifies appropriate backup methodologies and recovery processes based on the requirements in the engineering solution.

Deliverable 17: Backup Strategy Documentation

Deliverable 18: System Configuration Documentation

6.3.7 Subtask 7 – Stage 7 – Implementation Handoff and Closure

During this stage, the project manager will conduct an implementation closure meeting or call to validate that the solution conforms to requirements identified in this PWS. The contractor shall coordinate the date, place, and agenda for the meeting with the COR. Along with a final overview of the solution, the project documentation will also be finalized, and an implementation sign-off letter will be completed.

Deliverable 19: Finalized Project Documentation

Deliverable 20: Implementation Sign-Off Letter

6.4 Task 4 – Operations Support

The contractor shall provide onsite training for the CMMS solution.

6.4.1 Subtask 1 – Classroom Training

The contractor shall provide training for personnel based on roles and positions associated with the implemented solution. Training courses shall be specifically designed and developed for DISA’s configuration and implementation.

The contractor shall provide the following six (6) total trainings at DISA CONUS or OCONUS locations:

· Two instructor led trainings to cover administration of the solution for six (6) students each

· Two instructor led trainings to cover users of the solution for up to forty (40) students each

· Two instructor led trainings to cover reporting with the solution for twenty (20) students each

Training may be conducted virtually in conjunction with onsite training sessions in order to provide training to additional sites with government approval.

6.4.2 Subtask 2 – Training Materials

The contractor shall develop and provide the training material for implemented capabilities as identified by the Government. The Contractor shall develop a recommended training package with appropriate training material for approval by the Government. Training packages will consist of, but are not limited to, training documentation, course outline, course learning objectives, test bank of review questions, operational scenarios, and storyboards, Frequently Asked Questions (FAQ), and instructor notes. The Contractor shall develop and update training materials based on lessons learned and approved configuration changes. Training materials are anticipated to be developed at the unclassified levels, as needed and appropriate. All training materials should be scrubbed via a thorough quality assurance process prior to delivery. All documentation and software/media used for training must be approved by the Government and shall become the property of the Government upon delivery.

Deliverable 21: Course Materials

6.5 Task 5 – Option Year Software Support

The contractor shall provide software support for all software under the contract for the option years. Software support consists of software support, updates, revisions, error detection and correction, and rights to new releases and/or versions.

Deliverable 22: Option Year Software Support

6.6 Task 6 – Optional on-site data collection for Stuttgart-Vaihingen, and Wiesbaden,Germany for the CMMS Solution

The contractor shall provide on-site data collection for Stuttgart-Vaihingen, and Wiesbaden, Germany for the CMMS Solution at this OCONUS site.

Deliverable 23: Option Year travel to Stuttgart-Vaihingen, and Wiesbaden, Germany OCONUS site for collection and inclusion of data in CMMS system

6.7 Task 7 – Optional on-site data collection for Bahrain for the CMMS Solution

The contractor shall provide on-site data collection for Bahrain for the CMMS Solution at this OCONUS site.

Deliverable 24: Option Year travel to Bahrain OCONUS site for collection and inclusion of data in CMMS system

7. Performance Standards.

Performance Standard

Acceptable Quality Level (AQL)

Method of Surveillance

Task 3 Implementation of CMMS Solution (PWS para 6.3)

Deliverables –

· Weekly Activity Report

· Monthly Status Report

Delivery occurs on time in accordance with paragraph 11. Performance occurs with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

Subtask 1 - Stage 1 - Project Setup and Initiation (PWS para 6.3.1)

Deliverables –

1. TIM Minutes

1. Approved Draft Project Management Plan

1. Approved Draft Engineering/Implementation Plan

1. Solution Requirements Document

Delivery occurs on time in accordance with paragraph 11. Performance occurs with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

Subtask 2 - Stage 2 – Solution Requirements Definition (PWS para 6.3.2)

Deliverables

· Solution Requirements Specification

· Final Project Management Plan

· Final Engineering/Implementation Plan

· Test and Integration Plan

Delivery occurs on time in accordance with paragraph 11. Performance occurs with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

Subtask 3 - Stage 3 – Solution Install, Configuration, and STIG (PWS para 6.3.3)

Deliverables –

· Installation Guide

· Draft Configuration Design Document

· PO&AM Documentation

Delivery occurs on time in accordance with paragraph 11. Materials/Performance occur with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

Subtask 4 - Stage 4 – Production Deployment and Integration (PWS para 6.3.4)

Deliverables –

· Final Engineering Solution Design Document

· Final Configuration Design Document

· Knowledge Transfer Activity Document

Delivery occurs on time in accordance with paragraph 11. Materials/Performance occur with no required re-work, contains required information at least 80% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

Subtask 5 - Stage 5 – Testing and Quality Assurance (PWS para 6.3.5)

Deliverable

· Testing and Quality Assurance Report

Delivery occurs on time in accordance with paragraph 11. Materials/Performance occur with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

Subtask 6 - Stage 6 – Configuration Documentation and Backup (PWS para 6.3.6)

Deliverables –

· Systems Configuration Documentation

· Backup Strategy Documentations

Delivery occurs on time in accordance with paragraph 11. Materials/Performance occur with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

Subtask 7 - Stage 7 – Implementation and Handoff (PWS para 6.3.7)

Deliverables

· Finalize Project Documentation

· Implementation Sign-off Letter

Delivery occurs on time in accordance with paragraph 11. Materials/Performance occur with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

Task 4 – Operations Support (PWS para 6.4)

Subtask 1 – Classroom training

Deliverable – Training Classes

Delivery occurs on time in accordance with paragraph 11. Materials/Performance occur with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

Random sampling/Training surveys

Subtask 2 – Training Materials

Deliverable – Course Material

Delivery occurs on time in accordance with paragraph 11. Materials/Performance occur with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

Task 5 - Option Year Software Support (PWS para 6.5)

Deliverable – Software maintenance support agreement

Contractor –Determined format. Delivery occurs on time in accordance with paragraph 11. Materials/Performance occurs with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

Task 6 – Optional on-site data collection for Stuttgart-Vaihingen, and Wiesbaden, Germany

Deliverable – Option Year travel to Stuttgart-Vaihingen, and Wiesbaden, Germany OCONUS site for collection and inclusion of data in CMMS system

Delivery occurs on time in accordance with paragraph 11. Materials/Performance occur with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

Task 7 – Optional on-site data collection for Bahrain

Deliverable – Option Year travel to Bahrain OCONUS site for collection and inclusion of data in CMMS system

Delivery occurs on time in accordance with paragraph 11. Materials/Performance occur with no required re-work, contains required information at least 90% of the time. Revisions/problems that occur are minor and are resolved in a satisfactory manner.

100% inspection

8. Incentives. None prescribed.

9. Place of Performance. The work will be performed at the current DISA CONUS and OCONUS DECC’s.