Sub-factor 1a – Technical Experience Clause Samples

Sub-factor 1a – Technical Experience. The compactness of the NW development/release cycles (software drops and integration activities occurring twice yearly tied to major Army Capability Integration Evaluation (CIE) / Army Warfighter Assessment (AWA) events to validate NW performance) and short notice production/fielding timelines require the contractor to provide a stable/agile workforce with the required technical skill sets. The Offeror shall explain how they will meet the PWS requirements (PWS Section C.3.0, C.3.1, C.3.2, C.3.3 and associated sub paragraphs) based on the Offeror’s technical experience in the last three (3) years providing contract support in the following five (5) competency areas:  Soldier-borne equipment integration of hardware and software;  Software Development/Coding/Integration on Android operating system mobile handheld devices using software sprints, Nett Warrior or Android Tactical Assault kit (ATAK) software development kit and agile software development techniques;  Integrating mobile handheld devices with PRC154A, PRC 152A or other Tactical radios, and developing Variable Message Format (VMF) message software that runs on mobile handheld devices that is interoperable with Joint Battle Command-Platform (JBCP) / Joint Capabilities Release (JCR) mission command systems;  Leveraging commercial technologies or software and migrating onto or integration with Army and U.S. Army Special Operations Command (USASOC) dismounted mobile handheld devices; and  Leveraging DoD Risk Management framework and assisting in obtaining Soldier-borne equipment accreditation for Secret use. In order for a contract effort (related to competency stated above in this section) to be considered under this factor, the proposal must confirm that the prime or subcontractor that has experience in the competency areas identified will support the same competency areas if the Offeror receives the resultant award.
View Source

Related to Sub-factor 1a – Technical Experience

  • TECHNICAL EVALUATION (a) Detailed technical evaluation shall be carried out by Purchase Committee pursuant to conditions in the tender document to determine the substantial responsiveness of each tender. For this clause, the substantially responsive bid is one that conforms to all the eligibility and terms and condition of the tender without any material deviation. The Institute’s determination of bid’s responsiveness is to be based on the contents of the bid itself without recourse to extrinsic evidence. The Institute shall evaluate the technical bids also to determine whether they are complete, whether required sureties have been furnished, whether the documents have been properly signed and whether the bids are in order. (b) The technical evaluation committee may call the responsive bidders for discussion or presentation to facilitate and assess their understanding of the scope of work and its execution. However, the committee shall have sole discretion to call for discussion / presentation. (c) Financial bids of only those bidders who qualify the technical criteria will be opened provided all other requirements are fulfilled. (d) AIIMS Jodhpur shall have right to accept or reject any or all tenders without assigning any reasons thereof.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • Teaching Experience Recognized Years of Experience: Uncredited Experience:

  • Multi-year Planning Targets Schedule A may reflect an allocation for the first Funding Year of this Agreement as well as planning targets for up to two additional years, consistent with the term of this Agreement. In such an event, the HSP acknowledges that if it is provided with planning targets, these targets: a. are targets only, b. are provided solely for the purposes of planning, c. are subject to confirmation, and d. may be changed at the discretion of the Funder in consultation with the HSP. The HSP will proactively manage the risks associated with multi-year planning and the potential changes to the planning targets; and the Funder agrees that it will communicate any changes to the planning targets as soon as reasonably possible.

  • Power Factor Design Criteria (Reactive Power A wind generating plant shall maintain a power factor within the range of 0.95 leading to 0.95 lagging, measured at the Point of Interconnection as defined in this LGIA, if the ISO’s System Reliability Impact Study shows that such a requirement is necessary to ensure safety or reliability. The power factor range standards can be met using, for example without limitation, power electronics designed to supply this level of reactive capability (taking into account any limitations due to voltage level, real power output, etc.) or fixed and switched capacitors if agreed to by the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, or a combination of the two. The Developer shall not disable power factor equipment while the wind plant is in operation. Wind plants shall also be able to provide sufficient dynamic voltage support in lieu of the power system stabilizer and automatic voltage regulation at the generator excitation system if the System Reliability Impact Study shows this to be required for system safety or reliability.