Acq Notes

AcqNote Description Area

Systems Engineering

Process Inputs Outputs Loops

Process Inputs, Outputs and Loops are part of teh steps that are included in the Systems Engineering Process. Process Inputs  The customer’s/User’s needs, objectives and requirements in terms of capabilities, measures of effectiveness, environments, and constraints initiate the systems engineering process. A few of the inputs include: Customer Needs/Objectives/Requirements Measures of Effectiveness (MoE), Environments, Constraints […]

Systems Engineering

Process Inputs Outputs Loops Read More »

Contracts & Legal

Federal Acquisition Regulation Index

The Federal Acquisition Regulations (FAR) are divided into 53 parts and organized into eight (8) Subchapters designated A through H. Each part is then divided into subparts, sections, and subsections, with further divisions below the subsection level.  Website: Federal Acquisition Regulation Index Subchapter A—General Part 1—Federal Acquisition Regulations System Part 2—Definitions of Words and Terms

Contracts & Legal

Federal Acquisition Regulation Index Read More »

Systems Engineering

Physical Architecture

The physical architecture is the physical layout of a system and its components in a schema.  It refers to some representation of the structure or organization of the physical elements of the system.  The physical architecture should be part of the Allocated and Product Baselines. Definition: A physical architecture is an arrangement of physical elements

Systems Engineering

Physical Architecture Read More »

Systems Engineering

Operational Requirements Document

An Operational Requirements Document (ORD) was replaced by the Capability Development Document (CDD).  The ORD described the overall requirements for one system, how it interacts with other systems, and a system’s performance goals. An ORD is generally more detailed than a Concept of Operations (CONOPS). Older programs will have an ORD. The Mission Needs Statement

Systems Engineering

Operational Requirements Document Read More »

Contracts & Legal

Economy Act

The Economy Act (31 U.S.C. 1535) authorizes agencies to enter into agreements to obtain supplies or services by Interagency Acquisition. The Economy Act also provides authority for the placement of orders between major organizational units within an agency; procedures for such intra-agency transactions are addressed in agency regulations. The Economy Act applies when more specific

Contracts & Legal

Economy Act Read More »

Contracts & Legal

Defense Federal Acquisition Regulations Supplement (DFARS)

The Defense Federal Acquisition Regulations Supplement (DFARS) is the official DoD regulator supplement to the Federal Acquisition Regulations (FAR).  A Program Manager (PM) and Program Contracting Officer (PCO) must understand the FAR’s and DFARS’s that pertain to their program. Website: DFARS Table of Content The Defense Federal Acquisition Regulations Supplement (DFARS) Procedures, Guidance, and Information

Contracts & Legal

Defense Federal Acquisition Regulations Supplement (DFARS) Read More »

Systems Engineering

Operational Requirements

A requirement is an attribute of a product, service, or system necessary to produce an outcome(s) that satisfies the needs of a person, group, or organization. Operational Requirements are capabilities, performance measurement (Measures of Effectiveness, Measures of Performance, Measures of Suitability & Technical Performance Measurements), and processes needed to address mission area deficiencies, evolving threats,

Systems Engineering

Operational Requirements Read More »

Contracts & Legal

Data Rights

Data Rights (FAR Subpart 27.4) consist of the legal rights a contractor and/or the government have to use technical, Intellectual Property (IP), and software data. This data can include a proposal, source selection, software, management, concepts, and technical packages. Definition: Data Rights refer to the Government’s nonexclusive license rights in two categories of valuable intellectual

Contracts & Legal

Data Rights Read More »

Systems Engineering

Open-Standard System Architecture

An Open-Standard System Architecture (OSSA) is an architecture development approach that utilizes open standards to reduce the cost/risk of ownership of weapons systems, delay system obsolescence, and allow the fielding of capability more quickly. An open systems approach reduces weapon system cost by facilitating the use of widely accepted standard products from multiple suppliers in

Systems Engineering

Open-Standard System Architecture Read More »

Systems Engineering

Modular Open Systems Approach (MOSA)

Modular Open Systems Approach (MOSA) is an integrated business and technical strategy for the assessment and implementation of open systems in the DoD. An open system is a system that employs modular design tenets, uses widely supported and consensus-based standards for its key Interfaces, and is subject to Validation and Verification, including Test and Evaluation,

Systems Engineering

Modular Open Systems Approach (MOSA) Read More »

Systems Engineering

Modeling and Simulation (M&S)

Modeling and Simulation (M&S) is the use of models, including emulators, prototypes, simulators, and stimulators, either statically or over time, to develop data as a basis for making managerial or technical decisions. The terms “modeling” and “simulation” are often used interchangeably. [2] M&S is a tool used in systems engineering to gather information to make

Systems Engineering

Modeling and Simulation (M&S) Read More »

Contracts & Legal

Contractor Performance Report (CPR)

Note: The Integrated Program Management Report (IPMR) has replaced the Contractor Performance Report (CPR) for new contracts as of  July 1, 2012. The Contractor Performance Report (CPR) provides contract cost and schedule performance data that is used to identify problems early on an acquisition contract and forecast future contract performance in Earned Value Management (EVM).

Contracts & Legal

Contractor Performance Report (CPR) Read More »

Systems Engineering

Measures of Effectiveness (MOE)

Measures of Effectiveness (MOE) are measures designed to correspond to the accomplishment of mission objectives and the achievement of desired results. They quantify the results to be obtained by a system and may be expressed as probabilities that the system will perform as required. The Capability Based Assessment (CBA) defines the MOE’s and articulates them

Systems Engineering

Measures of Effectiveness (MOE) Read More »

Program Management

Free-rein Leadership Style

Free-rein leadership, also called Laissez-Faire, is a type of leadership style in which leaders are hands-off and allow group members to make the decisions. Mangers set objectives and employees are free to do whatever is appropriate to accomplish those objectives. The traits managers need in such an organization include warmth, friendliness, and understanding.  Free-rein is

Program Management

Free-rein Leadership Style Read More »

Systems Engineering

Interfaces

Interfaces are the functional and/or the physical interface between two components with a system. The components can be internal or external to the system.  It’s key to understand these interfaces in systems engineering to make sure systems components work properly with each other. See Interface Management Interface definition and control Interface definition and control are

Systems Engineering

Interfaces Read More »

Contracts & Legal

Contractor Performance Assessment Reporting System

The Contractor Performance Assessment Reporting System (CPARS) is a web-enabled application that collects and manages the library of automated contractor assessment data.  A Contractor Performance Assessment Report (CPAR) assesses a contractor’s performance and provides a record, both positive and negative, of a given contract during a specific period of time.  Each assessment is based on

Contracts & Legal

Contractor Performance Assessment Reporting System Read More »

Contracts & Legal

Contracting Officer’s Representative (COR)

A Contracting Officer’s Representative (COR) (FAR 106.4) is an individual authorized in writing by the Contracting Officer to perform specific technical or administrative contract functions. The COR must receive a written designation of their authority to act on behalf of the contracting officer. (DFARS Subsection 201.602-2). COR responsibilities include monitoring the contractor’s performance and performing

Contracts & Legal

Contracting Officer’s Representative (COR) Read More »

Program Management

Earned Value Management (EVM)

Earned Value Management (EVM) is a project management technique for measuring project performance and progress in an objective manner. EVM has the ability to combine measurements of scope, schedule, and cost in a single integrated system. It’s notable for its ability to provide accurate forecasts of project performance problems. Early EVM research showed that the

Program Management

Earned Value Management (EVM) Read More »

Systems Engineering

Interface Management

Interface Management identifies, develops, and maintains the external and internal interfaces necessary for system operation. It supports control measures (Configuration Management) to ensure that all internal and external interface requirement changes are properly documented in accordance with the configuration management plan and communicated to all affected configuration items. Definition: Interface management includes the activities of defining,

Systems Engineering

Interface Management Read More »