Exhibit B - IRES CDRLs.docx
DOCX document 5 MB Posted
- Attached to
- MDA IT Operations & Engineering Solutions (MIOES) - CANCELED Federal contract opportunity
- Solicitation number
- HQ0857-MIOES-ZA
- Issued by
- DOD Missile Defense Agency
View the file
Other files for this federal contract opportunity
Show all 50
MDA IT Operations & Engineering Solutions (MIOES) - CANCELED 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
H95001-15-R-0001 Exhibit B Exhibit B – IRES Contract Data Requirements List (CDRL) The Contract Data Requirements List (CDRLs) is comprehensive but not exhaustive; the CDRLs identified on this list may be ordered under individual task orders without review / approval of the MDA/DAP.
If CDRLs not on this list are determined necessary, a new DD Form 1423 will be developed and processed through the MDA/DAP CDRL Approval Process.
| CDRL # |
| DID Number |
| DID Title |
| Subtitle |
| Description |
| B001 |
| DI-ADMN-81306/T |
| Program Protection Implementation Plan (PPIP) |
| Facility Security Procedures (FSP) |
| Defines the contractor’s implementation of the Government developed Program Protection Plan for the MDIOC. |
| B002 |
| DI-CMAN-80858 |
| Contractor’s Configuration Management Plan |
| IRES Configuration Management Plan |
| Describes the Supplying activities’ configuration management program and the methods, procedures, and controls used for effective configuration identification, change control, status accounting, and audits of the total configuration, including hardware, software and firmware. The principle use is to provide the Acquiring activity a basis for review, evaluation and monitoring of the CM program and its proposed components. |
| B003 |
| DI-MGMT-80004/T |
| Management Plan |
| IRES Program Management Plan |
| Defines the contractor’s organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs. |
| B004 |
| DI-SESS-81785 |
| System Engineering Management Plan (SEMP) |
| System Engineering Management Plan (SEMP) |
| Defines the technical approach and proposed plan for the conduct, management, and control of the integrated activities performed under the contract. |
| B005 |
| DI-SAFT-81563/T |
| Accident / Incident Report |
| Accident / Incident Report: [insert contractor or subcontractor name] |
| Provides information / situational awareness of accidents / incidents occurring at the MDIOC. |
| B006 |
| DI-ADMN-81308A |
| Conference Report |
| [Enter Task Order #]: [Enter Conference / Meeting Name and Date] |
| Documents significant understanding, directions request, recommendations or suggestions that are discussed during a conference with the contractor and the authorized Government representative(s). |
| B007 |
| DI-MISC-80508B/T |
| Scientific And Technical Reports |
| MDIOC Unified Facilities Guide Specification (MUFGS) |
| An installation standard that identifies requirements, standards, and criteria for MDIOC facility improvements and modifications. |
| B008 |
| DI-NDTI-80603A/T |
| Test Procedure |
| Test Procedure: [Insert Test Name] |
| Identifies the step-by-step testing operations to be preformed on items under going developmental, qualification, or acceptance testing. It identifies items to be tested, the test equipment and support required, the test conditions to be imposed, the parameters to be measured, and the pass/fail criteria against which the test results will be measured. |
| B009 |
| DI-NDTI-80809B |
| Test / Inspection Reports |
| Test / Inspection Report: [insert test name] |
| Documents test / inspection results, findings, and analyses that will enable the government to evaluate compliance with system requirements, performance objectives, specifications, and test / inspection plans. |
| B010 |
| DI-IPSC-81428A |
| Software Installation Plan (SIP) |
| Software Installation Plan (SIP): [insert software title] |
| Defines the plan for installing software, including preparations, user training, and conversion from existing systems. |
| B011 |
| DI-MISC-80508B/T |
| Scientific And Technical Reports |
| MDIOC Facility Evacuation Plan |
| Provides the procedures for a safe, orderly and thorough evacuation of the MDIOC workforce. |
| B012 |
| DI-SESS-81704 |
| Test Plans/Test Procedures |
| [Enter Test Title]: Test Plans/Test Procedures |
| Mandatory on all task orders conducting a test. |
| B013 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Enter Task Order #]: [Enter Report Title] |
| A technical report provides fully documented results of studies or analysis performed. |
| B014 |
| DI-MGMT-81453A/T |
| Data Accession List (DAL) |
| Data Accession List (DAL): Period Ending [insert period end date] |
| Provides a medium for identifying contractor internal data which has been generated by the contractor in compliance with the work effort described in the Statement of Work (SOW). The DAL is an index of the generated data that is made available upon request. |
| B015 |
| DI-MGMT-81808 |
| Contractor’s Risk Management Plan |
| IRES Risk Management Plan |
| Defines the Contractor’s process to monitor management, cost and schedule of the contract efforts relative to a system and equipment. This information will provide the government with risk data for all risks associated with the system/ equipment. |
| B016 |
| DI-QCIC-81794 |
| Quality Assurance Program Plan |
| IRES Quality Assurance Program Plan |
| Defines the quality / mission assurance program and the methods, procedures, and controls employed for effective mission assurance. |
| B017 |
| DI-SESS-81248B |
| Interface Control Document (ICD) |
| [Insert Task Order #, Version #, Date]: Interface Control Document (ICD) |
| Provides a record of all system, segment, and enterprise interface information (such as drawings, diagrams, tables, and textual information) for use in the troubleshooting network anomalies and responding to emergent systems integration and other technical requirements. |
| B018 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #, Event or Project Title]: Engineering Documentation |
| This CDRL contains engineering documentation which potentially includes some or all of the following components: Slide Package, DoDAF Artifacts, Rack Elevation drawings, Facility Layout drawings, CONOPS, and Requirements Traceability Matrix (RTM), Version Description Documents, and Floor Plans. |
| B019 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #]: Operational Support Documents: Capacity Management Plan |
| The Capacity Management Plan addresses current capacity considerations for technology items supported by the office of the CIO and establishes and reports on trigger points associated with the need for either increasing capacity of mitigating capacity considerations through some other innovative solution / technique. |
| B020 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #]: [Insert System Name]: Certification and Accreditation Documentation |
| This CDRL shall contain the documentation required to support C&A activities: Risk Management Framework (RMF) Packages, FISMA Report, DITPR Report, Vulnerability Scan and Compliance Reports, Accreditation Boundaries Report, Boundary Protection Configurations, BMDS RMF Comprehensive Package, DR/COOP IT Quarterly Tabletop and Annual Exercise Scenarios/Test Plan Packages generated under this TO. |
| B021 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #]: Software Accountability and Maintenance Report |
| Captures all software licenses and deployed software obtained and in-use for MDA. The report will be configured by asset ID (barcode and/or serial number), software type and version installed, and the license accountability allocation. Summary records will also be provided detailing the type of software deployed by version, number deployed and number of licenses active and on file with the software librarian. |
| B022 |
| DI-MGMT-81644B/T |
| DOD Architecture Framework Documentation |
| [Insert TO #,] [enter Version #, Date]: Enterprise Architecture: [enter Architecture Name] |
| This document provides drawings and data that is used for gathering information for future projects and in troubleshooting network anomalies. The document shall describe the characteristics pertinent to the purpose of the architecture. End-to-end documentation for all supported unclassified and classified sites along with external connections to the MDA in an Enterprise Architecture repository that separates the information into specific sections. |
| B023 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert TO #]: Cybersecurity Workforce Management Report: [Insert FYQ] |
| This CDRL reports the status of IRES contractors performing cybersecurity functions in order to verify compliance with guidelines found in DOD 8570.01-M (specified in Chapters 3, 4, 5, 10, and 11). |
| B024 |
| DI-MGMT-81644B |
| DOD Architecture Framework Documentation |
| [Insert TO #,] [enter Version #, Date]: Segment Architecture: [enter Architecture Name] |
| This document provides a technical solution for segment architectures for specific enclaves. It contains the principles, technical positions, patterns, vocabulary, drawings, and data that are used for describing characteristics pertinent to the purpose of the architecture. |
| B025 |
| DI-MGMT-81644B |
| DOD Architecture Framework Documentation |
| [Insert TO #,] [enter Version #, Date]: Reference Architecture: [enter Architecture Name] |
| This document provides a template solution for an architecture for a particular domain. It contains the principles, technical positions, patterns, vocabulary, drawings, and data that are used for describing characteristics pertinent to the purpose of the architecture. |
| B026 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #]: Operational Support Documents: MDA Enterprise Strategic Plan |
| The MDA Enterprise Strategic Plan is the single governing document that portrays the key stakeholder’s high-level vision for the enterprise. It describes the current context of the business, and delivers a strategic direction purposed to posture the capabilities that currently exist in order to realize ongoing business value generation moving forward. |
| B027 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #]: Operational Support Documents: MDA CIO Service Portfolio |
| The CIO Service Portfolio is the superset of formal services offered to partners, suppliers, internal business functions, external business functions, and customers that model after the Information Technology Infrastructure Library (ITIL) framework approach to service delivery. |
| B028 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #]: Operational Support Documents: Technology Refresh Plan |
| The Technology Refresh Plan takes into account the formally documented current state of the hardware necessary to execute business functions, deliver services, and maintain the logical relationships between customers, partners, and suppliers. Primarily, this superset will contain the system architecture, the storage architecture, and the network architecture across the enterprise. |
| B029 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #]: Quarterly Reports: [Insert Document Title]: [Insert FYQ] |
| This CDRL shall contain the Quarterly Service Level and Performance Metrics and Trend Analysis Reports, and IT Service Plans. |
| B030 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #]: Operational Support Documents: Service Pipeline |
| This CDRL is a snapshot of the Service Pipeline and defines the variety of services that are currently under development/review within the service portfolios. The Service Pipeline is a futures-based concept that defines the future direction of the service portfolio and defines the health of the portfolio; requirements under development/consideration will remain in the pipeline until transitioned to operations. |
| B031 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #]: Charge-Back Show-Back Metrics: [Insert Month Ending] |
| This CDRL identifies the consumption rates of CIO managed IT resources by 2-Ltr organization and attributes costs for shared infrastructure and office productivity to the 2-Ltr in both a show back as well as charge back methodology based on both basic and enhanced service level agreements. |
| B032 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #]: Cyber Incident Handling Process: [FY] |
| This CDRL provides enterprise-wide guidance for cybersecurity incident handling, analyzing incident data, and determining the appropriate response. |
| B033 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| [Insert Task Order #]: [Insert System Name]: Open System Architecture Management Plan |
| The Open System Management Plan describes the Offeror's approach to modular, open design; inter-component dependencies; design information documentation; technology insertion; life cycle-sustainability; interface design and management; treatment of proprietary or vendor-unique components; reuse of pre-existing or common items; and treatment of proprietary elements. |
| B034 |
| DI-ADMN-81306/T |
| Program Protection Implementation Plan (PPIP) |
| [Insert Task Order #]: [Insert Program Name]: PPIP |
| Mandatory on task orders covered by a Government Program Protection Plan |
| B035 |
| DI-MCCR-80700/T |
| Computer Software Product End Items |
| [Insert Task Order #]: [Insert Computer Software Product End Item Name] |
| Identifies the software Computer Software Product End Items to be delivered under a task order. |
| B036 |
| DI-IPSC-814XX |
| Various Software Documentation |
| [Insert Task Order #]: [Insert Software Product Name], [Insert Document Name] |
| Identifies the software documentation to be delivered under a task order. |
| B037 |
| DI-MISC-80508B/T |
| Technical Report – Study/Services |
| Operational Support Documents : Data Management Plan |
| This CDRL contains the Data Management Plan for the Business Intelligence (BI) system which includes some or all of the following components: Data Sources, Data Dictionary, Data Schema and Mapping. |
| B038 |
| DI-MISC-80508B/T |
| Technical Report – Study/Services |
| [Application Name]: Application Engineering Documentation |
| This CDRL contains engineering documentation which potentially includes some or all of the following components: Slide Package, DoDAF Artifacts, Rack Elevation drawings, Facility Layout drawings, CONOPS, and Requirements Traceability Matrix (RTM), Version Description Documents, and Floor Plans. |
| B039 |
| DI-MISC-80508B/T |
| Technical Report – Study/Services |
| [Insert Activity Number and Event or Project Title]: Baseline Engineering Documentation |
| This CDRL contains engineering documentation which potentially includes some or all of the following components: Slide Package, DoDAF Artifacts, Rack Elevation drawings, Facility Layout drawings, CONOPS, and Requirements Traceability Matrix (RTM), Version Description Documents, and Floor Plans. |
EXPLANATION OF NUMBERED BLOCKS ON THE DD FORM 1423-1
(Unnumbered blocks are for Government internal office use) Block 1: Data Item Number:
CDRL sequence number.
Block 2: Title of Data Item:
The title listed on an authorized DD Form 1664, Data Item Description.
Block 3: Subtitle:
Amplification of DID title, if it requires more descriptive identification. Also used to identify the specific title of a deliverable document.
Block 4: Authority:
Reflects the exact DID identification number. A trailing, upper case alpha character indicates a revision. If project-specific modification is required to limit either the scope or clarify usage of a DID, a “/t” will follow the number to indicate tailoring of the DID has been made. Any DID tailoring is explained in Block 16.
Block 5: Contract Reference:
Reference(s) in a contract exhibit (e.g. SOW, SOO, Specification) which generates the requirement for the data item.
Block 6: Requiring Office:
This is the office that called for or ordered the data and it will advise the contracting officer on the currency and adequacy of the Contractor’s data submission.
Block 7: DD Form 250 Required:
The activity to perform the inspection and or acceptance. Only the code “LT” (Letter of Transmittal) is used in this CDRL, indicating that the DD Form 250 is not required for delivery of data items.
Block 8: Approval Code:
The following codes are applicable to this CDRL:
| A | Used when the data is critical (such as a specification) or of a technical nature, or when the Contractor requires Government concurrence on the document in order to implement a plan or proceed to the next event (for example, test plans must be approved prior to testing). |
| (BLANK) | Acceptance/Approval is not required. |
| Block 9: | Distribution Statement Required: |
The following distribution codes are used here:
| A | Approved for public release; distribution is unlimited. |
| B | Distribution authorized to US Government agencies only. |
| C | Distribution authorized to US Government agencies and their contractors. |
| D | Distribution authorized to Department of Defense and US DoD contractors only. |
| E | Distribution authorized to DoD components only. |
| F | Further dissemination only as directed by controlling DoD office or higher DoD authority. |
| X | Distribution authorized to US Government agencies and private individuals or enterprises authorized to obtain export-controlled technical data IAW regulations implementing 10 U.S.C. 130. |
| Block 10: | Frequency: |
The following codes are used in this block:
| Code |
| Description |
| DAILY |
| Daily |
| WEKLY |
| Weekly |
| BI-WE |
| Each 2 Weeks |
| MTHLY |
| Monthly |
| BI-MO |
| Each 2 Months |
| QRTLY |
| Quarterly |
| ANNLY |
| Annually |
| SEMIA |
| Each 6 Months |
| ASGEN |
| As Generated |
| ONE/R |
| One Time with Revisions |
| R/ASR* |
| Revisions as Required |
| ASREQ* |
| As Required |
| DFDEL |
| Deferred Delivery |
| ONE/P |
| One Time Preliminary Draft |
| XTIME |
| Specific Number of Submittals (substitute a digit for the “X”) |
| SEE 16* |
| Refer to Block 16 for an explanation |
Block 11: As of Date:
If the data will be submitted only once, the “as of” date (or cut-off date) is entered as follows: Day/Month/Year. If the data is of a recurring type, the number of days prior to the end of the report period is entered; for example, “15” places the “as of” date for this report at 15 days before the end of each month, quarter, or year, depending upon the frequency established in Block 10: “0” places the “as of” date at the end of each month, quarter, etc. (Block 16 is used for further explanation.)
Block 12: Date of First Submission:
The date of submission is entered as follows: Day/Month/Year. If data is constrained by a specific event or milestone, this constraint is entered. If contract start date is not known, the number of days after contract start is entered (Example: 30 DAC). If the date is not known or requires further clarification, Block 16 is used.
Block 13: Date of Subsequent Submission:
If data is submitted more than once, the dates of subsequent submissions are entered. If data is constrained by a specific event or milestone, the constraint is entered. (Block 16 is used for further explanation.)
*When used in Block 10, 11, 12 or 13, further explanation of the requirement is entered in Block 16 to provide the Contractor with the guidance necessary to adequately scope and schedule delivery of the data item.
Block 14: Distribution:
Entered here, or in Block 16, are the addresses and the number of copies to be received by each office. Office symbols and command initials are used. The media to be used for distribution to each office is explained in Block 16.
Block 15: Total:
The total number of copies for one delivery; this number should be the sum of all the copies specified in Block 14.
Block 16: Remarks.
Used to explain:
· Tailored features of the DID;
· Items 1 through 15;
· Any resubmittal schedule or actions involved in updating data submitted for Government acceptance/approval.
Block 17:
Not used in this contract.
Block 18:
Not used in this contract.
CONTRACT DATA REQUIREMENTS LIST (CDRL) NOTES
1. The DD Forms 1423, Contract Data Requirements List (CDRL), The DD Forms 1423, Contract Data Requirements List (CDRL), are cross-referenced in Block 5 to the associated SOO tasks under which the data is generated. Format, preparation and submission instructions for each data item are contained in the individual DD Form 1423 and the associated DD Form 1664, Data Item Description (DID), referenced in the CDRL. Any comments, explanations, clarification or limitations with respect to an individual DD Form 1664 will appear in Block 16 of the DD Form 1423. In any case, the information in Block 16 of the DD Form 1423 shall be considered part of the data item preparation instructions.
2. In the context of this CDRL, a “/t” following the DID number in Block 4 of the DD Form 1423 In the context of this CDRL, a “/t” following the DID number in Block 4 of the DD Form 1423 is to be interpreted as indicating deviations from, or clarification of, the DID, and an explanation of the deviation or clarification is given in Block 16. When a “/t” is not present, the data shall comply fully with the DID requirements for both format and content. Relief from format requirements of the DID—such as through the statement, “Contractor format is acceptable”—does not relieve the contractor of the responsibility to meet the content requirements of the DID.
3. The DD Form 250 shall not be used for CDRL deliveries.
The DD Form 250 shall not be used for CDRL deliveries. All submissions shall be by letter of transmittal. (“LT” code in Block 7 of the DD Form 1423.)
| a. | Transmittal letters shall be addressed to the contracting office for this contract but all copies of data items for the IRES shall be delivered to the IRES Data Management Office. |
| b. | When data is to be delivered to more than one office in an organization outside the MDA, the data may be packaged or sent together. When data for more than one office is packaged or sent together, the data for each office shall be separated and suitably identified to facilitate correct distribution. |
| c. | Unless called for on the DD Form 1423, data items shall initially be submitted only to the MDA; complete distribution, as indicated on the DD Form 1423, shall be made only after receipt of Government acceptance/approval without comment, or expiration, without comment, of the Government’s review cycle. |
| d. | The point of delivery for all CDRL deliverable products (up to and including SECRET classification) is the MDA E-CaRT system. The Contractor shall deliver all such products by saving and profiling them to E-CaRT, with the appropriate notification of delivery letter transmitted electronically to the Government’s Data Management Office. |
| 4. | Government acceptance/approval |
When the DD Form 1423, Block 8, indicates Government acceptance/approval is required, it shall be construed to mean acceptance/approval by the KO or their designated representative. Unless a different time period for acceptance/approval is specified elsewhere in this contract, the Government will have up to 30 days to notify the Contractor concerning the acceptance/approval/rejection/disapproval of a data item. If the Contractor does not receive notice of Government acceptance/approval/rejection/disapproval within the 30-day period, the data item shall be considered accepted/approved as written. The Government reserves the right to accept/approve, reject/disapprove, or comment on any data item, regardless of the acceptance/approval code indicated on the DD Form 1423.
| a. | After receipt of government response with comments, the Contractor shall make corrections as directed and resubmit the corrected data item for Government acceptance/approval. Upon resubmission, a new acceptance/approval period will commence. If there are no additional Government comments provided, the data item shall be considered accepted/approved as written. If other Government direction is provided, the Contractor shall follow that direction. |
| b. | When rejecting/disapproving a data item, the Government will stipulate the reasons for rejection/disapproval and may grant additional time without derogating any rights the Government may have in any other clause of this contract. For periodic submissions, comments/changes shall be incorporated in the next regular submittal unless otherwise stated by the Government. Upon resubmission, a new acceptance/approval period will commence. |
| 5. | Cover and title page |
Unless otherwise specified in the CDRL, data items shall have a cover and title page (Contractor’s design) which clearly identify the data item. The title page shall contain the:
· Contract Number
· Contractor’s Name/Cage Code
· DD Form 1664 Number
· Data Item Number
· Data Item Title or Subtitle
· Signature of Contractor’s Release Authority
| a. | Concurrent with an acceptance/approval letter, the Government may direct the Contractor to remove its identifying markings from a data item and reissue a final version with a cover, title page and identifying markings of Government design. In these cases, the Contractor shall distribute and archive only this final Government version. |
| b. | All data items produced as standard text documents shall be printed (or, in the case of soft copy delivery, formatted for printing) head-to-head, utilizing both sides of common white paper. Exceptions are allowed for title pages, foldout pages and color reproductions. Heavy stock and colored or glossy paper shall not be used unless specifically requested by the Government (as, for example, in a brochure). |
| c. | Unless otherwise specified by the Government, or required by a DID, all data items shall be prepared using standard MDA desktop productivity tools (latest versions). Where a previous submittal has been made by the Contractor, and accepted/approved by the Government, the Contractor shall, to the maximum extent possible, retain the format and styles used in making revisions or resubmittals of follow-on or like data items. |
| 6. | If no changes have occurred since the last submission |
Requirements for data items, where no changes have occurred since the date of last submission, shall be satisfied by a letter from the Contractor stating, “no changes have occurred since the last submission.” In such cases, the Contractor shall identify the title and document number of data item in question, the reporting period, and the date of the prior data transmittal.
7. Submission date / times Data shall be submitted for receipt by the Government not-later-than 0800 hours (MST/MDT) on the morning after the scheduled delivery date specified in the DD Form 1423, except that due dates falling on non-working days (Saturday, Sunday, and Government and Contractor official holidays) shall be construed to mean the next regular working day following such non-working days. All due dates (e.g., 30 DAC) are calendar counted.
8. Data Management The Contractor shall maintain a single authority for Data Management to insure compliance with CDRL requirements.
May 10, 2016 Page 1 Exhibit B 10May2016.zip image1.emf
File details come from the government source that posted it. Updated .