CRS_(I)_Special_Notice.pdf
PDF 372 KB Posted
- Attached to
- Common Robotic System (Individual) CRS(I)
- Solicitation number
- W56HZV-16-R-CRSI
About this file
Special Notice - Draft Maturity Assessment Information
View the file
Other files
Show 40 more
Latest 50 of 58 listed here. See the rest on GovTribe.
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
Common Robotic System (Individual) (CRS(I))
DRAFT Maturity Assessment Information
Purpose: To inform prospective offerors how the Government intends to evaluate System Integration Maturity in the forthcoming CRS(I) Request for Proposals and how test data will be considered based upon the level of independence of the assessed test results. Substantiating data other than Government test data may be considered less credible.
The CRS(I) RFP may require offerors to perform a self-assessment of the maturity of their proposed solution in several aspects as follows:
(1) Requirement Analysis Requirements decomposition completed Functional baseline completed Derived requirement development completed Interfaces assessment completed Decomposition of System Integration requirements contained within the performance specification completed. Address both Sections 3 and 4 of the performance specification.
(2) Preliminary Design Analysis Allocated Baseline completed Component Analysis / Selection completed CAD Models completed Weight Estimated Interface Designs completed Modeling and simulation of the system design using LS-Dyna or comparable program completed
(3) System Integration, Testing and Analysis in Lab:
Architectures completed (Operator Control Unit (OCU), Mobility Base Platform (MBP), Radios, and Payloads)
Analyze materials – types, weight, cost, availability – for the OCU, MBP, Radios, Payload Integration components including arm, fiber optic spooler and cameras
System Integration, Testing, and Analysis completed in laboratory environment on the following sub-systems: OCU, Mobility Base Platform, Radios, Payloads to include arm, fiber optic spooler and cameras.
(4) System Integration, Testing and Analysis in Relevant Environment:
Architectures completed for OCU, Mobility Base Platform, Radios, and Payloads.
Analyze materials – types, weight, cost, and availability – for the OCU, MBP, and Radios, Payload Integration components including arm, fiber optic spooler and cameras.
System Integration, Testing, and Analysis completed in a relevant environment on the following systems: OCU, MBP, Radios, Payloads including arm, fiber optic spooler and cameras.
The offeror will have the opportunity to provide substantiating data to support its self-assessment. Test data is one form of substantiating data that can be provided.
The credibility assigned to any test data provided may be assessed based on both the article that was tested, (i.e. was the design being proposed what was tested) and, if not, how representative was the test article of the proposed design as well as what entity conducted the test. The credibility of test results may be considered in the following descending order, with items lower on the list being provided less credibility:
(1) Government Conducted Testing
(2) Testing Conducted by an Independent Laboratory or Test Firm
(3)Testing Conducted by the Offeror
Offeror’s Interested in the CRS(I) RFP are also advised that the Multi-robot Operator Control Unit version 4 (MOCU 4) software is potentially available to offeror’s for their consideration in the development of their software for their proposed CRS (I) solution. This distribution of the software is controlled by Space and Naval Warfare Systems Center Pacific (SSC Pacific) and is distributed at their sole discretion following the process included in this Special Notice. Ability to obtain the MOCU 4 software is not required to respond to the CRS(I) RFP. Questions regarding obtaining the software should be directed to the Points of Contact in the SSC Pacific process.
This process and LP-CRADA Application only apply to a temporary loan of MOCU 4 from SSC Pacific to a company for test and evaluation purposes in order for a company to determine if they will propose use of MOCU 4 as part of a solution for the CRS(I) program of record. A different process or application may apply to loan MOCU 4 for other purposes. Contact the SSC Pacific Technology Transfer Office at ssc_pac_t2@navy.mil for further information.
Accessing Multi-robot Operator Control Unit version 4 (MOCU 4)
Space and Naval Warfare Systems Center Pacific (SSC Pacific) will use the Limited Purpose Cooperative
Research and Development Agreement (LP-CRADA) to provide Multi-robot Operator Control Unit version 4 (MOCU 4) source code to companies interested in evaluating MOCU 4 in connection with
Army’s Common Robotic System (Individual) (CRS(I)) program. The LP-CRADA is facilitated through the
SSC Pacific Technology Transfer (T2) Office, which operates separate from the CRS(I) program.
The purpose of the LP-CRADA is a temporary loan of MOCU 4 from SSC Pacific to a company for test and evaluation purposes in order for a company to determine if they will propose use of MOCU 4 as part of a solution for the CRS(I) program. A company’s right to use MOCU 4 is limited to this purpose. The LP-
CRADA will terminate upon a company submitting a proposal to the CRS(I) program. SSC Pacific will not provide any support under the LP-CRADA (except limited operational training if necessary). At the end of
LP-CRADA, the company will discontinue use of MOCU 4, uninstall and delete MOCU 4, and supply SSC
Pacific with a report of their testing and evaluation.
If a company awarded the CRS(I) contract desires to use MOCU 4 in support of CRS(I), then SSC Pacific will work with the Army and the company to release MOCU 4 as government furnished information under the CRS(I) contract. If a company that is not awarded the CRS(I) contract desires to continue testing and evaluating MOCU 4 for other purposes, the company may negotiate a new LP-CRADA with
SSC Pacific. A full CRADA, which involves SSC Pacific and a company conducting mutually beneficial research and development, could be pursued if it is deemed to be in the best interests of both parties. It is also possible that MOCU 4 could be licensed to a company for commercial purposes.
The following are characteristics of the MOCU 4 LP-CRADA in connection with CRS(I):
Enables temporary loan of MOCU 4 for test and evaluation purposes in order for a company to determine if they will propose use of MOCU 4 as part of a solution for the CRS(I) program
Test and evaluation shall only be conducted by employees of the company
Limited duration
No collaboration
No SSC Pacific support (except for operational training if necessary)
Company receives no rights to pre-existing intellectual property or software
Foreign owned, controlled, or influenced (FOCI) companies, or companies with foreign national employees need FOCI mitigation in place. Review of requests from FOCI companies will extend the time to execute the LP-CRADA.
For any new invention made by the company under the LP-CRADA: company owns title, and company grants the Government a nonexclusive, irrevocable, paid-up license to practice the
Invention, or have the Invention practiced throughout the world by or on behalf of the
Government
Company may contact SSC Pacific to discuss entering into a full CRADA or license agreement
Agreement will terminate upon a company submitting a proposal to the CRS(I) program
Recipient provides a final report to SSC Pacific on work conducted under the LP-CRADA (T2
Office provides a sample report template)
Recipient may publish on work conducted under the LP-CRADA per the terms of the agreement
This process and LP-CRADA Application only apply to a temporary loan of MOCU 4 from SSC Pacific to a company for test and evaluation purposes in order for a company to determine if they will propose use of MOCU 4 as part of a solution for the CRS(I) program of record. A different process or application may apply to loan MOCU 4 for other purposes. Contact the SSC Pacific Technology Transfer Office at ssc_pac_t2@navy.mil for further information.
LP-CRADA Process
Event Approximate duration (days are in business days)
Approximate cumulative days (days are in business days)
Company sends completed LP-CRADA Application to SSC Pacific Technology Transfer (T2) Office at ssc_pac_t2@navy.mil
T2 Office reviews application and addresses any concerns
5 days (Note this can take days to weeks longer under special circumstances such as when the recipient is FOCI or has foreign national employees.)
5 days
T2 Office drafts LP-CRADA document and receives initial SSC Pacific legal review.
5 days 10 days
T2 Office e-mails draft LP-CRADA to SSC Pacific and company contacts (including legal) and gives 5 business days to reply with comments or concurrence
5 days 15 days
T2 Office finalizes LP-CRADA and routes for signature to company signatory first, then to SSC Pacific Commanding Officer
5 days 20 days
T2 Office emails signed, executed LP- CRADA to SSC Pacific and company contacts
N/A N/A
SSC Pacific principal investigator (PI) provides MOCU 4 to company PI via AMRDEC SAFE or SPAWAR RITE service
Agreement specifies MOCU 4 is delivered within 30 calendar days of LP-CRADA execution, but delivery typically occurs within 5 business days
N/A
Company tests and evaluates MOCU 4 under the LP-CRADA
TBD N/A
Upon LP-CRADA termination, company uninstalls and deletes, and returns or destroys MOCU 4
N/A N/A
Company provides SSC Pacific PI and T2 Office with report, including notice of any publication, invention, or modification resulting from the work done under the LP-CRADA
Agreement specifies report is due within 30 days of LP- CRADA termination
N/A
This process and LP-CRADA Application only apply to a temporary loan of MOCU 4 from SSC Pacific to a company for test and evaluation purposes in order for a company to determine if they will propose use of MOCU 4 as part of a solution for the CRS(I) program of record. A different process or application may apply to loan MOCU 4 for other purposes. Contact the SSC Pacific Technology Transfer Office at ssc_pac_t2@navy.mil for further information.
LP-CRADA Application (Email to ssc_pac_t2@navy.mil)
1. Full Company Name:
2. Company Name Acronym/Abbreviation (if any):
3. Headquarters (or preferred) Address:
4. Mailing Address:
5. Principal Investigator (Point of contact conducting work under the LP-CRADA):
a. Name:
b. Title:
c. Phone number:
d. E-mail address:
6. Preferred Contact: (Preferred point of contact for coordinating execution and follow-up for the agreement)
a. Name:
b. Title:
c. Phone number:
d. E-mail address:
7. Legal Counsel (optional): (Note that the LP-CRADA is a standardized Navy document that should be reviewed carefully prior to signature.)
a. Name:
b. Title:
c. Phone number:
d. E-mail address:
8. Individual authorized to legally bind your company to the terms of the LP-CRADA:
a. Name:
b. Title:
9. What type of organization is your company? (e.g. corporation, non-profit entity, public/private educational institution, state/local/federal government entity):
10. Is your company a small business as defined in section 2 of Public Law 85-536 (15 USC 632) and implementing regulations of the Small Business Administration?
11. Your company is duly organized, validly existing and in good standing under the laws of the following State:
12. Is your company directly or indirectly owned, controlled, or influenced by a foreign entity such as foreign parent companies or investors, as well as employees or students who are foreign citizens? (Foreign Disclosure and Export Control reviews will need to be completed for collaborations with foreign owned, controlled, or influenced (FOCI) entities.):
a. Identify the name and country of the foreign entity that owns, controls, or influences your company:
b. Define the business/professional nature of the foreign entity and its legal/business relationship to your company:
c. What is your company’s CAGE Code?
| CRS (I) Special Notice_30 Nov |
| SSC Pacific MOCU |
| Accessing_MOCU_for_Evaluation-CRS(I)_20161103 |
File details come from the government source that posted it. Updated .