Policies and Procedures - Revision history

Gordp: /* Policy */

2007-02-20T21:51:50Z

Policy

← Older revision		Revision as of 21:51, 20 February 2007
Line 15:		Line 15:

	==Policy==		==Policy==
			*Users taking assets off-site require their ID-barcodes to be recorded, by Research staff
	*Assets to be taken off-site require their barcodes to be recorded, by Research staff		*Assets to be taken off-site require their barcodes to be recorded, by Research staff
	*Users taking assets off-site require their ID-barcodes to be recorded, by Research staff		*Assets to be taken off-site require an accompanying "Conveyance Form", which communicates to Security and Facilities that the asset-movement has been approved and recorded by Research staff
	*Assets to be taken off-site require an accompanying "Conveyance Form", which communicates to Security and Facilities that the asset ~~shifting~~ has been approved and recorded by Research staff

	==Procedure==		==Procedure==
	*have a member of the Research staff scan your ID-barcode, and the barcodes of the assets to be taken off-site		*have a member of the Research staff scan your ID-barcode, and the barcodes of the assets to be taken off-site
	*have a member of the Research staff provide a copy of the "Conveyance Form". Present this to Security or Facilities, as necessary. When returning from off-site, this same document my assist you in proving ownership and successfully removing the assets from the off-site venue.		*have a member of the Research staff provide a copy of the "Conveyance Form". Present this to Security or Facilities, as necessary. When returning from off-site, this same document my assist you in proving ownership and successfully removing the assets from the off-site venue.

Gordp: /* Rationale */

2007-02-20T21:50:47Z

Rationale

← Older revision		Revision as of 21:50, 20 February 2007
Line 10:		Line 10:
	:*Conferences (conference-hosting resources particularly, then presentation-resources, lastly attending-resources)		:*Conferences (conference-hosting resources particularly, then presentation-resources, lastly attending-resources)
	<br>		<br>
	<p>There is an expectation that the user who signs out the asset(s) treat it (them) as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition it (they) left in. This can be especially challenging for publicly-accessible circumstances, such as installations. Securing the assets may require substantial creative planning by the user.</p>		<p>There is an expectation that the user who signs out the asset(s) treat it (them) as their own. Every reasonable step must be taken to ensure that the asset(s) come(s) back in the same condition it (they) left in. This can be especially challenging for publicly-accessible circumstances, such as installations. Securing the assets may require substantial creative planning by the user.</p>
	<br>		<br>
	<p>In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.</p>		<p>In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.</p>

Gordp: /* Rationale */

2007-02-20T21:50:25Z

Rationale

← Older revision		Revision as of 21:50, 20 February 2007
Line 9:		Line 9:
	:*Installations		:*Installations
	:*Conferences (conference-hosting resources particularly, then presentation-resources, lastly attending-resources)		:*Conferences (conference-hosting resources particularly, then presentation-resources, lastly attending-resources)
			<br>
			<p>There is an expectation that the user who signs out the asset(s) treat it (them) as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition it (they) left in. This can be especially challenging for publicly-accessible circumstances, such as installations. Securing the assets may require substantial creative planning by the user.</p>
	<br>		<br>
	<p>In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.</p>		<p>In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.</p>
	~~<br>~~
	<p>There is an expectation that the user who signs out the asset(s) treat it (them) as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition it (they) left in. This can be especially challenging for publicly-accessible circumstances, such as installations. Securing the assets may require substantial creative planning by the user.</p>

	==Policy==		==Policy==

Gordp: /* Rationale */

2007-02-20T21:49:46Z

Rationale

← Older revision		Revision as of 21:49, 20 February 2007
Line 12:		Line 12:
	<p>In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.</p>		<p>In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.</p>
	<br>		<br>
	There is an expectation that the user who signs out the asset(s) treat it (them) as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition it (they) left in. This can be especially challenging for publicly-accessible circumstances, such as installations. Securing the assets may require substantial creative planning by the user.		<p>There is an expectation that the user who signs out the asset(s) treat it (them) as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition it (they) left in. This can be especially challenging for publicly-accessible circumstances, such as installations. Securing the assets may require substantial creative planning by the user.</p>

	==Policy==		==Policy==

Gordp: /* Rationale */

2007-02-20T21:49:23Z

Rationale

← Older revision		Revision as of 21:49, 20 February 2007
Line 10:		Line 10:
	:*Conferences (conference-hosting resources particularly, then presentation-resources, lastly attending-resources)		:*Conferences (conference-hosting resources particularly, then presentation-resources, lastly attending-resources)
	<br>		<br>
	In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.		<p>In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.</p>
	<br>		<br>
	There is an expectation that the user who signs out the asset(s) treat it (them) as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition it (they) left in. This can be especially challenging for publicly-accessible circumstances, such as installations. Securing the assets may require substantial creative planning by the user.		There is an expectation that the user who signs out the asset(s) treat it (them) as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition it (they) left in. This can be especially challenging for publicly-accessible circumstances, such as installations. Securing the assets may require substantial creative planning by the user.

Gordp: /* Rationale */

2007-02-20T21:48:54Z

Rationale

← Older revision		Revision as of 21:48, 20 February 2007
Line 8:		Line 8:
	:*Conducting research		:*Conducting research
	:*Installations		:*Installations
			:*Conferences (conference-hosting resources particularly, then presentation-resources, lastly attending-resources)
	<br>		<br>
	~~:*Conferences (conference-hosting resources particularly, then presentation-resources, lastly attending-resources)~~
	In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.		In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.
	<br>		<br>

Gordp: /* Rationale */

2007-02-20T21:48:39Z

Rationale

← Older revision		Revision as of 21:48, 20 February 2007
Line 4:		Line 4:
	:*manage the entire life-cycle of an asset (purchase date, vendor, price, repair-history, notes, end-of-life, etc)		:*manage the entire life-cycle of an asset (purchase date, vendor, price, repair-history, notes, end-of-life, etc)
	:*track the comings and goings of research assets, when they're required off-site		:*track the comings and goings of research assets, when they're required off-site
			<br>
	Examples of appropriate offsite usage may include:		Examples of appropriate offsite usage may include:
	:*Conducting research		:*Conducting research
	:*Installations		:*Installations
			<br>
	:*Conferences (conference-hosting resources particularly, then presentation-resources, lastly attending-resources)		:*Conferences (conference-hosting resources particularly, then presentation-resources, lastly attending-resources)
	:In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.		In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.
	<br>		<br>
	:There is an expectation that the user who signs out the asset(s) treat it (them) as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition it (they) left in. This can be especially challenging for publicly-accessible circumstances, such as installations. Securing the assets may require substantial creative planning by the user.		There is an expectation that the user who signs out the asset(s) treat it (them) as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition it (they) left in. This can be especially challenging for publicly-accessible circumstances, such as installations. Securing the assets may require substantial creative planning by the user.

	==Policy==		==Policy==

Gordp: /* Rationale */

2007-02-20T21:46:22Z

Rationale

← Older revision		Revision as of 21:46, 20 February 2007
Line 7:		Line 7:
	:*Conducting research		:*Conducting research
	:*Installations		:*Installations
	:*Conferences (particularly presentation resources)		:*Conferences (conference-hosting resources particularly, then presentation-resources, lastly attending-resources)
	In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered.		:In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered, historically.
	<br>		<br>
	There is an expectation that the user who signs out the asset(s) treat is as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition they left in. This can be especially challenging for publicly-accessible circumstances, such as installations~~, where securing~~ the assets may require substantial creative planning by the user.		:There is an expectation that the user who signs out the asset(s) treat it (them) as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition it (they) left in. This can be especially challenging for publicly-accessible circumstances, such as installations. Securing the assets may require substantial creative planning by the user.

	==Policy==		==Policy==

Gordp: /* Rationale */

2007-02-20T21:43:04Z

Rationale

← Older revision		Revision as of 21:43, 20 February 2007
Line 2:		Line 2:
	==Rationale==		==Rationale==
	Almost every asset within SIAT Research has a barcode-label. These allow us to:		Almost every asset within SIAT Research has a barcode-label. These allow us to:
	*manage the entire life-cycle of an asset (purchase date, vendor, price, repair-history, notes, end-of-life, etc)		:*manage the entire life-cycle of an asset (purchase date, vendor, price, repair-history, notes, end-of-life, etc)
	*track the comings and goings of research assets, when they're required off-site		:*track the comings and goings of research assets, when they're required off-site
	Examples of appropriate offsite usage may include:		Examples of appropriate offsite usage may include:
	*Conducting research		:*Conducting research
	*Installations		:*Installations
	*Conferences (particularly presentation resources)		:*Conferences (particularly presentation resources)
	In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered.		In the event that an asset is stolen while off-site, we can support the user filing a police-report by providing serial-numbers, and possibly other details as required. If an asset '''is''' stolen, there '''may''' be recourse through SFU's internal insurance. "Own-damage" has not been covered.
	<br>		<br>

Gordp: /* Background */

2007-02-20T19:41:32Z

Background

← Older revision		Revision as of 19:41, 20 February 2007
Line 1:		Line 1:
	=Signing out Research Equipment=		=Signing out Research Equipment=
	==~~Background~~==		==Rationale==
	Almost every asset within SIAT Research has a barcode-label. These allow us to:		Almost every asset within SIAT Research has a barcode-label. These allow us to:
	*manage the entire life-cycle of an asset (purchase date, vendor, price, repair-history, notes, end-of-life, etc)		*manage the entire life-cycle of an asset (purchase date, vendor, price, repair-history, notes, end-of-life, etc)
Line 11:		Line 11:
	<br>		<br>
	There is an expectation that the user who signs out the asset(s) treat is as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition they left in. This can be especially challenging for publicly-accessible circumstances, such as installations, where securing the assets may require substantial creative planning by the user.		There is an expectation that the user who signs out the asset(s) treat is as their own. Every reasonable step must be taken to ensure that the asset(s) come back in the same condition they left in. This can be especially challenging for publicly-accessible circumstances, such as installations, where securing the assets may require substantial creative planning by the user.


	==Policy==		==Policy==