zilongwang/ReadingBank huggingface dataset:
Figure 5: Apply for a Vacancy Most of the fields will be populate with the data you provided in your Profile. At this point, you can manually change the data if needed. Note: changes are for the application and will not be saved in your Profile. Attach your resume and narrative. Select a classification for each of these documents. Note: Supported formats are pdf, doc, docx, txt, and rtf. Press the Submit Application button. WHERE IS MY APPLICATION? Once submitted, your application will go to your organization’s Duty Program Office for nomination. Upon supervisor approval, it will be forwarded to the Joint Duty Program Office for the vacancy’s posting organization. To find out where your application is in this process, click the My Applications button located in the top right hand corner of each page. To view the vacancy, click on the vacancy number. To withdraw your application, click the Withdraw action. Figure 6: My Applications Under the status column, you will see one of the following possible statuses: Status Description Submitted Your application has not yet been nominated for the position. Nominated Your application has been forwarded to the agency who posted the position. Selected You were selected for the position. Not Selected You were not selected for the position. Accepted You were selected for the position and accepted. Declined You were selected for the position and declined.
greater than or equal to the inserted position are increased by one. A negative ordinal indexes from the end of the collection, with -1 representing an insert at the end of the collection. The syntax rule defines the formal grammar of the $index query option. Custom Query Options Custom query options provide an extensible mechanism for service-specific information to be placed in a URL query string. A custom query option is any query option of the form shown by the rule customQueryOption in . Custom query options MUST NOT begin with a $ or @ character. Example : service-specific custom query option debug-mode http://host/service/Products?debug-mode=true Parameter Aliases Parameter aliases can be used in of literal values in entity keys, parameters, or within a or expression. Parameter aliases MUST start with an @ character. The semantics of parameter aliases are covered in . The rule aliasAndValue defines the formal grammar for passing parameter aliases as query options.
Revision History Revision Date Editor Changes Made Working Draft 01 2016-06-22 Michael Pizzo Transferred content from OData 4.0 Part I - Protocol Errata 3 Committee Specification Draft 01 2016-12-08 Michael Pizzo Ralf Integrated 4.01 features Schema Versioning Preference omit-values $compute system query option Indexing into Ordered Collections Deep Update Improved referencing in batch requests Committee Specification 02 2017-06-20 Michael Pizzo Ralf Handl More 4.01 features operations JSON Batch format CSDL JSON format Committee Specification Draft 03 2017-09-28 Michael Pizzo Ralf Handl Incorporated review feedback Added nested query options for $select Added nested parameter alias value assignments within $expand and $select Simplified implicit parameter aliases for function (import) calls
This project was submitted for FASTLANE funding in FY 2017 under the project name: Reconstruction of I-44/US-75 Interchange Bridges and Related Improvements on I-44, City of Tulsa, Oklahoma Previously Incurred Project Cost: $1,084,580 Project on NHFN? YES Future Eligible Project Cost: $108,686,040 Project on NHS? YES Total Project Cost: $109,770,620 Project to add Interstate capacity? YES NSFHP Request: $63,829,200 Project in national scenic area? NO Federal Funds (including NSFHP) $86,948,830 Rail crossing or separation included? NO Intermodal or freight rail project, or freight project within freight rail, water, or intermodal facility? NO Matching funds restricted to specific project component? NO If yes, specify: NA NSFHP $ to be spent on above two items: NA State: Oklahoma Begin: Lat/Long: 36˚5’20.40”N / 96˚01’50.17”W Inclusion in Planning Documents: End: Lat/Long: 36˚5’23.40”N/ 95˚59’36.12”W TIP: NO* Size of project: Large STIP: NO* Submitting TIGER project? No MPO LRTP: YES Urbanized Area (UA): OK State LRTP: YES UA population, 2015 686,033 Freight Plan: NA *elements of this project are included in the current STIP and TIP documents
2st $55 M in accident cost reduction All results for the Benefit Cost Analysis are estimated for the segments in the immediate vicinity of the project which will be the most directly impacted. However, in addition to these localized benefits, a select link analysis of the Project’s impacts has demonstrated significant benefits to the broader transportation network in the region. For example, the Oklahoma Turnpike Authority, the MPO (INCOG), ODOT, and the City of Tulsa are currently working in a cooperative partnership to advance a major north-south freeway connection on the west side of Tulsa. This facility, once built, is expected to add approximately 10,000 vehicles per day to I-44 and in turn significantly enhancing the overall benefits of this project. Given the strategic importance of this segment for the region and the state in general, the estimated regional benefits are briefly summarized in Table 8 below. TABLE 8: Merit Criteria and Cost-Effectiveness - Summary of Infrastructure Improvements and Associated Benefits (Regional Impacts) CURRENT STATUS OR BASELINE and problems to be addressed CHANGES TO BASELINE / ALTERNATIVES TYPE OF IMPACTS POPULATION AFFECTED by impacts ECONOMIC BENEFIT SUMMARY OF RESULTS ($M discounted at 7%) Travel Delays for Passenger Vehicles and Trucks due to congestion on I-44. Increase the capacity of I-44 by widening I-44 from four through lanes to six through lanes from Union Avenue to the Arkansas River, along with bridge replacements at 33rd W. Avenue, Union Avenue, and the US-75 Interchange. Improved travel speeds, reduced long-term congestion, fuel savings Passenger vehicles, trucks Travel Time and Vehicle Operating Cost Savings 295.78 Emission Savings Passenger vehicles, trucks Emissions Cost Reduction 4.44 Improved Safety Passenger vehicles, trucks Accident Cost Reduction 54.63
Revision History Revision Date Editor Changes Made Working Draft 01 2016-06-22 Michael Pizzo Ralf Handl Transferred content from OData 4.0 Part 2 – URL Conventions Errata 3 Committee Specification 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features Alternate keys Key-as-segment convention Operators in and divby $expand with stream properties $compute system query option $index system query option Committee Specification Draft 02 2017-06-08 Michael Pizzo Ralf More 4.01 features Set-based operations $expand, $select, $filter with POST and PATCH Instance annotations in query options $schemaversion system query option Committee Specification Draft 03 2017-09-28 Michael Pizzo Ralf Handl Incorporated review feedback nested query options within $select nested alias value assignments within $expand and $select
014-108 SIDE OF HOOD AIR INTAKE WITH FIREWALL MOUNTED DONALDSON AIR CLEANER WITH SAFETY ELEMENT AND INSIDE/OUTSIDE AIR WITH SNOW DOOR 10 $367.00 124-1E1 DR 12V 200 AMP 28-SI QUADRAMOUNT PAD ALTERNATOR WITH REMOTE BATTERY VOLT SENSE $137.00 292-058 (3) ALLIANCE MODEL 1031, GROUP 31, 12 VOLT MAINTENANCE FREE 2280 CCA THREADED STUD BATTERIES -10 ($217.00) 290-017 BATTERY BOX FRAME MOUNTED 35 $65.00 282-003 SINGLE BATTERY BOX FRAME MOUNTED LH SIDE BACK OF CAB N/C 291-017 WIRE GROUND RETURN FOR BATTERY CABLES WITH ADDITIONAL FRAME GROUND RETURN STD 289-001 NON-POLISHED BATTERY BOX N/C 107-032 CUMMINS TURBOCHARGED 18.7 CFM AIR COMPRESSOR WITH INTERNAL SAFETY N/C 131-013 AIR COMPRESSOR DISCHARGE LINE STD 152-041 ELECTRONIC ENGINE INTEGRAL SHUTDOWN PROTECTION SYSTEM STD 128-037 C-BRAKE BY JACOBS WITH 2 SWITCHES; (1) ON/OFF, (1) LOW/MED/HIGH BRAKING 80 $2,580.00 016-1C2 RH OUTBOARD UNDER STEP MOUNTED HORIZONTAL AFTERTREATMENT SYSTEM ASSEMBLY WITH RH B-PILLAR MOUNTED VERTICAL TAILPIPE STD 28F-002 ENGINE AFTERTREATMENT DEVICE, AUTOMATIC OVER THE ROAD REGENERATION AND DASH MOUNTED REGENERATION REQUEST SWITCH STD 239-026 10 FOOT 06 INCH (126 INCH+0/-5.9 INCH) EXHAUST SYSTEM HEIGHT ($4.00) 237-1CR RH CURVED VERTICAL TAILPIPE B-PILLAR MOUNTED ROUTED FROM STEP STD 23U-001 6 GALLON DIESEL EXHAUST FLUID TANK STD 30N-003 100 PERCENT DIESEL EXHAUST FLUID FILL STD 23Y-001 STANDARD DIESEL EXHAUST FLUID PUMP MOUNTING STD 43X-002 LH MEDIUM DUTY STANDARD DIESEL EXHAUST FLUID TANK LOCATION STD 242-001 STAINLESS STEEL AFTERTREATMENT DEVICE/MUFFLER/TAILPIPE SHIELD STD 273-018 HORTON DRIVEMASTER ADVANTAGE ON/OFF FAN DRIVE N/C
276-001 AUTOMATIC FAN CONTROL WITHOUT DASH SWITCH, NON ENGINE MOUNTED STD 110-003 CUMMINS SPIN ON FUEL FILTER N/C 118-008 COMBINATION FULL FLOW/BYPASS OIL FILTER N/C 266-017 1300 SQUARE INCH ALUMINUM RADIATOR -20 N/C 267-006 MOUNTING FOR FIREWALL MOUNTED TANK STD 103-039 ANTIFREEZE TO -34F, OAT (NITRITE AND SILICATE FREE) EXTENDED LIFE COOLANT ($10.00) 171-007 GATES BLUE STRIPE COOLANT HOSES OR EQUIVALENT STD 172-001 CONSTANT TENSION HOSE CLAMPS FOR COOLANT STD 270-016 RADIATOR DRAIN VALVE N/C 168-998 NO RADIATOR/OIL PAN GUARD -5 ($94.00) 360-016 1310 ADAPTER FLANGE FOR PTO PROVISION 10 $1,366.00 138-011 PHILLIPS-TEMRO 1000 WATT/115 VOLT BLOCK HEATER 4 N/C 166-998 NO OIL PREHEATER ($69.00) 140-022 CHROME ENGINE HEATER RECEPTACLE MOUNTED UNDER LH DOOR STD 134-001 ALUMINUM FLYWHEEL HOUSING STD 132-004 ELECTRIC GRID AIR INTAKE WARMER N/C 155-058 DELCO 12V 38MT HD STARTER WITH INTEGRATED MAGNETIC SWITCH -10 N/C Transmission 342-582 ALLISON 3000 RDS AUTOMATIC TRANSMISSION WITH PTO PROVISION -110 -35 $7,691.00 Transmission Equipment 343-339 ALLISON VOCATIONAL PACKAGE 223 - AVAILABLE ON 3000/4000 PRODUCT FAMILIES WITH VOCATIONAL MODELS RDS, HS, MH AND TRV N/C 84B-012 ALLISON VOCATIONAL RATING FOR ON/OFF HIGHWAY APPLICATIONS AVAILABLE WITH ALL PRODUCT FAMILIES N/C 84C-022 PRIMARY MODE LOWEST GEAR 1, START GEAR 1, HIGHEST GEAR 5, AVAILABLE FOR 3000/4000 PRODUCT FAMILIES ONLY N/C
The proposed project is within the Tulsa urbanized area and the Tulsa Transportation Management Area (TMA) as shown in Figure 5. It is located within the I-44 corridor, a portion of the Primary Highway Freight Network, from its intersection with I-244 extending east approximately two and one-half miles to the Arkansas River (see Figure 6). The project’s extents are between 33rd W. Avenue and the Arkansas River. Bridge improvements are planned at 33rd W. Avenue, Union Avenue, and at the I-44/US-75 interchange. The interstate will be widened from Union Avenue to the Arkansas River. FIGURE 5: Tulsa Transportation Management Area (TMA) FIGURE 6: Project Elements Map The Oklahoma Department of Transportation (ODOT) is the project sponsor. ODOT is coordinating the project with the Indian Nations Council of Governments (INCOG), the City of Tulsa, and Tulsa County. The I-44/US-75 Improvements project is a true partnership, using State and Federal funds as shown in Table 1 below. Future Eligible Cost The future eligible cost for the I-44/US-75 Improvements project is $108,686,040. A project of this magnitude is beyond the capabilities of ODOT to fund with and federal appropriations alone. Without FASTLANE funding, ODOT would be forced to build the project in multiple phases over many decades. Availability and Commitment of all Committed and Expected Funding Sources and Uses of all Project Funds The availability and commitment of funding sources are presented in 1. TABLE 1: Sources and Uses of Funds
and through the interchange – an improvement which is known to correlate to reduced incidence of rear-end collisions. FIGURE 9: Selected Corridor Crash Statistics Within the Project Limits Statewide Average Visible Injury 66.8 11.37 5.88 Fatal 2.3 0.63 3.65 All Crashes 254.7 63.55 4.01 FIGURE 10: I-44 Severity Cluster Map (2010-2014) The second most prevalent crash type on the corridor, accounting for one-eighth of the total crashes, relates to collisions with fixed objects. More than half of these collisions involved injuries, and one was fatal. As part of the modernization of the corridor, the facility will be designed to current standards – with new median barrier protecting both directions (median barrier exists only for westbound traffic today), pier protection on I-44 under the US-75 and Union Avenue bridges, new bridge rail on all the replaced bridges, new barrier wall and impact
Moreover, the cooperative partnership between Oklahoma Turnpike Authority, the MPO (INCOG), ODOT, City of Tulsa, and Tulsa County to advance the long planned and NEPA-cleared Gilcrease Expressway is expected to add traffic volumes once built, in turn significantly enhancing the overall benefits of this project. Table 16: Overall Results of the Benefit Cost Analysis (Regional Impacts), Millions of 2015 Dollars Project Evaluation Metric 7% Discount Rate 3% Discount Rate Total Discounted Benefits $354.9 $650.9 Total Discounted Costs $84.2 $98.1 Net Present Value $270.7 $552.7 Benefit / Cost 4.21 6.63 Internal Rate of Return (%) 25.04% Payback Period (years) 3 years : Benefit Estimates by Merit Criteria for the Full Build Alternative (Regional Impacts) Merit Criteria Benefit Categories 7% Discount Rate 3% Discount Rate Economic Travel Time Savings $334,630,965 $611,468,896 Vehicle Operating Cost Savings -$38,846,729 -$67,162,641 Safety Accident Cost Reduction $54,630,055 $98,963,514 Community and Environmental Emissions Cost Reduction $4,438,142 $7,599,533 Total Benefit Estimates $354,852,433 $650,869,302 BCA Sensitivity Analysis The BCA outcomes presented in the previous sections rely on a large number of assumptions and long-term projections; both of which are subject to considerable uncertainty. The primary purpose of the sensitivity analysis is to help identify the variables and parameters whose variations have the greatest impact on the BCA outcomes: the “critical variables.” The sensitivity analysis can also be used to: Evaluate the impact of changes in individual critical variables – how much the final results would vary with reasonable departures from the “preferred” or most likely value for the variable; and Assess the robustness of the BCA and evaluate, in particular, whether the conclusions reached under the “preferred” set of input values are significantly altered by reasonable departures from those values.
Acknowledgments The following individuals were members of the OASIS OData Technical Committee during the creation of this specification and their contributions are gratefully acknowledged: Howard Abrams (CA Technologies) Ken Baclawski (Northeastern University) Jay Balunas (Red Hat) Stephen Berard (Schneider Electric Industries SAS) Mark Biamonte (Progress Software) Matthew Borges (SAP SE) Edmond Bourne (BlackBerry) Joseph Boyle (Planetwork, Inc.) Peter Brown (Individual) Antonio Campanile (Bank of America) Castro (Microsoft) Axel Conrad (BlackBerry) Robin Cover (OASIS) Erik de Voogd (SDL) Yi Ding (Microsoft) Diane Downie (Citrix Systems) Patrick Durusau (Individual) Andrew Eisenberg (IBM) Chet Ensign (OASIS) Davina Erasmus (SDL) George Ericson (Dell) Colleen Evans (Microsoft) Jason Fam (IBM) Senaka Fernando (WSO2) Josh Gavant (Microsoft) Brent Gross (IBM) Zhun Guo (Individual) Anila Kumar GVN (CA Technologies) Stefan Hagen (Individual) Ralf Handl (SAP SE) Barbara Hartel (SAP SE) Hubert Heijkers (IBM) Jens Hüsken (SAP SE) Evan Ireland (SAP SE) Gershon Janssen (Individual) Ram Jeyaraman (Microsoft) Ted Jones (Red Hat) Diane Jordan (IBM) Stephan Klevenz (SAP SE) Gerald Krause (SAP SE) Nuno Linhares (SDL) Paul Lipton (CA Technologies) Susan Malaika (IBM) Ramanjaneyulu Malisetti (CA Technologies) Neil McEvoy (iFOSSF – International Free and Open Source Solutions Foundation) Stan Mitranic (CA Technologies) Dale Moberg (Axway Software) Graham Moore (BrightstarDB Ltd.) Farrukh Najmi (Individual) Shishir Pardikar (Citrix Systems) Sanjay Patil (SAP SE) Nuccio Piscopo (iFOSSF – International Free and Open Source Solutions Foundation) Michael Pizzo (Microsoft) Ramesh Reddy (Red Hat) Robert Richards (Mashery) Sumedha Rubasinghe (WSO2) James Snell (IBM) Jeffrey Turpin (Axway Software) John Willson (Individual) John Wilmes (Individual) Christopher Woodruff (Perficient, Inc.) Martin Zurmuehl (SAP SE)
To determine the off‐site odour impact from existing operations 1. Non‐analytical assessment 2. Ambient sampling and measurement To determine the expected changes in off‐site odours resulting from new facilities, expansions of existing facilities or other operational changes 1. Source sampling and measurement 2. Ambient sampling and measurement 3. Dispersion modelling Section 6 of provides more detail about costs, accuracy, ease of use, limitations and other factors about each tool.
Revision History Revision Date Editor Changes Made Working Draft 01 2016-06-22 Michael Pizzo Ralf Handl Transferred content from OData 4.0 Part 2 – URL Conventions Errata 3 Committee Specification Draft 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features Alternate keys Key-as-segment convention Operators in and divby $expand with stream properties $compute system query option $index system query option Committee Specification Draft 02 2017-06-08 Michael Pizzo Ralf More 4.01 features Set-based operations $expand, $select, $filter with POST and PATCH Instance annotations in query options $schemaversion system query option Committee Specification Draft 03 2017-09-28 Michael Pizzo Ralf Handl Incorporated review feedback Added nested query options within $select Added nested alias value assignments within $expand and $select Committee Specification Draft 04 2017-11-10 Michael Ralf Handl Incorporated review feedback Simplified unrelating entities
CHILTERN DISTRICT COUNCIL AND SOUTH BUCKS DISTRICT COUNCIL ODOUR NUISANCE DIARY Dealt with by: My Ref: e-mail: Direct Line: This record is necessary for the investigation of your odour complaint and must be an accurate account of the nuisance disturbing you. All entries must be precise and signed as this record may be used as evidence if legal proceedings are taken in the future. Please only record the incidents that you consider unreasonable. Further guidance on completing the diary can be found in the Nuisance Information Pack. Any adult staying in your house that is disturbed by the odour may fill in a diary sheet. The diary is your own personal record of what you experience. You cannot write down something that other people (including your wife, husband or partner) have witnessed. They must record it in their own diary. You should fill in the diary as soon as possible after the incident has happened. Ensure you complete the top of the form with your name, address and telephone number. Please return the completed form to or Environmental Health Dept. King George V House. King George V Road. Amersham. Bucks. HP6 5AW Date Time nuisance starts & finishes Intensity (see Column 1) Offensiveness (see column 2) Duration/ Persistence (see column 3) Weather Conditions i.e. windy/rainy/ sunny Character of odour if distinguishable How and where it affects you within your property For example Wednesday 23/11/16 3 (There was a distinct odour) -4 (It was very unpleasant) 3 (It was detectable for most of the time) Sunny but windy Smoke from a garden bonfire I was not able to use my garden and the smoke was also in my house.
Date Time Start/Finish Intensity (1) Offensiveness (2) Duration/ Persistance (3) Weather conditions Character of odour How it affects you Signed ……………………………………………………………………………………………………… Date ………………………………………………….. CONTINUATION OF STATEMENT OF ……………………………………………………………………………… Date Time Start/Finish Intensity (1) Offensiveness (2) Duration/ Persistance (3) Weather conditions Character of odour How it affects you
Signed ……………………………………………………………………………………………………… Date ………………………………………………….. CONTINUATION OF STATEMENT OF ……………………………………………………………………………… Date Time Start/Finish Intensity (1) Offensiveness (2) Duration/ Persistance (3) Weather conditions Character of odour How it affects you
Revision History Revision Date Editor Changes Made Working 01 2016-06-22 Michael Pizzo Ralf Transferred content from 4.0 Part 2 – URL Conventions Errata 3 Committee Specification 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features Alternate keys Key-as-segment convention Operators in and divby $expand with stream properties $compute system query option system query option Committee Specification Draft 02 2017-06-08 Michael Pizzo Ralf Handl More 4.01 features Set-based operations $expand, $select, $filter with POST and PATCH Instance annotations in query options $schemaversion system option Committee Specification Draft 03 2017-09-28 Michael Pizzo Ralf Incorporated review feedback Added nested query options within $select Added nested alias value assignments within $expand and $select Committee Specification Draft 04 2017-11-10 Michael Pizzo Ralf Handl Incorporated review feedback Simplified unrelating entities Committee Specification 01 2018-01-17 Michael Pizzo Ralf Handl Non-Material Changes
ODP CERTIFIED INVESTIGATOR PROGRAM PHYSICAL EVIDENCE LOG SHEET CASE NAME: CASE NUMBER: Physical Evidence Identified Collected? Date/Time Collected Chain of Custody Notes 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18.
Request for Approved Program Capacity & Noncontiguous Clearance Attachment #1 SECTION A Legal Entity Name: Street Address/City/State/Zip: Contact Name: Phone Number (include area code): Email Address: MPI #: Service Location Code: Check the type of service location that applies to the request RESIDENTIAL SERVICE LOCATIONS COMMUNITY PARTICIPATION SUPPORT FACILITIES Licensed 55 Pa. Code Ch. 6400 Community Living Home Licensed 55 Pa. Code Ch. 6500 Family Living Home ☐ Unlicensed Life Sharing Home ☐ Licensed 55 Pa. Code Ch. 2380 Adult Training Facility Licensed 55 Pa. Code Ch. 6400 Community Living Home (For Respite Only Homes) Licensed 55 Pa. Code Ch. 3800 Child Residential and Day Treatment ☐ Licensed 55 Pa. Code Ch. 5310 Community Residential Rehabilitation ☐ Licensed 55 Pa. Code Ch. 2390 Vocational Facility Unlicensed Residential Habilitation Supported Living ☐ Licensed 6 Pa. Code Chapter 11 Older Adult Daily Living Centers Service Location Street Address/City/State/Zip: Check the Type of Request Request For a New Community Participation Support Facility to Establish Noncontiguous Clearance (Prior to Requesting Approved Program Capacity) (Proceed to Section B) Request For a New Licensed or Unlicensed Residential Service location to Establish Noncontiguous Clearance to Requesting Approved Program Capacity) (Proceed to Section C) Request to Establish Approved Program Capacity for a new Licensed Residential Service Location Under 55 Pa. Code Ch. 6400 Community Living Home (including Respite Only Homes), Ch. 6500 Family Living Home, Ch. 5310 Community Residential Rehabilitation or Ch. 3800 Child Residential and Day Treatment Facility (Proceed to Section D) Request to Establish Approved Program Capacity for a new Unlicensed Residential Service Location including Supportes Living, Life Sharing, and Residential Habilitation homes. (Proceed to Section E) Request to Change Current Approved Program Capacity For a Licensed or Unlicensed Residential Service Location (Proceed to Section F) Request to Close a Licensed or Unlicensed Residential Service Location (not including Supported Living) or a Community Participation Support Facility (Proceed to Section G) SECTION B – REQUEST FOR A NEW COMMUNITY PARTICIPATION SUPPORT FACILITY TO ESTABLISH NONCONTIGUOUS CLEARANCE
int16 Edm.Int16 format OpenAPI format int64 Edm.Int64 OpenAPI format int8 Edm.SByte OData-specific format single Edm.Single OData-specific format time Edm.TimeOfDay OData-specific format, was part of JSON Schema Draft 03 uint8 Edm.Byte OData-specific format uuid Edm.Guid OData-specific format
The proceeds of the performance security shall be payable to Office of the Director of Public Prosecutions (ODPP) as compensation for any loss resulting from the Tenderer’s failure to complete its obligations under the Contract. The performance security shall be denominated in the currency of the Contract, or in a freely convertible currency acceptable to the Judiciary and shall be in the form of : Cash. A bank guarantee. The performance security will be discharged by Office of the Director of Public Prosecutions (ODPP) and returned to the candidate not later than thirty (30) days following the date of completion of the tenderer’s performance of obligations under the contract, including any warranty obligations under the contract. Inspections and Tests Office of the Director of Public Prosecutions (ODPP) or its representative shall have the right to inspect and/or to test the services to confirm their conformity to the Contract specifications. Office of the Director of Public Prosecutions (ODPP) shall notify the tenderer in writing, in a timely manner, of the identity of any representatives retained for these purposes. The inspections and tests may be conducted on the premises of the tenderer or its subcontractor(s). If conducted on the premises of the tenderer or its subcontractor(s), all reasonable facilities and assistance, including access to drawings and production data, shall be furnished to the inspectors at no charge to the Judiciary. Should any inspected or tested services fail to conform to the Specifications, Office of the Director of Public Prosecutions (ODPP) may reject the services, and the tenderer shall either replace the rejected services or make alterations necessary to meet specification requirements free of cost to Office of the Director of Public Prosecutions (ODPP). Nothing in paragraph 3.7 shall in any way release the tenderer from any warranty or other obligations under this Contract. Payment The method and conditions of payment to be made to the tenderer under this Contract shall be specified in SCC Prices Prices charged by the contractor for services performed the Contract shall not, with the exception of any Price adjustments authorized in SCC , vary from the prices by the tenderer in its tender or in the ODPP’s request for tender validity extension as the
SECTION I - INVITATION FOR TENDERS Date: 26th SEPTEMBER, 2017 TENDER NEGOTIATION NUMBER: ………….. TENDER NO ODPP/OT/001/2017-2018 The Office of the Director of Public Prosecutions invites eligible bidders to tender for the following and services S/NO TENDER NUMBER TENDER DESCRIPTION REMARKS Bid bond amount CLOSING /OPENING DATE 1. PROVISION OF GROUP PERSONAL ACCIDENT INSURANCE COVER I. Two renewable annually based on satisfactory performance II. Submit on IFMIS and hardcopy 50,000 10/10/2017 1. Bidders must meet the minimum requirements as indicated in the tender documents.
2.26 Signing of Contract 2.26.1 At the same time as the ODPP notifies the successful tenderer that its tender has been accepted, the ODPP will simultaneously inform the other tenderers that their tenders have not been successful. 2.26.2 Within fourteen (14) days of receipt of the Contract Form, the successful tenderer shall sign and date the contract and return it to the ODPP. 2.26.3 The parties to the contract shall have it signed within 30 days from the date of notification of contract award unless there is an administrative review request. 2.27 Performance Security 2.27.1 Within seven (7) days of the receipt of notification of award from the ODPP, the successful tenderer shall furnish the performance security in accordance with the Conditions of Contract, in the Performance Security Form provided in the tender documents, or in another form acceptable to the ODPP. 2.27.2 Failure of the successful tenderer to comply with the requirement of paragraph 2.29 or paragraph 2.30.1 shall constitute sufficient grounds for the annulment of the award and forfeiture of the tender security, in which event the ODPP may make the award to the next lowest evaluated or call for new tenders. 2.28 Corrupt or Fraudulent Practices 2.28.1 The ODPP requires that tenderers observe the highest standard of ethics during the procurement process and execution of contracts. A tenderer shall sign a declaration that he has not and will not be involved in corrupt or fraudulent practices. 2.28.2 The ODPP will reject a proposal for award if it determines that the tenderer recommended for award has engaged in corrupt or fraudulent practices in competing for the contract in question; 2.28.3 further, a tenderer who is found to have indulged in corrupt or fraudulent practices risks being debarred from participating in public procurement in Kenya. Appendix to Instructions to Tenderers The following information for procurement of services shall complement or amend the provisions of the instructions to tenderers. Wherever there is a conflict
Acknowledgments The following individuals were members of the OASIS OData Technical Committee during the creation of this specification and their contributions are gratefully acknowledged: Howard Abrams (CA Technologies) Ken Baclawski (Northeastern University) Jay Balunas (Red Hat) Stephen Berard (Schneider Electric Industries SAS) Mark Biamonte (Progress Software) Matthew Borges (SAP SE) Edmond Bourne (BlackBerry) Joseph Boyle (Planetwork, Inc.) Peter Brown (Individual) Antonio Campanile (Bank of America) Pablo Castro (Microsoft) Axel Conrad (BlackBerry) Robin Cover (OASIS) Erik de Voogd (SDL) Yi Ding (Microsoft) Diane Downie (Citrix Systems) Stefan Drees (Individual) Patrick Durusau (Individual) Andrew Eisenberg (IBM) Chet Ensign (OASIS) Davina Erasmus (SDL) Colleen Evans (Microsoft) Fam (IBM) Senaka Fernando (WSO2) Josh Gavant (Microsoft) Brent Gross (IBM) Zhun Guo (Individual) Anila Kumar GVN (CA Technologies) Ralf Handl (SAP SE) Barbara Hartel (SAP SE) Hubert Heijkers (IBM) Jens Hüsken (SAP SE) Evan Ireland (SAP SE) Gershon Janssen (Individual) Ram Jeyaraman (Microsoft) Ted Jones (Red Hat) Diane Jordan (IBM) Stephan Klevenz (SAP SE) Gerald Krause (SAP SE) Nuno Linhares (SDL) Paul Lipton (CA Technologies) Susan Malaika (IBM) Ramanjaneyulu Malisetti (CA Technologies) Neil McEvoy (iFOSSF – International Free and Open Source Solutions Foundation) Stan Mitranic (CA Technologies) Dale Moberg (Axway Software) Graham Moore (BrightstarDB Ltd.) Farrukh (Individual) Shishir Pardikar (Citrix Systems) Sanjay Patil (SAP SE) Nuccio Piscopo (iFOSSF – International Free and Open Source Solutions Foundation) Michael (Microsoft) Ramesh Reddy (Red Hat) Robert Richards (Mashery) Sumedha Rubasinghe (WSO2) James Snell (IBM) Jeffrey Turpin (Axway Software) John Willson (Individual) John Wilmes (Individual) Christopher Woodruff (Perficient, Inc.) Martin Zurmuehl (SAP SE)
Table 1: Example of key datasets for the energy sector Dataset Description Example of best practice Detailed electricity consumption Average electricity consumption at the most detailed level (building, block, district) (); Power stations List of current power stations in the country, including their localization, installed and effective capacity Electricity transmission and distribution networks Geospatial data of lines and stations of electricity transmission and distribution network including length capacity, and expansion project. Existing electricity and in Uganda Statistics on renewable energy Statistics on generation of renewable energy per type of energy source. Power outages Historical, planned and real time power outages data. Energy audit (Certificate) Results of energy audits for private, public buildings and other infrastructures Detailed domestic gas consumption Average gas consumption at the most detailed (building, block, district) () Detailed domestic fuel consumption Average domestic fuel consumption at the most detailed level (building, block, district) Buildings List of main buildings including including properties such as type of roof. real estates List of publicly-owned, let or managed real estates Land Register Geospatial data of boundaries
Example : all customers from Berlin, Germany http://host/service/Customers? $filter=concat(concat(City,', '), Country) eq 'Berlin, Germany' contains The contains function has the following signature: Edm.Boolean contains(Edm.String,Edm.String) The contains function returns true if the second parameter string is a substring of the first parameter string value, otherwise it returns false. The containsMethodCallExpr syntax rule defines how the contains function is invoked. Example : all customers with a CompanyName that contains 'Alfreds' http://host/service/Customers?$filter=contains(CompanyName,'Alfreds') endswith The endswith function has the following signature: Edm.Boolean endswith(Edm.String,Edm.String) The endswith function returns true if the parameter string value ends with the second parameter string value, otherwise it returns false. The endsWithMethodCallExpr syntax rule defines how the endswith function is invoked. Example : all customers with a CompanyName that ends with 'Futterkiste' http://host/service/Customers?$filter=endswith(CompanyName,'Futterkiste') indexof The indexof function has the following signature: Edm.Int32 indexof(Edm.String,Edm.String) The indexof function returns the zero-based character position of the first occurrence of the second parameter value in the first parameter value, or -1 if the second parameter value does not occur in the first parameter value. The indexOfMethodCallExpr syntax rule defines how the indexof function is invoked. Example : all customers with a CompanyName containing 'lfreds' starting at the second character http://host/service/Customers?$filter=indexof(CompanyName,'lfreds') eq 1 length The length function has the following signature: length(Edm.String) The length function returns the number of characters in the parameter value. The lengthMethodCallExpr syntax rule defines how the length function is invoked. Example : all customers with a CompanyName that is 19 characters long http://host/service/Customers?$filter=length(CompanyName) eq 19 startswith The startswith function has the following signature:
Example 90: orders that are also BigOrders http://host/service/Orders?$filter=isof(NorthwindModel.BigOrder) http://host/service/Orders?$filter=isof($it,NorthwindModel.BigOrder) Example 91: orders of a customer that is a VIPCustomer http://host/service/Orders?$filter=isof(Customer,NorthwindModel.VIPCustomer) Geo Functions geo.distance The geo.distance function has the following signatures: Edm.Double geo.distance(Edm.GeographyPoint,Edm.GeographyPoint) Edm.Double geo.distance(Edm.GeometryPoint,Edm.GeometryPoint) The geo.distance function returns the shortest distance between the two points in the coordinate reference system signified by the two points’ geo.intersects The geo.intersects function has the following signatures: Edm.Boolean geo.intersects(Edm.GeographyPoint,Edm.GeographyPolygon) Edm.Boolean geo.intersects(Edm.GeometryPoint,Edm.GeometryPolygon) The geo.intersects function returns true if the specified point lies within the interior or on the boundary of the specified polygon, otherwise it returns false. geo.length The geo.length function has the following signatures: Edm.Double geo.length(Edm.GeographyLineString) Edm.Double geo.length(Edm.GeometryLineString) The geo.length function returns the total length of its line string parameter in the coordinate reference system signified by its SRID. Lambda Operators OData defines two operators that evaluate a Boolean expression on a collection. Both must be prepended with a navigation path that identifies a collection. 4.01 Services MUST support case-insensitive lambda operator names. Clients that want to work with 4.0 services MUST use lower case lambda operator names. The argument of a lambda operator is a lambda variable name followed by a colon (:) and a Boolean expression that uses the lambda variable name to refer to properties of members of the collection identified by the resource path. any The any operator applies a Boolean expression to each member of a collection and returns true if the expression is true for any member of the collection, otherwise it returns false. The any operator without an argumentreturns if the collection is empty.
Revision History Revision Date Editor Changes Made Working Draft 01 Michael Ralf Handl Transferred content from 4.0 Part 2 – URL Conventions Errata 3 Committee Specification Draft 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features 0608
Source of evidence Evidence of Impact Citation Study design Setting Source of sample Type of social protection Comparison Meeting basic needs Reducing poverty Employment Health access Mental health Berry & Smit (2011) South Africa; unknown if rural or urban 18 children with disabilities or chronic illness (recruited from tertiary care centres) Social assistance, targeted and mainstream Non-recipients with disabilities + Goldblatt (2009) Qualitative and urban South Africa 93 experts, including people with disabilities (recruited from clinics, grant offices) Social assistance, targeted None + No effect - Graham et al (2012) Mixed methods Urban South Africa 94 people with disabilities (population-based recruitment) Social assistance, targeted None + No effect Jelsma et al (2008) Urban and rural South Africa 305 people with cognitive, physical or sensory impairments (population-based recruitment) Social assistance, targeted Non-recipients with disabilities No effect Levine et al (2011) Namibia (national) 2003-2004 Namibia Household Income and Expenditures Survey Social assistance, targeted Non-recipients with disabilities + + Li et al (2013) Rural and urban China 826 individuals over 60 either bedridden or with dementia Insurance (pension), targeted None + Loyalka et al (2014) China (national) National Survey of Disabled Persons (2006) Social assistance and insurance, mainstream None + No effect Mixed Mitra (2008) Ecological study South Africa (national) General Household Surveys (2002-06), October Household Surveys (1998-99) Social assistance, targeted All people with disabilities in South Africa - Mitra (2010) South Africa (national) General Household Survey 2005 Social assistance, targeted Non-recipients with disabilities + - Palmer et al (2012) Vietnam (national) 27 households with a member with a disability Social assistance and insurance (health), mainstream None No effect Mixed Palmer (2014) Vietnam (national) 2006 Vietnam Household Living Standards Survey Insurance (health) Other recipients without disabilities Mixed + Vazquez et al (2011) Argentina, Brazil, Colombia 241 individuals with bipolar disorder (recruited from inpatient/outpatient programmes) Social assistance, targeted Non-recipients with disabilities - N.B. spaces indicate that particular study did not assess the given measure. Table 3: Impact of social protection on poverty, employment, health access and mental health
1. The requested Page is located at: 2. Currently the page states: Step 1: Choose the date that is best for your schedule. Dates for ODS in FY 16 (Oct 2015 - Sept 2016): DATE DATE GRADUATION DATE 16010 18-Oct-15 20-Nov-15 12-Feb-16 21-Feb-16 25-Mar-16 06-May-16​ 22-May-16 24-Jun-16​ 26-Jun-16 29-Jul-16 CLASS IS FILLED. NO MORE REQUESTS WILL BE TAKEN. 31-Jul-16 02-Sep-16 Annual Training ODS requests for FY-2016 will not be accepted until 14 Sept. 2015. 3. Change section to read: Step 1: Choose the date that is best for your schedule. Dates for ODS in FY-17 (1 Oct 2016 – 30 Sept 2017): CLASS TRAVEL START GRAD 17010 15-Oct-16 16-Oct-16 18-Nov-16 17020 11-Feb-2017 12-Feb-17 17-Mar-17 17030 29 –Apr-2017 30-Apr-17 2-Jun-17 3-Jun- 2017 4-Jun-17 7-Jul-17 17050 8-Jul-2017 9-Jul-17 11-Aug-17 17060 12-Aug- 2017 13-Aug-17 15-Sep-17 Annual Training ODS requests for FY-17 will not be accepted until 10 September 2016.
Absolute resource path and separate Host header Example : GET /path/service/People(1) HTTP/1.1 Host: myserver.mydomain.org:1234 Resource path relative to the batch request URI. Example : GET People(1) HTTP/1.1 Services MUST support all three formats for URLs of individual requests. Each body part that represents a single request MUST NOT include: authentication or authorization related HTTP headers Expect, From, Max-Forwards, Range, or TE headers Processors of batch requests MAY choose to disallow additional HTTP constructs in HTTP requests serialized within body parts. For example, a processor may choose to disallow chunked encoding to be used by such HTTP requests. Example 98: a batch request that contains the following individual requests in the order listed A request A change set that contains the following requests: Insert entity (with Content-ID = 1) Update entity (with Content-ID = 2) A second query request Note: For brevity, in the example, request bodies are excluded in favor of English descriptions inside <> brackets and OData-Version headers are omitted. Note also that the two empty lines after the Host header of the GET request are necessary: the first is part of the GET request header; the second is the empty body of the GET request, followed by a CRLF according to . POST /service/$batch HTTP/1.1 Host: host OData-Version: 4.0 Content-Type: multipart/mixed; Content-Length: ### --batch_36522ad7-fc75-4b56-8c71-56071383e77b Content-Type: application/http GET Host: host --batch_36522ad7-fc75-4b56-8c71-56071383e77b Content-Type: multipart/mixed; --changeset_77162fcd-b8da-41ac-a9f8-9357efbbd Content-Type: application/http Content-ID: 1 POST /service/Customers HTTP/1.1 Host: host Content-Type: application/json Content-Length: ### <JSON representation of a new Customer>
Virginia’s Training Center to Community Move Process END at 12 months PMM Reporting Active Move Status Week 1 Initial Pre-Move Meeting Week 2 Individual/AR/CSB reviews providers Weeks 3,4 and 5 Provider Tours Provider Information Requests Week 6 Provider Pre-Move Meeting Week 7 Day Visits Week 8 Evening Week 9 Provider Training and Overnight Visits Week 10 Final Pre-Move Meeting Week 11 Preparation for Moving Week 12 Moving Post-Move Monitoring
TC Days 3, 10 and 17 PMM Report to CIM, OLS, OHR, Provider, and CSB OLS within 45 days of move PMM shared with CIM, Provider, and CSB, if appropriate CSB by day 7 and monthly for 12 months 1st CSB PMM and monthly notes to Training Center PMMC CRC Referral as needed Provider training and supports OHR within 30 and 90 days. Then as needed PMM Report to OLS, CIM and CSB (to share w/provider)
Acknowledgments The following individuals were members of the OASIS OData Technical Committee during the creation of this specification and their contributions are gratefully acknowledged: Howard Abrams (CA Technologies) Ken Baclawski (Northeastern University) Jay Balunas (Red Hat) Stephen Berard (Schneider Electric Industries SAS) Mark Biamonte (Progress Software) Matthew Borges (SAP SE) Edmond Bourne (BlackBerry) Joseph Boyle (Planetwork, Inc.) Peter Brown (Individual) Antonio Campanile (Bank of America) Pablo Castro (Microsoft) Axel Conrad (BlackBerry) Robin Cover (OASIS) Erik de Voogd (SDL) Yi Ding (Microsoft) Diane Downie (Citrix Systems) Patrick Durusau (Individual) Andrew Eisenberg (IBM) Chet Ensign Davina Erasmus (SDL) George Ericson (Dell) Colleen Evans (Microsoft) Fam (IBM) Senaka Fernando (WSO2) Josh Gavant (Microsoft) Brent Gross (IBM) Zhun Guo (Individual) Kumar GVN (CA Technologies) Stefan Hagen (Individual) Ralf Handl (SAP SE) Barbara Hartel (SAP SE) Hubert Heijkers (IBM) Jens Hüsken (SAP SE) Evan Ireland (SAP SE) Gershon Janssen (Individual) Ram Jeyaraman (Microsoft) Ted Jones (Red Hat) Jordan (IBM) Stephan Klevenz (SAP SE) Gerald Krause (SAP SE) Nuno Linhares (SDL) Paul Lipton (CA Technologies) Susan Malaika (IBM) Ramanjaneyulu Malisetti (CA Technologies) Neil McEvoy (iFOSSF – International Free and Open Source Solutions Foundation) Stan Mitranic (CA Technologies) Dale Moberg (Axway Software) Graham (BrightstarDB Ltd.) Farrukh Najmi (Individual) Shishir Pardikar (Citrix Systems) Sanjay Patil (SAP SE) Nuccio Piscopo (iFOSSF – International Free and Open Source Solutions Foundation) Michael (Microsoft) Ramesh Reddy (Red Hat) Robert Richards (Mashery) Sumedha Rubasinghe (WSO2) James Snell (IBM) Jeffrey Turpin (Axway Software) John Willson (Individual) John Wilmes (Individual) Christopher Woodruff (Perficient, Inc.) Martin Zurmuehl (SAP SE)
Revision History Revision Date Editor Changes Made Working 01 2016-06-22 Michael Pizzo Transferred content from OData 4.0 Part I - Protocol Errata 3 Committee Specification Draft 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features Schema Versioning Preference omit-values $compute system option Indexing into Ordered Collections Deep Update Improved referencing in batch requests Committee Specification Draft 02 2017-06-20 Michael Pizzo Ralf Handl More 4.01 features Set-based operations JSON Batch format CSDL JSON format
Services SHOULD NOT change their data model depending on the authenticated user. If the data model is user or usergroup dependent, all changes MUST be safe changes as defined in this section when comparing the full model to the model visible to users with restricted authorizations.
Acknowledgments The following individuals were members of the OASIS OData Technical Committee during the creation of this specification and their contributions are gratefully acknowledged: Howard Abrams (CA Technologies) Ken Baclawski (Northeastern University) Jay Balunas (Red Hat) Stephen Berard (Schneider Electric Industries SAS) Mark Biamonte (Progress Software) Matthew Borges (SAP SE) Edmond Bourne (BlackBerry) Joseph Boyle (Planetwork, Inc.) Peter Brown (Individual) Antonio Campanile (Bank of America) Pablo Castro (Microsoft) Axel Conrad (BlackBerry) Robin Cover (OASIS) Erik de (SDL) Yi Ding (Microsoft) Diane Downie (Citrix Systems) Patrick Durusau (Individual) Andrew Eisenberg (IBM) Chet Ensign (OASIS) Davina Erasmus (SDL) George Ericson (Dell) Colleen Evans (Microsoft) Jason Fam (IBM) Senaka Fernando (WSO2) Josh Gavant (Microsoft) Brent Gross (IBM) Zhun Guo (Individual) Anila Kumar GVN (CA Technologies) Stefan Hagen (Individual) Ralf Handl (SAP SE) Barbara Hartel (SAP SE) Hubert Heijkers (IBM) Jens Hüsken (SAP SE) Evan Ireland (SAP SE) Gershon Janssen (Individual) Ram Jeyaraman (Microsoft) Ted (Red Hat) Diane Jordan (IBM) Stephan Klevenz (SAP SE) Gerald Krause (SAP SE) Nuno Linhares (SDL) Paul Lipton (CA Technologies) Malaika (IBM) Ramanjaneyulu Malisetti (CA Technologies) Neil McEvoy (iFOSSF – International Free and Open Source Solutions Foundation) Stan Mitranic (CA Technologies) Dale Moberg (Axway Software) Graham Moore (BrightstarDB Ltd.) Farrukh Najmi (Individual) Shishir Pardikar (Citrix Systems) Sanjay Patil (SAP SE) Nuccio Piscopo (iFOSSF – International Free and Open Source Solutions Foundation) Michael Pizzo (Microsoft) Ramesh Reddy (Red Hat) Robert Richards (Mashery) Sumedha Rubasinghe (WSO2) James Snell (IBM) Jeffrey Turpin (Axway Software) John Willson (Individual) John Wilmes (Individual) Christopher Woodruff (Perficient, Inc.) Martin Zurmuehl (SAP SE)
Revision History Revision Date Editor Changes Made Working 01 2016-06-22 Michael Pizzo Transferred content from OData 4.0 Part I - Protocol Errata 3 Committee Specification Draft 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features Schema Versioning Preference omit-values $compute system query option Indexing into Ordered Collections Deep Update Improved referencing in batch requests Committee Specification Draft 02 2017-06-20 Michael Ralf Handl More 4.01 features Set-based operations JSON format CSDL JSON format Committee Specification Draft 03 2017-09-28 Michael Ralf Handl Incorporated review feedback Added nested query options for $select Added nested parameter alias value assignments within $expand and $select Simplified implicit parameter aliases for function (import) calls
Revision number V0.1 Revision Date Status (Final (F), Draft (D), Revised Draft (RV)) Dissemination level (Public (PU), Restricted to other program participants (PP), Restricted to a group specified by the consortium (RE), Confidential for consortium members only (CO)) Confidential – Initial draft - Consortium only. Document History Revision Date Modification Author 0.1 Initial draft Approvals Name Organisation Date Signature (initials) Coordinator WP Leaders