ATT0032 REVISED ST-1 CDRL SE003 Pre Deployment Meeting.pdf
PDF 142 KB Posted
- Attached to
- TOTAL ENGINEERING and INTEGRATION SERVICES-TEIS IV Federal contract opportunity
- Solicitation number
- W9128Z-20-R-0001
About this file
This document package includes a federal contract opportunity solicitation and a pre-deployment meeting checklist data item.
The solicitation is for Total Engineering and Integration Services to support the United States Army Information Systems Engineering Command. Required services include full life cycle engineering support for information and communication systems, from planning and design through sustainment and retirement. Support is needed worldwide, including in secure facilities, remote locations, and sometimes hostile areas with limited infrastructure. The solicitation was issued by the Department of the Army Materiel Command Army Contracting Command located at Aberdeen Proving Ground.
The pre-deployment meeting checklist data item is a template to be completed after an assessment team pre-deployment meeting. It addresses administrative details, responsibilities, tools, conduct expectations, security controls validation, and projected deadlines. The checklist is due no more than one business day after the pre-deployment meeting to the technical monitor, contracting officer's representative, and government project lead.
View the file
Other files for this federal contract opportunity
Show all 50
TOTAL ENGINEERING and INTEGRATION SERVICES-TEIS IV has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DD FORM 1423-1, FEB 2001
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
PREVIOUS EDITION MAY BE USED.
Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
TDP ________ TM _______ OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE
7. DD 250 REQ
8. APP CODE
9. DIST STATEMENT
REQUIRED
10. FREQUENCY
11. AS OF DATE
12. DATE OF FIRST SUBMISSION
13. DATE OF SUBSEQUENT
SUBMISSION
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
Draft Final
Reg Repro
15. TOTAL
16. REMARKS
17. PRICE GROUP
18. ESTIMATED
TOTAL PRICE
G. PREPARED BY H. DATE I. APPROVED BY J. DATE
Page of Pages
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
TDP ________ TM _______ OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
16. REMARKS (Continued)
DD FORM 1423-1, FEB 2001 Page of Pages
INSTRUCTIONS FOR COMPLETING DD FORM 1423
(See DoD 5010.12-M for detailed instructions.)
FOR GOVERNMENT PERSONNEL
Item A. Self-explanatory.
Item B. Self-explanatory.
Item C. Mark (X) appropriate category: TDP - Technical Data Package;
TM - Technical Manual; Other - other category of data, such as "Provisioning,""Configuration Management," etc.
Item D. Enter name of system/item being acquired that data will support.
Item E. Self-explanatory (to be filled in after contract award).
Item F. Self-explanatory (to be filled in after contract award).
Item G. Signature of preparer of CDRL.
Item H. Date CDRL was prepared.
Item I. Signature of CDRL approval authority.
Item J. Date CDRL was approved.
Item 1. See DoD FAR Supplement Subpart 4.71 for proper numbering.
Item 2. Enter title as it appears on data acquisition document cited in Item 4.
Item 3. Enter subtitle of data item for further definition of data item (optional entry).
Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.
Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work paragraph number).
Item 6. Enter technical office responsible for ensuring adequacy of the data item.
Item 7. Specify requirement for inspection/acceptance of the data item by the Government.
Item 8. Specify requirement for approval of a draft before preparation of the final data item.
Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24).
Item 10. Specify number of times data items are to be delivered.
Item 11. Specify as-of date of data item, when applicable.
Item 12. Specify when first submittal is required.
Item 13. Specify when subsequent submittals are required, when applicable.
Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.
Item 15. Enter total number of draft/final copies to be delivered.
Item 16. Use for additional/clarifying information for Items 1 through 15.
Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14.; Desired medium for delivery of the data item.
FOR THE CONTRACTOR
Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.
a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort (production, development, testing, and administration) but which is required by DD Form 1423.
Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.
b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.
Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.
c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.
Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and delivering such data item to the Government.
d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.
Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.
Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data.
These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government's right to use the data shall be governed by the pertinent provisions of the contract.
DD FORM 1423-1 (BACK), FEB 2001
RMF SCA Pre Deployment Meeting
Click here to enter system name
Click here to enter a date.
1. ADMINISTRATIVE:
Contract Mod Received: <Date>
CIA Level:
Approved CIA Categorization Memo uploaded to eMASS: <Yes/No>
Have all documentation ONLY CCIs been addressed by the team: <Yes/No>
2. RESPONSIBILITIES (Enter Names):
Project Lead:
Government Lead:
On-Site Team Lead:
Contractor Lead:
In Brief & Out Brief:
Security Control Interviews:
Controls Author(s):
<For large efforts you may also want to make additional assignments. The following are just examples. Modify as needed; Delete if not needed.>
Data Collector: <If the team lead is unable to track and organize documents and scan data, the role of data collector may be necessary. The data collector is responsible for ensuring the collection and organization of all test data.>
Test Scheduler: <Again, if the team lead is unable to run the test schedule, he/she may want to appoint a scheduler to creates and manage the testing schedule while on site to include keeping track of who tested the box.>
Physical Security: <Responsible for all Physical Security controls.>
3. TOOLS:
Information Security Evaulation Laptop (ISEL)
Picked up?
Tested?
Have Necessary SW Licenses?
Who’s transporting?
Software Tools
What tools are required?
Does the team have latest versions?
Pre-Visit Tasks
4. CONDUCT WHILE ON SITE: <The team lead should discuss his/her conduct expectations while on site. The following are just some examples. This section should be customized to the team and location.>
Dress code
1st & last day, professional attire for in and out briefs
Otherwise, business attire or dress appropriately if tracing cables etc.
Discussions/disagreements in private
Don’t be an alarmist; discuss issues internally before taking to the customer.
Provide advice, guidance, and assistance (for SE efforts) but don’t recommend changes be made on the spot.
5. SECURITY CONTROLS: <The team lead should discuss how the evaluation, analysis and input of security controls into eMASS will be handled. Will they be divided among the team members or will every team member report what they observe in all areas? This section will also be customized to the effort and document the team lead’s expectations. >
6. FIND THE GOOD!
Look for and report on practices, processes, procedures, equipment, anything that would fall into the “doing good” category.
7. VALIDATION: <The team lead will discuss the sampling philosophy and the idea that we do not just grab data and run. The first couple of boxes tested must be thoroughly evaluated to include performing and documenting manual checks (unknown, other, errors) and verifying vulnerabilities found by the tools. The team lead can customize this section, as long as it meets the MED sampling philosophy to include performing a thorough check of at least two boxes of each type. >
8. HOT WASHES: <The team lead will address how the daily hot washes will be conducted. The following is just an example, this area should be customized to meet the team lead’s expectations.>
-- Status of testing
-- Status of data collection
-- Good stuff
-- Issues
9. PROJECTED DEADLINES: <Include projected deadlines here if SharePoint Project data has not yet been completed. Insure ALL deadlines are updated in SharePoint.>
Version 2, November 2015
| data_item: SE003 |
| title: Pre Deployment Meeting Checklist |
| sub: |
| auth: N/A |
| ref: Sample Task 1 para 3.1.2, 3.2 |
| req_ofc: USAISEC |
| dd250: N/A |
| appcode: N/A |
| dist: |
| freq: See Blk 16 |
| asof: |
| firstsub: See Blk 16 |
| subsub: See Blk 16 |
| addressee1: COR |
| draft1: |
| reg1: 1 |
| repro1: |
| addressee2: TM |
| draft2: |
| reg2: 1 |
| repro2: |
| addressee3: Gov Project Lead |
| draft3: |
| reg3: 1 |
| repro3: |
| addressee4: |
| draft4: |
| reg4: |
| repro4: |
| addressee5: |
| draft5: |
| reg5: |
| repro5: |
| addressee6: |
| draft6: |
| reg6: |
| repro6: |
| addressee7: |
| draft7: |
| reg7: |
| repro7: |
| addressee8: |
| draft8: |
| reg8: |
| repro8: |
| addressee9: |
| draft9: |
| reg9: |
| repro9: |
| addressee10: |
| draft10: |
| reg10: |
| repro10: |
| addressee11: |
| draft11: |
| reg11: |
| repro11: |
| addressee12: |
| draft12: |
| reg12: |
| repro12: |
| addressee13: |
| draft13: |
| reg13: |
| repro13: |
| addressee14: |
| draft14: |
| reg14: |
| repro14: |
| addressee15: |
| draft15: |
| reg15: |
| repro15: |
| addressee16: |
| draft16: |
| reg16: |
| repro16: |
| addressee17: |
| draft17: |
| reg17: |
| repro17: |
| addressee18: |
| draft18: |
| reg18: |
| repro18: |
| addressee19: |
| draft19: |
| reg19: |
| repro19: |
| addressee20: |
| draft20: |
| reg20: |
| repro20: |
| addressee21: |
| draft21: |
| reg21: |
| repro21: |
| addressee22: |
| draft22: |
| reg22: |
| repro22: |
| addressee23: |
| draft23: |
| reg23: |
| repro23: |
| addressee24: |
| draft24: |
| reg24: |
| repro24: |
| addressee25: |
| draft25: |
| reg25: |
| repro25: |
| addressee26: |
| draft26: |
| reg26: |
| repro26: |
| addressee27: |
| draft27: |
| reg27: |
| repro27: |
| addressee28: |
| draft28: |
| reg28: |
| repro28: |
| addressee29: |
| draft29: |
| reg29: |
| repro29: |
| addressee30: |
| draft30: |
| reg30: |
| repro30: |
| addressee31: |
| draft31: |
| reg31: |
| repro31: |
| addressee32: |
| draft32: |
| reg32: |
| repro32: |
| addressee33: |
| draft33: |
| reg33: |
| repro33: |
| addressee34: |
| draft34: |
| reg34: |
| repro34: |
| addressee35: |
| draft35: |
| reg35: |
| repro35: |
| addressee36: |
| draft36: |
| reg36: |
| repro36: |
| addressee37: |
| draft37: |
| reg37: |
| repro37: |
| addressee38: |
| draft38: |
| reg38x: |
| repro38: |
| total_draft: 0 |
| total_reg: 3 |
| total_repro: 0 |
| remarks: Date of first and subsequent submissions: The Pre Deployment Meeting will be scheduled in conjunction with the Government Project Lead. The Pre Deployment Meeting Checklist is due no later than 1 business day, by 4PM Arizona time, after the Pre Deployment Meeting is completed. The Pre Deployment Meeting process will be in accordance with the USAISEC Cybersecurity Process Manual. |
Format: Template will be provided as part of the USAISEC Cybersecurity Assessment and Security Engineering Manual.
Content: Provide deliverable that is technically sound, logically organized, coherent, and free of typographical and grammatical errors following the approved template provided in the USAISEC Cybersecurity Assessment and Security Engineering Manual.
Method of delivery: One (1) soft copy of the checklist shall be submitted to the Technical Monitor, Contracting Officer’s Representative (COR) and Government Project Lead via CD/DVD or e-mail, and included as an artifact in the DCAFS Archive. The checklist shall be fully identified and referenced in the subject line of the email message. The document shall not be locked or protected in any fashion that would prevent text to be copied or edited by the Government after delivery.
| group: |
| total_price: |
| prep_name: |
| line_item: |
| exhibit: |
| xtdp: Off |
| xtm: Off |
| othercat: X |
| system: |
| ctr_no: |
| contr: |
| remarksb: |
| Page2: 2 |
| Reset: |
| prep_date: |
| app_by: |
| app_date: |
| Page: 1 |
| of_pages: 3 |
| app: Adobe Professional 8.0 |
File details come from the government source that posted it. Updated .