text:
Find fellowships, conferences, grants and awards deadlines, workshops and networking opportunities, crowd-sourced leads to job banks, reporting toolkits, hundreds of MOOCs and more. GO >>
2020 Journalists' Guide to Energy & Environment
SEJournal looks ahead to key issues in the coming year with this "2018 Journalists' Guide to Energy & Environment" special report.
Find Out More >>
Blogs and More
This is a listing of SEJ members' websites and blogs, as well as archives of non-member sites SEJ members have recommended as useful to any journalist covering environmental issues.
Find Out More >>
Books includes our members' own volumes and their suggestions for resource books you should consult, as well as environmental fiction they've enjoyed reading.
Find Out More >>
Climate Change Guide
SEJ's guide to the information and disinformation surrounding climate change includes an intro; basic science; federal and international agencies; industry, academic, and enviro groups; an expert rolodex; regional resources; and that's not all. Find Out More >>
COVID-19 Resources for Journalists
SEJ compiles articles, resources, funding opportunities and events to aid in your reporting on the COVID-19 pandemic. Find Out More >>
Environmental Podcasts
Here you'll find informative and interesting podcasts by SEJ members and other journalists. Find Out More >>
Featured Journalists
Here, we proudly highlight the diverse endeavors of our members and other journalists.
Find Out More >>
Here are resources for the growing freelance segment of SEJ's membership.
Find Out More >>
Find journalism job links here.
Find Out More >>
A Rack Full of Magazines on Environmental Subjects — both print and online.
Find Out More >>
Media on the Move
This feature highlights changes in SEJ members' careers. Have you changed jobs? Won a fellowship? Earned a promotion? Written a book? Let us know by filling out a simple form.
Find Out More >>
Reporting Tools
A beginning list....
Find Out More >>
SEJ Canada
These resources are useful for journalists covering Canadian environmental issues, as well as for those covering trans-border issues.
Find Out More >>
SEJ Español
Links to SEJ's Spanish-language web pages and English-language Spanish resources.
Find Out More >>
Source Lists
Our Source lists page provides contact information for the U.S. Department of Interior (including HQ, Bureau of Indian Affairs, Bureau of Land Management, Bureau of Reclamation, Minerals Management Service, National Park Service, Office of Surface Mining, U.S. Fish & Wildlife Service, U.S. Geological Survey) and the U.S. Environmental Protection Agency.
Find Out More >>
Teaching Tools
Teaching tools offers resources for those who teach EJ at the university level. Includes course syllabi from around the world and a link to the SEJ-edu members-only listserv which is a forum for teachers and students to exchange information. Also for students is a listing of environmental journalism education programs.
Find Out More >>
Useful Links
Useful Links contains more than 1,500 entries representing the most useful web sites for environmental reporters.


text:
225 killed in 200 heavy vehicle crashes last year
THE number of people killed in crashes involving heavy vehicles has dropped by 20% over the past five years.
It has been revealed 225 people died in 200 crashes involving heavy vehicles on Australian roads in the 2011-12 financial year.
The figures were released by the Bureau of Infrastructure, Transport and Regional Economics on Friday.
Parliamentary Secretary for Infrastructure and Transport Catherine King said while the number of fatal crashes and fatalities had continued to fall, any loss of life was unacceptable.
"This latest report shows that over the last five years the number of crashes involving articulated trucks and rigid trucks has decreased by 13%," Ms King said.
"Also the number of fatal articulated truck crashes is down by 18%, as well as fewer fatalities from heavy bus crashes with a 4.2% decrease from the year before."
She said the establishment of the National Heavy Vehicle Regulator would help in reducing the number of death even further.

subset: commoncrawl


text:
Manually using GPRS
From Openmoko
m (→Turning your FreeRunner into a Network Address Translation (NAT) gateway)
Monkeypanic (Talk | contribs)
(→Some APN names for reference: added virgin australia)
|Line 292:
|Line 292:
! user/password if required
! user/password if required
! Working pppd scripts
! Working pppd scripts
| Australia || Vodafone || Any || vfinternet.au || ||
| Australia || Vodafone || Any || vfinternet.au || ||
Revision as of 07:48, 27 August 2008
The GPRS connection is made using the PPP protocol to a server identified by an "APN" at the network operator. Once a GPRS connection is made, it is possible to share that connection with a connected computer, allowing that computer to access the internet through the phone!
Option 1: With GSM multiplexing and with a GUI
|NOTE: The following does not appear to work if you have a SIM PIN. The dialog to enter your SIM PIN never pops up and the GSM multiplexing daemon continuous loops and runs into a SIM PIN error.
GSM multiplexing allows both a GPRS connection and a phone call to be handled at the same time. By default, Om 2008.8 does not multiplex the GSM device. The FSO distribution, however, introduces GSM multiplexing with a new service and a DBus API to that service. The instructions to modify the OM2008.8 distribution to make use of GSM multiplexing and allow you to start GPRS from a GUI can be found here: http://freeyourphone.de/portal_v1/viewtopic.php?f=21&t=295
However, using those instructions, you will encounter a few hurdles. Do not use the gsm0710muxd that is found in the OM2008.8 repository. It will not work, instead, use the one found here:
In order to install that version of gsm0710muxd, however, you will also have to install a bunch of missing dependencies. Those can be found by clicking on the dependencies found here:
Make sure that you install the armv4t versions of all packages.
The APN Reference table may come in handy when you are looking for the required network specific information.
Once you follow through with all the instructions, you will notice that the "Services" GUI will crash. This has to do with this bug: http://docs.openmoko.org/trac/ticket/1718
The fix is to change the "init()" call on line 82 of /usr/lib/python2.5/site-packages/gtk-2.0/gtk/_init_.py to "_init()" (add an underscore).
You may also have to modify your /etc/resolv.conf file and add the nameserver (DNS Server) of your service provider if you have DNS resolution problems.
Then, hopefully, you should be up in running with GPRS and a GUI to turn it on and off.
Option 2: With GSM multiplexing and without a GUI
1) In /etc/rc5.d start gsm0710muxd before gsmd:
- S34gsm0710muxd -> ../init.d/gsm0710muxd
- S35gsmd -> ../init.d/gsmd
2) Modify S35gsmd so it can start either with or without gsm0710muxd:
... case "$1" in start) if [ "$(pidof gsm0710muxd)" ] ; then id=$(date +%s) GSM_DEV=$(dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer org.freesmartphone.GSM.MUX.AllocChannel string:$id | grep string | cut -d \" -f 2) else [ -n "$GSM_POW" ] && ( echo "0" >$GSM_POW; sleep 1 ) [ -n "$GSM_POW" ] && ( echo "1" >$GSM_POW; sleep 1 ) [ -n "$GSM_RES" ] && ( echo "1" >$GSM_RES; sleep 1 ) [ -n "$GSM_RES" ] && ( echo "0" >$GSM_RES; sleep 2 ) fi if [ ! "$GSM_DEV" ] ; then echo "GSM_DEV was not set" exit 1 fi echo -n "Starting GSM daemon: " start-stop-daemon -S -x /usr/sbin/gsmd -- gsmd -p $GSM_DEV $GSMD_OPTS -d -l /var/log/gsmd if [ $? = 0 ]; then echo "gsmd." else echo "(failed.)" fi ;; stop) if [ ! "$(pidof gsm0710muxd)" ] ; then [ -n "$GSM_POW" ] && echo "0" >$GSM_POW fi echo -n "Stopping GSM daemon: " ...
3) Remove the tty from /etc/ppp/peers/simyo (replace simyo with your provider).
4) Use a ppp start script like this:
$ cat /usr/local/bin/ppp-start #!/bin/sh id=$(date +%s) TTY=$(dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer org.freesmartphone.GSM.MUX.AllocChannel string:$id | grep string | cut -d \" -f 2) logger -t ppp-start "using tty $TTY" pppd $TTY call simyo
5) Use "killall pppd" to terminate the PPP connection.
Option 3: Without GSM multiplexing and without a GUI
The program that implements PPP on Linux is pppd, which we need to configure and run to get a connection. When that is working, we can configure pppd to wait until it's needed before it connects, and to disconnect if the connection becomes idle. Further, we can start pppd in the background during the boot process.
Configuring pppd for manual connections
You'll need /etc/ppp/peers/gprs:
# Uncomment the following if you want some debug. #debug #logfile /var/volatile/log/pppd.log lock /dev/ttySAC0 115200 crtscts connect /etc/ppp/gprs-connect-chat disconnect /etc/ppp/gprs-disconnect-chat hide-password usepeerdns ipcp-accept-local noauth noipdefault novj novjccomp defaultroute replacedefaultroute # Reopen the connection if it fails, pausing for a while. persist holdoff 15 # Check the line every 20 seconds and presume # the peer is gone if no replay for 4 times. lcp-echo-interval 20 lcp-echo-failure 4
Depending on the APN, you may need password authentication using CHAP or PAP. In /etc/ppp/pap-secrets you can add the following default line for "password-less" connections:
# client server secret IP addresses * * "" *
For CHAP, lines in /etc/ppp/chap-secrets are used. For PAP, the lines are in /etc/ppp/pap-secrets. The client should match the "user" option in pppd the config file (below). You can use * to mean any here, but the option user "" doesn't mean empty!
For example:
# Secrets for authentication using CHAP # client server secret IP addresses "user" * "password" *
For this you need the following options in /etc/ppp/peers/gprs:
# username to use for authentication, should match "client" in /etc/ppp/{chap,pap}-secrets user "user"
gprs-connect-chat, version 1
You'll also need /etc/ppp/gprs-connect-chat (needs "chmod +x"):
#!/bin/sh -e exec chat -v -S -s\ TIMEOUT 15\ "" "\K\K\K\d+++ATH"\ OK-AT-OK ATZ\ OK ATE1\ ABORT BUSY\ ABORT DELAYED\ ABORT "NO ANSWER"\ ABORT "NO DIALTONE"\ ABORT VOICE\ ABORT ERROR\ ABORT RINGING\ TIMEOUT 60\ OK AT+CFUN=1\ OK AT+COPS\ OK AT+CGDCONT=1,\"IP\",\"internet\"\ OK ATD*99#\ CONNECT /n/d
(08/18/08) Note: I needed to add the command "AT+CMOD=2" (formatted as "OK AT+CMOD=2\" without the quotes) in order to get GPRS working with the above script (otherwise it would ERROR on the CFUN, COPS, or the ATD if the other two were removed). I have T-Mobile (US) with the $5.99 "tzones" addon, which works with Minimo as it supports HTTP proxy setups.
gprs-connect-chat, version 2
Update: On my freerunner the first AT+CFUN=1 always generated ERROR. I managed to get gprs work by using the following script from http://lists.openmoko.org/pipermail/community/2008-July/023246.html:
#!/bin/sh -e exec /usr/sbin/chat -v \ TIMEOUT 10 \ OK-AT-'' ''\ ABORT BUSY\ ABORT DELAYED\ ABORT "NO ANSWER"\ ABORT "NO DIALTONE"\ ABORT VOICE\ ABORT ERROR\ ABORT RINGING\ TIMEOUT 30 \ '' ATZ\ OK ATE1\ OK AT+CFUN=1\ ERROR AT+CPIN=\"XXXX\"\ << USE YOUR OWN OK AT+COPS\ OK AT+CGDCONT=1,\"IP\",\"internet\"\ OK 'ATDT*99***1#'\ CONNECT ''
The error seems to vary a bit, sometimes it's before AT+COPS, sometimes as above. I have two versions of the gprs-connect-chat, which I vary between depending on which is needed. Or is there a way to specify two acceptable answers like {OK,ERROR}?
You will need to adjust the APN name "internet" in at+cgdcont line and possibly the phone number in the ATD line to match what your network operator provides. See below in the table "Some APN names for reference" for the right settings for your operator.
Also good to have is /etc/ppp/gprs-disconnect-chat (needs "chmod +x"):
#!/bin/sh -e /usr/sbin/chat -v\ ABORT OK\ ABORT BUSY\ ABORT DELAYED\ ABORT "NO ANSWER"\ ABORT "NO CARRIER"\ ABORT "NO DIALTONE"\ ABORT VOICE\ ABORT ERROR\ ABORT RINGING\ TIMEOUT 12\ "" "\K\K\K\d+++ATH"\ "NO CARRIER-AT-OK" "\c"
Starting PPP connection
The following script can be used to start the ppp connection. First it stops gsmd because gsmd may put the phone in a unknown state. It then turns on the power to the phone, modifies the ownership, and then creates a tty connection. Finally it starts pppd with the gprs settings.
/etc/init.d/gsmd stop echo "1" > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on chown uucp.uucp /dev/ttySAC0 stty -F /dev/ttySAC0 crtscts pppd call gprs
If you are having problems connecting ensure you have a good GSM signal and replace the last line with the below line. This will allow you to see the details of the connection on the console.
pppd debug nodetach call gprs
The config above will establish a persistant link over gprs. The battery will run low in less than an hour. See an example for an on-demand config below.
Resolve.conf issues
The latest build seems to have solved the following issue, it should be automatically updated by pppd.
If you expeience DNS issues after connecting to DNS you may need a proper /etc/resolv.conf:
ln -sf /var/run/resolv.conf /etc
If needed put your nameserver for usb-net into /var/run/resolv.conf, not in /etc.
The image does not set a correct resolv.conf. i do so with an
echo nameserver 192.168.0.201 > /var/run/resolv.conf
in the right place. because a post-up in /etc/network/interfaces is not supported i do that in /etc/network/if-up.d/08setupdns
another problem is pppd's /etc/ppp/ip-down.d/92removedns which does not properly remove the link when shuting down ppp. my fix is this script:
#!/bin/sh ACTUALCONF=/var/run/resolv.conf PPPCONF=/var/run/ppp/resolv.conf if [ -f $PPPCONF ] ; then if [ -f $ACTUALCONF ] ; then if [ ! -h $ACTUALCONF -o ! "`readlink $ACTUALCONF 2>&1`" = "$PPPCONF" ] ; then mv $ACTUALCONF $ACTUALCONF.ppporig fi fi ln -sf $PPPCONF $ACTUALCONF fi
Some APN names for reference
|user/password if required
|Working pppd scripts
|Any, behind NAT
| mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
org.freesmartphone.GSM.PDP.ActivateContext internet.fido.ca fido fido
|Any, behind NAT
|nameserver 126.96.36.199
|must be empty
|Any, behind NAT
|Any, behind NAT
|Any, behind NAT
|Any, public IP
|under tests
|under tests
|under tests
|Bouyges Telecom
|Web & Mail
|Work great under FSO. Just follow instructions at http://wiki.openmoko.org/wiki/GPRS_FSO. Proxy: 220.127.116.11:8080. For emails, only ports 25 (smtp) and 110 (pop) are allowed. (They use a transparent proxy ...)
|BASE (and others?)
|eplus gprs
|Base pppd scripts
|simyo simyo
|simyo pppd scripts
|Any, behind NAT
|Superinternet, public IP
|internet.wind / *99#
|wind/wind (any string)
|Wind pppd scripts
|live.vodafone.com / *99***1#
|Vodafone pppd scripts
|New Zealand
|live.vodafone.com / *99***2#
|Works with FSO
|e.g. Natel Basic Liberty, behind NAT
|other providers
|Unlimited data plan (attached to pay-as-you-go voice plan)
|wap.cingular / *99***1#
|Cincinnati Bell Wireless
|Cingular (AT&T)
|Less than full internet
|wap.cingular / may require *99***1#
|Anything less than full internet
|Need to set proxy to 126.96.36.199 T-Mobile docs say "216.155.165.050". 050 octal = 40 decimal and will *not* work. I think port is 8080 or 9100. No luck w/ pppd scripts. GPRS_FSO directions work under FSO though.
|Regular internet plan
|T-Mobile pppd scripts
|"VPN" internet plan
|Pre- y post-pago
[1] connected through a WAP proxy (slower, but the only way to access Vodafone live! and SFR portal)
[2] Unless stated otherwise the phone number to call is "*99#"
Also see Ross Barkman's page for a detailed list of more global GPRS providers APN details
Starting pppd automatically
Once you have finished debugging your gprs-connect-chat and gprs options files, you may wish to automatically connect whenever needed and hang up when finished. Make sure you understand the impact of this change to your carrier plan billing. This is not recommended unless you have a large-use or unlimited data plan. These scripts do NOT prompt you before connecting.
On-demand connection settings
Additional settings are needed if you want the actual connection to be up only while there is traffic. In the 'gprs' file above, insert the following, making sure 'nodetach' is commented out. If 'nodetach' is on, the boot process will stop when it starts pppd. Also remove the option 'persist' mentioned above.
# Wait until needed before connecting demand # Disconnect if idle for given amount of seconds idle 20
Start on boot (method 1)
Add the following definition to /etc/network/interfaces:
auto ppp0 iface ppp0 inet ppp provider gprs
That should be it. Now you can use 'ifup ppp0' and 'ifdown ppp0' manually too.
Start on boot (method 2)
Create the following file as /etc/ppp/ppp_on_boot (needs chmod +x). The /etc/init.d/ppp script will call it to set up the daemon.
#!/bin/sh # # Rename this file to ppp_on_boot and pppd will be fired up as # soon as the system comes up, connecting to `provider'. # # If you also make this file executable, and replace the first line # with just "#!/bin/sh", the commands below will be executed instead. # # The location of the ppp daemon itself (shouldn't need to be changed) PPPD=/usr/sbin/pppd # The default provider to connect to $PPPD call gprs # Additional connections, which would just use settings from # /etc/ppp/options.<tty> #$PPPD ttyS0 #$PPPD ttyS1 #$PPPD ttyS2 #$PPPD ttyS3
Finally, you need to add the /etc/init.d/ppp script to the init process by creating symbolic links from the appropriate directories. I chose the following:
/etc/rc0.d/K25ppp /etc/rc1.d/K45ppp /etc/rc2.d/S45ppp /etc/rc3.d/S45ppp /etc/rc4.d/S45ppp /etc/rc5.d/S45ppp /etc/rc6.d/K25ppp
Sharing the GPRS connection with a computer
Once you successfully connect to your network operator, you can start sharing your data plan with your computer through USB or Bluetooth networking. The following describes how you can do so through USB networking.
Setting up your computer's network settings
I find it useful to have my computer automatically acquire it's network address, mask, gateway, and DNS servers from the FreeRunner instead of manually setting these up. In order to this, I installed busybox-udhcpd from the Angstrom repositories (see Repositories)
opkg install busybox-udhcpd
Once it is installed, it needs to be configured. Edit the /etc/udhcpd.conf file. Mine looks like this:
# Sample udhcpd configuration file (/etc/udhcpd.conf) # The start and end of the IP lease block start 192.168.0.200 #default: 192.168.0.20 end 192.168.0.200 #default: 192.168.0.254 # The interface that udhcpd will use interface usb0 #default: eth0 # The maximim number of leases (includes addressesd reserved # by OFFER's, DECLINE's, and ARP conficts #max_leases 254 #default: 254 # If remaining is true (default), udhcpd will store the time # remaining for each lease in the udhcpd leases file. This is # for embedded systems that cannot keep time between reboots. # If you set remaining to no, the absolute time that the lease # expires at will be stored in the dhcpd.leases file. #remaining yes #default: yes # The time period at which udhcpd will write out a dhcpd.leases # file. If this is 0, udhcpd will never automatically write a # lease file. (specified in seconds) #auto_time 7200 #default: 7200 (2 hours) # The amount of time that an IP will be reserved (leased) for if a # DHCP decline message is received (seconds). #decline_time 3600 #default: 3600 (1 hour) # The amount of time that an IP will be reserved (leased) for if an # ARP conflct occurs. (seconds #conflict_time 3600 #default: 3600 (1 hour) # How long an offered address is reserved (leased) in seconds #offer_time 60 #default: 60 (1 minute) # If a lease to be given is below this value, the full lease time is # instead used (seconds). #min_lease 60 #defult: 60 # The location of the leases file #lease_file /var/lib/misc/udhcpd.leases #defualt: /var/lib/misc/udhcpd. leases # The location of the pid file #pidfile /var/run/udhcpd.pid #default: /var/run/udhcpd.pid # Everytime udhcpd writes a leases file, the below script will be called. # Useful for writing the lease file to flash every few hours. #notify_file #default: (no script) #notify_file dumpleases # <--- usefull for debugging # The following are bootp specific options, setable by udhcpd. #siaddr 192.168.0.22 #default: 0.0.0.0 #sname zorak #default: (none) #boot_file /var/nfs_root #default: (none) # The remainer of options are DHCP options and can be specifed with the # keyword 'opt' or 'option'. If an option can take multiple items, such # as the dns option, they can be listed on the same line, or multiple # lines. The only option with a default is 'lease'. #Examles opt dns 192.168.0.202 <your APN's DNS server> option subnet 255.255.255.0 opt router 192.168.0.202 opt wins 192.168.0.202 #option dns 188.8.131.52 # appened to above DNS servers for a total of 3 option domain local option lease 864000 # 10 days of seconds # Currently supported options, for more info, see options.c #subnet #timezone #router #timesvr #namesvr #dns #logsvr #cookiesvr #lprsvr #bootsize #domain #swapsvr #rootpath #ipttl #mtu #broadcast #wins #lease #ntpsrv #tftp #bootfile
Notice that I set the start and end of the IP lease block to 192.168.0.200. If you follow the instructions at USB Networking, this is the address that it assumes the host to be and the /etc/resolv.conf file points to this address to allow name resolution from your phone.
The interface in this case is usb0. This will have to be set differently if you are using Bluetooth.
The dns is set to the FreeRunner's address, as well as my network operator's DNS server address. You don't have to use your network operator's DNS address if you can find a caching nameserver for the FreeRunner.
The router is set to the FreeRunner.
Turning your FreeRunner into a Network Address Translation (NAT) gateway
I set up my FreeRunner so that it acts as a NAT gateway so that all traffic that goes to my network operator appears to originate from the phone. I installed iptables to accomplish this:
opkg install iptables iptables-utils kernel-module-ipt-masquerade kernel-module-iptable-nat
Once that is installed, I have the following script named firewall.sh that I use to set up the NAT once connected to the GPRS network:
#!/bin/sh IPTABLES='/usr/sbin/iptables' # Set interface values EXTIF='ppp0' INTIF='usb0' # enable ip forwarding in the kernel /bin/echo 1 > /proc/sys/net/ipv4/ip_forward # flush rules and delete chains $IPTABLES -F $IPTABLES -X #Enable masquerading to allow LAN internet access $IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE #Forward LAN traffic from LAN $INTIF to Internet $EXTIF $IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT #Allowing access to the SSH server" #$IPTABLES -A INPUT --protocol tcp --dport 22 -j ACCEPT #Allowing access to the HTTP server" #$IPTABLES -A INPUT --protocol tcp --dport 80 -j ACCEPT # block out all other Internet access on $EXTIF $IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP $IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP
so once connected through GPRS, I run:
and then you should be able to connect to the internet from your computer!
Of course this also works when sharing your WLAN connection. Just set EXTIF to eth0.
See also
English • العربية • Български • Česky • Dansk • Deutsch • Esperanto • Eesti • Español • فارسی • Suomi • Français • עברית • Magyar • Italiano • 한국어 • Nederlands • Norsk (bokmål) • Polski • Português • Română • Русский • Svenska • Slovenčina • Українська • 中文(中国大陆) • 中文(台灣) • Euskara • Català


text:
Low Platform Trailer
Tire Tubes for Low Platform Trailer Tires
Trailer tire tubes CAN be used for rim leaks, but SHOULD NEVER be used to repair a puncture. This includes sidewall tears or cracking, vandalism punctures, and even punctures in the tread. The RMA or Rubber Manufacturers Association, is very clear on their recommendations for tire repair.
Click here to visit the website for more information on tire repairs.
If you have any questions, please call us to make sure that you are using a trailer tire tube properly and safely
In general, most trailer tires are tubeless. Because of the abuse these tires take, rims can get banged up causing rim leaks and air pressure loss. If the tires are punctured or sidewalls are cracked, you should consider replacing the tire.
Low profile trailer tires come in fewer sizes so you can not just use your average tube. The rim is bigger and these tubes will only fit a few tire sizes and have a special valve. These trailers are made for heavy cargo and require a good quality, heavy duty tire tube.
Tire tubes can fit many different tire sizes, so if you don't see your tire size listed, just give us a call and we will find the right tube for your trailer tire and application.
More Tips on Choosing Trailer Tire Tubes
HELPFUL REMINDER ABOUT TIRE TUBES: Tire tube manufacturers are moving toward only producing RADIAL TIRE TUBES due to the fact that they can be used in both radial and bias tires. Still, some tire tubes are made in both radial and bias construction. Just remember RADIAL TIRE TUBES can be installed in both RADIAL TIRES AND BIAS TIRES, but BIAS TIRE TUBES can only be installed in BIAS TIRES. So, if your tire is of bias construction but a bias tube is not available, don't hesitate substituting a radial tube. NOTE: A Radial tube is designated with an "R" in the size (ex. 18.4R30).
7/8/9R14.5 Firestone Radial LPT Trailer Tire Tubes TR15CW
Part Number: 551988$18.96 Out Of Stock
7/8/9x14.5 Carlisle LPT Trailer Tire Tubes TR300
Part Number: 322290$27.87 Out Of Stock
825R15 Carlisle Radial LPT Trailer Tire Tubes TR444
Part Number: 322240$23.30 Out Of Stock
700/750R15 Carlisle Radial LPT Trailer Tire Tubes TR440
Part Number: 322450$19.81 Out Of Stock
900/1000/1100R15 Carlisle Radial LPT Trailer Tire Tubes TR444
Part Number: 322250$32.59 Out Of Stock
5 Item(s)
Grid List


text:
To join the discussion about Rock Bottom Blessings, or to order a copy, go here.
Rock Bottom Blessings is Karen Beattie's autobiographical description of finding the hidden blessings in the losses that everyone faces in life.
The rock bottom for Mrs Beattie was losing her job and her dream of adopting an Ethiopian baby.
Mrs Beattie married at the age of 40. She and her husband were both in the grip of delayed dreams they wanted to fulfill while life still gave them enough time to do it. They heard their life-clocks, ticking away the time they had to do these things.
For her husband, the delayed dream was a career change from journalism to counseling. Since his new wife had a well-paying job, they couple decided he should pursue this dream. He was accepted into a good school and received a scholarship to pursue his studies.
At the same time, the couple began trying to fulfill Mrs Beattie's delayed dream of having a baby. After infertility treatment and two miscarriages, she accepted that she would not be able to have a baby herself, and immediately turned to international adoption.
The couple ran head-on into the spider's web of government regulations and expense which has grown up around these adoptions, but moved ahead with the process, anyway. Then Mrs Beattie lost her job, and the financial wherewithal to adopt along with it.
Ultimately, they were faced with a decision as a couple as to whose dream they would go for: The husband's dream of changing careers, or Mrs Beattie's dream of international adoption. They chose to go for the career change.
I won't spoil the book by telling you what happens next. What I will do is say that the needs of children are being lost in these adoption regulations.
While we debate what are essentially red herring issues such as whether or not homosexual couples should be allowed to adopt, we ignore the overwhelming adoption issue, which is the red tape and expense we have hung on this process. This spider's web of regulations often make it impossible to place children in loving homes.
The truth is, children languish in situations which are destructive to them as human beings while their potential parents grieve because they can't adopt.
Private adoptions have become fraught with the peril of emotional devastation for adoptive parents. So much so, that many people simply won't try it anymore. I personally know a couple who arranged a private adoption, only to have the birth mother change her mind later and take the baby away from them.
This is hell for the adoptive parents, and hell for the baby.
I do not want to see young women coerced into giving their babies up for adoption. But neither the birth mother nor the birth father should be able to change their mind after the baby goes to the adoptive home. I also think that we need firm limits on how long parents who have had their children taken from them for drug addiction or mistreatment of the children will have to demonstrate changes in their lives. If the parents do not care to change, these children should be placed for permanent adoption so they can have a chance at life.
This is a difficult issue for the simple reason that social workers are sometimes ham-handed in removing children from homes. I know of instances where this was done for trivial or even bogus reasons. Other times, they leave children in abusive situations so long that the children end up getting killed.
There is one thread running through all of this: The needs of the children come last in our system.
We have developed a "rights based" system of government in which children are not given the power of "rights" of their own to defend themselves.
Mrs Beattie's book is a small window on this world of adoption. That is not the book's primary focus. The main storyline of the book is Karen Beattie's attempt to grapple with the disappointments of her life through her Christian faith.
Don't be bitter. She admonishes herself at one point, which is good advice for all of us. She struggles to understand how God can love her and still deny her the gift of children.
All in all, the book is an interesting read. The narrative moves well and keeps you interested as you wait to see if this good woman will be able to realize her dream of adopting a child.


text:
Photo by Chris Schwegler AtlasIcons
Neon Trees, the modern pop band that is musically and sartorially indebted to new wave, might rely heavily on synthesizers to achieve its dance-approved approach. But on its latest album, Pop Psychology (Island Records), the very first sounds—the transient rasp of an instrument cable, followed by the ringing open D and G strings—give a hint of both the importance and the subtlety of the guitar on the record.
Throughout the album, Chris Allen doesn't play standard-issue rock guitar but something more thoughtful. His collection of riffs and timbres, plus the occasional oddball atonal move, feel spontaneous and orchestrated, and pair nicely with that of his bandmate Branden Campbell, who's style is equally informed by such great session bassists as Donald "Duck" Dunn and by Campbell's contemporary counterparts like John Stirratt of Wilco.
The roots of Neon Trees—whose name was inspired by the signage of In-N-Out Burger, the fast-food joint headquartered in Southern California—go back to Allen's childhood days. He and Tyler Glenn, the group's singer and keyboardist, were neighbors in Murrieta, California. When Allen took off to college in Utah, Glenn followed him, and there they eventually teamed up with bassist Campbell and drummer Elaine Bradley, independently releasing a debut EP, Becoming Different People, in 2006.
Before Neon Trees, Campbell was involved with, among many other bands, a ska group with the drummer Ronnie Vannucci, Jr., who would go on to join The Killers. After witnessing an early live show of Neon Trees, Vannucci was suitably impressed by his former bandmate's new outfit, and as a result Neon Trees got its big break in opening for The Killers on its 2008 tour. This led to the Trees scoring a record deal with Mercury Records, which released Habits (2010) and Picture Show (2012), respectively spawning the hit singles "Animal" and "Everybody Talks."
As was revealed a few years ago in our PG Rig Rundown, Allen and Campbell might be described as major gear heads, aficionados of equipment both new and vintage, so we were excited to check in with them on their most recent rigs and hear about the thought processes behind Pop Psychology.
Tell us about your gear.
Chris Allen: My main guitar is an Eric Johnson Strat, and then I have a Telemaster that I had a Master Builder at Fender—Jason Smith, I used to play with him in high school—make for me. It's got a Jazzmaster body and neck pickup but a Telecaster bridge and bridge pickup and selector switch. The neck profile is the same as on the Eric Johnson model guitar, and it has this 12-string-like headstock. I also had him build me a guitar based on a '48 Esquire prototype with one TV Jones pickup and the whole thing painted a uniform color, Ford Grabber blue, so that it looks like a big hunk of plastic. Then I have a Jazzmaster and a bunch of guitars I only use in the studio. And I really like old Silvertones, which have such unique voices. I'm always picking them up on eBay or when we're out on tour, at local shops. My favorite is the black-and-white hollowbody Silvertone, the 1446 that everybody calls the Chris Isaak model.
Live I use a Laney Lionheart, the L20H with a matching 2x12 cab, as well as a Roland JC-120. I also use those amps in the studio, plus a Divided by 13 JJN 50/100, a Silvertone Twin Twelve, and a Fender Hot Rod Deluxe. The main pedal on my board is an Ibanez Tube Screamer, a handwired TS808. I held off on that one for the longest time because of the price tag, but then I realized that I had no problem spending $350 on a delay pedal, so why not spend that much on overdrive, being as it's such a big part of my sound? I also use a Keeley 4-knob compressor and a Boss RV-3 Digital Reverb/Delay. The RV-3 has been discontinued, so I went searching on eBay and got a few of them, since they'll probably only get harder to find in the future. In the studio I like to use a JangleBox and the Eventide TimeFactor, but with so many knobs on the TimeFactor, it can be a bit intimidating to use live.
Branden Campbell: My main bass is made by Mike Lull, who teamed up with [Pearl Jam's] Jeff Ament to make a signature model oversize bass with a neck and body that are 20 percent larger than standard. Mine has a custom satin finish, in Kerry green. I've got a Fano hollowbody bass that I love, as well as Fender Pino Palladino and Adam Clayton signature basses. Then there's the 1975 Gibson Ripper and the Rickenbacker 4003, both which I tune down to D, and a 1966 Guild Starfire. Bass players don't usually switch up that much, but, travelling between different climates, and using different tunings, I need at least a few basses on the road. Some basses lend themselves more to D standard [low to high: D–G–C–F], and nothing seems to respond quite as well to the lower tension as the Ripper.
For amps I use an Aguilar DB 751, and I've also got an Aguilar Tone Hammer preamp pedal. That's my holy grail—I take it everywhere I go. We once had a gig in the Philippines where I had no choice but to play through a questionable old amp that had gotten all rusty due to the climate there. Even though that wasn't optimal, I knew that with the Hammer in the front end, everything would be fine and the 10,000 people waiting to hear us would not be disappointed.
Most of my D-standard songs use a chorus pedal, the EBS UniChorus, which is my nod to Peter Hook from New Order and Joy Division. The EBS Billy Sheehan Drive pedal with a built-in compressor is really solid, too. I'm a sucker for drive and also use the SolidGoldFX Beta bass overdrive, the Z.Vex Wooly Mammoth, and the Electro-Harmonix Bass Big Muff Pi. I'm really stoked on the new DigiTech Bass Whammy pedal, and have been using the Electro-Harmonix Micro Synth. I also added the Moog Sub Phatty analog synthesizer keyboard. Running that thing through the bass Big Muff is just insane!
YouTube It
Neon Trees performs its first hit, "Animal," live in a stripped-down setting.


text:
August 10, 2018 by Wrong Hands
Posted in Cartoon | Tagged Comics, Editing, Fonts, Funny, Grammar, Humor, Language, Punctuation, Typography, Writing | 8 Comments
A new take on the "San Serriffe" hoax. 😀 Cool!
LikeLiked by 1 person
This is a place in Xanth. Or at least, it should be. Ever read the Xanth books?
No I haven't…but maybe I will now.
You'd love it. It's all puns.
Sounds great!
it took me a minute… good one!!
Very good. I like the highly original ideas you come up with. You've clearly mastered connecting disparate elements and eliciting droll laughter. Bravo.
Comments RSS
Fill in your details below or click an icon to log in:
You are commenting using your WordPress.com account.
( Log Out /
Change )
You are commenting using your Google account.
( Log Out /
Change )
You are commenting using your Twitter account.
( Log Out /
Change )
You are commenting using your Facebook account.
( Log Out /
Change )
Connecting to %s
Notify me of new comments via email.
Notify me of new posts via email.
Enter your email address to follow this blog and receive notifications of new posts by email.
Join 19,700 other followers
Email Address:
Like Wrong Hands on Facebook
Blog at WordPress.com.


text:
401 Martin Luther King Jr Blvd
Raleigh, NC 27601
If you live in Raleigh, you automatically are a member of a Citizens Advisory Council. The City of Raleigh has 19 CACs, each representing a different geographic region of the city.
Each CAC elects its own officers and decides its own activities and priorities. All CAC meetings are open to everyone; however, you can vote only at meetings of the CAC where you reside. You can attend as an individual or you can represent your neighborhood-based organization at your CAC meetings.
CACs are nonpartisan. CACs are the only advisory boards to the City Council that are not appointed by the Council.


text:
The Speakers' Corner was an open space in the Forum for any participant or group of participants that wanted to promote their water-related activities, share new and innovative techniques, or just give their opinion on any given subject. For the details please read the Information note on Speakers's Corner.A quarter of the space was booked up in advance through a form on the VMS, and the rest was available for participants to sign up during the Forum week. In total, 27 presentations from 16 countries were made during the week under the aegis of the Speakers' Corner, over the two venues, ranging from Mexican school kids presenting on aquaculture and aquaponics to studies on the genetic improvement of drought tolerance in fruit crops from Egypt. This component provided a lively and more relaxed means of information sharing and exchange of ideas between participants. Please see more details on the events.
Forum VenueRegistrationGroup RegistrationAccommodationTransportationTourist Information


text:
Anyone who knows me knows how I like to race: in a sports bra and briefs. Briefs are those things that some women runners wear that look like bikini bottoms. I like to call them spankies! But you might also know them as "buns" or "bun huggers." Whatever you call them, they're what I like to race in.
Of course, this choice of apparel is not without controversy both in and out of the running universe. Today I want to tell you why I (and perhaps you might) like to wear them and give you some things to consider if you do.
Let's do this Q & A style.
Q: Rocket, why do you run in your underwear? Are you trying to be sexy?
I am often asked why I run "naked." My choice of briefs is really NOT meant to be a fashion statement. I don't wear them to be sexy. I mean, seriously! Being sexy is the last thing on my mind when I toe the line! Even so, I've overheard the comments. Things like, "Did you see that girl in a bikini, what the hell?" When my picture was on the front cover of the news paper after I won the Akron Marathon there was some backlash. Here's a sample comment about the photo:
When I looked at the front page of the paper this morning I thought my neighbors Playboy magazine had been delivered to my house by mistake. In a few years, they'll be running with g-strings and nipple pads. There is obviously no longer such a thing as modesty or propriety in our sex-crazed American culture.
Alrighty then. The answer is that no, I will not be moving to g-strings or nipple "pads" (does he mean pasties?) The reason I and many other women runners wear them to race in is because they are comfortable and feel fast! There is just something about the feeling of peeling off your bulky warm ups and being in a sleek uniform that finally says I am ready to go!
Q. Do you have to be fast to wear them? I mean, you don't usually see buns in the back of the pack, if you know what I mean.
Most people assume to be in them means you have to be fast. Well, more times than not the ladies choosing to adorn the smallest buns and singlets possible have some pretty fast legs and are usually in the top 5 percent of the race. Should this be a steadfast rule? No! If you think spankies are the most comfortable option go for it!
But word to the weak of heart – if you don't like being poked fun of, you won't make it out there. I don't care if you are fast, I have heard some pretty snide remarks about my race attire beyond that I look like I want to be in Playboy (*snicker*). When you let a lot hang out, people can say mean things about it. I just roll with it, because to me their comfort and the fact that I feel fast in them makes it worth hearing the occasional snide remark.
Q. Ok, then you need to be super thin to wear them, right?
Well, no! Wear them if they make YOU happy. But remember, they show it all! Every bump, every ounce of whatever you are. So for people who don't like the idea of others seeing that, I would recommend longer shorts. If it makes you feel self conscious, choose something more modest. Spankies are not for everyone, but there are certainly no restrictions on the size or shape of who can pull them off. Like most things, it's all in the attitude and with what makes you comfortable.
Q. Say, I'm interested in trying out some bun huggers. What should I look for when shopping for a pair?
When looking for and choosing a good pair of spankies, there are a few things to take into account. They all boil down to making sure they fit!
Fit rule #1: no wedgies! If they are too big, it will be wedgie city!! Since underwear are not typically worn under them, you know what that means… you will be mooning people all over an entire city! Nice decent people who don't deserve it will see your butt!
Fit rule #2: no camel toe! If the waistband is too loose and they ride up, there's your camel toe, end of story. Do not let this happen to you! No one wants to see that, and you won't be buying the pictures of your newly-minted PR if this happens.
Fit rule #3: no muffin top! Make sure they are not too small. If they are too small, they will give you a super cute muffin top, and make your toned, fit legs look like they are part of a string of sausages. So for a good fit, you want no extra material on your thighs and the leg holes to be just snug enough that they won't move around.
Fit rule #4: no see-through! Finally make sure they are a color that is not see-through. Sometimes terrible things happen during races and you want to make sure that it isn't the only thing people remember about your race! Also, what happens when white gets wet? Exactly! One other color to stay away from is heather gray. About two seconds into the race when sweating starts, it looks like you have decided to forgo the the port-o-let, front and back! On race day, we want to feel sleek, poised and ready to go. Maybe try black for your first try with briefs; it's definitely the safest color choice.
Q. What kind of top goes with them?
To finish off this race day look, I recommend a colorful and fun sports bra! Something that makes you smile when you see those race photos. Another good option is a long bra or fitted singlet. It looks weird to have a loose singlet tucked in or flopping around, making you look like you don't have any pants on. So stay away from loose and floppy on the top when choosing what to wear with your spankies!
Have you ever raced in bun huggers? Do you love your spankies? Buns scare you? Tell us how you feel about the littlest running bottoms!


text:
Microsoft Office is too dangerous to leave with users
Paul DeGroot from Directions on Microsoft was recently quoted by CNet saying a very scary thing about MS-Office: "The chances you are going to switch out are pretty well nil. You have way too much money invested."
It may not be politically correct to say so, but the leopard cannot change his spots, nor the Ethiopian his skin. Paul's comment came after a conference at which Microsoft claimed one million developers were basing applications on MS-Office 2003, and a quick glance at Microsoft's historical spots makes it obvious that this is just another lock-in-and-squeeze cycle. MS-Office has traditionally come down in price until competition effectively ended, and then increased again. At the end of the last such cycle the price more than doubled.
The OpenOffice suite is within hailing distance on a feature by feature basis (in some ways, ironically, it excels), and there's no way for Microsoft to undercut the price, so they must compete in other ways.
One of the major roadblocks to competition on the desktop is the need to run a specific application or two all of which require MS-Windows. The WINE project is eroding that barrier, but running the entire interlocked behemoth represented by MS-Office and all of the dependencies needed to support its integration is still no mean feat.
Perhaps more tellingly, there's not much point in "escaping" a monopoly on the desktop if a Line-Of-Business application still depends upon MS-Office.
MS-Office Pro is currently AUD$570 retail; how much would you be prepared to pay for it if your business became dependent on having it? $1000 per desktop? $5000? $50,000? However much that is, it's the price point that Microsoft will be chasing as soon as they can reasonably expect to get it.
Short-term, they will almost certainly discount MS-Office a little in order to discourage defections, but if enough customers are locked into using it the price will go up again, probably to the $1000-1500 a seat mark. And by "extending" file formats and the like, they will force you to update it regularly.
Eventually, development of OpenOffice or some other suite may follow MS-Office into the darker corners of your computer and provide enough application-level compatibility for you to migrate off again, but given Microsoft's dexterity at milking patents, it's a poor plan to bet your business on.
Meanwhile, if you let your users continue to use MS-Office on their desktops, some of them will be finding and using the encouragements Microsoft is building in, and will gradually enslave your business to MS-Office by stealth. An Excel macro here, a dynamic object embedded in Word there, sooner or later it all adds up to "we can't change" and you're no longer in control of your own IT. You're forced to "spend good money after bad".
How can you protect yourself? By carefully planning for and rolling out an alternative office suite now.
Just as eliminating MSN Messenger and replacing MS-Outlook with Thunderbird (or presently Evolution) improves your corporate security, so does replacing MS-Office with OpenOffice.org or another office suite.
Careful planning will avoid rubbing your users up the wrong way. Any change produces resistance, and by minimising the changes (converting beloved templates, making conditions under the new suite better, sending copies home especially with people who only have MS-Works or MS-Word there etc) you can maximise acceptance.
Make OpenOffice the default or only office suite on new installs. Use it yourself, for everything; train your technical people up on it so they become used to using and installing it by default and your other users will see the "elites" using it.
Since OpenOffice is now available to more than 10% of all desktops and the file format is about to become a European standard, it is now more socially reasonable to send office documents in the OASIS format adopted by OpenOffice.
If you know the recipient is able to read OASIS documents, make a point of sending them that way - and if you don't know, ask. And ask again every six months or so. "For security and portability reasons, we use the OASIS open standard for documents as implemented by the OpenOffice suite throughout our enterprise. Are you able to read OASIS documents yet?" And include a CD, it costs less than a buck.
In fact, if you ever snail-mail documents on CD or DVD - even if they're in MS-Office format - add them to an OpenOffice CD and send that rather than just sending them a frisbee with only the inner five millimeters used. It's a powerful answer to "I can't read this" and some recipients will be floored at being given powerful software for free. It's good PR.
Up front, this looks like needless bother, but the alternative is having recipients balk when they can't read your documents as produced by the latest version of MS-Office when you update. Every time you update. Which you're essentially required to do when your peers do, otherwise you can't read their documents.
Secure your future now by dodging this bullet. Start the migration to a safer office suite today.
This topic does not have any threads posted yet!
You cannot post until you login.


text:
Listen free for 30 days
Fra Angelico
- San Marco, Florence
- Narrated by: M. Jane McIntosh
- Length: 2 hrs and 16 mins
- Categories: Arts & Entertainment, Art
Now you can tour this widely loved site, guided by the scholarship of a highly regarded art historian. This Jane's Smart Art Audio Guide is the exclusive audio adaptation of a popular book in The Great Fresco Cycles of the Renaissance series, written by William Hood, professor of art history at Oberlin College and a renowned Fra Angelico scholar.
Jane's engaging narration reveals the true meaning of Fra Angelico's art in the context of the culture and monastic traditions of the times, and explains the central role these ground-breaking paintings played in the daily lives of the humble friars who lived here. Some famous feet have walked these halls: one of Michelangelo's brothers was an Observant Dominican living here, Cosimo dei Medici had a suite of cells here, and the fire-and-brimstone preacher Savonarola was prior at San Marco in the late 15th century.
This in-depth guide is indispensable for art-lovers and history-buffs. It's the smart way to experience Fra Angelico's frescoes at San Marco! With Jane as your audio tour guide, you can put away your guidebook, become absorbed in the story of San Marco, and experience a deep and lasting appreciation of the essence of this remarkable place.
The 45-minute "Slice of History" background segment is meant for advance listening. It provides the context that will enhance your appreciation of what you'll see once you arrive at San Marco. The on-site tour starts in the lovely, restful cloister and the adjacent Chapter Room, and then proceeds upstairs to the dormitory. The on-site tour takes from 75 minutes to 95 minutes.
A printable eight-panel PDF file includes floor plans keyed to the audio track list, to keep you oriented, and a glossary to clarify unfamiliar terms.


text:
Integrated Science Solutions, Inc.
B-406987,B-406987.2: Oct 10, 2012
Additional Materials:
- Full Report:
(202) 512-8278
Kenneth E. Patton
(202) 512-8205
Office of Public Affairs
(202) 512-4800
Integrated Science Solutions, Inc. (ISSi), of Walnut Creek, California, protests the proposed award of a contract to Earth Resources Technology (ERT), of Laurel, Maryland, under request for proposals No. NNA09263816R, issued by the National Aeronautics and Space Administration (NASA) for safety, environmental, and medical support services.
We deny the protest.
The decision issued on the date below was subject to a GAO Protective Order. This redacted version has been approved for public release.
Matter of: Integrated Science Solutions, Inc.
File: B-406987; B-406987.2
Date: October 10, 2012
Patricia A. Meagher, Esq., Neil H. ODonnell, Esq., and Suhani Kamdar, Esq., Rogers Joseph O'Donnell, for the protester.
J. Patrick McMahon, Esq., William T. Welch, Esq., and Kevin R. Learned, Esq., McMahon, Welch and Learned, PLLC, for the intervenor.
Alexander T. Bakos, Esq., and Kevin F. Kouba, Esq., National Aeronautics and Space Administration, for the agency.
Christina Sklarew, Esq., and Guy R. Pietrovito, Esq., Office of the General Counsel, GAO, participated in the preparation of the decision.
Protest that an agency misevaluated the protesters and awardees proposals is denied where the evaluation was reasonable and consistent with the solicitation criteria.
Integrated Science Solutions, Inc. (ISSi), of Walnut Creek, California, protests the proposed award of a contract to Earth Resources Technology (ERT), of Laurel, Maryland, under request for proposals No. NNA09263816R, issued by the National Aeronautics and Space Administration (NASA) for safety, environmental, and medical support services.
We deny the protest.
The RFP, issued as a small business set-aside, provided for the award of a single indefinite-delivery/indefinite-quantity contract for safety, environmental, and medical support services to all organizations and employees at the NASA Ames Research Center, California. Agency Report (AR) at 1.[1] This contract consolidates services currently being performed under two separate contracts: one for environmental support services, currently being performed by ISSi, and another for occupational safety, industrial hygiene and medical services.[2] Offerors were informed that both fixed-price and time-and-materials (T&M) task orders would be issued under the contract. RFP at 61.
The RFP provided for award on a best-value basis, considering the following evaluation factors: mission suitability, past performance, and cost/price. Id. at 91. The mission suitability factor was somewhat more important than cost/price, which was significantly more important than past performance. Id. at 104. The following subfactors and point scores were identified for the mission suitability factor:[3]
1. Technical Approach
a. Technical understanding
b. Response to case study A
2. Management Approach
a. Organizational structure and approach
b. Staffing, recruitment, retention, and training
c. Key personnel
d. Total compensation plan
e. Quality assurance plan
f. Response to case study B
g. OCI avoidance plan
3. Task Order Plan
4. Safety and Health Plan
Offerors were informed that the evaluation of proposals under the mission suitability factor would consider the offerors ability to fulfill the technical requirements while meeting quality, schedule, and safety requirements. Id. at 94. Compatibility between the proposed technical and management approaches and the overall resources proposed to accomplish the work was identified as an important consideration. Offerors were also informed that the agency would consider proposal risk with respect to cost, performance, and technical and management approach. Id.
The technical approach subfactor (275 points) consisted of two elements: technical understanding, which offerors were to address in their written volumes, and case study A (a hypothetical scenario), which offerors would address in an oral presentation. Id. at 70-72. In case study A, offerors were asked to address a laboratory managers request for technical assistance to ensure that the renovation of a 1960s research laboratory facility, which uses radioactive sources and organic chemistry procedures, meets all safety, health, and environmental regulatory requirements. A number of assumptions were stated for the case study, including funding limitations that led the laboratory manager to seek a cost effective approach. Id. at 70-71. Offerors were instructed to present a coordinated approach and detailed technical analysis in responding to the case study, and were provided a list of items to include in their response. Id. at 70-72.
The management approach subfactor (275 points) consisted of 7 elements, 2 of which--organizational structure and approach, and case study B--were to be addressed in the oral presentation. The remaining elements, such as key personnel, were to be addressed in the written proposal volume. In case study B, offerors were asked to address a hypothetical scenario under which the laboratory from case study A, now in operation, is undergoing an unannounced Nuclear Regulatory Commission (NRC) inspection. The scenario involves two researchers having an accident in the hallway, including spilled chemicals, a lacerated hand, a broken mercury thermometer, alarmed building occupants, and a fire department response without tools or expertise to evaluate radioactive materials releases, among other things. Offerors were required to present a management plan for providing support to emergency responders following an accident; defining actions needed to return affected areas to unrestricted use; providing a technical assessment of regulatory requirements; and providing briefings to an inspector and employees. A list of items that offerors were to include in their response was provided in the RFP. Id. at 74-75.
Offerors were informed that the agencys evaluation of the past performance factor would consider relevant quantitative and qualitative aspects of each offerors record of performing services or delivering products similar in size, content, and complexity to the requirements of this acquisition. Id. at 92-93, 100-02. Offerors were instructed to list up to three relevant contracts performed by the offeror and up to three relevant contracts for each major subcontractor. Id. at 79. The RFP provided that past performance would be assessed as providing a very high level of confidence; high level of confidence; moderate level of confidence, low level of confidence; very low level of confidence; or neutral.[4] Id. at 93.
With respect to cost/price, offerors were required to provide cost/price proposals for ten fixed-price sample tasks (representing the work that would be required), which would be evaluated for price reasonableness; and for time-and-material tasks, consisting of government-estimated amounts for fees/permits, materials and travel, which offerors would burden with indirect costs (such as material handling or general and administrative fees, and profit). Id. at 86. Offerors were informed that the agency would perform a price analysis to assess the reasonableness of proposed fixed prices, and a cost analysis to assess reasonableness of time-and-materials cost elements. Id. at 93. The RFP stated that proposed profit would be evaluated for reasonableness and for the extent that it [would] serve as a motivator of efficient and effective contract performance. Id. at 103. Offerors were warned that the agency would evaluate relatively low costs/prices to determine whether there is a risk of default in the event of award to that Offeror. Id.
The RFP also provided a number of pricing templates, such as summary pricing templates for the fixed-price sample tasks and for time-and-materials sample tasks, that offerors were required to complete. Id. at 83-88. Offerors were also required to complete a template for fully-burdened rates for each contract year, showing how the offeror arrived at its individually proposed rates, including profit. Id. at 85. Offerors were instructed to provide a detailed narrative to explain the rationale for the proposed profit. Offerors performing as prime incumbents, such as ISSi, were instructed to include current actual incumbent labor rates, if applicable, for each standard labor category. Offerors were informed that an offerors evaluated cost/price for selection purposes would be the sum of the offerors cost/price proposed on the summary fixed-price and time-and-materials templates for 5 years, excluding the price of phase-in and the emergency response T&M task. Id. at 103.
Five firms, including ISSi and ERT, submitted proposals, which were evaluated by the agencys source evaluation board (SEB). The SEB members individually evaluated proposals and then met to agree to a consensus evaluation for each proposal, identifying strengths, weaknesses, and deficiencies in respective proposals.[5] See AR at 7; see, e.g., AR, Tab 42, ISSi Initial Consensus Evaluation, at 2,223-52. Cost/price proposals were evaluated by a price analyst who, among other things, reviewed offerors pricing templates and proposed profit rates. AR, Tab 69, Price Analysts Statement, at 2-3.
The initial consensus evaluation results were presented to the source selection authority (SSA), who decided to include four proposals, including ERTs and ISSis, in the competitive range. AR at 8; Tab 46, SSA Initial Evaluation Findings Briefing. The SSA directed the SEB to further analyze the remaining competitive range offerors proposals to ensure vertical and horizontal consistency among the offers, and to confirm evaluated strengths and weaknesses. AR at 8.
Discussions were conducted, and ERTs and ISSis final proposal revisions (FPR) were received and evaluated as follows:
Mission Suitability
Technical approach
Very Good
Management approach
Task order plan
Very Good
Safety & health plan
Past Performance
High Confidence
High Confidence
$38.8 million
$33.9 million
AR, Tab 63, SEBs Final Evaluation Findings, at 4,397. The SEBs adjectival ratings and point scores were supported by narrative discussions that described the offerors respective strengths and weaknesses. In this regard, the SEBs description of an evaluated strength addressed how the strength reflected the RFPs requirements and explained why it was considered a strength.
For example, ERTs very good rating under the technical approach subfactor reflected the SEBs judgment that ERTs revised proposal presented one significant strength, two strengths, and no weaknesses. Id. at 4,403-04. ERTs response to case study A was one of the identified strengths, where the SEB found that ERT had demonstrated a clear understanding of the technical requirements and had proposed several innovative approaches to performing the work. Id. at 4,408. In explaining why ERTs proposal merited a strength under this subfactor, the SEB noted, among other things, ERTs proposal of a decommissioning phase, recycling materials during the construction phase, and preparing consolidated reports. Id.
ISSis good rating under the technical approach factor reflected the SEBs determination that ISSis revised proposal presented three strengths (none of which were significant) and no weaknesses. Id. at 4,412. ISSis response to case study A was not one of the identified strengths.
ERTs excellent rating under the management approach subfactor reflected the SEBs judgment that ERTs proposal presented a significant strength, three strengths, and no weakneses. Id. at 4,420-21. One of the strengths identified in ERTs FPR under this subfactor was for its effective and appropriate response to case study B, in which it identified the procedures that should be in place in the Research Center during an emergency situation. The SEB cited ERTs incisive and detailed assessment under this case study of the likely radiological injury and medical treatment options, which was found to show an ability to effectively support NASA Ames during similar situations. Id. at 4,424. In explaining why the SEB considered ERTs response to case study B to be a strength, the evaluators noted ERTs analysis of the health unit procedures, identification of factors to consider for treatment, and proposed long-term surveillance of injured parties, and found that the thoroughness of ERTs response provided a clear indication of the vendors medical expertise, as well as inspiring confidence that ERT would provide effective support in similar real-life situations. Id.
ISSis good rating under the management approach subfactor reflected the SEBs judgment that ISSis FPRs contained four strengths (none of which were significant) and no weaknesses. Id. at 4,428-29. One of the strengths indentified in ISSis proposal was its offer of a highly-qualified project manager as a key person, who the SEB found would have a positive impact on contract performance. Id. at 4,428, 4,430.
Another strength was ISSis response to case study B, where the SEB found that ISSi proposed a multitude of effective and appropriate mitigations to the hazards and risks associated with medical care during an accidental spill or a similar emergency situation. The SEB also found that ISSi proposed lessons learned that provide continuous improvement during emergencies. The SEB found that this reasonable and effective approach would help increase employee safety and have a positive impact on successful contract performance. Id. at 4,431. In explaining why it considered ISSis case study B response to be a proposal strength, the SEB noted ISSis risk reduction approach, stating that the offeror had identified 16 risks and 36 risk mitigation measures, addressing such matters as delay in the delivery of medical care, and risk of contamination spread outside the containment zone during the transportation of the injured employee. The SEB found ISSis approach to the complex situation presented in case study B to be comprehensive and highly developed. Id. at 4,431-32.
The firms revised costs/prices were evaluated by the agencys price analyst, who again reviewed, among other things, the offerors pricing templates and proposed profit rates. AR, Tab 69, Price Analysts Statement, at 3. He also developed a chart to reflect the rates proposed for positions for which the offeror was the incumbent contractor; and considered the offerors stated intentions with respect to retaining incumbent contractor employees, and whether current compensation levels for those employees would be paid. The price analyst analyzed each offerors potential realized profit and profit rate if they were to hire the incumbents and retain them at their current pay levels. Id. Thus, with respect to ISSi, the price analyst performed calculations based on the assumption that ISSi would retain incumbent staff at their current pay levels (as stated in its proposal) and found that this would result in an increase in ISSis probable cost over costs proposed in ISSis FPR.[6] The analyst calculated, further, that this increase in costs would result in reducing ISSis realized profit rate to approximately 1.6 percent (in contrast to the 7 percent profit rate listed in the protesters FPR). Id. at 4.
The technical and price evaluation judgments were presented to the SSA, who also read the offerors FPRs. He concurred with the findings and adopted them in making his source selection decision. AR, Tab 66, Source Selection Decision, at 4,696. Noting that he found no discriminators among the offerors under the past performance factor, the SSA based his selection decision on the mission suitability and cost/price factors, and recognized that the RFP provided that the mission suitability factor was somewhat more important than cost/price. Id. at 4,697. With respect to price, the SSA stated that the integration between mission suitability findings and price was critical to determining price reasonableness. Id. at 4,688. In this regard, the SSA noted the SEBs determination that offerors cost/price proposals were reasonable and realistic, and that no cost adjustments were made. Id. at 4,695.
Regarding the evaluation of the firms proposals under the mission suitability factor, the SSA noted ISSis proposal was the second-lowest rated among the proposals included in the competitive range. In this regard, the SSA found that ISSis proposal, which had been assessed as containing nine strengths under this factor (none significant), simply met the RFP requirements in many areas of the statement of work. Id. at 4,697. In contrast, ERTs proposal was the highest rated under the mission suitability factor, having received 121 points more than the next highest offer (and 179 points more than ISSis proposal). The SSA noted that ERTs proposal had been assessed as having three significant strengths under the three most heavily-weighted mission suitability subfactors (contract task order plan, technical approach, and management approach), and eight strengths.
Recognizing that other offerors, such as ISSi, had lower evaluated costs/prices than ERT, the SSA nevertheless concluded that these firms lower costs/prices were outweighed by ERTs evaluated technical superiority under the mission suitability factor.[7] Id. at 4,700. The SSA stated that he based his selection decision primarily upon the markedly stronger approaches by ERT in these three most heavily weighted Mission Suitability [s]ubfactors. Id. at 4,698. The SSA states that ERTs superior mission suitability proposal would translate into better risk avoidance and management; that ERTs proposal was credible and reflected the reality of the current market; and that ERTs proposed prices supported the likelihood that the firm would obtain, and retain, high-quality staff throughout the life of the contract, which would provide superior contract performance within budget and with potential future efficiencies. Id.
ISSi was informed that ERT was the apparent successful offeror,[8] and this protest followed a debriefing.
ISSi challenges numerous aspects of the agencys evaluation of its proposal under the mission suitability factor, primarily arguing that its scores and ratings should have been higher and that the agency treated ISSi and ERT unequally. ISSi also objects to the agencys cost/price evaluation, arguing that NASA incorrectly analyzed ISSis profit rate. We have considered all of ISSis arguments, although we only address its more significant arguments, and find that none provide a basis to object to the agencys selection of ERT for award.[9]
In reviewing protests challenging the evaluation of proposals, we do not conduct a new evaluation or substitute our judgment for that of the agency, but examine the record to determine whether the agencys judgment was reasonable and in accord with the solicitations evaluation criteria. Abt Assocs. Inc., B-237060.2, Feb. 26, 1990, 90-1 CPD ¶ 223 at 4. Where a protester challenges the agencys evaluation and source selection, we will review the evaluation and award decision to determine if they were reasonable, consistent with the solicitations evaluation scheme, as well as procurement statutes and regulations, and adequately documented. See, e.g., Wackenhut Servs., Inc., B-400240, B-400240.2, Sept. 10, 2008, 2008 CPD ¶ 184 at 6; S4, Inc., B-299817, B-299817.2, Aug. 23, 2007, 2007 CPD ¶ 164 at 9. A protesters mere disagreement with the agencys evaluation provides no basis to question the reasonableness of the evaluators judgments. See Citywide Managing Servs. of Port Washington, Inc., B-281287.12, B-281287.13, Nov. 15, 2000, 2001 CPD ¶ 6 at 10-11.
Technical Approach Subfactor
ISSi complains that NASA misevaluated its proposal under the technical approach subfactor, because NASA did not identify ISSis response to case study A as a strength. ISSi contends that the technical requirements in the statement of work were nearly identical to the technical requirements of the contract ISSi has been performing, so that its proposal of its incumbent approach demonstrated its proven ability to comply with the applicable regulations and demonstrated a clear understanding of the technical requirements. Protest at 7. ISSi complains, in this regard, that the agency assigned a strength to ERTs proposal for its approach to case study A, where the agency found ERTs response showed a clear understanding of the technical requirements, the ability to work in a reasonable and effective manner, and the ability to comply with applicable regulations.
The agency responds that it reasonably evaluated the two firms responses to case study A. With respect to ERTs response, the SEB found that ERT had proposed cost-effective and innovative approaches to the renovation of a laboratory facility, which would help ensure regulatory compliance and employee safety. AR, Tab 63, Final SEB Report, at 4,408. The SEB specifically noted as justification for its assigned strength ERTs proposed innovations, such as adding a lab decommissioning phase in order to clear out the area prior to the construction phase (which demonstrated insight into controlling hazards that may interfere with construction efforts) and consolidating safety, health, and environmental reports (which would streamline the review and distribution process, resulting in time savings for the contractor and the agency). Id.
In contrast, the agency notes that, although ISSis response to the case study was appropriate, reasonable, and effective for all of the required elements, it did not propose anything unique or innovative that warranted a finding of a strength. AR at 11. Further, the agency states that its evaluation was based on its review of the offerors proposals, and not upon an offerors performance as the incumbent contractor.
We find the agencys evaluation reasonable and consistent with the RFP. The SEB documented its basis for its evaluation in this area, citing specific examples to justify the strengths assigned. The SEBs conclusion that ERTs response to case study A demonstrated an approach that exceeded the RFP requirements and would have a positive impact on the successful performance of the contract was consistent with the evaluation standard stated in NASAs Source Selection Guide. While ISSi disagrees with the evaluation results, insisting that NASA has provided no rationale for its failure to recognize this strength, ISSi has not shown that it offered innovations or other features (greater than its proven ability to meet the requirements) exceeding the requirements or otherwise warranting the assignment of a strength in this area. Protesters Comments at 5. ISSis disagreement provides no basis to question the agencys judgment.
Management Approach Subfactor
Similarly, ISSi complains that its proposal should have been assessed a significant strength under the management approach subfactor for its key personnel, arguing that each of its proposed key personnel exceeded the RFP requirements, and that its proposed program manager, in particular, could not reasonably be viewed as providing anything less than a significant strength. In this regard, ISSi states that it proposed the same individual for its program manager in earlier competitions for this requirement (in 1999 and 2004), where the program manager was identified as a significant strength in its proposal.[10] ISSi argues that this program manager has been successful and effective in performing the incumbent contract, and that her increased experience and expertise should have been recognized as a significant strength. ISSi also argues that the inconsistency of the results here with prior evaluationson the subject of its program manager--is unreasonable.
NASA responds that the protesters program manager was specifically cited as highly qualified and effective, and was identified as a strength in ISSis proposal. However, the agency disagrees that a significant strength was warranted, noting that no other offeror was given a strength with respect to proposed key personnel. The agency again states that its evaluation was appropriately based on a review of the submitted written and oral materials, and not on prior evaluations or opinions.
The evaluation record supports the agencys arguments; the SEBs review of ISSis FPR describes the protesters proposed program manager as having demonstrated the ability to efficiently perform, coordinate, and integrate environmental, safety, health, and medical requirements. The SEBs review also notes that ISSis choice of the program manager was based, in part, on the individuals consistently meeting environmental, health, and safety requirements despite declining budgets and staff. The SEB concluded from this that the program manager should help Ames facilitate effective management of the work, which will have a positive impact on the successful performance of the contract. AR, Tab 63, Final SEB Report, at 4,430. This conclusion is consistent with the definition of a strength. AR, Tab 32, NASA Source Selection Guide, at 382. We find the agencys evaluation reasonable and consistent with the RFP.
Also under the management approach subfactor, ISSi argues that its proposal was misevaluated for its response to the case study B element. Here the protester argues that it was unreasonable to assign only a strength for the response when the SSA stated that ISSi proposed a multitude of effective and appropriate mitigations to potential hazards and risks, and that this tracks the plain-language reading of what is needed for a significant strength. Protest at 9.
Case study B describes a complex hypothetical scenario in which a radioisotope lab is undergoing a surprise inspection, during which an accident occurs that presents multiple problems that must be managed. Offerors were required to respond to the scenario with an oral presentation, presenting a management plan detailing initial response support, and defining the actions needed to solve the various critical problems. RFP at 97-98. The RFP stated that the management plan would be evaluated for an efficient methodology that meets current regulatory and operational requirements in a synergistic and timely manner, and listed the elements the evaluators would consider in determining the appropriateness, reasonableness, and effectiveness of the response. Id. at 97.
The SEB found a strength in ISSis response, as cited by the SSA, above, and discussed it in its report with examples of risk mitigation measures that ISSi proposed, as well as noting the protesters lessons-learned approach to provide continuous improvement during emergencies. AR, Tab 63, Final SEB Report, at 4,431-32. NASA argues that these evaluation conclusions, and the narrative evaluation on which they are based, are consistent with a strength, and not more. We agree. The definition of significant strength requires some aspect of the proposal that greatly enhances the potential for successful contract performance. AR, Tab 32, NASA SEB Source Selection Guide, at 382. We again find ISSis objections to the evaluation to be based on disagreement, without showing that the agencys judgment was unreasonable or its conclusions inconsistent with the RFP.[11]
Cost/Price Evaluation
ISSi also protests the agencys cost/price evaluation, arguing that the agencys concerns with ISSis realized profit rate were based upon a flawed analysis. See Supp. Protest at 7-11. As described above, the price analyst reported to the SEB that ISSis actual profit rate was likely to be significantly lower than the rate it stated in its FPR, if it hired incumbent staff and paid them at their current rates. This concern was mentioned by the SSA in his source selection decision. ISSi contends the analysts reasoning and calculations were flawed in a variety of ways.
NASA disagrees with ISSi that the agencys evaluation of the firms actual profit rate was unreasonable. Supp. AR at 5-8. The agency also contends that, in any event, this concern was not found to be a proposal weakness, which was required to be discussed, and did not affect the SSAs selection judgment. Id. at 9-10.
We need not resolve ISSis concerns with the agencys evaluation of its profit rate because the record shows that the award decision was not affected by the SEBs or SSAs consideration of the adequacy of ISSis proposed profit rate. The SSAs contemporaneous documentation of the source selection includes only one sentence relating to this issue: [a]nd I have concerns regarding some of the proposed profit rates, which, in my opinion, may not be high enough . . . . AR, Tab 66, Source Selection Decision, at 4700. Despite this expression of concern, the selection decision is substantively based on ERTs proposals distinct superiority under the most important mission suitability factor, and the SSAs conclusion that this technical superiority merits the associated difference in cost. Id. Under these circumstances, we conclude that, even were we to agree that errors were made in the price analysis, it would provide no basis to sustain ISSis protest.[12]
The protest is denied.
Lynn H. Gibson
General Counsel
[1] Our page citations to the AR, and included documents, are to the Bates numbers assigned by the agency.
[2] The agency states that the work currently performed by ISSi involves less than half of the total requirements and functional areas of the new, consolidated contract at issue here. AR at 1.
[3] The RFP also provided that the mission suitability factors would receive adjectival ratings (excellent, very good, good, fair or poor) in addition to point scores. RFP at 92.
[4] As relevant here, a very high level of confidence rating reflected relevant past performance of exceptional merit that was very highly pertinent, and which indicated exemplary performance in a timely, efficient, and economical manner, with very minor (if any) problems with no adverse effect on overall performance. A high level of confidence rating reflected relevant past performance that was highly pertinent, which demonstrated very effective performance that would be fully responsive to contract requirements with contract requirements accomplished in a timely, efficient, and economical manner for the most part with only minor problems with little identifiable effect on overall performance. RFP at 93.
[5] A significant strength reflected some aspect of the proposal that was found to greatly enhance the potential for successful contract performance. A strength reflected an aspect of the proposal that would have some positive impact on the successful performance of the contract. AR, Tab 32, NASA Source Selection Guide, at 382.
[6] The analyst found that an appreciable number of the rates proposed by ISSi for incumbent positions were notably lower than the current actual rates for those labor categories. AR, Tab 69, Price Analysts Statement, at 3.
[7] Regarding the other offerors lower evaluated costs/prices, the SSA acknowledged that none of them were found to be unrealistic or unreasonable, but stated that, in his judgment, each offer carried some level of performance risk, and did not correspond as well to what was promised under the mission suitability factor. In addition, the SSA was concerned that some of the proposed profit rates may not be high enough to serve as a motivator of efficient and effective contract performance. AR, Tab 66, Source Selection Decision, at 4,700.
[8] ISSi and another offeror challenged ERTs size at the Small Business Administration (SBA), alleging that ERT had outgrown the size standard applicable to this procurement when it submitted its initial proposal on December 20, 2010. On September 19, SBA found that ERT met the small business size standard applicable to this procurement.
[9] ISSi also protested the agencys evaluation of ERTs past performance, arguing that ERT proposed a subcontractor whose allegedly fraudulent conduct should have precluded the high level of confidence rating ERT received. ISSi also argued that its own past performance rating should have been higher. The agency addressed ISSIs past performance arguments in its report, and ISSi did not rebut or otherwise address the agency's response. We find that the protester has abandoned these arguments. CM Mfg., Inc., B-293370, Mar. 2, 2004, 2004 CPD ¶ 69 at 3.
[10] Although ISSi states generally in its protest that the key personnel it identified in its proposal exceeded the requirements, the RFP did not specifically state requirements for key personnel. We recognize that the RFP in Attachment J.1(b)(2) provides standard labor categories description[s] for [the] pricing template, but ISSi does not explain how its comparison of the qualifications of its key personnel against the labor category descriptions in this attachment establish that its key personnel should have been evaluated as a strength under the management approach subfactor. In this regard, other than the program manager, the positions ISSi identified as key do not track the standard labor categories listed in the RFP. Compare RFP Attachment J.1(b)(2), Standard Labor Categories Description for Pricing Template, at 169-73, with AR, Tab 53, ISSis Mission Suitability FPR, at 2,955-60. Moreover, after generally raising this argument in its initial protest, ISSi did not further address it in its pleadings.
[11] Further, ISSi complains that the evaluators treated its proposal and ERTs proposal unequally with respect to case study B, arguing that they noted strengths for ERT based on individual task orders, whereas ISSis proposal was found to have only one strength for its innovative and proactive approach for seven task orders. NASA responds that ISSi proposed the exact same set of management system and other details for the individual tasks, while ERT described a customized and distinct approach to various aspects of the subfactor tasks. Supp. AR at 10-11. We find that the agencys assignment of strengths reasonably reflected the offerors differing approaches.
[12] ISSi also argues that because the agencys concerns with its profit rate were fatal to ISSis chances [of] receiving [the] contract award, it should have been raised in discussions. Supp. Protest at 1. As noted above, we do not agree that the expressed concern with ISSis profit rate affected the source selection decision.
Nov 25, 2020
Battelle Memorial Institute
We deny the protest.
Exceed, LLC
We deny the protest.
Nov 24, 2020
Posterity Arora JV, LLC
We deny the protest.
Technology, Automation & Management, Inc.
We deny the protest.
Nov 20, 2020
Cellco Partnership dba Verizon Wireless
We deny the protest.
RIVA Solutions, Inc.
We deny the protest.
DynCorp International, LLC
We deny the protest.
Nov 19, 2020
Qbase, LLC; Perspecta Enterprise Solutions, LLC; and Northrop Grumman Systems Corporation
We sustain the protest.
Looking for more? Browse all our products here


text:
Employment Training Program
$50,000 | Spring 2018 | Social Causes
Paul M. Angell Family Foundation
Supporting Conservation, Performing Arts, Social Causes
Employment Training Program
$50,000 | Spring 2018 | Social Causes
Welcome to the web site of the Paul M. Angell Family Foundation, where you can learn about the Foundation, its granting activities, and peruse grant recipients. Current account holders can log into the online grant management area to work on open applications or complete reports. While you're here, please click on About Paul M. Angell to learn about the life of the man who inspired the formation of this Foundation.
Dear Friends and Colleagues, Like all of you, our hearts ache. The murder of Mr. George Floyd is unbearable and intolerable. Of course, we know all too well that this is not an isolated tragedy. Racism has been deeply embedded in our nation's systems and institutions for hundreds of years and it won't be rooted out quickly. But such horrors must … Learn More »
The Foundation is pleased to announce the grant cycle calendars for 2021. Please note, all LOIs are due on the deadline date on or before 11:59 PM, Central Time, unless otherwise noted. … Learn More»