Government_ResponseQA_26_MAR19.xlsb
XLSB spreadsheet 84 KB Posted
- Attached to
- Meter Data Management System (MDMS)
- Solicitation number
- W912DY-19-R-0022
About this file
This is a request for proposals from the Department of the Army Corps of Engineers Engineering Support Center Huntsville for meter data management services. The selected contractor will operate, sustain, and maintain a centralized meter data management system to deliver dependable meter data, normalize facility energy consumption data using industry standards, and provide tools through an interface for facility and energy program managers to identify energy reduction opportunities. Services are to be provided throughout the United States and its territories as well as in Germany, Italy, Japan, and South Korea. Proposals are due no later than April 5, 2019 by 2:00 PM Central Time and shall be shipped to the specified Huntsville address. The associated North American Industry Classification System code is 541512 for computer system design services and the Product Service Code is 7035 for information technology support equipment.
Amendment 0003, Government's Response to questions
Text of this file
Table 1
| 7878660 Contracting due date | Government Response | Internal Notes | ||||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | ||||||
| Given the details and attachments required to be reviewed and responded to under W912DY-19-R-0022, and the fixed price nature of the proposal to be submitted. Will the government please consider and grant a 14 day extension to the proposal due date? | There will be no extension to the solicitation at this time. | |||||
| On: Mar 07 2019. | ||||||
| Current Request Status: Request Pending | ||||||
| Information for this report is procurement sensitive. | ||||||
| 7879847 Contracting Page 1 and 83 | ||||||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | ||||||
| Request clarification of the appropriate SB NAICS Code. | ||||||
| Page 1: NAICS Code: 541512 The small business size standard is less than $27.5M. | ||||||
| Page 83; The North American Industry Classification System (NAICS) code for this acquisition is 561210. The small business size | ||||||
| standard is $38.5M. On: Mar 08 2019. | ||||||
| Current Request Status: Request Pending | ||||||
| Information for this report is procurement sensitive. | ||||||
| 7882666 Contracting Attachment VIII Sample Task Order | ||||||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | ||||||
| Appendix A is referenced 8 times in this document, as in Section 2.3: "The Contractor shall provide a detailed labor effort breakout for this task in the format provided in Appendix A." | ||||||
| Will the Government please provide Appendix A for providing the requested detailed breakout? On: Mar 11 2019. | Appendix A provided in Amendment 02 | Pre-Award | ||||
| Current Request Status: Request Pending | ||||||
| Information for this report is procurement sensitive. | ||||||
| 7886598 | Program Management | Request for extensions | ||||
| Comment Classification: UNCLASSIFIED (U) |
1. Will the government extend the question period for an extra seven days?
2. Will the government extend the RFP response by 60 days to provide the government time to answer and clarify the many questions we will be submitting?
| On: Mar 12 2019. | See government's response to question #7878660 | Pre-Award and PM | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7886605 | Contracting | Section L | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Given the complexity of the solicitation and detail required in the response would the government consider a 30 day extension in order that we may provide the best possible solution.
| On: Mar 12 2019. | See government's response to question #7878660 | Pre-Award and PM | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7886894 | Energy Mon | ||||
| & Controls | N/A | N/A | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | |||||
| Since another amendment was issued today, will the government extend the question period for an extra week? On: Mar 12 2019. | See government's response to question #7878660 | Pre-Award and PM | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7886895 | Energy Mon | ||||
| & Controls | N/A | N/A | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Since the answers to the hundreds of questions still need to be posted by the government, will the government extend the RFP response by 60 days to provide time for the vendors to review and process the answers? This will allow for offerings that best fit the interests of the government.
| On: Mar 12 2019. | There will be no extension to the solicitation at this time. There were several repetitive questions throughout this document. | Pre-Award and PM | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7886903 | Energy Mon | ||||
| & Controls | N/A | N/A | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
As an OSIsoft Partner for decades, and having installed hundreds of PI systems mostly in the commercial facilities and utilities sectors, the most widely used OSIsoft interface products are PI-OPC-DA and PI-MODBUS. Has the government deployed either of them in the test system? Will the government allow these interfaces to be used in the production environment?
| On: Mar 12 2019. | No neither interface has been deployed. The vast majority of meter data are communicated through the EEDRS boxes. The EEDRS communicate up to MDMS via csv file and for the two pilot installations we will use the PI Universal File and Stream Loadoing Interface. Neither EEDRS sustainment nor below is the responsible of this contract. The EEDRS boxes may nor may not continue to handle the majority of interval data being sent to MDMS or the course of this contract. The MDMS contractor will serve to advise the Army over the period of this vehicle of architecture improvements below the gateways but execution of those changes are not the responsiblity of this program at this time. Currently sustainment belongs to the land holding commands. | Engineerinig | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887000 | Contracting | Vol III - Factor 3: Management Approach | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Vol. III has a 20-page limit. However, it is required to include resumes, letters of commitment, multiple plans, and more in this volume. Would the Government consider expanding the page limit to 40 pages to accommodate all information requested?
| On: Mar 13 2019. | Changed See Amendment 0002 | Pre-Award and PM | ||||
| Current Request Status: Request Pending | ||||||
| Information for this report is procurement sensitive. | ||||||
| 7887002 | Contracting | Key Personnel | ||||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | ||||||
| PWS 5.7 lists 4 key personnel senior positions, but the RFP Vol VI lists two mid-level positions as key personnel in addition to those | ||||||
| 4 senior positions. Please clarify how many and which positions are considered key personnel for proposal requirements. On: Mar 13 2019. | The 4 positions listed in section 5.7 are the key personnel meaning the government requires these positions to be filled no matter how the contractor decides to use the other labor categories to execute their plan for each task order. The Senior Energy Engineer and Senior Information Security Engineer position require 15 years experience meaning to be in alignment with the position experience required in section 5.6 they would be required to be senior pay scale rates. The other two key positions only require 9 years of experience meaning they could be filled at the mid-level or senior position rates. The government is trying to give the contractor maximum flexibility in how they execute outside these 4 positions as each of those 4 are paramount roles to program success. | Engineerinig | ||||
| Current Request Status: Request Pending | ||||||
| Information for this report is procurement sensitive. | ||||||
| 7887114 | Information Management | Page 35 | Proposal Format | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Is there a desire to have a formal cover letter and/or executive summary included in responses outside of the list of the cover letter with the list enclosures?
| On: Mar 13 2019. | Cover letter with authorized signature for the organization applies to overall proposal. Then a TOC for each of the volumes | Pre-Award and PM | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887135 | Contracting | RFP, p. 35 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
"A page printed on both sides shall be counted as two pages. Submission as double-sided printing/copying on recycled paper is encouraged."
Double-sided printing may cause blank "back" sides to some pages due to tab separator pages between major sections in the binders. Please confirm that such "blank" pages and tab separator pages will be EXCLUDED from page count.
| On: Mar 13 2019. | 3See Amendment 03 | Pre-Award and PM | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887138 | Contracting | RFP, Location, p. 2 of 95 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
RFP, Location, p. 2 of 95 and Attachment V MDMS Pricing Spreadsheet "This work will occur at sites located throughout the United States and its Territories, and Hawaii, Germany, Italy, Japan and the Republic of Korea."
a) Is work to be performed at government or contractor site?
| b) Is pricing to be government or contractor site? On: Mar 13 2019. | The contractor may perform the work outside of a government facility except for the potential short term TDYs to support gateway sustainmnet at installations. | |||
| Current Request Status: Request Pending | ||||
| Information for this report is procurement sensitive. | ||||
| 7887140 | Contracting | RFP, Proposal Format, p. 35 of 95 | ||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
RFP, Proposal Format, p. 35 of 95 "Page Limitations. The cover letter, title page, table of contents, table of figures, list of tables and glossary of abbreviations & acronyms do not count against page count limitations."
Please confirm that resumes, letters of commitment for Key Personnel, past performance questionnaires (PPQ), and subcontractor letters of commitment or teaming agreements are EXCLUDED from the page limitations.
| On: Mar 13 2019. | See Amendment 03 | Pre-Award and PM | ||||
| Current Request Status: Request Pending | ||||||
| Information for this report is procurement sensitive. | ||||||
| 7887143 | Information Management | Page 38 | VOLUME IV – Factor 4 – PAST PERFORMANCE | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | ||||||
| Do the PPQs count towards the page limit? On: Mar 13 2019. | See Amendment 03 | Pre-Award and PM | ||||
| Current Request Status: Request Pending | ||||||
| Information for this report is procurement sensitive. | ||||||
| 7887151 | Information Management | Page 38 | VOLUME III – Factor 3 – MANAGEMENT APPROACH: | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | ||||||
| Is there a letter of commitment form that we need to use? On: Mar 13 2019. | No sample letter of commitment was provided with this solicitation. | Pre-Award and PM | ||||
| Current Request Status: Request Pending | ||||||
| Information for this report is procurement sensitive. | ||||||
| 7887165 | Information | Amendment VIII | Task 03 Energy Engineering | |||
| Management | ||||||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Pertaining to the Amendment VIII performance work statement, do all buildings have meters measuring their entire utility consumption and pass data to the MDMS? For buildings that do not have complete utility metering (natural gas, propane, chilled/hot water, steam, etc), will a list be provided to the solution provider detailing such information?
| On: Mar 13 2019. | No not all facilities have meters measuring their entire utility consumption. The governement does not have a list of buildings that are not completely metered. | ||||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887188 | Information Management | Sample Task Order | Task 01 | ||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Will the data quality downstream of the MDMS gateway be within the responsibility of the solution provider? (I.e. data quality issues related to the EERS/UMCS or BPOC.
| On: Mar 13 2019. | No. Contractors will only be responsible for data quality within the MDMS program responsibilites. Contractors should be expected to advise the government of issues downstream and advise the government on downstream architectural improvements or issues. | |||
| Current Request Status: Request Pending | ||||
| Information for this report is procurement sensitive. | ||||
| 7887306 | Contracting | RFP, p. 35 and 36, Proposal Format | ||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
RFP, p. 35 and 36, Proposal Format On page 35, the RFP states, "The proposal shall be accompanied by a cover letter prepared on the company's letterhead stationery. The cover letter shall identify all enclosures being transmitted and shall be used only to transmit the proposal and shall include no other information."
On page 36, the RFP states, "Each volume in the proposal shall include a copy of the cover letter, title page and table of contents."
Please clarify whether a single cover letter in a separate file and outside the binders should be submitted, or the cover letter should be included in each Volume file and binder.
| On: Mar 13 2019. | See response to Question # 7887114 | Pre-Award and PM | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887308 | Contracting | RFP, p. 38, Volume IV – Factor 4 – Past Performance AND | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
RFP, p. 38, Volume IV – Factor 4 – Past Performance AND Attachment 1 Past Performance Questionnaire The instruction in the RFP states, "Completed PPQs should be submitted with the Offeror's proposal" unless the client requests to submit directly to CEHNC-MDMS@usace.army.mil and Robin.Boateng@usace.army.mil.
The instructions in the Attachment 1 Pat Performance Questionnaire (PPQ) state, "Please return this completed Questionnaire via e-mail to the Contract Specialist at robin.L.boateng@usace.army.mil Thank you for your assistance."
a) Please clarify whether the completed PPQs are to be submitted by the Offeror in their proposal, or all PPQs are to be submitted electronically directly to USACE.
b) If the answer to (a) is that all PPQs are to be submitted directly to USACE by email per the instruction in the Attachment 1, please clarify if Offerors still need to provide the first page of the PPQ in the proposal.
| On: Mar 13 2019. | Attachment 1 Revised | Pre-Award and PM | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887310 | Contracting | RFP, p. 35 of 95, Page Limitations | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
RFP, p. 35 of 95, Page Limitations The instructions provide a page limit of 10 pages for Volume IV, Past Performance; however, if past performance questionnaires (or the first pages thereof) are to be submitted by the Offeror in this volume and there may be up to 25 projects with PPQs, and the PPQ is 4 pages long, the page limit cannot be met.
| Please clarify and increase the page count for Volume IV. On: Mar 13 2019. | See Amendment 03 | Pre-Award and PM | ||
| Current Request Status: Request Pending | ||||
| Information for this report is procurement sensitive. |
| 7887314 | Contracting | RFP, 9.23 Meetings, Materials, and Briefs, p. 93 of 95 |
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
RFP, 9.23 Meetings, Materials, and Briefs, p. 93 of 95 "The Contractor may be required to attend specified meetings for the purpose of discussing any number of issues pertaining to the task order or potential future task orders. Such meetings may be held at the Contractor's office or other government designated locations."
| Where "physically" are the "government designated locations" for these briefs? In Huntsville? On: Mar 13 2019. | The MDMS program is managed out of USACE Huntsville Center. Some meetings may be required at other government facilities to include garrisons or leadership facilities. | Anyone | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887320 | Contracting | Attachment V MDMS Pricing Spreadsheet | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment V MDMS Pricing Spreadsheet Can Offerors alter the Price Proposal (Attachment V. MDMS Pricing Spreadsheet) to add whether the non-loaded labor was a subcontracted position versus a Prime filled position, as each would bear a different indirect burdened based on our accounting practices. This would help avoid any issues analyzing submissions.
| On: Mar 13 2019. | No. A contractors accounting practices are not the responsibilty of the government. The rates apply whether executed by the prime contractor or a sub-contractor. | Pre-Award and PM | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887326 | Contracting | Attachment VII, PWS, Section 5 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 5 and RFP, Volume VI – Factor 6 – PRICE/COST RELATED INFORMATION, p. 40 The PWS lists four (4) Key Personnel positions. The RFP notes six (6) Key Personnel. Please confirm the required Key Personnel positions and levels.
| On: Mar 13 2019. | The 4 positions listed in section 5.7 are the key personnel meaning the government requires these positions to be filled no matter how the contractor decides to use the other labor categories to execute their plan for each task order. The Senior Energy Engineer and Senior Information Security Engineer position require 15 years experience meaning to be in alignment with the position experience required in section 5.6 they would be required to be senior pay scale rates. The other two key positions only require 9 years of experience meaning they could be filled at the mid-level or senior position rates. The government is trying to give the contractor maximum flexibility in how they execute outside these 4 positions as each of those 4 are paramount roles to program success. If the program manager is filled by an employee with 11 years of experience they would get the mid-level program manager rate....if filled by an employee with 20 years experience they would use the Senior Rate. These apply when a contractor submits a proposal for a task order. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887329 | Contracting | Attachment VII, PWS, Section 5 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 5 and RFP, Volume VI – Factor 6 – PRICE/COST The PWS lists the "Program Manager" as Key Personnel, however, the RFP says "Senior Level Program Manager." Also, the PWS lists "Technical Director" and the RFP lists "Senior level Technical Director."
| On: Mar 13 2019. | The 4 positions listed in section 5.7 are the key personnel meaning the government requires these positions to be filled no matter how the contractor decides to use the other labor categories to execute their plan for each task order. The Senior Energy Engineer and Senior Information Security Engineer position require 15 years experience meaning to be in alignment with the position experience required in section 5.6 they would be required to be senior pay scale rates. The other two key positions only require 9 years of experience meaning they could be filled at the mid-level or senior position rates depending on experience. The government is trying to give the contractor maximum flexibility in how they execute outside these 4 positions as each of those 4 are paramount roles to program success. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887333 | Contracting | Attachment VII, PWS, Section 5 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 5 and RFP, Volume VI – Factor 6 – PRICE/COST RELATED INFORMATION, p. 40 The PWS lists the "Program Manager" as Key Personnel, however, the RFP says "Senior Level Program Manager." Also, the PWS lists "Technical Director" and the RFP lists "Senior level Technical Director."
| Please confirm the labor category(ies) and levels that are Key Personnel. On: Mar 13 2019. | The 4 positions listed in section 5.7 are the key personnel meaning the government requires these positions to be filled no matter how the contractor decides to use the other labor categories to execute their plan for each task order. The Senior Energy Engineer and Senior Information Security Engineer position require 15 years experience meaning to be in alignment with the position experience required in section 5.6 they would be required to be senior pay scale rates. The other two key positions only require 9 years of experience meaning they could be filled at the mid-level or senior position rates depending on experience. The government is trying to give the contractor maximum flexibility in how they execute outside these 4 positions as each of those 4 are paramount roles to program success. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887335 | Contracting | Attachment VII, PWS, Section 6.0, Software, p. 6 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | |||||
| Attachment VII, PWS, Section 6.0, Software, p. 6 of 19 | Version 3.4 . PI Vision and 2 copies of PI Data link, PI Server (Data Arcive and AF), and PI Interface (UFL) | Engineering | |||
| What versions of OSIsoft PI Server and tools will be, or are installed? |
On: Mar 13 2019.
| Current Request Status: Request Pending | ||
| Information for this report is procurement sensitive. | ||
| 7887339 | Contracting | Attachment VII, PWS, Section 6.9, p. 7 of 19 |
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 6.9, p. 7 of 19
| Will USACE be providing geospatial information for existing and new meter installations? On: Mar 13 2019. | USACE will provide geospatial information for existing meters where available. If no geospatial information is availible the contractor may use the center of a facility polygon or a facility polygon which are Army CIP layers. Joins are made between the Real Property ID field in HQIIS and the Real Property ID field in the facility geospatial feature. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887342 | Contracting | Attachment VII, PWS, Section 6.5, Test Environment, p. 7 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 6.5, Test Environment, p. 7 of 19
| How many development (Dev) and production (Prod) environment servers are involved? On: Mar 13 2019. | Currenlty around 13 with MDMS V2. We are looking forward in this solicitation to an full COTS implementawtion that meets objectives from section 2 of the PWS or section 1.1 of the Sample Task Order. The past architecture is not as relevant as where we are going. A contractor will be free to use to whatever test environment they feel is best. This section references the PWS (Base contract scope). | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887347 | Contracting | Attachment VII, PWS, Section 6.5, Test Environment, p. 7 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 6.5, Test Environment, p. 7 of 19
| Will the government provide the system architecture for the Dev and Prod environments? On: Mar 13 2019. | Yes | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887349 | Contracting | Attachment VII, PWS, Section 6.5, Test Environment, p. 7 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 6.5, Test Environment, p. 7 of 19
| What system interfaces will be required for the Development environment? On: Mar 13 2019. | UFL is the only current requirement. Requirements may change. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887351 | Contracting | Attachment VII, PWS, Section 7.3, p. 8 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 7.3, p. 8 of 19
| How many common controls have been identified for the existing MDMS Version 2 system? On: Mar 13 2019. | Common, or inherited, controls are 62 of 309. Of those, 22 are Tier 1 common controls. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887356 | Contracting | Attachment VII, PWS, Section 8.0, Billing, p. 9 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 8.0, Billing, p. 9 of 19 Does the data need to be automatically fed into a billing system? If so, what billing systems, data exchanges, and interfaces are you currently utilizing?
| On: Mar 13 2019. | No. The billing requirement in the PWS is only to produce a report so that an energy manager may forward that report about facility consumption and utility cost via email to resource management for execution in an approved Army billing system. The contractor is not expected to interface with any billing system. Reports would look similar to a bill a residential or commercial client receives explaining usage and cost. Most likely report would be in .pdf format. Ideally an energy manager with multipile tenants could produce multiple reports/pages with one click. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887360 | Contracting | Attachment VII, PWS, Section 9.1, Parsing & Cleaning Time- Stamped Meter Data, p. 9 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 9.1, Parsing & Cleaning Time-Stamped Meter Data, p. 9 of 19 Will the OSIsoft PI Integrator for Business Analytics (BA) be utilized to parse the data in the desired interval and to interpolate/extrapolate missing interval data?
| On: Mar 13 2019. | It will be up to the contractor to decide the best way to execute parsing the data. The government is not seeking to design through scope. The government only expects the system to provide time data in 15 minute intervals. Interpolate/extrapolating missing data should be done to best practices. Data should not be interpolated if it would be stastically inaccurate to provide that data. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887362 | Contracting | Attachment VII, PWS, Section 10.2, Benchmarking, p. 11 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 10.2, Benchmarking, p. 11 of 19
| Are the EUI and benchmark referenced tables auto updated or do they require periodic manual updates? On: Mar 13 2019. | The government is not seeking to design by scope and is instead looking to industry to recommend the most efficient way to calcualte metrics. Performance as viewed by the user should paramount to if EUI or benchmarks are calculated on the fly or through storage. Ideally at some point benchmarking should be model driven by actual Army data as Army has many unique facilities and use cases. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887366 | Contracting | Attachment VII, PWS, Section 11.1, p. 12 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 11.1, p. 12 of 19
| Are the necessary OSIsoft PI Interfaces identified, installed, and configured? On: Mar 13 2019. | The necessary PI interfaces will be implemented for the two installations as part of the current pilot project by September 2019. The contractor should expect over the course of the contract to be able to interface with whatever device/sensor/system that our every changing mission requirements dicate. The specifics will be detailed for task orders for the period of performance of those task orders. We are looking for highly adaptable and agile contractors to improve the program. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887369 | Contracting | Attachment VII, PWS, Section 12.2, p. 12 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.2, p. 12 of 19 What is the required frequency of OS, database, and web application vulnerability scans?
| Will scanning support be required for both MDMS Version 2 system and the OSIsoft PI system? On: Mar 13 2019. | OSIsoft PI is part of the 'system'; not separate. The DECC hosted servers are scanned monthly by the current host provider via ACAS. Mitigations are addressed by teh contractor or in coordination with the hosting provider. SCAP is done by the contractor working with DISA to ensure the STIG Checklist stay current. This is done monthly at a minimum. Changes may require off schedule scanning. The test lab environment is scanned quarterly or if needed to verify a new configuration, change, or address a mitigation effort for an alert. MDMS Gateway servers at the isntallation are updated monthly (minimum) by the contractor whether scan are completed by the host site or not. The contractor shall run SCAP scans against the gateway servers to ensure STIG compliance monthly. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887371 | Contracting | Attachment VII, PWS, Section 12.4, p. 13 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.4, p. 13 of 19
| Are code reviews automated or manual? If automated, is a code review tool identified? On: Mar 13 2019. | Automated. Currently using HP Fortify. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887375 | Contracting | Attachment VII, PWS, Section 12.8, p. 13 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.8, p. 13 of 19
| Does the system have a complete and up-to-date system hardware and software inventory? On: Mar 13 2019. | Yes | PM | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887379 | Contracting | Attachment VII, PWS, Section 12.8, p. 13 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.8, p. 13 of 19
| Have SCAP and ACAS vulnerability scanning tools been identified? On: Mar 13 2019. | The contractor shall use ACAS in the test environment against the fielded images. SCAP is used to assess the operational systems. ACAS of operation systems at the DECC are scanned via DECC ACAS administrators. Gateways are scanned by the NEC/RNEC where there is a willingness by the site to run such scans. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887383 | Contracting | Attachment VII, PWS, Section 12.11, p. 13 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.11, p. 13 of 19
| Does the system have a current Configuration Management Plan? On: Mar 13 2019. | Yes | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887387 | Contracting | Attachment VII, PWS, Section 12.11, p. 13 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | |||||
| Attachment VII, PWS, Section 12.11, p. 13 of 19 | BMC Track It is currently used to provide this function. | Engineering | |||
| Is there a tool in place for identifying configuration changes to a system? |
On: Mar 13 2019.
| Current Request Status: Request Pending | ||
| Information for this report is procurement sensitive. | ||
| 7887391 | Contracting | Attachment VII, PWS, Section 12.12, p. 13 of 19 |
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.12, p. 13 of 19
| Is the ISSO role in addition to the ISSE role? On: Mar 13 2019. | No. That requirement can be filled by the ISSE | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887394 | Contracting | Attachment VII, PWS, Section 12.19, p. 14 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.19, p. 14 of 19
| Has the system migrated to the NIST RMF Framework? On: Mar 13 2019. | Yes. Currently going through RMF reauthorization. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887397 | Contracting | Attachment VII, PWS, Section 12.19, p. 14 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.19, p. 14 of 19
| What is the status of current ATO? When does it expire? On: Mar 13 2019. | 28-Jun-19 | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887403 | Contracting | Attachment VII, PWS, Section 12.19, p. 14 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.19, p. 14 of 19 What is the status of the current system's security documentation? Does the system have a current System Security Plan and Contingency Plan?
| On: Mar 13 2019. | The status is green. Yes, the system has a System Security Plan. The System has an active ATO. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887409 | Contracting | Attachment VII, PWS, Section 12.19, p. 14 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.19, p. 14 of 19
| Does the system have interconnection agreements for all connections to other systems? On: Mar 13 2019. | Yes, where required. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887412 | Contracting | Attachment VII, PWS, Section 12.19, p. 14 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.19, p. 14 of 19 What is the FIPS-199 security categorization for the existing MDMS version 2 system? Will the OSIsoft PI system have the same categorization?
| On: Mar 13 2019. | C-I-A categorization is Low, Low, Low. | |||
| The OSIsoft PI system will have the same categorization. | Engineering | |||
| Current Request Status: Request Pending | ||||
| Information for this report is procurement sensitive. | ||||
| 7887417 | Contracting | Attachment VII, PWS, Section 12.21, p. 14 of 19 | ||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.21, p. 14 of 19
| Is the security documentation up to date in eMASS? On: Mar 13 2019. | Yes | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887423 | Contracting | Attachment VII, PWS, Section 12.21, p. 14 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 12.21, p. 14 of 19
| When were the security controls last assessed in eMASS? On: Mar 13 2019. | Currently under review (Mar 11-15) by the SCA-V as part of the reauthorization effort. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887428 | Contracting | Attachment VII, PWS, Section 13.4, p. 15 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 13.4, p. 15 of 19
| We understand that HQIIS serves as the Army's data warehouse, what kind of database platform does HQIIS use? On: Mar 13 2019. | HQIIS is a database containing real property information such as building use, square footage, build date, etc… We receive a quarterly Microsoft Access file. A web service is available for use but we have found that service is unreliable at this time to be used in real time. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887431 | Contracting | Attachment VII, PWS, Section 13.6, p. 15 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 13.6, p. 15 of 19
| What percentage of the meters in the field are manual (i.e., need to be read manually by someone looking at them)? On: Mar 13 2019. | None | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887435 | Contracting | Attachment VII, PWS, Section 15.7 Machine Based Learning, |
p. 17 of 19 Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) Attachment VII, PWS, Section 15.7 Machine Based Learning, p. 17 of 19
| In addition to the OSIsoft Asset Analytics and event frame notifications, what other machine learning tools will be utilized? On: Mar 13 2019. | The government is not seeking to design by scope. We are looking to hire industry experts to implement and utilize tools based on best practices. We are looking for a contractor to tell us how to best utilize these tools. As machine learning capabilites are quickly being utilized throughout industry and DOD those capabilites are included in the scope so that we may execute them if they are required in the best interest of the government over the next 5 years. The PWS is a base contract not a specific deliverable. It details what we can do under this vehicle. Details of what we will execute will be handle in task orders. If they were not included in the base contract PWS we would not be able to execute them under this vehicle. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887441 | Contracting | Attachment VII, PWS, Section 15.8, p. 17 of 19 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS, Section 15.8, p. 17 of 19
| Will the COTS software feed data into a maintenance system for work-order management? On: Mar 13 2019. | This is not in our current mission scope. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887443 | Contracting | Attachment VII, PWS | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, PWS
| Will the contractor be required to survey new and existing points or will this information be provided by the IGI&S Manager? On: Mar 13 2019. | The contractor may be required to do inverntory surveys under asset metadata management responsibilities. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887445 | Contracting | Amendment 0001, Attachment VIII, Sample Task Order, 1.2.4, p. 1 of 4 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Amendment 0001, Attachment VIII, Sample Task Order, 1.2.4, p. 1 of 4 Does the Government already have a Cloud Access Point (CAP) in place or should that be included in the overall cloud migration approach and schedule?
On: Mar 13 2019. At this time we have not designated a Cloud Access Point. Please remember this is an OACSIM/big Army mission being executed by USACE. USACE CAP are not relevant as this is not an internal USACE mission. Engineering
| Current Request Status: Request Pending | ||
| Information for this report is procurement sensitive. | ||
| 7887448 | Contracting | Attachment VIII, Sample Task Order, Section 2.5.4, p. 2 of 4 |
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VIII, Sample Task Order, Section 2.5.4, p. 2 of 4
| Army IGI&S QAPs are developed by OACSIM, does the Government mean "comply" with existing QAPs? On: Mar 13 2019. | Yes OACSIM IGI&S QAPS are developed by OACSIM…but this program is centrally funded by OACSIM and is the program of record for metering. If we collect the data for OACSIM through this program centrally it may not make sense for the garrison to perform duplicate work to collect this data and submit it through the usual IGI&S process when we already have that data so there could be a scenario where we development and sustain that plan...but most defintely OACSIM IGI&S would "own" that plan and we would comply with it. Please keep in mind this is a sample task order of things that may be asked to execute in actual task orders and conversations about the the actual implemnetation are only in the infancy stages of conversations. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887450 | Contracting | Attachment VIII, Sample Task Order, Section 3, p. 2 of 4 | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VIII, Sample Task Order, Section 3, p. 2 of 4 Does Task 0002 "Maintain the RMF Authorization" include the start-to-finish RMF effort for the new PI system in addition to the maintenance of the existing MDMS Version 2 RMF Authorization?
| On: Mar 13 2019. | No, PI is included as part of the overall security boundary for the current RMF effort underway. The system's RMF effort, to include PI, is expected to be completed before Jun 28, 2019. Changes occurring in the future will be through the change management process, or if required, as a new authorization effort depending on the scope of any changes. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887453 | Contracting | RFP, General | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
RFP, General
| What is the current level of effort? On: Mar 13 2019. | Current level of overall effort not relevant to future levels of effort. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887457 | Contracting | Attachment VII PWS and Attachment III PRS | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII PWS and Attachment III PRS
| Please provide current or trending metrics for the system. On: Mar 13 2019. | Current metrics for this soliciation are located in the Performance Requirements Summary. Objectives are locatad in section 2 of the PWS. We are looking to industrry to propose further metrics based on experience that are in alignment with objectives in section 2. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887471 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, Section 6.8 - Which Business Intelligence/Dashboarding platforms are being used? What dashboards currently exist? What reporting formats are required?
| On: Mar 13 2019. | None are currently being used. This is only in the scope of the new contract. MIS is a term used to descibe a method of quality surveillance in quality assurance management plans not a separate system. These are tools meant to help the government and contractor manage and quantify overall system health and performance. These reports could easilty be developed in the designated COTS tool modules or COTS tools that work with the designated COTS tool. PDF is most likely report for map. Excel most likely data export. We are looking for proposals from industry standard that meet objective in Section 2 of the PWS based on contractor experience. The government is not seeknig to design through scope. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887472 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | |||||
| Is the data currently being collected in the desired interval formal or does it require interpolation/extrapolation? On: Mar 13 2019. | Interpolation is often required due to reliability issues downstream. Downstream issues are out of scope for this contract. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887473 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | |||||
| Attachment VII, Section 9.0 - Does the meter data need filtering for outliers requiring further analysis? On: Mar 13 2019. | Yes, the tool should be able to identify all types of assets that are performing outside normalized limits whether they be facility level meters, sub-meters, or any type of asset. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887476 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | |||||
| Are there currently personnel maintaining the ESRI ARCGIS application and the OSIsoft integrator for ESRI? What layers of data | The ESRI ARGGIS OSIsoft integrator is not currently a part of the pilot. | Engineering | |||
| have been created and are being maintained? |
On: Mar 13 2019.
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887479 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | |||||
| Attachment VII, Section 9.1.2: What GIS system is currently used? Is one system used by all bases? On: Mar 13 2019. | This is a enterprise system so all users hit the enterprise servers. We are currently using ESRI products. The government has an ELA with ESRI. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887483 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Attachment VII, Section 9.1.2 - Are there CAD drawings available to be utilized by ArcMap to extract the asset locations for ArcGIS?
| On: Mar 13 2019. | No. Contractor should use Army GIS Common Installtion Picture layers. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887485 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | |||||
| How many users will be accessing the system. What user group types exist? On: Mar 13 2019. | The system is accessed by adminsitrators at the DISA DECC and by the contractor sustaining MDMS. Web users access the website front end to obtain reports/present data. There are no other 'users' for the system. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887487 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
To better understand the management of the various components, is the system installed on physical servers or in a virtualized environment? If virtual, what virtualization platform is in use?
| On: Mar 13 2019. | Most of the servers are on VMWare. Gateways are either virtual of physical. There remains 4 or 5 physical servers at the DISA DECC. The lab environment is virtual (VMWare). MDMS Administrator clients are physical laptops (GFE). | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887489 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) | |||||
| Will the vendor be required to manage DMZ assets including management of switches and firewalls for this project? On: Mar 13 2019. | No | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887495 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
The RFP does not outline any high availability or COOP failover requirements. Is this a requirement for implementation in the cloud and for the OSIsoft architecture? Will the contractor be expected to implement these options or to maintain them if they have been built? For COOP what are the Recovery Time Objective (RTO) and Recovery Point Objective (RPO) metrics?
| On: Mar 13 2019. | The system as a Continuity strategy/plan. There is no failover mandate for L, L, L systems. Continuity is addressed via DECC failover and recovering the system at the Montgomery DECC. The contractor is responsible for ensuring data is backed up and maintained to facilitate recovery of the systems and databases/data. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887499 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
What third part Operating Level Agreements (OLAs) are in place to coordinate change management across the various assets, enterprise services, and system interfaces which are managed by 3rd party organizations/vendors? In example, will there be a channel of communication to easily work with network or security operations personnel to open port communication access?
| On: Mar 13 2019. | Changes are coordianted with the hosting environment liason for enterprise production systems for the current MDMS. Gateway servers at the installation are coordinated through NETCOM and with the Regional Cybersecurity Center responsible for the DMZ where the server logically resides. Agreements are inplace today, but will likely need to be coordinated/updated after award. POCs at DISA, NETCOM, RCCs, and RNECs/NECs are already known, but changes over time are expected as pesonnel changes occur. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887504 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
Will the MDMS architecture be covered under an enterprise license agreement for the OSIsoft software? What license and support agreements are in place for other system components?
| On: Mar 13 2019. | At this time an enterprise license agreement is not in place for OSIsoft. | Engineering | |||
| Current Request Status: Request Pending | |||||
| Information for this report is procurement sensitive. | |||||
| 7887506 | Contracting | RFP | |||
| Comment Classification: Unclassified\\For Official Use Only (U\\FOUO) |
It is unclear from Attachment VII, Section…
This is the start of the file's text. The full file is on GovTribe.
Other files
Show all 23
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
File details come from the government source that posted it. Updated .