N00024-15-R-6400_Amendment_0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to extend the proposal submission date accordingly.

1. CONTRACT ID CODE PAGE OF PAGES

U 1 49

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 26-May-2015

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N00024-15-R-6400

X 9B. DATED (SEE ITEM 11)

09-Apr-2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

26-May-2015

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2060

N00024 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00024-15-R-6400

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 11-Jun-2015 12:00 PM to 10-Jul-2015 12:00 PM.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

Instructions, Conditions and Notices to Offerors

1. General

The Offeror shall submit all information required by this RFP. Failure to comply with the terms and conditions of the RFP may result in the Offeror being removed from consideration for award. The Offeror’s proposal shall be based on the requirements contained in this RFP (including those documents, exhibits, and other attachments to the

RFP identified in Section J). Offerors are required to submit a proposal encompassing all items listed in Section B of this RFP.

The solicitation will be made available only through the internet at:

http://www.fbo.gov

Offerors are hereby notified that from time to time, the Government may post additional information to the web site relating to this solicitation (e.g. responses to questions, amendments, etc.). It is the Offeror’s responsibility to check the web site for any such information. The drawings and the classified performance specifications may be obtained by contacting the Contract Specialist, Shanna Laging at shanna.laging@navy.mil (cc PCO Michael Brown at michael.l.brown2@navy.mil). Offerors will provide their physical address, classified address, CAGE code, and a point of contact for the above-mentioned documents. Once the security approval has been obtained the information will be mailed to the offeror.

The Offeror must ensure that the MK48 Mod 7 G&C Section and CBASS Upgrade Kit items meet Navy requirements. The Offeror shall explain in their technical proposal how the design meets the Navy’s performance specification requirement and provide an in-depth comparison to the Navy’s informational design.

Offeror Solicitation Questions: Offerors may electronically submit written questions requesting clarification of solicitation requirements by sending an email to the Contract Specialist, Shanna Laging at shanna.laging@navy.mil

(cc PCO Michael Brown at michael.l.brown2@navy.mil). Offeror’s comments and/or questions must be submitted utilizing Attachment 17 “Question and Comments Form” and include, at a minimum: Document Description; Page numbers; Section/Paragraph; Question or Comment; proposed action or change (if applicable); or other definitive citation requiring classification. All such questions should be received in writing within 20 days after release of the

RFP to allow the Navy adequate time to prepare and issue responses to all Offerors prior to the date and time set for receipt of proposals. Only questions transmitted electronically will receive a response. The Navy will continue to accept questions up to the closing date and time of the solicitation; however, time may not permit responses to be issued prior to proposal receipt. Questions received after the time set forth above will not result in an extension to the proposal due date. It is the Government’s intention that questions and responses will be distributed electronically to all Offerors. Information provided with each question shall include the section of the solicitation, document name, document date, specific page, paragraph, clause or other definitive citation requiring clarification.

http://www.fbo.gov/ mailto:shanna.laging@navy.mil mailto:shanna.laging@navy.mil

Any Classified questions shall be submitted within ten (10) calendar days of the request for proposal via secured mail on an appropriately marked CD and sent to the following address:

Naval Sea Systems Command, (PMS404P1)

Attn: Darnell Eaton

1333 Isaac Hull Avenue SE, Stop 176

Washington Navy Yard, D.C. 20376-4401

Handling and marking procedure for classified questions (or questions related to classified specification sections) must follow the appropriate procedures. Answers to classified questions will be securely mailed to all bidders who are appropriately cleared and request such answers. Classified questions and answers are prohibited from public release and therefore interested Offerors must make a specific request for obtaining said questions and answers.

Should classified questions be submitted, all interested Offerors will be informed of such questions.

Any Classified questions shall be submitted within ten (10) calendar days of the request for proposal via secured mail on an appropriately marked CD. Handling and marking procedures for classified questions (or questions related to classified specification sections) must follow the appropriate procedures. Answers to classified questions will be securely mailed to all bidders who are appropriately cleared and request such answers. Classified questions and answers are prohibited from public release and therefore interested Offerors must make a specific request for obtaining said questions and answers. Should classified questions be submitted, all interested Offerors will be informed of such questions.

1.1. Solicitation Response Requirements

The solicitation response shall be contained in three separate Volumes, delivered by the date of the closing of the solicitation which, unless an extension has been granted, will be as specified in Block 9 of Section A (SF-33 Form) of this RFP:

I Technical Proposal

II Cost/Price Proposal

III Solicitation Package to include signed copy of RFP and all associated amendments

For Volumes I, II, and III the number of copies required and the page limit are shown in the table below.

Volume Title Original

(Paper)

Additional

Paper Copies

File(s) on CD-ROM Page

Limit

I Technical

Proposal

1 10 2 145

II Cost/Price

Proposal

1 6 2 No Limit

III Solicitation

Package

1 1 2 N/A

Electronic proposal submissions and supporting information shall be submitted on CD-ROM suitable for reading in a standard PC compatible CD-ROM drive. All view graphs shall be in Microsoft PowerPoint 2010. All spreadsheets or mathematical computations (cost data) shall be in Microsoft Excel 2010 format and shall be working versions, including formulas and computations. Note, submission of locked spreadsheets will not be acceptable. All text shall be in Microsoft Word 2010 or searchable Adobe Acrobat Portable Document Format (PDF). All schedules, including Integrated Master Schedule (IMS), shall be in Microsoft Project 2010. The electronic proposal material shall not contain any information not contained in the hard copy format. In the event of disparities between hardcopies and electronic information, the hardcopy governs.

The narrative material in the hardcopy proposal shall be typed or printed in a font with the type no smaller than size

12 Times New Roman font on standard 8-1/2 x 11 inch paper. Text line spacing shall be 1.5 lines. One-inch minimum margins on each side, including top and bottom are required. Text within tables, diagrams, pictorial charts, or graphic material may use 8-point Times New Roman font. Fold out pages may be used for diagrams, charts or graphic material only and may not exceed 11 inches by 17 inches. Fold out pages will be counted as two pages. Fold out pages may only include narrative sufficient to describe the diagram, chart or graphic material. Every paragraph, figure, and table shall be numbered. Pages in excess of the page count limitation will be removed prior to the evaluation. Proposal material shall be presented on double-sided pages only and in a single column on each page

(refer to Section I, FAR 52.204-4). Each double-sided page counts as 2 pages. Pages are to be numbered sequentially and tabs are to be used for chapter breaks. It is not acceptable to restart numbers in subsequent chapters within the proposals.

A date shall be placed on each page of the proposal corresponding to the date of the initial proposal. Any pages that may be revised as a result of discussions (if required) shall contain revision numbers and dates.

Each volume shall be bound separately and shall not exceed the page limitation cited above including both classified and unclassified data. For the purposes of compliance with the page limitation, classified information (if applicable) shall be supplied separately as a supplement and added at the end of the technical volume. The page count shall include all material with printed matter and figures except cover pages, title pages, Table of Contents (TOC), lists of illustrations, tab pages, appendices, index and lists of tables. Pages excluded from the page count must contain only material pertinent to the page heading or be blank and marked "Intentionally Left Blank." Index pages and Tabs are required and shall be cross-referenced to the TOC. Every page, except those marked as blank, must be numbered. If the proposal exceeds the page limit identified in the table above, the Government will remove all pages exceeding the specified page count from the back of the substantive proposal volume (not the appendices) prior to the evaluation of the proposal and will not be reviewed or evaluated. Pages will not be removed from the index or from any appendices provided at the back of the proposal. Each hard-copy volume of the proposal shall be bound in three ring binders to permit removal of sections with each major part tabbed. The Offeror’s company name shall appear at the top of each page and all pages shall be numbered.

Offerors are cautioned that, in accordance with the “Instruction to Offerors-Competitive Acquisition” clause (FAR

52.215-1), the Government intends to award a contract on the basis of initial proposals received, without discussions. Therefore, each proposal shall contain the Offeror’s best terms from a cost and technical standpoint.

The Government intends to award this contract without any discussions with Offerors, but it reserves the right to hold discussions. The Government will conduct discussions regarding issues in the proposal’s technical or cost volumes if they are determined to be necessary.

In addition to the paper copies, the Offeror shall provide Volumes I, II and III on separate CD-ROMs in the format described above. If a classified supplement is included it shall be provided on a separate CD-ROM with appropriate security classification markings. Each disk shall be labeled as follows:

Volume #

Offeror Company Name, City, State

Offeror POC

Offeror POC Phone #

The cover page of each Proposal Volume shall contain:

Volume Number and Title (e.g., Volume I - Technical Proposal)

Item Nomenclature and Request For Proposal (RFP) Number

Company Name of the Offeror

Offeror's Position on Disclosure of Proposal Data

Security Classification of the Volume

Serial Number/Copy Number

Proposal submission shall be as follows:

1) All copies of all proposal volumes (including electronic copies) shall be submitted at the place and at or before the time specified in Block 9 of the SF 33.

2) No cost or pricing information shall be included in the Offeror's cover letter or in any part of its submitted volumes, except the Cost/Price Volume. Cover letters are merely instruments for transmitting the submitted proposals; they are not part of the page count and will not be evaluated.

3) Although legible, neat, orderly, and comprehensive proposal(s) are required, elaborate brochures or other presentations beyond that sufficient to present a complete and effective explanation are not desired. Elaborate artwork, expensive visual or other presentation aids are neither necessary nor desired.

4) The Proposal shall contain all the pertinent information in sufficient detail to permit evaluation. The proposal should be so detailed and complete as to clearly demonstrate that the Offeror has a thorough comprehension of all technical and other requirements. If an Offeror fails to comply with content requirements its proposal may be downgraded for failure to follow instructions.

1.1.1. Solicitation Responsiveness

Offerors are advised to submit proposals that are complete, clear, and consistent in all respects without the need for additional explanation or information. Offerors are cautioned against the use of general, vague, or unsubstantiated statements, which prevent concise proposal evaluation. The proposals will be evaluated under each factor on how well the response meets the requirements of the solicitation. The response that completely addresses all of the solicitation requirements may be judged superior to the response that minimally addresses solicitation requirements.

1.1.2. Competitive Range

If an award is not made on the basis of initial proposals, the Contracting Officer will make the determination as to which proposals are in the “Competitive Range.” The competitive range shall be determined based on the results of the evaluation of initial Technical and Cost Proposals, considering all evaluation criteria, and shall include the most competitive proposals. The number of proposals within the competitive range may also be reduced if the Contracting

Officer determines the number of most competitive proposals that might otherwise be included within the competitive range exceeds the number at which an efficient competition can be conducted.

1.1.3. Discussion/Final Proposal Revision (FPR)

Please note that pursuant to FAR 52.215-1, the Government intends to award contract(s) based upon the initial proposals. Therefore, the Offeror’s proposal shall contain the Offeror’s best terms from a price and technical standpoint. However, the Government may contact any or all or a limited number of Offeror’s with questions concerning their proposals as permitted under FAR Part 15. The Government reserves the right to conduct discussions if the Procuring Contracting Officer determines them to be necessary. If discussions are held, offerors selected to participate in the discussion shall be advised of weaknesses, deficiencies and risks in their proposals as well as adverse past performance ratings to which the offeror has not had an opportunity to respond. Offerors shall be offered a reasonable opportunity to correct or resolve such weaknesses, deficiencies, and risks and to submit such technical and cost information, or other revisions to their proposals, that may result from such discussions. At the end of discussions, if they occur, the Government will request Final Proposal Revisions (FPRs) from all Offerors still within the competitive range. If it is determined that an Offeror is no longer in the competitive range they will not be given an opportunity to submit an FRR.

1.2. Special Proposal Receipt Requirements

Offerors shall submit proposals in accordance with HQ L-2-0013 Special Proposal Receipt Requirements

(NAVSEA) (SEP 2009).

1.3. Use Of Contractor Facilities For Source Selection

In accordance with NAVSEA Instruction 4200.19, the Director of Contracts, Naval Sea Systems Command, determined that adequate facilities to support source selections are not available at NAVSEA for Solicitation

N00024-15-R-6400. Therefore, Offerors are advised that facilities may be acquired through a Contractor

(Commercial Property managed by WC Smith and Company, leased by Alion and located at 1100 New Jersey

Avenue, SE, Washington, D.C. 20003) so that the Source Selection Organization can effectively evaluate proposals submitted for this procurement. In addition, all Offerors are notified that at all relevant times, the Government will maintain control over the source selection spaces.

1.4. Availability of Competition Library Documentation

A Competition Library containing relevant GFI (including the Technical Data Packages) has been created by

PMS404. CD-ROMs are available to eligible Offerors. Companies requesting a copy of the Competition Library set must provide the Contracting Officer a completed “Competition Library Request Form” (Attachment 18), a completed DD254 (Attachment 6) indicating that the requesting company has a Defense Security Service (DSS) issued SECRET facility clearance, providing for SECRET personnel clearances and SECRET safeguarding capability, and a completed “Terms of Use and Non-Disclosure Agreement” (Attachment 14). The Government will not provide sponsorship for new or upgraded personnel or facility clearances. Upon receipt by the Contract

Specialist, the Competition Library will be made available in a secure manner to the Offeror so long as the Offeror has met the security requirements detailed herein.

The deadline to request access to the Competition Library shall be the same as the deadline to submit questions.

The “Competition Library Request Form”, DD254, and “Terms of Use and Non-Disclosure Agreement” shall be signed and returned to both of the following POCs:

To: Ms. Shanna Laging – shanna.laging@navy.mil

CC: Mr. Michael Brown – michael.l.brown2@navy.mil

2. CONTENTS OF THE OFFER

The offer consists of and must include the following to be eligible for award:

Volume I, Technical Proposal:

See Section L, Section 3.1 for the content and format requirements of the Technical Proposal

Volume II, Cost Price Proposal:

See Section L, Section 3.2 for the content and format requirements of the Cost/Price Proposal.

Volume III, Solicitation Package:

See Section L, Section 3.3 for the content and format requirements of the Solicitation Package

Proposal.

3. PROPOSAL ORGANIZATION

3.1. Volume I: Technical Proposal

The Technical Proposal shall be specific and complete so as to clearly demonstrate to the Government that the

Offeror has a comprehension of and capabilities to perform all aspects of the solicitation requirements including technical, product assurance, fabrication, management, availability and reliability objectives, and resource requirements as well as all other provisions of this solicitation. This volume shall be organized into Subfactors as outlined below. This volume shall not exceed 145 pages and shall consist of the following:

Page

No. Description i Title Page ii Table Of Contents iii List Of Figures iv List Of Tables v List Of Appendices vi Glossary Of Abbreviations And Acronyms

(The items above do not count against Technical Proposal page limitation)

CHAPTER 1.0 SUBFACTOR 1: TECHNICAL APPROACH

CHAPTER 2.0 SUBFACTOR 2: MANAGEMENT APPROACH

CHAPTER 3.0 SUBFACTOR 3: QUALITY APPROACH

CHAPTER 4.0 SUBFACTOR 4: PAST PERFORMANCE (All past performance information provided in

Chapter 4.0 counts against the Technical Proposal page limitation, with the exception of the

Sections 4.1 and 4.2.)

Section 4.1 Past Performance Questionnaire (Does not count against Technical Proposal page limitation)

Section 4.2 Past Performance Self-Assessment (Does not count against Technical Proposal page limitation)

CHAPTER 5.0 ATTACHMENTS/SUPPLEMENTAL INFORMATION

Section 5.1 Supplemental Information Regarding Offeror’s Basis of Estimates for Labor and Bill of Materials

(Does not count against Technical Proposal page limitation)

Section 5.2 Supplemental Information Concerning Restrictions On Technical Data (TD), Computer Software

(CS), And Computer Software Documentation (CSD) (Does not count against Technical Proposal page limitation)

Section 5.3 Supplemental Information Regarding Background Inventions and Licensing (Does not count against Technical Proposal page limitation)

Section 5.4 Supplemental Information – CLASSIFIED INFORMATION (Separate Binder) (Does not count against Technical Proposal page limitation)

Section 5.5 Cross Reference Matrix (Does not count against Technical Proposal page limitation)

Section 5.6 Staffing Plan and Key Personnel (Rates not included) (Does not count against Technical Proposal page limitation)

Section 5.7 Software Development Plan (Does not count against Technical Proposal page limitation)

Section 5.8 WBS Dictionary (Does not count against Technical Proposal page limitation)

Section 5.9 Program Management Plan (Does not count against Technical Proposal page limitation)

Section 5.10 Integrated Master Schedule (IMS) (Does not count against Technical Proposal page limitation)

Section 5.11 Work for Private Party Agreements (WFPPA) (Does not count against Technical Proposal page limitation)

Section 5.12 Quality Program Plan (Does not count against Technical Proposal page limitation)

3.1.1. CHAPTER 1.0 Subfactor 1: Technical Approach

3.1.1.1. Systems Engineering Approach

The Offeror shall describe the systems engineering process, including preparation and maintenance of Systems

Engineering documentation to support the manufacturing and delivery of MK48 Mod 7 G&C Sections, MK48 Mod

7 CBASS Upgrade Kits and Factory Acceptance Test Equipment.

The Offeror shall describe an engineering reliability approach to demonstrate the designs are compliant to performance specifications.

3.1.1.2. Non-Recurring Engineering (NRE) /and Proof of Manufacture (POM)

The Offeror shall describe its systems engineering approach to implement the design for production of build-to-specification items and to ensure that build-to-specification items meet the specified performance requirements provided in Attachment 1 Contract Baseline. The Offeror shall describe its systems engineering approach to implement the production of build-to-print items and to ensure that build-to-print items meet the specified drawing requirements provided in Attachment 1 Contract Baseline.

The Offeror shall further describe its approach to reuse, modify, or create software and firmware as part of its MK48

Mod 7 G&C Sections, CBASS Upgrade Kits, and Factory Test Equipment designs.

The Offeror shall describe its approach to develop and validate Factory Test Equipment for CCA and FIR level testing (this does not include Government Furnished Equipment (GFE) / Government Furnished Facilities (GFF)

Factory Test Equipment) referenced in Attachment 12, Description of GFE-GFF Test Capabilities, unless plans include modification or replacement of GFE GCB and Preamp/BSAR Factory Test Equipment.

The Offeror shall describe their redesign and/or life of the contract purchasing strategy to ensure that their proposed approach can be purchased without major modification for the life of the contract, including commercial-off-the-shelf (COTS) processing boards. As described in the CBASS Kit Obsolescence White Paper (Attachment 16), significant obsolescence issues have been identified with the GCB and BSAR. Source code listed in Attachment 3 will be provided as GFI.

The Offeror shall discuss their approach for evaluating and proposing Design for Manufacturability & Assembly

(DFMA) changes to the TDP after contract award. The Offeror’s DFMA approach should be used to optimize the design for cost effective manufacturing and assembly where applicable while maintaining form, fit, and function.

This may include, but not be limited to: minimization of the number of parts, minimization of the number of fasteners, standardization of parts and fasteners, avoidance of difficult components, use of modular subassemblies, use of multifunctional parts, minimization of reorientation, use of self-locating features, avoidance of special tooling and test equipment, providing accessibility, and minimization of operations and process steps. The Offeror may propose alternate designs for BTP items, but the Offeror must demonstrate that the alternate design meets the same form fit and function as the BTP design provided with this RFP and that the alternate design provides a significant

(greater than $500,000) cost savings to the Government.

The Offeror shall describe proposed designs of build-to-specification items that demonstrate an understanding of the performance requirements. Hardware and software designs shall clearly identify the proposed technical implementation addressing obsolescence concerns.

The Offeror shall denote the total quantity of hardware it plans to build to support its Non-Recurring Engineering

(NRE) efforts. It should be noted that at a minimum quantity of three (3) Contractor Owned Units, that do not count as deliveries to the Government, will be required for each FIR to perform Thermal Margin (1 unit), Vibration

Margin (1 unit), and the Proof of Life Testing (1 unit) detailed in Manufacturing Quality Assurance Specification, Torpedo Functional Item Replacement (Document Number 8595331 (Attachment 1)). Pre-POM and POM Kits shall be provided as specified in Section C. Hardware used to support Contractor First Article testing is not to be included in the Pre-POM or POM deliveries. Pre-POM Kits will be the proposed design for the deliverables under

CLIN 0002. They are delivered to support early integration of Government software with the Contractor supplied

HW/SW and to develop changes needed to the test sets required by the HW/SW design changes.

3.1.1.3. Technical Data Packages

The Offeror shall describe how it will develop, validate, and deliver MK48 Mod 7 G&C Section and CBASS

Upgrade Kit Technical Data Packages that meet all specified requirements for build-to-specification (BTS) items, including all hardware, software, and firmware items.

The Offeror shall describe how it will meet the build-to-print portions of the MK48 Mod 7 G&C Section and

CBASS Upgrade Kit Technical Data Packages and maintain updates.

The Offeror shall describe how it will develop, validate, and deliver a Factory Test Equipment Technical Data

Package that includes all hardware, software, and firmware items. Details shall be included on any Non-

Developmental Items (NDI) or Commercial off-the-shelf (COTS) data planned to be utilized.

The Offeror shall describe the extent to which proprietary or otherwise limited or restricted components, subsystems, interfaces, and software are used. Rights in Technical Data/Computer Software/Computer Software

Documentation (TD/CS/CSD) shall be explain the degree to which the proposal provides the level of technical data rights (commercial and noncommercial) and rights in computer software that will enable the Navy to adequately sustain the MK48 Mod 7 G&C Section and Factory Test Equipment over their life cycle to include maintainability, reparability, and re-procurement.

If an Offeror proposes to deliver any commercial or noncommercial TD/CS/CSD with less than Government

Purpose Rights (GPR), the Offeror shall describe the impact on the Government's ability to use, modify, release or disclose such TD, CS, or CSD. The use of proprietary algorithms, designs, processes or interfaces shall be described. The Offeror shall provide justification and rationale for all intellectual property and data rights assertions.

Per NAVSEA Clause - ALTERNATIVES TO SPECIFICATIONS OR STANDARDS (NAVSEA) (AUG 1994), the

Offeror’s proposal shall provide rationale describing the advantages of any proposed alternative specification or standard.

3.1.1.4. Design & Obsolescence

The Offeror shall describe its approach to manufacture, test, and deliver MK48 Mod 7 G&C Sections and CBASS

Upgrade Kits in accordance with the Contract Baseline, Attachment 1. The Offeror shall describe its proposed design and associated risk. The Offeror shall include the strategy that will be employed to adequately manage obsolescence during the contract’s period of performance. The obsolescence strategy shall also include management of obsolescence for build-to-print items. The Offeror shall provide a list of all items that are obsolete and its technical approach to address this obsolescence. The Offeror shall provide a list of all items that are viewed as at risk of becoming obsolete during the contract period and its technical approach to address this obsolescence risk.

The Offeror shall review the Technical Data Packages provided in Attachments 1 (Contract Baseline) and

Attachment 3 (GFI) and the White paper, “Known CBASS Obsolescence” provided in Attachment 16. The

Offeror shall describe the proposed scope of any redesign tasks associated with obsolescence; including electronics design work, any required software or firmware changes, and developmental/design verification testing that will ensure the G&C performs to all requirements in Attachment 1. Impacts of the design changes to GFE Factory Test

Equipment also must be considered and addressed. In describing the scope of the software and firmware redesign effort required due to obsolescence, the Offeror shall describe the scope and complexity of the effort required to perform the software and firmware redesign, integration, test, and validation. Attachment 16 (CBASS

Obsolescence Impacts) is provided to the Offeror to give an understanding of the existing system complexity and assist in the preparation of the Offeror’s Basis of Estimates (BOE).

The Offeror’s proposal may comment on the scope of the obsolescence and redesign effort as it relates to the

Government’s acquisition approach detailed in this solicitation, the proposed design, the Offeror risks, as well as the government proposed schedule.

3.1.1.5. Factory Test Equipment Design & Approach

The Offeror shall describe the Factory Test Equipment and test approach and discuss how it will validate that MK48

Mod 7 G&C sections and MK48 Mod 7 CBASS Upgrade Kits meet the requirements of the MK48 Mod 7 G&C

Contract Baseline, Attachment 1, prior to delivery to the Government.

The Offeror shall provide descriptions for the proposed design of the following Factory Test Equipment under

CLINs 0005, 0105, 0205, 0305 and 0405: Transmitter Test Set, upgraded or new design GCB Test Set, and upgraded or new design Preamp/BSAR Test Set.

The Offeror shall describe the new Transmitter Test Equipment design to meet the requirements provided of

Attachment 1 (Transmitter Test Equipment System Requirements Document, 8595292).

The Offeror shall describe plans for test of G&C Type I cables in accordance with requirements provided in Section

C.

The Offeror shall describe how it will modify the GFE Preamp/BSAR and GCB Factory Test Equipment in order to test the redesigned BSAR and GCB. The Offeror’s Factory Test Equipment approach will include development of

GCB Circuit Card Assembly Factory Test Equipment required in addition to GFE GCB Factory Test Equipment to meet Factory Acceptance Test (FAT) requirements provided in Section C.

The Offeror’s test approach shall describe the test programs, development of test procedures, in-process testing, analyses, and inspections that it will implement to verify MK48 Mod 7 G&C Sections and MK48 Mod 7 CBASS

Upgrade Kits are in compliance with the requirements of the contract baseline.

The Offeror shall optimize requirements verification plans to reduce schedule impacts. The Offeror shall discuss in the proposal how it plans to inspect and test items built by subcontractors, including the identification of the party responsible for Quality Assurance.

3.1.1.6. Highly Accelerated Stress Screen (HASS)/ Margin Testing/ Proof of Life (POL) Testing

The Offeror shall provide its plans for performing Highly Accelerated Stress Screening (HASS) on the G&C

Functional Item Replacements (FIRs) at the FIR level for production deliveries per 8595331 (Attachment 1).

The Offeror shall include plans for Margin Testing and Proof of Life (POL) Testing per 8595331 (Attachment 1).

The Offeror’s plan shall include a detailed schedule showing the resources required, at a minimum, the thermal chambers, electro-dynamic vibration tables, hardware fixtures, special cabling, test sets/automatic test sets and personnel required. The Offeror’s plan shall identify the total quantity of FIR hardware required to perform vibration and thermal HASS, Margin Testing, and POL testing. The Offeror’s plan shall provide a throughput analysis that identifies the choke points in the 100% Factory Acceptance Test HASS for production and demonstrates the ability to meet delivery quantities proposed.

NOTE: In order to meet HASS test requirements in previous production contracts, thermal testing alone has required the GCB tester for 50 hours, not including retest. Further allowance should be assumed for retest, vibration, full functional FAT prior to and following HASS, and other potential test set demands such as fault isolation both for production and hardware return.

3.1.1.7. Manufacturing Processes, Throughput, & Facilities

The Offeror shall include a production throughput analysis demonstrating its ability to meet delivery requirements in

Section F (reference Attachment 2 – Shipping Instructions Data) and identifying where production capacity may be limited. The Offeror shall provide a material and manufacturing process flow chart from material receipt, inspection, and storage through final delivery. The Offeror shall describe its overall manufacturing approach including production processes, procedures, collection and storage of test data, material handling and controls for the fabrication of the MK48 Mod 7 G&C Sections and MK48 Mod 7 CBASS Upgrade Kits.

The Offeror shall include description of Factory Test Equipment maintenance, sparing and engineering support in the throughput analysis to ensure Factory Test Equipment availability is sufficient to support production requirements.

The Offeror shall describe and identify the production level documentation that the offeror will use to produce the

MK48 Mod 7 G&C Sections and CBASS Upgrade Kits. The Offeror shall describe how it will implement FIR level assembly.

The Offeror shall describe the operational status of existing manufacturing facilities, or how manufacturing facilities will be established. The Offeror shall describe any specialized test facilities that will be required for environmental testing and the objectives, limitations, thresholds, and goals for environmental testing. The Offeror shall describe the physical manufacturing test capabilities for production verification and factory acceptance testing of the contract end items. The Offeror shall describe whether the production test capabilities are located on-site or if the Offeror will outsource test capabilities for production verification and testing.

3.1.1.8. Parts Management

The Offeror shall discuss how it will manage parts issues throughout the period of performance of this contract as required in Section C, section 3.3.1.2. This includes obsolescence management, parts selection process, screening for counterfeit parts, parts list or Bill of Materials (BOM), subcontractor management, part and supplier quality, part level documentation, substitute and alternative part authorization, customer-contractor teaming, lead-free electronic parts, and long lead time material.

3.1.1.9. Security Requirements

The Offeror shall provide its plans to establish and maintain a facility to meet security requirements identified in

Section C, section 3.3.1.1.

3.1.1.10. Contractor On-Site Support

The Offeror shall describe plans for contractor support at the Naval Undersea Warfare Center (NUWC) Division

Keyport (Washington), and Division Newport (Rhode Island) during the production delivery phase of the contract to support failure analysis, fault isolation, on and off line repair, and warranty and conditional acceptance support.

3.1.1.11. Electrostatic Discharge (ESD) Control Program

The Offeror shall describe its ESD control program to minimize effects to ESD sensitive components, assemblies and equipment.

3.1.1.12. Software Development Plan (SDP)

The Offeror shall develop a Software Development Plan that meets the software development requirements of the solicitation with regards to the Software and Firmware requirements of the G&C Section and of the Transmitter Test

Equipment in accordance with the following clauses and CDRL A022:

HQ L-2-0016 SOFTWARE DEVELOPMENT PLAN (NAVSEA) (DEC 2006)

(a) As part of the proposal, offerors shall submit an initial SDP that at a minimum addresses the requirements of

Section C. The initial SDP shall not be subject to the technical proposal page limitation of the solicitation. Offerors are advised however, that initial SDPs, which are concise and well-written, may receive more favorable consideration than those that contain extraneous material and/or brochuremanship.

(b) Offerors shall also submit an SDP rationale which describes why their specific approach is appropriate for the system to be procured, developed or maintained and how their proposed processes are equivalent to those articulated by CMMI capability level 3. The SDP rationale is subject to the technical proposal page limitation of the solicitation and shall not exceed 20 pages.

HQ L-2-0017 SOFTWARE DEVELOPMENT AND CMMI OR EQUIVALENT EXPERIENCE (NAVSEA) (DEC

2006)

(a) Offerors shall submit a description of previous relevant experience, within the past 24 months in developing software of the similar size and complexity as that required under the statement of work. As a part of this description, the offerors shall describe the extent to which personnel who contributed to these previous efforts will be supporting any resultant contract.

(b) Offerors shall also describe any previous relevant CMMI or equivalent model-based process maturity appraisals performed within the past 24 months. 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. This description shall not exceed 5 pages.

The descriptions called for under paragraphs (a) and (b) above are subject to the technical proposal page limitation of the solicitation.

As a part of the proposal, offerors shall submit a draft version of their SDP in accordance with the content defined in the SOW. The SDP may be formatted as desired by the Offeror but must contain the information described by the

SDP DID. The SDP is not page limited. N SDP, if it is to-the-point and appropriate, may be preferable to a SDP that is excessively wordy and contains non-essential material.

Offerors shall also submit, as a part of their proposal, an SDP Rationale which describes why their specific approach is appropriate for the system to be procured and how their proposed processes are equivalent to those articulated by

CMMI capability level 3.

Offerors shall submit a description of previous experience in developing software of the same nature as this solicitation. As a part of this description, the offerors shall describe the extent to which personnel who contributed to these previous efforts will be supporting this solicitation.

Offerors shall submit a description of previous experience in developing software using the same or similar processes and approaches as proposed for this solicitation. Offerors shall describe the extent to which personnel who contributed to these previous efforts will be supporting this solicitation. Offerors shall also 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.

3.1.2. CHAPTER 2.0 Subfactor 2: Management Approach

3.1.2.1. Program Management Plan

The Offeror shall describe the program management methodology based on the principles of Integrated Product and

Process Development to ensure the timely communication of program, technical, cost and schedule status information to the Governments management team.

The Offeror shall deliver a Program Management Plan showing how the schedule required by the solicitation will be accomplished. The Program Management Plan shall address the requirements of Section C and CDRL A001. The

Program Management Plan shall include the Offeror’s proposed Integrated Master Schedule (IMS). The IMS shall include milestones, stages, and activities consistent with the proposed Program Management Plan. The IMS should align to the contract line item number structure, the contract work breakdown structure, show an allocation of tasks between the prime and subcontractors, and the appropriate SOW and specification paragraph. The Program

Management Plan and IMS shall provide sufficient evidence that the proposal activities, processes and procedures will accomplish the requirements in this solicitation. The Offeror shall identify the program’s critical path, associated risks and mitigation plans.

The Offeror shall present a detailed work plan and schedule, including production milestones and a work breakdown structure (WBS), identifying the specific tasks (events) required to design, fabricate, and test the MK48 Mod 7 G&C

Sections and CBASS Upgrade Kit items. The WBS must include lower breakdown levels where the Offeror identifies risk associated with technical issues or resources and identify control plans whether or not the items are reported back to the Government. The cost risks shall be contained in the Volume II: Cost/Price Proposal, if risks contain actual cost data/information.

The Offeror shall provide organizational chart and supporting narrative describing the key personnel proposed to manage the contractual commitments including lines of control, responsibilities, functional relationships, and authority between the key personnel and the offeror’s other organizational elements. The offeror shall also describe all interfaces between the contractor and the Government. The offeror shall provide plan for obtaining clearances by the time of performance for personnel supporting this contract, as specified in the DD254. This plan shall include confirmation of existing clearances and/or a schedule for obtaining new clearances. Also the offeror shall identify the Senior Technical Representative (STR) designated to manage tasks. Include a resume for the STR (if the STR's resume is included elsewhere in the proposal, identify its location, do not resubmit). Address the STR's authority, ability to independently commit company resources to performance under the contract, and the STR's line of communication to senior company management. Describe the STR's previous experience managing similar efforts.

(Note: The STR does not need to be a Key or Non-Key Person directly charging to the task order).

3.1.2.2. Organizational Management

The Offeror shall describe how engineering, production, quality, test, and management teams are integrated to overcome production risks from geographic distance and organizational structures. The Staffing plan provided in

Volume I will be utilized in evaluation of the Offeror’s Organization Management. Describe the qualifications of the key personnel, which shall be leads for each proposed functional areas. All Key Personnel shall have a minimum of

5 years of experience in their respective field demonstrating specific capability, knowledge, and relevant experience for contract(s) of similar scope and complexity. The Offeror’s Key Personnel narratives shall demonstrate the individual’s depth of experience and qualification to perform the scope of work required. The requirements for the staffing plan are provided in paragraph 3.1.5.6.

3.1.2.3. Risk Management

The Offeror shall describe its risk management process to identify and mitigate cost, schedule and technical risks.

The Offeror shall identify what are considered to be at least five of the greatest risks, and provide a mitigation approach for each.

3.1.2.4. Configuration Management

The Offeror shall describe its configuration management program, how the program is organized and how the program will be conducted. Describe the methods, procedures and controls in place to maintain effective configuration identification, change control, status accounting, and audits of total configuration hardware, software, and documentation.

3.1.2.5 Small Business Participation

The Offeror shall provide a description of the small business subcontracting plan (minus cost elements) with details to support meeting PEO SUB’s small business goals as stated in Note D of Section B clause, “SMALL BUSINESS

SUBCONTRACTING INCENTIVE” or a detailed explanation as to why the goal cannot be included in the plan.

The Offeror shall propose a Small Business Participation percentage for this Contract. A Small Business offeror shall indicate the percentage of work performed by themselves, as well as any Small Business Subcontractors.

Proposals submitted by Large Business Concerns shall indicate the percentage of work performed by Small Business

Subcontractors.

3.1.2.6 Work for Private Party Agreements

The Offeror shall describe and provide copies of any Work for Private Party Agreements with Government agencies to be used to meet the requirements of the contract within Section 5.11 of their proposal. The Offeror shall describe the scope of work under WFPPA and how the agreements will be managed.

3.1.2.7 Subcontractor Management Plan

If teaming or subcontracting is contemplated, Offerors must discuss agreements/arrangements with its subcontractors and why such agreements will benefit the Government and aid the contractor in achieving the requirements and objectives of this effort throughout the life of the contract. If teaming or subcontracting is contemplated, Offerors must provide a full description of:

-the proposed subcontractors or team members;

-the planned division of tasks with the team (percentage and description of subcontracting and or allocation to peer team members);

-benefits to the Government of the teaming agreements;

-the management structure for coordinating and controlling subcontractors and/or team members;

-subcontracting deliveries to the prime, team deliveries to the prime, and payment tracking and reporting;

-points of contact;

-the sole bearer of ultimate responsibility of performance.

3.1.3 CHAPTER 3.0 Subfactor 3: Quality Approach

3.1.3.1 Process Quality

The Offeror shall provide detailed process flow diagrams identifying test and inspection points for each FIR, and for test and inspection of the full G&C section. The proposal shall demonstrate how production will be accomplished utilizing continuous improvement to reduce manufacturing defects.

The Offeror shall identify the quality personnel and how they are integrated into design, manufacturing, and product assurance activities.

3.1.3.2 Quality Management System

The Offeror shall describe internal quality assurance methods and processes including how quality assurance methods and processes will identify, assess, mitigate, implement and document substandard workmanship or nonconforming products. Describe any ISO or AS9100C certifications.

The Offeror shall provide a draft Quality Program Plan (QPP) in Section 5.12 of Volume I, Technical proposal that documents the Quality Management System that will be used to validate design, manufacturing processes, and product assurance to meet all requirements. The Quality Program Plan shall, at a minimum, address the requirements of Section C and CDRL A020. The QPP shall meet all Quality Assurance Surveillance Plan (Attachment 7) criteria. The QPP shall not be subject to the technical proposal page limitation of the solicitation.