RFP F20R010040 RFI amendment 1.pdf

(x)

33330220RF0010040

x x copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted ; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR

OFFER. If by virtue of this amendment you desire to change an offer already submitted , such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

x

OCON

Washington DC 20013-7012

MRC 1200

P.O. BOX 37012

OCON

OCON

Washington DC 20013-7012

MRC 1200

P.O. BOX 37012

SMITHSONIAN INSTITUTION

07/09/20200001

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

12. ACCOUNTING AND APPROPRIATION DATA (If required) is not extended.is extended, Items 8 and 15, and returning

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended , by one of the following methods: (a) By completing

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

FACILITY CODE CODE

10B. DATED (SEE ITEM 13)

10A. MODIFICATION OF CONTRACT/ORDER NO.

9B. DATED (SEE ITEM 11)

9A. AMENDMENT OF SOLICITATION NO.

CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

7. ADMINISTERED BY (If other than Item 6)CODE 6. ISSUED BY

PAGE OF PAGES

4. REQUISITION/PURCHASE REQ. NO.3. EFFECTIVE DATE2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO. (If applicable)

1. CONTRACT ID CODE

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

07/09/2020

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority) appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

E. IMPORTANT: Contractor is not is required to sign this document and return __________________ copies to the issuing office.

ORDER NO. IN ITEM 10A.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

This is amendment 1 to the above numbered solicitation.

The due date for proposals is unchanged.

The following RFIs are hereby integrated into the requirements of this solicitation.

Q1. First, are these systems you have utilized in other spaces already (other Smithsonian locations)? It seems you are looking to build a lighting control system from the ground

up. Was there a reason you are looking to start from scratch instead of utilizing products/protocols in the lighting controls world that are fully built out, tested, and reliable for use in many large museum spaces across the world?

A1. The Smithsonian has not implemented a system with these specific capabilities before, Continued ...

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)15A. NAME AND TITLE OF SIGNER (Type or print)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED

(Signature of person authorized to sign) (Signature of Contracting Officer)

Thomas Dempsey

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

Previous edition unusable

Except as provided herein, all terms and conditions of the document referenced in Item 9 A or 10A, as heretofore changed, remains unchanged and in full force and effect .

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

NAME OF OFFEROR OR CONTRACTOR

2 4

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

(A) (B) (C) (D) (E) (F)

33330220RF0010040/0001

although we do have a prototype control system in place as a proof of concept.

Q2. What you have put together is a very interesting request and I am curious to understand why you went this route. Are you willing to look at systems that would be able to provide the UI you are requesting, but come with built out warranties and full support systems in place should bugs arise?

A2. The project requirements do not specify that the solution must be customized, however any commercially available product would have to meet all the requirements described in Section C.4

Project Requirements. We would consider any proposals that meet these requirements, whether customized, or commercially available.

Q3. There is a mention of ¿a touchless interaction design approach¿, which is then referred to a couple of times in the RFP. Is there any clarification of what is to be provided by the respondent as part of the intended scope of work?

A3. The implementation of the Touchless layer was left open so that vendors would have an opportunity to propose innovative solutions.

Since the requirements are fairly specific

(parallel to the GUI requirements, and

¿touchless¿) the respondent would need to articulate how touchless interaction would reimplemented the intended scope of work, this could be articulated as a method (gestures) or technology (haptics, etc.¿).

Q4. Xicato includes triggers for Behaviors. The data model does not include information related to these triggers. Is there an intention to be able to map triggers to behaviors? Is there an intention to be able to use these triggers outside of Xicato, for example, Modbus commands via Medialon Manager?

A4. Not Xicato triggers, no. Behaviors in this control system are a higher-level concept that can apply to any control system object, whether it is a xicato device, modbus device, DMX device, or group. The high-level functionality of each behavior is predetermined, but the attribute and trigger values may be abstractly assigned. A good example is daylight harvesting. The base behavior is to fade between two different scenes based on a trigger value. Each object that has daylight harvesting behavior assigned to it may

Continued ...

NSN 7540-01-152-8067 OPTIONAL FORM 336 (4-86)

Sponsored by GSA

FAR (48 CFR) 53.110

3 4

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

(A) (B) (C) (D) (E) (F)

33330220RF0010040/0001

also assign specific High/Low scene values, fade times, and data trigger values, using any data in the database. If you think of each control system object/device as a class (in the object-oriented sense), each behavior would be a common method they all share. Please note that creating behaviors is not a requirement of the

Base Contract, only assigning those values to the database within the data model through the Ux interface.

Q5. The connections to the database are labeled

ODBC. Is that a requirement or can a standard

PostgreSQL connection be used?

A5. The database connection protocol may be refined during the Discovery Phase. ODBC is not a requirement (more of a placeholder).

Q6. The software schematic has software segregated into specific boxes. Is this a requirement or can a different layout be proposed?

A6. The segregation is not required, however the relationships between components is. Meaning two components (two boxes) could be combined into a single VM, permitting it does not exceed the capabilities of the VM. Since SI is commissioning Hypervisor we would have to see alterations to the software component schematic clearly defined in the proposal in order to evaluate whether the change is feasible.

Q7. Are the scheduling zones fixture selection required to be end-user adjustable?

A7. Logical Control Zones (those in Attachment N

- DWRC Zone Layout) are pre-determined and are not intended to be adjusted by the end user.

That graphic is meant to illustrate an end-user selecting a pre-determined zone, not defining it.

Q8. Is offline programming required? If so, what functionality is required.

A8. Offline programming is not required for the

Contractor furnished components, however there are basic extensibility requirements so that they may be modified, if necessary.

Q9. What is the expected latency and network topology between the VMs and the field devices?

Are layer 2 connections possible or strictly layer 3?

A9. Layer 3. The VM¿s are physically in a different zip code than the gateways and other endpoint nodes. We would like to minimize latency, obviously, but we don¿t have benchmark requirements (1ms per API command, etc.¿)

Continued ...

NSN 7540-01-152-8067 OPTIONAL FORM 336 (4-86)

4 4

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

(A) (B) (C) (D) (E) (F)

33330220RF0010040/0001

Q10. What level of software redundancy is required for the Contractor furnished components?

A10. The Scheduling Software is required to have a ¿High Availability¿ software model. We do not require software redundancy for the Ux Software, but we would recognize it as a valuable contribution.

NSN 7540-01-152-8067 OPTIONAL FORM 336 (4-86)