CMMS_-_Functional_Test_Plan_Attachment_3.docx
DOCX document 43 KB Posted
- Attached to
- Computerized Maintenance Management Software (CMMS) Solution Federal contract opportunity
- Solicitation number
- DHQCAP15MP60007
- Issued by
- Defense Information Systems Agency
About this file
Attachment 3 Functional Test Plan
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Questions_for_DHQCAP15P60007.docx | DOCX document | |
| RFP_CMMS_DHQCAP15MP60007_17_March.docx | DOCX document | |
| Sources_Sought_Questions.docx | DOCX document | |
| DHQCAP15MP60007_CMMS_PWS_8_March.docx | DOCX document | |
| RFP_CMMS_DHQCAP15MP60007_8_March.docx | DOCX document | |
| DHQCAP15MP60007_CMMS_QASP.docx | DOCX document | |
| DHQCAP15MP60007_CMMS_PWS.docx | DOCX document | |
| RFP_CLIN_Pricing_Worksheet.xlsx | XLSX spreadsheet | |
| Provisions_Clauses.docx | DOCX document | |
| RFP_CMMS_DHQCAP15MP60007.docx | DOCX document | |
| RFP_CMMS_DHQCAP15MP60007.docx | DOCX document |
Show all 11
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
COMPUTERIZED MAINTENANCE MANAGEMENT SOFTWARE (CMMS) SOLUTION
Functional Test Plan
FEBRUARY 23, 2016
DEFENSE INFORMATION SYSTEMS AGENCY
ENTERPRISE INFORMATION SERVICES (EIS)
Manpower, Personnel and Engineering (MPE1)
INTRODUCTION
PURPOSE OF THE TEST PLAN DOCUMENT
The primary objective of this test plan is to verify that the proposed solution(s) meet the requirements that were derived from the Performance Work Statement as proposed by the offeror. All items shall meet the applicable DoD STIGs and security checklists. The results from these tests will be used to validate the offeror’s proposal.
COMPETITIVE RANGE TESTING
TESTING OVERVIEW
The offeror will provide the government testing team with a job aide related to the functional items to be evaluated in order to assist the government team in navigating the system during testing. Offeror support will be available to the government during the two days allotted for the testing to answer questions and address any concerns.
2.2 SYSTEM SET-UP
The test environment consists of the Government’s VMware Virtual Operating Environment (VOE) set-up to simulate the production installation. The simulated environment will include representative data from mechanical, electrical, and plumbing equipment, as well as data from Sustainment, Repair and Modernization (SRM)-funded DISA facilities.
The offeror is providing a total CMMS solution. The offeror is required to supply a complete proposed solution to support testing. This will include at a minimum database, web, and application server software. During the testing process, any minor assistance given to offerors by the testing staff, or any comment or questions that take place during testing, will not constitute as an exchange (such as: clarifications, discussions or other communications) with offerors as discussed in FAR 15.306. Any such FAR 15.306 exchanges will solely be issued by the Contracting Officer.
“Total solution” means that whatever architecture (self-contained) the offeror is submitting for testing (hardware and software) at the functional stage of this effort must be provided for testing. It also means that each offeror MUST have all software, hardware, and installation documentation at the site location ready for testing. All software must be provided in the form of an ISO image file which will be remotely uploaded and expanded for installation on the government testing environment.
The offeror will instruct government personnel through the installation of their proposed solution onto the Governments testing environment. Offeror personnel will be permitted to monitor the test execution process, but will not be permitted to update the configured environment during testing. The offeror is responsible for all cost for their personnel in attendance during the testing period.
Offeror is responsible for the costs of shipping the complete solution to and from DISA. It is anticipated that testing will take place at DISA DECC Montgomery, Gunter AFB AL. Offeror’s solution will be shipped/delivered to DISA DECC Montgomery not later than 1 full business week prior to test initiation. Shipping address: DISA DECC Montgomery, ATTN: Harvey Green, (334) 416-1887, 401 East Moore Dr., Bldg 857, Maxwell AFB/Gunter Annex, Montgomery, AL 36114-3001, MARK FOR: Project: CMMS.
While testing will be done on the government environment in Montgomery, AL, installation activities may be completed remotely at a DISA location yet to be determined. All offeror’s in the competitive range will be notified of the actual location when they are identified as being within the competitive range.
2.3. TEST METHODOLOGY
Testing will be broken into two major categories:
· SRR (security review)
· Technical testing to include Functional and the ability to meet all technical requirements noted in the RFP Section 6.
Total testing time will be six (6) weeks:
| Five (5) weeks – installation/STIG |
| One (1) week – testing |
1.1 1.2
ITEMS TO BE TESTED
| Item to test |
| Test Description |
| User Access |
| User will log on, testing various role assignments / permissions |
| Import Data |
| User will import data from a legacy system |
| Name View/Map |
| User will name map/view and save changes |
| Modify View/Map |
| User will modify map/view to add, change, and remove items and save changes |
| Modify View/Map |
| User will modify map/view to rename assets, establish a new field for a Unique Identification # (UID #), and save changes |
| Search View/Map |
| User will search map/view for specific assets and requests |
| Drill up/down |
| User will drill down into the map/view to locate detailed information on assets and requests |
| Modify View/Map |
| User will establish a recurring request for a targeted asset |
| Modify View/Map |
| User will establish Parent-Child relationships for targeted assets |
| Reporting |
| User will run out of the box reports on assets, including work request historical information. |
| Reporting |
| User will create ad hoc reports including identification of Parent-Child relationships on targeted assets. |
| Export View/Data |
| User will export data from the system to .xml, .xlsx, html, docx files |
| User will print reports, tasks, or workflows |
TEST PASS/FAIL CRITERA
In the detailed use cases, expected results will be identified. When expected results are achieved, the test will be documented as passing. When expected results are not achieved, the test will be documented as a failure.
TESTING DELIVERABLES
Testing deliverables from the offeror include the job aide and detailed use cases. Test results will be fully documented and included as part of the Government’s technical evaluation.
TESTING ENVIRONMENT
The physical location for the test environment will be Montgomery, AL. Reference Section 2.2. Offeror personnel may be directed to another DISA location yet to be determined to complete remote installation/test activities.
3. TEST SITE LOGISTICS
Escorts – The site chosen to host remote installation and testing will identify an escort(s) to be the main points of contact with the offerors, responsible for the coordination of personnel coming in and out of DISA sites.
Badges – The escort(s) will handle the regulation of all badge requirements to enter the building. Working with DISA security personnel through the sign in and sign out procedures.
image1.png
File details come from the government source that posted it. Updated .