![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Back to work this morning, after an uneventful and mostly slept-through pair of flights got me from LAX to BWI yesterday. Already the annoying microdrama kicks in, with Lazar Pestke and Neal Evil and Rocco Martine all quibbling about an acquisition that's been postponed for, well, more than a year now, one week or one month at a time. The latest draft documents to be published (late January? early February?) ask bidders to include something called a 'Statement of Work—Solution (SOW-S)'; and while proposals often must include a Statement of Work (listing out in organized outline fashion all the things you intend to do for your client) and sometimes a 'technical solution' (a more discursive examination of how you intend to accomplish the work), the term 'Statement of Work—Solution' is not a recognized piece of jargon and it seems clear the customer just made it up. It's kinda like asking for a 'Grilled Cheese Sandwich—Pizza.'
Now, because the agency hasn't answered any questions about the acquisition for three months and because they have never defined what they mean by 'Statement of Work—Solution', arguing about how to develop one is a little like the Jews in Salome bickering endlessly about the more obscure points of scripture. Which, ok, you go ahead and debate unanswerable questions, but PLEASE don't bring the argument into my office. We only talk about real things in here. *Sigh*
Now, because the agency hasn't answered any questions about the acquisition for three months and because they have never defined what they mean by 'Statement of Work—Solution', arguing about how to develop one is a little like the Jews in Salome bickering endlessly about the more obscure points of scripture. Which, ok, you go ahead and debate unanswerable questions, but PLEASE don't bring the argument into my office. We only talk about real things in here. *Sigh*