Get documents about "Business Management Agreement
Description
Business Management Agreement document sample
Document Sample
Document Types
SORT KEY
Metadata Working
M subtypes Definition Project Information P subtypes Notes
Group
Action is broader than action
item. Action items are tracked
Action Item, RFA, in separate systems. Actions
Action item Task assignments. Action
RID include RFAs and RIDs. For
MWG, an RFA would be in a
meeting file.
Agreements between
NASA/JPL and other U.S. or
international agencies,
between NASA and JPL, or
between JPL organizations.
May include Memoranda of
Agreement, Memoranda of
M gets inconsistent with split
Understanding, Letters of
between records and
Agreement, Research and Contract, MOA,
documents. Contract and
Agreement files Technology Objectives and Agreement/Contract; MOU, OIA, WA,
agreement should go one
Plans (RTOPS), Interface Statement of Work
place; while payment info goes
Control Documents,
another
Operational Interface
Agreements, Service Level
Agreements, and Work
Agreements. Includes all
supporting records and
correspondence about the
agreement.
M says they are agreements,
but A says they are much
closer to specifications and
Agreement files Interface Control EICD, MICD, IICD
should be a standalone
category since that is what
people call them
Agreement files Business record (was Lien)
May include actual costs,
Business Financial,
personnel information and
Management Cost/Resource Procurement, WBS,
other files used in resource
Record Workforce
management.
D:\Docstoc\Working\pdf\7e6e81a1-c56e-42f0-a0ad-4ac582ec9361.xlsDoc types
Based on MY/AK discussion Jan. 24 26/05; last edited Feb.1
Other classes of documentation/records: Cat A, Cat C, uncontrolled, AIDS, ECR, Waiver, PFR?, Drawings
Page 1 of 9
Document Types
Metadata Working
M subtypes Definition Project Information P subtypes Notes
Group
Records of changes to
documentation, hardware, or See: ECR, Waiver (different
Configuration
ECR, Waivers software. Includes No equivalent information class so not
Control Record
Engineering Change included)
Requests and waivers
M gets inconsistent with split
between records and
documents. Contract and
Project copies of RFPs,
agreement should go one
Contract/Procureme proposals, contracts, and Agreement/Contract; OR
place; while payment info goes
nt Record other procurement-related Cost/Resource
another. M: Do we need this
records
when we have business
management record? M does
this absorb proposal?
Letters and emails related to
administrative management,
Correspondence Correspondence
housekeeping operations, and
mission-specific work.
Correspondence Memo
Raw data, including science
Data No equivalent
data and test data
M: Is dictionary part of
Design or
Dictionary specification or a separate doc
specification
type?
Documents about the design Design is high level;
Equipment, Material,
of a spacecraft, hardware, or specification is specific!
Design or Test, Part/Item,
software. May include Specification Design doc is a plan; M:
specification Process, Service,
documents about data, recommend we change to
System/Subsystem
command, and dictionaries. Specification
Copies of engineering
drawings, either hardcopy,
Drawing microform, or electronic, that Drawing Different information class
show experimental,
preliminary, or final versions.
D:\Docstoc\Working\pdf\7e6e81a1-c56e-42f0-a0ad-4ac582ec9361.xlsDoc types
Based on MY/AK discussion Jan. 24 26/05; last edited Feb.1
Other classes of documentation/records: Cat A, Cat C, uncontrolled, AIDS, ECR, Waiver, PFR?, Drawings
Page 2 of 9
Document Types
Metadata Working
M subtypes Definition Project Information P subtypes Notes
Group
Copies of documents which
are retained only for use as
Form or Template Form/Template
forms or templates when
creating a new document.
Art work, graphics, sound
clips, and other multimedia Electronic Image,
Graphic/Multimedia Graphic/Multimedia
files used in presentations, Physical Photo/3-D
flyers, or for other purposes
Guidance information that is
intended to assist and that is
Guide, Handbook,
Guideline not mandatory (unless Guideline
Manual
invoked by a policy,
requirement, or procedure).
Meeting or Review
Agenda
File
Agenda, Minutes, Includes agendas,
Meeting or Review Presentation, Action item, presentations, review files, Agenda; Minutes, Presentation,
File Recommendation for meeting notes, and record Action
Action, copies of minutes.
Meeting or Review
Minutes
File
Meeting or Review
Presentation
File
HRCR, RDD, SECR,
Meeting or Review File Review packages
SRCR
Project or task planning
documents. May include
Plan schedules and early forms of Plan
planning documents such as
concepts and definitions.
Policy Rules specific to a project. Policy
Calibration,
Engineering,
Instructions for completing a Maintenance,
Procedure Procedure
task. Modification,
Operating, Standard,
Test
D:\Docstoc\Working\pdf\7e6e81a1-c56e-42f0-a0ad-4ac582ec9361.xlsDoc types
Based on MY/AK discussion Jan. 24 26/05; last edited Feb.1
Other classes of documentation/records: Cat A, Cat C, uncontrolled, AIDS, ECR, Waiver, PFR?, Drawings
Page 3 of 9
Document Types
Metadata Working
M subtypes Definition Project Information P subtypes Notes
Group
Documents reflecting actions
Project Authorization leading up to and including
Agreement/Contract;
File the authorization for initiation
of a project.
JPL proposals to sponsors,
Proposal Proposal/Announcement Proposal; AO
including related materials.
DPA, FMECA, WCA,
Report Analysis
Stress
Report List
Report Matrix
May include Trade Studies,
Benchmarking, Data Log, Metric,
packages, test plans and Assessment, Test,
log, problem report, status reports, MCDL, Reference Significant
Report report, study report/trade and Technical Reports. Report Event/Status, End
study Record of progress or activity. Item Data Package,
Problems associated ECR and Waiver for
spacecraft, including flight and contractors
flight support equipment
Report Study
Documents that establish the
requirements of spacecraft
Requirement hardware, software, or Requirement
computer systems as needed
to fulfill the project objectives.
Schedules and Proposed workforce, budget
Schedule
Forecasts and schedule.
Software component files,
including any source code or
Software documentation would
Software executable program files, Code/Script
be separate type for Alix
configuration files, make files,
etc.
Charter/role Charter/role
D:\Docstoc\Working\pdf\7e6e81a1-c56e-42f0-a0ad-4ac582ec9361.xlsDoc types
Based on MY/AK discussion Jan. 24 26/05; last edited Feb.1
Other classes of documentation/records: Cat A, Cat C, uncontrolled, AIDS, ECR, Waiver, PFR?, Drawings
Page 4 of 9
Document Types
Metadata Working
M subtypes Definition Project Information P subtypes Notes
Group
No equivalent Unspecified (was Miscellaneous)
Costing,
No equivalent Model Mathematical,
Statistical
No equivalent Notes
No equivalent Notice e.g., GIDEP?
Journal article Proceeding/Article
Meeting paper Proceeding/Article
No equivalent because a
No equivalent Standard
Category C document type
D:\Docstoc\Working\pdf\7e6e81a1-c56e-42f0-a0ad-4ac582ec9361.xlsDoc types
Based on MY/AK discussion Jan. 24 26/05; last edited Feb.1
Other classes of documentation/records: Cat A, Cat C, uncontrolled, AIDS, ECR, Waiver, PFR?, Drawings
Page 5 of 9
Metadata Compilation
Element Name Description Values, Guidance and "Gold Source" Repeating?
Mandatory Elements
Author Preparer or responsible individual. Syntax: First name Last name or Last name, First name yes
Date Date of this version, usually cover date.
Values: 1) Controlled Document, 2) Record, 3) Other Working Material.
High-level classification indicating whether Controlled Document is defined as a document under version control and will appear on an
Document Class the item is a controlled document, record or MCDL when released. Record is defined as an unchanging document that is evidence of
neither. doing work, e.g., email, meeting minutes, test results, etc. Other is everything else (drafts,
etc.)
Action item; Agreement files; Business Management Record; Charter/Role; Configuration
Control Record; Contract/Procurement Record; Correspondence; Data; Design or
Document Type The kind of document. specification; Drawing; Form or Template; Graphic/Multimedia; Guideline; Journal Article;
Meeting or Review File; Meeting Paper; Plan; Policy; Procedure; Project Authorization File;
Proposal; Report; Requirement; Schedules and Forecasts; Software
File Name Label given to the file.
System supplied. Source: http://www.w3.org: Internet Media Type (RFC 1590) and MIME
Format File/Mime Type (e.g., .pdf, .doc, .xls)
Content Type (RFC 1521)
D:\Docstoc\Working\pdf\7e6e81a1-c56e-42f0-a0ad-4ac582ec9361.xls Metadata
Rev. MY Feb. 1, 2005
Official location: https://bravo-lib.jpl.nasa.gov/docushare/dsweb/Get/Document-28864 After Feb. 1 meeting
Page 6 of 9
Metadata Compilation
Element Name Description Values, Guidance and "Gold Source" Repeating?
Entity creating the work, typically the "home"
Values: from JPL Taxonomy. Also require ability for user to input organizations not on the
Organization of the author. (Maybe JPL Org # or yes
list.
contractor company name.)
Indicates where item resides: in which
Repository/Location Should be system supplied.
repository or other location.
Not yet determined. Possible Values: 1) Discreet; 2) Proprietary (may have subtypes for
Sensitivity JPL and external) 3) Intellectual Property; 4) Export Controlled 5) Limited Distribution 6) yes
None (Unlimited Distribution); 7) Not Assessed
Title Descriptive name. Title should be as specific, distinctive, and descriptive as possible
D:\Docstoc\Working\pdf\7e6e81a1-c56e-42f0-a0ad-4ac582ec9361.xls Metadata
Rev. MY Feb. 1, 2005
Official location: https://bravo-lib.jpl.nasa.gov/docushare/dsweb/Get/Document-28864 After Feb. 1 meeting
Page 7 of 9
Metadata Compilation
Element Name Description Values, Guidance and "Gold Source" Repeating?
CONDITIONAL ELEMENTS (ARE OPTIONAL WHEN CONDITIONS DO NOT APPLY)
Condition: If Project-related
Project Name Values: from JPL Taxonomy
Condition: if Controlled Document
Hierarchy information based on document Source: ? Values: Level 1= Program; Level 2 = Project; Level 3=System; Level
Document Level
tree/approval level. 4=Subsystem; Level 5=Box/Assembly
Unique identifier(s) that persists beyond a
For example, D#; MGS-4-1234
particular repository such as a JPL
Document Number Both a D# and a Project Document Number are strongly encouraged, where appropriate. If yes
document number and/or project document
system assigned, should be persistent.
number.
Current status of item based on pre-defined
Document State Source: JPL Rules! Document and Data Control Requirement (DocID 57034):
list.
Number or letter that identifes the unique
Revision/Version For example, 0, 1, 2, 3 or A, B, C
iteration of the document.
Condition: If Document /Record
Predefined code that identifies records Automatically populated when a document type is selected. Record series format typically
Retention Schedule
retention schedule. is N-NAN-Na. No format determined yet for Caltech records.
Condition: When approved by DRS for public release
The number assigned by JPL Document
DRS Clearance Number Review when the document is approved for Assigned by DRS
unlimited external release.
Condition: If Submitted by Someone other than Author or if Someone other than Author is Responsible
The individual, if other than the author, who
submitted or uploaded the item. The person
responsible for the document long-term and
Submitter/Custodian yes
who ensures continuity over the project's
lifetime, such as the appropriate-level
manager or the approver.
D:\Docstoc\Working\pdf\7e6e81a1-c56e-42f0-a0ad-4ac582ec9361.xls Metadata
Rev. MY Feb. 1, 2005
Official location: https://bravo-lib.jpl.nasa.gov/docushare/dsweb/Get/Document-28864 After Feb. 1 meeting
Page 8 of 9
Metadata Compilation
Element Name Description Values, Guidance and "Gold Source" Repeating?
OPTIONAL ELEMENTS
Additional Date yes
Audience Values: from NASA Taxonomy Facet
Business Purpose Values: from NASA Taxonomy Facet
Competencies Values: from NASA Taxonomy Facet yes
Description Overview of the content.
Industries
Instruments Values: from NASA Taxonomy Facet yes
System requirement but not a document requirement. Examples: pregnancy vs. family
Keywords Search terms not in the title or body. leave. Lists associated/equivalent terms. Author inputs keywords to assist in determining yes
subject terms.
Locations Values: from NASA Taxonomy Facet. Autofill if possible yes
Source: JPL Rules: JPL Project Lifecycle (DocID=58813): Values = Proposal; Pre-Phase
Predefined lifecycle phase of the mission or
Phase A; Formulation Phase (with subtypes A and B); Phase C/D (with subtypes C and D); Phase
project associated with this item.
E
Pre-defined topic(s) or category(ies) that
Subject Values: from NASA Taxonomy Facet yes
describe the item.
may come from an additional level of the
System/Subsystem
WBS
Team/Group Name of associated team or group. yes
Source: JPL Rules! Standard JPL Work Breakdown Structure (DocID 59533). Values:
The JPL Standard Flight Project Work
1=Project Management; 2=Project System Engineering; 3=Safety & Mission Assurance;
WBS # Breakdown Structure number associated
4=Mission Design; 5=Science; 6=Payload System; 7=Flight System; 8=Mission Ops
with this document.
System; 9=Launch System (authority: JPL Rules Standard WBS)
D:\Docstoc\Working\pdf\7e6e81a1-c56e-42f0-a0ad-4ac582ec9361.xls Metadata
Rev. MY Feb. 1, 2005
Official location: https://bravo-lib.jpl.nasa.gov/docushare/dsweb/Get/Document-28864 After Feb. 1 meeting
Page 9 of 9
Related docs
