Brand_Name_Redacted.pdf
PDF 98 KB Posted
- Attached to
- Synopsys Software Maintenance Federal contract opportunity
- Solicitation number
- HQ0727-17-T-0003
- Issued by
- Defense Microelectronics Activity
About this file
Brand Name Restriction
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| HQ0727-17-T-0003.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
9 November 2016
MEMORANDUM FOR: DMEA/MEEC
FROM: DMEA/MEAB
SUBJECT: Brand-Name/Single Source Justification
1. My office is requesting software maintenance for the Synopsys Design Tools Environment.
2. The Synopsys Design Tools Environment provides a UNIX based design environment for digital hardware design, simulation, and synthesis for complex Application Specific Integrated Circuit (ASIC) and Field Programmable Gate Array (FPGA) designs. Continued maintenance of this software system is necessary to support DMEA mission and advanced microelectronics technology application programs. Software maintenance includes software licensing, program updates, help desk and customer support for the software.
The Synopsys Design Tools Environment consists of the following software tools:
Product Number Synopsys Product Name Qty
2661-0 DC Expert Perpetual NE Maintenance 1
2673-0 Library Compiler Perpetual NE Maintenance 1
2681-0 VHDL Compiler Perpetual NE Maintenance 2
3160-0 Design Vision Perpetual NE Maintenance 2
2665-0 Design Analyzer Perpetual NE Maintenance 1
2671-0 HDL Compiler Verilog Perpetual NE Maintenance 1
2925-0 DesignWare Library 1
3335-0 VCS MX 2
3. This justification is for a brand-name acquisition.
DMEA has a perpetual license for the software tools that makeup the Synopsys Design Tools Environment. DMEA has been acquiring software maintenance for the Synopsys Design Tools Environment for over 10 years.
DEFENSE MICROELECTRONICS ACTIVITY
4234 54TH STREET
MCCLELLAN, CALIFORNIA 95652-2100
The Synopsys Design Tools Environment integrates different Synopsys tools into a single environment to support all steps of the design process. If a program error, flaw, failure, or fault occurs during the design flow process, technical support can be obtained for the Synopsys Design Tools Environment and all Synopsys programs within the environment.
Use of non-Synopsys programs would introduce foreign, potentially non-compatible source programming language into the Synopsys Design Tools Environment. An adequate level of technical support for the Synopsys Design Tools Environment containing foreign software would be difficult to obtain. Lack of adequate technical support for the design flow process will create a significant technical risk.
DMEA uses the Synopsys Design Tools Environment specifically for ASIC designs targeting the DMEA ARMS foundry. Files for these process are written in a proprietary language understood by all the software tools in the Synopsys Design Tools Environment.
A different tool would not understand the proprietary language, which would cause translation errors between tools in the design flow to occur. The translation errors, if left unchecked, will ultimately lead to ASIC design mistakes. In order to mitigate mistakes and errors, the ASIC process files would need to undergo quality control reviews. The amount of time required for DMEA foundry design engineers to perform quality control reviews would be a significant schedule risk.
The passage of time has allowed for DMEA foundry personnel to master the software tools in the Synopsys Design Tools Environment. DMEA foundry personnel will be unfamiliar with different software tools, as it will contain different software characteristics. In order for DMEA foundry design engineers to master the new software tools, a contractor would need to train every design engineer. The amount of training required for DMEA foundry design engineers to master a new tool would be a significant cost risk.
4. Based on previous contract pricing, the anticipated dollar value of this procurement is for 12 months of software maintenance.
5. The following contract awards were brand name acquisitions of software maintenance for the Synopsys Design Tolls Environment:
H94003-06-P-6003 H94003-08-P-8006 H94003-09-P-9004 H94003-10-P-1009 H94003-11-P-1104 H94003-12-P-1201 H94003-13-P-1302
HQ0727-14-C-1404
HQ0727-15-P-1509
HQ0727-16-P-1608
6. Market research consisted of:
A sources sought notice was posted on FBO.gov. No responses from industry were received.
Articles available on the internet explained the importance of software maintenance on design tools. Design tools are very expensive, essential to research and development work, and must be properly maintained to ensure that commercial designs are completed on schedule. Market research found that larger design automation companies constantly acquire smaller design automation companies because the design technology of smaller companies can be adapted into the design environment. These enhancements are added to the design environment via software maintenance.
7. I am aware that the contracting officer, and not the requiring activity, is the final authority for determining the adequacy of any sole source justification before contract placement.
8. If you have any further questions regarding this letter, please feel free to contact the undersigned at .
Project/Program Engineer PE Supervisor
DMEA J&A 17-03
Brand Name Restriction
Background: FAR 11.105, Items Peculiar to One Manufacturer, states: “Agency requirements shall not be written so as to require a particular brand-name, product, or a feature of a product, peculiar to one manufacturer, thereby precluding consideration of a product manufactured by another company, unless
(1) The particular brand name, product, or feature is essential to the Government’s requirements, and market research indicates other companies’ similar products, or products lacking the particular feature, do not meet, or cannot be modified to meet, the agency’s needs;
(2)(ii) The basis for not providing for maximum practicable competition is documented in the file (see 13.106-1(b)) or justified (see 13.501) when the acquisition is awarded using simplified acquisition procedures.
(3) The documentation or justification is posted for acquisitions over $25,000. (See 5.102(a)(6).)”
Current Action: This requirement is for annual software maintenance for the Synopsys Design Tools Environment.
This product is essential to the Government’s requirements, and market research indicates other companies’ similar products, or products lacking the particular feature, do not meet, or cannot be modified to meet, the agency’s needs IAW FAR 11.105(1).
The basis for not providing for maximum practicable competition is documented in Tab 6 of the contract file IAW FAR 13.106-1(b).
The brand name documentation will be posted on FBO.gov with the solicitation IAW FAR 5.102(a)(6).
Based on the above, brand name restriction to Synopsys software is in accordance with the FAR and is in the in best interest of the Government.
Matthew Duane Contracting Officer
| Brand Name Letter 7M17A301 |
| Brand Name Restriction |
File details come from the government source that posted it. Updated .