text:
In case you hadn't heard, Justin Roiland, creator of Rick and Morty, just announced that he's started a new VR games studio. The new studio is a collaboration between Roilander and Tanya Watson, who previously worked at Epic Games.
Naturally, Roilander named the game studio "Squanchtendo." (For those unaware, "squanch" is a word used by the character Squanchy in Rick and Morty and is basically every part of speech possible — think of it like the word "Smurf" in Smurf culture.)
The new studio was announced via a comic of all things, alongside a website that is characteristically Roilander. And while the game studio hasn't announced any projects and seems to be focused on IPs outside of Rick and Morty, it's still fun to imagine what would happen if Squanchtendo did decide to mix the wonderful world of Rick and Morty with the crazy world of virtual reality.
So today, we're going over our top 7 Rick and Morty episodes that we think would make perfect virtual-reality games.
7. "Get Schwifty"
"Show me what you got!" - Armagheadon
Look, it might not have a whole lot going on in terms of space exploration, but "Get Schwifty" has led to several memes and it would be a travesty to keep that from players. Plus, it would give players a chance to lay down some sick Rick beats — but in virtual reality, bro.
I can even see it having a side quest where you must help Ice-T regain his powers and defeat the Numericons. Talk about action and adventure!
6. "Meeseeks and Destroy"
"Look at me, I'm Mr. Meeseeks!" - Mr. Meeseeks
Take two strokes off your golf game! Give Beth relationship advice! Teach a teen what the true meaning of popularity is! But make sure to do it within the time limit, or things are gonna get weeeeeird.
Not a fan of time-based challenges? Why not try to help a Medieval-style village by killing the terrifying giant and narrowly escaping the legal system. Once that's done, hop on top of Slippery Stair for a thrilling trip down the giant staircase back to the village!
5. "Close Rick-counters of the Rick Kind"
"Save your anti-Rick speech for the Council of Ricks, terror-Rick." - Rick (but not our Rick)
I'm dreamin' big here, but what if Squanchtendo decides to give a go at the MMO genre? This would be the perfect opportunity to play as one of an infinite number of Ricks and meet up with other Av-Rick-tars in the Citadel of Ricks.
Plus, you could compete to be the first Rick to clear your name in a crime-solving, Rick-tastic adventure. Not enough for you? How about inter-dimensional travel where you have to hide amongst the chair-people? But what, there's more!
Find out who framed you for the Rickicidal epidemic? Put a bounty on that Rick's head in the crazy RVR (Rick versus Rick) system.
4. "Lawnmower Dog"
"Where are my testicles, Summer?" - Snowball, formerly known as Snuffles.
Don't let the plethora of adorable virtual-reality puppies fool you. This one's serious business, brah. It's kinda like Inception, so if you don't like it, then maybe that movie wasn't so great.
The great thing about this episode is that it offers the chance for some crazy, Watch_Dogs-like intrusion into people's dreams, which can open worlds of possibilities. Sure, the main story might be a legally safe knock-off of an '80s horror film, but if the horror genre in VR becomes too much for you, you can always dream-hop your way into someone else's dream.
3. "Anatomy Park"
"Welcome to Anatomy Park!" - Dr. Xenon Bloom
Take a ride on Pirates of the Pancreas! Have a spooky romp through the Haunted Liver! Get down and dirty with the Colon Log Ride!
Yes, Anatomy Park has it all, and it's totally safe! Yup, no Bubonic Plague or Tuberculosis to shoot down here. Perfectly safe.
Anatomy Park would be the perfect setting for a virtual-reality experience, because you could see first-hand what it's like to have an amusement park inside a human's body while also honing your first-person shooter skills against diseases. It's fun and educational!
2. "Look Who's Purging Now"
"It's a purge planet. They're peaceful, and then, you know, they just purge." - Rick Sanchez
It's the survival-horror experience of a lifetime. You've crash landed on this planet the night of the purge, and you need to survive until morning. Oh, and you also need to reap maximum carnage.
Seriously, this episode has everything you'd need for a perfect VR experience. A full planet's setting to explore, cat-people, consequence-free violence, and even an upgrade-able robotic suit of armor to help you survive and fly around the planet like Iron Man.
Of course, you could always take the pacifist route and try to Morty your way to safety until sunrise — but where's the fun in that?
1. Roy
"This guy doesn't have a social security number for Roy!" - Some background character
No, it's not an episode. You know who doesn't give a f***? Rick! Also me. I don't care.
Roy — the game from "Mortynight Run" — is made for virtual reality. Like, literally. It's a virtual reality game within the show, so if anything from Rick and Morty makes it into virtual reality, it needs to be Roy.
But, of course, it would have to first let players walk through Blips n Chitz in virtual reality, because if it's not a virtual reality game within a virtual reality game, what's even the point?


text:
September 24, 2011 BY Brendan Dunne
With "breathability" being a buzzword this year, it comes as no surprise that the Nike Trainer 1.3 Max is scheduled for a ventilation upgrade. No, its not getting the Hyperfuse treatment like so many other sneakers this year, instead it will evolved into the Nike Trainer 1.3 Max Breathe, featuring perforated paneling on the upper that encourages air passage. Of course the basics of the trainer remain intact, including the all important 360 Max Air sole. Take a full look at both of the Summer 2012 colorways after the jump and let us know what you think of this upgrade on the Nike Trainer 1.3 Max. via CK
Nike Trainer 1.3 Max Breathe
White/Photo Blue/Black
White/Varsity Maize/Black
Filed under: Nike Air Max Trainer Upcoming Sneakers

subset: commoncrawl


text:
The Fire 15 features 11 great sounding amp models and 18 editable Zoom effects. Standards like Chorus, Flanger, Phase, Delay, and Reverb as well as modern sounds like Ring Modulator and Slow Attack.
All Zoom 2 Models
35 Watt Amp. 10" driver. 22 built-in amp models. 7 effects modules. 19 effects types. 10 user programmable patches / 20 Zoom preset patches. 3-band EQ. Auto-chromatic tuner. AUX input.


text:
Thu 14th Feb at 8:00pm
Valentine's Comedy Burlesque
@ The Musician, Leicester
Featuring: Talulah Blue, Doc Leroc, Kiki Kaboom
This event has been and gone!
Catch the next one:
Check out the info below for future tour dates, and track them to receive alerts when they tour near you
Valentine's Comedy Burlesque: Talulah Blue, Doc Leroc, Kiki Kaboom
Talulah Blue
'... sapphire-haired siren and international burlesque performer' (Bluestocking Lounge, Swansea).
Talulah Blue tour dates
Track this event
- Event has been added to your calendar
- Any important updates will be sent to your email address
- Add to your personal Ents24 calendar
- Sync with iCal, Outlook and others
- Receive important updates
Venue Facts
Venue: The Musician
Website: themusicianpub.co.uk
Email: ...
Phone: 0116 251 0080
Disabled Bookings: 0116 251 0080
→ Leicester 11 min walk


text:
Saturday, November 09, 2013
The background has been given a wash of diluted tester pot paint " dusted Fondant". I have stamped the page using a stamp by Visible Image "Ripped Fishnet". I have used this stamp a couple of times now and love it. There are so many uses that it can be put to.
The plastic netting overlay is from a net bag used on bottles of booze. (Kindly donated by The Doc after consumption of course!. The letter N is from a Free Calligraphy site and can be found here.
Entering into the following challenge:
The Craft Barn Alpha Challenge: Use the letter N.
The 'Net' is closing in now as there are just 4 letters left to choose. I,Q,S & X.
I wonder which one it will be next!!
18 comments:
That Ripped Fishnet is a marvellous stamp....love it....today I had a workshop with mixed media...one of the ladies had some tiny dies of cats, so I immediately had to think of you....you should love them I think!ReplyDelete
Have a great weekend!
♥♥♥ Margreet
Hi Mrs A, Love this page, and the 'net' stamp is fabulous - thought it was real at first.ReplyDelete
Avril xx
Hi Mrs A .....Fish nets say no more....lol fabulous page as always truly love it xReplyDelete
Wonderful and so cleverly embellished.ReplyDelete
Great csrf by you n Doc Mrs A.ReplyDelete
Oops card! I meant, on mobile.:)ReplyDelete
Wonderful net page, love that stamp.ReplyDelete
Sylv xx
Fabulous stamping Mrs A, that stamp is on my wish list xReplyDelete
The ripped fishnet looks almost three-D.ReplyDelete
Thought you had recycled your tights:)
Sue xxx
Well done for keeping up with these Mrs A! Great one this time!ReplyDelete
Great choice and interpretation!ReplyDelete
Well done
Thanks for playing with us at the Craft Barn
Well done, Mrs. A! Very, very tactile and wonderful! I've just come from a visit with Miss Di and read about your antics! You two make everyone wish they knew you!! Hugs, DarnellReplyDelete
I see, I see - brilliant! So glad I ordered that fishnet stamp with you on Sunday - it looks a bit like me after a night out, dancing round our handbags with you really! Girlies do that and then run home to their chaps and act sensible of course.ReplyDelete
Snigger, I see Darnell has finally cottoned onto you :) You do realise we now need to devise a special 'song and dance routine' for folk we might meet from Blogland? I can be the little plump one and you can do the tall and elegant bit! Top hat and tails anyone?
Right now am crawling round like the Hunchback of Notre Dame though, sigh, off to bed just to lie flat and it's only 7:30 pm :( Gawd, them coach seats were not at all comfy were they? :( Me taking a cushion to Bath!!
Hugs, Di xx
hi Mrs A oh wow you have done a great job and I love the stamp :)great idea :)ReplyDelete
This net stamp is fabulous! Too bad I have already blown this months scrappy budget on other treasures...but this one might just go on my Xmas stocking stuffer list!ReplyDelete
I make a lot of fishing, boating, mermaid cards and netting is crucial.
Your N page is fabulous...and so nice that the Doc was thinking of you and helping out with emptying the bottle!!!
God help Bath! Love the colours xReplyDelete
This is a great page and an inspired idea to illustrate the letter N. I have recently bought some stamps with a seaside theme and this stamp would go beautifully, and thank you for your lovely comments.ReplyDelete


text:
This year's Patriots team is very similar to the Patriots team that won the Super Bowl in 2004.
"USA Today" noticed that there are a lot of, quote, "eerie similarities" between this year's New England Patriots team the Patriots team that beat the Carolina Panthers in Super Bowl 38 back in 2004.
Here they are the 13 ways:
1. Both Patriots teams played, or will play the big game in Houston.
2. Both played or will play an NFC South team in the Super Bowl.
3. Both teams went 16-2 to get to the Super Bowl.
4. The Super Bowl 38 Patriots were two seasons removed from beating an NFC West team (in that case the Rams). The Super Bowl 51 Patriots are two years removed from beating an NFC West team (the Seahawks).
5. Both Patriots defenses finished FIRST in the league in points allowed.
6. Both teams were the #1 seed in the AFC playoffs and managed to avoid the #2 seed, the Chiefs, in the AFC Championship.
7. Both teams finished first in the AFC East with a 14-2 record. The Dolphins finished second with a 10-6 record both times.
8. Both teams suffered their first loss of the season by being shut-out by the Bills.
9. During the 2004 playoffs, Tom Brady threw five touchdowns and two interceptions. Entering Super Bowl 51, he's thrown five touchdowns and two interceptions in the playoffs.
10. Before playing Super 38, the Patriots hadn't trailed in a game since Week 12. The current Patriots team hasn't trailed since Week 12.
11. This year's Patriots beat an AFC South team that plays in Houston (the Texans) in the divisional round. The Super Bowl 38 Patriots beat an AFC South team that used to play in Houston (the Titans) in the divisional round.
12. Both teams beat the Jets in Week 16, and then they beat another divisional opponent in Week 17 to finish the season with a record of 5-1 in the AFC East.
13. And #13 is that these two seasons are 13 years apart!
Click Here to see more.


text:
Mr. GRAHAM. Mr. President, I want to thank my colleague from New Hampshire who has been one of the strongest voices since the day she got here in the Senate to talk about the difference between fighting a war and fighting a crime. The Senator has been the attorney general of New Hampshire, and I have been a military lawyer for over 30 years. The legal systems to fight a war are different than the legal systems to solve a domestic crime.
Here is the problem: Do I believe Al Qaeda is at war with the United States and our values and our friends? Would they kill us all if they could? Yes.
Why did 3,000 Americans die on 9/11/2001? They couldn't kill 3 million of us. If they could, they would have. If you believe that, then the goal of our generation is to marginalize this movement, and when we capture one of them, we need to find out what they are up to.
Dying for their cause is not a deterrent. It is like first prize. So when you tell somebody who has joined Al Qaeda that you may die in the course of this attack, they say good. The goal is to prevent them from hitting us, and the best way to do that is through intelligence gathering.
When you capture someone who is determined by our military and intelligence community to be a member of Al Qaeda, then under the law of war--the authorization to use military force passed by Congress over a decade ago--you can hold that person under the law of war to gather intelligence.
Why is that the case? War is about winning the war. Enemy prisoners are valuable captured alive because they can provide information about what the enemy is up to.
When you charge someone with a crime, you cannot spend a long time with them without their lawyer trying figure out if they committed the crime because of the right against self-incrimination in our criminal justice system. The military legal system, and the law of war, is completely different when it comes to asking questions of an enemy prisoner about future military activity or what they know about past operations.
The most dangerous thing we could do as a nation is to treat a captured Al Qaeda terrorist as a common criminal, read them their Miranda rights, and put them in civilian court before we have a chance to gather intelligence. That is exactly what the Obama administration did here. To their credit, they captured al-Libi. Here is what breaks my heart the most: The special forces units that go into Libya, Somalia, and Pakistan risk their lives to capture these people alive, if possible, so we can gather intelligence.
It really does bother me that after completing this operation, which was very successful, we only had control of this enemy prisoner for about 10 or 11 days. I will never be convinced that in that short period of time we were able to gather the intelligence he possessed. He has been associated with Al Qaeda at the highest level for 20 years. He was a treasure trove of information.
This was a political decision by the Obama administration, not a legal decision based on the law of war. This is not what our military advises or our intelligence community advises. This is what the President chose to do because he does not want to use Guantanamo Bay.
Why was he placed on a ship? Because there is no prison available in the United States, other than a naval vessel, to hold someone as an enemy combatant under the law of war. Why? Because the President refuses to use Guantanamo Bay.
If we can close Guantanamo Bay and create a new prison to allow people to be held as enemy combatants, sign me up. But the idea of not having a jail available to the United States on land at a time of great stress, and during a very pivotal moment in the war on terror, is an ill-conceived and dangerous policy.
I applaud the Senator from New Hampshire for bringing up this issue.
Here is what we need to understand as Members of Congress: This policy cannot be sustained. When we capture high-value targets, such as a 20-year veteran of Al Qaeda, we are crazy as a nation not to use the law of war to gather intelligence.
I am not for torturing anyone. I have been a military lawyer for 31 years. I believe in the Geneva Conventions. I believe my country is special. I believe in the international regimes about how we interrogate prisoners we hold. I know what Al Qaeda does to their prisoners. I do not want to be like them. I want to be the United States. But the United States has a right, under the law of war, to gather intelligence.
The last thing a member of Al Qaeda should hear when they are captured is: You have a right to remain silent. Here is your lawyer.
I don't want them to remain silent. I want them, over time, to provide us with whatever intelligence is available.
Why was he moved off the ship? Apparently, he had a medical condition that could not be treated on the naval vessel. I believe in providing quality health care to prisoners of war simply because I want that standard to be available to our soldiers in future wars. The standard we set today will follow us into the next war and, unfortunately, there will be. But having to take him off the ship because he was sick is no excuse to stop his interrogation to gather intelligence. Putting him on the ship because we don't want to use Guantanamo Bay is an ill-conceived and ill-designed strategy that, if it is not changed or replaced, is going to come back to haunt this country.
This man possesses an enormous amount of intelligence potential. He is now in Federal court. He will be given a lawyer. Once he is charged with a crime, he should be given a lawyer. But before that, we have the right under the law of war to hold him to gather intelligence--treat him humanely but question him about what he knows about Al Qaeda, because they are still out there, lurking.
I will end with this. I wish to work with the Senator from New Hampshire and anybody on the other side who would like to try to find a detention and interrogation policy that is more rationally based. Guantanamo Bay, in its early years, did hurt the image of this country. Some of our interrogation techniques right after 9/11 hurt us as a nation.
Guantanamo Bay has been reformed. It is Geneva Convention compliant. The Detainee Treatment Act that I helped author with Senator Levin and Senator McCain is the gold standard of how we treat people under the law of war. I am proud of the system we have created over the last several years in a bipartisan manner, and I urge this administration to create a vehicle to interrogate under the law of war people such as al-Libi so we can be prepared for the next attack. The policy they have in place today is going to deny this country the ability to gather valuable intelligence.
When it comes to defeating Al Qaeda, the more we know about how they behave and what they are up to the safer we will be, because they will not be deterred by the threat of death. We cannot deter them; we have to stop them. We have to hit them before they hit us, and the best way to do that is to gather intelligence when we find someone such as al-Libi.
I am very disappointed that we have blown it when it comes to intelligence gathering with this high-value target. I am very sad to report to the military members and their families that the bravery they have demonstrated and shown just a few weeks ago has been undermined, in my view, by an irrational political decision that denies our country the ability to learn from a high-value target they risked their life to capture.
I don't know how to fix this in the current political environment, but I know as a military lawyer it needs to be fixed, and I know we are not elevating our country by diminishing our ability to use legal systems that have been around for hundreds of years at a time when we need them the most. So I look forward to working with the Senator from New Hampshire who has become one of the leading voices when it comes to detention and interrogation under the law of war.
Mr. GRAHAM. Will the Senator yield for a question?
Ms. AYOTTE. Yes, I will.
Mr. GRAHAM. We are throwing around names. I think Zawahiri is the person who took bin Laden's place. If we captured him tomorrow, that would be the ultimate treasure trove.
Ms. AYOTTE. Right.
Mr. GRAHAM. Can the Senator from New Hampshire tell us a little bit about this individual called al-Libi? Why do we believe he would be such a treasure trove? What is his background? How long has he been involved in Al Qaeda? And what have we missed here? What opportunities have we lost by only holding him as an enemy combatant for less than 2 weeks?
Ms. AYOTTE. Mr. al-Libi is someone who is alleged to have been involved in Al Qaeda for decades. He is someone who as early as the 1990s was working with Osama bin Laden. He is alleged to have been involved with--and that is what he is charged with in Federal court, as I mentioned--the 1998 bombings of the Kenya and Tanzania Embassies that killed 224 people, including 12 Americans.
He reportedly played a critical role as the intermediary between al-Zawahiri, whom we just discussed, who took over for Osama bin Laden as the head of Al Qaeda in an effort to establish an Al Qaeda-affiliated operation network in Libya where our Ambassador, of course, was murdered, along with three brave Americans, last September 11. He has been reported to be an Al Qaeda computer intelligence and operations security expert, and he is alleged to have been involved in Al Qaeda strategic planning.
This is one of the most important captures we have had in years of Al Qaeda.
Mr. GRAHAM. Mr. President, if the Senator from New Hampshire will yield for one more inquiry. He was captured in Tripoli, Libya; is that right?
Ms. AYOTTE. Yes.
Mr. GRAHAM. We believe he was in Libya before the attack on our consulate in Benghazi, right?
Ms. AYOTTE. Right.
Mr. GRAHAM. We also know him to be one of the higher level Al Qaeda operatives roaming the planet. He was involved in bombing our Embassies in 1998 in Kenya and Tanzania; is that correct?
Ms. AYOTTE. That is right.
Mr. GRAHAM. What are the odds that he was in Tripoli before the Benghazi attack, had a record of bombing embassies in the 1990s, and had nothing to do with the consulate attack in Benghazi? The Senator from New Hampshire is a prosecutor. What does my colleague think the odds are of this guy not having any knowledge or involvement in killing our Ambassador in Benghazi and being involved in the attack on our consulate that was organized by Al Qaeda affiliates? And what have we learned, if anything, about his potential involvement in Benghazi? How can we learn everything this man has done in 11 or 12 days before we give him a lawyer? I would argue we can't.
The PRESIDING OFFICER. The time of the Senator has expired.
Mr. GRAHAM. I ask unanimous consent for 1 more minute.
The PRESIDING OFFICER. Without objection, it is so ordered.
Ms. AYOTTE. I thank the Chair.
Mr. GRAHAM. Thank you. I would argue we can't possibly understand all he knows about Benghazi in the last 20 years of terrorism by holding him on a ship for less than 2 weeks. He should be held at Gitmo as long as it takes to find out what he knows and then he should be tried. Does the Senator from New Hampshire agree with that?
Source: http://thomas.loc.gov


text:
Jelly Belly Sour Marshmallow Bunnies 8.5oz. (sold out)
Price: $6.20
Please enter your email address below and we will notify you when this item is back in stock.
Sour Bunnies from Jelly Belly. Sour bunny-shaped Easter candies in 6 fruit flavors and spring colors. Great candy for baskets! Fruit in the front, marshmallow in the back and sour all over, these bright little bunnies are a sweet and tangy delight. Their apple, cherry, grape, lemonade, orange and raspberry flavors keep taste buds hopping. 8.5 oz. bag.
Shipping Info


text:
Mummer's Mardi Gras Feb 18
Mummers Mardi Gras is your chance to get up close and personal with some of the finest Mummers – The String Band Association! Join us on Saturday, February 18th, 2017 as we welcome back all 17 String Bands to parade down Main Street in Manayunk. The parade kicks off at 11:00 am and activities continue until 6:00 pm.
The daylong celebration will not only provide excitement for Manayunk but will generate exposure and raise money for one of the greatest and oldest traditions in Philadelphia, the Mummers. This event produces a full day of family-friendly activities such as face painting, photo booths, and much more! Meet the Mummers at their "Clubhouses" for the day and enjoy performances, photo-ops, and food and drink!
Smokin' John's BBQ is an official clubhouse! Smokin' John's will host the Avalon String Band.
Visit http://www.mummersmardigras.com/ for more info.


text:
White Long Sleeved Frill Wrap Bodysuit
Add some flamenco fusion to your new season 'drobe! This ballin' bodysuit in fresh white features a wrap style, frill neck and tie details at the cuffs. Opt for this new piece for an instant babe status.
regular fit - popper fasten at the gusset - tie cuffs
95% Polyester 5% Elastane
Approx length: 69cm/27" (based on a UK size 8 sample)
Vivien wears a UK size 8 / EU size 36 / US size 4 and her height is 5'8"
Product number: TW410566
Machine Washable
You've already saved this to your wish list


text:
My Trackers
my Nutrition
my Fitness
my Weight
Other Goals
my SparkPoints
Community Home
Community Feed
Message Boards
Challenge Central
Member Blogs
What's New
Health & Wellness
Weight Loss
Stuff We Love
Healthy Family
Pregnancy & Postpartum
Instant Inspiration
Food Database
Lifestyle Centers
The SparkPeople Blog
Stream hundreds of free workout videos and track them in one click. Get fit at home, at work or wherever you are!
Today's Featured Video:
Visit SparkPeople.TV
Access hundreds of thousands of recipes that are healthy and easy to make. Get full nutrition info for every recipe and track with one click!
Today's Featured Recipe:
Chili Cheese Fries
Visit SparkRecipes.com
Secrets of Success
Getting Back to Normal
Tuesday, December 04, 2012
Thanksgiving is over. I am back from Alabama where I spent the time with both my girls. We had a wonderful, relaxing long weekend. The traveling took two full days and was a bit long, but so worth it to be with my girls.
I brought my youngest back with me and she spent a week here with me. I was a crazy, busy week but so nice to have her an extra week. She left Sunday night to go back home.
The day after I am without both daughters is always so hard on me. I know to plan to stay busy. So, that I did yesterday. I handled a few stressful problems. The stress level was high, but it kept me from missing my girls too much. I was exhausted by the evening and went to bed early. I slept a little better than I had the previous three nights.
My girls are 32 and 30 - grown with their own busy lives. But I am still the momma - always wanting to be near them and trying to make sure that they are okay and have what they need. My wish is for us to be physically closer, but I know that is not feasible at this time. I have learned to make the most of the time we do spend together. We still keep in contact very regularly through phone calls and emails. Sometimes I just want to be able to give them hugs and kisses...
So now it's time to get back into a routine. I want to make it a little different - to add some activities that are different and keep me a little busier and in contact with more people. Thinking of how I want to do it but don't have definite plans. A get-together of family and friends before Christmas may be something to do. It can be hard to get everyone together but I think it's worth a shot. I will put my thinking cap on today and see what I can come up with.
Share This Post With Others
Report Inappropriate Blog
Member Comments About This Blog Post
Report Inappropriate Comment
My SparkPage
My son is in Germany and I am in California. I totally understand the missing of shared times.
1812 days ago
Report Inappropriate Comment
My SparkPage
Glad you had such a wonderful time with our dd's. Only a wish for me these days...
It was so awesome to go to the Women's Evening at my friend's church last nite, always said I need a Christmas Concert to put me in the mood...
1812 days ago
Report Inappropriate Comment
My SparkPage
1812 days ago
Report Inappropriate Comment
It's hard when your kids live far away. This is so common these days. Getting together with friends is a great idea.
1812 days ago
Add Your Comment to the Blog Post
Log in to post a comment
Disclaimer: Weight loss results will vary from person to person. No individual result should be seen as a typical result of following the SparkPeople program.
Get An Email Alert Each Time
PATTYKLAVER Posts
See Today's Featured Member Blog Posts
More Blogs by PATTYKLAVER
I Feel Like Charlie Brown: ARRRRRRRRGH!!!!!!!!!!!!!!!!!!!!!!!
- 11/15/2017
I Need a Break!
- 11/6/2017
So Over It Already
- 11/2/2017
Toe Update
- 10/26/2017
View All ›
close ×


text:
K G Jose - Director, Rajagiri Business School
Email-ID : firstname.lastname@example.com
A Bachelor in Commerce from Kerala University, Dr.Jose is a quadruple post graduate with First Rank in M.Com from the University of Calicut and doctorate in Social Science from the Cochin University of Science and Technology. He has a teaching experience of over three decades. His areas of interest include Marketing, Human Resource Management, Student Counseling, Communication Skills and Accounting. Prior to his post in Rajagiri, he was the Head of the Post Graduate Department of Commerce and Management Studies at Vimla College, Thrissur (Nationally Accredited with Five Star Status). He is also an approved Ph. D guide for MG University, Bharathiar University, Christ University and Indira Gandhi National Open University in Commerce and Management and a Ph.D. Examiner for eight Universities. He was a member of various academic and professional bodies which include Board of Studies in Commerce of Madras University, Life Member of World Association for Psycho Social Rehabilitation. He is a resource person for various training institutions like Academic Staff College as well as industries for the Government of Kerala; Dr. Jose is the recipient of Dr.M.M.Ghani Award for the Best Teacher of Calicut University for the year 2006-07. He also served as Secretary of Commerce Association of Kerala. He has been a Visiting International Scholar at Nazareth College Rochester, Western Washington University, Columbus State University and the Western Michigan University, Kalamazoo, USA


text:
Fort Sumner District Court 248 E Ave C Fort Sumner NM 88119 21.0 miles from House 575-355-2896
Fort Sumner Magistrate Court 508 Avenue B Fort Sumner NM 88119 22.8 miles from House 575-355-7371
Tucumcari District Court 300 South 3rd Street Tucumcari NM 88401 37.8 miles from House 575-461-2764
Tucumcari Magistrate Court 122 West Center Street Tucumcari NM 88401 37.9 miles from House 575-461-1700
Tucumcari Municipal Court 215 East Center Street Tucumcari NM 88401 37.9 miles from House 575-461-6375
Clovis District Court 700 North Main Street Clovis NM 88101 43.2 miles from House 575-762-9148
Clovis Municipal Court 217 West 4th Street Clovis NM 88101 43.2 miles from House 575-769-7860
Clovis Magistrate Court 221 Pile Street Clovis NM 88101 43.4 miles from House 505-762-3877
Portales Magistrate Court 42427 U.s. 70 Portales NM 88130 45.4 miles from House 575-356-8569
Portales District Court 109 West 1st Street Portales NM 88130 45.4 miles from House 575-359-6920
Portales Municipal Court 520 West 2nd Street Portales NM 88130 45.5 miles from House 575-356-4923
A court is a judicial body charged with resolving violations of a legal right. Judicial courts are created by the government and enforce the law by hearing civil and criminal matters.
Court records are available to the public. Court documents contain valuable information on a range of legal issues, including felony and misdemeanor cases, traffic accident reports, tax court records, and more. Many court records are available online.


text:
[Updated: New stills added] CTV has released stills from the two-hour season finale of "Saving Hope". Check it out!
"Anybody Seen My Baby" (4.17)
Air date: Thursday, Feb. 14 @ 8pm on CTV
Dr. Charlie Harris (Michael Shanks) is shocked to find out that nurse Kristine Fields (Nicole Underhay, MURDOCH MYSTERIES) has had a stroke. After Dr. Alex Reid (Erica Durance) discovers the nurse's past may not be as remembered, she and Charlie must team up to find a way to bring peace to the already troubled spirit. In the ward, Dr. Maggie Lin (Julia Taylor Ross), Dr. Jeremy Bishop (Peter Mooney), and Dr. Cassie Williams (Kim Shaw) treat a transplant-list patient for acute liver failure when it's revealed her symptoms masked a pronounced pregnancy. As complications mount, the doctors must fight an uphill battle to save the life of their patient and her miracle baby. Meanwhile, as the Fellowship Award pitches get underway, Dr. Zach Miller's (Benjamin Ayres) growing relationship with Dawn (Michelle Nolden) is put on the rocks after Maggie delivers some surprising news to Zach.
The 2-hour season finale airs Sunday February 14 at 8pm on CTV.


text: I am just wondering what people in Kentucky are charging per acre and what is their largest account this year. I like to charge about $25-30 an acre. I feel like some people on here get to charge double than that and people around here just can't and won't pay that.


text:
|Publication number
|Publication type
|Application number
|Publication date
|Feb 5, 2002
|Filing date
|Dec 14, 1998
|Priority date
|Dec 14, 1998
|Fee status
|Also published as
|Publication number
|Mark Jarrett
|Original Assignee
|National Railroad Passenger Corporation
|Export Citation
|BiBTeX, EndNote, RefMan
|Patent Citations (27), Non-Patent Citations (8), Referenced by (36), Classifications (7), Legal Events (4)
|External Links: USPTO, USPTO Assignment, Espacenet
The present invention relates generally to systems used for reporting product defects to maintenance personnel and tracking product repairs. More particularly, the invention relates to a paperless system for handling enroute equipment problems and repairs, especially in connection with railway locomotives and cars.
Railway trains consist of one or more locomotives and cars that periodically experience one or more equipment problems while enroute to a destination. For example, on a passenger train, it would not be uncommon for a dining car to have a oven door that is hard to keep closed; a sleeper car in which a bathroom faucet is leaky, or a room in which a light is burned out. In the past, on-board crew personnel identified such problems by completing a written report which was kept permanently in the car and eventually examined (if not otherwise lost or misplaced) by a repairman at a downline maintenance facility when the train reached its final destination. The lengthy reporting process required on-board personnel to spend a considerable amount of time in writing the report, which included providing car ID information, a description and location of the problem, employee information of on-board personnel supplying the written report, etc. Apart from the time factor, report illegibility was also a problem. These written reports necessitated problems for down- line maintenance personnel as well. In addition to attempting to interpret what were often illegible reports, the maintenance personnel had to prepare written reports as well, describing the type of repair made. Often, the problems identified in the on-board personnel generated reports could be acted upon by maintenance personnel until after the locomotive or car departed from the location of the maintenance facility. This necessitated a time intensive search for the locomotive or car in order to identify the next downline maintenance facility at which the repair could be made. The problem of identifying a next-in-line facility was further exacerbated if the locomotive or car was re-assigned to a different train.
It is accordingly one object of the present invention to handle enroute equipment problems and repairs in a paperless process.
Another object of the invention is to enable on-board personnel to report equipment problems using a cellular phone, railphone or regular telephone.
Another object is to enable on-board personnel to describe the problem in their own words in as much detail as warranted without completion of any paperwork.
Still another object is to enable on-board personnel reporting a particular problem to subsequently follow the progress of repair.
Still another object is to enable mechanics to have immediate access to reported problems so that the mechanics can prepare for problems on a train well in advance of arrival.
Still another object is to enable mechanics to call in the repair and describe in detail what was done to fix the problem without necessitating the preparation of a written report by the mechanic.
Yet a further object is to provide an interactive defect reporting system in which the system updates a nationwide master system which keeps track of all trains so that anyone who has access to the master system can identify reported equipment problems for an inbound train or unit.
A further object is to enable the interactive defect reporting system to update itself by accessing current information from the master system in order to identify next-in-line repair facilities to which an inbound train having an unrepaired equipment problem is travelling to.
Yet a further object is to provide an interactive defect reporting system capable of updating repair codes used in the master system so equipment problem histories can be easily generated.
The present invention concerns an interactive defect reporting system for handling enroute equipment problems and repairs in a streamlined paperless process. The system enables on-board train personnel to report equipment problems using a cellular phone, railphone or a regular telephone. After calling the system, the on-board personnel describes the problem in their own words in as much detail as necessary without generating any paperwork. The interactive defect reporting system then assigns a unique 'Trouble Ticket' identification number to the report and this same number is used with respect to all subsequent repairs.
In the preferred embodiment of this system, the Trouble Tickets are immediately available to all downline maintenance facilities such as by facsimile. Preferably, as soon as a Trouble Ticket is generated as a result of a reported equipment problem, a facsimile transmission is automatically generated which identifies that a Trouble Ticket has just been generated for a particular train and unit (i.e., locomotive or car) being identified. The date and time of the report is included with the-faxed information as well as the ticket number and a toll-free or other number that a mechanic or other interested user may contact to obtain information. A mechanic in a downline maintenance facility can immediately listen to the Trouble Ticket and can therefore prepare for problems on the train well in advance of its arrival.
Once a problem is fixed, in whole or in part, the mechanic may call in the repair and describe in detail what was done to fix the problem. The mechanic also determines whether the reported problem is in fact a problem requiring repair. On-board personnel may listen to the repairs or request a fax copy of the Trouble Ticket which the interactive defect reporting system of the present invention sends both immediately and automatically. In this manner, most problems may be fixed within twenty-four hours of the initial report.
The interactive defect reporting system of the present invention is preferably designed to interface with an existing nationwide computerized control system utilized by the assignee of the present invention. This system is known as ARROW/OMS which is utilized to contain all information with respect to all trains and units in the assignee's inventory. The master system also includes a file of OMS repair codes. The interactive defect reporting system of the present invention is preferably linked to update the ARROW/OMS master system so that everyone who has access to the ARROW system can also access the Trouble Ticket numbers for any train or unit. The interactive defect reporting system of the invention preferably also updates the OMS repair codes so that equipment problem histories can be easily generated.
A further feature of the interactive defect reporting system of the present invention is the capability of enabling users of the system to receive written descriptions of the problem reports as well as the repair reports on a Trouble Ticket specific basis. Accordingly, a feature of this invention is the ability of a transcription clerk to listen to the voice message problem report or the repair report, respectively generated by on-board personnel or the mechanic, to enable transcription of the verbal report into a computer stored text message.
Still another feature of the present invention involves the capability of accessing advanced reporting features of the interactive defect reporting system to enable users to obtain very detailed information concerning equipment problems and repairs including, but not limited to:
tickets without responses;
equipment histories by type;
train histories;
facility repair histories;
tickets reported by a specific crew member; and
tickets repaired by a specific mechanic.
Still other objects and advantages of the present invention will become readily apparent to those skilled in this art from the following detailed description, wherein only the preferred embodiments of the invention are shown and described, simply by way of illustration of the best mode contemplated of carrying out the invention. As will be realized, the invention is capable of other and different embodiments, and its several details are capable of modifications in various obvious respects, all without departing from the invention. Accordingly, the drawing and description are to be regarded as illustrative in nature, and not as restrictive.
FIG. 1 is a flow diagram of menu options and events occurring once the interactive defect reporting system of the invention is accessed by telephone;
FIG. 2 is a representative preliminary report automatically generated by the system of the invention for immediate faxing of the existence of a reported problem to a downline repair facility;
FIG. 3 is an illustration of a computer screen visualized by a transcription clerk in order to transcribe reported problems and repairs;
FIG. 4 is an illustration of a computer screen visualized by a transcription clerk after double clicking a ticket number requiring transcription from the screen depicted in FIG. 3;
FIG. 5 is a screen accessed by the transcription clerk in order to transcribe a reported repair message;
FIG. 6 is an illustration of a screen similar to FIG. 4 when there is more than one repair on a Trouble Ticket;
FIG. 7 is an illustration of a screen appearing after the transcription clerk has transcribed all repairs to a ticket and the repairs are now ready to be coded;
FIG. 8 is an illustration of a screen that is accessed by the transcription clerk upon clicking the coding button of FIG. 7;
FIG. 9 is an illustration of a second coding screen that appears to provide specific sub-coding information for a particular coded category;
FIG. 10 is a browser screen;
FIG. 11 is a map representation of open tickets in each of the repair facilities within the system;
FIG. 12 is similar to FIG. 11 with a drop-down report generated as a result of clicking a particular facility in the map of FIG. 11;
FIG. 13 is a computer screen displayed when running the Redirect program of IDRS; and
FIG. 14 is a screen indicating the future locations of units with open or updated Trouble Tickets relative to their current and future locations.
The interactive defect reporting system, generally designated with reference numeral 10 in FIG. 1, is a computerized system for handling enroute equipment problems and repairs. This system 10, also hereinafter identified as "IDRS", is designed as a streamlined paperless process that replaces previously used written paper-based systems that required on-board personnel and maintenance personnel to generate hand-written reports.
IDRS has several significant features:
1. On-board personnel report equipment problems using a cellular phone, a railway phone or a regular phone. After calling the system, on-board personnel describes one or more problems in their own words in as much detail as necessary—all without any paperwork. IDRS automatically assigns a unique Trouble Ticket number to the report and all subsequent repairs.
2. Mechanics listen to the Trouble Tickets or have transcribed copies faxed to their facility.
3. Trouble Tickets are immediately available to all downline maintenance facilities. For example, a Trouble Ticket having the information 12 contained in FIG. 2 can be generated by IDRS immediately upon termination of an equipment problem phone call by on-board personnel. The preliminary report 12 automatically generates the ticket number 14, the train 16 experiencing the problem, the car 18 on the train experiencing the problem, the report date 20 and report time 22. Mechanics can immediately access the telephonic message report and prepare for problems on a train well in advance of its arrival. Alternatively, the mechanics can await transcription of the report into a written text message that can be faxed on demand to the mechanic or other responsible or interested railway personnel.
4. Once a problem is fixed, the mechanics may call in the repair and describe in detail what was done to fix the problem.
5. On-board personnel may listen to the repairs or request a fax copy of the Trouble Ticket which is sent immediately by the IDRS. With this invention, most problems have the capability of being fixed within twenty-four hours of the initial report.
6. IDRS updates the ARROW/OMS system automatically so everyone who has access to ARROW can view the Trouble Ticket numbers for any train or unit. IDRS also automatically updates OMS repair codes so equipment problem histories can be easily generated, as discussed more fully below.
As used in this specification, a Trouble Ticket is intended to mean a unique number which is automatically assigned by IDRS to track the problems reported for each car and locomotive and their subsequent repairs. On-board personnel preferably report all problems they experience for a particular car or locomotive on one Trouble Ticket. It is a highly preferred feature that only one car or locomotive be reported per ticket in order to facilitate proper repairs and tracking of completed repairs. Each ticket also identifies the individual who reported the problem as well as the individual who repaired the problems.
Reporting Problems—On-Board Personnel
Problems are typically reported by on-board crew members utilizing a cellular phone, Railphone, or a regular telephone system. On-board crew members as well as all users of IDRS can access the system by dialing a well publicized toll-free number as depicted, for example, in IDRS access block 24 of FIG. 1.
Therefore, to report problems, on-board personnel would dial the publicized access number and would then immediately hear a main menu providing three or more options. The first option 26 is "If you are an on-board crew member reporting a problem press 1." The on-board crew member would press 1 on the telephone keypad to access the problem reporting section 28 of IDRS.
When accessing the problem reporting section 28, IDRS requests the user to supply their last four digits of the user's social security number (block 30). This information will assist the mechanic or mechanics repairing the problem in contacting the on-board crew member in the event they require additional information. This information also enables the on-board crew member to obtain a copy of all Trouble Tickets they report, as described in further detail below. If the caller is initiating their first call into the system, IDRS also requests the crew member's name and crew base location.
Following receipt of the personal information, IDRS then prompts the caller to "Please enter the unit number for the car or locomotive that you are reporting." This information 32 is entered with the telephone keypad and the entry may be completed by pressing the # sign as is conventional. In the preferred embodiment, it is important to enter the unit number and not the consist number. For railway cars, unit numbers are typically located above the car body end doors. After receipt of the unit number, IDRS reads back the unit number and advises, for confirmation purposes, as to what type of car or locomotive is being reported, e.g., "Superliner Coach" or "P-42 Locomotive". If the information is incorrect, the user may follow the prompts to re-enter this information. IDRS then requests the train number 34. Once this information is obtained, IDRS repeats the train number and, for confirmation purposes, expresses the train number, e.g., "Train Number 58—the city of New Orleans". If the information is incorrect, the user follows the prompts to re-enter this information.
Once IDRS has identified the caller 30, the train 34 and which car or locomotive 32 a problem is being reported for, the IDRS prompts the caller to describe the problem 36 being experienced. In the preferred embodiment, the on-board crew member has up to three minutes (or other predetermined time interval) to describe the problem or problems for each car or locomotive. Preferably, the on-board crew member can report as many problems as exists with respect to a single piece of equipment within the context of a single Trouble Ticket. However, in the event one or more on-board crew members are reporting problems in different cars or locomotives, the caller will preferably use a separate Trouble Ticket for each car or locomotive being reported.
Upon completion of description of all problems 36 associated with a particular car or locomotive 32, the user preferably presses any key at which time IDRS provides the following prompt: "Do you have any other problems to report?". If the answer is NO, IDRS provides the caller with the Trouble Ticket number for the problem(s) reported. If there are no further equipment problems to be reported, the user terminates the call by hanging up. Otherwise, the user is prompted to return to step 2 and enter the car or locomotive number of the next car being reported in order to provide the information requested in steps 2-4, i.e., information blocks 32-36.
Once the user hangs up, IDRS provides the Trouble Ticket to the next or all downline maintenance facilities immediately. The Trouble Ticket has the form 12 set forth in FIG. 2.
Generally, the on-board crew member reporting a problem can expect a response within twenty-four hours after the train arrives at its final destination. The user may contact IDRS and listen to the repair response, described more fully below, or have a copy faxed immediately via the Fax on Demand feature described below. To listen to repairs made to equipment reported, the user contacts IDRS and selects Option 2 (block 38) to check on ticket information. IDRS will prompt the caller to listen to the ticket information or have the ticket information faxed immediately.
If the caller elects to listen to ticket information (block 40), IDRS prompts the caller to enter the ticket number (block 42) assigned by IDRS to a particular problem(s) and car. In this manner, IDRS retrieves the ticket information from storage and plays both the defect that was reported and the repair that was made. IDRS is also capable of providing the caller with information as to who repaired the problem, the date the repairs were made and where the repairs were performed.
In the alternative, the aforementioned ticket information may be faxed to the caller (see block 44). IDRS prompts the caller to provide their fax machine number 46 and then automatically faxes the above-identified information typically within five minutes.
Utilizing advanced reporting features discussed more fully below, the caller can also request a copy of all Trouble Tickets the caller may have reported, or tickets reported for a specific car, locomotive or train.
Reporting Repairs—(Mechanics)
As mentioned above and with reference to FIG. 2, a facsimile message 12 is generated immediately upon receipt of a problem reported by a crew member to IDRS under Option 1. The facsimile message 12 may have the form and contents set forth in FIG. 2. By interfacing with the ARROW system, IDRS is capable of identifying the next downline repair facility, or all downline facilities, for purposes of faxing the problem notification of FIG. 2 to an appropriate mechanic.
The mechanic accesses IDRS by dialing the general access number 24 set forth in FIG. 1 and then selecting the appropriate prompt from the menu. In this case, the mechanic would select Option 2 (block 38) to listen to ticket information 40 or have the information sent via facsimile 44. To be effective, the information sent via facsimile 44 is preferably available once the recorded information has been transcribed in the manner described below. Otherwise, by selecting Option 1 under the retrieve ticket information menu, the user may listen to the problems recorded either specifically by Trouble Ticket number, unit number or train number. In this manner, appropriate repair personnel can obtain information about problems on all trains enroute to their facility.
From the above, it will be appreciated that IDRS provides a number of methods for repair personnel to obtain reported ticket numbers and the problems they represent. Whenever a problem report is called in, as discussed above, IDRS automatically faxes an alert sheet having the form depicted in FIG. 2 to the downline facility. The alert sheet 12 states the ticket number, unit reported, train on which that unit is travelling and the date and time the problem was reported. This information is train specific so that mechanics will not receive these notifications if the train is not travelling to their facility. The mechanic can use these alert sheets 12 to access specific tickets or obtain Trouble Ticket information by unit, train or by destination facility by calling IDRS and requesting information as discussed in more detail below.
By selecting Option 2 as described above in connection with FIG. 1, IDRS plays the "retrieve ticket information" menu 48 and prompts the user to either listen to ticket information 40 or have the information 44 faxed to the downline maintenance facility. To listen to ticket information, as mentioned above, the user may choose Option 1 and IDRS then prompts the user with a short series of choices that allows the user to listen to a specific ticket, all tickets for car or locomotive, all tickets reported for a specific train, or all tickets for all trains that are arriving at the mechanic's facility.
If the mechanic already has the ticket number and wants to listen to the problem reported, IDRS prompts the mechanic to "Enter the ticket number, then press the # key." The mechanic then enters the ticket number they wish to hear, presses the # key and IDRS then plays the reported problem along with car or locomotive number, and the date and time the problem was reported.
If the mechanic wishes to listen to all tickets for a car or locomotive, IDRS prompts the mechanic to "Enter the car or locomotive number, then press the # key." The mechanic then enters this information, presses the # key, and IDRS then plays a list of all of the ticket numbers for the unit chosen. The mechanic may listen to a report for a specific ticket while his list of ticket numbers is being played by pressing the * key once the mechanic hears the number of the desired ticket.
In addition to enabling the user to listen to all tickets for a car or locomotive, IDRS also allows the user to obtain all reports for a specific train. If this information is requested, IDRS prompts the user to "Enter the train number, then press the # key." After entering the train number, IDRS plays a list of all open Trouble Tickets for this train. As with tickets for a specific unit, the user may press the * key to hear the full IDRS report after hearing the number of the ticket to be selected.
IDRS also advantageously enables the user to listen to all tickets 50 for all trains coming to a particular maintenance facility. IDRS requests the user to enter the facility code. In most cases, this code is a three letter ARROW city code for the city in which the facility is located, such as representatively set forth in Table 1 below.
Maintenance Facility
City Code
Los Angeles
New Orleans
New York
San Antonio
Washington, D.C.
In addition to providing the actual recorded problem, IDRS can also send the same information to the user's fax machine. This feature, called Fax on Demand, provides a printed copy (when available) of all IDRS information requested by the user. To retrieve IDRS information using Fax on Demand, the user selects Option 2 (block 44) from the Retrieve Ticket Information Menu 48 as depicted in FIG. 1. After selecting the Fax on Demand Option 2, the user can select the information they want to have faxed in the same manner as if they were going to listen to the information, as described in detail above. Once the user makes their selection, IDRS prompts the user for their fax number 46. IDRS will then typically fax the requested information within five minutes. In the event that requested information is not transcribed and therefore unavailable in written form for faxing, IDRS has the capability of faxing the user a message which informs the user to contact IDRS and listen to the recorded information in the manner described above.
Irrespective of whether the user chooses to listen to the recorded problem message 40, or receive a written transcription 44 thereof, in either option the information is provided to the user in the exact words of the crew member that reported the problem. This type of detailed, accurate information should significantly aid the mechanic in their diagnosis and repair of the problem. In addition, as mentioned above, the mechanic can obtain identification of the crew member who reported the problem in the event that further information is necessary by contacting the crew member.
Once the mechanic has retrieved the IDRS ticket information and has taken the action to correct the problem, IDRS advantageously enables the mechanic to contact IDRS at the general number 24 to report the repair. This information enables IDRS to close the ticket and provide a copy to the crew member that reported the problem, as well as other interested IDRS users.
To report the repair, the mechanic contacts IDRS at the general number 24 and selects Option 3 (block 52) from the main menu. IDRS prompts the mechanic for the last four digit of their social security number 54, their name and maintenance facility (only on the mechanic's first call), the ticket number 56, the unit that was repaired and a verbal description 58 of the repair. Preferably, IDRS is designed to allow the mechanic up to three minutes per ticket to describe all repairs made to a particular car. The mechanic's response is available to the on-board crew member that reported the problem. IDRS may be equipped to provide the on-board crew member with an automatic fax copy of the repair report once the report has been transcribed.
Once the mechanic finishes describing the repair, any key may be pressed to enable the mechanic to describe repairs made with respect to other Trouble Tickets and to repeat the process for reporting repairs until no other ticketed repairs exist. The mechanic may then hang up.
Advanced Options
Advanced reporting options are available through IDRS. Advanced options include a number of reports that are available through Fax on Demand. To access the advanced options section of IDRS, Option 4 (block 60) is selected from the main menu.
Once Option 4 has been selected, the advanced reporting feature of IDRS allows the user to obtain very detailed information about equipment problems and repairs including:
tickets without responses;
equipment histories by type of car (e.g., all Viewliners);
train histories;
facility repair histories;
tickets reported by a specific crew member;
tickets repaired by a specific mechanic.
Each available report preferably has a report number which the user must select to have that report faxed. Table 2 below contains the report numbers of the available reports to IDRS users.
IDRS Advanced Reporting Options
Document Index
Page 1 of 1
Tickets Without Responses (facility)
Equipment History per Equipment Type
last 30 days
last 30 days
last 90 days
last 90 days
past half year (182 days)
past half year (182 days)
past year (365 days)
past year (365 days)
past 2 years (730 days)
past 2 years (730 days)
Train History
Unit History
last 30 days
last 30 days
last 90 days
last 90 days
past half year (182 days)
past half year (182 days)
past year (365 days)
past year (355 days)
past 2 years (730 days)
past 2 years (730 days)
Tickets Reported By Crew Member
Tickets Repaired By Mechanic
last 30 days
last 30 days
last 90 days
last 90 days
past half year (182 days)
past half year (182 days)
past year (365 days)
past year (365 days)
past 2 years (730 days)
past 2 years (730 days)
Facility Repair History ( *** REPORT NOT YET AVAILABLE *** )
In addition to Report Code, you will be voice prompted to enter
facility code, train, unit, equipment type, or social security numbers
where appropriate.
Up to 5 documents may be requested per telephone call to IDRS at 1-800-475-9158.
Equipment Type Codes (for use with Equipment History Reports)
Type or General Type
Type or General Type
Superliner I (all types)
Superliner I Sleepers
Food Service (Horizon)
Superliner I Lounge
Food Service HCDP (Horizon)
Superliner I Coach
Coach (Horizon)
Superliner I Deluxe Sleeper
Coach HDCP (Horizon)
Superliner I Snack Coach
Viewliner (all types)
Superliner I Diner
Viewliner Sleeper
Superliner I Coach/Bag
Viewliner Diner
Superliner I Trans Dorm
Cab Car (Amfleet)
Cab Car Conference (Amfleet)
Cab Car Regular (Amfleet)
AmCafe II
AmCoach II
To obtain the current catalog of available reports, the user may select Option 1 from the Advanced Options Menu. IDRS will prompt the user to enter the number of the fax machine where the user requests the information to be sent. IDRS is also capable to sending the catalog of available reports (Table 2) to the user by facsimile. Once the user receives the catalog of current reports, the user can then choose a report to be faxed by first selecting Option 2 from the Advanced Reporting Options Menu. IDRS will prompt the user to enter the report number they wish, followed by the # sign. IDRS then prompts the user to enter the fax number where the user wishes the report to be sent. Typically, IDRS will send the requested report within five minutes.
Table 3 below is a representative advanced report which identifies tickets reported by train number and unit number. The first column identifies the Trouble Ticket number. The second column identifies the unit number within a specific train. The third column identifies the date the problem was reported. The fourth column identifies the number of days since the problem was reported and the fifth column represents the status of each ticket.
Open tickets for Chicago
Days open
Train 3
Train 4
Train 5
Train 6
Transcription of Reported Problems and Repairs
As discussed above, an important feature of IDRS resides in the ability to transcribe problem reports and repair tickets, Transcription of the problem reports and the repair tickets helps the fleet provider maintain a more reliable fleet on the road. Since the IDRS is preferably a computer based system (e.g., utilizing an OS/2 operating system in combination with a WINDOWS NT platform), the transcription clerk or clerks will initially access the IDRS transcription program by double clicking an appropriate icon.
Upon accessing the transcription program, the clerk will initially see a first screen 61 such as depicted in FIG. 3. The first lefthand column 62 is entitled "Ticket" and the second column 64 bearing the legend "Typed" advises the transcription clerk whether the associated ticket number in the first column has been transcribed. If the column has a YES in it, then a problem report has already been transcribed. If the column has a NO in it, then a problem report needs to be transcribed. Preferably, but not necessarily, this information can also be provided by highlighting the ticket number in a color different from ticket numbers that have already been transcribed.
The third and fourth columns 66 and 68 are self explanatory. They provide the viewer with train and car identification information.
The date column 70 indicates the date a particular Trouble Ticket report was generated. In accordance with a unique feature of the invention, the pull-down bar 72 in the date column enables the transcription clerk or user to view tickets in other months.
The status column 74 advises whether the ticket is open (O) or updated (U). Closed tickets preferably are not depicted in this screen 61.
The ticket repair column 76 preferably has one of three entries. One entry is NO indicating that no mechanic has responded to this ticket and that the ticket is in a state of investigation. It is important to note that in IDRS, a problem report is not a defect until a mechanic determines whether a defect really exists. The second entry in this field is YES meaning that the repair has been typed and is awaiting investigation to determine why the ticket has not been closed. If the ticket has been completed and all repairs to the problem report have been made, the ticket will disappear from this screen. It is also possible that a condition may exist wherein all repairs have not been performed. In this case, the ticket remains in the updated status (third entry type)
The last column or code column 78 indicates whether the ticket has been OMS coded. This is only active on repairs that have already been made.
FIG. 4 is an illustration of a screen 80 visualized by the transcription clerk after double clicking a ticket number 62 requiring transcription from the screen 61 depicted in FIG. 3. On the lefthand side of the screen 80 is an open area 82 to be used for the actual typing of exactly what is said by the on-board crew member rendering the problem report. The area "Available Tickets" 84 indicates the repair tickets requiring transcription. The three columns inside the Available Tickets area are respectively the ticket number, the type of ticket it is, and whether the ticket has been typed.
To activate the "Message Player" 86 on the far right of the screen 80, the transcription clerk double clicks the ticket number appearing in the Available Tickets area 84. Preferably, the ticket is highlight in red or a different color to indicate that it requires transcription.
The Message Player section 86 includes five buttons typical to that of a regular tape player. By double clicking one of these buttons, the transcription clerk can either listen to the on-board crew member describing a defect or, if the mechanic has already rendered a verbal repair report, to the mechanic that repaired the defect. The first button (which may also be actuated by pressing the F5 key located below this bottom on the transcription clerk's keyboard) enables the clerk to back up the message in order to hear it from the beginning. The second button (F6) is the play button. This plays the message beginning from where the clerk has previously stopped the message. The pause button (F7) will pause the message to enable the transcription clerk to catch up while transcribing. The next button (F8) allows the transcription clerk to rewind the last few seconds of the message just played. This button enables the transcription clerk to hear words or phrases that are difficult to understand. The last button is the skip forward button (F9) which enables the transcription clerk to skip forward in the message a few seconds. This allows the transcription clerk to hear parts of a message instead of listening to the entire message.
After the transcription clerk has typed the problem report, the clerk clicks the Done button. In the available ticket area, the identifier in the Type column will change from NO to YES indicating that the reported message has been typed. The Exit button enables the transcription clerk to return to the screen 80 of FIG. 3.
FIG. 5 is a screen 90 accessed by the transcription clerk in order to transcribe a reported repair message and to code the tickets for the OMS program which monitors maintenance and repairs in the ARROW system.
In the Available Tickets section 92, the second line 94 has the same ticket number as the first line and in the adjacent Type window, the designation has been changed to Repair. The Typed column indicates NO which means that a repair message has been recorded but not transcribed. To transcribe the repair message, the transcription clerk follows the same instructions used to transcribe problem reports as discussed in detail above. The repair recording is accessed by double clicking the ticket number appearing in the second line to activate the Message Player.
FIG. 6 is an illustration of a screen 99 similar to FIG. 4 indicating that there may be more than one repair on a ticket. The second line of the Available Tickets area 102 awaits transcription while the third line indicates a repair under the same ticket number (i.e., in the same locomotive or car) that has already been transcribed. FIG. 6 therefore illustrates the occurrence of multiple repairs on one ticket. Each repair must be transcribed in the manner specified above.
The arrow 100 denotes a check box 104 at the bottom of the lefthand side of the screen 99 bearing the legend (not shown in detail) "Check here if nothing was done in the repair section." This box 104 is checked by the transcription clerk if the intent is to leave the ticket in an updated status and it is desired not to close the ticket. In the example of FIG. 6 in which one repair has been transcribed and the other repair has not, the box 100 must have been previously checked by the transcription clerk in order to access the screen of FIG. 6. If the transcription clerk forgets to check box 100 or wishes to close the ticket, as soon as the clerk presses the Exit button, IDRS will automatically close this ticket. However, IDRS will alert the transcription clerk that it is closing the ticket before actual closure.
FIG. 7 is an illustration of a screen 110 after the transcription clerk has transcribed all repairs to a ticket. At this point, the repairs are ready to code and the Code button is now black to indicate that this button may be actuated in order to access the coding screen 120 depicted in FIG. 8.
In the top lefthand corner of the coding screen 120, there is displayed the ticket number, followed by the train, unit and type. The repair report from FIG. 7 now appears in the top right area of the coding screen 120. In the area in the lefthand side of the screen 120 is a description of the list 122 of codes that must be selected by the transcription clerk. For example, in order to code the repair "Shower Light Repaired" depicted in the reported repair transcription box 124, the transcription clerk would highlight the designation "Electrical" as denoted with arrow 124 since all lights, for example, are coded in "Electrical".
Still with reference to the example being discussed above, with reference now to FIG. 9, the second coding screen 130 under the designation "Electrical" is now displayed with respect to the "Shower Light Repaired" problem and repair. The transcription clerk will highlight the designation "Light-Ceiling" identified by arrow 134. By clicking this designation, the description of the selected defect immediately appears in the "Selected Defect Descriptions" area 136 in the lower righthand corner of the screen 130.
The transcription clerk essentially codes by highlighting the specific repairs in sequential order, beginning at the top of the list 125 in FIG. 8, until all repairs have been coded in the manner described above. At that point, the transcription clerk will click the "OK" button 127 and will be returned to FIG. 7. Upon being returned to the screen 110 of FIG. 7, the transcription clerk may close the ticket by clicking the Exit button as mentioned above. To prevent inadvertent ticket closures, any ticket which has not yet been coded will still be highlighted in red. Preferably, the transcription clerk will check these areas to ensure complete transcription before closing the ticket.
The IDRS Browser
FIG. 10 is an illustration of the main screen 150 of the IDRS browser. In the upper lefthand corner, the open file cabinet 152 indicates that the ticket numbers displayed are open tickets. The second file cabinet 154 with a hand filing a record is the updated ticket file. The third file cabinet 156 with the closed drawers is the closed ticket file. An updated ticket indicates that a repair has been made on a ticket but has not yet been completed. All tickets are filed in one of these drawers 152-156, irrespective of whether they have been transcribed.
The train locations area 158 has a drop down menu of all repair facilities that receive trains. By highlighting one of these repair facility locations, all ticket numbers of trains enroute to that area may be displayed.
Push button 160 allows the user to search for specific ticket numbers. Push button 170 allows the user to browse for ticket numbers associated with a specific train.
Push button 180 allows the user to browse for a specific car or locomotive. Advantageously, this information is cross-referenced.
The dates field 182 allows the user to browse for ticket numbers that came in on the present date in question, all tickets up to the present date, all tickets for the month, and all tickets for the year. Depending on which of the fields is highlighted, the total number of relevant tickets appears at the bottom of this field 182 (e.g., 195 tickets in the illustrated drawing).
In the upper righthand corner of the screen 150 depicted in FIG. 10, there is a calendar 184 which obviously allows the user to select specific months and dates to obtain relevant ticketing information.
In the lower lefthand section 186 of the browser screen, there is an identification of the problem that has been reported by an on-board crew member. If the problem has already been transcribed, then the transcription appears in the section 186 of this screen. The loudspeaker icon 187 enables the user to listen to the problem in the reporting crew member's own words and appropriate play button icons 188 appear in this section of the screen 150 as depicted in the drawing figure.
At the bottom of the browser depicted in FIG. 10, there is a Map button 190. By clicking the Map button 190, a map 200 of the United States appears as depicted in FIG. 11 and the total number of open tickets is displayed for both locomotives and cars. In addition, the number of open tickets destined by each downline repair facility is displayed and the number of repair responses made since the previous day, for example, is also identified. If the user wishes to obtain specific information for a particular repair facility, the user simply double clicks the facility name at which time all open tickets are displayed as an overlay on the screen as depicted in FIG. 12. It is to be noted that the open tickets being displayed also include updated tickets in which some but not all repairs have been made.
Redirection Program
Since the fleet is in continuous daily use, a highly preferred and key feature of the present invention is the Redirect Program which has the capability of automatically accessing the ARROW system (see FIG. 13) in order to automatically update the open tickets (including the updated tickets) to identify the new or future location of a unit when it leaves its current location. FIG. 14 is an illustration of a screen 300 which may be displayed after the Redirect Program is run to indicate the current and future location of each open ticket by accessing the information in the ARROW system. The redirect software is preferably run three times a day so that each of three maintenance or repair shifts can have updated and therefore current information with respect to inbound trains and units having open tickets.
Within the fleet, it is common for units to be associated with the same train number. However, in the event a particular unit (i.e., car) becomes a part of a different train, the redirect software will advantageously identify the new train number as a result of interfacing with the ARROW system.
From the foregoing description, it will become apparent that IDRS has four programs associated with it:
the main program;
the transcription program;
the browser program;
and the redirect program.
With the exception of the Fax on Demand feature in which downline facilities must be identified for automatic receipt of a facsimile after a problem is immediately reported, or to run the Redirect program, both of which features require access to the ARROW system, the other programs and features of IDRS are capable of operation and data storage without access to the ARROW system.
It is to be understood that the Redirect program updates the open tickets automatically on a daily or thrice daily basis. However, the Redirect program may be operated in a manual mode by depressing the Start button appearing in the screen depicted in FIG. 14. After the Redirect program is operated, the redirect information in that screen may be automatically sent via facsimile to the new downline repair locations by clicking the Send button.
As mentioned briefly above, the main IDRS program runs on, for example, on OS/2 IBM operating system which stores the operating files described above. This operating system can run, for example, on a 200 MHz MMX computer preferably equipped with 196 megabytes of RAM with a 500 gigabyte hard drive. The operating system is linked directly to a similar computer system equipped with a ten megabyte hard drive to store the IDRS data files for use in conjunction with a Windows NT box. The Browser and Redirect programs identified above may be Visual Basic programs and a fourth program is a SYS PROD program which establishes a main frame connector link to access the ARROW/OMS system in order to upload and download information between IDRS and ARROW.
As also mentioned above, the ARROW system is an existing nationwide system used by Amtrak which contains train information, car information, ticket reservation information, unit maintenance and repair information, etc.
In view of the foregoing detailed description of both the IDRS programs and the interface requirements with the ARROW/OMS system, programmers of ordinary skill in the art will be able to develop the necessary software creating the data storage files used to achieve the functions described in detail hereinabove with respect to each of the four main programs.
It will now also be appreciated by persons skilled in the art that IDRS may be modified to report and track problems and repairs with respect to virtually any type of fleet other than railway cars, such as passenger and cargo delivery systems as may occur with the use of trucks, buses, taxis, aircraft, etc. With respect to each of these passenger and cargo delivery systems, it is to be understood that an IDRS type of system may be programmed to operate and be linked with an existing and possibly online nationwide system associated with the particular delivery system that allows for storage and tracking of basic information peculiar to fleet operation within that industry.
As mentioned briefly above, the operating system side of IDRS preferably includes a plurality of separate voice and fax lines to enable the system of users to report problems and repairs and request fax information as identified above. The operation system preferably includes software to display online the actual use of the voice and fax lines in real time.
As also mentioned above, it is also a preferred feature of this invention to generate one Trouble Ticket per car in which all problems associated with that car are reported on the specific ticket. This facilitates tracking and eventual repair of any one car. The purpose of coding the repairs is to create an OKI (okay for inspection) entry in the ARROW system to allow users to track in ARROW after the repair is made. The coding entries also enables audit of and cost of repairs being tracked. The repairs are coded only after completion. If no defect is found by a mechanic in response to a particular problem reported, there will be entered an entry item termed "No Action Required".
It is to be further understood that IDRS lends itself to the fact that different downline facilities may make different repairs at different times to a car until all repairs have been made and a ticket can be closed.
It will be readily seen by one of ordinary skill in the art that the present invention fulfills all of the objects set forth above. After reading the foregoing specification, one of ordinary skill will be able to effect various changes, substitutions of equivalents and various other aspects of the invention as broadly disclosed herein. It is therefore intended that the protection granted hereon be limited only by the definition contained in the appended claims and equivalents thereof.
|Cited Patent
|Filing date
|Publication date
|Feb 21, 1989
|Apr 2, 1991
|Fuji Jukogyo Kabushiki Kaisha
|Diagnosis system for a motor vehicle
|Jan 30, 1991
|May 25, 1993
|Edge Diagnostic Systems
|Interactive diagnostic system for an automotive vehicle, and method
|May 29, 1991
|Mar 22, 1994
|Alcatel N.V.
|Wireless telephone network centralized maintenance method
|May 12, 1993
|May 17, 1994
|Ford Motor Company
|Method and apparatus for diagnosing engine and/or vehicle system faults based on vehicle operating or drive symptoms
|Jan 25, 1994
|Dec 27, 1994
|Cellular Communications Corporation
|Apparatus and method for a cellular freeway emergency telephone
|Aug 26, 1993
|Feb 7, 1995
|Nippondenso Co., Ltd.
|Self-diagnostic apparatus of vehicles
|Nov 16, 1992
|Aug 15, 1995
|Wireless motor vehicle diagnostic and software upgrade system
|Sep 16, 1992
|Sep 26, 1995
|Caterpillar Inc.
|Computerized diagnostic and monitoring system
|Jun 14, 1994
|Dec 26, 1995
|Nippondenso Co., Ltd.
|Vehicle diagnosis system
|Apr 10, 1995
|Nov 5, 1996
|Ford Motor Company
|Vehicular emergency message system
|Aug 8, 1995
|May 20, 1997
|Spx Corporation
|Diagnosis method for vehicle systems
|Aug 12, 1994
|Jun 24, 1997
|Caterpillar Inc.
|Maintenance monitor system
|Oct 27, 1994
|Jul 8, 1997
|General Motors Corporation
|Automotive diagnostic communications
|Feb 22, 1996
|Dec 9, 1997
|Nippondenso Co., Ltd.
|Self-diagnosis apparatus for vehicles
|Jun 7, 1995
|Sep 15, 1998
|Automotive Technologies International, Inc.
|On board vehicle diagnostic module using pattern recognition
|Jul 16, 1997
|Sep 7, 1999
|Harness System Technologies Research, Ltd.
|Vehicle communication control apparatus
|Jan 31, 1997
|Dec 21, 1999
|Honda Giken Kogyo Kabushiki Kaisha
|Method and apparatus for diagnosing a vehicle
|Mar 15, 1999
|Jul 25, 2000
|Hewlett-Packard Company
|Modular wireless diagnostic, test, and information
|Oct 3, 1996
|Sep 5, 2000
|Ab Volvo
|Diagnostic system particularly for an engine management system
|May 18, 1993
|Dec 8, 1993
|Aircraft Technical Publishers
|Computer aided maintenance and repair information system for equipment subject to regulatory compliance
|Mar 31, 1994
|Oct 4, 1995
|Zucker, JoAnn
|Method of using telephone system to transmit certified messages
|Nov 5, 1997
|Jun 3, 1998
|Boston Technology Inc.
|A system for accessing multimedia mailboxes and messages over the internet and via telephone
|Title not available
|Title not available
|Title not available
|Title not available
|Title not available
|"No more Paper Orders with Mobile Data Software"-Electrical World-Dec., 1996-p48 vol. 210 No. 12.*
|"Service Fleet Management Practices" Newton, C Transmission & Distribution World-v8n8 Aug. 1996.*
|"No more Paper Orders with Mobile Data Software"—Electrical World—Dec., 1996—p48 vol. 210 No. 12.*
|"Service Fleet Management Practices" Newton, C Transmission & Distribution World—v8n8 Aug. 1996.*
|Patent Abstract of Japan. vol. 1998, No. 8, Jun. 30 ,1998 & JP 10 076052 A (Toshiba Corp), Mar. 24, 1998 abstract.
|Patent Abstracts of Japan. vol. 016, No. 412 (E-1256), Aug. 31, 1992 & JP 04 137851 A (matsushita Electric Ind Co Ltd), May 12, 1992 abstract.
|Patent Abstracts of Japan. vol. 1998, No. 09, Jul. 31, 1998 & JP 10 108277 A (Toshiba Eng Co Ltd), Apr. 24, 1998 abstract.
|Patent Abstracts of Japan. vol. 1998, No. 13, Nov. 30, 1998 & JP 10 2225654 A (Hitachi Building Syst Co Ltd), Aug. 21, 1998 abstract.
|Citing Patent
|Filing date
|Publication date
|Nov 19, 1999
|Apr 1, 2003
|General Electric Company
|Process and system for configuring repair codes for diagnostics of machine malfunctions
|Sep 30, 2002
|Oct 26, 2004
|General Electric Company
|Method for identifying a loss of utilization of mobile assets
|Jul 10, 2001
|Apr 26, 2005
|General Electric Company
|Method and system for tracking repair of components
|Aug 14, 2002
|Jan 10, 2006
|Ford Motor Company
|Computer-implemented method and system for attributing applicable condition codes to field claims
|Jul 31, 2002
|Jan 31, 2006
|General Electric Company
|Method and system for monitoring problem resolution of a machine
|Oct 17, 2003
|Mar 14, 2006
|General Electric Company
|Apparatus and method for performance and fault data analysis
|Apr 19, 2001
|Aug 15, 2006
|Koninklijke Philips Electronics N.V.
|Method and apparatus for removing defects in an image sequence
|Sep 21, 2004
|Nov 28, 2006
|International Business Machines Corporation
|Adaptive message delivery system
|Nov 7, 2001
|Sep 4, 2007
|Sparta Systems, Inc.
|Graphical user interface for automated process control
|Aug 5, 2002
|Feb 19, 2008
|Todd E. Vander Hill
|Digital design and maintenance system and method
|Feb 13, 2002
|Dec 1, 2009
|General Electric Railcar Services Corporation
|Railcar condition inspection database
|Aug 27, 2007
|Oct 11, 2011
|Red Hat, Inc.
|Systems and methods for linking an issue with an entry in a knowledgebase
|May 31, 2007
|Sep 11, 2012
|Red Hat, Inc.
|Systems and methods for directed forums
|May 31, 2007
|Jan 15, 2013
|Red Hat, Inc.
|Systems and methods for improved forums
|Jan 20, 2009
|Feb 26, 2013
|General Electric Company
|Locomotive assistant
|Sep 14, 2012
|Aug 12, 2014
|At&T Intellectual Property I, L.P.
|Method and apparatus for processing of a toll free call service alarm
|Dec 7, 2012
|Aug 25, 2015
|At&T Intellectual Property I, L.P.
|Method and apparatus for providing automated processing of a switched voice service alarm
|Apr 19, 2001
|Oct 24, 2002
|Philips Electronics North America Corp.
|Method and apparatus for remooving defects in an image sequence
|Feb 13, 2002
|Dec 12, 2002
|William Eugene Moser
|Railcar condition inspection database
|Jul 10, 2001
|Jan 16, 2003
|Olle Michael S.
|Method and system for tracking repair of components
|Aug 5, 2002
|Feb 5, 2004
|Hill Todd Vander
|Digital design and maintenance system and method
|Jul 31, 2002
|Feb 5, 2004
|Roddy Nicholas Edward
|Method and system for monitoring problem resolution of a machine
|Aug 14, 2002
|Feb 19, 2004
|Zambo Donald James
|Computer-implemented method and system for attributing applicable condition codes to field claims
|Sep 30, 2002
|Apr 1, 2004
|Jammu Vinay Bhaskar
|Method for identifying a loss of utilization of mobile assets
|Oct 17, 2003
|Jul 22, 2004
|Hedlund Eric H.
|Apparatus and method for performance and fault data analysis
|May 14, 2004
|Feb 9, 2006
|Mathur Harish C
|Deferred method of sending information
|Sep 21, 2004
|Mar 23, 2006
|Fisher James A
|Adaptive message delivery system
|Jun 16, 2006
|Dec 20, 2007
|Sikorsky Aircraft Corporation
|Supplier teardown & analysis reporting system
|May 31, 2007
|Dec 4, 2008
|Hibbets Jason S
|Systems and methods for improved forums
|May 31, 2007
|Dec 4, 2008
|Mattox John R
|Systems and methods for directed forums
|Aug 27, 2007
|Mar 5, 2009
|Hibbets Jason S
|Systems and methods for linking an issue with an entry in a knowledgebase
|Jan 20, 2009
|Jul 22, 2010
|Todd Goodermuth
|Locomotive Assistant
|Aug 20, 2009
|Feb 24, 2011
|Verizon Patent And Licensing Inc.
|Method and system for trouble ticket creation using templates
|Sep 14, 2012
|Jan 10, 2013
|At&T Intellectual Property I, L.P.
|Method and apparatus for processing of a toll free call service alarm
|Jul 8, 2011
|Jul 4, 2013
|Juan A. Paz Salgado
|System and method of diagnosis of incidents and technical support regarding communication services
|Jul 24, 2006
|Jan 31, 2008
|Siemens Ag
|Method for displaying diagnostic data on image surface of display screen in drivers cab of rail car, involves displaying diagnostic data as text in one area, and components status of rail car is displayed as graphics in another area
|U.S. Classification
|International Classification
|Cooperative Classification
|European Classification
|Mar 11, 1999
Owner name: NATIONAL RAILROAD PASSENGER CORPORATION, DISTRICT
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:JARRETT, MARK;REEL/FRAME:009810/0029
Effective date: 19990208
|Aug 24, 2005
|Maintenance fee reminder mailed
|Feb 6, 2006
|Lapse for failure to pay maintenance fees
|Apr 4, 2006
|Expired due to failure to pay maintenance fee
Effective date: 20060205


text:
Two civil rights groups called for a federal investigation into a Jindal administration program that they allege is failing to deliver on promised services to keep at-risk youth with mental health problems out of detention centers and hospitals.
In response, the state health chief acknowledged Wednesday that there are "challenges" in getting providers to meet the specialized needs of the youth and their families, but said the administration remains committed to the program.
The Southern Poverty Law Center and the Advocacy Center complained to the federal Centers for Medicare and Medicaid Services, called CMS, about shortcomings of the program that attorneys claim violate federal law.
Gov. Bobby Jindal launched the Coordinated System of Care amid much fanfare in early 2012 as a way to help children and youth up to age 21 stay out of institutions. The program is supposed to provide short-term respite care, crisis stabilization as well as family and youth support services that allow those at risk to remain in their homes and communities.
The program has been operating in five regions of the state, including the Baton Rouge and New Orleans areas, with the potential for helping 1,200 children and youth. CMS recently approved expansion of the program statewide, which would bring capacity to 2,400.
"It just really hasn't lived up to the promise," Advocacy Center lawyer Nell Hahn said Wednesday. "It looks good on paper and people were really excited about it … but there are such serious gaps in failing to give people services in their homes and communities."
Hahn said the state Department of Health and Hospitals hasn't developed the provider network necessary to support the program — more than two years since its implementation.
State Department of Health and Hospitals Secretary Kathy Kliebert said the state has struggled to get the providers necessary to deliver the services, which had not been offered in the past.
"We have raised rates," Kliebert said. And Magellan — the private company coordinating mental health care — has tried to recruit providers, she said.
"But they just don't feel comfortable at this point taking on new services," Kliebert said. "We do believe we will eventually get there. We have got the right structure, the right service model and services, but we don't have the providers to get there. That's been a big challenge for us."
Kliebert said the state still has the same goal of keeping the at-risk children and youth out of institutions. "We have a lot more to do to get there," Kliebert said.
But she said the program is working and "we are seeing success."
According to the federal complaint, mandated services are not available, and there are waiting lists for others. "These failures place Louisiana's children at serious risk of institutionalization in direct violation of both the federal Medicaid Act and the Americans With Disabilities Act," the groups' lawyers wrote to CMS Director Cindy Mann.
Mann is asked to investigate why the services are unavailable and "take all necessary action" to ensure that program failings are corrected.
Kliebert said she did not see how Louisiana could be out of compliance with federal law because it is "expanding services to these kids" where they live.
The Coordinated System of Care is a special federally approved program for children and youth who have complex behavioral health needs that make them high-risk for placement in a juvenile detention facility, psychiatric hospital, residential treatment facilities, foster care or alternative schools.
The administration initiative pooled funding from a variety of agencies that interface with the population, including the state departments of Health and Hospitals, Children and Family Services, Education and Juvenile Justice. The idea was to reduce the state's cost of providing services by leveraging Medicaid and other funding sources.
Follow Marsha Shuler on Twitter, @MarshaShulerCNB. For more coverage of the State Capitol, follow Louisiana Politics at http://blogs.theadvocate.com/politicsblog.


text: Hi, I appreciate everyone's expediency on this one. I'm in Marietta, GA and plan to spend the next day doing some serious Southern-style chowhounding. I want cheap, local food, preferring shacks, diners and dives over restaurants proper. Fried chicken livers are a favorite. Please share your recommendations, post haste, for places with good eats and a ton of atmosphere. And happy holidays!


text:
Wessex FM News
Be A Shark Trainer At Weymouth Sealife Park
8:45am 1st April 2013
How do you fancy the chance to be a shark trainer for the day?
It's one of the prizes on offer if you're the six millionth guest to visit Weymouth's Sea Life Centre.
You'll also get to name the next creature born at the park, get a premium pass for four people, and more.
Raquel Cubillo told Wessex FM, "This is the first time we've ever done a prize like this. From our numbers we've seen that it will happen within the next, probably, ten days or two weeks... someone will be our six millionth visitor".
For more information about Weymouth Sea Life Centre head to their website here: http://www.visitsealife.com/Weymouth/
Sign up for the latest local news direct to your inbox


text:
"Undiagnosed Breach Baby Born At Home"
About: Lister Hospital / Maternity Lister Hospital Maternity SG1 4AB
Posted via NHS Choices
21.07.16 Two Paramedics arrived at our home as our baby was being born rather quickly. They remained very calm considering the rarity of this situation. I did not realise my baby was being born in the breach position. They did not panic either me or my partner. A midwife arrived and helped to deliver the body of our baby very calmly. They also stayed with me after the birth and in the ambulance to the hospital. Two other midwives arrived and helped deliver the head of my baby, which was proving to be very stuck. As a team effort we all managed to successfully deliver the babies head. 2 further paramedics arrived to take care of our baby. The support from all 7 members of this team was absolutely phenomenal. They remained calm throughout this difficult, rare birth and helped each other out at an outstanding level of professionalism. It was overwhelming for all of us involved and with the high level of skill and support from all involved we now have a happy, healthy baby girl. I have never been in an emergency situation before and I can honestly say that they helped me keep calm and not panic. All three midwives have been in touch with me since the birth and I would like to thank them all for saving my baby and being utterly fantastic with their jobs. They are an absolute credit to the NHS and I am proud to have met them and see what incredible work they do. The paramedics were beyond amazing and I would like to thank them all for helping to deliver my baby and for transporting both me and my baby (separately) to Lister hospital. One midwife took care of me at Lister hospital and the care i received from them was so wonderful. They were so kind and caring and told me to stay strong for my little baby (who i didn't get to see for 4 hours. She was too poorly.) This midwife also taught me how to hand express my milk and talked me through everything that had been happening. They made me hot chocolates and gave me lots of hugs. I would also like to thank them for being so kind to me, sitting on the edge of the bed and holding my hand when talking about my baby. My Husband and I would like to say a huge thank you to the ANTS team who transported our baby to Addenbrooks in Cambridge. They also were extremely kind, friendly and honest with us. They made everything so clear for us to understand and we completely trusted putting our baby into their safe hands. They also transported our baby back to Lister hospital 12 days later. Thank you to everyone who helped our daughter to survive her very difficult birth.
Response from Lister Hospital 13 months ago
Thank you so much for getting in touch Natalie - sounds like you had a very tough time of it, but glad that you had all the support you needed from the paramedics and maternity teams. We'll pass your review on to them and in the meantime, please accept our best wishes for the future to you your now slightly bigger family!
- {{helpful}} {{helpful == 1 ? "person thinks" : "people think"}} this response is helpful
- Was this response helpful? Yes | No
Thank you for your feedback.
See more responses from Lister Hospital