EWPMTDraftSectionL.pdf

INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFEROR OR RESPONDENTS

1 General

The Offeror shall submit (electronically) a proposal that responds to the Request for Proposal (RFP) and the requirements stated in Section L, which presents the Offeror‟s proposed approach and capabilities in meeting the programs requirements and objectives. Proposals shall be submitted via the Army Single

Face to Industry (ASFI) in the files set forth below. The URL for the ASFI is https://acquisition.army.mil/asfi?ASFI_FAQ.cfm. Upon accessing this web page, look for the tab titled

“ASFI for Industry”. Under the “ASFI for Industry” tab you will be able to: check for business opportunities by clicking on the Contract Opportunities Search link, receive notifications by clicking on the Vendor Notification Service link. Vendor cannot submit responses via the Vendor Bid History.

Vendors can only view “high level” information regarding the response. No registration is needed for the

Vendor to browse for business opportunities. For the Vendor to receive notifications he merely needs to provide company Commercial and Government Entity (CAGE) Code and E-Mail address. To submit a response the Vendor must provide the CAGE Code and Marketing Partner Identification Number

(MPIN). Your company must be registered and current in the Central Offeror Register (CCR) in order to submit bids/proposals on ASFI. Please be advised that hard copies of the solicitation will not be made available. You must download solicitation documents from the ASFI. Instructions on how to use ASFI to include; receiving notification, submitting and uploading bids or proposals, formatting and system requirements are provided at https://acquisition.army.mil/asfi?ASFI_FAQ.cfm. For Technical ASFI assistance please e-mail help desk at ASFI@conus.army.mil. WARNING: Please do not wait until the last minute to submit your proposals! To avoid submission of late proposals, we recommend the transmission of your proposal file 24 hours prior to the required proposal due date and time.

2 Proposal Preparation Instructions

Microsoft Office Professional 2007 and MS Project 2007 or later shall be used to create the files. All graphics shall be compatible with MS PowerPoint 2000. All .MPP files shall be compatible with MS

Project 2007. All information pertaining to a particular file shall be confined to that file. The Cost information shall be contained in an EXCEL file (RFP Section J) with all formulas and calculations included. The titles for each file, along with the references are shown in the paragraph 2.1 below. Each file shall contain the applicable proposal information in the referenced paragraph. All proposal submissions shall be submitted with one-inch margins (top, bottom, left and right), single column read left to right. Line spacing shall be set at no less than single space. The top, bottom, left and right margins shall be a minimum of one inch each. All text shall be 10 point Times New Roman style font. Tables and drawings may be 8 point Arial font. Characters shall be set at no less than normal spacing and 100% scale. Graphics may be submitted in black & white, half-tone or in color, in font sizes sufficient for all information to be read or reproduced without difficulty (but in no case less than 6 point Arial). Pages that exceed the margin, font or total page limit will not be evaluated. Page count will NOT be based upon the numbers of pages, printed but rather dictated by the number of pages in a print layout view in the application based upon the above-prescribed document settings. Counting pages in the order they appear for viewing will make up the page count.

https://acquisition.army.mil/asfi?ASFI_FAQ.cfm https://acquisition.army.mil/asfi?ASFI_FAQ.cfm

Proposal Page Limitations and Constraints:

Technical Approach section shall not exceed 80 pages, including, graphs, tables, drawings, and any other attachments submitted with proposals and not specifically excluded by this solicitation, will be counted against the page limitation requirement.

Appendices below, to be submitted with Volume 1 Technical Performance are excluded from the page count limitation. Information provided in the appendices shall be factual and directly associated with that topic and NOT used as a means for submitting additional information in support of the Technical

Approach.

A Cross Reference Matrix, Index, and Glossary shall be included in Volume which cross referenced the government‟s requirements, e.g. the PWS-G, PBS-G, IMP to the essential and corresponding proposal elements; an index for the proposal and a glossary of terms (including acronyms) contained within the offeror‟s proposal. The Cross Reference Matrix, Index, and Glossary are not included in the page count.

The use of „Hyperlinks‟ within the proposal or across proposal volumes and appendices is NOT allowed.

PROPOSAL ORGANIZATION

The Offeror‟s proposal shall consist of:

Volume I: Technical Proposal

Appendices:

Appendix 1 – Performance Work Statement – Contractor (PWS-C):

Appendix 2 – Performance Work Statement Task Order 1 (PWSTO1)

Appendix 3 – Integrated Master Schedule (IMS)

Appendix 4 – Contractor Work Breakdown Structure (CWBS)

Appendix 5 – Performance Based Specification (PBS)

NOTE: Information provided in the Appendices shall be directly relevant to that

Appendix and shall not be a continuation of the Offerors proposal contained in

Technical Performance. If the government deems that the information being provided is non-relevant, that information will not be evaluated.

Volume II: Past Performance Proposal

Volume III: Cost Proposal

Volume IV: Small Business Participation Proposal

All information shall be confined to the appropriate volume. The Offeror shall confine the submissions to essential matters, sufficient to define the proposal and to provide an adequate basis for evaluation. Files shall not contain classified data. The Cost Volume shall be submitted as a separate Excel file (with all formulas and calculations intact and no read only or password protected files) and be clearly annotated.

3 Proposal

Proposal Files –

All of the proposal files shall be compressed (zipped) into one file entitled proposal.zip using WinZip version 6.2 or later, or as separate uploads in their native format, i.e., docx, xlsx, pdf, etc. Up to five (5) files can be uploaded at one time. The combined size of the five (5) files cannot exceed 10Mb. Break your attachments into smaller files or use the upload utility multiple times if your files exceed the 10Mb size limit. **Please note - Self extracting .exe files are no longer accepted. Microsoft Office Professional 2007 and Microsoft Project 2007 shall be used to create the respective files (except as otherwise noted below).

All information shall be confined to the appropriate file. The use of hyperlinks in proposals is prohibited.

Offerors shall submit proposal files under the following associated filenames and file formats: Failure to submit any of these items to the place required, by the time required, will be subject to late submission rules.

Alternative proposals are NOT allowed.

3.1 Proposal File Structure

Volume Title Filename Page Limit

I Technical Factor OfferorName-Tech.doc 80 pages not including the

Appendices

Tech Approach Sub-Factor

Management Sub-Factor

Appendix 1: PWS-C OfferorName-PWS-C.doc

No page limit

Appendix 2: PWSTO1-C OfferorName-PWSTO1-C

No page limit

Appendix 3: IMS OfferorName-IMS.mmp

No page limit

Appendix 4: CWBS OfferorName-CWBS.exe No page limit

Appendix 5: PBS-C OfferorName-PerfSpec.doc No page limit

II Past Performance OfferorName-Past-Perf- -

Factor. doc

35 pages

III Cost Factor OfferorName-Cost-

Factor.doc

No page

IV Small Business

Participation Plan Factor

OfferorName-SmallBus-

Factor.doc

No page

V Solicitation Documents OfferorName-SF33.pdf No page

NOTE: Files shall NOT be ‘password’ or ‘read only’ protected.

Offerors are encouraged to submit all files in a compressed form, i.e. “Zipped” to reduce transmission time.

3.2 Classified Documents - Proposal files transmitted via the ASFI shall not contain classified information or data. Delivery of the Classified Proposal elements is subject to the same date and time of delivery as for the Unclassified proposal itself. Classified proposal material shall be provided on two (2) identical CD ROMS, suitably marked as being classified material, and delivered to the address listed below.

The Offeror shall consolidate classified material into the „topic‟ appropriate sections and provide it as separate appendices:

Each entry in the classified addendum shall be cross-referenced to the applicable unclassified proposal volume, page number, and paragraph number to which it applies. Similarly, a reference/footnote shall be placed in the unclassified volume where the classified information applies, i.e. the page and paragraph numbers within the appendix as to where it can be found.

Any classified material must be submitted as a separate attachment, marked and transmitted in accordance with the National Industrial Security Program Operating Manual (NISPOM) procedures for safeguarding Classified Information, DOD 5220.22-M.

Classified material shall be sent in accordance with NISPOM requirements, to the address listed below. Submission of the classified portions of the Offeror‟s proposal is subject to the same proposal due date and delivery time requirements as for the unclassified proposal.

PM, Electronic Warfare

ATTN: SFAE-IEW&S-EW (Security)

Bldg 4504

Aberdeen Proving Grounds, MD 21005

(410) 306-4144 (voice)

POCs: Alison Powell 410-306-4144 or Irene Booth 410-306-4145

The Offeror shall have an approved SECRET facility clearance and security infrastructure for safeguarding classified material and property in effect based on the IEWS Security Classification Guide, DD Form 254 and NISPOM requirements. The following information must be provided via email to

Alison.t.powell.civ@mail.mil to verify the facility clearance: Contractor Name, Cage Code, Corporate

Mailing Address, Classified Mailing Address, and Security Office Information including Name, Title, E-mail and telephone number.

mailto:Alison.t.powell.civ@mail.mil

3.3 Proposal Format - The proposal shall be clear, concise, cohesive and logically organized. It shall include sufficient detail for effective evaluation of the Offeror‟s proposal. All information shall be confined to the appropriate file. The Offeror‟s proposal shall be complete, cohesive, and be confined to essential matters, sufficient to define the offeror‟s proposed approach in meeting the government requirements and to provide an adequate basis for government evaluation. The proposal shall provide detailed explanations, and address how the Offeror intends to meet all requirements stated in the RFP.

Offerors shall assume that the Government has no prior knowledge of the proposed technology, the

Offeror‟s capabilities and prior performance on Government contracts, facilities and experience. The

Offeror‟s proposal, in its totality, will be evaluated solely on the information presented.

3.3.1 Indexing/Cross Referencing/Table of Contents - Each volume shall contain a detailed table of contents delineating the subparagraphs within that volume to the proposal content. Indices and cross-referencing shall be included in the appropriate volumes, and across the proposal, to ensure that the

Offeror has addressed all required elements in the proposal and compliance with the Government‟s requirements. The Index, Table of Contents and Cross-Reference Matrix are not included in the page count

3.3.2 Cross Referencing - Each volume shall be prepared on a stand-alone basis, so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal.

The proposal shall include an RFP Cross-Reference Matrix, clearly identifying where requirements are addressed in the proposal. The matrix shall cross-reference each major proposal paragraph, including attachments by paragraph number to the respective paragraph in the RFP. Cross-referencing to PWS-

G/PWS-C, PBS-G/PBS-C, the CWBS elements, and the Integrated Master Schedule (IMS) elements shall be provided.

3.3.3 Glossary of Abbreviations and Acronyms - Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. The glossary is not included in the page count.

3.3.4 Tables & Drawings - Tables, charts, graphs and drawings may be used wherever practical to depict organizations, antennas and layout, implementation schedules, plans, etc. and will be included in the page count. For tables, charts, graphs and drawings the file format shall be Power Point or Word and the font shall be no smaller than 6 point. Tables, figures and drawings may be embedded in the text body.

Tables, figures, and drawings not embedded in the text body, i.e., spanning multiple pages shall be 11 inch x 17-inch foldouts and will be counted as two pages. Scanned figures (e.g. photographs), drawings

(e.g. CAD/CAM), etc. provided as an embedded or standalone JPEG image files are acceptable provided that the image quality is sufficiently legible for evaluation.

4 Proposal Content - The Offeror shall document the complete approach towards meeting the

Government‟s requirements. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of the proposal. It is incumbent on the offeror to identify and address both the explicit as well as implicit requirements contained and provided in the PBS, PWS, and IMP in the proposed approach and proposal content.

4.1 Volume I Technical Performance: The Offeror shall propose a design and technology development approach for the EWPMT system that complies with the requirements of the TO1 PWS and the EWPMT Performance Based Specification designated as Capability Drop 1 (CD 1). The Technical

Proposal shall consist of the following sections:

Section 1 - Technical Approach

Section 2 - Management

Proposals must contain supporting rationale for any statements relating to proposed performance.

Unsupported claims or mere statements of compliance with contractual requirements are insufficient. No assumptions will be made regarding areas that are not addressed in the Offeror‟s written proposal.

4.1.1 Subfactor 1. Tech Approach. The Offeror shall describe its Software Development Processes, Schedule, Training and Supportability approach for the requirements stated in Task Order 1 PWS and all requirements stated in PBS-G. At a minimum, the Offeror shall provide the following as part of its proposal:

4.1.1.1 The proposal shall describe the Offeror‟s overall EWPMT approach for developing all requirements from Capability Drop 1 through 6 as stated in PBS-G. This section shall cover PWSTO-G section 3.

4.1.1.2 Provide a detailed analysis of how each of the Capability Drop 1 requirements in the PBS-G will be met. This section shall cover PWSTO-G section 3.

4.1.1.3 The proposal shall describe how the Offeror‟s modular open systems approach as covered in the

Governement PWS paragraphs 1.2, 3.2.1 and 3.3 will enable the Offeror to implement a technical strategy which addresses the following:

How the modular design (1) defines key interfaces using (2) uses widely-supported, consensus-based (e.g., open) standards that are published and maintained by a recognized industry standards organization (e.g. Open Standards).

Explanation of how the modular open systems approach supports benefits such as reconfigurability, portability, interoperability, technology insertion, vendor independence, reusability, scalability, and commercial product based maintainability.

A design description that identifies the reuse of existing COTS, GOTS and proprietary components and their respective open/proprietary interfaces.

A description of the strategy for maintaining the currency of technology (e.g., through

COTS insertion, technology refresh strategies, and other appropriate means).

Identify common Ozone widgets and their interactions

4.1.1.4 In the system design or architecture, the Offeror will include a description on the use of Service

Oriented Architecture (SOA) principles for interoperability and operational agility at the enterprise level and identify specific open standards used to implement SOA. Describe the

System web services and how they will interface with the web services within DCGS-A, Mission Command and other enterprise wide applications. This section shall cover PWSTO-G section 1.2, 3.3.1.

4.1.1.5 Describe approach and rationale to utilizing proprietary data to which other than Government

Purpose Rights or unlimited data rights may apply, the impact of any limited or restricted rights on the ability of the Government to fulfill stated program goals. This section shall cover

PWSTO-G section 3.4.6

4.1.1.6 If Ozone Widget Framework is to be employed, provide an analysis demonstrating that thin client approach allows the Modeling and Simulation of EMOE with in a 3D visualization and provides the user interaction with the visualizer for EW Mission Planning.

4.1.1.7 Describe approach to partner with government agencies (i.e. CERDEC and CECOM SEC) to leverage synchronized development and software release and sustainment schedules GOTS/GPR modules and components in use in other programs (e.g. at a minimum the offerer shall leverage the Communications Effects Simulator (CES), the Spectrum Planning Advisor (SPA), and the

Spectrum Knowledge Repository (SKR) – all modules of the Electromagnetic Battle Manager, EMBM). The Offeror shall demonstrate how its architecture, development plan, and schedule will reduce cost, schedule, and performance risk to the program. This section shall cover

PWSTO-G section 3.4.6.

4.1.1.8 Describe approach to working with US Army CERDEC laboratories to verify and validate interfaces with unclassified and classified spectrum data sources (eg SXXI, ARAT, SKR, JDSR), for use within product. Similarly the offeror shall describe how it will work with US

Army CERDEC to verify that analytical models (e.g. propagation, interference, deconfliction) performed within their product provide precision and results corresponding to other tools in use by DOD Spectrum Managers. This section shall cover PWSTO-G section 3.4.6.

4.1.1.9 Provide a detailed description of the offeror‟s test program and describe how the proposed test program supports demonstration and certification of the requirements as described in the

Government PBS. The Offeror shall specify how they plan to collaborate with government components within US Army CERDEC and CECOM to leverage existing capabilities and facilities to perform demonstrations and interoperability testing with DCGS-A and Mission

Command System Integration Laboratories (SILs). The Offeror shall provide and discuss its

Master Test Schedule (MTS) that clearly depicts all build, integration and test efforts which are expected to take place, whether software, hardware, including systems integration. The Offerror shall describe a Master Test Plan (MTP) that is consistent with support of the MTS. This section shall cover PWSTO-G section 3.6.

4.1.1.10 Describe how the architecture will process classified data and meet IA requirements identified in

DoDD 8500.1. Describe the integration of the IA process into the systems engineering process.

Address security vulnerabilities in COTS/reuse components. The Offeror shall state how the interfaces support an overall Information Assurance strategy. This section shall cover PWSTO-

G section 3.5.3.

4.1.2 Subfactor 2. Management. The Offeror shall describe its approach to managing the efforts required for this contract. Describe approach to ensuring all contract activities within scope are planned, executed and reported according to plan. Describe approach for reporting progress against plans to include identification of the technical and programmatic risks and the proposed mitigation plan for medium and high risks. Identify process for addressing corrective actions.

Identify and describe tools which will be leveraged in support of program management efforts.

Include probability of occurrence and consequence of risk. This section should cover the

PWSTO-G section 3.4.

4.1.2.1 Identify subcontractors used, why they were selected, scope of work assigned to each, and approach to managing subcontractors to ensure quality and performance. Provide a list of offerors and subcontractors ISO, DCMA, security, CMMI or other certifications. Provide an outline of how the effort required by the solicitation will be assigned for performance within the offerors corporate entity and among the proposed subcontractors. The information provided for the prime offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, DUNS Number and type of work to be performed by citing the

Government or Offerors PWS-C subparagraph number Major subcontractor is defined as a subcontractor anticipated to perform more than 10 percent of the total contract. This section shall cover PWSTO-G section 3.4.1.

4.1.2.2 Discuss methods for attracting, hiring, developing, training, and retaining a workforce with all the skills and knowledge necessary to support the EWPMT Program requirements. Describe the approach to provide the training and mentoring necessary to keep the work force up-to-date on current technologies, trends, and best business practices. The plan shall also take into consideration the impact of an environment of fluctuating workloads, demanding schedules, and complex project issues. This section shall cover PWSTO-G section 3.4.1.

4.1.2.3 Provide a thorough description of the Configuration Management Program the Offeror will use for EWPMT. This section shall cover PWS-G section 3.4.8.

4.1.2.4 Describe any previous CMMI or equivalent model-based process maturity appraisals performed. As a part of this description, Offerors shall identify the organizational entity and location where the appraisal was performed, the type of evaluation, the organization performing the evaluation, and the level earned.

4.1.2.5 Describe Quality Assurance procedures and activities they will use to help ensure that the

EWPMT exhibits high quality. This section shall cover PWSTO-G section 3.5. The Offeror shall describe their software metrics to address:

Growth and stability regarding delivery of the required capability.

Product quality regarding delivered products to meet the user‟s need without failure, as reflected in associated requirements documents.

Software development performance regarding the capabilities to meet documented program requirements.

Technical adequacy regarding software reuse, programming languages, and use of standard data elements.

4.1.2.6 Provide a description of the Offerors approach to its training courses and products. This section shall cover PWSTO-G section 3.7.4.

Describe the approach on development of a EWPMT train-the trainer course to the government and its support contractors that enable the government to assume instructional responsibility for conducting standardize training at an Army training site.

Describe the approach to developing a EWPMT training product that is scenario-based, adaptive, and/or collaborative in nature.

Describe the approach on developing and delivering an embedded training product in accordance with TRADOC Pamphlet 350-37, 9 June 2003.

Describe the approach to developing a computer based and web-based interactive multimedia instructions that comply with the Joint Advanced Distributed Learning

Initiative.

Describe the approach for Army Leader/Planner course development.

Describe the approach for Army maintainer's course development.

Describe the approach for Field Software Engineer (FSE) course development.

4.1.2.7 Discuss the program Integrated Mater Schedule (IMS), which meets program requirements. The detailed schedule(s) shall be submitted in Appendix 3 and 4. The Offeror shall describe in detail how the proposed schedule shall meet or beat the timelines for System delivery. The IMS shall indicate a logical, systematic approach to program execution, identify dependencies and realistic timelines for all events. Slack times should be indicated as well identification of the critical path.

The IMS must be consistent with the contractor‟s Work Breakdown Structure (WBS). This section shall cover PWSTO-G sections 3.1, 3.4.1, 3.4.4, 3.6.1.3.

4.1.2.8 Describe security classification level of offeror‟s engineering, development or other facilities where work on this program will be performed. Describe offeror‟s approach to meeting security requirements detailed in PWSTO-G section 3.5.

4.2 Appendices – The Offeror shall provide the detailed information identified in the Technical

Performance Proposal paragraph above, into the following Appendices. The Offeror shall not embellish or provide, as a continuation of the Technical Approach, any additional amplifying information. The Appendices are not restricted by page count.

4.2.1 Performance Work Statement – Contractor (PWS-C) (Appendix 1) - This Appendix is the

Offeror‟s Performance Work Statement and all CDRLs proposed for the program. The PWS-G provides the Government‟s overall requirements for this solicitation. Offerors shall use the PWS-

G together with the PBS-G and other applicable portions of this RFP, as the basis for preparing its proposal, to include submitting a PWS-C and a PWS-C for Task Order 1 using MIL-HDBK-

245D for guidance. The PWS-C, CDRL and CLIN/SLIN structure shall be consistent with the

Offeror‟s proposed effort and shall be incorporated into the contract if or when accepted.

The Offeror shall ensure all aspects of the government‟s PWS-G are addressed in the PWS-C.

The PWS-C should specify in clear, understandable terms the work to be done in the development of the System to be delivered by the contractor. The Offeror‟s understanding of both required goods/services, and work effort required to accomplish System development shall be fully demonstrated in the Offeror‟s proposed PWS-C including both explicit and implicit requirements parsed from the PWS-G or the PBS-G where the requirement pertains.

The CDRLs identified and listed in the PWS-G constitutes a minimum set of Government data requirements. All data requirements shall be traceable to specific tasks defined in the PWS-G.

4.2.2 Performance Work Statement Task Order 1 – Contractor (PWSTO1-C) (Appendix 2) - This

Appendix is the Offeror‟s Performance Work Statement and all CDRLs proposed for the program

Task Order 1. The PWSTO1-G provides the Government‟s overall requirements for Task Order

1. Offerors shall use the PWSTO1-G together with the PBS-G and other applicable portions of this RFP, as the basis for preparing its proposal, to include submitting a PWS-C for Task Order 1 using MIL-HDBK-245D for guidance. The PWSTO1-C, CDRL and CLIN/SLIN structure shall be consistent with the Offeror‟s proposed effort and shall be incorporated into the contract if or when accepted.

The Offeror shall ensure all aspects of the government‟s PWS-G are addressed in the PWSTO1-

C. The PWSTO1-C should specify in clear, understandable terms the work to be done in the development of the System to be delivered by the contractor. The Offeror‟s understanding of both required goods/services, and work effort required to accomplish System development shall be fully demonstrated in the Offeror‟s proposed PWSTO1-C including both explicit and implicit requirements parsed from the PWSTO1-G or the PBS-G where the requirement pertains.

The CDRLs identified and listed in the PWSTO1-G constitutes a minimum set of Government data requirements. All data requirements shall be traceable to specific tasks defined in the

PWSTO1-G.

4.2.3 Integrated Master Schedule (IMS) (Appendix 3) - This section shall contain the Offeror‟s overarching Integrated Master Schedule for the proposed program, and include detailed discussion of schedule for Task Order 1. The Offeror shall propose and discuss an IMS showing the inter-relationships for each program effort and any relationships to/with the IMP. The Offeror shall partition the IMS into logical elements/sections based on the proposed program approach.

The IMS shall include the Offeror‟s scheduled events. Dependencies shall be identified. The IMS shall be constructed as to identify „critical path‟ and slack time(s) both negative and positive.

Progress for each of the IMS tasks shall be indicated/provided. In addition, as previously stated, the IMS shall include CWBS identification for each element of the proposed effort, including applicable Task Order 1 PWS and PBS-G references as required. The IMS shall present information to at least Level 4, with Level 5 supporting backup, consistent with the Offeror‟s

CWBS. The IMS will be incorporated into the contract. IMS shall be prepared in MS Project.

The IMS shall include all deliverable, i.e. CDRLs/DD Form 1423s provided in the governments‟

PWS-G, and the offeror propsed CDRL/DD Form 1423s.

4.2.4 Contractor Work Breakdown Schedule (Appendix 4) - This appendix shall contain the

Offeror‟s WBS for the proposed program based on MIL-STD-881 to at least Level 3 as covered in the Government PWSTO1 paragraph 3.4.2.2.

4.2.5 Performance Based Specification – Contractor (Appendix 5) - This section shall contain the

Offeror‟s Specification for the proposed program.

5 Volume II Past Performance Proposal:

The Offeror shall demonstrate, through its current or previous Government contracts developing technologies similar in scope and/or technical complexity, the Offeror‟s ability to meet the design, development and testing requirements of this solicitation, in particular its approach to a modular open system design. Offerors (including major subcontractors) shall submit a description of Government contracts that are relevant to the efforts required by this solicitation, and that are or have been in performance within the last three (3) years of the date of the release of this RFP. Up to ten (10) and a minimum of three (3) past performance references are requested with at least one from each major subcontractor. Major subcontractor is defined as a subcontractor anticipated to perform more than 10 percent of the total contract value. The past performance data shall document a history of recent, relevant experience and past contract performance. Relevance is defined as contracts which include:

a. Design or development of software using similar processes and approaches ( modular open system design) and/or

b. Integration of software into networked, modular systems with Electronic Warfare capabilities, and/or

c. Systems of similar complexity

This relevancy assessment will also consider the magnitude, i.e., size of the referenced contract.

The Past Performance Volume shall include the following information for each contract referenced:

Section 1 Contract Description

The contract description shall include the following information in the following format:

a. Identify if reference submitted is for the prime offeror or a proposed major subcontractor

b. Offeror/Subcontractor place of performance, CAGE Code and DUNS Number. If the work was performed as a subcontractor, also provide the name of the prime contractor and POC within the prime contractor‟s organization (name, current address, email address, and telephone and fax numbers.

c. Government contracting activity, current address, and Procuring Contracting Officer‟s (PCO) name, email address, telephone and fax numbers

d. Government‟s technical representative/Contracting Officer‟s Representative (COR) activity, current address, name, email address, telephone and fax numbers

e. Government contract administration activity and Administrative Contracting Officer‟s (ACO) name, current address, email address, telephone and fax numbers

f. Government contract administration activity‟s Pre-Award Monitor‟s name, current address, email address, telephone, and fax numbers

g. Contract number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket

Purchase Agreements, also include Delivery Order numbers

h. Contract Type (specific type such as Firm Fixed Price (FFP), Cost Reimbursement (CR), Time and

Materials (T&M), etc. In the case of Indefinite Delivery contracts, indicate specific type

(Requirements, Definite Quantity, and Indefinite Quantity) and secondary contract type (FP, CR, T&M, etc))

i. Awarded price/cost

j. Final price/cost

k. Original delivery schedule, including dates of start and completion of work

l. Final or projected delivery schedule, including dates of start and completion of work

Section 2 Performance

Offerors shall provide a specific narrative explanation of each contract describing the objectives achieved and detailing how the effort is relevant to the requirements of this solicitation. The narrative shall address (a) the degree to which the Offeror demonstrated its design approach, plans for technology insertion, and sustainment strategy were consistent with the modular open systems requirements, (b) the degree to which the Offeror managed the impact of changing requirements and evolving technology on the system‟s ability to continue to satisfy improved capabilities over time, (c) the degree to which the Offeror‟s test and evaluation planning contained the means for testing the conformance to open standards to ensure the openness of key interfaces throughout the system life cycle, (d) the degree to which the Offeror‟s approach contains capabilities to easily and quickly update, revise, and change the system as threats (warfighting and information assurance threats) or technologies (COTS or reusable) evolve, and (e) the extent to which personnel who contributed to these previous efforts will be supporting this solicitation.

Any problems to include, cost growth, material problems, quality problems, labor problems, facility problems, and delivery delays shall be disclosed and fully explained. The Offeror shall demonstrate how it was able to resolve (or why it could not resolve) special or unexplained problems as well as difficulties in meeting delivery schedule, performance, or cost parameters. Emphasis shall be placed on the Offeror‟s ability to solve problems associated with critical testing, and quality control.

Furthermore, the Offeror shall indicate any quality awards or recognition received.

Describe experience in software development specifically with 1) Service Oriented Architecture

(SOA), 2) Modular and Open System Architectures / Navy Open Architecture (MOSA/NOA)/, 3)

Using MOSA to enable rapid Technical Insertion, 4) using the Ozone Widget Framework (OWF), 5)

Web Services. Also, describe any experience in the fields of RF, Electronic Warfare and Spectrum

Management.

5.1.1 New Corporate Entities

New entities that have no past customers shall notify the Contract Specialist, prior to the date and time established for the RFP closing, that they have had no previous clients and that the minimum number of questionnaires cannot be provided. New corporate entities may submit data on prior contracts involving its officers and employees. However, in addition to other requirements in this section, the offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above.

5.1.2 Past Performance Assessment Questionnaire

For all contracts referenced, Past Performance Assessment Questionnaires (PPAQ) shall be submitted. The offeror shall complete Part I of the PRAQ and email the questionnaire to both the

Government contracting activity and technical representative responsible for the past/current contract.

The POCs shall be instructed to electronically complete Part II of the questionnaire and email the entire questionnaire to the Contract Specialist at Sherelle.r.lockhart.civ@mail.mil, within 25 calendar days of RFP release. The offeror shall specifically request that each Government customer/client prepared questionnaire response NOT be provided back to the offeror, either as an original or as a copy. The offeror shall request that the Government POCs maintain the original/signed questionnaire as a record of its response. The offeror shall also email to the Contract Specialist a list of all the POCs who were sent a questionnaire. It is requested that the Government be provided this list within 15 calendar days after release of RFP; but this list must be provided NLT the proposal submission time/date. The POC List shall be submitted in Microsoft Word Table format to include the following mailto:Sherelle.r.lockhart.civ@mail.mil fields: Solicitation Number; Company Name; Contract Number; Government Agency; POC Last

Name; First Name; POC Title; POC Telephone Number; POC Email Address; Date Emailed to POC

(month/day).

The Past Performance Questionnaire is provided in Section J of the RFP.

6 Volume III Cost:

6.1 *** Details for Cost proposal will be released at a later date****

7 Volume IV Small Business Participation :

All Offerors, both small and large businesses, are required to submit Small Business Participation

Plan information in accordance with DFARS 215.304 that shall include the following:

(a) Type of Business of Prime Contractor:

Check all applicable boxes

{ } Large

{ } Small (also check type of Small Business below)

{ } Small Disadvantaged Business

{ } Woman-Owned Small Business

{ } HUB Zone Small Business

{ } Veteran Owned Small Business

{ } Service Disabled Veteran Owned Small Business

(b) Small Business Participation Goals: Use the matrix below to propose your small business participation goals.

Each participation percentage below shall be accompanied by detailed supporting documentation. If applicable, detailed explanations should be provided as to why certain goals specified by the

Government in Section M “Basis for Award” cannot be met or exceeded.

An Offeror who qualifies as a small business should include its prime contractor dollars in calculating its proposed percentage goals in all of the small business categories that it qualifies for in the matrix below. For example, an Offeror contractor who is a small disadvantaged women owned business gets credit in the prime category (B), the small category (D), the small disadvantaged business category

(E) and the women owned small business category (F).

The sum of the percentages in matrix categories for small business (E thru I) may exceed 100% since individual subcontractors may be counted in more than one category. (See below example).

EXAMPLE: Total Contract Value in Cost Proposal- $100

Offeror/Prime (WOSB) $60 60%

Large $40 40%

Small Business $60 60%

Small Disadvantaged $60 60%

Women Owned Small $60 60%

Hubzone $ 0 0%

Veteran Owned Small $ 0 0%

Service Disabled Veteran Small Business $ 0 0%

DESCRIPTION DOLLARS % of TOTAL

CONTRACT

VALUE

A. TOTAL CONTRACT VALUE :

This value should include all options, etc. and match the TOTAL

CONTRACT VALUE you have proposed in your cost proposal volume.

100%

B. DOLLAR VALUE AND PERCENTAGE OF YOUR

PARTICIPATION AS PRIME

CONTRACTOR:

If you are a small business Offeror, you receive credit for participation as a prime contractor. (%=B÷A)

C. DOLLAR VALUE AND PERCENTAGE OF SUBCONTRACTS

PLANNED FOR LARGE BUSINESS (%=C÷A)

D. DOLLAR VALUE AND PERCENTAGE OF

PARTICIPATION/SUBCONTRACTS PLANNED FOR SMALL

BUSINESS:

This is the sum of all subcontracts to Small Business, Small

Disadvantaged, Women Owned Small, Hubzone Small, Veteran Owned

Small, Service Disabled Veteran Owned Small and Historically Black

Colleges and Universities/Minority Institutions (HBCU/MI). If the

Offeror is any of these Small Business categories, include the dollars reflecting participation as the prime contractor from B above.

(%=D÷A)

E. DOLLAR VALUE AND PERCENTAGE OF

PARTICIPATION/SUBCONTRACTS PLANNED FOR SDB AND

HBCU/MI

This should reflect the value of all subcontracts planned for Small

Business Administration (SBA) CERTIFIED SDB (as verified in

Central Contractor Registration (CCR)/Pro-Net Database) or

HBCU/MI. If the Offeror is an SBA CERTIFIED SDB or

HBCU/MI, include the dollars reflecting participation as the prime contractor from B above. (%=E÷A)

F. DOLLAR VALUE AND PERCENTAGE OF

PARTICIPATION/SUBCONTRACTS PLANNED FOR WOMEN

OWNED SMALL BUSINESS:

This should reflect the value of all subcontracts planned for Women

Owned small businesses. If the Offeror represents itself as a Women

Owned small business, include the dollars reflecting participation as the prime contractor from B above. (%=F÷A)

G. DOLLAR VALUE AND PERCENTAGE OF

PARTICIPATION/SUBCONTRACTS PLANNED FOR

HISTORICALLY UNDERUTILIZED BUSINESS ZONE

(HUBZONE) SMALL BUSINESS:

This should reflect the value of all subcontracts planned for SBA

CERTIFIED HUBZone small businesses as verified in CCR/Pro-Net

Database. If the Offeror is an SBA CERTIFIED HUBZone small business, include the dollars reflecting participation as the prime contractor from B above. (%=G÷A)

H. DOLLAR VALUE AND PERCENTAGE OF

PARTICIPATION/SUBCONTRACTS PLANNED FOR VETERAN

OWNED SMALL BUSINESS:

This should reflect the value of all subcontracts planned for ALL

Veteran Owned small businesses including Service-Disabled Veteran-

Owned Small Businesses (SDVOSB). If the Offeror represents itself as a Veteran-Owned small business, include the dollars reflecting participation as the prime contractor from B above. (%=H÷A)

I. DOLLAR VALUE AND PERCENTAGE OF

PARTICIPATION/SUBCONTRACTS PLANNED FOR SDVOSB:

The value of all subcontracts planned for SDVOSB. If the Offeror represents itself as a SDVOSB, include the dollars reflecting participation as the prime contractor from B above. Total should be equal to or less than H. (%=I÷A)

(c) List principal supplies/services to be subcontracted. Be specific as possible (i.e.

references to statement of work, etc) that will demonstrate a variety and complexity of work:

Name of Company (including its CAGE code) Type of Service/Supply

Large:

Small Business:

Small Disadvantaged Business and HBCU/MI:

Women-Owned Small Business:

HUB Zone Small Business:

Veteran Owned Small Business:

Service Disabled Veteran Owned Small Business:

(d) Small Disadvantaged Business (SDB) and HBCU/MI target participation must be expressed as dollars and percentages of TOTAL CONTRACT VALUE, in each of the applicable, authorized six digit 2007 NAICS Industry Subsectors that the Offeror best believes describes the product or service planned for SDB and HBCU/MI subcontracts, (available at http://www.census.gov/epcd/naics07/) and a total target for SDB participation by the Offeror.

SDB targets by NAICS code will be incorporated into any resulting contract and the contractor will be required to report SDB and HBCU/MI target participation. Use the following matrix to report SDB and HBCU/MI target participation which should be the same as (E) in the matrix.

COMPANY NAICS DOLLARS % OF TOTAL

CONTRACT VALUE

TOTAL: $_____________

(e) Prior Performance Information: Provide any information substantiating the

Offeror‟s track record of utilizing small business on past contracts. For large and small businesses, provide descriptive historical information for ALL small business categories.

Any information concerning long-term relationships with small business subcontractors, such as mentor-protégé relationships, etc. should be provided. Large business should also include its latest ACO rating and, at a minimum, its two (2) most recent Standard

Form (SF) 295s.

(f) Extent of Commitment: Provide documentation regarding enforceable commitments for this effort including teaming agreements. Copies of such agreements should be provided as part of your small business participation plan.

(2) In order to comply with the requirements for the Small Business Participation Plan, please be sure you have:

(a) based your percentages on TOTAL CONTRACT VALUE;

(b) provided NAICS codes for all Small Disadvantaged Businesses and HBCU/MI;

(c) included detail and documentation supporting the goals you have proposed. if applicable, be sure you explain whether goals cannot be met or exceeded as stated in

Section M, “Basis for Award”.

(e) included detail regarding your historical performance with small business

8 Volume V - Solicitation, Offer and Award Document, Certifications /Representations:

(1) Certifications and Representations. Each Offeror shall complete (fill-in and signatures) the solicitation sections indicated below using the file (without modification to the file) provided with the solicitation. An authorized official of the firm shall sign the SF 33 and all certifications requiring original signature. An Acrobat PDF file shall be created to capture the signatures for submission.

This Volume shall contain the following:

(a) Solicitation Section A Standard Form 33 (SF 33), Solicitation, Offer and Award

(b) Solicitation Section G Contract Administration Data

(c) Solicitation Section K Representations, Certifications and Other Statements of Offerors*

(d) Any proposed exceptions to solicitation terms and conditions.

*Note: Offerors must complete all representations and certifications listed in Section K in addition to provision FAR 52.204-8, Annual Representations and Certifications.

FAR 52.204-8 allows offerors to complete the corresponding individual representations and certifications in the solicitation or to complete said annual representations and certifications electronically via the Online Representations and Certifications Application (ORCA) website. Offerors are encouraged to read this provision carefully and indicate to the Government which option is being selected for proposal submission.

(2) In accordance with FAR 16.301-3(a) Cost reimbursement contracts may be used only when the contractors accounting system is adequate for determining costs applicable to the contract. Upon receipt of an offeror's proposal, the Defense Contract Audit Agency (DCAA) will conduct a preaward survey of each offeror's accounting system per the mandates of section 5-202 of the DCAA Contract

Audit Manual. A determination of an adequate accounting system by DCAA in this preaward survey is necessary to be eligible for an award.

(3) The Offeror shall provide the Government with the current status (e.g. approved, disapproved, acceptable, adequate, or inadequate) of its Estimating and Purchasing Systems, including any reports or other correspondence received from Defense Contract Audit Agency (DCAA) and Defense

Contract Management Agency (DCMA) in the last three years. The Offeror shall provide the

Government with its own assessment of the adequacy of its systems to ensure that estimated costs are based on well documented and supported bases. Additionally, the Offeror shall address its procedures for Subcontract Award and Administration, including documentation of the extent of adequate price competition achieved over the past three years, and/or the extent of comprehensive price/cost analysis where competition is not feasible. The Offeror shall discuss its practices to ensure that agreed-to pricing with major subcontractors and suppliers is accomplished prior to finalizing a price with the

Government, and that it documents substantiation for the price reasonableness of subcontracts and material costs. Finally, the Offeror shall address its procedures relating to commercial item pricing, demonstrating that the prices paid are in line with those paid by commercial customers based on relevant quantities.

If the approved or adequate status of either of these systems is currently in question, or if DCAA has issued any reports (including issuance of any Statements of Condition(s) and Recommendation(s) and/or Auditor Comments related to the Offeror‟s response to the Statement of Condition(s) and

Recommendation(s)) released to the Offeror prior to issuance of a final report to the Contracting

Officer) on inadequacies of the systems, the Offeror shall provide an explanation of its agreement or disagreement with the cited inadequacies of the system. The Offeror shall provide such correspondence received from DCAA and/or DCMA within the last three years. The Offeror should explain in detail the system inadequacies and completed corrective actions as well as specific plans for future corrective action, including milestones for implementation of revised procedures. Also, the

Offeror should discuss the impact on this procurement of the reported system inadequacies, and what action is being taken to ensure that these systems are corrected to ensure no detrimental impact should the Offeror receive a contract award.

The information requested in subparagraphs (a) and (b), above, shall also be provided for any major subcontractors anticipated to perform more than 10 percent of the contract value.

(4) Each large business Offeror shall provide a Small Business Subcontracting Plan that contains all the elements required by FAR 52.219-9. This plan shall be submitted separately from the SBPP information required above, which applies to both large and small businesses. The Subcontracting

Plan is not a requirement for evaluation in the source selection, but rather, a requirement for award to a large business and it will be incorporated into any resultant contract.

(5) Technical Data Rights - Offerors competing for this contract will, to the extent authorized by law, be required to grant to the Government, no less than Government Purpose Rights (GPR) in the SW designs to be delivered. The EWPMT contract will, to the extent authorized by law, not contain any restrictions on the Government's rights to share, modify, or re-use the noncommercial technical data associated with any EWPMT deliverable, including Technical Data Packages.

If any Teaming Partners data is deemed proprietary, it may be submitted directly to the Government.

In such cases, the Teaming Partners submission must clearly identify the solicitation number and the name of the Prime Offeror (multiple Prime Offerors must be identified separately). The Prime Offeror remains responsible for ensuring that any Teaming Partner submissions are made in a timely manner and in accordance with the proposal instructions in the solicitation.

(6) The Offeror shall submit an RFP Cross-Reference Matrix as outlined in paragraph 3.3.2.