1. SunSpec Alliance Architecture Committee February 22, 2012

2. Architecture Committee Scope • Vet and Address Issues • Common Model specification • Cross-Model • Release process • Vet Model errors, omissions, improvements • Develop new 2.0 • Documentation Standards • Naming Standards • Test Specs / Process

3. Architecture Committee Members • Aaron Parker • Andreas Schacht • Bill Randle • Bob Fox • Brett Francis • Brian Lydic • Howard Davis • John Blair • John Nunneley • Lu Jiang • Lynn Linse • Martin Beran • Motoko Furukawa • Stephen Lapointe • Steve Lewis • Tim Shirley • YaronBinder

4. Scope Laundry List • Specification Release Process • Machine Readable Format • Naming Conventions (aka Short Names) • Networking Configuration • Scale Factor Type • Event Handling • Modbus address alignment • Device Classification • Model Updates / New • Vendor Specific Fields in Maps (Mgmt of vendor extt) • Location String in Common Block • Device Manifest Convention

5. Specification Release Process, John Nunneley • Recognize spec levels of maturity • Need for implementations • Promote stability of releases • Reduce spec churn

6. Machine Readable Format, John Blair • Long time goal of specification level • Support automation of Logger and Application support • Capture all PICS info • Description of variable (repeating) length blocks • Status and Event Codes

7. Point Naming Conventions, Bob Fox • Doubles as both the human readable name and the M2M name • Globally unique name is not a requirement and is not manageable • Overloaded with Model family prefix • Unnecessary, Cumbersome • Address bandwidth & CPU constrained deployments (cell modems) • Efficient M2M exchange • Need for consistent naming convention

8. Networking Configuration, Bill Randle • Common need for devices that support both RTU and TCP • Configuration of typical TCP/IP parameters • IP / DNS / Gateway • Netmask • IPv4 / 6 mode • SNTP

9. Scale Factor Type, John Blair • Common Scale Factor Type (sf) is not used in the PICS • Codify naming convention – XXX_SF • Important for automation and test tool

10. Event Handling, Randy Redding • Unlatched Events .vs. Latched Events • Pros & Cons • Clarify best practice and intent • Clarification of the status and event values

11. Modbus Address Alignment, Robert Hyatt • Mapping guidelines • Organization • Reuse (aggregation) • Efficient reading of Modbus registers • Common model has odd length • All blocks should be of even length • Handling of float variant • Use of _SF values

12. Device Classification, Logger WG • No formal concept of a device type • SunSpec Map is an arbitrary concatentation of a common block + N models. • Notion of a device type: Inverter, Meter, String Combiner, etc. • Model variants • Simple, Advanced • Integer, Float • Needed for data and control filtering

13. Model Erratta & New Models • String Combiner issue, Aaron Parker • Inverter issues • Connection type overloaded onto DID, John Nunneley • MPPT Inverter Model, John Blair • New Charge Controller Model Proposal • Tim Shirley, Outback

14. Next Meeting • Weekly, Wed 8am PT, GotoMeeting ID: 867-620-025 • Discuss work breakdown and priority • Form subteams to work issues • Bring back straw proposals to broader committee