N66604-15-R-150131.pdf
PDF 378 KB Posted
- Solicitation number
- N66604-14-R-0594
About this file
Solicitation
View the file
Other files
| File | Type | Posted |
|---|---|---|
| NPT_JA_14031_Redacted.pdf | ||
| N66604-15-4-0131MOD1.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CODE
(Hour)
PAGE(S)
until local time
X
A X B X C X D
EX
X
G F 48 - 58
59 - 63 X H dawn.griffin@navy.mil
RATING PAGE OF PAGES
7. ISSUED BY
(Date)
IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.
Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)
Prescribed by GSA FAR (48 CFR) 53.214(c)
DO-C9 1 63
(If other than Item 7)
15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO
AND
ADDRESS
SIGN OFFER (Type or print)
OF
OFFEROR
AMENDMENT NO. DATE
15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS
IS DIFFERENT FROM ABOVE - ENTER
SUCH ADDRESS IN SCHEDULE.
18. OFFER DATE
1. THIS CONTRACT IS A RATED ORDER
UNDER DPAS (15 CFR 700)
2. CONTRACT NO.
N66604 8. ADDRESS OFFER TO
See Item 7
9. Sealed offers in original and 0 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in
CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.
10. FOR INFORMATION
CALL:
A. NAME (NO COLLECT CALLS)
DAWN A GRIFFIN 401-832-4005
11. TABLE OF CONTENTS
SOLICITATION/ CONTRACT FORM
SUPPLIES OR SERVICES AND PRICES/ COSTS
2 - 6
X I CONTRACT CLAUSES
DESCRIPTION/ SPECS./ WORK STATEMENT X
PACKAGING AND MARKING
7 - 21 22 - 23
J LIST OF ATTACHMENTS
INSPECTION AND ACCEPTANCE
DELIVERIES OR PERFORMANCE
24 - 25 26 - 27
X K
REPRESENTATIONS, CERTIFICATIONS AND
OTHER STATEMENTS OF OFFERORS
CONTRACT ADMINISTRATION DATA 28 - 32 X
SPECIAL CONTRACT REQUIREMENTS
OFFER (Must be fully completed by offeror) 33 - 38 M
L INSTRS., CONDS., AND NOTICES TO OFFERORS
EVALUATION FACTORS FOR AWARD
NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.
is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.
13. DISCOUNT FOR PROMPT PAYMENT
(See Section I, Clause No. 52.232-8)
14. ACKNOWLEDGMENT OF AMENDMENTS
(The offeror acknowledges receipt of amendments
AMENDMENT NO. DATE
to the SOLICITATION for offerors and related documents numbered and dated):
FACILITY
12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period
SOLICITATION, OFFER AND AWARD
X
(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)
PART I - THE SCHEDULE
26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE
EMAIL:TEL: (Signature of Contracting Officer)
CODE CODE
B. TELEPHONE (Include area code) C. E-MAIL ADDRESS
AWARD (To be completed by Government)
19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION
22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:
10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)
23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM
24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE
PART IV - REPRESENTATIONS AND INSTRUCTIONS
PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS
39 - 46
PART II - CONTRACT CLAUSES
NAVAL UNDERSEA WARFARE CTR. DIV., NPT.
DAWN A. GRIFFIN, CODE 0221
CONTRACTS DEPARTMENT
1176 HOWELL STREET, BLDG. 1258
NEWPORT RI 02841
401-832-4005
401-832-4820FAX:
TEL:
FAX:
TEL:
NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".
SOLICITATION
6. REQUISITION/PURCHASE NO.5. DATE ISSUED
17 Oct 2014
4. TYPE OF SOLICITATION
SEALED BID (IFB)
NEGOTIATED (RFP)
[ X ]
3. SOLICITATION NO.
N66604-15-R-0131
Section B - Supplies or Services and Prices
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
0001 Lot XTDAS Engineering Services
CPFF
Services in accordance with the Statement of Work, Clause C12
Estimated Number of Hours: 189,600
FOB: Destination
ESTIMATED COST
FIXED FEE
TOTAL EST COST + FEE
0002 Lot Other Direct Costs (ODCs)
COST
Other Direct Costs associated with labor under CLIN 0001.
Notes:
(1) This is a NOT TO EXCEED AMOUNT CLIN
(2) This CLIN is NON-FEE BEARING
(3) This CLIN contains Material Overhead
ESTIMATED COST
0003 Lot Contract Data Requirements Lists (CDRLs)
Data in accordance with Exhibit A, Contract Data Requirements Lists (CDRLs), DD Form 1423
NOT SEPARATELY PRICED
NET AMT
CLAUSES INCORPORATED BY FULL TEXT
HQ B-2-0007 LIMITATION OF COST OR LIMITATION OF FUNDS LANGUAGE
The clause entitled "LIMITATION OF COST" (FAR 52.232-20) or "LIMITATION OF FUNDS" (FAR 52.232-22), as appropriate, shall apply separately and independently to each separately identified estimated cost.
HQ B-2-0014 PAYMENTS OF FEE(S) (COMPLETION) (NAVSEA) (MAY 1993)
(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, "fixed fee" in cost-plus-fixedfee type contracts for completion and phase type contracts.
(b) The Government shall make payments to the Contractor, subject to and in accordance with the clause in this contract entitled "FIXED FEE" (FAR 52.216-8) or "INCENTIVE FEE", (FAR 52.216-10), as applicable. Such payments shall be equal to TBD percent (TBD) of the allowable cost of each invoice submitted by and payable to the Contractor pursuant to the clause of this contract entitled "ALLOWABLE COST AND PAYMENT" (FAR 52.216-7), subject to the withholding terms and conditions of the "FIXED FEE" or "INCENTIVE FEE" clause, as applicable (percentage of fee is based on fee dollars divided by estimated cost dollars, including facilities capital cost of money).
Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract.
(c) In the event of discontinuance of the work under this contract, or any specified phase of the contract, in accordance with the clause of this contract entitled "LIMITATION OF FUNDS" (FAR 52.232-22) or "LIMITATION OF COST" (FAR 52.232-20), as applicable, the fee shall be equitably adjusted by mutual agreement to reflect the diminution of work. If the adjusted fee is less than the sum of all fee payments made to the Contractor under this contract, the Contractor shall repay the excess amount to the Government. If the adjusted fee exceeds all payments made to the Contractor under this contract, the Contractor shall be paid the additional amount, subject to the availability of funds. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract at the time of the discontinuance of work.
(d) Fee(s) withheld pursuant to the terms and conditions of this contract shall not be paid until the contract has been modified to reduce the fee(s) in accordance with paragraph (c) above, or until the Procuring Contracting Officer has advised the paying office in writing that no fee adjustment is required.
HQ B-2-0015 PAYMENTS OF FEE(S) (LEVEL OF EFFORT) (NAVSEA) (MAY
1993)
(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, or "fixed fee" in cost-plus-fixed-fee type contracts for level of effort type contracts.
(b) The Government shall make payments to the Contractor, subject to and in accordance with the clause in this contract entitled "FIXED FEE" (FAR 52.216-8) or "INCENTIVE FEE", (FAR 52.216-10), as applicable. Such payments shall be equal to percent ( %) of the allowable cost of each invoice submitted by and payable to the Contractor pursuant to the clause of this contract entitled "ALLOWABLE COST AND PAYMENT" (FAR 52.216-7), subject to the withholding terms and conditions of the "FIXED FEE" or "INCENTIVE FEE" clause, as applicable (percentage of fee is based on fee dollars divided by estimated cost dollars, including facilities capital cost of money).
Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract.
(c) The fee(s) specified in SECTION B, and payment thereof, is subject to adjustment pursuant to paragraph (g) of the special contract requirement entitled "LEVEL OF EFFORT." If the fee(s) is reduced and the reduced fee(s) is less than the sum of all fee payments made to the Contractor under this contract, the Contractor shall repay the excess amount to the Government. If the final adjusted fee exceeds all fee payments made to the contractor under this contract, the Contractor shall be paid the additional amount, subject to the availability of funds. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract at the time of the discontinuance of work.
(d) Fee(s) withheld pursuant to the terms and conditions of this contract shall not be paid until the contract has been modified to reduce the fee(s) in accordance with the "LEVEL OF EFFORT" special contract requirement, or until the Procuring Contracting Officer has advised the paying office in writing that no fee adjustment is required.
HQ B-2-0020 TRAVEL COSTS - ALTERNATE I (NAVSEA) (DEC 2005)
(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its reasonable actual travel costs in accordance with FAR 31.205-46. The costs to be reimbursed shall be those costs accepted by the cognizant DCAA.
(b) Reimbursable travel costs include only that travel performed from the Contractor's facility to the worksite, in and around the worksite, and from the worksite to the Contractor's facility.
(c) Relocation costs and travel costs incident to relocation are allowable to the extent provided in FAR 31.205-35; however, Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incident to relocation.
(d) The Contractor shall not be reimbursed for the following daily local travel costs:
(i) travel at U.S. Military Installations where Government transportation is available,
(ii) travel performed for personal convenience/errands, including commuting to and from work, and
(iii) travel costs incurred in the replacement of personnel when such replacement is accomplished for the Contractor's or employee's convenience.
HQ B-2-0021 CONTRACT SUMMARY FOR PAYMENT OFFICE (COST
TYPE) (FEB 1997)
This entire contract is cost type.
B18 SUPPLIES/SERVICES AND PRICES - IDIQ (SEP 2001)
(a) This is an indefinite delivery - indefinite quantity contract with cost plus fixed fee provisions. Individual Orders under this contract will be issued on either a term or completion form basis.
(b) The Contractor shall, in accordance with orders issued by the ordering officer, perform work assignments within the parameters of the Statement of Work.
(c) The services and material to be ordered hereunder shall be reimbursed in accordance with the provisions of the clauses herein entitled, Allowable Cost and Payment (FAR 52.216-7) and Fixed Fee (FAR 52.216-8), the terms of which are construed to apply, on an individual basis, to each order issued. For the purpose of establishing the fixed fee for each order issued under this contract, refer to the clause in this section entitled, Payment of Fee(s).
Section C - Descriptions and Specifications
HQ C-1-0001 ITEM(S) - DATA REQUIREMENTS (NAVSEA) (SEP 1992)
The data to be furnished hereunder shall be prepared in accordance with the Contract Data Requirements List, DD Form 1423, Exhibit A , attached hereto.
HQ C-2-0002 ACCESS TO PROPRIETARY DATA OR COMPUTER SOFTWARE
(NAVSEA) (JUN 1994)
(a) Performance under this contract may require that the Contractor have access to technical data, computer software, or other sensitive data of another party who asserts that such data or software is proprietary. If access to such data or software is required or to be provided, the Contractor shall enter into a written agreement with such party prior to gaining access to such data or software. The agreement shall address, at a minimum,
(1) access to, and use of, the proprietary data or software exclusively for the purposes of performance of the work required by this contract, and (2) safeguards to protect such data or software from unauthorized use or disclosure for so long as the data or software remains proprietary. In addition, the agreement shall not impose any limitation upon the Government or its employees with respect to such data or software. A copy of the executed agreement shall be provided to the Contracting Officer. The Government may unilaterally modify the contract to list those third parties with which the Contractor has agreement(s).
(b) The Contractor agrees to: (1) indoctrinate its personnel who will have access to the data or software as to the restrictions under which access is granted; (2) not disclose the data or software to another party or other Contractor personnel except as authorized by the Contracting Officer; (3) not engage in any other action, venture, or employment wherein this information will be used, other than under this contract, in any manner inconsistent with the spirit and intent of this requirement; (4) not disclose the data or software to any other party, including, but not limited to, joint venturer, affiliate, successor, or assign of the Contractor; and (5) reproduce the restrictive stamp, marking, or legend on each use of the data or software whether in whole or in part.
(c) The restrictions on use and disclosure of the data and software described above also apply to such information received from the Government through any means to which the Contractor has access in the performance of this contract that contains proprietary or other restrictive markings.
(d) The Contractor agrees that it will promptly notify the Contracting Officer of any attempt by an individual, company, or Government representative not directly involved in the effort to be performed under this contract to gain access to such proprietary information. Such notification shall include the name and organization of the individual, company, or Government representative seeking access to such information.
(e) The Contractor shall include this requirement in subcontracts of any tier which involve access to information covered by paragraph (a), substituting "subcontractor" for "Contractor" where appropriate.
(f) Compliance with this requirement is a material requirement of this contract.
HQ C-2-0011 COMPUTER SOFTWARE AND/OR COMPUTER DATABASE(S)
DELIVERED TO AND/OR RECEIVED FROM THE GOVERNMENT
(NAVSEA) (APR 2004)
(a) The Contractor agrees to test for viruses all computer software and/or computer databases, as defined in the clause entitled "RIGHTS IN NONCOMMERCIAL
COMPUTER SOFTWARE AND NONCOMMERCIAL COMPUTER SOFTWARE
DOCUMENTATION" (DFARS 252.227-7014), before delivery of that computer software or computer database in whatever media and on whatever system the software is delivered.
The Contractor warrants that any such computer software and/or computer database will be free of viruses when delivered.
(b) The Contractor agrees to test any computer software and/or computer database(s) received from the Government for viruses prior to use under this contract.
(c) Unless otherwise agreed in writing, any license agreement governing the use of any computer software to be delivered as a result of this contract must be paid-up and perpetual, or so nearly perpetual as to allow the use of the computer software or computer data base with the equipment for which it is obtained, or any replacement equipment, for so long as such equipment is used. Otherwise the computer software or computer database does not meet the minimum functional requirements of this contract. In the event that there is any routine to disable the computer software or computer database after the software is developed for or delivered to the Government, that routine shall not disable the computer software or computer database until at least twenty-five calendar years after the delivery date of the affected computer software or computer database to the Government.
(d) No copy protection devices or systems shall be used in any computer software or computer database delivered under this contract to restrict or limit the Government from making copies. This does not prohibit license agreements from specifying the maximum amount of copies that can be made.
(e) Delivery by the Contractor to the Government of certain technical data and other data is now frequently required in digital form rather than as hard copy. Such delivery may cause confusion between data rights and computer software rights. It is agreed that, to the extent that any such data is computer software by virtue of its delivery in digital form, the Government will be licensed to use that digital-form data with exactly the same rights and limitations as if the data had been delivered as hard copy.
(f) Any limited rights legends or other allowed legends placed by a Contractor on technical data or other data delivered in digital form shall be digitally included on the same media as the digital-form data and must be associated with the corresponding digital-form technical data to which the legends apply to the extent possible. Such legends shall also be placed in human-readable form on a visible surface of the media carrying the digital-form data as delivered, to the extent possible.
HQ C-2-0015 DATE/TIME PROCESSING REQUIREMENT--INFORMATION
TECHNOLOGY (NAVSEA) (SEP 2009)
(a) All information technology (IT), whether commercial or noncommercial, delivered under this contract that will be required to perform date/time processing involving dates subsequent to December 31, 1999, shall be Year 2000 compliant if properly installed, operated, and maintained in accordance with the contract specifications and applicable documentation. If the contract requires that specific deliverables operate together as a system, this requirement shall apply to those deliverables as a system.
(b) "Information Technology" or "IT," as used in this requirement, means "information technology" as that term is defined at FAR 2.101, and further including those items that would otherwise be excluded by paragraph (c) of that definition. "Year 2000 compliant" (as defined at FAR 39.002) means that the IT accurately processes date/time data (including), but not limited to, calculating, comparing, and sequencing) from, into, and between the twentieth and twenty-first centuries, and the years 1999 and 2000 and leap year calculations, to the extent that other IT, used in combination with the IT being delivered, properly exchanges date/time data with it. The "proper exchange" of date/time data shall be in accordance with the interface requirements specification(s) of the contract.
(c) For line item deliverables which are commercial items (as defined at FAR 2.101), and which include commercial IT, the terms and conditions of the standard commercial warranty covering such commercial IT shall apply in addition to, and to the extent such terms and conditions are consistent with, this requirement. Any applicable commercial warranty shall be incorporated into this contract by attachment.
(d) Notwithstanding any provision to the contrary in any other warranty of this contract, or in the absence of any such warranty(ies), the remedies available to the Government under this requirement shall include those provided in the Inspection clause(s) of this contract.
Nothing in this requirement shall be construed to limit any rights or remedies the
Government may otherwise have under this contract.
(e) Unless specified elsewhere in the contract, the Contractor will also deliver to the Government a report summarizing any Year 2000 compliance testing that was performed, and the results thereof.
(f) The remedies available to the Government for noncompliance with this requirement shall remain available for one hundred eighty (180) days after acceptance of the last deliverable IT item under this contract (including any option exercised hereunder).
HQ C-2-0032 INFORMATION AND DATA FURNISHED BY THE
GOVERNMENT - ALTERNATE II (NAVSEA) (SEP 2009)
(a) NAVSEA Form 4340/2 or Schedule C, as applicable, Government Furnished Information, attached hereto, incorporates by listing or specific reference, all the data or information which the Government has provided or will provide to the Contractor except for
(1) The specifications set forth in Section C, and
(2) Government specifications, including drawings and other Government technical documentation which are referenced directly or indirectly in the specifications set forth in Section C and which are applicable to this contract as specifications, and which are generally available and provided to Contractors or prospective Contractors upon proper request, such as Federal or Military Specifications, and Standard Drawings, etc.
(b) Except for the specifications referred to in subparagraphs (a)(1) and (2) above, the Government will not be obligated to provide to the Contractor any specification, drawing, technical documentation or other publication which is not listed or specifically referenced in NAVSEA Form 4340/2 or Schedule C, as applicable, notwithstanding anything to the contrary in the specifications, the publications listed or specifically referenced in NAVSEA Form 4340/2 or Schedule C, as applicable, the clause entitled "GOVERNMENT PROPERTY" (FAR 52.245-1) or "GOVERNMENT PROPERTY INSTALLATION OPERATION SERVICES " (FAR 52.245-2), as applicable, or any other term or condition of this contract.
(c)(1) The Contracting Officer may at any time by written order:
(i) delete, supersede, or revise, in whole or in part, data listed or specifically referenced in NAVSEA Form 4340/2 or Schedule C, as applicable; or
(ii) add items of data or information to NAVSEA Form 4340/2 or Schedule C, as applicable; or
(iii) establish or revise due dates for items of data or information in NAVSEA
Form 4340/2 or Schedule C, as applicable.
(2) If any action taken by the Contracting Officer pursuant to subparagraph (c)(1) immediately above causes an increase or decrease in the costs of, or the time required for, performance of any part of the work under this contract, the contractor may be entitled to an equitable adjustment in the contract amount and delivery schedule in accordance with the procedures provided for in the "CHANGES" clause of this contract.
HQ C-2-0059 UPDATING SPECIFICATIONS AND STANDARDS (NAVSEA)
(AUG 1994)
If, during the performance of this or any other contract, the contractor believes that any contract contains outdated or different versions of any specifications or standards, the contractor may request that all of its contracts be updated to include the current version of the applicable specification or standard. Updating shall not affect the form, fit or function of any deliverable item or increase the cost/price of the item to the Government. The contractor should submit update requests to the Procuring Contracting Officer with copies to the Administrative Contracting Officer and cognizant program office representative for approval. The contractor shall perform the contract in accordance with the existing specifications and standards until notified of approval/disapproval by the Procuring Contracting Officer. Any approved alternate specifications or standards will be incorporated into the contract.
HQ C-2-0065 SOFTWARE DEVELOPMENT REQUIREMENTS (NAVSEA) (DEC 2006) (MODIFIED) (SEP 2012)
(a) The contractor shall define a general Software Development Plan (SDP) appropriate for the computer software effort to be performed under this contract. The SDP shall, at a minimum:
(1) Define the contractor's proposed life cycle model and the processes used as a part of that model. In this context, the term "life cycle model" is as defined in IEEE Std. 12207:2008;
(2) Contain the information defined by ISO/IEC/IEEE 15289:2011, section 7.3 (generic content) and the Mapping of ISO/IEC 12207:2008 (IEEE Std. 12207:2008) Clauses to Information Items for Each Software Life Cycle Process in Table 2 of ISO/IEC/IEEE 15289:2011. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted;
(3) Identify the specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification;
(4) Document all processes applicable to the system to be acquired, including the Primary, Supporting, and Organizational life cycle processes as defined by IEEE Std. 12207:2008 as appropriate. Such processes shall be equivalent to those articulated by CMMI®;
(5) Include the content defined by all information items listed in Table 2 of ISO/IEC/IEEE 15289:2011, as appropriate for the system and be consistent with the processes proposed by the developers;
(6) Adhere to the characteristics defined in section 6.1 ISO/IEC/IEEE 15289:2011, as appropriate;
(7) Describe the overall life cycle and include primary, supporting, and organizational processes based on the work content of this contract;
(8) Be in accordance with the framework defined in IEEE Std. 12207:2008, including, but not limited to, defining the processes, the activities to be performed as a part of the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks;
(9) Contain a level of information sufficient to allow the use of the SDP as the full guidance for the developers. In accordance with 7.3 of ISO/IEC/IEEE 15289:2011, such information shall at a minimum contain, specific standards, methods, tools, actions, reuse strategy, and responsibility associated with the development and qualification of all requirements, including safety and security.
(b) The SDP shall be delivered to the Government for concurrence under CDRL and shall not vary significantly from that proposed to the Government for evaluation for award. The contractor shall follow the Government concurred with SDP for all computer software to be developed or maintained under this effort. Any changes, modifications, additions or substitutions to the SDP also require prior Government concurrence.
C12 STATEMENT OF WORK - IDIQ (SEP 2001)
Services shall be performed in accordance with the Statements of Work which are included in the individual orders.
These Statements of Work detail efforts that fall within the scope of the basic contract.
Statement of Work
1.0 BACKGROUND
NAVSEA System Command Program Management Sea, PMS 404, 425, and 450, and NAVSEA System Command PMS 397 have tasked Naval Undersea Warfare Center Division, Newport (NUWCDIVNPT) Codes 252 and 253 to direct the conduct of system performance, certification, calibration and developmental testing for new construction and acquisition programs and in-service Command, Control, Communications, Computer, Coordination and Intelligence (C5I) System technology refresh and technology insertion efforts. Among the programs included are:
Ohio Class Replacement Program, VIRGINIA (SSN 774) Class Submarine Program and its Non-Propulsion Electronics System (NPES); weapons systems and associated interfacing systems including sonar, combat control, external communications systems, imaging, electronic warfare systems, navigation, Netherlands, Turkey, Royal Australian Navy (RAN), Brazil, Canada and other potential Foreign Military Sales (FMS) Combat or weapon systems; and Submarine Combat System Capability Assessment program (SCS CAP) test programs. At-sea Testing events include Weapons System Accuracy Trials (WSAT), VIRGINIA Warfare Material Certification Program (VWMCP), and Follow-on Developmental Test and Evaluation (FDT&E). These test programs will hereafter be referred to as the NUWC Test Program.
To maximize the quality and speed of data processing required by this tasking in the most cost effective manner, NUWC Codes 252 and 253 support the development of automated test tools. In the Department of Defense (DoD) Small Business Innovative Research (SBIR) FY2003 Program Solicitation 03-1, proposals were requested for “Innovative Test Data Analysis Technologies”. System Engineering Associates Corporation (SEA CORP) proposed and was selected for Phase I, Phase II, and Phase III awards under topic number N03-16. The SEA CORP automated test tool technology developed under these awards, Extensible Markup Language Test Data Analysis Tool (XTDAS), provides an automated method for collecting Combat and Weapon System message data, sonar data and launcher data, and then analyzing and/or displaying the collected data in a format that can be utilized for data verification and reporting purposes. Additionally, XTDAS provides real-time automated data validation capability during actual laboratory, dockside, and at-sea test events.
Sponsors of this work are NAVSEA Program Management Systems (PMS) 397, 404, 425, 450, and Joint Program Office (JPO) (inclusive of RAN), Codes to be involved in the sponsorship of this tasking include 252 and 253.
Funding for this tasking includes Other Procurement Navy (OPN) for production units, Operation and Maintenance Navy (OMN) for maintenance, for Research, Development, Test & Evaluation (RDT&E) prototyping, Special Deposits (SPDP) for the Royal Australian Navy (RAN) efforts, which are conducted under an existing Armaments Control Program (ACP), Foreign Military Sales (FMS) for support of FMS cases, and Ships Construction Navy (SCN) for construction.
2.0 SCOPE
The contractor shall continue to develop, upgrade, and adapt XTDAS technology to provide a means to collect and analyze Submarine Non Propulsion Electronic System (NPES) and other combat and weapon system data for Test and Evaluation (T&E). XTDAS development includes both hardware and software for data collection, analysis, as well as data reduction tools. XTDAS Technology shall be utilized by NUWCDIVNPT test programs. This includes developing and maintaining various XTDAS hardware and software variants for each Technical Insertion/Advanced Processor Build (TI/APB) cycle as required for each class of US Submarines and Foreign Military Submarines and associated systems hardware and software. US submarine classes include the SSN-688/688I class, SSN-21 class, SSN 774 class, SSBN/SSGN 726 class, and the Ohio Replacement class. Submarines from foreign countries include Canada, Brazil, Netherlands, Turkey, Japan, Taiwan, and other. The XTDAS tool will be used by NUWCDIVNPT to support Developmental and Operational Test planning and execution efforts for all US and Foreign Submarines that utilize the United States Navy’s Technology Insertion Advance Processing Builds (TI/APB) variants and the Ohio Class Replacement (OCR) Submarines. The contractor shall utilize the XTDAS to provide Subsystem test, evaluation, integration, system engineering, technical, and XTDAS support services (as described in detail in Section 4.0) to NUWC and other Navy activities and organizations, including foreign Navy combat system test and evaluation programs; to perform system level and weapon compatibility testing, software and hardware testing, systems engineering, and integration, installation, and certification of Submarine combat system related electronics during new construction and at the Command and Control Module Off-Hull Assembly, and Test Site (COATS). The contractor shall adapt the XTDAS technology to support planning and preparation for Ohio Replacement Program (ORP) test program.
3.0 APPLICABLE DOCUMENTS
Number Name Task Number
3.1 NAVSEAINST 9093.2A, Submarine Combat System Certification and Assessment Program
4.2.1
3.2 DoD Directive 5000.1 4.1
3.3 DoD Instruction 5000.2 “Defense Acquisition Management Documentation 4.1 and Reports”
3.4 NUWCDIVNPT Administrative Publications 11,255 4.1
3.5 ORP Master Development Schedule 4.1, 4.2.3
3.6 ORP Capabilities Development Document 4.1, 4.2.3
3.7 Virginia Class Master Development Schedule 4.1, 4.2.1, 4.2.2, 4.2.3
3.8 Virginia Class Operational Requirements Document 4.1, 4.2.1, 4.2.2, 4.2.3
3.9 Virginia Class Test and Evaluation Master Plan 4.1, 4.2.1, 4.2.2, 4.2.3
3.10 Joint Fleet Maintenance Manual (JFMM) 4.0
3.11 Virginia Class COATS Test Plan 4.1, 4.2.1, 4.2.2, 4.2.3
3.12 Security Policy Training for Individuals Requiring Access to Briefings/
Documents Containing VIRGINIA Class Stealth Performance Data 4.1, 4.2.1, 4.2.2, 4.2.3
3.13 FY14 Virginia Class Test Schedule 4.1, 4.2.1, 4.2.2, 4.2.3
3.14 FMS Brazil Integrated Combat System (ICS) specifications (Tupi) 4.1
3.15 FMS Brazil Integrated Combat System (ICS) specifications (Tikuna) 4.1
3.16 Code 252 FMS Testing Planning Schedule 4.2.1
3.17 IEEE/EIA 12207.0 Guide for Information Technology (GIT) – Software
Lifecycle Processes (SLP) 4.1
3.18 IEEE/EIA 12207.1 GIT – SLP Lifecycle Data 4.1
3.19 Virginia Block 3 Data Management Plan 4.2.2
4.0 REQUIREMENTS
In accordance with applicable document 3.10 and other applicable documents as identified in each task, the contractor shall provide engineering services as detailed in the following tasks for all programs and platforms discussed in Section 2.0. The tasks shall be accomplished in accordance with Government Specifications and Standards in Section 3.0 and within the scope of the tasks specified below. These tasks shall be performed in accordance with Government Furnished Information (GFI) identified in Section 6.0, Task and Delivery Orders, and Technical Instructions (TI).
4.1 Extensible Markup Language (XML) Test Data Analysis Tool (XTDAS) Adaptation
In accordance with applicable documents 3.2, 3.3, 3.5, 3.6, 3.7, 3.8, 3.9, 3.11, 3.12, 3.13, 3.14, 3.15, 3.17, and 3.18, the contractor shall adapt the XTDAS to meet the requirements of the applicable test program. The Contractor shall adapt XTDAS to support the Ohio Class Replacement Test Program (ORTP) for all US and Foreign Submarines that utilize the United States Navy’s Technology Insertion Advance Processing Builds (TI/APB) variants. This ORTP XTDAS configuration shall support conduct of ORP Developmental Test and Evaluation (DT&E) and Initial Operational Test and Evaluation (IOT&E). The contractor shall establish a preliminary XTDAS support plan for the systems onboard the ORP platform. The contractor shall define a list of all sub-systems affected by the ORP Critical Design Document (CDD) and ensure that the constructed test approach covers these systems. The Test Data collection approach for the ORP system shall be defined in preliminary format. This data collection approach shall be utilized as the starting point for configuring the XTDAS system to support test preparation.
The contractor shall establish and maintain a software engineering process in accordance with applicable documents 3.17 and 3.18 to meet the requirements of the contract and achieve XTDAS performance. The software engineering process shall be documented in a Software Development Plan (SDP). The contractor shall tailor the requirements identified in applicable documents 3.17 and 3.18 as applicable to the XTDAS program and the tailoring shall be included as part of the SDP.
Using GFI 6.4, 6.5, 6.6, and 6.7, the Contractor shall adapt the XTDAS to interface with ship’s system interfaces on board VIRGINIA (SSN 774) Class submarine platforms for all US and Foreign Submarines that utilize the United States Navy’s Technology Insertion Advance Processing Builds (TI/APB) variants. The XTDAS configuration shall support the conduct of WSAT and VWMCP shipboard events. The Contractor shall identify the required hardware and software configuration changes needed to integrate the XTDAS variant to the WSAT AND VWMCP test platforms. The Contractor shall obtain, manufacture, incorporate, and install the required hardware and software changes and verify expected vs. received data. At the completion of the contract the Contractor shall provide XTDAS hardware and computer software as defined in FAR 52.227-20 (such as computer programs that comprise a series of instructions, rules, routines, or statements, regardless of the media in which recorded, that allow or cause a computer to perform a specific operation or series of operations statements), to the Government.
At the completion of the contract the contractor shall provide detailed XTDAS software definition documentation as defined in FAR 52.227-20 (such as owner’s manuals, user’s manuals, installation instructions, operating instructions, and other similar items, that explain the capabilities of the computer software or provide instructions for using the software), to the Government. The contractor shall deliver all adapted software.
Using Applicable Documents 3.14 and 3.15, the Contractor shall adapt the XTDAS to interface with foreign Navy submarine ship’s systems. The XTDAS configuration shall support the conduct of laboratory and shipboard test events. The Contractor shall identify the required hardware and software configuration changes needed to integrate the XTDAS variant to the foreign Navy combat systems and test platforms. The Contractor shall obtain, manufacture, incorporate, and install the required hardware and software changes and verify expected vs. received data. At the completion of the contract the Contractor shall provide XTDAS hardware and computer software as defined in FAR 52.227-20 (such as computer programs that comprise a series of instructions, rules, routines, or statements, regardless of the media in which recorded, that allow or cause a computer to perform a specific operation or series of operations statements), to the Government.
At the completion of the contract the contractor shall provide detailed XTDAS software definition documentation as defined in FAR 52.227-20 (such as owner’s manuals, user’s manuals, installation instructions, operating instructions, and other similar items, that explain the capabilities of the computer software or provide instructions for using the software), to the Government. The contractor shall deliver all adapted software.
4.2 Test & Evaluation
4.2.1 Test Planning
In accordance with applicable documents 3.1, 3.7, 3.8, 3.9, 3.11, 3.12, 3.13, and 3.16, the Contractor shall support test planning for combat and weapon system testing related to all classes of U.S. submarines as well as foreign Navy submarines. Test planning shall include development of test plans, test procedures, data collection plans, and test reporting requirements. This will include all types of test events and activities including system performance, certification, calibration and developmental testing for new construction/acquisition programs and in-service Command, Control, Communications, Computer, Coordination and Intelligence (C5I) System technology refresh and technology insertion efforts. Among the programs included are: the VIRGINIA (SSN 774) Class Submarine Program and its Non-Propulsion Electronics System (NPES); SCS CAP weapons systems and associated interfacing systems including sonar, combat control, external communications systems, imaging, electronic warfare systems, and navigation; Royal Australian Navy (RAN), Brazil, Canada and other potential Foreign Military Sales (FMS) Combat or weapon systems test programs.
The Contractor shall support FMS Case combat and weapon system testing identified in test plans and procedures and shall assess whether all test requirements are met.
The Contractor shall perform the following activities as part of test planning:
a. Verify each platform’s combat and weapon system configuration to identify major hardware and software upgrades and data collection requirements.
b. Review System Employment Manuals (SEMs) and functional documentation for each combat system platform configuration assess whether that test planning accounts for required fleet employment and system functional capabilities.
c. Operate the combat and weapon system to be tested in laboratory and shipboard environments.
d. Develop a SCS CAP test data plan, customized for each platform and submit to SCS CAP Technical
Program Manager (TPM) for approval.
e. Coordinate each platform schedule with respective submarine squadron.
f. Configure an XTDAS variant for each platform to verify expected vs. received data.
The Contractor shall verify data collection requirements for the various test events during dockside availability.
The Contractor shall provide an XTDAS variant to support the laboratory, dockside, and at-sea test events.
The Government will provide the contractor with a Test Plan for each test event that defines the framework of the required testing. The contractor shall develop test procedures for execution of the Government requirements
4.2.2 Test Conduct
In accordance with applicable documents 3.7, 3.8, 3.9, 3.11, 3.12, and 3.13 the Contractor shall conduct laboratory, dockside, and at-sea testing in accordance with the test plans developed in 4.2.1 above. As part of test conduct and in accordance with test plans developed in 4.2.1, the Contractor shall collect required data for XTDAS analysis. The contractor shall manage collected test data in accordance with applicable document 3.19.
The Contractor shall install XTDAS in laboratories and on the test submarine platforms and remove upon completion of testing. Testing at Submarine builders facilities shall be conducted by the Contractor to verify the XTDAS is ready for at-sea testing. The Contractor also shall conduct testing at Command and Control Module Off-Hull Assembly and Test Site (COATS) facilities in support of VIRGINIA test events.
4.2.3 Test Data Analysis
In accordance with applicable documents 3.5, 3.6, 3.7, 3.8, 3.9, 3.11, 3.12, and 3.13 and utilizing XTDAS Technology, the Contractor shall process and analyze the data collected during testing to assess whether test objectives and system acceptance can be made for the above tests.
The Contractor shall finalize the data collection capability approaches and work to define the XTDAS hardware and software requirements needed to collect the data defined in section 4.1 for ORP, VIRGINIA, and foreign Navy combat and weapon systems DT&E and IOT&E during laboratory availabilities (period of time when the XTDAS can be connected to actual system hardware).
4.3 Reporting/Meeting Support/Data Management/Production Buys
Resource Management - The Contractor shall develop, recommend, provide, prepare, maintain, ship, stage, store test facility equipment, instrumentation, consumable material, and other resources required to support test conduct.
The contractor shall attend Working Group Meetings, Working Integrated Product Team (WIPT) meetings and Commander Operational Test and Evaluation Force (COMOPTEVFOR) Mission Based Testing Design (MBTD) meetings to gain detailed insight to the combat and weapon system design and to assess the adequacy of the XTDAS configuration.
Data Management – The Contractor shall maintain full accountability for all test data including data logging, recording, backup, storage, packaging and mailing for all data collected during testing. Contractor shall adhere to Alternative or Compensatory Control Measures (ACCM) Classified handling procedures.
The Contractor shall deliver test reports for each test. The Contractor shall deliver a Data Collection Program Plan (DDPP) that addresses the data collection requirements to support developmental and operational testing.
5.0 PROGRESS REPORTS
The Contractor shall deliver monthly cost and performance reports in accordance with the basic contract Clause C16
COST AND PERFORMANCE REPORTING.
6.0 GOVERNMENT FURNISHED INFORMATION (GFI)
Number Name Task Number
6.1 Database Design Document for the TI-10/APB09 Digital Data Collection System
– Information Server (DDCS-IS), P007294, Revision D, 1 June 2012
4.1
6.2 Software Requirements Specification (SRS) for the Digital Data Collection System, P000056, Revision B, 21 May 2004
4.1
6.3 Software Requirements Specification (SRS) for the Tactical Control System (TCS) Digital Data Collection System (DDCS) Computer Software Configuration Item Final, 22 June 2009
4.1
6.4 NUWCDIVNPTINST 5500.4b, Naval Undersea Warfare Center Division, Newport Security Manual, Change 2, 31 January 2012
4.1
7.0 QUALITY SURVEILLANCE AND PERFORMANCE STANDARDS
7.1 Surveillance
The Government will conduct quality surveillance via various methods including formal and informal meetings, review of technical reports, review of monthly progress reports, and review of deliverables.
7.2 Evaluation
Contractor performance shall be evaluated in the areas of technical quality, responsiveness, timeliness and cost.
Technical quality shall be evaluated against the performance standards defined in the Performance Requirements Summary (PRS) Table incorporated into the contract as Attachment 1. Responsiveness shall be evaluated based upon the Government's experience interacting with the Contractor during performance. Timeliness shall be evaluated based on the Contractor's ability to meet CDRL schedules with minimal variance. Cost shall be evaluated based upon the Contactor's ability to manage to the negotiated costs.
ECMRA
Enterprise‐wide Contractor Manpower Reporting Application (ECMRA)
The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Naval Undersea Warfare Center Division, Newport, RI via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil.
C16 COST AND PERFORMANCE REPORTING (OCT 2012)
(a) The Contractor agrees to upload the Contractor's Funds and Man-hour Expenditure Reports in the Electronic Cost Reporting and Financial Tracking (eCRAFT) System and submit the Contractor’s Performance Report on the day and for the same timeframe the contractor submits an invoice into Wide Area Workflow (WAWF). Compliance with this requirement is a material requirement of this contract. Failure to comply with this requirement may result in contract termination.
(b) The Contractor's Funds and Man-hour Expenditure Report reports contractor expenditures for labor, materials, travel, subcontractor usage, and other contract charges.
(c) The Contractor's Performance Report indicates the progress of work and the status of the program and of all assigned tasks. It informs the Government of existing or potential problem areas.
(1) Access:
a) eCRAFT: Reports are uploaded through the Electronic Cost Reporting and Financial Tracking (eCRAFT) System Periodic Report Utility (EPRU). The EPRU spreadsheet and user manual can be obtained at: http://www.navsea.navy.mil/nuwc/newport/contracts/default.aspx under eCRAFT information. The eCRAFT e-mail address for report submission is: Ecraft.nuwc.npt.fct@navy.mil . If you have problems uploading reports, please see the Frequently Asked Questions at the site address above.
b) WAWF: See SectionG – Clause HQ G-2-0009 and 252.232-7006.
(2) Format.
a) eCRAFT: Data shall be reported in a format acceptable to the Electronic Cost Reporting and Financial Tracking System (eCraft) as defined in the EPRU manual.
b) Contractor’s Performance Report: The pages shall be sequentially numbered. All attachments shall be identified and referenced in the text of the report. The report shall be prepared in the contractor's format and shall be legible and suitable for reproduction. Electronic submission is mandatory.
(3) Scope and Content. Costs incurred under this contract/task order are to be segregated at the lowest level of performance, either task, subtask or Technical Instruction (TI), rather than on a total task contract/order basis.
a) eCRAFT: Supporting documentation in eCRAFT shall include summaries of work charged during the period covered.
b) Contractor’s Performance Report:
(i) Provide a front cover sheet that indicates the contractor's name and address, the contract number, the system or program nomenclature, the report date, the reporting period, the report title and a serial number for the report, the security classification, the name and address of the person who prepared the report, and the name of the issuing Government activity (Naval Undersea Warfare Center Division, Newport).
(ii) Report contract schedule status. Describe the progress made against milestones during the reporting period.
(iii) Report any significant changes to the contractor's organization or methods of operation, to the project management network, or to the milestone chart, including the addition/deletion of any subcontractors and key personnel
(iv) Report problem areas affecting technical, scheduling, or cost elements. Provide background and recommendations for solutions. Report results (positive or negative) obtained related to previously identified problem areas, with conclusions and recommendations.
(v) Report all trips and significant results. This shall be a full breakdown, including locations, names of the people who travelled, and costs.
(vi) Report all significant communications and any commitments made thereby. Include all non-contractual communications, such as technical instructions, e-mails, telephone conversations, etc.
(vii) Report Engineering Change Proposal (ECP) status. Identify all ECPs by status, i.e., proposed, approved and implemented.
(viii) Report plans for activities during the following reporting period.
(ix) Include appendices for any necessary tables, references, photographs, illustrations, charts, etc.
(4) Submission and Approval.
a) The contractor shall submit their reports on the same day and for the same timeframe the contractor submits an invoice into WAWF. The amounts shall be same. eCRAFT Approval will be indicated by e-mail notification from eCraft.
b) Distribution Statement. Distribution Statement B: Distribution to U.S. Government agencies only;
Proprietary Information; (date data generated). Other requests for this document shall be referred to NUWCDIVNPT Code 59.
(d) The contractor shall not provide other funds, man-hour, or status reporting without the prior written approval of the contracting officer.
C25 ACCESS TO GOVERNMENT SITE (OCT 2009)
(a) Contractor personnel shall comply with all current badging and security…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .