Attachment_4_-_Cross_Reference_Matrix.xlsx
XLSX spreadsheet 61 KB Posted
- Attached to
- SBEAS FINAL REQUEST FOR PROPOSAL
- Solicitation number
- FA8771-17-R-1000
View the file
Other files
Show 40 more
Latest 50 of 55 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
Instructions
| SBEAS Cross Reference Matrix Instructions |
| Note 1: Only enter responses in columns B through G |
Note 2: A "Sample CRM" worksheet is provided for reference on entering information required only. No evaluation implications are intended by the examples given.
Note 3: Information entered into cells B3 - G8 will automatically populate into cells B50 - G55.
Note 4: The cells with zeros (0) in them are an internal check. The zeros mean the cells below are empty. Once a reference is typed in the cell, the zero is changed to identify how many cells are "not blank". A space, with no text, will cause the cell to count as filled.
| Step 1: Enter the Offeror name in Row 1 of the "CRM For Submission" Worksheet |
| Step 2: Enter the Contract Information: |
In Row 3 Contract Number:
-Enter the contract number being used for each contract used in the Technical Volume. Include the task order number(s) as applicable; expand the row if necessary -If an offeror submits less than six (6) contract references in the technical volume, enter "NOT USED" in the remaining cells for Row 3.
In Row 4 Customer/Organization Name:
- Enter the Customer and Organization's name who can confirm the work performed for the contract..
In Row 5 Project Title:
- Provide a short but detailed descriptive narrative (in plain English) of the project that informs the reader of the project’s purpose and intent.
In Row 6 Period of Performance (PoP):
- Enter the PoP in the following format: Day-Month-Year through Day-Month-Year DD-MMM-YY through DD-MMM-YY. If the work is still in progress, the end of the PoP may be replace with "present". See the sample CRM.
In Row 7 Customer Phone Number:
- Enter the phone number, with area code, of the customer identified in row 4. Example: (###) ###-#### In Row 8 Customer E-mail
- Enter the email address of the customer identified in row 4.
Step 3: Complete the Factor 1 TECHNICAL EXPERIENCE Cross-Reference -In rows 12 through 47, insert the page and paragraph number in columns B through G, indicating where the experience for the Column A TECHNICAL ELEMENT is demonstrated in the TECHNICAL NARRATIVE section of the Technical Volume.
Step 4: Verify the Contract Information in Rows 50 - 55:
- If less than six (6) contract references are used in the Technical volume (in Row 3), use the additional cells in Rows 50 - 55, with the Contract Number now titled "NOT USED" to insert the additional contract information for references used for the PAST PERFORMANCE volume. *Note, it is permissible to have more contract references for Past Performance than used for Technical Experience; however all contract references used for Technical Experience shall also be used for Past Performance.
Step 5: Complete the Factor 2 PAST PERFORMANCE Sub-Factor Cross-Reference -In rows 58 - 77, insert the page and paragraph number in columns B through G, indicating where the experience for the Column A PAST PERFORMANCE ELEMENT is demonstrated in the PAST PERFORMANCE NARRATIVE section of the Past Performance Volume.
Section J Attachment 4 Cross-Reference Matrix (CRM) Instructions
FA8771-17-R-1000
Page &P of &N
SAMPLE CRM
| SBEAS CROSS-REFERENCE MATRIX (Offeror: ) | ||||||
| Technical Narrative | Technical Narrative | Technical Narrative | Technical Narrative | Technical Narrative | Technical Narrative | |
| Contract Number | FA8771-14-D-0007, 0100, 0125, 0138 | FA8772 | AB1234 | XX0001 | NOT USED | NOT USED |
| Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name |
| Project Title | Project Title | Project Title | Project Title | Project Title | Project Title | Project Title |
| Period of Performance | 07-Apr-15 through 06-Apr-17 | 01-Jun-16 through present | 23-Feb-15 through present | 17-Aug-16 through 16 Aug-17 | Period of Performance | Period of Performance |
| Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number |
| Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail |
| FACTOR 1: TECHNICAL EXPERIENCE | ||||||
| Life-cycle SW Svc (Element #1): | 1 | 2 | 1 | 1 | 0 | 0 |
| 1(a) Provided development services for an Information System (IS) | ||||||
| 1(b)(1) Re-Engineering | Pages 1-3 paragraphs 4-3 | Page 4, paragraphs 3-4 | ||||
| 1(c)(2) Migration | Page 4, paragraph 3 | |||||
| 1(d)(3) Modernization | Page 7, paragraph 4 | |||||
| 1(e) ERP | Page 12, paragraphs 5-6 | |||||
| Cybersecurity (Element #2): | 0 | 1 | 0 | 1 | 0 | 0 |
| 2(a) Assess software application vulnerabilities and threats using RMF | Page 13, paragraph 2 | |||||
| 2(b) Risk Management Principles and Information Security Requirements | Page 4, paragraphs 3-4 | |||||
| IT Business Analysis (Element #3): | 0 | 0 | 1 | 2 | 0 | 0 |
| 3(a) Requirements Analysis | Page 13, paragraph 3 | |||||
| 3(b) Testing, Validation and Verification | Page 16, paragraphs 2-4 | |||||
| 3(c) Service Desk | Page 8, paragraph 3 | |||||
| 3(d) Functional Business Area Expert (FBAE) | ||||||
| Programming Lang/Frameworks (Element #4): | 1 | 0 | 1 | 0 | 0 | 0 |
| 4(a) Any 2: Java, COBOL, PowerBuilder, .NET, ColdFusion, C# | Page 7, paragraphs 3-5 | |||||
| 4(b) Any 2: JavaScript, Perl, SQL, PYTHON, PHP | Page 4, paragraph 2 | |||||
| 4(c) Any 1: SWIFT, Ruby On Rails, JavaScript MV* Frameworks, Spark | ||||||
| Tools/Dev Method (Element #5): | 1 | 0 | 1 | 0 | 0 | 0 |
| 5(a) Security | ||||||
| 5(b) Quality | Page 3, paragraph 4 | |||||
| 5(c) Testing | ||||||
| 5(d) Development Methodology | Page 6, paragraph 1 | |||||
| Platform/Environ (Element #6): | 0 | 0 | 0 | 0 | 0 | 0 |
| 6(a) Mainframe, Mid-tier/Client-server, Web Services | ||||||
| 6(b) Customer's facility | ||||||
| 6(c) Commercial, Non-commercial, Hybrid Cloud | ||||||
| 6(d) DISA DECC or DoD computing facility | ||||||
| Database Comp (Element #7): | 0 | 0 | 0 | 0 | 0 | 0 |
| 7(a) RDBMS | ||||||
| 7(b) NoSQL | ||||||
| 7(c) Data store support for RDBMS or NoSQL | ||||||
| Mobile/IoT (Element #8): | 0 | 0 | 0 | 0 | 0 | 0 |
| 8(a) New Mobile Application Development | ||||||
| 8(b) Redesigned legacy system to work or on mobile device | ||||||
| 8(c) Automatic Identification Technology (AIT) | ||||||
| Server Operating Systems (Element #9): | Page 7, paragraph 4 | |||||
| COTS/GOTS/FOSS Software (Element #10): |
| Past Performance Narrative | Past Performance Narrative | Past Performance Narrative | Past Performance Narrative | Past Performance Narrative | Past Performance Narrative | ||
| Contract Number | FA8771-14-D-0007, 0100, 0125, 0138 | FA8772 | AB1234 | XX0001 | NOT USED | NOT USED | |
| Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | |
| Project Title | Project Title | Project Title | Project Title | Project Title | Project Title | Project Title | |
| Period of Performance | 07-Apr-15 through 06-Apr-17 | 01-Jun-16 through present | 23-Feb-15 through present | 17-Aug-16 through 16 Aug-17 | Period of Performance | Period of Performance | |
| Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | |
| Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | |
| FACTOR 2: PAST PERFORMANCE | |||||||
| Sub-Factor 1: | |||||||
| Life-Cycle Software Services | 2 | 4 | 5 | 2 | 2 | 1 | |
| 1(a) System Architect and Design | Page 16, paragraph 2 | ||||||
| 1(b) Technical Solution, Design, Creation and Implementation | Page 2, paragraph 3 | Page 4, paragraph 1 | Page 6, paragraph 3 | Page 17, paragraph 1 | |||
| 1(c) Software Development Methodologies | Page 4, paragraph 3 | Page 4, paragraphs 1-2 | Page 6, paragraph 1 | Page 19, paragraph 4 | |||
| 1(d) Information Web Services Development and Testing | |||||||
| 1(e) Mobile or Internet of Things (IoT) | |||||||
| 1(f) Information Display Solutions and Services | Page 6, paragraph 3 | ||||||
| 1(g) Database Development or Conversion | Page 7, paragraphs 3-5 | ||||||
| 1(h) Automated Integration Testing and Implementation | |||||||
| 1(i) Data or System Migration | Page 4, paragraph 3 | ||||||
| 1(j) Application/System/Database/Interface Administration | Page 12, paragraph 8 | ||||||
| 1(k) Modification of F3I or Interface an In-Service Configuration Item | |||||||
| 1(l) Hardware Technology Refresh | Page 13, paragraph 3 | ||||||
| 1(m) Software Modernization | Page 3, paragraphs 3-4 | Page 7, paragraph 4 | |||||
| 1(n) Decommission Planning and Execution | |||||||
| Sub-factor 2: Cybersecurity | 0 | 1 | 0 | 1 | 1 | 1 | |
| 2(a) Confidentiality, Integrity, and Availability | Page 4, paragraphs 3-5 | ||||||
| 2(b) Authentication, Authorization, and Accountability (nonrepudiation)) | Page 12, paragraph 6; | ||||||
| Page 13, paragraph 2 | Page 16, paragraph 3 | Page 20, paragraph 2 | |||||
| Sub-Factor 3: IT Business Analysis | 0 | 0 | 1 | 1 | 1 | 1 | |
| 3(a) Functional Business Area Expertise (FBAE) in two (2) areas | Page 13, paragraph 3 | Page 16, paragraph 6 | |||||
| 3(b) Service desk, field and technical support | Page 8, paragraph 3 | Page 22, paragraph 3 |
Section J Attachment 4 Cross-Reference Matrix (CRM) Sample
Page &P of &N
CRM For Submission
| SBEAS CROSS-REFERENCE MATRIX (Offeror: ) | ||||||
| Technical Narrative | Technical Narrative | Technical Narrative | Technical Narrative | Technical Narrative | Technical Narrative | |
| Contract Number | Contract Number | Contract Number | Contract Number | Contract Number | Contract Number | Contract Number |
| Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name |
| Project Title | Project Title | Project Title | Project Title | Project Title | Project Title | Project Title |
| Period of Performance | Period of Performance | Period of Performance | Period of Performance | Period of Performance | Period of Performance | Period of Performance |
| Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number |
| Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail |
| FACTOR 1: TECHNICAL EXPERIENCE | ||||||
| Life-cycle SW Svc (Element #1): | 0 | 0 | 0 | 0 | 0 | 0 |
| 1(a) Provided development services for an Information System (IS) | ||||||
| 1(b)(1) Re-Engineering | ||||||
| 1(c)(2) Migration | ||||||
| 1(d)(3) Modernization | ||||||
| 1(e) ERP | ||||||
| Cybersecurity (Element #2): | 0 | 0 | 0 | 0 | 0 | 0 |
| 2(a) Assess software application vulnerabilities and threats using RMF | ||||||
| 2(b) Risk Management Principles and Information Security Requirements | ||||||
| IT Business Analysis (Element #3): | 0 | 0 | 0 | 0 | 0 | 0 |
| 3(a) Requirements Analysis | ||||||
| 3(b) Testing, Validation and Verification | ||||||
| 3(c) Service Desk | ||||||
| 3(d) Functional Business Area Expert (FBAE) | ||||||
| Programming Lang/Frameworks (Element #4): | 0 | 0 | 0 | 0 | 0 | 0 |
| 4(a) Any 2: Java, COBOL, PowerBuilder, .NET, ColdFusion, C# | ||||||
| 4(b) Any 2: JavaScript, Perl, SQL, PYTHON, PHP | ||||||
| 4(c) Any 1: SWIFT, Ruby On Rails, JavaScript MV* Frameworks, Spark | ||||||
| Tools/Dev Method (Element #5): | 0 | 0 | 0 | 0 | 0 | 0 |
| 5(a) Security | ||||||
| 5(b) Quality | ||||||
| 5(c) Testing | ||||||
| 5(d) Development Methodology | ||||||
| Platform/Environ (Element #6): | 0 | 0 | 0 | 0 | 0 | 0 |
| 6(a) Mainframe, Mid-tier/Client-server, Web Services | ||||||
| 6(b) Customer's facility | ||||||
| 6(c) Commercial, Non-commercial, Hybrid Cloud | ||||||
| 6(d) DISA DECC or DoD computing facility | ||||||
| Database Comp (Element #7): | 0 | 0 | 0 | 0 | 0 | 0 |
| 7(a) RDBMS | ||||||
| 7(b) NoSQL | ||||||
| 7(c) Data store support for RDBMS or NoSQL | ||||||
| Mobile/IoT (Element #8): | 0 | 0 | 0 | 0 | 0 | 0 |
| 8(a) New Mobile Application Development | ||||||
| 8(b) Redesigned legacy system to work or on mobile device | ||||||
| 8(c) Automatic Identification Technology (AIT) | ||||||
| Server Operating Systems (Element #9): | ||||||
| COTS/GOTS/FOSS Software (Element #10): |
| Past Performance Narrative 1 | Past Performance Narrative 2 | Past Performance Narrative 3 | Past Performance Narrative 4 | Past Performance Narrative 5 | Past Performance Narrative 6 | |
| Contract Number | Contract Number | Contract Number | Contract Number | Contract Number | Contract Number | Contract Number |
| Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name | Customer/Organization Name |
| Project Title | Project Title | Project Title | Project Title | Project Title | Project Title | Project Title |
| Period of Performance | Period of Performance | Period of Performance | Period of Performance | Period of Performance | Period of Performance | Period of Performance |
| Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number | Customer Phone Number |
| Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail | Customer E-mail |
| FACTOR 2: PAST PERFORMANCE | ||||||
| Sub-Factor 1: Life-cycle Software Services | 0 | 0 | 0 | 0 | 0 | 0 |
| 1(a) System Architect and Design | ||||||
| 1(b) Technical Solution, Design, Creation and Implementation | ||||||
| 1(c) Software Development Methodologies | ||||||
| 1(d) Information Web Services Development and Testing | ||||||
| 1(e) Mobile or Internet of Things (IoT) | ||||||
| 1(f) Information Display Solutions and Services | ||||||
| 1(g) Database Development or Conversion | ||||||
| 1(h) Automated Integration Testing and Implementation | ||||||
| 1(i) Data or System Migration | ||||||
| 1(j) Application/System/Database/Interface Administration | ||||||
| 1(k) Modification of F3I or Interface an In-Service Configuration Item | ||||||
| 1(l) Hardware Technology Refresh | ||||||
| 1(m) Software Modernization | ||||||
| 1(n) Decommission Planning and Execution | ||||||
| Sub-factor 2: Cybersecurity | 0 | 0 | 0 | 0 | 0 | 0 |
| 2(a) Confidentiality, Integrity, and Availability | ||||||
| 2(b) Authentication, Authorization, and Accountability (nonrepudiation)) | ||||||
| Sub-Factor 3: IT Business Analysis | 0 | 0 | 0 | 0 | 0 | 0 |
| 3(a) Functional Business Area Expertise (FBAE) in two (2) areas | ||||||
| 3(b) Service desk, field and technical support |
Section J Attachment 4 Cross-Reference Matrix (CRM) Submission
Page &P of &N
File details come from the government source that posted it. Updated .