US Government Open Systems Specifications: … · • Fort Hood, Texas ... • Basewide System,...
-
Upload
nguyendang -
Category
Documents
-
view
215 -
download
1
Transcript of US Government Open Systems Specifications: … · • Fort Hood, Texas ... • Basewide System,...
US Government Open Systems Specifications:
Understanding the bidding process and vision
1
U.S. Army Corps of Engineers
Dave SchwenkEngineer Research Development Center Construction Engineering Research Laboratory
(ERDC/CERL) [email protected]
phone: 217-373-7241Will White
Huntsville Engineering Support Center [email protected]
phone: 256-895-1739
ConnectivityWeek 2010
US Government Open SystemsSpecifications
Outline
How we got to LON
Military funding
Doing business with the bureaucrats
2
Doing business with the bureaucrats
The good, the bad and the ugly
Getting better all the time
Some current Corps LON projects
ConnectivityWeek 2010
The U.S. Army Corps of Engineers is the Design and Construction Agent for Army and Air Force military facilities and many other government agencies
US Government Open Systems Specifications
3
U.S. government procurement regulations dictate that we obtain competitive bids and avoid sole source procurement
ConnectivityWeek 2010
So what’s the problem?
Multi-vendor DDC results in multiple software tools, laptops, & interface hardware
Proprietary supervisory architecture
Multi-vendor DDC is inevitable due to the Government’s competitive procurement rules.
Varied & incompatible building systems
Non-interoperable systems
Overall… a great deal of complexity and significant challenges for O&M staff, construction inspectors, and end users
12 O&M laptops (and counting) at one Army garrison ConnectivityWeek 2010
Open System Goals
1. One system. Multiple buildings with controls installed by multiple vendors are integrated into one system.
2. One common front-end providing users with interface to all buildings (monitoring, supervisory control, etc.).
5
3. One common tool for network management & device configuration. One tool for device programming would be great!
4. No future need for the original (installing) contractor or any particular device manufacturer.
ConnectivityWeek 2010
Open System Goal
The one-line version…
“One (integrated, multi-vendor) system
6
“One (integrated, multi-vendor) system
with no future dependence on any one
contractor or controls vendor.”
ConnectivityWeek 2010
Open System Options
A standard communications protocol is a critical component. While BACnet® is a viable option…
We identified CEA/ANSI-709 and LONWORKS® as the best solution:
7
best solution:
– Easier to get Open system
– End system more Open
– End system easier to use & maintain
ConnectivityWeek 2010
Building Automation Systems Criteria
MILCON RFP: Building Automation System
UFGS 23 09 23: DDC for HVAC & Other Local Building SystemsUFGS 25 10 10: Utility Monitoring & Control SystemUFGS 25 08 10: Utility Monitoring and Control System TestingECB 2004-11: UMCS and DDC Criteria UpdateECB 2005-17: LONWORKS, BACnet, and Building Automation Systems PlanningECB 2007-08: LONWORKS, BACnet, and Building Automation Systems PlanningUFC 3-401-01: Utility Monitoring & Control System (draft) (wbdg.org version is old)
8
UFC 3-401-01: Utility Monitoring & Control System (draft) (wbdg.org version is old)UFC 3-410-02: DDC for HVAC & Other Local Building Systems (draft) (wbdg.org version is old)
Proponent Sponsored Corps of Engineer Training (PROSPECT) courses
Crs 340: HVAC Control Systems: Design and Quality VerificationCrs 246: HVAC Control Systems: O&M
Notes: MILCON RFP : Military Construction Request For Proposal UFGS : unified Facilities Guide SpecificationsUFC : Unified Facilities Criteria (design guidance)ECB : Engineering and Construction Bulletin
ConnectivityWeek 2010
Building Automation Systems Criteria
--Unified Facilities Guide Specifications (UFGS)--
UFGS 25 10 10: LonWorks Utility Monitoring and Control System
UFGS 23 09 23: LonWorks DDC For HVAC & Other
9
UFGS 23 09 23: LonWorks DDC For HVAC & Other Building Control Systems
We need both the UMCS specification and building-level DDC specification for a complete system
ConnectivityWeek 2010
Basewide ANSI 709.1B over IP Network (EIA-852) >=100Mbps
BPOCRouter
RTRMore devices. No more RTRs
or RPTRs709
.3)
One or more workstation running: -GUI Clients -Network Management Tool Clients -Web Clients (optional)
One or more servers running: -LNS Server -Network Management Tool -Graphical User Interface (GUI) -Monitoring and Control Software -Web Server (optional)
UFGS 25 10 10
RTRnon-ANSI 709.1
BPOCGateway
RTR
RTRMore devices
and/or ‘subnets’
RTR
More devices. No more RTRs or
RPTRs
RTR
or RPTRs
AN
SI
709
.1B
ov
erT
P/F
T-1
0(I
AW
AN
SI7
UF
GS
2309
23
non-ANSI 709.1legacy system
RTR=RouterBPOC=Building Point Of ConnectionCircle = node (ANSI-709.1 device)
LONWORKS®
UMCS/DDC“Building Automation
System” ConnectivityWeek 2010
LON Specifications
LonWorks Utility Monitoring and Control System (UMCS)
UFGS 25 10 10
Central supervisory monitoring and control system
11
Central supervisory monitoring and control system
Interface to one or more multi-vendor building-level DDC systems
Does not specify/include the building-level controls (unlike the old UMCS specification)
ConnectivityWeek 2010
LON Specifications
LonWorks Direct Digital Control (DDC) For HVAC & Other Building Control Systems
UFGS 23 09 23
Building-level control systems and communications
12
Building-level control systems and communications network (based on CEA/ANSI-709.1 communications protocol)
Focus is on HVAC controls but supports other technologies (lighting, metering, etc.)
ConnectivityWeek 2010
Why 2 Specs?
Unbundle DDC bldg systems from the UMCS front-end:
• Buildings can run “stand-alone” with little/no user interface
• Provides clear demarcation of responsibility
• Helps keep the “fox out of the henhouse”
* * * * * * * * * * * *
13
* * * * * * * * * * * *
1- Competitive procurement for (DDC) building systems
-- AND --
2- Single base-wide (UMCS) front-end operator interface with consistent ‘look and feel’ for monitoring, control, & mgmt across vendors -- can be multiple workstations/clients.
ConnectivityWeek 2010
DDC (building-level)Requirements Summary
Standard protocol: ANSI/CEA-709.1B
Standard Network Variable Types (SNVTs)
CEA-852 router (providing for flat architecture)
Building Control Network: TP/FT-10 with backbone
LonWorks® Network Services (LNS®) database for the building
LNS Plug-ins for ASCs
14
LNS Plug-ins for ASCs
LONMARK® certification for ASCs
Few/no gateways
Configurable using standard means: SCPT, UCPT, SNVT
System Scheduler (on/off Occupancy) as prescriptively specified
Points Schedule submittal – very important documentation
Software and licenses submittals
ConnectivityWeek 2010
Types of Project Funding for Military Facilities
MILCON (Military Construction)
– New construction and major renovations
O&M (Operations and Maintenance)
15
O&M (Operations and Maintenance)
– Ongoing maintenance/upgrades
ConnectivityWeek 2010
MILCON Projects
Corps of Engineers District provides design & specification services/oversight to Garrison
– Specs: UFGS or MILCON RFP
Most projects include controls. Usually low bidder as a
16
Most projects include controls. Usually low bidder as a sub to the prime gets the work.
Can include UMCS with award to a controls manufacturer or systems integrator
ConnectivityWeek 2010
O&M Projects
Local garrison usually provides design & specification services/oversight but can be relegated to Corps District
– Specs: Usually in-house SOW. Not UFGS or MILCON RFP.
17
Need to educate garrisons on value of Open and how to get UMCS and System Integration
ConnectivityWeek 2010
LONWORKS UMCS (front-end)- Some possible scenarios -
1. New UMCS with no DDC system:– Design UMCS using Corps criteria
2. New UMCS with new DDC system: – Design UMCS using Corps criteria. Award 2 separate contracts.
3. New UMCS with existing proprietary DDC system:
18
3. New UMCS with existing proprietary DDC system:– Sole source procurement to DDC system supplier or use
gateways (bad options). Do this on exception basis only.
4. New UMCS with existing LonWorks DDC system(s)– Design UMCS to Corps criteria. Require integration.
5. Existing UMCS with interface to new DDC system(s)– Design UMCS to Corps criteria. Various integration options…
ConnectivityWeek 2010
UMCS System Integration Approaches
• “In-House” System Integrator (SI)– Government employee
– Contractor - through an existing or new services contract
– Contractor - through other mechanism such as ESPC
• Long Term Contract – Cost by task– Local ID/IQ (may not exist)
19
– Local ID/IQ (may not exist)
– HNC ID/IQ (popular method)
• Case-by-Case – single SOW/contract for DDC and integration
– This approach is strongly discouraged
• Case-by-Case – separate SOW/contract for DDC and integration
Note: Garrison/designer needs to define SI approach in advance.
ConnectivityWeek 2010
Doing Business with the Bureaucrats
Proposals / Bids
Be thorough w/ proposals, look at keywords
Be honest, no sales bragging
Minimize/avoid fluff about your company
20
Answer RFP points. And be succinct.
Say you “will do”, not “consider doing”
Alternate solutions must be separate and priced accordingly as an option
ConnectivityWeek 2010
Doing Business with the Bureaucrats
Be patient. Develop relationships at the installations and Army Corps Districts
Partner with another that has a contract Be a sub to the prime Be aware of funding from major programs
21
Be aware of funding from major programs– Energy Policy Act of 2005: Mandate for installation metering – American Recovery and Reinvestment Act – Energy Conservation Investment Program (ECIP) funding for
UMCS projects
Installation Management Command (IMCOM) funding for energy projects
ConnectivityWeek 2010
Doing Business with the Installations
Establish a relationship with garrison Energy Engineers/Managers and Directorate of Public Works (DPW) personnel.
Recognize, accept, and communicate the need for Open systems. Be an Open systems advocate.
22
Open systems. Be an Open systems advocate.
Assist with statements of work. Include applications and engineering.
– No (sole source) hooks or gotchas
ConnectivityWeek 2010
Doing Business with the Installations
Provide competitive proposal to local contracting or…
Take advantage of contracting vehicles
– ID/IQ (Indefinite delivery indefinite quantity)
23
– GSA (General Services Administration)
– ESPC (Energy Savings Performance Contract)
Every Installation needs a good Systems Integrator – be one. Understand your customer.
ConnectivityWeek 2010
Traits of a Good System Integrator (SI)
Formally trained on the UMCS and related tools/software Experience with LonWorks and Corps specs Experience with UFGS 25 10 10 and UFGS 23 09 23 Creates/facilitates LNS database management Checks/verifies LNS databases from DDC contractors Helps with handoff of documentation from DDC contractors Points Schedules – Critically important drawing/documentation
24
Points Schedules – Critically important drawing/documentation Understands Scheduler device/functionality and UFGS prescriptive
requirements Experience with proprietary protocols and legacy systems if these
will be integrated into the UMCS Familiarity with Garrison IT and network security requirements.
Prior experience is beneficial but few integrators have this experience.
ConnectivityWeek 2010
The Good, the Bad, and the Ugly
Good: Support from LonMark, Vendors/Manufacturers, Army Corps Headquarters, Installation management Command Headquarters, multiple army garrisons, Huntsville, Savannah District, CERL
Bad: Open is not easy. Garrisons are under funded,
25
Bad: Open is not easy. Garrisons are under funded, under staffed, under trained.
Ugly: FUD (Fear Uncertainty Doubt)
ConnectivityWeek 2010
Getting Better All the Time- The ToDo List -
1. Set a goal for a single basewide UMCS
– See: Forts Hood, Bragg, Bliss, Lee, others
2. Make a plan
– ERDC/CERL TR-08-12: “IMCOM LONWORKS®
Building Automation Systems Implementation
26
Building Automation Systems Implementation Strategy”
– Staffing (BAS manager, SI, operators, technicians, etc.)
3. Define a strategy for system integration
– Funding and contracting
– Do the two-step: 1. Get an SI 2. Integrate DDC systems
ConnectivityWeek 2010
Getting Better All the Time- The ToDo List -
4. Work with the IT folks (NEC/DOIM) early and often
– Recognize DIACAP and Networthiness
– No drive-by fielding
5. Pay attention to and enforce the specs open system requirements
27
requirements
6. Handoff documentation. Drawings, LNS database, etc.
– Points Schedule drawing is critical
7. Training
NEC: Network Enterprise Center DOIM: Directorate of Information ManagementDIACAP: Defense Information Assurance Certification and Accreditation Program
ConnectivityWeek 2010
UMCS Staffing, Growth & Maintenance
A successful BAS must be managed
– Including proper staffing, use, growth, maintenance
– Historically not well accomplished
– Army / IMCOM / USACE working on a solution
Staffing is big challenge. Roles include:
28
Staffing is big challenge. Roles include:– BAS Manager– UMCS Administrator – Technical Expert – System Integrator– UMCS Operator(s)– Controls Technician(s)
ConnectivityWeek 2010
Some Corps LON Projects
• Fort Hood, Texas• Energy Savings Performance Contract (ESPC), Have integrated
Circon, Distech and TAC buildings, w/Johnson Controls UMCS• 2007 LONMARK Multi-Vendor Project award. Other Govt. awards.
• Fort Bragg, North Carolina• Basewide System, MILCON funded (ECIP), Johnson Controls UMCS
• Fort Bliss, Texas
29
• Fort Bliss, Texas• Basewide System, O&M Funded, Johnson Controls UMCS
• Fort Sill, Oklahoma• Multi-building UMCS, MILCON Funded, TAC UMCS
• Fort Lee, VA• Energy Savings Performance Contract (ESPC), Johnson Controls
UMCS• NAVY Mechanicsburg, Pennsylvania
• Basewide UMCS, MILCON Funded, TAC UMCS
ConnectivityWeek 2010
National Defense Authorization Act for FY 2010 (NDAA 2010) Section 2841 ConnectivityWeek 2010
Useful WEB Sites
Whole Building Design Guide Websitehttp://www.wbdg.org/
(documents library, Army/COE criteria, UFGS, ECBs etc.)
Huntsville UMCS MCX site
http://www.hnd.usace.army.mil/umcs/
31
http://www.hnd.usace.army.mil/umcs/
CERL - Building automation systems and controls site
https://eko.usace.army.mil/fa/bas/
(Technical Reports, drawings, draft UFCs, etc.)
ConnectivityWeek 2010
Summary
We need open systems
Challenges are ongoing
We’ve had successes
32
We continue to make progress
ConnectivityWeek 2010
Questions?
33
ConnectivityWeek 2010