Maneesha,
Interesting thing about P311 requests "lifespan"... The times recorded on the P311 requests are only how long it takes for P311 to route them to the appropriate city department. Often times a new queue system is then entered where the time to action is different. For example, I put in a request to Philly311 last May to get a L&I inspection. The P311 requests were "closed" nearly immediately by Philly 311 because they had "completed" their task of forwarding it to L&I.
With L&I however, the inspector would not arrive for another three months and to date many of the issues raised are still unaddressed. In the L&I system the new item opened was a "case investigation" and subsequently "violations" of the city code. These have their own datasets, however the time from Philly 311 submission to arrival of an inspector is not publicly available that I'm aware unless you know the relevant IDs to match them or they included publicly the address involved and there are few enough to match consistently. Other departments have other similar queues for say potholes at the Streets Department etc.
This is one of the major issues I have with Phily 311. There appears to be little "real" accountability as this aspect of the system is obfuscated by the centrality that the city has placed on Philly 311 as the single point of contact. Once it's out of their hands, they have no insights into how long it will take or even if the department of interest is pursuing the case. I was told by L&I that when Philly 311 misroutes a case to the wrong section the case is just closed without forwarding it to the right section even within L&I. There are also fiefdoms and turf wars so if you ask for a pothole repair that is on a street that also has trolley tracks, SEPTA and the Streets Department will both deny its their responsibility because it's simultaneously too close to and also not close to the trolley tracks making it the other department's responsibility.
It's kind of a big mess under the hood. Aspects of Philly 311 were completely down for about 5 months last year and not allowing a good number of users to sign in. No one admitted was a problem and they denied it even when I showed them how Twitter was full of complaints. I eventually figured out what the issue was after the vendor lied saying it was an error on Facebook's end. I sent them a guide about Facebook making changes to single sign-on authentication and pointed out there was notice months in advance. I never heard back from anyone, and two weeks later magically the errors suddenly disappeared.
Point is, don't take anything at face value. Data dictionaries would be very nice and they have not been forthcoming. We just get told the "metadata" is enough when it doesn't in fact include information on many codes used in the datasets.
Phil