l9n/ North Dakota

2011 Regular Session, 2011–2012

Senate Bill 2296

Relating to an energy usage database for public buildings.

Did not become law. It stopped in the House of Representatives on March 24, 2011. The 62nd Legislative Assembly has ended.

What it does

The synopsis the Legislative Assembly published with the bill.

A BILL for an Act to create and enact a new section to chapter 54-44.5 of the North Dakota Century Code, relating to an energy usage database for public buildings.

Sponsors

Who carried the bill in each chamber, and who signed on. Each name leads to the member's page.

In the Senate

4 co-sponsors

Dick Dever, Mac Schneider, Scott Louser, Mark Sanford

Its course

January 21 to March 24, 2011, on one scale. In the top row each mark is a day something happened; taller marks are busier days.

Each committee stop sits inside its chamber.

Every action11 actions on 11 days

In the SenateJan 21 to Feb 919 days

Political SubdivisionsJan 21 to Feb 717 days

In the House of RepresentativesFeb 9 to Mar 24 · stopped43 days

Political SubdivisionsFeb 23 to Mar 2126 days

Votes

Yeas to nays, as the Legislative Assembly recorded them. Committee votes are set in.

  • Political Subdivisions5–0

    Do pass as amended · Feb 7

  • Senate, second reading47–0

    Passed · Feb 9

  • Political Subdivisions12–0

    Do pass as amended · Mar 21 · 2 present

  • House of Representatives, second reading39–51

    Failed · Mar 24

Amendments

Each amendment offered, and what became of it.

  • Senate committee amendmentAdopted

    Adopted Feb 8

  • House of Representatives committee amendmentAdopted

    Adopted Mar 22

Text

Each version as the Legislative Assembly printed it.

l9n doesn't hold this bill's text yet.

What happened

In l9n's words, one line for each step. Every action as the Legislative Assembly published it is below.

In the Senate Jan 21 – Feb 9

  1. Jan 21Introduced and sent to Political Subdivisions
  2. Feb 4Heard in Political Subdivisions
  3. Feb 7Political Subdivisions recommended it as amended, 5 to 0
  4. Feb 8Amended as the committee recommended
  5. Feb 9Passed the Senate, 47 to 0

In the House of Representatives Feb 10 – Mar 24

  1. Feb 10Arrived in the House of Representatives
  2. Feb 23Read a first time and sent to Political Subdivisions
  3. Mar 11Heard in Political Subdivisions
  4. Mar 21Political Subdivisions recommended it as amended, 12 to 0
  5. Mar 22Amended as the committee recommended
  6. Mar 24Failed in the House of Representatives, 39 to 51
All 11 actions, as published
  1. Jan 21Introduced, first reading, referred Political Subdivisions CommitteeSenate
  2. Feb 4Committee Hearing 09:30Senate
  3. Feb 7Reported back amended, do pass, amendment placed on calendar 5 0 0Senate
  4. Feb 8Amendment adopted, placed on calendarSenate
  5. Feb 9Second reading, passed, yeas 47 nays 0Senate
  6. Feb 10Received from SenateHouse of Representatives
  7. Feb 23Introduced, first reading, referred Political Subdivisions CommitteeHouse of Representatives
  8. Mar 11Committee Hearing 09:00House of Representatives
  9. Mar 21Reported back amended, do pass, amendment placed on calendar 12 0 2House of Representatives
  10. Mar 22Amendment adopted, placed on calendarHouse of Representatives
  11. Mar 24Second reading, failed to pass, yeas 39 nays 51House of Representatives