Having been on the receiving end of Request for Information (RFI) and Request for Proposal (RFP) responses, from an evaluation perspective there are ways respondents can make it easier for the evaluation panel to assess what it is being proposed and ultimately have greater success on getting through to the next round. These considerations are from my experiences with Software package selection and with Delivery partner selection, but should be applicable to many other selections. 1. First impressions count. Even before the RFI/RFP response is opened, an evaluator can be swayed by the presentation of the response and the level of engagement getting there. Key considerations: Ask questions during the response period to validate any areas lacking clarity, but don’t go overboard. Make sure you meet the response times. Use good quality paper and colour (if required to present a paper copy). Binding can make a document look classier. If the response requests that all questions a
" Site Reliability Engineering: How Google Runs Production Systems " edited by Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy contains a number of insights into Google's SRE practice. It is a bit repetitive at times but this assists in drilling in some of the key points. My key take aways were: Google places a 50% cap on all aggregate "ops" work for all SREs - tickets, on-call, manual tasks, etc. The remaining 50% is to do development. If consistently less than 50% development then often some of the burden is pushed back to the development team, or staff are added to the team. An error budget is set that is one minus the availability target (e.g. a 99.99% availability target will have a 0.01% error budget). This budget cannot be overspent and assists in the balance of reliability and the pace of innovation. Cost is often a key factor in determining the proposed availability target for a service. if we were to build an operate
Time Machine is the built-in backup feature of OS X. It keeps a copy of all your files, and remembers how your system looked on any given day so you can revisit your Mac as it appeared in the past. Apple sells a device called a Time Capsule, but rather than buy one of these I opted for a diy approach using my Raspberry Pi and so far it seems to be working well. My setup consists of: Raspberry Pi Model B running Raspbian connected via network cable to a router MacBook Pro running OS X Yosemite v10.10.1 connected via Wifi to a router External 2TB drive (with separate power) attached via USB to the Raspberry Pi It was relatively easy to setup following the instructions at http://www.raspberrypi.org/forums/viewtopic.php?f=36&t=47029 . I am reiterating the instructions here just in case the page disappears (with a couple of additions I needed): 1. Start with a clean installation of Raspbian, configured for your network 2. Power down your Pi, connect your storage drive,
Comments
Post a Comment